What is SBOM generation?

Producing a machine-readable inventory of everything in a build, usually in CycloneDX or SPDX format.

By Cláudia FernandesUpdated

A Software Bill of Materials lists every component and version in a piece of software so that, when the next widely-exploited dependency vulnerability lands, an organization can answer 'are we affected' in minutes rather than weeks.

SBOMs have moved from good practice to procurement requirement in regulated sectors and government supply chains, and vendors that generate them sometimes charge for it as an add-on or a higher tier. An SBOM is only as useful as the process around it: one generated for a procurement form and never refreshed will not answer 'are we affected' on the day it matters.

What to look for

  • Which formats are supported, since CycloneDX and SPDX are the two that matter
  • Whether SBOMs can be generated per build and stored historically
  • Signing and attestation support, if you need supply-chain provenance
  • Whether an existing SBOM can be imported and scanned

Best 11 SBOM generation tools

Every tool in the directory whose documentation covers this, 10 fully and 1 partially. Full support is shown first. Shown in a random order that changes on every visit, so no tool gets an advantage from its position.

Support is not the same as parity, since some implementations are narrower in scope, gated to a higher plan tier, or maintained only for existing customers. The note under each tool is what its own documentation describes.

FAQ

What is SBOM generation?

Producing a machine-readable inventory of everything in a build, usually in CycloneDX or SPDX format.

How many tools in the directory offer SBOM generation?

11 of the 20 tools in this directory offer SBOM generation, 10 fully and 1 partially:

Support is not the same as parity, since some implementations are narrower in scope, gated to a higher plan tier, or maintained only for existing customers. The note under each tool is what its own documentation describes.

What should you check when comparing tools with SBOM generation?

Four things:

  • Which formats are supported, since CycloneDX and SPDX are the two that matter
  • Whether SBOMs can be generated per build and stored historically
  • Signing and attestation support, if you need supply-chain provenance
  • Whether an existing SBOM can be imported and scanned