sha1
native js function for hashing messages with SHA-1
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 |
|---|---|---|---|---|
| npm-metadata | suspicious-initial-version | AI (npm-metadata): [email protected] is a 14+ year old legitimate package; version 0.0.0 reflects early npm conventions, not malicious intent. This heuristic is a stable false positive for this package. | ai | |
| dependencies | unvetted-dep:crypt | AI (dependencies): crypt is a companion package by the same author (pvorb) and is a stable, expected dependency for this SHA-1 implementation. Generalizes across versions. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Publisher has strong track record (36 approved, 0 rejected). Version diff shows no material changes, making account takeover unlikely. Dormancy is consistent with low-maintenance utility package. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 1.1.1 | 2 / 1 | |
| 1.1.0 | 2 / 1 | |
| 1.0.1 | 2 / 1 | |
| 1.0.0 | 2 / 1 | |
| 0.0.1 | 2 / 0 | |
| 0.0.0 | 2 / 0 |
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.