The release has an MIT declaration but its license file is detected as Apache-2.0, creating a compatibility question. It includes a README and release notes, but the single maintainer and lack of security scanning add little reassurance.
38%
Total Score
50
67
50
The manifest declares MIT while the artifact license file is detected as Apache-2.0. Although a license file is present, the mismatch requires compatibility and provenance review before adoption.
The package has one registry maintainer, which leaves a thin publishing base. The linked repository is user-owned rather than organization-backed, so there is no provided evidence of broader maintenance capacity.
Only two releases were published, and the latest was about five years ago; there is no release activity in the last 12 months. This is strong evidence of abandonment risk for a package intended as a dependency.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap. The repository is not archived, but there is no recent activity to offset the concern.
The linked repository has no security policy, reducing transparency for reporting and handling issues. This is a secondary concern beside the much older maintenance activity.
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.