The artifact is small, readable, and has no install-time scripts, limiting integration and installation concerns. Its license files and registry declaration disagree, while the project shows no visible maintenance for years and may not clearly correspond to the package.
40%
Total Score
50
70
50
The package declares OSL-3.0 and AFL-3.0, but the detected LICENSE file is MIT. A license is present, yet the mismatch creates avoidable legal uncertainty.
This is the only release, published about five years ago, with no releases in the last 12 months. That leaves meaningful abandonment risk despite the stable 1.0.0 version.
There were no commits or active maintainers in the last three months, consistent with a project that has been inactive since July 2021. This materially raises maintenance and abandonment risk.
The repository name does not match the package name and its README does not mention the package. Although this can occur with subpackages, the absence of either link makes package ownership less transparent.
The repository has no security policy. This is a modest transparency gap for a dependency, but the package's small size and lack of other workflow findings limit 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.