The project is tiny, with no security tooling and almost no community activity. Its MIT declaration and direct repository match add transparency, but do not offset the long maintenance gap.
34%
Total Score
25
67
83
The last release was in June 2016, and there were no releases in the following 12 months of the observed history. That long gap is strong evidence of abandonment risk.
The repository recorded zero commits and zero active maintainers during the last three months of the assessment window, consistent with the extended release gap.
There was one open issue but no new or closed issues and no pull-request activity in the last month, providing no evidence of active support.
The repository has zero stars and forks and only one watcher. Popularity is not decisive, but these figures provide little supporting evidence of adoption or community oversight.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This is a transparency gap, though it does not by itself show unsafe code.
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.