Documentation, tests, licensing, and a tiny dependency surface support adoption. The single maintainer and repository/package mismatch add uncertainty, while the project shows little recent activity.
42%
Total Score
0
100
50
75
The latest release was nearly nine years ago, with no releases in the last 12 months. Six releases over the package's lifetime show some history, but the long release gap raises abandonment risk.
The repository recorded zero commits and zero active maintainers during the last three months. This is consistent with the long release gap and provides little evidence of current maintenance.
The artifact contains a recognized GPL-2.0 license file, but it does not clearly cover the declared GPL-2.0+ and MIT combination. That mismatch warrants caution for downstream licensing decisions.
The repository name does not match the package name and its README does not mention the package, weakening confidence that the linked source clearly represents this release.
The repository has no security policy. For an old package with no recent commit activity, this leaves vulnerability-reporting and maintenance expectations unclear.
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.