AIBOM vs SBOM Analyzer
Paste a CycloneDX bill of materials and see whether it is just an SBOM (code only) or a real AIBOM — and exactly what an AIBOM adds that an SBOM misses. Nothing is uploaded.
| SBOM | AIBOM | |
|---|---|---|
| Code libraries & versions | ✓ | ✓ |
| Code licenses | ✓ | ✓ |
| Known-vulnerability matching | ✓ | ✓ |
| Models (base, fine-tunes, adapters) | — | ✓ |
| Datasets (training / eval) | — | ✓ |
| Model & dataset licenses | — | ✓ |
| Model cards / provenance | — | ✓ |
Loading…
Sample report · illustrative data
Sample result: AIBOM vs SBOM verdict
Example run on a pasted CycloneDX file that lists three code libraries (transformers, torch and fastapi) and no models or datasets.
Verdict
- Result
- This is an SBOM, not an AIBOM
- Code components
- 3
- Models
- 0
- Datasets
- 0
- What it means
- Models and training data, the riskiest parts of an AI product, are unaccounted for
What each kind of bill of materials covers
| Item | SBOM | AIBOM |
|---|---|---|
| Code libraries and versions | Yes | Yes |
| Code licenses | Yes | Yes |
| Known-vulnerability matching | Yes | Yes |
| Models (base, fine-tunes, adapters) | No | Yes |
| Datasets (training and evaluation) | No | Yes |
| Model and dataset licenses | No | Yes |
| Model cards and provenance | No | Yes |
Made-up example data. Your own run uses your inputs. Downloads of the full report need Pro.
More security tools
The tools people use most on PlayCISO.
Catch injected instructions hiding in content your AI agent should only read.
Score your readiness against the first international standard for AI security threats.
Critical CVEs across 21 major vendors, month by month — and what the 2026 surge means.
Build an ordered ruleset, replay labelled packets and catch shadowed and any-to-any rules.
Self-assess all six Functions, from Govern to Recover, and see your weakest one.
Search 172 threat actors across Microsoft, CrowdStrike, Mandiant and community names.