PodSalsa is a reference for building and releasing a Go application on GitHub with SLSA Build Level 3 provenance. The documentation is organised around three questions.
flowchart LR
A["<b>How is it built?</b><br/>workflows, trusted builders"] --> B["<b>How is it proven?</b><br/>provenance, signing"] --> C["<b>How do you check?</b><br/>verification, enforcement"]
| Documentation | Summary |
|---|---|
| PodSalsa GitHub Workflows | Every workflow in the repository, and how the release pipeline fits together |
| Trusted builders and SLSA Build L3 | Why the release is split into a caller and two trusted builders |
| GitHub Actions best practices | Secrets, permissions, script injection, pinning, Scorecard, Allstar |
| Documentation | Summary |
|---|---|
| Sigstore | How keyless signing works with Fulcio, Rekor and OIDC |
| Rekor transparency log | Querying the log and reading the signing certificate |
| Documentation | Summary |
|---|---|
| Release verification | Verify every released artifact with gh attestation verify and cosign |
| Prerequisites | Installing gh, cosign, crane, cue |
| Enforcement on Kubernetes | Blocking unverified images with Kyverno on a local kind cluster |
| policy.cue | The CUE policy the provenance contents must satisfy |
- Additional information — supplementary material that is not part of the release pipeline, such as component analysis with Dependency-Track and GUAC.
- Archive — superseded approaches kept for reference, including verification of releases up to v0.9.x.