Skip to converter

XML records to CycloneDX 1.5 JSON SBOM (restricted) Converter.

Exchange a basic software bill of materials package inventory from XML records to CycloneDX 1.5 JSON SBOM (restricted) without uploading files.

Featured resources

App or project

NGSpeak: Language Learning App

Learn English and Bengali with 160 offline-first lessons across CEFR A1–C2, including speaking, writing, pronunciation practice, and progress tracking.

Download Now

Convert your file

INPUTXML records
OUTPUTCycloneDX 1.5 JSON SBOM (restricted)
Files stay on your device

Up to 2 MiB · 1–2,000 library package records · Local conversion

Choose a compatible source file to begin.
Private processingYour source file stays in your browser
Original stays intactDownload a new output file
Real formatsUnsupported conversions show an error

STEP BY STEP

How to convert XML records to CycloneDX 1.5 JSON SBOM (restricted)

  1. Choose a source file. Select a real XML records file from your device.
  2. Run the local converter. The converter checks the input and processes it locally using the appropriate browser engine.
  3. Download the result. Save the generated CycloneDX 1.5 JSON SBOM (restricted) file. Your original file is unchanged.

FORMAT GUIDE

Why convert XML records to CycloneDX 1.5 JSON SBOM (restricted)?

Review simple package names, versions, known license IDs and package URLs in a spreadsheet or another narrowly supported SBOM format.

  • Auditing a curated library inventory in a spreadsheet.
  • Exporting a simple CycloneDX list as a restricted SPDX 2.3 document.
  • Preparing package inventories without uploading dependency information.

UNDERSTAND YOUR FILES

XML records vs. CycloneDX 1.5 JSON SBOM (restricted): what changes?

Input · XML records

A simple records-based XML table format with record elements and named cells, rather than arbitrary XML documents.

Output · CycloneDX 1.5 JSON SBOM (restricted)

CycloneDX 1.5 is a JSON SBOM standard. This tool exchanges only a documented package-only library inventory subset, not dependency or vulnerability records.

Review simple package names, versions, known license IDs and package URLs in a spreadsheet or another narrowly supported SBOM format. Choosing an output format changes how another app reads the file; it does not restore detail missing from your source.

Before you share the output

Check column headings, escaped characters, delimiters and empty values. Data type information and spreadsheet formulas may not survive a plain-text format change.

Your files and privacy

Your selected file is converted on your device. You can download the new file while keeping the original unchanged.

Some formats work differently across browsers and devices. Check the converted result before using it for important work. Advertising and other optional website services may have separate privacy practices.

Format compatibility and limitations

Strict local package inventory only: 1–2,000 library entries, up to 2 MiB, with exactly four table columns in order: package_name, version, license_id, purl. Names and versions are required. License ID may be blank or one of a documented set of simple SPDX identifiers; license expressions are not supported. Package URLs are optional, limited to a safe subset of PURL types. CycloneDX inputs must be version 1.5 with only basic library components. SPDX inputs must be version 2.3 in the exact NGInfinite package-only document profile; generated SPDX includes administrative metadata and unknown values marked NOASSERTION. Dependency graphs, vulnerabilities, hashes, files, external component links, rich licensing and unsupported annotations are rejected rather than silently discarded. No dependency scanning, license analysis or security certification is performed; preserve originals and check interoperability with receiving software.

Actual output behavior depends on the input file, your browser, device resources and the converter engine. Check important files before sharing or replacing them.

HELP & ANSWERS

XML records to CycloneDX 1.5 JSON SBOM (restricted) questions

Does this scan packages or detect vulnerabilities?

No. It only converts local, explicitly supplied package inventory records.

Which spreadsheet headings are required?

Use exactly: package_name, version, license_id, purl.

Does this convert any CycloneDX or SPDX file?

No. Only the documented restricted profile is accepted; dependency graphs and rich metadata are rejected.