The stable version, included tests, license files, and minimal runtime dependency support adoption. Its release and repository activity stopped in 2014, while security scanning and a security policy are absent; the license declarations also do not fully match the detected license text.
39%
Total Score
0
100
67
75
The package has only two releases, with none in the last 12 months, and its latest release was in 2014. This is strong evidence of abandonment risk, though the stable version may still be adequate for unchanged use cases.
The repository recorded zero commits and zero active maintainers in the last three months, matching the long release gap. No provided maintenance signal compensates for this inactivity.
A license file is present and the release declares licenses, so licensing is not absent. The detected MIT and BSD-3-Clause text does not fully match the declaration that also includes GPL-2.0, creating a transparency concern.
Composer build tooling is present, showing basic project structure, but no security scanning tools were detected. The missing scanning is a modest transparency and maintenance concern.
The repository has no security policy, leaving no stated process for reporting or handling vulnerabilities. This is a hygiene gap that matters more for a library with no recent maintenance activity.
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.