The package has clear licensing, a README, and a matching source repository. Its tiny project footprint and lack of security tooling leave little evidence of ongoing care; pinning this 2016-era code carries substantial maintenance risk.
38%
Total Score
50
86
50
The package has had only two releases, both around November 2016, with no releases in roughly nine years. That strongly raises abandonment risk for a dependency.
The repository recorded zero commits and zero active maintainers during the last three months, consistent with the long release gap and providing no evidence of current maintenance.
Composer is used for builds, but the repository has no security scanning tools. This is a meaningful transparency and maintenance gap for a package that has not changed in years.
The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. The absence adds to the package's limited maintenance evidence.
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.