@scandit/web-datacapture-barcode
Scandit Data Capture SDK for the Web
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:new-function-constructor | AI (semgrep): Emscripten WASM JS glue routinely uses new Function(); stable false positive for this package. | ai | |
| source-diff | net-exec-file:build/js/chunks/chunk-3AKV37VJ.js | AI (source-diff): Emscripten WASM loader pattern (Blob+Worker for .wasm files); stable false positive for this SDK package. | ai | |
| source-diff | net-exec-file:build/js/chunks/chunk-BE6R6FCS.js | AI (source-diff): Blob URL + WASM fetch is Scandit's documented worker-loading pattern; not malicious. | ai | |
| source-diff | net-exec-file:build/js/chunks/chunk-ELW7RLZN.js | AI (source-diff): WASM worker loader using Blob URL — standard pattern for WebAssembly SDKs, not dropper malware. | ai | |
| source-diff | net-exec-file:build/js/chunks/chunk-KQ3LRAYO.js | AI (source-diff): Code is a purity-checker sandbox that blocks network/eval globals in user functions — not a dropper. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scandit multi-module SDK; templated naming and minimal README are expected patterns for this commercial package family. | ai | |
| phantom-deps | phantom-dep:@types/emscripten | AI (phantom-deps): WebAssembly SDK; @types/emscripten is a type-only dep used by convention for WASM interop, not directly imported. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 8.4.0 | 1 / 0 | |
| 8.3.1 | 1 / 0 | |
| 8.1.4 | 1 / 0 | |
| 7.6.14 | 1 / 0 | |
| 7.6.13 | 1 / 0 | |
| 7.6.12 | 1 / 0 | |
| 7.6.11 | 1 / 0 | |
| 7.6.10 | 1 / 0 |
v8.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.4
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.14
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.13
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.12
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.11
3 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.