prebuild
A command line tool for easily making prebuilt binaries for multiple versions of node, electron or node-webkit 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 | publisher-changed | AI (provenance): lovell is the maintainer of sharp, a primary consumer of prebuild, and a well-established npm publisher. The transition from ralphtheninja is a legitimate ecosystem handoff. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): lovell added as maintainer is consistent with their role as a major stakeholder in the native addon ecosystem; not a suspicious takeover. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): prebuild is a native addon build tool; spawning child processes (node-gyp, cmake-js, etc.) is its core documented function. | ai | |
| semgrep | semgrep:child-process-spawn | AI (semgrep): Same rationale — spawning build processes is the package's primary purpose. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): require(path.resolve('package.json')) is a standard pattern for reading the consuming project's metadata at build time; not a security risk. | ai | |
| phantom-deps | phantom-dep:cmake-js | AI (phantom-deps): cmake-js is a listed runtime dependency used as an optional build backend; referenced in config rather than directly imported is expected. | ai |
Versions (showing 100 of 117)
| Version | Deps | Published |
|---|---|---|
| 13.0.1 | 19 / 3 | |
| 13.0.0 | 19 / 3 | |
| 12.1.0 | 19 / 4 | |
| 12.0.0 | 19 / 4 | |
| 11.0.4 | 20 / 5 | |
| 11.0.3 | 20 / 5 | |
| 11.0.2 | 20 / 5 | |
| 11.0.1 | 20 / 5 | |
| 11.0.0 | 20 / 5 | |
| 10.0.1 | 20 / 5 | |
| 10.0.0 | 19 / 5 | |
| 9.1.1 | 19 / 5 | |
| 9.1.0 | 20 / 5 | |
| 9.0.1 | 19 / 5 | |
| 9.0.0 | 19 / 5 | |
| 8.2.1 | 19 / 5 | |
| 8.2.0 | 20 / 5 | |
| 8.1.2 | 19 / 5 | |
| 8.1.1 | 19 / 5 | |
| 8.1.0 | 20 / 5 | |
| 8.0.1 | 19 / 5 | |
| 8.0.0 | 19 / 5 | |
| 7.6.2 | 19 / 5 | |
| 7.6.1 | 19 / 5 | |
| 7.6.0 | 19 / 6 | |
| 7.5.0 | 19 / 6 | |
| 7.4.0 | 17 / 5 | |
| 7.3.0 | 17 / 5 | |
| 7.2.2 | 16 / 5 | |
| 7.2.1 | 16 / 5 | |
| 7.2.0 | 16 / 5 | |
| 7.1.0 | 15 / 5 | |
| 7.0.0 | 15 / 5 | |
| 6.2.2 | 15 / 5 | |
| 6.2.1 | 15 / 5 | |
| 6.2.0 | 14 / 5 | |
| 6.1.0 | 14 / 5 | |
| 6.0.2 | 14 / 5 | |
| 6.0.1 | 14 / 5 | |
| 6.0.0 | 14 / 5 | |
| 5.1.2 | 19 / 5 | |
| 5.1.1 | 19 / 5 | |
| 5.1.0 | 19 / 5 | |
| 5.0.3 | 19 / 5 | |
| 5.0.2 | 19 / 5 | |
| 5.0.1 | 19 / 5 | |
| 5.0.0 | 19 / 5 | |
| 4.5.0 | 18 / 5 | |
| 4.4.0 | 18 / 5 | |
| 4.3.1 | 18 / 5 | |
| 4.3.0 | 18 / 5 | |
| 4.2.2 | 17 / 5 | |
| 4.2.1 | 17 / 5 | |
| 4.2.0 | 17 / 5 | |
| 4.1.2 | 17 / 5 | |
| 4.1.1 | 17 / 5 | |
| 4.1.0 | 17 / 5 | |
| 4.0.2 | 17 / 5 | |
| 4.0.1 | 17 / 5 | |
| 4.0.0 | 17 / 5 | |
| 3.0.3 | 16 / 5 | |
| 3.0.2 | 16 / 5 | |
| 3.0.1 | 16 / 5 | |
| 3.0.0 | 16 / 6 | |
| 2.9.2 | 16 / 6 | |
| 2.9.1 | 16 / 6 | |
| 2.9.0 | 16 / 6 | |
| 2.8.1 | 14 / 5 | |
| 2.8.0 | 14 / 5 | |
| 2.7.2 | 14 / 5 | |
| 2.7.1 | 14 / 5 | |
| 2.7.0 | 14 / 5 | |
| 2.6.2 | 14 / 5 | |
| 2.6.1 | 14 / 5 | |
| 2.6.0 | 14 / 4 | |
| 2.5.5 | 14 / 3 | |
| 2.5.4 | 13 / 3 | |
| 2.5.3 | 13 / 3 | |
| 2.5.2 | 14 / 3 | |
| 2.5.1 | 14 / 3 | |
| 2.5.0 | 14 / 3 | |
| 2.4.0 | 14 / 3 | |
| 2.3.4 | 12 / 3 | |
| 2.3.3 | 12 / 3 | |
| 2.3.2 | 13 / 3 | |
| 2.3.1 | 11 / 1 | |
| 2.3.0 | 11 / 1 | |
| 2.2.10 | 11 / 0 | |
| 2.2.9 | 11 / 0 | |
| 2.2.8 | 11 / 0 | |
| 2.2.7 | 11 / 0 | |
| 2.2.6 | 11 / 0 | |
| 2.2.5 | 11 / 0 | |
| 2.2.4 | 11 / 0 | |
| 2.2.3 | 11 / 0 | |
| 2.2.2 | 11 / 0 | |
| 2.2.1 | 11 / 0 | |
| 2.2.0 | 11 / 0 | |
| 2.1.5 | 11 / 0 | |
| 2.1.4 | 11 / 0 |
v13.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.1.0
2 findingsThis version was published by a different npm account than previous versions on 2023-09-23. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.0.0
2 findingsThis version was published by a different npm account than previous versions on 2023-09-06. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.