fleetlint Policy for a fleet of repositories
v0.3
Getting started

release/sbom

Releases publish an SBOM

Severityerror
Tiers1
Stacksany
Scoperoot
Kindoutcome
Sourcelibrary v0.0.0-20261011205826-ecb4e9b3ffd4
Selected byfleetlint-recommended@0.1.0

Requirement

Every release produces an SPDX or CycloneDX SBOM for its artifacts, generated inside the release pipeline and published alongside them. Any recognised producer counts: GoReleaser sboms:, anchore/sbom-action or CycloneDX actions, syft/cyclonedx/trivy commands, a Makefile sbom target the release workflow calls, a build-tool plugin, or docker/build-push-action with sbom: true. Repositories add producers with accept:.

Why

Consumers and scanners need to know what is inside an artifact; generating the SBOM in the pipeline ties it to the exact build.

Applies when

release.exists

Fix

Add an SBOM step to the tag-triggered release workflow (syft, SPDX JSON, one per artifact) or a sboms: section to .goreleaser.yaml, and upload the files with the release.

Agent instruction: In the tag-triggered release workflow add a step running syft on each artifact producing SPDX JSON files, and include them in the release upload step. Do not change other steps. If the repo uses GoReleaser, add a sboms: section instead.

See: https://fleetlint.org/baseline/#releases


Generated by fleetlint docs from catalog v0.0.0-20261011205826-ecb4e9b3ffd4.