Review Builds
Open Builds when you need history for an SCM-backed project's analyzed CI runs, or when you need reports for a commit that is not the project's default-branch summary.
A Build is an analyzed CI pipeline run for a connected SCM-backed project. One Build can include multiple SBOMs from the same run. Generic projects do not use Builds; they continue to show the latest uploaded SBOM data.
Open the Builds list
- Organization Builds — In the organization sidebar, Builds lists every Build across projects, with project, status, source, commit, SBOM count, vulnerability count, and start time. Filter by status or source. Open a row to enter that Build's hub, or download the Build's SBOMs as a zip.
- Project Builds — Inside an SCM-backed project, Builds lists that project's history. You can also filter by git ref. Generic projects hide the Builds navigation item.
Use the Build hub
Each Build has a hub with:
- Summary — Vulnerability and license compliance status for that Build, plus Build Comparison against the previous completed Build on the same ref (and, for non-default refs, against a default-branch baseline).
- SBOMs, Vulnerabilities, and Licenses — The exact reports for that Build.
How project report pages relate to Builds
For SCM-backed projects, the project overview and project-level SBOMs, Vulnerabilities, and License compliance pages pin to the latest complete Build on the project's default branch. Until that Build exists:
- The project shows an empty state that points you to finish CI setup, run a pipeline on the default branch, or open build history.
- Feature-branch Builds can still appear under Builds, but they do not replace the default-branch summaries on the project report pages.
Organization-level SBOMs, Vulnerabilities, Components, and License compliance remain organization-wide roll-ups and are not scoped to a single Build.