← Home

@loaders.gl/crypto

npm Repository
4
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

pessimistresskylebarronibgreendryabininbelom88dterekhovaopenjs-operationsfelixpalmer

Keywords

cryptohashdigestencryptdecryptcrc32crc32cmd5sha256

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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 4 of 4)

Version Deps Published
4.4.2 3 / 1
4.4.1 3 / 1
4.4.0 3 / 1
4.3.4 3 / 1

v4.4.2

3 findings
HIGH Long encoded string in modified file: dist/index.cjs source-diff

Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

HIGH Long encoded string in modified file: dist/dist.min.js source-diff

Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.4.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v4.4.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v4.3.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.