The package is documented, tested, and has release notes, with a small dependency surface and no install-time scripts. Its matching, organization-owned repository is not archived or deprecated, but the project shows little evidence of current maintenance or security oversight.
42%
Total Score
50
100
75
75
The latest release was about 9 years ago, and there have been no releases in the last 12 months. This is strong evidence of abandonment risk despite the package having nine total releases.
The repository recorded 0 commits and 0 active maintainers in the last 3 months, reinforcing the long release gap and indicating no observed current maintenance.
Composer is used for builds, but no security scanning tools were detected. This modestly reduces supply-chain hygiene evidence without proving the package is unsafe.
The repository is not archived, which is a compensating signal, but its last push was about 8 years ago and does not offset the broader inactivity evidence.
The repository has no security policy, leaving vulnerability reporting and response expectations unclear. This is a secondary transparency gap alongside the maintenance concerns.
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.