The codebase is tiny and has no security scanning or security policy, limiting assurance. Its README, MIT declaration, and matching repository provide basic transparency, but they do not offset the lack of maintenance evidence.
44%
Total Score
50
86
50
Only one release exists, published over five years ago, with no releases in the last 12 months. This is strong evidence of an unmaintained dependency.
The repository has recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and raising abandonment risk.
Composer build tooling is present, but no security scanning tools were detected. For a small package this is a meaningful, though not severe, assurance gap.
The repository has no security policy. Combined with the absence of security scanning, this leaves no documented route or process for reporting and handling vulnerabilities.
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.