wasm-opt
1
Versions
—
License
Yes
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
mrrefactoring
Keywords
wasmwasm-opt
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| install-scripts | install-script:postinstall | AI (install-scripts): Postinstall fetches platform-specific wasm-opt binary — standard native-binary-wrapper pattern, stable for this package. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process used only to spawn the bundled wasm-opt binary with user CLI args; no arbitrary command execution. | ai | |
| semgrep | semgrep:child-process-spawn | AI (semgrep): Spawns the local wasm-opt binary with process.argv args; benign wrapper pattern. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 1.4.0 | 2 / 1 |
v1.4.0
2 findings
HIGH
Package has 'postinstall' script
install-scripts
Script: node bin/index.js
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.