prebuild-install
A command line tool to easily install prebuilt binaries for multiple version of node/iojs on a specific platform
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Package is 10+ years old with a strong publisher track record; lack of Sigstore provenance is expected for packages of this vintage. | ai | |
| dependencies | unvetted-dep:detect-libc | AI (dependencies): detect-libc is a standard build utility for native modules; stable dependency for this package. | ai | |
| dependencies | unvetted-dep:napi-build-utils | AI (dependencies): napi-build-utils is a standard NAPI build utility; stable dependency for this package. | ai | |
| dependencies | unvetted-dep:github-from-package | AI (dependencies): Minimal dependency (0.0.0) used to extract GitHub URLs from package.json; appropriate for this tool's purpose. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): The dynamic require loads the consuming project's package.json for metadata — a standard, benign pattern for a prebuild installer tool. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 7.1.3 | 12 / 7 | |
| 2.5.3 | 15 / 6 | |
| 2.5.2 | 15 / 6 | |
| 2.5.1 | 15 / 5 |
v2.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.