package-hash
Generates a hash for an installed npm package, useful for salting caches
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Documented legitimate maintainer transition from novemberborn to coreyfarrell in 2019; coreyfarrell has strong track record (285 approved/0 rejected). Stable for this package. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): coreyfarrell is the known successor maintainer with a strong track record; this is a legitimate handoff, not a compromise. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process is used to invoke git for hashing purposes — core to the package's documented functionality. Not a security risk. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Buffer.from(hash, 'hex') is standard hex-to-buffer conversion for a hashing utility; no obfuscation or malicious payload involved. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 4.0.0 | 4 / 6 | |
| 3.0.0 | 4 / 6 | |
| 2.0.0 | 4 / 6 | |
| 1.2.0 | 1 / 12 | |
| 1.1.0 | 1 / 12 | |
| 1.0.0 | 1 / 12 |
v4.0.0
2 findingsThis version was published by a different npm account than previous versions on 2019-04-09. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.