@hono/zod-validator
Supply chain provenance
Status for the latest visible version.
Maintainers
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 0.8.0 | 0 / 5 | |
| 0.7.6 | 0 / 5 | |
| 0.7.5 | 0 / 5 | |
| 0.7.4 | 0 / 7 | |
| 0.7.3 | 0 / 7 | |
| 0.7.2 | 0 / 7 | |
| 0.7.1 | 0 / 7 | |
| 0.7.0 | 0 / 6 | |
| 0.6.0 | 0 / 6 | |
| 0.5.0 | 0 / 6 |
v0.8.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.