The matching repository and stable 1.0.0 release provide a clear, usable baseline. Documentation is minimal, and the project has had no commits or releases for nearly four years; it also lacks a license and security policy.
45%
Total Score
0
71
75
The package has only one release, published nearly four years ago, with no releases in the last 12 months. That is strong evidence of abandonment risk for a dependency.
The repository recorded no commits and no active maintainers in the last three months, consistent with the long release gap and leaving little evidence of ongoing maintenance.
No declared license, license file, or repository license file was detected. This creates a real adoption and redistribution risk for an open-source dependency.
The package includes a GitHub release and a README, but the README is only 15 characters and provides almost no consumer guidance. The absence of tests and a changelog is normal for published artifacts and is not penalized.
The repository has no security policy, so there is no documented channel or process for reporting vulnerabilities. The small project footprint limits how severe this gap is, but it still reduces transparency.
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.