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

release/sbom/npm

Releases publish an SBOM

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

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

Requirement

npm resolves a package’s dependencies from its manifest and lockfile; the registry holds the graph, so a separate SBOM adds nothing unless the package bundles dependencies (then npm sbom with the files uploaded 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.