SBOM Inventory Comparator

Compare supported SBOM JSON inventories and filter changes while retaining complete exports.

On-device No sign-up Free to use

Compare inventories controls

?

CycloneDX 1.4, 1.5 or 1.6 JSON, or SPDX 2.2 or 2.3 JSON. Up to 5 MiB and 5,000 components.

?

The later SBOM, in the same or the other supported format. Both documents stay in your browser.

Drop your file here

or choose one from your device

One supported UTF-8 JSON file up to 5 MiB. It takes priority over the before text.

    Drop your file here

    or choose one from your device

    One supported UTF-8 JSON file up to 5 MiB. It takes priority over the after text.

      ?

      The table shows up to 300 matching rows. Downloads retain the complete comparison.

      Processed in your browser. Your inputs stay on this device.

      Showing an example. Change the fields, then use compare inventories to update it.

      Result

      Showing an example.

      Update the declared logger version, remove parser and add router in two example inventories.

      1 added, 1 removed, 1 version change, 0 licence declaration changes.

      Loading the tool. Your result will appear here.

      https://usefreetools.net/sbom-inventory-comparator · 20 November 2026

      Was this helpful?

      How to use SBOM Inventory Comparator

      1. Paste the earlier and later inventories or select one supported UTF-8 JSON file for either state. A selected file replaces the text on that side.
      2. Use CycloneDX 1.4–1.6 or SPDX 2.2–2.3 JSON. Cross-format comparison needs compatible PURLs; other identifiers are not guessed across formats.
      3. Choose a component view and run Compare inventories. Review added, removed, exact version-string and declared-licence changes, plus unmatched identities.
      4. Read up to 300 matching rows on the page. Download CSV/JSON for the complete comparison, and investigate component declarations separately from any vulnerability or licence decision.

      Example: SBOM Inventory Comparator

      Update the declared logger version, remove parser and add router in two example inventories.

      You add
      Before SBOM (JSON): { "bomFormat": "CycloneDX", "specVersion": "1.6", "components": [ { "type": "library", "group": "org.example", "name": "logger", "version": "1.2.0", "purl": "pkg:maven/org.example/logger@1.2.0", "bom-ref": "logger@1.2.0", "licenses": [ { "license": { "id": "Apache-2.0" } } ] }, { "type": "library", "group": "org.example", "name": "parser", "version": "3.0.1", "purl": "pkg:npm/@example/parser@3.0.1", "bom-ref": "parser@3.0.1" } ] } After SBOM (JSON): { "bomFormat": "CycloneDX", "specVersion": "1.6", "components": [ { "type": "library", "group": "org.example", "name": "logger", "version": "1.3.0", "purl": "pkg:maven/org.example/logger@1.3.0", "bom-ref": "logger@1.3.0", "licenses": [ { "license": { "id": "Apache-2.0" } } ] }, { "type": "library", "group": "org.example", "name": "router", "version": "0.9.0", "purl": "pkg:npm/@example/router@0.9.0", "bom-ref": "router@0.9.0" } ] } Components to display: all
      You get
      1 added, 1 removed, 1 version change, 0 licence declaration changes.

      Options

      Before SBOM (JSON)
      CycloneDX 1.4, 1.5 or 1.6 JSON, or SPDX 2.2 or 2.3 JSON. Up to 5 MiB and 5,000 components.
      After SBOM (JSON)
      The later SBOM, in the same or the other supported format. Both documents stay in your browser.
      Before SBOM file (optional)
      One supported UTF-8 JSON file up to 5 MiB. It takes priority over the before text.
      After SBOM file (optional)
      One supported UTF-8 JSON file up to 5 MiB. It takes priority over the after text.
      Components to display
      The table shows up to 300 matching rows. Downloads retain the complete comparison.

      Supported inputs and limits

      • Supported CycloneDX/SPDX JSON subset only.
      • No XML, vulnerability feed, live package lookup, licence advice or software-composition certification.
      • Accepts CycloneDX 1.4–1.6 or SPDX 2.2–2.3 JSON, up to 5 MiB and 5,000 components per document.
      • Optional files replace pasted JSON.
      • Versioned PURLs are normalized for component comparison; malformed and ambiguous duplicate identities are refused.

      Where your input is processed

      This tool does not upload your inputs. See the limits for anything saved on your device.

      An inventory difference is not a vulnerability finding

      Component identity first uses PURL without its version, while retaining literal qualifiers and subpaths. Within one format it can then use explicit bom-ref/SPDXID or an unambiguous name. Cross-format items without compatible PURLs remain unmatched. Versions compare as exact strings, not semantic versions. Licence strings are declarations from the supplied documents. None of these differences is a CVE finding, dependency-resolution result or legal conclusion.

      Questions about SBOM Inventory Comparator

      Does a changed version mean vulnerable?

      No. This comparator has no current vulnerability feed.

      Are licence changes legal advice?

      No. The report compares declarations without interpreting permission or obligations.

      Can ambiguous components be merged?

      No. Ambiguous identities need explicit review rather than silent matching.

      Page updated · Project managed by Tony Hines · Report a problem with SBOM Inventory Comparator