The beta release has a minimal footprint, no tests, and no security policy; its license declaration also differs from the detected license. The repository matches the package and includes a usable README, but there is little evidence of ongoing project activity.
36%
Total Score
50
63
75
This is the only release, published about 11 years ago, with no releases in the last 12 months. That is strong evidence of abandonment risk for a dependency.
A BSD 3-Clause license is declared and a license file is present, but the artifact file was detected as BSD-2-Clause. The mismatch creates a transparency concern despite the package being licensed.
The repository is owned by the same individual namespace as the package, providing direct ownership context. It is individual-backed rather than organization-backed, so maintenance capacity remains limited.
There are no open issues or pull requests and no recent activity. While a clean issue tracker can be benign, the lack of activity is consistent with the long release gap.
The repository has only 2 stars and 3 forks. Popularity is supporting evidence rather than a verdict, but these small numbers provide little evidence of broad adoption or community support.
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.