BertBaseUncased 1.0AI model2 componentsFormat: CycloneDXProfile: default
| Cluster | Present | Gap | Review | Total |
|---|---|---|---|---|
| Metadata | 9 | 1 | 0 | 10 |
| System Level Properties | 3 | 2 | 4 | 9 |
| Models | 12 | 2 | 0 | 14 |
| Datasets Properties | 8 | 0 | 2 | 10 |
| Infrastructure | 0 | 2 | 0 | 2 |
| Security Properties | 0 | 1 | 3 | 4 |
| Key Performance Indicators | 0 | 1 | 1 | 2 |
| Total | 32 | 9 | 10 | 51 |
| Framework | Present | Gap | Failed | Review | Total |
|---|---|---|---|---|---|
| EU AI Act — Annex IV technical documentation | 7 | 7 | 0 | 9 | 23 |
| AI Framework Act (Korea) | 1 | 2 | 0 | 7 | 10 |
| BSI TR-03183-2 — SBOM data fields (EU CRA) | 7 | 1 | 0 | 6 | 14 |
| US SBOM minimum elements | 16 | 3 | 0 | 4 | 23 |
BomLens does not certify or determine compliance with the EU AI Act, the Korean AI Framework Act, the EU Cyber Resilience Act, or any other regulation. This crosswalk covers only the documentation elements an SBOM can carry; obligations that an SBOM cannot express — bias and fairness assessment, risk management, human oversight — are out of its scope and must be met through separate documents. It makes documentation gaps visible so a person can prepare; interpreting it against a specific product's legal obligations is a person's job.
| # | Status | Requirement | Required | Detail | Evidence / how |
|---|---|---|---|---|---|
| Can be fixed4 | |||||
| 16 | Warn | SHA-512 checksum coverage (>= 80%, recommended) | no | 0% (0/2) | |
| 22 | Warn | SBOM author signature | no | not present in the SBOM | What to establishA signature carried inside the document, or a detached one sitting next to the SBOM as <sbom-filename>.sig (cosign's own convention, e.g. from --sign), is detected automatically and this row will say so. A detached signature under a different name or location is not visible here, because this report only looks for that one convention. Verify it against the sender's key before treating the contents as theirs, and record that you did. A signature carried inside the document, or a detached one sitting next to the SBOM as <sbom-filename>.sig (cosign's own convention, e.g. from --sign), is detected automatically and this row will say so. A detached signature under a different name or location is not visible here, because this report only looks for that one convention. Verify it against the sender's key before treating the contents as theirs, and record that you did. |
| 33 | Warn | Component identifiers | no | 2/3 component(s) | pkg:huggingface/google-bert/bert-base-uncased@86b5e093 |
| 35 | Warn | Component hash value | no | 2/3 component(s) | How to fill this |
| Needs a person4 | |||||
| 39 | Review | Coverage | no | requires human review (no automated source) | What to establishEstablish that the SBOM lists every component making up the software, transitive dependencies included. No tool can confirm this from the document alone — the document cannot show what was left out of it. Compare it against the build's own dependency resolution, or against the manifests the software is built from. Establish that the SBOM lists every component making up the software, transitive dependencies included. No tool can confirm this from the document alone — the document cannot show what was left out of it. Compare it against the build's own dependency resolution, or against the manifests the software is built from. |
| 40 | Review | Accommodation of updates to SBOM data | no | requires human review (no automated source) | What to establishEstablish that there is a way to correct SBOM data after it has been published, and that corrections go out promptly. This is a practice of the organisation issuing the SBOM, not a field in it. Establish that there is a way to correct SBOM data after it has been published, and that corrections go out promptly. This is a practice of the organisation issuing the SBOM, not a field in it. |
| 41 | Review | Distribution and delivery | no | requires human review (no automated source) | What to establishEstablish that whoever needs the SBOM can get it promptly, and that any access control keeps unauthorized parties out without blocking authorized ones or preventing the data from being loaded into their security tools. Establish that whoever needs the SBOM can get it promptly, and that any access control keeps unauthorized parties out without blocking authorized ones or preventing the data from being loaded into their security tools. |
| 43 | Review | Frequency | no | requires human review (no automated source) | What to establishEstablish that each software version or update has an SBOM of its own, and that a revised SBOM is issued when the component data changes or an error in it is found. Establish that each software version or update has an SBOM of its own, and that a revised SBOM is issued when the component data changes or an error in it is found. |
| Not applicable11 | |||||
| 5 | N/A | Component name+version coverage (100%) | yes | no packages to measure | |
| 6 | N/A | PURL coverage (>= 90%) | yes | no packages to measure | |
| 7 | N/A | File component identifier coverage (hash, >= 80%, recommended) | no | no file components | |
| 10 | N/A | PURL namespace where the type requires it (pkg:maven/<groupId>/name) | yes | no identifiers of a type that requires a namespace | |
| 11 | N/A | PURL namespace for golang/huggingface (advisory) | no | no identifiers of a type that requires a namespace | |
| 17 | N/A | Component creator coverage (>= 80%, recommended) | no | no packages to measure | |
| 18 | N/A | Component filename coverage (>= 80%, recommended) | no | no packages to measure | |
| 19 | N/A | Source or distribution URI coverage (>= 80%, recommended) | no | no packages to measure | |
| 20 | N/A | Delivered-file properties (executable/archive/structured) | no | no packages to measure | |
| 44 | N/A | PURL namespace of rpm/deb/apk is a distribution id (advisory) | no | no rpm, deb or apk identifiers with a namespace | |
| 46 | N/A | PURL resolves in its repository (advisory) | no | repository lookup not run | |
| Met27 | |||||
| 1 | Pass | Spec version (CycloneDX 1.3/1.4/1.5/1.6/1.7) | yes | CycloneDX 1.7 | |
| 2 | Pass | Timestamp (metadata.timestamp) | yes | 2026-11-22T02:23:25+00:00 | |
| 3 | Pass | Tool info (metadata.tools) | yes | 2 tool(s) | |
| 4 | Pass | Top-level component name+version | yes | bert-base-uncased@86b5e093 | |
| 8 | Pass | Traceable PURL (no pkg:generic, advisory) | no | 0 untraceable | |
| 9 | Pass | PURL syntax (pkg:type/[namespace/]name) | yes | 0 malformed | |
| 12 | Pass | PURL type defined by purl-spec (advisory) | no | 0 undefined type(s) | |
| 13 | Pass | Transitive dependencies (graph edges) | yes | 2 edge(s), graph completeness unknown (no positive evidence found, not a defect) | |
| 14 | Pass | License coverage (>= 80%, recommended) | no | 100% (2/2) | |
| 15 | Pass | Hash coverage (>= 50%, recommended) | no | 50% (1/2) | |
| 21 | Pass | SBOM author | no | present | |
| 23 | Pass | SBOM data format name | no | present | |
| 24 | Pass | SBOM data format version | no | present | |
| 25 | Pass | SBOM generation context | no | present | |
| 26 | Pass | SBOM timestamp | no | present | |
| 27 | Pass | SBOM tool name | no | present | |
| 28 | Pass | SBOM tool version | no | present | |
| 29 | Pass | SBOM version | no | present | |
| 30 | Pass | Component name | no | 3/3 component(s) | |
| 31 | Pass | Component version | no | 3/3 component(s) | |
| 32 | Pass | Component producer | no | 3/3 component(s) | |
| 34 | Pass | Component license | no | 3/3 component(s) | |
| 36 | Pass | Component hash algorithm | no | 3/3 component(s) | |
| 37 | Pass | Component dependency relationship | no | present | |
| 38 | Pass | Machine-processable data | no | present | |
| 42 | Pass | Explicitly identifying unknown information | no | present | |
| 45 | Pass | Component version is a plain version string (advisory) | no | 0 malformed version(s) (whitespace, "key: value" shape, control character or over 128 characters) | |
| # | Status | Requirement | Detail | Evidence / how |
|---|---|---|---|---|
| Can be fixed9 | ||||
| 5 | Warn | SBOM author signature | not present in the SBOM | How to fill this |
| 11 | Warn | System name | not present in the SBOM | |
| 13 | Warn | System producer | not present in the SBOM | |
| 25 | Warn | Model description | 0/1 model component(s) | How to fill this |
| 29 | Warn | Model input-output properties | 0/1 model component(s) | How to fill this |
| 44 | Warn | Infrastructure software (dependencies) | not present in the SBOM | |
| 45 | Warn | Infrastructure hardware (HBOM link) | not present in the SBOM | How to fill this |
| 49 | Warn | Vulnerability referencing | not present in the SBOM | |
| 51 | Warn | Operational performance KPIs | not present in the SBOM | |
| Needs a person10 | ||||
| 16 | Review | System data flow | requires human review (no automated source) | What to establishDescribe how data moves through the system: where an input comes from, what the model receives, and where its output goes. In BomLens, declare it with the service in the AI declaration (service.dataFlows: the direction, a classification, and the source and destination addresses); the next scan writes it to the SBOM as CycloneDX services[].data, marked as the publisher's declaration. An SBOM from another tool counts when its services carry serviceData. Confirm the description matches how the system is actually deployed. Describe how data moves through the system: where an input comes from, what the model receives, and where its output goes. In BomLens, declare it with the service in the AI declaration (service.dataFlows: the direction, a classification, and the source and destination addresses); the next scan writes it to the SBOM as CycloneDX services[].data, marked as the publisher's declaration. An SBOM from another tool counts when its services carry serviceData. Confirm the description matches how the system is actually deployed. |
| 17 | Review | System data usage | requires human review (no automated source) | What to establishState what the system does with the data it receives: whether it is stored, passed to another component, or used for further training. In BomLens, write it as the description of each data flow of the declared service (service.dataFlows[].description); the next scan writes it to the SBOM, marked as the publisher's declaration. Check this against the privacy notice you publish. State what the system does with the data it receives: whether it is stored, passed to another component, or used for further training. In BomLens, write it as the description of each data flow of the declared service (service.dataFlows[].description); the next scan writes it to the SBOM, marked as the publisher's declaration. Check this against the privacy notice you publish. |
| 18 | Review | System input/output properties | requires human review (no automated source) | What to establishDescribe the input and output the system accepts and produces: formats, size limits, and anything it refuses. In BomLens, declare the service's input and output kinds (service.inputModality, service.outputModality); the next scan records them on the service, marked as the publisher's declaration. A person confirms the rest, because a model card lists modalities, not the system's actual interface. Describe the input and output the system accepts and produces: formats, size limits, and anything it refuses. In BomLens, declare the service's input and output kinds (service.inputModality, service.outputModality); the next scan records them on the service, marked as the publisher's declaration. A person confirms the rest, because a model card lists modalities, not the system's actual interface. |
| 19 | Review | Intended application area | requires human review (no automated source) | What to establishState the field the system is intended for and the uses that are out of scope. This is a decision, not a fact a tool can read, and regulators ask for it directly. In BomLens, declare the service's field and what it is for (service.domain, service.informationAboutApplication); the next scan records them on the service, marked as the publisher's declaration. State the field the system is intended for and the uses that are out of scope. This is a decision, not a fact a tool can read, and regulators ask for it directly. In BomLens, declare the service's field and what it is for (service.domain, service.informationAboutApplication); the next scan records them on the service, marked as the publisher's declaration. |
| 40 | Review | Dataset statistical properties | requires human review (no automated source) | What to establishGive the size and shape of the training data — record counts, class balance, and any known skew. These numbers explain the model's limits, so state them even when they are unflattering. Give the size and shape of the training data — record counts, class balance, and any known skew. These numbers explain the model's limits, so state them even when they are unflattering. |
| 41 | Review | Dataset sensitivity (PII/copyright) | requires human review (no automated source) | What to establishJudge whether the training data holds personal information or third-party copyrighted work, and record what you filtered out and how. Where the answer is unclear, take it to your privacy and legal contacts before release. Judge whether the training data holds personal information or third-party copyrighted work, and record what you filtered out and how. Where the answer is unclear, take it to your privacy and legal contacts before release. |
| 46 | Review | Security controls | requires human review (no automated source) | What to establishList the controls that protect the model and its data — who can reach the weights, how the training environment is isolated, how artefacts are signed. These live in your operations, not in the SBOM. List the controls that protect the model and its data — who can reach the weights, how the training environment is isolated, how artefacts are signed. These live in your operations, not in the SBOM. |
| 47 | Review | Security compliance | requires human review (no automated source) | What to establishName the security standard or internal policy this model was built under, and who signed off. Point at the assessment record rather than restating it here. Name the security standard or internal policy this model was built under, and who signed off. Point at the assessment record rather than restating it here. |
| 48 | Review | Cybersecurity policy information | requires human review (no automated source) | What to establishGive the route for reporting a vulnerability in this model and who answers it. A published model needs a contact that outlives the person who trained it. Give the route for reporting a vulnerability in this model and who answers it. A published model needs a contact that outlives the person who trained it. |
| 50 | Review | Security metrics | requires human review (no automated source) | What to establishRecord what you measured on the security side — adversarial or jailbreak testing, refusal rates, red-team results — with the method and the date. If nothing was measured, say so plainly. Record what you measured on the security side — adversarial or jailbreak testing, refusal rates, red-team results — with the method and the date. If nothing was measured, say so plainly. |
| Met32 | ||||
| 1 | Pass | SBOM author | present | |
| 2 | Pass | SBOM version | present | |
| 3 | Pass | SBOM data format name | present | |
| 4 | Pass | SBOM data format version | present | |
| 6 | Pass | SBOM tool name | present | |
| 7 | Pass | SBOM tool version | present | |
| 8 | Pass | SBOM generation context | present, also read from metadata.lifecycles | |
| 9 | Pass | SBOM timestamp | present | |
| 10 | Pass | SBOM dependency relationship | present | |
| 12 | Pass | System components | present | |
| 14 | Pass | System version | present | |
| 15 | Pass | System timestamp | present | |
| 20 | Pass | Model name | 1/1 model component(s) | |
| 21 | Pass | Model identifier | 1/1 model component(s) | pkg:huggingface/google-bert/bert-base-uncased@86b5e093 |
| 22 | Pass | Model version | 1/1 model component(s) | |
| 23 | Pass | Model timestamp | 1/1 model component(s) | |
| 24 | Pass | Model producer | 1/1 model component(s) | |
| 26 | Pass | Model hash value | 1/1 model component(s) | |
| 27 | Pass | Model hash algorithm | 1/1 model component(s) | SHA-256 |
| 28 | Pass | Model properties (model card) | 1/1 model component(s) | bert |
| 30 | Pass | Model training properties | 1/1 model component(s) | |
| 31 | Pass | Model license | 1/1 model component(s) | Apache-2.0 |
| 32 | Pass | Model license — openness (weight/architecture/data/training) | present | open-architectureopen-dataopen-weightand 4 moreopenness:architecture=open-architecture, openness:training-data=open-data, openness:training=undisclosed, openness:weights=open-weightopenness:architecture=open-architecture, openness:training-data=open-data, openness:training=undisclosed, openness:weights=open-weight |
| 33 | Pass | Model external references | 1/1 model component(s) | |
| 34 | Pass | Dataset name | present | bookcorpuswikipedia |
| 35 | Pass | Dataset description | present | |
| 36 | Pass | Dataset content | present | |
| 37 | Pass | Dataset identifier | present | |
| 38 | Pass | Dataset hash | present | |
| 39 | Pass | Dataset provenance | present | |
| 42 | Pass | Dataset dependency relationship | present | |
| 43 | Pass | Dataset license | present | |