You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's getting fairly common for build systems to output not only the artifact they are building i.e container image but also a in-toto attestation in the form of slsa provenance.
This provenance file can be signed and stored in an OCI registry using cosign, so similarly to #244, we could pull that data from the container image being attested in Chainloop.
It's getting fairly common for build systems to output not only the artifact they are building i.e
container image
but also a in-toto attestation in the form of slsa provenance.This provenance file can be signed and stored in an OCI registry using cosign, so similarly to #244, we could pull that data from the container image being attested in Chainloop.
This feature is two fold
att
files associated with a container image. Obviously operators should be the ones deciding what container images should contain one, again, similarly to feat: being able to automatically pull and record attached SBOMS #244The text was updated successfully, but these errors were encountered: