The GPL-2.0 declaration, readable documentation, and organization-backed repository improve transparency. The project has no recent development activity and no security scanning, so its old code should be treated as an adoption liability.
40%
Total Score
50
79
50
Only two releases were published, both in March 2016, with none in the last 12 months. That long publishing gap is strong evidence of abandonment risk for a dependency.
The repository recorded 0 commits and 0 active maintainers during the last 3 months, consistent with the roughly 10-year-old release history and lack of current maintenance.
There were no new or closed issues and no merged pull requests in the last month. This provides no evidence of active support or defect resolution.
Composer is used as a build tool, which supports reproducibility, but no security scanning tools were detected. For an old package, that missing verification increases maintenance and transparency concerns.
The repository has no security policy. This is a secondary transparency gap, especially alongside the absence of recent maintenance, but it is not severe on its own.
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.