wasm-sjlj
setjmp/longjmp implementation from Emscripten
Supply chain provenance
Status for the latest visible version.
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): Established publisher with 191 approved packages; lack of Sigstore provenance is common and not a meaningful risk signal here. | ai | |
| install-scripts | install-script:install | AI (install-scripts): node-gyp rebuild is the standard build step for this native/WASM binding package; stable and expected across all versions given the .gyp build file and C sources. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 1.0.6 | 0 / 0 | |
| 1.0.4 | 0 / 0 | |
| 1.0.3 | 0 / 0 | |
| 1.0.1 | 0 / 0 | |
| 1.0.0 | 0 / 0 |
v1.0.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.4
2 findingsScript: node-gyp rebuild
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.3
2 findingsScript: node-gyp rebuild
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.1
2 findingsScript: node-gyp rebuild
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
2 findingsScript: node-gyp rebuild
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.