Basics

SBOM example: a CycloneDX and SPDX file, explained line by line

By SBOMBox SBOM experts · · 3 min read

Short answer: an SBOM is a JSON (or XML) file with two parts: metadata about the document (who made it, when, with which tool, about which product) and a list of components (name, version, identifier, supplier, licence, hash) linked by dependency relationships. Below is a small but complete example in CycloneDX and in SPDX, then how to check your own file.

A CycloneDX SBOM example

{
  "bomFormat": "CycloneDX",
  "specVersion": "1.6",
  "serialNumber": "urn:uuid:1b4e28ba-2fa1-41d2-883f-0016d3cca427",
  "version": 1,
  "metadata": {
    "timestamp": "2026-11-13T09:00:00Z",
    "lifecycles": [{ "phase": "build" }],
    "tools": { "components": [{ "type": "application", "name": "syft", "version": "1.18.0" }] },
    "authors": [{ "name": "Example Ltd build team" }],
    "component": {
      "type": "application", "bom-ref": "app", "name": "invoice-service", "version": "3.2.0"
    }
  },
  "components": [
    {
      "type": "library",
      "bom-ref": "pkg:npm/express@4.21.2",
      "supplier": { "name": "OpenJS Foundation" },
      "name": "express",
      "version": "4.21.2",
      "purl": "pkg:npm/express@4.21.2",
      "licenses": [{ "license": { "id": "MIT" } }],
      "hashes": [{ "alg": "SHA-512", "content": "7f1a…" }]
    }
  ],
  "dependencies": [
    { "ref": "app", "dependsOn": ["pkg:npm/express@4.21.2"] }
  ]
}
What each CycloneDX field is for
FieldMeaningMinimum element
bomFormat, specVersionThe format and its versionSBOM data format name and version
serialNumber, versionIdentify this SBOM and its revisionSBOM version
metadata.timestampWhen it was generatedSBOM timestamp
metadata.lifecyclesSource, build or post-buildGeneration context
metadata.toolsGenerator name and versionTool name and version
metadata.authorsWho produced the SBOMSBOM author
metadata.componentThe product the SBOM describes(the root of the dependency graph)
supplier, name, versionWho makes the component, what it is, which versionComponent producer, name, version
purlA package URL that vulnerability databases understandComponent identifiers
licenses, hashesLicence and integrity hashComponent licence, hash value and algorithm
dependenciesWhich component pulls in whichDependency relationship

The right-hand column maps to CISA's 2026 SBOM minimum elements. Hashes are shortened here; a real file carries the full value.

The same SBOM in SPDX

{
  "spdxVersion": "SPDX-2.3",
  "dataLicense": "CC0-1.0",
  "SPDXID": "SPDXRef-DOCUMENT",
  "name": "invoice-service-3.2.0",
  "documentNamespace": "https://example.com/spdx/invoice-service-3.2.0-1b4e28ba",
  "creationInfo": {
    "created": "2026-11-13T09:00:00Z",
    "creators": ["Organization: Example Ltd", "Tool: syft-1.18.0"],
    "comment": "Generated at build time from the release artifact."
  },
  "packages": [
    {
      "SPDXID": "SPDXRef-app", "name": "invoice-service", "versionInfo": "3.2.0",
      "downloadLocation": "NOASSERTION"
    },
    {
      "SPDXID": "SPDXRef-express",
      "name": "express",
      "versionInfo": "4.21.2",
      "supplier": "Organization: OpenJS Foundation",
      "downloadLocation": "https://registry.npmjs.org/express/-/express-4.21.2.tgz",
      "licenseConcluded": "MIT",
      "checksums": [{ "algorithm": "SHA512", "checksumValue": "7f1a…" }],
      "externalRefs": [{
        "referenceCategory": "PACKAGE-MANAGER", "referenceType": "purl",
        "referenceLocator": "pkg:npm/express@4.21.2"
      }]
    }
  ],
  "relationships": [
    { "spdxElementId": "SPDXRef-DOCUMENT", "relationshipType": "DESCRIBES", "relatedSpdxElement": "SPDXRef-app" },
    { "spdxElementId": "SPDXRef-app", "relationshipType": "DEPENDS_ON", "relatedSpdxElement": "SPDXRef-express" }
  ]
}

The content is the same; the shape differs. SPDX keeps creators as typed strings, identifiers in externalRefs and the graph in relationships. If you are choosing between them, see CycloneDX or SPDX?.

How to validate and check an SBOM

Two different checks matter, and most teams only run the first:

Where real SBOMs fall short

To produce an SBOM like this automatically, see generating an SBOM in GitHub Actions or Syft vs Trivy vs cdxgen.

Frequently asked questions

What does an SBOM look like?

A machine-readable JSON or XML file. It has document metadata (author, timestamp, tool, the product described) and a list of components, each with a name, version, identifier such as a purl, supplier, licence and hash, plus the dependency relationships between them.

What format is an SBOM?

Almost always CycloneDX or SPDX, usually in JSON. Both are international standards: CycloneDX is ECMA-424 and SPDX is ISO/IEC 5962.

How do I validate an SBOM?

Validate the schema with a tool such as the CycloneDX CLI, sbom-utility or the SPDX tools, then check its quality: whether every component has the fields needed for vulnerability and licence management. The SBOMBox free checker does the quality check.

Where can I find SBOM examples?

The CycloneDX project publishes example BOMs on GitHub, and the SPDX specification includes examples. The annotated examples on this page show a minimal file that meets CISA's 2026 minimum elements.