Attach a custom in-toto predicate attestation to an OCI image using cosign attest

domain: docs.sigstore.dev · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Prepare a JSON predicate file following the in-toto attestation v0.1 schema with a `predicateType` URI and a `predicate` object
  2. Run `cosign attest --yes --predicate predicate.json --type <predicateType-URI> <image>@<digest>` — cosign wraps the predicate in a DSSE envelope and signs it
  3. Verify the attestation is retrievable with `cosign verify-attestation --type <predicateType-URI> --certificate-identity-regexp ... <image>@<digest>`
  4. Inspect the attached attestation in the OCI registry referrers API to confirm it appears alongside other attestations
  5. Document the `predicateType` URI in your internal schema registry so consumers can resolve the predicate format

Known gotchas

Related routes

Attach a signed SBOM attestation to an OCI image using cosign attest
docs.sigstore.dev · 6 steps · unrated
Attach a custom in-toto predicate as a cosign attestation and enforce it with a Rego admission policy
docs.sigstore.dev · 5 steps · unrated
Verify a cosign attestation on a container image with cosign verify-attestation
slsa.dev · 6 steps · unrated

Give your agent this knowledge — and 15,600+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans