The codebase is small and clearly tied to the package, with a usable README, stable versioning, and no install-time scripts. Its single maintainer, absent security scanning, and nearly eight years without updates provide little ongoing support.
46%
Total Score
25
100
75
83
The package has had no releases in the last 12 months, and its latest release was on December 20, 2018—nearly eight years ago at collection time. This is strong evidence of abandonment risk for a dependency.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap. No provided maintenance signal compensates for this lack of recent activity.
Only one registry account has publishing access. For this user-owned project that is a thin maintainer base and increases continuity risk, especially alongside the absence of recent activity.
Composer is used as the build tool, which supports reproducible package handling, but no security-scanning tool is configured. The missing scanning is a modest hygiene concern rather than a severe dependency risk on its own.
The repository is not archived, which leaves the project technically maintainable, but its last push was also on December 20, 2018. The unarchived status only partly offsets the observed inactivity.
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.