release/sbom/image
Releases publish an SBOM
Implements release/sbom for the image artifact: it runs when the release publishes one (see artifacts).
| Severity | warning |
| Tiers | 1 |
| Artifact | image |
| Scope | root |
| Kind | outcome |
| Source | library v0.4.0 |
| Selected by | fleetlint-recommended@v0.4.0 |
Requirement
The image’s SBOM is attached to its digest: BuildKit sbom: true (build-push-action or docker buildx build --sbom=true), cosign attest --type spdx|cyclonedx, or syft/trivy over the pushed image with the result uploaded or attested, GoReleaser dockers_v2: with sbom: true or kos: (ko attaches an SPDX SBOM unless sbom: none).
Why
Consumers and scanners need to know what is inside an artifact; generating the SBOM in the pipeline ties it to the exact build.
Capability applies when
release.exists || repo.artifacts.size() > 0Fix
Set sbom: true (and provenance: true) on docker/build-push-action; BuildKit attaches the SBOM to the image digest.
Agent instruction: Add sbom: true to the docker/build-push-action step’s with:; nothing else changes.
Sources
- https://csrc.nist.gov/pubs/sp/800/218/final (standard, PS.3.2: Collect, safeguard, maintain, and share provenance data for all components of each software release)
- https://github.com/ossf/scorecard/blob/main/docs/checks.md (standard, SBOM)
- https://spdx.github.io/spdx-spec/v2.3/ (spec)
- https://cyclonedx.org/specification/overview/ (spec)
- https://fleetlint.org/baseline/#releases
- https://docs.docker.com/build/metadata/attestations/sbom/ (spec)
- https://docs.github.com/en/actions/security-for-github-actions/using-artifact-attestations/using-artifact-attestations-to-establish-provenance-for-builds (guidance, Generating an SBOM attestation for container images)
- https://github.com/anchore/syft (spec)
Generated by fleetlint docs from catalog v0.4.0.