hashery
Browser Compatible Object Hashing
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Legitimate transition from manual publish to GitHub Actions CI/CD with SLSA provenance. | ai | |
| provenance | missing-githead | AI (provenance): Expected when publishing via GitHub Actions; SLSA provenance compensates. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 3.0.1 | 1 / 15 | |
| 3.0.0 | 1 / 15 | |
| 2.0.0 | 1 / 15 | |
| 1.5.1 | 1 / 14 | |
| 1.5.0 | 1 / 14 | |
| 1.4.0 | 1 / 12 | |
| 1.3.0 | 1 / 12 |
v3.0.1
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
v3.0.0
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
This version was published by a different npm account than previous versions on 2026-06-10. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.