@aws-crypto/sha256-js
A pure JS implementation SHA256.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@aws-crypto/util | AI (dependencies): @aws-crypto/util is a sibling package in the same AWS crypto helpers monorepo, published by the same trusted aws-crypto-tools-ci-bot publisher. This internal dependency is stable and expected across all versions. | ai | |
| source-diff | encoded-string-file:build/knownHashes.fixture.js | AI (source-diff): Long hex strings in knownHashes.fixture.js are standard SHA-256/HMAC test vectors from RFC 4231 and NIST — expected content for a cryptographic hash implementation package. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher change from lavaleri to salkeldr reflects a documented AWS internal maintainer transition; salkeldr has a clean 39-approved/0-rejected track record and the package content is unchanged. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainer salkeldr is an established AWS publisher with a clean track record; consistent with legitimate AWS team rotation for this package. | ai | |
| provenance | no-provenance | AI (provenance): Already marked accepted risk; AWS crypto tools CI bot publishing without Sigstore provenance is consistent with their established publishing pipeline. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 5.2.0 | 3 / 0 | |
| 5.1.0 | 3 / 0 | |
| 5.0.0 | 3 / 0 | |
| 4.0.0 | 3 / 0 | |
| 3.0.0 | 3 / 0 | |
| 2.0.2 | 3 / 0 | |
| 2.0.1 | 3 / 0 | |
| 2.0.0 | 3 / 0 | |
| 1.2.2 | 3 / 0 | |
| 1.2.1 | 3 / 0 | |
| 1.2.0 | 3 / 0 | |
| 1.1.0 | 3 / 0 | |
| 1.0.0 | 3 / 0 | |
| 0.1.0 | 3 / 10 |
v2.0.2
2 findingsModified file contains 4 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
3 findingsThis version was published by a different npm account than previous versions on 2021-09-17. This could indicate a legitimate maintainer transition or an account compromise.
Modified file contains 4 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
2 findingsThis version was published by a different npm account than previous versions on 2021-01-13. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.