@emscripten-forge/mambajs
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:comlink | AI (phantom-deps): Bundled build; comlink is a real runtime dep declared in package.json, heuristic false positive. | ai | |
| phantom-deps | phantom-dep:@baszalmstra/rattler | AI (phantom-deps): Bundled build; rattler is a real runtime dep declared in package.json, heuristic false positive. | ai | |
| source-diff | encoded-string-file:lib/index.js | AI (source-diff): Encoded string is a base64 WebAssembly binary loaded via _loadWasmModule; expected for this emscripten-forge WASM package. | ai | |
| phantom-deps | phantom-dep:@conda-org/rattler | AI (phantom-deps): First-party org dep declared in package.json; phantom detection is a false positive for this bundled package. | ai | |
| phantom-deps | phantom-dep:yaml | AI (phantom-deps): yaml is a declared runtime dep; phantom-dep heuristic false positive for this package. | ai | |
| license | uncommon-license:BSD-3-Clause license | AI (license): BSD-3-Clause is a well-known permissive license; trailing space in string causes false positive. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 0.21.4 | 3 / 5 | |
| 0.21.3 | 3 / 5 | |
| 0.17.0 | 3 / 5 | |
| 0.15.5 | 3 / 5 | |
| 0.13.1 | 3 / 5 | |
| 0.13.0 | 4 / 5 |
v0.21.4
2 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.21.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.