zxing-wasm
ZXing-C++ WebAssembly as an ES/CJS module with types
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/miniprogram/index.js | AI (source-diff): Bundled dist output for miniprogram target; barcode format tables, no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/cjs/share.js | AI (source-diff): Standard CJS bundle output; no suspicious code in sample. | ai | |
| provenance | publisher-changed | AI (provenance): Moved from manual publish (sec-ant) to GitHub Actions CI/CD; same repo owner. | ai | |
| provenance | missing-githead | AI (provenance): GitHub Actions publish flow doesn't set gitHead; SLSA provenance compensates. | ai | |
| dependencies | unvetted-dep:@types/emscripten | AI (dependencies): @types/emscripten is the standard TypeScript types package for Emscripten; expected and benign for a WASM project compiled with Emscripten. | ai | |
| phantom-deps | phantom-dep:@types/emscripten | AI (phantom-deps): @types/emscripten augments global types rather than being directly imported; this pattern is standard for Emscripten WASM modules. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 3.1.0 | 2 / 21 | |
| 3.0.3 | 2 / 20 | |
| 3.0.2 | 2 / 20 | |
| 3.0.1 | 2 / 24 | |
| 3.0.0 | 2 / 24 | |
| 2.2.4 | 2 / 24 | |
| 2.2.3 | 2 / 24 | |
| 1.1.3 | 1 / 13 |
v3.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.1
5 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
This version was published by a different npm account than previous versions on 2026-03-09. This could indicate a legitimate maintainer transition or an account compromise.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.0
5 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
This version was published by a different npm account than previous versions on 2026-02-24. This could indicate a legitimate maintainer transition or an account compromise.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.2.4
5 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
This version was published by a different npm account than previous versions on 2025-11-18. This could indicate a legitimate maintainer transition or an account compromise.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.2.3
5 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
This version was published by a different npm account than previous versions on 2025-11-08. This could indicate a legitimate maintainer transition or an account compromise.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.