fleetlint Policy for a fleet of repositories
v0.11 (latest)
Getting started

release/sbom

Releases publish an SBOM

A capability keyed by published artifact: each kind the release publishes is checked by its own implementation, and every one must pass. Implemented for android-app, apple-app, crate, gem, helm-chart, image, maven, npm, nuget, oci-artifact, pub, pypi, release-files.

Severitywarning
Tiers1
Stacksany
Scoperoot
Kindcapability
Sourcelibrary v0.8.0
Selected byfleetlint-recommended@v0.8.0

Requirement

Every artifact a release publishes that carries its own dependencies (files on a forge release, a container image, a Maven artifact, a NuGet package, an Android app) comes with an SPDX or CycloneDX SBOM generated inside the release pipeline and published next to it. A package the registry resolves from a manifest (npm, PyPI, crates.io, RubyGems, pub.dev) is not checked: the registry holds its dependency graph. Each artifact kind’s implementation names its producers; repositories add producers with accept:.

Why

Consumers and scanners need to know what is inside an artifact; generating the SBOM in the pipeline ties it to the exact build.

Applies when

release.exists || repo.artifacts.size() > 0

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 release workflow add a step producing an SBOM for each published artifact with its producer (syft writing SPDX JSON for files, BuildKit sbom: true for images, the build tool’s CycloneDX plugin for Maven, NuGet and Android) and upload the files with the release or publish them with the artifact. Do not change other steps. If the repo uses GoReleaser, add a sboms: section instead.

Sources


Generated by fleetlint docs from catalog v0.8.0.