The package has a clear MIT license, a README, and a changelog, with no install-time scripts or deprecation notice. Its repository does not clearly identify the package, and it has no security policy or scanning; pinning this old release leaves substantial maintenance uncertainty.
38%
Total Score
50
79
75
The package has only three releases, with none in the last 12 months; its latest release was nearly 9 years ago. This is strong evidence of abandonment risk for a library dependency.
The repository recorded zero commits and zero active maintainers in the last 3 months, consistent with the registry's long release gap. No provided signal shows current maintenance capacity.
The repository name does not match the package name and its README does not mention the package, so the linked source may not clearly belong to this release. That weakens source transparency.
Composer is used for the build, which is appropriate, but no security-scanning tool is present. This is a modest transparency and maintenance gap rather than evidence of unsafe code.
The linked repository has no security policy. For an old library with no recent activity, this leaves no documented path for reporting or handling security issues.
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.