Simple help and sanity checks for Node CLI bin scripts
64%
Total Score
50
100
90
75
50
No build attestation or trusted-publisher provenance is available, leaving release origin less transparent. This is a transparency weakness, not evidence that the release is unsafe.
Only one registry account has publish access, creating a thin publishing base. The matching repository owner and observed repository activity provide some compensation.
The repository is owned by an individual rather than an organization, so there is no visible organizational backing to broaden maintenance capacity.
The package has 15 releases since 2015, but none in the last three years, which raises maintenance concerns. The linked repository remains unarchived and has recent pull-request activity, partly offsetting the gap.
There were no commits and no active maintainers during the last three months, consistent with the old registry release and suggesting slowed maintenance.
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.