Its single-maintainer project has no security policy and no demonstrated testing or security tooling, reducing confidence in ongoing support. The matching repository and stable release provide some transparency, but not enough to offset the maintenance risk.
39%
Total Score
33
75
83
The latest release was in February 2017, with no releases in the past 12 months. This is strong evidence of abandonment risk for a dependency receiving no recent maintenance.
The repository recorded zero commits and zero active maintainers in the last three months, confirming that the long release gap reflects inactivity rather than only delayed publishing.
One registry maintainer is consistent with a small user-owned project, but it leaves little maintainer redundancy when the repository also shows no recent activity.
The repository is owned by an individual rather than an organization, so the single-maintainer and inactivity concerns are not offset by visible organizational backing.
The repository has zero stars and forks and only one watcher, providing little supporting evidence of active community use or review. Popularity is secondary, but it does not compensate for the lack of maintenance.
We didn't find any vulnerabilities for this package.
No direct dependencies.
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.