jssha
jsSHA implements the complete Secure Hash Standard (SHA) family (SHA-1, SHA-224/256/384/512, SHA3-224/256/384/512, SHAKE128/256, cSHAKE128/256, and KMAC128/256) with HMAC
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/sha1.mjs | AI (source-diff): Minified ESM build artifact produced by rollup+terser; contains BSD copyright header and SHA hash logic. Standard dist output for this crypto library. | ai | |
| source-diff | obfuscated-file:dist/sha256.mjs | AI (source-diff): Minified ESM build artifact produced by rollup+terser; contains BSD copyright header and SHA hash logic. Standard dist output for this crypto library. | ai | |
| source-diff | obfuscated-file:dist/sha3.mjs | AI (source-diff): Minified ESM build artifact produced by rollup+terser; contains BSD copyright header and SHA hash logic. Standard dist output for this crypto library. | ai | |
| source-diff | obfuscated-file:dist/sha512.mjs | AI (source-diff): Minified ESM build artifact produced by rollup+terser; contains BSD copyright header and SHA hash logic. Standard dist output for this crypto library. | ai | |
| source-diff | obfuscated-file:dist/sha512.js | AI (source-diff): dist/sha512.js is a standard rollup+terser minified build artifact for the jsSHA library. Minified dist files are expected and intentional for this package. | ai | |
| source-diff | obfuscated-file:dist/sha.js | AI (source-diff): dist/sha.js is a standard rollup+terser minified build artifact for the jsSHA library. Minified dist files are expected and intentional for this package. | ai | |
| source-diff | obfuscated-file:dist/sha.mjs | AI (source-diff): dist/sha.mjs is a standard rollup+terser minified ESM build artifact for the jsSHA library. Minified dist files are expected and intentional for this package. | ai | |
| source-diff | obfuscated-file:dist/sha1.js | AI (source-diff): dist/sha1.js is a standard rollup+terser minified build artifact for the jsSHA library. Minified dist files are expected and intentional for this package. | ai | |
| source-diff | obfuscated-file:dist/sha256.js | AI (source-diff): dist/sha256.js is a standard rollup+terser minified build artifact for the jsSHA library. Minified dist files are expected and intentional for this package. | ai | |
| source-diff | obfuscated-file:dist/sha3.js | AI (source-diff): dist/sha3.js is a standard rollup+terser minified build artifact for the jsSHA library. Minified dist files are expected and intentional for this package. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 3.3.1 | 0 / 28 | |
| 3.3.0 | 0 / 28 | |
| 3.2.0 | 0 / 28 | |
| 3.1.2 | 0 / 28 | |
| 3.1.1 | 0 / 28 | |
| 3.1.0 | 0 / 28 | |
| 3.0.0 | 0 / 28 | |
| 2.4.2 | 0 / 2 | |
| 2.4.1 | 0 / 2 | |
| 2.4.0 | 0 / 2 | |
| 2.3.1 | 0 / 2 | |
| 2.3.0 | 0 / 2 | |
| 2.2.0 | 0 / 2 | |
| 2.1.0 | 0 / 0 | |
| 2.0.2 | 0 / 0 | |
| 2.0.1 | 0 / 0 | |
| 2.0.0 | 0 / 0 |
v3.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.
v3.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
7 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.
v2.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.