Cli tools for napi-rs
88%
Total Score
healthy
Frequent releases, active contributors, and verified publishing outweigh workflow pinning gaps.
The repository name does not match the package and its README does not mention @napi-rs/cli. This can be normal for a monorepo subpackage, but the lack of an explicit README mention leaves a small identity-transparency gap.
The project uses TypeScript, npm scripts, and esbuild, and has a SECURITY.md policy. No security scanning tools were detected, which is a minor hygiene gap but not decisive given the other evidence.
All 7 workflows were analyzed with no untrusted checkouts or script injection; however, 132 of 135 action uses are unpinned, and a high-confidence low-severity finding reports an ad hoc package install. One workflow has top-level write permissions, but no dangerous trigger was found.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
obug Version ^3.0.0 | — | — |
semver Version ^7.8.2 | — | — |
js-yaml Version ^5.0.0 | — | — |
typanion Version ^3.14.0 | — | — |
clipanion Version ^4.0.0-rc.4 | — | — |
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.