hash-it
Hash any object based on its value
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/min/index.js | AI (source-diff): dist/min/index.js is a standard rollup+terser minified UMD build artifact for hash-it. Content is readable minified JS with no malicious patterns. Stable false positive for this package. | ai | |
| source-diff | large-new-source-files | AI (source-diff): v6 restructured build output into multiple dist subdirectories (cjs/esm/umd/min). New file count reflects legitimate build system overhaul, not injected code. | ai |
Versions (showing 32 of 32)
| Version | Deps | Published |
|---|---|---|
| 7.0.2 | 0 / 22 | |
| 7.0.1 | 0 / 25 | |
| 7.0.0 | 0 / 25 | |
| 6.0.1 | 0 / 36 | |
| 6.0.0 | 0 / 37 | |
| 5.0.2 | 0 / 39 | |
| 5.0.1 | 0 / 39 | |
| 5.0.0 | 0 / 39 | |
| 4.1.0 | 1 / 37 | |
| 4.0.5 | 1 / 38 | |
| 4.0.4 | 3 / 38 | |
| 4.0.3 | 3 / 38 | |
| 4.0.2 | 3 / 38 | |
| 4.0.1 | 3 / 38 | |
| 4.0.0 | 3 / 38 | |
| 3.1.2 | 1 / 32 | |
| 3.1.1 | 1 / 28 | |
| 3.1.0 | 1 / 28 | |
| 3.0.0 | 1 / 28 | |
| 2.1.2 | 0 / 28 | |
| 2.1.1 | 0 / 28 | |
| 2.1.0 | 0 / 28 | |
| 2.0.1 | 0 / 25 | |
| 2.0.0 | 0 / 25 | |
| 1.3.1 | 0 / 25 | |
| 1.3.0 | 0 / 24 | |
| 1.2.1 | 0 / 24 | |
| 1.2.0 | 0 / 24 | |
| 1.1.0 | 0 / 24 | |
| 1.0.0 | 0 / 22 | |
| 7.0.0-rc.0 | 0 / 34 | |
| 7.0.0-beta.0 | 0 / 32 |
v7.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.0
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
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.