How to use SBOM Inventory Comparator
- 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.
- 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.
- Choose a component view and run Compare inventories. Review added, removed, exact version-string and declared-licence changes, plus unmatched identities.
- 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.
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.