What regulators ask for in an AI or software bill of materials
Three regulations now ask organisations shipping ML models to document what is inside them. Each guide below sets out what the text requires, when it applies, and which parts an AI BOM from AIsbom can give you evidence for, with every date and article cited to the primary source.
EU AI Act Article 53
Documentation duties for providers of general-purpose AI models. Applies since 2 August 2025; fines from 2 August 2026.
EU Cyber Resilience Act
24-hour vulnerability reporting since 11 September 2026. Machine-readable SBOM from 11 December 2027.
FDA section 524B
An SBOM in every premarket submission for a cyber device, since 29 March 2023.
What AIsbom does and doesn't do here
AIsbom reads model files (PyTorch, SafeTensors, GGUF and pickle variants) and the Python dependencies pinned beside them, and writes what it finds as CycloneDX 1.7 or SPDX, with optional VEX. That gives you evidence for the inventory, integrity, licence and exploitability parts of these regulations, for the ML side of your product.
It cannot see your policies, processes, risk assessments or evaluations, and those make up much of what each regulation asks for. Each guide says plainly which rows are out of scope.
Check a repository against all three
Connect a repo and the readiness view scores your latest scan against each framework and lists the gaps. Free on every plan.
Open the readiness view What is an AI BOM?Last reviewed 2026-10-31. These guides are general information, not legal advice. AIsbom reports what an SBOM contains. It does not assess or attest to anyone's regulatory status.