Its README, tests, license, and single runtime dependency make the small codebase easier to evaluate. A single publisher and absent security policy leave limited support and oversight.
42%
Total Score
25
100
71
83
The package has only one release, published more than 11 years ago, with no releases in the last 12 months. This is strong evidence of abandonment risk for a dependency.
There were zero commits and zero active maintainers in the last three months, consistent with the package's long release gap and indicating no current maintenance.
Only one registry account has publishing access. That is a thin publishing base, and the provided project backing identifies an individual rather than an organization.
The project uses Make and Composer, which supports repeatable builds, but no security scanning tooling was found. That is a modest hygiene gap rather than evidence of unsafe code.
The repository has no security policy. For a small, inactive package this reduces transparency about vulnerability reporting and maintenance response.
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.