Lock
42%
Total Score
unhealthy
A single release from May 2017, no recent commits, and no license make this a risky dependency.
The package has only one release, published about 9 years ago, with no releases in the last 12 months. This is strong evidence of abandonment risk for a dependency.
The repository recorded 0 commits and 0 active maintainers in the last 3 months, consistent with the last push occurring in May 2017. No provided signal shows current maintenance capacity.
No declared license, license file, or repository license file was detected. This creates a real legal and adoption concern because consumers cannot identify the terms governing the code.
The repository has 1 star, 1 fork, and 1 watcher, providing little evidence of a broad user or contributor base. Popularity is supporting evidence, but it reinforces the maintenance concern rather than deciding it alone.
The repository has no security policy, so there is no documented channel or process for reporting vulnerabilities. This is a transparency gap, though the small six-file package limits its significance.
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.