release/sbom/nuget
Releases publish an SBOM
Implements release/sbom for the nuget artifact: it runs when the release publishes one (see artifacts).
| Severity | warning |
| Tiers | 1 |
| Artifact | nuget |
| Scope | root |
| Kind | outcome |
| Source | library v0.4.0 |
| Selected by | fleetlint-recommended@v0.4.0 |
Requirement
The workflow that pushes the package runs the CycloneDX .NET tool (dotnet CycloneDX) or Microsoft’s sbom-tool and ships the SBOM inside or next to the package.
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
Install CycloneDX as a dotnet tool and run dotnet CycloneDX <solution> -o sbom before dotnet nuget push; include the file in the package or the release.
Agent instruction: In the tag-triggered release workflow add a step producing an SPDX JSON SBOM for each published artifact (syft for files, BuildKit sbom: true for images, the stack’s CycloneDX plugin otherwise) and include the files 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://github.com/CycloneDX/cyclonedx-dotnet (spec)
Generated by fleetlint docs from catalog v0.4.0.