The license file and package-to-repository match improve traceability, but the project offers little safety tooling or written guidance. Its organization ownership is a modest positive, not evidence of ongoing maintenance.
38%
Total Score
50
50
50
The package has only one release, published about 10 years ago, with no releases in the last 12 months. That strongly suggests the dependency is no longer actively maintained.
The repository recorded zero commits and zero active maintainers in the last 3 months, providing no evidence of current maintenance capacity.
The artifact includes an MIT license file, but the manifest declares the package as Private. This mismatch creates avoidable licensing uncertainty despite the detected license text.
A README is present, but it is only 44 characters and provides almost no integration guidance. The absence of tests and a changelog is normal for a published package artifact and is not counted against it.
The repository is not marked archived, which avoids the strongest abandonment signal, but its last push was about 10 years ago and does not offset the stale release and commit history.
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.