The package has a clear README, matching repository, MIT license, no install-time scripts, and no runtime dependencies. It has no tests or security policy, leaving long-term maintenance and review largely dependent on one inactive maintainer.
43%
Total Score
33
100
80
75
Only two releases were published, with the latest nearly six years ago and none in the last 12 months. This strongly indicates abandonment risk despite the package not being formally deprecated.
The repository had no commits and no active maintainers in the last three months, consistent with the long release gap. This is the strongest maintenance concern for a dependency.
One registry maintainer is consistent with a small personal project, but it leaves limited visible publishing capacity when combined with the lack of recent activity.
The repository is owned by an individual rather than an organization, so the single registry maintainer is not offset by visible organizational backing. This reinforces the limited maintenance capacity.
The repository has no security policy. This is a transparency and maintenance gap, though it is less severe than the absence of recent release or commit activity.
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.