It has a matching source repository, a clear MIT license, and no install-time scripts. Its small codebase, lack of tests and security tooling, and minimal documentation provide little evidence of ongoing care.
38%
Total Score
25
100
69
83
The last release was in September 2015, and there have been no releases in more than 11 years. Four releases over roughly three weeks show an initial burst but no continuing maintenance.
The repository has recorded no commits and no active maintainers in the last three months, consistent with the last push being in September 2015. This is strong evidence of abandonment risk.
A README is present and the absence of tests or a changelog in the published artifact is normal packaging practice. However, the README is only 48 characters and the repository also has no tests or changelog, limiting transparency.
The repository is owned by a personal user account rather than an organization, so the single registry maintainer is not explained by organization-backed publishing. Combined with inactivity, this leaves a thin maintenance base.
The repository has zero stars and forks and one watcher, providing no meaningful community support signal. Low popularity alone is not decisive, but it offers no compensation for the long maintenance gap.
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.