supply-chain-stack
Chart · Stacks · standard · v0.0.8
Admission-time supply-chain control: Kyverno admits only QuenchWorks images signed by the QuenchWorks build workflows (cosign keyless, checked against Sigstore) in the namespaces you label, and trivy-operator scans what runs.
Version
The latest line lives at the base page; older lines have their own page so you can pin and verify exactly that version. Only the most recent releases are listed — an older chart pins an older image digest.
Deployed image digest
sha256:636a67e0f3a792f4b42be772e8bfc58c35973e4276044306700d481dd49b192bChart OCI version
oci://ghcr.io/quenchworks/charts/supply-chain-stack:0.0.8The chart pins its image by this signed digest, so you never track it yourself. Signatures, SBOM, and provenance attach to the same digest.
Install the chart
Deploy to Kubernetes with hardened defaults. The chart pins its image by signed digest, so you never track it yourself.
Install (latest)
helm install my-supply-chain-stack oci://ghcr.io/quenchworks/charts/supply-chain-stack --version 0.0.8Deploys images (digest-pinned)
- kyverno1.19.1A
ghcr.io/quenchworks/images/kyverno@sha256:636a67e0f3a792f4b42be772e8bfc58c35973e4276044306700d481dd49b192b - kubectl1.37.1A
ghcr.io/quenchworks/images/kubectl@sha256:d5c4037b5c931585adcd7d8c997f094c9b8b90e56600ed2ff0f585b1b6b48cee - trivy-operator0.34.0A
ghcr.io/quenchworks/images/trivy-operator@sha256:22d4dd8a873268856b97f0bad5a2896f0d6d1d6571a153f6f5e016b064205328 - trivy-scanner0.74.0
ghcr.io/quenchworks/images/trivy-scanner:0.74.0
Charts used:
- Chart version
- 0.0.8
- App version
- 1.0.0
- Chart license
- Apache-2.0
- App license
- Unknown
- Signed
- cosign (keyless)
- Values schema
- yes
- Last published
- 2026-10-11
Verify the chart
cosign verify ghcr.io/quenchworks/charts/supply-chain-stack:0.0.8 \
--certificate-identity-regexp 'https://github.com/quenchworks/.+' \
--certificate-oidc-issuer https://token.actions.githubusercontent.comTransparency
The chart publishes its attestations on GitHub and the image it deploys carries its own on the same digest, publicly verifiable with the commands above. Both log to the Sigstore transparency log (Rekor), which cosign verify checks for you.