Free SBOM tool
Free SBOM validator, viewer and vulnerability checker
Validate a CycloneDX or SPDX SBOM, read every component in a searchable viewer, check the NTIA minimum elements and, if you choose, look up known vulnerabilities in OSV.dev. Parsing runs in your browser. The result is an operational observation, not a legal compliance determination.
Validate and view a machine-readable SBOM
CycloneDX 1.2–1.6 JSON/XML or SPDX 2.2–2.3 JSON/tag-value · up to 5 MB · processed in this browser
The file stays in this tab; Vellaci does not receive or store it.
Quality report
Your results will appear here.
Structure, NTIA minimum elements, identifiers, licences and the dependency graph, then an optional known-vulnerability lookup. These are operational observations, not a CRA compliance score.
What it checks
Eight checks between an SBOM file and usable evidence.
Each check answers one question a security team, a customer or an authority will ask of the inventory. Fix the gaps in the generator, not by editing the file after the fact.
| Check | Why it matters | How to fix it |
|---|---|---|
| Format and spec version | Only a document a tool can read is useful evidence. The checker accepts CycloneDX 1.2–1.6 (JSON or XML) and SPDX 2.2–2.3 (JSON or tag-value) and names the exact version it found. | Regenerate with a current generator and set specVersion or SPDXVersion explicitly; if a tool only emits SPDX 3.0, export SPDX 2.3 for consumers that do not read 3.0 yet. |
| Component name and version | Without a version you cannot say whether the release you shipped is exposed to an advisory. | Generate the SBOM from the lockfile or the built artifact, not from the manifest's version ranges. |
| Package URL (purl) | A purl such as pkg:npm/express@4.18.2 lets vulnerability databases match the exact package and version instead of guessing by name. | Use an ecosystem-aware generator; add purls by hand only for vendored code you can identify. |
| CPE and hashes | Other unique identifiers help where no purl exists, and a hash pins the exact artifact that was shipped. | Enable hash output (SHA-256 or stronger) in the generator; keep CPEs for operating-system and firmware components. |
| Supplier and licences | Supply-chain due diligence and licence obligations both start from who supplied a component and under which terms. | Turn on supplier and licence fields; review NOASSERTION values rather than leaving them for later. |
| Dependency graph | Direct versus transitive decides who can fix a vulnerability and how quickly. | Emit the dependencies array (CycloneDX) or DEPENDS_ON and CONTAINS relationships from the described package (SPDX). |
| Duplicate identities | The same package listed twice inflates counts and duplicates every finding. | Deduplicate by purl in the generator or merge step; the checker collapses duplicates and reports how many. |
| Timestamp, tool and author | They show when, how and by whom the inventory was produced, and which release it describes. | Record the creation time, the generator, an author and the described component (metadata.component in CycloneDX). |
How to validate
Validate a CycloneDX or SPDX SBOM in three steps.
CycloneDX (JSON or XML)
- Drop the
bom.json,.cdx.jsonorbom.xmlfile above, or paste its contents. The checker readsbomFormatandspecVersion(or the XML namespace) first and stops on an unsupported version. - Read the quality report: components after deduplication, purl coverage, versions, licences, the dependency graph from the
dependenciesarray and the direct dependencies ofmetadata.component. - Fix gaps in the generator — for example the CycloneDX plugin for your package manager — and run the check again before you attach the file to the release.
SPDX (JSON or tag-value)
- Drop the
.spdx.jsonor.spdxfile, or paste it. SPDX 2.2 and 2.3 are supported; purls are read fromexternalRefsof type purl, CPEs from cpe22Type or cpe23Type references. - Check that the document
DESCRIBESyour product package and thatDEPENDS_ONorCONTAINSrelationships connect it to its components; without them, direct and transitive dependencies cannot be told apart. - Review
NOASSERTIONlicences and suppliers. GitHub’s dependency graph export is SPDX JSON, and container scanners such as Syft and Trivy can emit it too.
The checker parses documents structurally; it does not replace strict schema validation. If a customer or a pipeline requires schema conformance, also run the official CycloneDX CLI or the SPDX project’s validation tools. Read the CycloneDX specification or SPDX 2.3 for field-level detail.
NTIA minimum elements
The seven fields every SBOM should carry.
NTIA's 2021 report “The Minimum Elements for a Software Bill of Materials” lists the baseline data fields. The checker scores each one as present, partial or missing.
- Supplier name
- The entity that creates, defines and identifies the component.
- Component name
- The name the supplier assigned to the unit of software.
- Version of the component
- The identifier the supplier uses for a change from a previous version.
- Other unique identifiers
- Identifiers such as purl, CPE or a hash that look the component up in other sources.
- Dependency relationship
- That component X is included in software Y — the graph from product to dependencies.
- Author of SBOM data
- Who created the SBOM data. When only a generator tool is recorded, the checker reports the element as partial.
- Timestamp
- The date and time the SBOM data was assembled.
The NTIA list is a US baseline that many buyers and tools use as a reference point. The Cyber Resilience Act does not adopt it verbatim; it is still a sound minimum for an inventory you expect to be read by someone else.
Vulnerability check
Check an SBOM for known CVEs.
An SBOM becomes useful the moment you can ask which of its components have published advisories. The optional OSV.dev lookup answers that question by package version.
OSV is an open vulnerability database that aggregates advisories from sources such as the GitHub Advisory Database, PyPA, RustSec, the Go vulnerability database and Linux distributions, and indexes them by package and affected version range. The checker sends each component’s package URL with its version — qualifiers such as ?type=jar removed — in batches of up to 1,000 to OSV’s public query API, then fetches summaries, CVE aliases and the published severity for the first 50 advisories.
Three limits matter. Components without a versioned purl cannot be matched, so purl coverage sets the ceiling of the check. A match means the package version is listed as affected, not that your product is exploitable: the vulnerable function may be unused or unreachable in your build. And a one-off lookup ages as soon as a new advisory is published. The defensible output is a per-product decision — affected, not affected, fixed or under investigation — recorded as VEX, with exploitation signals such as the CISA KEV catalogue and EPSS deciding what to look at first.
Cyber Resilience Act
Where the SBOM sits in the CRA.
Annex I Part II(1) of Regulation (EU) 2024/2847 requires manufacturers to identify and document the vulnerabilities and components in their products, including by drawing up an SBOM in a commonly used, machine-readable format covering at least the top-level dependencies.
The SBOM belongs to the technical documentation and must be available to market surveillance authorities on request; the regulation does not require you to publish it. A structurally sound SBOM is necessary but not sufficient: the same Annex asks manufacturers to remediate vulnerabilities without delay, test, disclose fixed vulnerabilities and run a coordinated disclosure policy, and Article 14 has required reporting of actively exploited vulnerabilities since 11 September 2026.
Read the SBOM guide for the CRA for formats, minimum content and generators per ecosystem, and SBOM vs VEX for how an inventory turns into product-specific exploitability statements.
Continuous monitoring
From a one-off check to an SBOM per release.
Generate the SBOM in the build pipeline for every release, attach it to the release artifact and send it to Vellaci’s SBOM API — SBOM in CI/CD shows GitHub Actions and GitLab CI examples. Vellaci keeps the original file with the product version it describes, deduplicates components, re-matches them as advisories are published and records triage decisions with reasons and CycloneDX VEX per product.
See SBOM management in Vellaci or start with the ingestion documentation.
FAQ
SBOM validator questions.
- Is my SBOM uploaded to Vellaci?
- No. The file is read and parsed in your browser tab and is never sent to Vellaci. Only if you press “Check components against OSV.dev” are the versioned package URLs — and nothing else — sent from your browser directly to the public OSV.dev API, which Google operates.
- Which SBOM formats and versions are supported?
- CycloneDX 1.2 to 1.6 in JSON or XML, and SPDX 2.2 and 2.3 in JSON or tag-value, up to 5 MB in this free checker. Vellaci's authenticated ingestion accepts the same formats in larger files and keeps the original document with the product version.
- Does the checker validate against the JSON Schema?
- Not exhaustively. It parses the document structurally, rejects malformed or unsupported documents and reports missing data that matters operationally. For strict schema conformance, run the official CycloneDX CLI validate command or the SPDX project's validation tools as well — a schema-valid SBOM can still lack versions, purls or a dependency graph.
- How do I check an SBOM for vulnerabilities or CVEs?
- Load the SBOM, then press “Check components against OSV.dev”. Every component with a versioned package URL is looked up by package and version; matches are listed with their OSV advisory id, CVE aliases and the severity published by the source database. Components without purls — vendored code, firmware blobs — cannot be matched this way.
- If a component has an advisory, is my product vulnerable?
- Not necessarily. An advisory says the package version is affected somewhere; whether your product is affected depends on whether the vulnerable code is present, reachable and exploitable in your configuration. Record that decision per product and version, with a justification, as a VEX statement.
- Is a valid SBOM enough for the Cyber Resilience Act?
- No. Annex I Part II(1) requires manufacturers to identify and document components, including in an SBOM covering at least top-level dependencies, but the SBOM is the start of vulnerability handling, not the end. Remediation, disclosure, reporting and technical documentation follow, and the result here is an operational observation, not a compliance determination.
- How do I fix components without a purl?
- Most gaps come from generating the SBOM from source manifests or from a generic filesystem scan. Generate it with the package manager's own plugin from the lockfile or build output, and for vendored or copied code add a purl or at least a CPE and hash where you can identify the upstream package.
- What is the difference between an SBOM validator and an SBOM viewer?
- A validator tells you whether the document is well formed and complete enough to use; a viewer lets you read what is inside it. This page does both: the quality report and NTIA minimum elements validate, and the searchable component table is the viewer.
Read next
- Guide
SBOM guide for the CRA: formats, minimum content and operations
CycloneDX versus SPDX, what a CRA-oriented SBOM must contain, which tools generate one per ecosystem, how to keep it current per release, how to share it, and how it feeds vulnerability handling and VEX.
- Guide
VEX vs SBOM: component inventory and exploitability context
A concise technical comparison of SBOM and VEX, how component matching leads to product-specific exploitability statements, and what each artifact can and cannot establish.
- Docs
SBOM ingestion
Upload, GitHub, GitLab, CI/CD and the API.
- Docs
CI/CD SBOM ingestion
GitHub Actions, GitLab CI, Jenkins, CircleCI examples.
- Docs
VEX
Per-product exploitability statements and signed CycloneDX VEX documents.