The source is small and easy to inspect, and organizational backing provides some accountability. The README only says the project is still in development, while the license file needs clarification before adoption.
35%
Total Score
75
50
100
The manifest declares MIT, but the artifact license file and repository license are detected as GPL-3.0. This unresolved mismatch creates a material legal and dependency-adoption concern.
The package includes a README, but it is only 35 characters and says the project is still in development. Missing tests and changelog files are normal for published artifacts and are not concerns here.
The latest release was published in January 2017, with no releases in the last 12 months. This long period without releases is strong evidence of abandonment risk, despite the package having six historical releases.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the release history's prolonged inactivity. Organizational ownership does not compensate for the absence of observed maintenance.
The repository name does not match the package name and its README does not mention the package. Although name differences can occur in subpackages, this combination makes package-to-source provenance 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.