The repository is small, has no security policy, and does not clearly identify this package in its README. Its MIT license, stable versioning, and lack of install-time scripts provide useful safeguards, but the project has limited transparency.
38%
Total Score
25
69
75
The latest release was over eight years ago, with no releases in the last 12 months. That long silence outweighs the earlier four-release history and is strong evidence of abandonment risk.
There were zero commits and zero active maintainers in the last three months. Combined with the old last push, this is direct evidence that the code is not being maintained.
There were no new or closed issues or pull requests in the last month, while one issue and one pull request remain open. This suggests little active support for users or pending contributions.
The repository name does not match the package name, and no README mention was available to establish the connection. This makes package ownership less transparent, although a subpackage or naming convention could explain the mismatch.
The repository has only 4 stars and 5 forks, indicating a small user and contributor community. Popularity is supporting evidence rather than decisive proof, but this offers little resilience if maintenance stops.
We didn't find any vulnerabilities for this package.
No maintainer information available.
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.