sax-wasm
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
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): lib/sax-wasm.wasm is the package's core compiled Rust artifact; stable across versions. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 3.1.4 | 0 / 16 | |
| 3.1.3 | 0 / 17 | |
| 3.1.2 | 0 / 17 | |
| 3.1.1 | 0 / 17 | |
| 3.1.0 | 0 / 17 | |
| 3.0.12 | 0 / 17 | |
| 3.0.11 | 0 / 17 | |
| 3.0.10 | 0 / 17 | |
| 3.0.9 | 0 / 17 | |
| 3.0.8 | 0 / 17 | |
| 3.0.7 | 0 / 17 | |
| 3.0.6 | 0 / 17 | |
| 3.0.5 | 0 / 17 | |
| 3.0.4 | 0 / 17 | |
| 3.0.3 | 0 / 17 | |
| 3.0.2 | 0 / 17 | |
| 3.0.1 | 0 / 17 | |
| 3.0.0 | 0 / 17 |
v3.0.6
2 findingsPackage contains compiled binaries that could be backdoors: • lib/sax-wasm.wasm
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.5
2 findingsPackage contains compiled binaries that could be backdoors: • lib/sax-wasm.wasm
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.4
2 findingsPackage contains compiled binaries that could be backdoors: • lib/sax-wasm.wasm
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.3
2 findingsPackage contains compiled binaries that could be backdoors: • lib/sax-wasm.wasm
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.2
2 findingsPackage contains compiled binaries that could be backdoors: • lib/sax-wasm.wasm
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.1
2 findingsPackage contains compiled binaries that could be backdoors: • lib/sax-wasm.wasm
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
2 findingsPackage contains compiled binaries that could be backdoors: • lib/sax-wasm.wasm
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.