@loaders.gl/crypto
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | encoded-string-file:dist/crypto-worker.js | AI (source-diff): Minified esbuild worker bundle; benign build output stable across versions. | ai | |
| source-diff | encoded-string-file:dist/index.cjs | AI (source-diff): Base64-encoded WASM binary for MD5 hash algorithm; stable pattern across all versions of this crypto package. | ai | |
| source-diff | encoded-string-file:dist/dist.min.js | AI (source-diff): Minified bundle containing the same WASM base64 payload; expected build artifact for this package. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Node.js atob polyfill in MD5 WASM helper; not a payload decoder. Stable pattern for this package. | ai | |
| typosquat | typosquat.levenshtein:bcrypt | AI (typosquat): Legitimate scoped package in the visgl/loaders.gl ecosystem; not a typosquat of bcrypt. | ai | |
| phantom-deps | phantom-dep:@types/crypto-js | AI (phantom-deps): @types/crypto-js is a type declaration package; not directly imported but used for type checking, stable false positive. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 4.4.3 | 3 / 1 | |
| 4.4.2 | 3 / 1 | |
| 4.4.1 | 3 / 1 | |
| 4.4.0 | 3 / 1 | |
| 4.3.4 | 3 / 1 | |
| 4.3.3 | 3 / 1 | |
| 4.3.2 | 3 / 1 | |
| 4.3.1 | 3 / 1 | |
| 4.3.0 | 3 / 1 | |
| 4.2.5 | 3 / 1 | |
| 4.2.4 | 3 / 1 | |
| 4.2.3 | 3 / 1 | |
| 4.2.2 | 3 / 1 |
v4.3.3
2 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.2
2 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.1
2 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
3 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (dterekhova) than the most recent previously approved version (belom88) on 2024-10-16, but dterekhova is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v4.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.