esbuild-linux-ppc64le
The Linux PowerPC 64-bit Little Endian binary for esbuild, a JavaScript bundler.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | bundled-binaries | AI (npm-metadata): esbuild-linux-ppc64le is a platform binary package whose sole purpose is shipping the esbuild executable for Linux ppc64le. Bundled binary is expected and intentional. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Platform-specific binary packages structurally lack deps, keywords, and detailed READMEs. These signals are false positives for this package type. | ai |
Versions (showing 11 of 311)
| Version | Deps | Published |
|---|---|---|
| 0.4.12 | 0 / 0 | |
| 0.4.11 | 0 / 0 | |
| 0.4.10 | 0 / 0 | |
| 0.4.9 | 0 / 0 | |
| 0.4.8 | 0 / 0 | |
| 0.4.7 | 0 / 0 | |
| 0.4.6 | 0 / 0 | |
| 0.4.5 | 0 / 0 | |
| 0.4.4 | 0 / 0 | |
| 0.4.3 | 0 / 0 | |
| 0.0.1 | 0 / 0 |
v0.4.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.