js-sha3 MIT 20 versions

js-sha3

npm Repository Homepage

A simple SHA-3 / Keccak / Shake hash function for JavaScript supports UTF-8 encoding.

20

Versions

MIT

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

emn178

Keywords

sha3keccakshakecshakekmachashencryptioncryptographyHMAC

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	encoded-string-file:tests/test-shake.js	AI (source-diff): Long hex strings in test-shake.js are expected hash digest test vectors for SHAKE128/SHAKE256, not obfuscated payloads. Stable for this crypto hash library.	ai	2026/04/24

Versions (showing 20 of 20)

Version	Deps	Published
0.9.3	0 / 5	2023-12-16
0.9.2	0 / 5	2023-09-16
0.9.1	0 / 5	2023-08-31
0.9.0	0 / 5	2023-08-30
0.8.0	0 / 5	2018-08-05
0.7.0	0 / 5	2017-12-01
0.6.1	0 / 4	2017-07-03
0.6.0	0 / 4	2017-06-26
0.5.7	0 / 4	2016-12-30
0.5.6	0 / 3	2016-12-29
0.5.5	0 / 3	2016-09-26
0.5.4	0 / 3	2016-09-12
0.5.3	0 / 3	2016-09-08
0.5.2	0 / 3	2016-06-07
0.5.1	0 / 3	2015-10-27
0.4.1	0 / 3	2015-09-18
0.3.1	0 / 2	2015-05-22
0.2.0	0 / 2	2015-04-04
0.1.2	0 / 2	2015-02-27
0.1.0	0 / 2	2015-02-23

v0.9.2

1 finding

LOW No provenance attestation provenance

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

v0.9.1

1 finding

LOW No provenance attestation provenance

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

v0.9.0

1 finding

LOW No provenance attestation provenance

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

v0.7.0

1 finding

LOW No provenance attestation provenance

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

v0.6.1

1 finding

LOW No provenance attestation provenance

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

v0.6.0

2 findings

HIGH Long encoded string in modified file: tests/test-shake.js source-diff

Modified file contains 10 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.

v0.5.7

1 finding

LOW No provenance attestation provenance

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

v0.5.6

1 finding

LOW No provenance attestation provenance

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

v0.5.5

1 finding

LOW No provenance attestation provenance

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

v0.5.4

1 finding

LOW No provenance attestation provenance

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

v0.5.3

1 finding

LOW No provenance attestation provenance

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

v0.5.2

1 finding

LOW No provenance attestation provenance

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

v0.5.1

1 finding

LOW No provenance attestation provenance

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

v0.4.1

1 finding

LOW No provenance attestation provenance

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

v0.3.1

1 finding

LOW No provenance attestation provenance

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

v0.2.0

1 finding

LOW No provenance attestation provenance

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

v0.1.2

1 finding

LOW No provenance attestation provenance

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

v0.1.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.