MIT licensing and a single runtime dependency make the package straightforward to evaluate. Its tiny documentation, absent tests, and lack of a security policy provide little maintenance evidence, while the repository has seen no release activity for over six years.
48%
Total Score
100
71
75
The artifact has a README, and release notes say “Bugs fixed,” but the README is only 17 characters and neither the package nor repository has tests. The missing tests are normal packaging practice, while the minimal consumer documentation limits transparency.
Only two releases exist, with the latest published over six years ago and none in the last 12 months. This is meaningful abandonment risk for a package intended as a library.
The repository has zero stars and forks and one watcher. Popularity is only supporting evidence, but these counts provide no meaningful community or adoption signal to offset the stale release history.
The linked repository has no security policy. This is a transparency and maintenance gap, though it is not evidence that the package is unsafe by itself.
The assessed release is still v0.1.1 rather than a stable major release, which indicates limited maturity. It is not marked as a prerelease, so this is a caution rather than a severe release-quality concern.
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.