Provenance
Where each component in your SBOM came from, and who stands behind it.
What it measures
Regulators and customers want to know who is responsible for every component you ship. The EU Cyber Resilience Act, NTIA minimum elements and BSI TR-03183-2 all require supplier information. SBOMBox reads the supplier, author and publisher fields on each component.
How it is scored
Provenance is one of the score categories. It is the average of four checks, each scored 0-10 by the share of components that pass:
- Supplier - components with a named supplier. Required by NTIA, CRA and BSI.
- Author - components with a declared author.
- Publisher - components with a declared publisher.
- Any provenance - components with at least one of the three.
Read your result
sbombox score sbom.json --format detailedThe provenance rows look like this:
Category Score Check Covered
provenance 5.0 supplier_coverage: 10.0 3/3
author_coverage: 0.0 0/3
publisher_coverage: 0.0 0/3
any_provenance: 10.0 3/3- Covered is how many components pass the check, out of all components.
- The category score is the average of the four checks: (10 + 0 + 0 + 10) / 4 = 5.0.
- In this example every component has a supplier, so the SBOM already meets the supplier requirement in NTIA, CRA and BSI. The 5.0 comes from the optional author and publisher fields, which most SBOM generators leave empty.
Improve it
- Suppliers first, because regulations require them. List the components without one:
sbombox list sbom.json --missing suppliers - Then authors and publishers, to raise the rest of the score:
sbombox list sbom.json --missing authors sbombox list sbom.json --missing publishers
sbombox fix does not fill in provenance: it cannot know who stands behind a component, so it never guesses. Add the values in your SBOM generator's configuration or from your vendor records, then score again. --missing provenance lists components with none of the three. See the CLI reference.