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

release/sbom/crate

Releases publish an SBOM

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

Severitywarning
Tiers1
Artifactcrate
Scoperoot
Kindexpr
Sourcelibrary v0.5.0
Selected byfleetlint-recommended@v0.5.0

Requirement

crates.io holds the dependency graph and cargo-auditable embeds it in binaries; binaries built from the crate are checked as release files.

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

Applies when

false

Check

true

Fix

Run the artifact’s SBOM producer in the release workflow (fleetlint explain release/sbom/<artifact>): syft or GoReleaser sboms: for release files, BuildKit sbom: true or cosign attest --type spdx for an image, the CycloneDX build plugin for Maven, NuGet and Android; upload the files with 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


Generated by fleetlint docs from catalog v0.5.0.