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

release/sbom/nuget

Releases publish an SBOM

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

Severitywarning
Tiers1
Artifactnuget
Scoperoot
Kindoutcome
Sourcelibrary v0.6.0
Selected byfleetlint-recommended@v0.6.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() > 0

Fix

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.

A finding of this rule points at the file artifact.workflows.size() > 0 ? artifact.workflows[0] : ".github/workflows/release.yml" yields.

Sources


Generated by fleetlint docs from catalog v0.6.0.