CycloneDX 1.6 Application SBOM (XML)
The same fictional CycloneDX 1.6 SBOM serialised as XML against the cyclonedx.org/schema/bom/1.6 namespace — the JSON twin of this file carries identical components and edges, so a converter can be diffed exactly. Every package, version, hash and licence is fictional — the tree describes nothing real.
<?xml version="1.0" encoding="UTF-8"?>
<bom xmlns="http://cyclonedx.org/schema/bom/1.6" serialNumber="urn:uuid:2bae4ff9-6a91-404d-a46c-839ce60bc29a" version="1">
<metadata>
<timestamp>2026-01-01T00:00:00Z</timestamp>
<authors>
<author><name>Orchard SBOM Team (fictional)</name><email>sbom@orchard.example</email></author>
</authors>
<component type="application" bom-ref="pkg:npm/%40orchard-example/gateway@4.2.0">
<name>@orchard-example/gateway</name>
<version>4.2.0</version>
<purl>pkg:npm/%40orchard-example/gateway@4.2.0</purl>
</component>
<properties>
<property name="novus:sample">SAMPLE — fictional supply-chain data. Every package, registry, version, hash, licence, advisory identifier and signature in this document is invented.</property>
</properties>
</metadata>
<components>
<component type="library" bom-ref="pkg:npm/%40orchard-example/router@2.1.3">
<name>@orchard-example/router</name>
<version>2.1.3</version>
<purl>pkg:npm/%40orchard-example/router@2.1.3</purl>
<licenses>
<license><id>Apache-2.0</id></license>
</licenses>
<hashes>
<hash alg="SHA-256">d17f0a5171a018c41cdaaa2701b6c32bf49f7404032fa45e5721e2b794cd2e51</hash>
</hashes>
</component>
<component type="library" bom-ref="pkg:npm/%40orchard-example/http-core@1.8.0">
<name>@orchard-example/http-core</name>
<version>1.8.0</version>
<purl>pkg:npm/%40orchard-example/http-core@1.8.0</purl>
<licenses>
<license><id>MIT</id></license>
</licenses>
<hashes>
<hash alg="SHA-256">05dc223ec1875dfd80d8c5873f8c29f036f98587f2fe2d02abc7c718bfb4b8bf</hash>
</hashes>
</component>
<component type="library" bom-ref="pkg:npm/example-metrics@4.0.0">
<name>example-metrics</name>
<version>4.0.0</version>
<purl>pkg:npm/example-metrics@4.0.0</purl>
<licenses>
<license><id>MIT</id></license>
</licenses>
<hashes>
<hash alg="SHA-256">4a8930c617fd12bb99d26e868224d9918e4a3e00f8dd26b876ed19eb6e664f73</hash>
</hashes>
</component>Specifications
- Seed
- 51200
- Sample Only
- true
- Format
- CycloneDX
- Spec Version
- 1.6
- Serialisation
- XML
- Components
- 9
- Line Endings
- LF
Testing contract
Reference control- Scenario
- Convert a CycloneDX XML SBOM to JSON, or validate it against the 1.6 schema.
- Expected result
- Output matches the JSON twin component-for-component: same 9 purls, same SHA-256 values, same 10 dependency refs.
What is a .xml file?
XML (Extensible Markup Language) is a verbose, self-describing markup language using nested tags, attributes, and namespaces to represent structured, hierarchical data. It supports schemas, entities, and validation and underlies many document and data formats. It remains common in enterprise, publishing, and interchange contexts.
How to use this file
Use an example XML file to test parsers, namespace and schema validation, XPath queries, and protection against entity-expansion and external-entity attacks.
How to use this file for testing
“CycloneDX 1.6 Application SBOM (XML)” is a deterministic Novus Examples fixture for Conversion testing, Schema validation, Editor testing. The same content exported across many formats and linked as a group, so you can convert one and diff against the expected twin.
Documented properties for this file: seed 51200 · LF · CycloneDX. Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.
Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such — expect parsers to fail loudly rather than silently accept them.
SBOM, lockfile, provenance, and advisory fixtures describe the same fabricated component tree across formats, so a converter or scanner can be diffed against a known answer. Every package name, version, hash, and advisory ID is invented — never treat a finding here as real.
Code examples
import xml.etree.ElementTree as ET
tree = ET.parse("cyclonedx-1.6-application.xml")
root = tree.getroot()
print(root.tag, [c.tag for c in root][:5])Related files
- mdCoverage — Markdown Pull-Request SummaryThe Markdown comment a coverage bot posts on a pull request: a headline percentage, a per-file table and the uncovered line numbers. Useful for testing Markdown table rendering and for checking that a bot's generated comment matches the machine-readable report it claims to summarise. Every file in this group describes the same four-file source tree and reports 127/140 lines, 17/24 branch outcomes and 18/20 functions, so a converter can be diffed against a known answer.

- jsonAttestation With a Full SPDX PredicateAn in-toto statement whose predicate is an entire SPDX 2.3 document — the nesting that makes attestation payloads large and that a size-limited verifier has to cope with. Every package, version, hash and licence is fictional — the tree describes nothing real.

- jsoncargo-audit Report (JSON)A cargo-audit report that shows three findings while a fourth is on the ignore list, plus an unmaintained-crate warning — so a gate must decide whether warnings count against it. Advisory identifiers use the invented NOVUS-SAMPLE namespace with SAMPLE-CVE aliases; no identifier here refers to a published CVE, GHSA or OSV record, and no package named exists.

- lockCargo.lock (version 4)A Rust Cargo.lock in the version 4 format — TOML [[package]] tables with a registry source, a sha256-shaped checksum and a name-only dependencies array that resolves against the other tables. Every package, version, hash and licence is fictional — the tree describes nothing real.

- jsonCSAF 2.0 VEX DocumentA CSAF 2.0 VEX advisory with the nested product tree that CSAF requires — vendor, product name, product version — and product_status buckets rather than a per-statement status field. Advisory identifiers use the invented NOVUS-SAMPLE namespace with SAMPLE-CVE aliases; no identifier here refers to a published CVE, GHSA or OSV record, and no package named exists.

- jsonCycloneDX VEX DocumentA CycloneDX VEX document asserting a different analysis state for each of the four SAMPLE advisories, so a suppression pipeline can be tested against every branch at once. Advisory identifiers use the invented NOVUS-SAMPLE namespace with SAMPLE-CVE aliases; no identifier here refers to a published CVE, GHSA or OSV record, and no package named exists.

Generated by generation/supply_chain.py. Free for any use, no attribution required — license.