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.4.0 |
| Selected by | fleetlint-recommended@v0.4.0 |
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.
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.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 binaries)
- https://goreleaser.com/customization/sbom/ (spec)
- https://github.com/anchore/syft (spec)
Generated by fleetlint docs from catalog v0.4.0.