The project has had no new release or commit activity for more than 12 years, and it has no security policy or scanning tools. Clear documentation, tests, a minimal dependency set, and an MIT declaration reduce adoption friction but do not offset the abandonment risk.
40%
Total Score
0
100
75
75
This package has only one release, published more than 12 years ago, with no releases in the last 12 months. That is strong evidence of abandonment for a dependency that may need compatibility or security updates.
The repository recorded zero commits and zero active maintainers in the last 3 months, consistent with the package's long release silence. No provided maintenance signal compensates for this inactivity.
Composer is used as a build tool, but no security-scanning tools are present. The missing scanning is a modest hygiene concern rather than evidence that the package is unsafe.
The repository has no security policy, leaving no documented route for reporting vulnerabilities. This is a transparency gap, though the package's small scope limits its weight compared with the maintenance evidence.
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.