@jitl/quickjs-wasmfile-release-sync
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
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): WASM is the package's core build artifact; stable across versions of this quickjs variant. | ai | |
| provenance | no-provenance | AI (provenance): Established package from a known author with a clean track record; lack of provenance attestation is common and not a risk signal here. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 0.32.0 | 1 / 0 | |
| 0.31.0 | 1 / 0 | |
| 0.30.0 | 1 / 0 | |
| 0.29.2 | 1 / 0 | |
| 0.29.1 | 1 / 0 | |
| 0.29.0 | 1 / 0 | |
| 0.28.0 | 1 / 0 | |
| 0.27.0 | 1 / 0 | |
| 0.26.0 | 1 / 0 | |
| 0.25.1 | 1 / 0 | |
| 0.25.0 | 1 / 0 |
v0.31.0
2 findingsPackage contains compiled binaries that could be backdoors: • dist/emscripten-module.wasm
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.30.0
2 findingsPackage contains compiled binaries that could be backdoors: • dist/emscripten-module.wasm
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.29.2
2 findingsPackage contains compiled binaries that could be backdoors: • dist/emscripten-module.wasm
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.29.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.