# What is CycloneDX? The SBOM standard, explained with examples

URL: https://sbombox.com/blog/what-is-cyclonedx
By SBOMBox SBOM experts. Published 2026-11-17

> CycloneDX is the OWASP bill of materials standard behind most SBOMs. What it covers, its versions, a minimal example and how to generate and validate one.

Short answer: CycloneDX is an open standard for bills of materials, run by OWASP and standardised by Ecma International as ECMA-424. A CycloneDX SBOM is a JSON or XML file that lists every component in a piece of software with its version, package URL, hashes, licences and dependencies. Beyond software, the same format covers services, hardware, cryptography, ML models and VEX statements.

## Where CycloneDX comes from

CycloneDX began in 2017 inside the OWASP community, built for security use cases such as feeding [OWASP Dependency-Track](https://sbombox.com/blog/dependency-track-alternatives). It is now an OWASP flagship project, and Ecma International published it as the standard ECMA-424 in 2024. The other main SBOM format, SPDX, is an ISO standard from the Linux Foundation; [CycloneDX or SPDX?](https://sbombox.com/blog/cyclonedx-vs-spdx-which-to-pick) compares them.

## What a CycloneDX document can describe

**CycloneDX capabilities**

| Capability | What it records | Added in |
| --- | --- | --- |
| SBOM | Software components, versions, purls, hashes, licences, dependency graph | 1.0 onwards |
| VEX and VDR | Whether known vulnerabilities affect the product | 1.4 |
| SaaSBOM | Services, endpoints and data flows | 1.2 onwards |
| HBOM | Hardware devices and firmware | 1.x (device components) |
| ML-BOM | Machine-learning models and datasets | 1.5 |
| CBOM | Cryptographic assets: algorithms, keys, certificates | 1.6 |
| Attestations | Machine-readable claims of conformance with standards | 1.6 |

That breadth is why CycloneDX is a common choice for security teams: one format for every [type of bill of materials](https://sbombox.com/blog/types-of-bill-of-materials). SBOMBox reads CycloneDX 1.4 to 1.7 in JSON or XML.

## A minimal CycloneDX SBOM

```json
{
  "bomFormat": "CycloneDX",
  "specVersion": "1.6",
  "serialNumber": "urn:uuid:3e671687-395b-41f5-a30f-a58921a69b79",
  "version": 1,
  "metadata": {
    "timestamp": "2026-11-17T09:00:00Z",
    "component": { "type": "application", "name": "example-api", "version": "1.4.0" }
  },
  "components": [
    {
      "type": "library",
      "bom-ref": "pkg:npm/express@4.21.2",
      "name": "express",
      "version": "4.21.2",
      "purl": "pkg:npm/express@4.21.2",
      "licenses": [{ "license": { "id": "MIT" } }]
    }
  ],
  "dependencies": [
    { "ref": "pkg:npm/express@4.21.2", "dependsOn": [] }
  ]
}
```

The key parts: bomFormat and specVersion identify the document; metadata says what the SBOM describes and when it was made; components lists each part; dependencies records the graph. A full file is annotated line by line in our [SBOM example](https://sbombox.com/blog/sbom-example).

## How to generate a CycloneDX SBOM

The CycloneDX project maintains a generator for most ecosystems, and general tools such as Syft, Trivy and cdxgen can also write CycloneDX.

**CycloneDX generators by ecosystem**

| Ecosystem | Command | Guide |
| --- | --- | --- |
| npm | npx @cyclonedx/cyclonedx-npm --output-file sbom.cdx.json | [JavaScript](https://sbombox.com/docs/languages/javascript) |
| Python | cyclonedx-py environment --output-file sbom.cdx.json | [Python](https://sbombox.com/docs/languages/python) |
| Maven | mvn org.cyclonedx:cyclonedx-maven-plugin:makeAggregateBom | [Java](https://sbombox.com/docs/languages/java) |
| Go | cyclonedx-gomod mod -json -output sbom.cdx.json | [Go](https://sbombox.com/docs/languages/go) |
| Any repository | cdxgen -o sbom.cdx.json . | [Syft vs Trivy vs cdxgen](https://sbombox.com/blog/syft-vs-trivy-vs-cdxgen) |

Or let SBOMBox pick the right generator for each project and score the result in one step:

```bash
sbombox generate
```

## How to validate a CycloneDX file

- Schema validation: the CycloneDX CLI checks the file against the official JSON or XML schema.
- Content quality: a valid file can still be missing versions, suppliers or hashes. The [free SBOM checker](https://sbombox.com/audit) scores it against BSI TR-03183-2, CISA, NTIA and CRA requirements.
- Browse it: open the file in the [free SBOM viewer](https://sbombox.com/tools/sbom-viewer) to see the components and dependency tree.

```bash
cyclonedx validate --input-file sbom.cdx.json
```

Need SPDX for a customer? The [SBOM converter](https://sbombox.com/tools/sbom-converter) turns CycloneDX into SPDX and back in your browser.

## Frequently asked questions

### What is CycloneDX used for?

Mainly for SBOMs: machine-readable inventories of software components used for vulnerability management, licence compliance and regulatory evidence. It also describes services, hardware, cryptography, ML models and VEX.

### Is CycloneDX an official standard?

Yes. It is an OWASP flagship project and was published by Ecma International as ECMA-424.

### What is the difference between CycloneDX and SPDX?

Both are open SBOM standards. CycloneDX comes from OWASP and is security-focused with wide coverage beyond software; SPDX comes from the Linux Foundation, is ISO/IEC 5962:2021 and grew out of licence compliance.

### Does the Cyber Resilience Act accept CycloneDX?

The CRA requires a commonly used, machine-readable format and does not name one. CycloneDX meets that description, as does SPDX.

### Which file extension does CycloneDX use?

Usually .cdx.json or .cdx.xml, or bom.json and bom.xml.
