fleetlint Policy for a fleet of repositories
v0.11 (latest)
Getting started

release/sbom/image

Releases publish an SBOM

Implements release/sbom for the image artifact: it runs when the release publishes one (see artifacts).

Severitywarning
Tiers1
Artifactimage
Scoperoot
Kindoutcome
Sourcelibrary v0.8.0
Selected byfleetlint-recommended@v0.8.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() > 0

Fix

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.

A finding that names no file points at the first workflow that publishes the artifact, or .github/workflows/release.yml when there is none.

Sources


Generated by fleetlint docs from catalog v0.8.0.