@scandit/web-datacapture-label
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-generated WASM JS glue; new Function() is standard in this build output across all Scandit SDK versions. | ai | |
| source-diff | large-new-source-files | AI (source-diff): New files are ML model assets and WASM bundles expected for label-capture feature additions. | ai | |
| source-diff | obfuscated-file:build/js/NativeProxy-B98bIlIp.d.ts | AI (source-diff): Long lines are TypeScript declaration union-type imports, not obfuscated code; stable pattern for Scandit SDK packages. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scandit commercial SDK suite; templated naming and minimal README are expected patterns across their package family. | ai | |
| phantom-deps | phantom-dep:@types/emscripten | AI (phantom-deps): @types/emscripten is a type-only dependency for WebAssembly bindings; not directly imported at runtime by convention. | 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 source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.11
1 findingPackage 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.