The package includes a README, release notes, and matching MIT licensing, with no install-time scripts. Its single-maintainer ownership and absent security tooling reduce resilience for a package that has seen little recent activity.
38%
Total Score
25
71
75
The latest release was published in June 2015, about 11 years ago, and there have been no releases in the last 12 months. The early median interval of about 17 days shows the project once released regularly, but does not offset the prolonged gap.
The repository recorded zero commits and zero active maintainers in the last three months, with its last push in March 2017, about 9 years ago. This is strong evidence of abandonment risk.
Only one registry account has publish access. Because the repository is owned by an individual rather than an organization, this provides little redundancy if that maintainer stops publishing.
Composer is used for builds, but no security-scanning tool is configured. That leaves dependency and code issues less likely to be caught automatically.
The repository has no security policy. This weakens vulnerability-reporting transparency, although it is a secondary concern compared with the long maintenance gap.
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.