napi-rs
1
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
broooooklyn
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:child-process-import | AI (semgrep): Build/CLI tool legitimately spawns compilers; stable pattern for this package. | ai | |
| semgrep | semgrep:child-process-spawn | AI (semgrep): Spawn used for build commands in documented CLI workflow; not malicious. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Requires user-supplied package.json path to read napi config; expected pattern for this tool. | ai | |
| phantom-deps | phantom-dep:inquirer | AI (phantom-deps): inquirer is listed in dependencies and used for interactive CLI prompts; phantom-dep is a false positive here. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 0.3.10 | 10 / 24 |
v0.3.10
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.