Skip to content
Go to platform

Understand job SBOM completeness

Use CRACI SBOM completeness to understand whether CRACI detected gaps while building a job’s SBOM.

CRACI considers a job’s SBOM complete when package detection finishes without a recorded degradation reason. Restoring caches, pulling OCI artifacts, and allowing unmatched, unmonitored traffic are degradation reasons.

The job view displays Complete CRACI SBOM for either complete status. For an incomplete or unavailable SBOM, its banner warns that packages may be missing or package detection did not finish. When the status is unknown or absent, no completeness banner is shown; absence does not mean the SBOM is complete.

The completeness statuses distinguish these conditions:

StatusMeaningComplete
CompletePackage detection finished without a recorded degradation reason.Yes
Complete with connectionsComplete under the same criteria, but network connections can allow packages to go undetected.Yes
IncompleteCRACI recorded a condition that could leave dependencies out of the SBOM.No
UnavailablePackage detection did not finish.No
Unknown or absentNo completeness result is available.No
  • Choose network rules deliberately. Prefer supported package sources over passthrough connections. Restrict a necessary connection’s destinations and ports, and verify it cannot supply unobserved dependencies.
  • Do not treat complete as a guarantee. Review package detection coverage before treating a job SBOM as a release inventory.

See Control network access from jobs for source coverage and policy behavior.