Only one registry maintainer and no README mention of the package reduce confidence in ongoing ownership. The package has no security policy, although it is licensed and not deprecated.
43%
Total Score
50
86
75
One registry maintainer provides a thin publishing base for a user-owned project. The linked repository and release history provide some ownership evidence, but not enough to offset the maintenance concern.
This is the only release, published about 2 years and 7 months ago, with no releases in the last 12 months. That leaves little evidence of continued maintenance.
The repository recorded no commits and no active maintainers in the last 3 months, consistent with the long release gap and raising abandonment risk.
The repository name matches the package, but its README does not mention the package. That weakens transparency about whether the repository is the intended source.
No repository security policy was found, leaving vulnerability-reporting and maintenance expectations undocumented. This is a transparency gap rather than evidence of malicious behavior.
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.