The MIT license, clear README, and organization-owned repository provide useful transparency. The tiny project footprint and lack of security tooling limit confidence in ongoing care.
38%
Total Score
50
71
75
This package has only one release, published about 11 years ago, with no releases in the last 12 months. That 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 last push being about 11 years ago. No newer activity compensates for this gap.
The repository has zero stars and one fork, offering little supporting evidence of community adoption. Popularity is secondary, but it does not compensate for the inactive release and commit history.
Composer is used for the build, but no security-scanning tools were detected. For this small, old package this is a modest transparency gap rather than a severe risk.
No repository security policy was found. This weakens disclosure transparency, although the absence is less significant than the package's long 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.