The package is small, documented, tested, and has no install-time scripts. Its single maintainer and missing security policy provide limited ongoing assurance despite clear licensing and a matching source repository.
42%
Total Score
25
100
75
75
The package has had only one release, with no new release in roughly 13 years. That is strong evidence of abandonment risk for a dependency, even though the package may be stable.
There were no commits or active maintainers in the last three months, consistent with the repository having been inactive since 2013. This materially increases abandonment risk.
Only one registry publishing account is listed, leaving limited visible publishing redundancy. The linked repository is user-owned, so this is a modest concern rather than evidence of organizational backing.
Composer build tooling is present, but no security-scanning tooling was detected. This is a maintenance and assurance gap, though it is secondary to the long inactivity period.
The repository is not archived, which is a positive counterpoint to the old release history, but its last push was in December 2013 and therefore does not demonstrate current maintenance.
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.