release/sbom/release-files
Releases publish an SBOM
Implements release/sbom for the release-files artifact: it runs when the release publishes one (see artifacts).
| Severity | warning |
| Tiers | 1 |
| Artifact | release-files |
| Scope | root |
| Kind | outcome |
| Source | library v0.3.1 |
| Selected by | fleetlint-recommended@v0.3.1 |
Requirement
The workflow that uploads the release files produces an SPDX or CycloneDX SBOM per artifact and uploads it next to them: GoReleaser sboms:, anchore/sbom-action or CycloneDX actions, syft, cyclonedx-* CLIs, trivy, cdxgen, Microsoft’s sbom-tool, cargo-sbom, or a Makefile sbom target the release workflow calls.
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
Add an SBOM step to the 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 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, https://github.com/anchore/syft
Generated by fleetlint docs from catalog v0.3.1.