It has a README, tests, and a matching repository, but its early-stage status and single-person ownership provide little evidence of ongoing support. The absence of security tooling adds a smaller transparency concern.
38%
Total Score
33
100
67
83
Only two releases were published, both in February 2020, with no releases in the following six years. This is strong evidence of abandonment for a package intended as an application dependency.
There were no commits and no active maintainers in the last three months, following a last push in February 2020. This is a direct and substantial abandonment risk.
Registry publishing access is held by one maintainer. Because the repository is user-owned rather than organization-backed, this gives the project a thin support base when combined with its lack of recent activity.
The registry namespace and repository are both owned by the same individual account. This confirms ownership alignment but provides no organizational backing to offset the thin maintenance base.
The repository has zero stars and forks and only one watcher. Popularity is not required for health, but these counters provide no supporting evidence of broad community adoption or backup maintenance.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
jorisros/file-storage Version ^1.0 | — | — |
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.