The package is small and clearly documented, with a matching source repository, tests, and no install-time scripts. Its single maintainer, limited security practices, and older dependency stack leave little evidence of ongoing support.
42%
Total Score
38
100
72
83
The package has had only two releases, with the latest on March 27, 2017 and no releases in the last 12 months. This is strong evidence that maintenance has stopped for a package intended for an evolving framework ecosystem.
There were zero commits and zero active maintainers in the last three months. Combined with the repository's last push in 2019, this indicates prolonged inactivity and materially raises abandonment risk.
Only one registry account has publish access. For this user-owned project that indicates a thin publishing and continuity base, though it does not by itself prove abandonment.
The registry namespace and repository owner match, but both are tied to a single user rather than an organization. This supports package identity while offering limited evidence of institutional backing.
There were no new or closed issues or pull requests in the last month, while one issue and two pull requests remain open. This suggests little current project attention.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
mhetreramesh/flysystem-backblaze Version * | — | — |
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.