hash-wasm
Lightning fast hash functions for browsers and Node.js using hand-tuned WebAssembly binaries (MD4, MD5, SHA-1, SHA-2, SHA-3, Keccak, BLAKE2, BLAKE3, PBKDF2, Argon2, bcrypt, scrypt, Adler-32, CRC32, CRC32C, RIPEMD-160, HMAC, xxHash, SM3, Whirlpool)
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/index.esm.js | AI (source-diff): Base64-encoded WASM hash modules, core to package function; stable FP. | ai | |
| source-diff | encoded-string-file:dist/index.umd.js | AI (source-diff): Base64-encoded WASM hash modules, core to package function; stable FP. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 4.12.0 | 0 / 17 | |
| 4.10.0 | 0 / 23 | |
| 4.9.0 | 0 / 26 | |
| 4.8.0 | 0 / 26 | |
| 4.7.0 | 0 / 26 | |
| 4.6.0 | 0 / 27 | |
| 4.5.0 | 0 / 27 | |
| 4.4.1 | 0 / 27 | |
| 4.4.0 | 0 / 26 | |
| 4.3.0 | 0 / 25 | |
| 4.2.2 | 0 / 23 | |
| 4.2.1 | 1 / 22 | |
| 4.2.0 | 1 / 22 | |
| 4.1.0 | 0 / 21 | |
| 4.0.1 | 0 / 21 | |
| 4.0.0 | 0 / 21 |
v4.10.0
20 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 21 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 21 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 21 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 21 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified 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.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.8.0
3 findingsModified file contains 21 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 21 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.7.0
3 findingsModified file contains 19 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 19 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.6.0
3 findingsModified file contains 18 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 18 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.5.0
3 findingsModified file contains 18 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 18 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.4.1
3 findingsModified file contains 17 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 17 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.4.0
3 findingsModified file contains 17 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 17 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 15 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 15 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.2.2
3 findingsModified file contains 14 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 14 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.2.1
3 findingsModified file contains 14 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 14 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.2.0
3 findingsModified file contains 14 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 14 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.1.0
3 findingsModified file contains 13 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 13 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.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.