shipcra

What is an SBOM? Software bill of materials explained, with an example

Reviewed 2 min read

An SBOM, or software bill of materials, is a machine-readable list of the components inside a piece of software: their names, versions, suppliers, licences and how they depend on each other. Under the Cyber Resilience Act, manufacturers must draw one up covering at least the top-level dependencies. They don’t have to publish it.

Key facts

Stands for
Software bill of materials
Main formats
CycloneDX (ECMA-424) and SPDX (ISO/IEC 5962:2021)
Basis in the CRA
Annex I, Part II, point 1
Minimum depth under the CRA
The top-level dependencies
Publication
Not required; available to market surveillance authorities on request

What an SBOM contains

Think of it as the ingredients list for your software. For each component, an SBOM usually records:

  • Name and version, for example react 19.2.0.
  • An identifier, typically a package URL (pkg:npm/react@19.2.0), so other tools can match it against vulnerability databases.
  • Supplier or author, where it is known.
  • Licence, such as MIT or Apache-2.0.
  • Relationships: which component depends on which, so you can tell direct dependencies from transitive ones.
  • Hashes, when the generator can compute them, to prove which exact file was shipped.

The document also describes the product itself (name, version, manufacturer) and when the SBOM was generated.

An SBOM example

Here is a trimmed CycloneDX 1.6 document for a small app with a single dependency:

{
  "bomFormat": "CycloneDX",
  "specVersion": "1.6",
  "serialNumber": "urn:uuid:3e671687-395b-41f5-a30f-a58921a69b79",
  "version": 1,
  "metadata": {
    "timestamp": "2026-11-19T10:00:00Z",
    "component": {
      "type": "application",
      "bom-ref": "lumen-notes@2.4.1",
      "name": "lumen-notes",
      "version": "2.4.1"
    }
  },
  "components": [
    {
      "type": "library",
      "bom-ref": "pkg:npm/react@19.2.0",
      "name": "react",
      "version": "19.2.0",
      "purl": "pkg:npm/react@19.2.0",
      "licenses": [{ "license": { "id": "MIT" } }]
    }
  ],
  "dependencies": [
    { "ref": "lumen-notes@2.4.1", "dependsOn": ["pkg:npm/react@19.2.0"] },
    { "ref": "pkg:npm/react@19.2.0", "dependsOn": [] }
  ]
}

A real app lists hundreds of components. The structure stays the same.

CycloneDX or SPDX

CycloneDX SPDX
Maintained by OWASP, standardised as ECMA-424 The Linux Foundation, standardised as ISO/IEC 5962:2021
Origin Application security Licence compliance
Common encodings JSON, XML JSON, tag-value, RDF, YAML
Good at Dependencies, vulnerabilities, services Licences, files, provenance

Both satisfy the CRA. Converters exist in both directions, so the choice isn’t permanent.

What the Cyber Resilience Act asks for

Annex I, Part II, point 1 says manufacturers shall “identify and document vulnerabilities and components contained in products with digital elements, including by drawing up a software bill of materials in a commonly used and machine-readable format covering at the very least the top-level dependencies of the products.”

In practice:

  • Top-level dependencies are the floor. Most generators list transitive dependencies too, which makes vulnerability matching far more useful.
  • One SBOM per release. The SBOM has to match what you shipped, so regenerate it each time the dependencies change.
  • Keep it, don’t necessarily publish it. It belongs in your technical documentation and goes to authorities on request.

The Commission can adopt implementing acts with more detail on SBOM format and content. Until then, the text above is the requirement.

What an SBOM doesn’t do

An SBOM is an inventory. It doesn’t prove that a product is secure, and it doesn’t show that the product meets the CRA. It is the starting point for the work that does: matching components against known vulnerabilities, deciding what to fix, and reporting when something is actively exploited.

It also only lists what the generator can see. Code you copied into the repository, native libraries and engine runtimes often need to be added by hand. The practical guide to generating an SBOM from a lockfile covers how to catch those gaps.

Questions

Is an SBOM mandatory under the Cyber Resilience Act?

Yes, for products in scope, from 11 December 2027. Annex I, Part II, point 1 requires manufacturers to identify and document components, including by drawing up an SBOM in a commonly used, machine-readable format that covers at least the top-level dependencies.

Do I have to publish my SBOM?

No. The CRA doesn’t require you to make it public. You keep it with your technical documentation and provide it to market surveillance authorities on a reasoned request. If you choose to share it with users, Annex II asks you to say where they can find it.

Should I use CycloneDX or SPDX?

Either meets the CRA’s ‘commonly used and machine-readable’ test. CycloneDX is security-oriented and has strong tooling for vulnerability data; SPDX grew out of licence compliance and is an ISO standard. Pick the one your tools produce and your customers ask for.

What’s the difference between an SBOM and a lockfile?

A lockfile is an input written for your package manager. An SBOM is a standard document meant for people and other tools: it adds identifiers such as package URLs, licences, suppliers and the product it describes.

Sources

  1. Regulation (EU) 2024/2847, Annex I Part II and Annex II, EUR-Lex
  2. CycloneDX specification
  3. SPDX specification

This guide explains the regulation in general terms. It isn’t legal advice for your product.

Turn your lockfile into an SBOM.

shipcra reads your lockfile in the browser and builds a CycloneDX SBOM for your technical documentation. The file never leaves your machine.

Join early access