@hapi/cryptiles
General purpose crypto utilities
8
Versions
BSD-3-Clause
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
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
nlfdevinivywyattlloydbensonnargonathcjihrigmarsup
Keywords
cryptographysecurityutilites
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): @hapi/cryptiles is a long-established hapi ecosystem package; lack of Sigstore provenance is expected for packages of this age and is not a security concern here. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 6.0.3 | 1 / 5 | |
| 6.0.2 | 1 / 5 | |
| 6.0.1 | 1 / 5 | |
| 6.0.0 | 1 / 5 | |
| 5.1.0 | 1 / 2 | |
| 5.0.0 | 1 / 2 | |
| 4.2.1 | 1 / 2 | |
| 4.2.0 | 1 / 2 |
v4.2.1
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.0
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.