@parcel/hash
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:hapi | AI (typosquat): @parcel/hash is the official Parcel bundler hashing utility under the @parcel npm scope; no typosquat relationship to 'hapi' exists. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Established native binding package; missing description is a minor metadata gap, not a malice indicator. | ai | |
| provenance | no-provenance | AI (provenance): Provenance attestation is a best-practice gap; not a blocker for an established, well-maintained package. | ai | |
| npm-metadata | bundled-binaries | AI (npm-metadata): @parcel/hash is a NAPI-RS native addon; bundled .node binaries are the expected delivery mechanism for prebuilt platform-specific binaries. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require is the standard NAPI-RS platform-selection pattern, loading one of the bundled .node files based on OS/arch — not arbitrary module loading. | ai | |
| dependencies | unvetted-dep:detect-libc | AI (dependencies): detect-libc is a well-known utility used by native addons to distinguish glibc vs musl Linux; its use here is expected and benign. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 2.9.3 | 1 / 2 | |
| 2.9.2 | 1 / 2 | |
| 2.9.1 | 1 / 2 | |
| 2.9.0 | 1 / 2 | |
| 2.8.3 | 2 / 2 | |
| 2.8.2 | 2 / 2 | |
| 2.8.1 | 2 / 2 | |
| 2.8.0 | 2 / 2 | |
| 2.7.0 | 2 / 2 | |
| 2.6.2 | 2 / 2 | |
| 2.6.1 | 2 / 2 | |
| 2.6.0 | 2 / 2 | |
| 2.5.0 | 2 / 2 | |
| 2.4.1 | 2 / 2 | |
| 2.4.0 | 2 / 2 | |
| 2.3.2 | 2 / 2 | |
| 2.3.1 | 2 / 2 | |
| 2.3.0 | 2 / 2 | |
| 2.2.1 | 2 / 2 | |
| 2.2.0 | 2 / 2 | |
| 2.1.1 | 2 / 2 | |
| 2.1.0 | 2 / 2 | |
| 2.0.1 | 2 / 2 | |
| 2.0.0 | 2 / 2 |
v2.9.3
2 findingsPackage contains compiled binaries that could be backdoors: • parcel-hash.darwin-arm64.node • parcel-hash.darwin-x64.node • parcel-hash.linux-arm-gnueabihf.node • parcel-hash.linux-arm64-gnu.node • parcel-hash.linux-arm64-musl.node • parcel-hash.linux-x64-gnu.node • parcel-hash.linux-x64-musl.node • parcel-hash.win32-x64-msvc.node
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.3
2 findingsPackage contains compiled binaries that could be backdoors: • parcel-hash.darwin-arm64.node • parcel-hash.darwin-x64.node • parcel-hash.linux-arm-gnueabihf.node • parcel-hash.linux-arm64-gnu.node • parcel-hash.linux-arm64-musl.node • parcel-hash.linux-x64-gnu.node • parcel-hash.linux-x64-musl.node • parcel-hash.win32-x64-msvc.node
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.