Turn SBOMs into
supply-chain decisions
The local-first Rust CLI for SBOM, CBOM, and AI BOM intelligence
Diff CycloneDX & SPDX, catch OSV and KEV vulnerabilities, and assess readiness against NTIA, CRA, and PQC — in seconds, right inside your CI
brew install sbom-tool/tap/sbom-toolsfeatures
SBOM, CBOM, and AI BOM analysis
Compare inventories, assess quality, and investigate software and cryptographic risk
Semantic Diffing
Component-level change detection with version diffs, vulnerability tracking, and license delta analysis.
Illustrative output
+ pkg:npm/zod@3.23.8
- pkg:npm/body-parser@1.20.2
~ lodash 4.17.20 → 4.17.21
Vulnerability & EOL Enrichment
OSV/KEV vulnerability tracking, end-of-life detection, and typosquat flagging.
Illustrative output
✗ CVE-2024-29041 (HIGH)
express <4.19.2 — resolved
⚠ EOL: python 2.7 (2020-01-01)
⚠ Typosquat: lod-ash → lodash?
Multi-Format Support
CycloneDX 1.4–1.7 JSON/XML; SPDX 2.2/2.3 JSON, tag-value and RDF/XML; SPDX 3.0/3.0.1 JSON-LD, including AI and Dataset profiles
Illustrative output
Quality & Compliance
Score SBOMs against NTIA, FDA, CRA, NIST SSDF, and EO 14028 standards with 6 scoring profiles.
Illustrative output
Fuzzy Matching
Multi-tier matching with PURL, alias lookup, ecosystem normalization, and string similarity.
Illustrative output
matching…
✓ PURL exact → 89 matched
~ Fuzzy → 12 resolved
? Unmatched → 3 remaining
Multiple Outputs
JSON, SARIF, HTML, Markdown, CSV, table, side-by-side, summary, and interactive TUI.
Illustrative output
screenshots
See it in action
Diff, view, and score your BOMs in the terminal
how it works
How It Works
From BOM files to reviewable changes and reports
- Step 1
Input
CycloneDX or SPDX files
- JSON
- XML
- SPDX tag-value
- RDF
- Step 2
Analyze & Diff
Semantic comparison engine
- Fuzzy Match
- Vuln Enrich
- Graph Diff
- Scoring
- Step 3
Report
Reports and interactive review
- JSON
- SARIF
- HTML
- TUI
quick start
Quick Start
Get up and running in seconds
# Compare two SBOMs
$ sbom-tools diff old.json new.json --enrich-vulns# View interactively
$ sbom-tools view sbom.json# Check SBOM requirements
$ sbom-tools validate sbom.json --standard ntia,cra# Assess quality
$ sbom-tools quality sbom.json --profile security --recommendations# Score CBOM crypto health
$ sbom-tools quality cbom.json --profile cbom# View CBOM inventory
$ sbom-tools view cbom.json --bom-type cbom# Search across SBOMs
$ sbom-tools query "log4j" --version "<2.17.0" fleet/*.json# Fleet comparison
$ sbom-tools diff-multi baseline.json target1.json target2.json# Shell completions
$ sbom-tools completions bash > ~/.local/share/bash-completion/completions/sbom-toolsExample diff output:
SBOM Diff: old-sbom.json → new-sbom.json Components: 142 → 145 (+5 added, -2 removed, ~3 modified) + pkg:npm/express@4.19.2 (added) + pkg:npm/zod@3.23.8 (added) - pkg:npm/body-parser@1.20.2 (removed) ~ pkg:npm/lodash@4.17.20 → 4.17.21 (version bump) ~ pkg:npm/axios@1.6.0 → 1.7.4 (version bump) Vulnerabilities: ✗ CVE-2024-29041 (HIGH) — express <4.19.2 [resolved] ✗ CVE-2024-4068 (HIGH) — braces <3.0.3 [new] License changes: none
query & fleet
Query & Fleet
Search across SBOMs and compare entire portfolios
Find vulnerable components across your entire SBOM fleet
$ sbom-tools query "log4j" --version "<2.17.0" fleet/*.cdx.json Query: "log4j" AND version=<2.17.0 across 5 SBOMs (1247 total components) COMPONENT VERSION ECOSYSTEM LICENSE VULNS FOUND IN log4j 2.14.0 maven Apache-2.0 1 firmware-v1, device-a log4j 2.14.1 maven Apache-2.0 1 gateway 2 components found across 5 SBOMs
ci/cd
CI/CD Integration
Gate deployments on SBOM changes, vulnerabilities, or quality regressions
Official GitHub Action — diff, validate, and gate SBOMs directly in your workflows.
.github/workflows/sbom-check.yml
name: SBOM Check
on:
pull_request:
paths: ['sbom.json']
permissions:
contents: read
security-events: write
jobs:
sbom-diff:
# Code-scanning writes are unavailable to fork pull requests.
if: github.event.pull_request.head.repo.full_name == github.repository
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
with:
fetch-depth: 0
ref: ${{ github.event.pull_request.head.sha }}
- name: Extract PR base SBOM
env:
BASE_SHA: ${{ github.event.pull_request.base.sha }}
run: |
# Fail clearly if the baseline file is absent; do not compare to an empty BOM.
git show "$BASE_SHA:sbom.json" > old-sbom.json
- name: Diff SBOM
uses: sbom-tool/sbom-tools-action@c73f5ccd0e22e0797e1647d8abd57ba59e407472 # v1.2.0
with:
version: '0.3.0'
command: diff
args: old-sbom.json sbom.json
fail-on-vuln: true
enrich-vulns: true
output-format: sarif
output-file: results.sarif
- name: Upload SARIF
if: always() && hashFiles('results.sarif') != ''
uses: github/codeql-action/upload-sarif@v3
with:
sarif_file: results.sarifDiff exit codes (v0.3.0)
These codes apply to diff policy flags; other commands differ. Code 2 can also signal invalid command usage. Workflows compare the PR head to its base SHA, require an existing base SBOM, and skip forks because SARIF write permissions are restricted.
trust
Supply Chain Trust
We practice what we preach — every release is transparent, attested, and signed
Sigstore Signing
Keyless signatures on all release archives — verify authenticity without managing keys.
View ReleasesBuild Attestations
GitHub build attestations provide per-binary cryptographic proof of provenance.
View AttestationsDual-Format SBOMs
CycloneDX 1.6 + SPDX 2.3 SBOMs published alongside release archives.
Download & VerifyEvery release is built in GitHub Actions with provenance attestations and keyless Sigstore signatures. How to verify a release →