It has a clear MIT license, a README, release notes, and only one runtime dependency. Those strengths do not offset the absence of maintenance since 2016 or the repository's failure to identify this package clearly.
38%
Total Score
0
100
75
75
The latest release was in April 2016, with no releases in the last 12 months and only two releases overall. This is strong evidence of abandonment risk, although the package is not deprecated.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the release history showing no activity since 2016. No stronger maintenance signal compensates for this.
The repository name does not match the package name and its README does not mention the package, so the source-to-package relationship is not transparent. The matching owner namespace provides context but does not resolve that gap.
The repository has no security policy and no security-scanning tools. This is a transparency and response-readiness gap, though the project’s long inactivity is the larger concern.
We didn't find any vulnerabilities for this package.
No maintainer information available.
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.