CBOM Check
Semantic checks for CycloneDX 1.6 and 1.7 Cryptography Bills of Materials.
Loading Python engine (about 15 MB, cached after the first visit)…
Bulk mode: each CBOM is checked on its own. The ACVP report and previous CBOM apply to a single CBOM, so they are ignored here.
Try a sample: · · ·
Checks
CBOM_SCHEMA_INVALID: baseline CycloneDX 1.6 / 1.7 schema validationCBOM_ASSET_MISSING_CRYPTO_PROPERTIESCBOM_ASSETTYPE_IMPLAUSIBLE: heuristic, warning only; the modelling decision is yoursCBOM_NIST_LEVEL_ON_NON_ALGORITHM,CBOM_NIST_LEVEL_MISMATCHCBOM_PARAMETER_SET_NAME_INCOMPLETE,CBOM_NO_CLASSICAL_ALGORITHMSCBOM_SERIALNUMBER_NOT_REFRESHED,CBOM_TIMESTAMP_NOT_REFRESHEDACVP_ALGORITHM_NOT_IN_CBOM,CBOM_ALGORITHM_NOT_TESTED,ALGORITHM_NAME_MISMATCHCBOM_CERTIN_ELEMENT_MISSING: optional; CERT-In CBOM minimum elements (Technical Guidelines v2.0)CBOM_WEAK_ALGORITHM: optional; MD5, Triple DES, RSA below 2048 bits (errors), SHA-1 and DSA (warnings), per NIST SP 800-131A Rev. 2 and FIPS 186-5CBOM_CNSA2_NOT_ALLOWED,CBOM_CNSA2_TRANSITIONAL: optional; NSA CNSA 2.0 (AES-256, SHA-384/512, ML-KEM-1024, ML-DSA-87, LMS/XMSS; classical public-key algorithms only during the transition)
Limits
The assetType check is a heuristic; every other check is deterministic. It does not check inventory completeness, certificate contents, or whether an ACVP report is genuine; key sizes are only read from algorithm names and parameter-set identifiers. Self-run test vectors are not CAVP validation.
Reproducible results
The downloaded result names the SHA-256 of every input file and the checker version, so anyone can run the same files and get the same result. It is not a timestamp: for proof of when a CBOM passed, ActaSeal seals the result.
Privacy
The checker is Python running in your browser (Pyodide). Your files are read locally and
never sent anywhere. The same code runs as a CLI:
python cbom_check.py cbom.json --acvp report.json --baseline old.json --strict