A traditional SBOM inventories software components and their dependencies – libraries, versions, licences. The behaviour of an AI system, however, is largely determined by artefacts that this grid does not capture: the model itself, its weights, the training and evaluation datasets, and their provenance and preprocessing. A model can change fundamentally through retraining or fine-tuning without a single line of code or package version moving. An AI-SBOM therefore extends the inventory to include exactly these components – as a prerequisite for being able to assess the provenance, integrity and risks of an AI system at all.
Transparency for the AI supply chain
Why models, weights and training data belong in the bill of materials – and how CycloneDX ML-BOM and SPDX 3.0 make the AI supply chain documentable.
2established standard formats: CycloneDX ML-BOM and SPDX 3.0
~100malicious models identified on Hugging Face (JFrog, February 2024)
10OWASP Top 10: the AI supply chain as a dedicated risk (LLM03:2025 Supply Chain)
2027CRA main obligations (from 11 December)
AI systems consist of more than code: their behaviour is determined by models, model weights, training datasets and ML frameworks – artefacts that do not appear in a traditional software bill of materials (SBOM). At the same time, the AI supply chain is a real attack target, from tampered models on public model hubs to compromised framework dependencies. With CycloneDX ML-BOM and the AI and Dataset profiles of SPDX 3.0, two established standard formats now exist for inventorying these components in machine-readable form. In parallel, the Cyber Resilience Act and the AI Act are turning the documentation of components, datasets and pre-trained models into a regulatory obligation.
From specification to obligation
Five stages of the AI-SBOM — tap a milestone for details.
June 2023
CycloneDX 1.5 with ML-BOM
CycloneDX has supported the ML-BOM since version 1.5: the component types "machine-learning-model" and "data" place models and datasets on an equal footing with software libraries.
February 2024
JFrog findings on Hugging Face
JFrog identifies around 100 malicious models on Hugging Face whose payload executes when the model is loaded — made possible by the pickle format, which can execute arbitrary Python code during deserialisation.
April 2024
SPDX 3.0 with AI and Dataset profiles
SPDX 3.0 organises the second major SBOM format into modular profiles — including a dedicated AI profile and a Dataset profile for AI packages and datasets.
2 August 2025
GPAI obligations under the AI Act
Under Art. 53, providers of GPAI models must provide technical documentation, information for downstream providers and a sufficiently detailed summary of the training content.
11 September 2026
CRA reporting obligations
The reporting obligations of the Cyber Resilience Act apply from this date; the main obligations follow from 11 December 2027.
The Essentials at a Glance
Six topic blocks — tap to expand.
Format explorer: three routes to documented AI
CycloneDX ML-BOM, SPDX 3.0 and model cards side by side — tap a tab.
- The component types "machine-learning-model" and "data" place models and datasets on an equal footing with software libraries.
- A "modelCard" object documents intended use, limitations, biases, training parameters, datasets used, performance metrics and ethical considerations.
- First published as the international standard ECMA-424 in June 2024; the current 2nd edition (December 2025) corresponds to CycloneDX 1.7.
machine-learning-modeldatamodelCardECMA-424CycloneDX 1.7
- Organised into modular profiles since version 3.0 (April 2024, currently 3.0.1) — including a dedicated AI profile and a Dataset profile.
- The AI profile describes AI packages ("AIPackage") with model type, training information, energy consumption and a safety risk assessment; the Dataset profile documents datasets ("DatasetPackage") including sensitive information and known biases.
- A version 3.1 so far exists only as a release candidate — still at the draft stage.
AIPackageDatasetPackage3.0.1release candidate
- Standardised short documentation per model: intended use, evaluation results under different conditions — for example across demographic groups — and known limitations.
- Common practice on model hubs today, but mostly as free text without a binding schema.
- CycloneDX turns the concept into a machine-readable format with the "modelCard" field — usable for automated checks, procurement decisions and risk assessments.
Mitchell et al.modelCardmodel hubs
Standards & Sources
The content on this page is based on the following publicly available guides and studies.
ECMA-424: CycloneDX Bill of Materials Specification
International standardisation of CycloneDX; 1st edition June 2024, 2nd edition (December 2025) corresponds to CycloneDX 1.7 – ML-BOM capabilities since CycloneDX 1.5.
SPDX Specification v3.0.1
Defines the AI profile (AIPackage, energy consumption, safety risk assessment) and the Dataset profile (DatasetPackage) for AI components in SBOMs.
Model Cards for Model Reporting
Original publication of the model card concept, which CycloneDX adopted as the machine-readable modelCard field.
OWASP Top 10 for LLM Applications – LLM03:2025 Supply Chain
Describes supply chain risks from pre-trained models to LoRA adapters and explicitly recommends SBOM/AI-BOM inventories based on CycloneDX.
Verordnung (EU) 2024/2847 (Cyber Resilience Act)
SBOM obligation in Annex I Part II No. 1; reporting obligations from 11 September 2026, main obligations from 11 December 2027.
Verordnung (EU) 2024/1689 (AI Act)
Technical documentation for high-risk AI (Art. 11, Annex IV) and GPAI obligations including the training data summary (Art. 53, Annexes XI/XII), phased in from 2 August 2025/2 August 2026.
Do you know what is inside your AI systems?
If you would like to take a structured approach to building an AI-SBOM or meeting the documentation requirements of the CRA and the AI Act, feel free to contact us for a non-binding initial consultation.