The release is clearly licensed, documented, and tied to a matching organization repository. Its small scope and lack of security tooling provide limited evidence of ongoing oversight, so future compatibility work may be difficult.
55%
Total Score
75
83
75
Only two releases exist, with the latest published over nine years ago and no releases in the last 12 months. This strongly lowers confidence in ongoing maintenance, though the package is not marked deprecated.
The repository recorded no commits or active maintainers in the last three months, consistent with a largely inactive project. This is a meaningful maintenance concern but not proof of abandonment on its own.
The repository has no security policy, leaving no documented route for reporting vulnerabilities. This is a modest transparency gap for a dependency, although the package has no other supplied evidence of active security handling.
Version 0.1.1 is not a prerelease, but the package remains below a stable major version and has had only two releases. This suggests limited maturity for a dependency with long-term compatibility expectations.
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.