DevGuard SLSA API
SLSA build provenance records which source, which build configuration and which builder produced an artifact. The claim is only worth as much as the identity behind it, so DevGuard does not let a pipeline sign its own provenance: the CI job sends what it built along with its OIDC workload identity token, DevGuard verifies that token with its issuer, writes the verified identity into the provenance and signs the result with a key no CI job ever sees.
Signing returns a DSSE envelope, or a sigstore bundle when a transparency log is configured. The public key endpoint hands out the key that verifies those signatures, which is what cosign verify-attestation needs when checking an image outside the pipeline that produced it.
Related Documentation
- Sign Build Provenance with DevGuard — the pipeline setup these endpoints serve
- SLSA Level 3 — why the signing key stays out of CI
- SLSA Framework — the levels and what each one requires
- Provenance Tracking — how build history is retained
- Attestations API — the related attestation surface
- In-toto API — link and layout verification
- Use the DevGuard API — authentication and conventions
- DevGuard API Reference