MIT licensing and a usable README make the package straightforward to evaluate and integrate. Its single-user ownership, absent security policy, and negligible repository adoption leave little evidence of resilience if maintenance is needed.
39%
Total Score
25
79
75
The package has made no releases in the last 12 months, and its latest release was in February 2022. This long publishing gap is strong evidence of abandonment risk, despite the three-release history.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the last push occurring in February 2022. No provided activity signal compensates for this prolonged inactivity.
Only one registry maintainer is listed, leaving a thin publishing base and increasing continuity risk. The repository is also owned by an individual rather than an organization.
The repository has zero stars and forks and only one watcher. Popularity is supporting evidence rather than a verdict, but these counts provide little evidence of an active user or contributor community.
The repository has no security policy, reducing transparency for reporting and handling vulnerabilities. This is a meaningful hygiene gap, though it is less severe than the maintenance inactivity.
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.