release/sbom/npm
Releases publish an SBOM
Implements release/sbom for the npm artifact: it runs when the release publishes one (see artifacts).
| Severity | warning |
| Tiers | 1 |
| Artifact | npm |
| Scope | root |
| Kind | expr |
| Source | library v0.6.0 |
| Selected by | fleetlint-recommended@v0.6.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() > 0Applies when
falseCheck
trueFix
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
- 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
Generated by fleetlint docs from catalog v0.6.0.