The license declaration conflicts with the license file, and the project has no security policy. Its small, focused scope and clear README reduce adoption friction, but do not offset the stale maintenance picture.
43%
Total Score
0
70
50
The latest release was nearly six years ago, with no releases in the last 12 months. That is a substantial abandonment concern despite the package having a stable release history before then.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and leaving little evidence of ongoing maintenance.
The package declares GPL-2.0-or-later, while the artifact license file was detected as GPL-3.0. Both indicate licensing exists, but the mismatch creates avoidable legal ambiguity.
The repository has no security policy or documented reporting path. This is a transparency and maintenance gap, although the package's narrow scope limits its weight.
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.