ARGUS · SBOM

An SBOM from every scan, with VEX to say what does not affect you.

ARGUS builds a software bill of materials on every scan, in CycloneDX 1.6 and SPDX 2.3, with versions, package URLs, licenses and hashes. It turns reachability into VEX, so you can tell a customer which CVEs do not affect you, and why.

Coverage

What you can export

Every scan produces an SBOM. Other BOM types appear when the scan finds something to put in them; empty ones are left out rather than padded.

  1. 01

    SBOM

    Name, version, package URL, license, scope and hashes for every component. CycloneDX 1.6 and SPDX 2.3, as JSON, XML, tag-value or CSV.

  2. 02

    VEX

    OpenVEX or CycloneDX VEX. Unreachable CVEs become not affected, with the evidence; reachable open ones stay affected.

  3. 03

    HBOM

    The infrastructure you deploy, from Terraform, Docker Compose, Dockerfiles and Kubernetes workloads.

  4. 04

    CBOM and QBOM (beta)

    The cryptography in your code with file and line locations, and the subset at risk from quantum computers, referencing FIPS 203, 204 and 205.

How it works

From scan to fix

  1. 01

    Scan once

    Every full scan builds the SBOM from your lockfiles.

  2. 02

    Compare versions

    See what was added, removed or upgraded between two BOMs.

  3. 03

    Add VEX

    Generate VEX from reachability, or import a supplier's VEX to suppress CVEs they declared not affected.

  4. 04

    Hand it over

    Export in the format your customer or regulator asks for.

Why teams use it

An SBOM that answers the next question

VEX from evidence

Not affected statements come from reachability evidence, not from someone typing them in.

Scan an SBOM you were given

Upload a vendor's CycloneDX or SPDX file and check it for vulnerable and malicious packages, without code access.

Ready for EU CRA and SSDF requests

BOMs sit alongside the compliance evidence packs buyers and regulators ask for.

Limits, stated plainly

What it does not do yet

We would rather you hear it here than find it in week two.

  • CBOM and QBOM are in beta. They are pattern-based inventories, not an exhaustive cryptography audit.
  • HBOM covers deployed infrastructure from config files, not physical hardware.
  • An AI bill of materials (AIBOM) is on the roadmap, not available yet.
  • The BOMs page is switched off by default; turn it on in settings.
FAQ

SBOM questions, answered

Straight answers about SBOM and how ARGUS does it. Updated 17 November 2026.

Still have questions? Contact us

What is an SBOM?

An SBOM (software bill of materials) is a machine-readable inventory of the components in a piece of software: each package, its version, supplier, license and relationships. It lets you answer "are we affected by this CVE?" in minutes. ARGUS generates one on every scan in CycloneDX 1.6 and SPDX 2.3.

Why do companies need an SBOM?

Buyers and regulators increasingly ask for one. US Executive Order 14028 made SBOMs part of federal software supply-chain requirements, and the EU Cyber Resilience Act requires manufacturers to draw one up. An SBOM also speeds up your own response when a new vulnerability is published.

Which SBOM formats does ARGUS support?

CycloneDX 1.6 and SPDX 2.3, exported as CycloneDX JSON or XML, SPDX JSON or tag-value, or CSV. You can also compare two BOMs to see what was added, removed or upgraded.

What is the difference between CycloneDX and SPDX?

Both are open standard SBOM formats. CycloneDX comes from OWASP and is security-focused, with native support for VEX and cryptography BOMs. SPDX comes from the Linux Foundation, grew out of license compliance and is published as ISO/IEC 5962. ARGUS exports both, so you can send whichever a customer asks for.

What is VEX and how does ARGUS create it?

VEX (Vulnerability Exploitability eXchange) states whether a product is actually affected by a known vulnerability. ARGUS generates OpenVEX or CycloneDX VEX from reachability: unreachable CVEs are marked not affected with the evidence, fixed ones fixed, and open reachable ones affected.

What is the difference between an SBOM and a CBOM?

An SBOM lists software components. A CBOM (cryptography bill of materials) lists the cryptographic algorithms the software uses. ARGUS builds a CBOM in beta when it detects cryptography, with file and line locations, plus a QBOM of the algorithms at risk from quantum computers.

What does HBOM mean in ARGUS?

In ARGUS, the HBOM describes the infrastructure you deploy, built from Terraform resources, Docker Compose, Dockerfile base images and Kubernetes workloads. It is not a physical hardware inventory, which is what HBOM means in some other contexts.

How do I generate an SBOM with ARGUS?

Connect a repository and run a scan. ARGUS builds the SBOM from your lockfiles automatically. Turn on the BOMs page in settings, then export in the format you need or generate VEX alongside it.

Can ARGUS scan an SBOM from a vendor?

Yes. Upload a CycloneDX or SPDX JSON file with package URLs and ARGUS checks it for known vulnerabilities and malicious packages, without access to the vendor's code. Checks that need source code are reported as not assessed.

Does ARGUS generate an AI bill of materials (AIBOM)?

Not yet. AIBOM is on the roadmap. Today ARGUS produces SBOM, VEX and HBOM, with CBOM and QBOM in beta.

Try it on one repository.

Connect a GitHub repo and see the findings, ranked, in your first scan.