What does this Sigstore cosign command produce?
cosign sign registry.example.com/api@sha256:4f1c...
- A copy of the image re-encrypted
- A signature bound to that digest
- A new tag named after the digest
- A scan report of the image's CVEs
cosign signs the immutable image digest and stores the signature in the registry beside it; deploy-time policy can then verify it. Signing a digest rather than a tag avoids a moved tag.
Play DevOps ▸