The single-person ownership and absent security policy leave little resilience if the project needs attention. A readable package with tests, release notes, and a clear MIT license reduces adoption friction, but does not offset its limited project capacity.
42%
Total Score
25
79
75
The package has made only two releases, with none in the last 12 months; its latest release was published in April 2014, over 12 years ago. This is strong evidence of abandonment risk for a dependency.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap. No provided maintenance signal compensates for this lack of recent activity.
Only one registry maintainer is listed, leaving a thin publishing and maintenance base. The repository is user-owned rather than organization-backed, so there is no provided evidence of broader continuity.
The repository has zero stars and forks and only two watchers, providing little evidence of an active user or contributor community. Popularity is supporting evidence rather than decisive on its own, but it does not offset the inactivity.
The repository has no security policy, which weakens vulnerability-reporting transparency. This is a secondary concern alongside the much stronger signs of inactivity.
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.