nice-napi
nice(2) bindings for Node.js
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:node-gyp-build | AI (dependencies): node-gyp-build is a well-known, widely-used utility for loading prebuilt native addons; its use here is entirely expected. | ai | |
| install-scripts | install-script:install | AI (install-scripts): node-gyp-build is the standard install script for native addons using prebuildify; stable and expected for this package. | ai | |
| npm-metadata | bundled-binaries | AI (npm-metadata): Bundled .node prebuilts for darwin-x64 and linux-x64 are the standard distribution mechanism for this native addon; no suspicious executables. | ai | |
| phantom-deps | phantom-dep:node-addon-api | AI (phantom-deps): node-addon-api is a C++ header-only dependency used at build time; not directly imported in JS but legitimately referenced in native addon build configs. | ai |
v1.0.2
3 findingsScript: node-gyp-build
Package contains compiled binaries that could be backdoors: • build/Release/obj.target/nice_napi.node • prebuilds/darwin-x64/node.napi.node • prebuilds/linux-x64/node.napi.node • build/Release/obj.target/nice_napi/binding.o • build/Release/obj.target/nothing/node_modules/node-addon-api/nothing.o
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.