Clear documentation, tests, and a permissive license reduce adoption friction. The project has not released since January 2015 and has had no commits in the last three months, making maintenance risk substantial.
42%
Total Score
25
100
70
50
The package has only two releases, both in January 2015, with no releases in the last 12 months. This long release gap is strong evidence of abandonment risk.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the package's extended release silence. The repository is not archived, but that does not compensate for the lack of observed activity.
Two issues remain open, while there were no new or closed issues and no pull-request activity in the last month. This is a smaller concern than the absent release and commit activity, but it provides no evidence of active maintenance.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This adds a transparency concern, although it is secondary to the project's prolonged inactivity.
Version 0.1.1 is not a prerelease, but it remains below a stable major version and has not advanced since the package's early release period. This limits confidence in long-term API maturity.
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.