The release has no license information, and publishing depends on one registry account. A clear README and release notes help consumers, while the repository is not archived and matches the package.
55%
Total Score
50
83
100
Neither the package nor the linked repository provides a declared or detected license file. This is a transparency and adoption concern for a dependency.
Only one registry account has publishing access, leaving a thin release-publishing base. The linked repository is user-owned, so this is a real bus-factor concern rather than organization publishing hygiene.
There were no releases in the last 12 months, despite nine releases overall and a previously regular median interval of about 41 days. This indicates a meaningful slowdown in published maintenance.
The repository recorded zero commits and zero active maintainers during the last 3 months. That weakens evidence of ongoing maintenance, although the repository was pushed recently enough that abandonment is not certain.
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.