Its README, declarations, zero runtime dependencies, and exact release notes make integration straightforward. A single maintainer, no security policy, and unpinned workflow actions leave limited maintenance and build transparency.
64%
Total Score
50
100
89
63
50
No build attestation or trusted-publisher provenance is available, leaving publication origin less independently verifiable.
A prepack lifecycle script is present, adding build-time behavior that should be understood when reproducing the package, but it is not by itself a severe health concern.
Only one registry account has publish access, which creates a thin publishing base. The linked repository is directly owned by the same individual, so this is a modest resilience concern rather than a standalone severe risk.
The repository is owned by an individual rather than an organization, so there is no organizational backing to offset the thin maintainer base.
The package has 11 releases over more than 10 years, but none in nearly four years and none in the last 12 months. This indicates materially reduced 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.