@alwatr/hash-string
A simple utility to generate a hash string.
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
Versions (showing 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 9.25.0 | 0 / 4 | |
| 9.16.0 | 0 / 4 | |
| 9.14.0 | 0 / 4 | |
| 9.11.2 | 0 / 4 | |
| 9.10.1 | 0 / 4 | |
| 9.10.0 | 0 / 4 | |
| 9.7.0 | 0 / 4 | |
| 9.4.5 | 0 / 4 | |
| 9.4.0 | 0 / 4 | |
| 9.3.0 | 0 / 4 | |
| 9.1.1 | 0 / 4 | |
| 9.1.0 | 0 / 4 | |
| 6.0.2 | 0 / 4 | |
| 6.0.1 | 0 / 4 | |
| 6.0.0 | 0 / 4 | |
| 5.2.30 | 0 / 4 | |
| 5.2.29 | 0 / 4 | |
| 5.2.28 | 0 / 5 | |
| 5.2.27 | 0 / 5 | |
| 5.2.26 | 0 / 5 | |
| 5.2.25 | 0 / 5 | |
| 5.2.24 | 0 / 5 | |
| 5.2.23 | 0 / 5 | |
| 5.2.22 | 0 / 5 | |
| 5.2.21 | 0 / 5 | |
| 5.2.20 | 0 / 5 |
v9.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.11.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.