The MIT license and matching source repository make the package easy to inspect and reuse. Its single maintainer, minimal popularity, and absent security policy provide little resilience for a dependency this old.
38%
Total Score
33
75
88
The last release was about 10 years ago, with no releases in the past 12 months. Seven releases show an established history, but the long current gap strongly raises abandonment risk.
The repository has had zero commits and zero active maintainers in the past 3 months, while its last push was in September 2016. The repository is not archived, but that does not offset the prolonged inactivity.
Only one registry account has publish access, which is a limited operational base. The organization-owned repository provides some backing, so this is a resilience concern rather than a severe standalone risk.
There has been no issue or pull-request activity in the past month, and no open issues or pull requests remain. Combined with the old last push, this supports inactivity rather than active stability.
The repository has 1 star and 2 forks, offering little community evidence or likely backup capacity. Low popularity is supporting evidence only and does not by itself make the package unsafe.
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.