@twsxtd/hapi-linux-x64
hapi binary for linux x64
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | bundled-binaries | AI (npm-metadata): Package is a platform-specific prebuilt-binary distribution (bin/hapi); the binary is its stated function, no wrapper/install/exfil code. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.23.4 | 0 / 0 | |
| 0.23.3 | 0 / 0 | |
| 0.23.2 | 0 / 0 | |
| 0.23.1 | 0 / 0 | |
| 0.22.3 | 0 / 0 |
v0.23.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.3
2 findingsPackage contains compiled binaries that could be backdoors: • bin/hapi
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.