Risky to adopt: the package has not released or received repository commits since October 2014, making abandonment and compatibility problems likely. It is licensed, has tests, and is not deprecated or archived, but those positives do not offset the very long maintenance gap.
35%
Total Score
50
100
78
75
The latest release was in October 2014, with no releases in the last 12 months despite the package being over 12 years old. This long release gap is strong evidence of abandonment risk.
The repository had zero commits and zero active maintainers in the last three months. Combined with the last push in 2014, this indicates a severe and sustained maintenance gap.
The repository has zero stars and forks and only one watcher. Popularity is not decisive by itself, but these counters provide little supporting evidence of an active user or contributor community.
Composer is used as a build tool, which supports reproducible project structure, but no security scanning tools are present. Given the package's long inactivity, the lack of security tooling increases transparency and maintenance concerns.
The repository has no security policy. This is a transparency gap, particularly for a dependency that has received no maintenance for many years.
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.