Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Components of a version

The components page lists what the latest SBOM of a project version holds, vulnerable or not: to check that an SBOM arrived complete, read a component’s license, or confirm that a dependency is there. The steps are in Check what nanobom received.

Address

The Components tab of the project page opens /organizations/{organization}/projects/{project}/components, for the version the page shows. Any member of the organization can open it, as for the project page; another organization’s project, or an unknown version, is a 404.

Query parameterMeaningDefault
versionThe name of a project version; an empty version= names the unnamed versionThe latest version
nameOnly components whose name contains this text, namespace included, ignoring case (% and _ match themselves)Every name
showopen: components with at least one open finding (ignored and fixed ones do not count). unlicensed: components whose SBOM entry gives no licenseEvery component
pageThe page, from 11

The filter form and the page links keep the version and the filters; filtering goes back to the first page.

What it shows

Above the table: the number of components of the version, the components of its latest upload that had no package URL (not stored, so not listed, see Components without package URL), and how many components match the filters when there are any.

ColumnContent
ComponentThe name, with its namespace (org.apache.logging.log4j/log4j-core), and the package URL
VersionThe package URL’s version
EcosystemThe package URL type: npm, cargo, maven…
LicenseThe license expression of the SBOM, or None declared
Open findingsThe severity of the worst open finding and their number, linking to the finding when there is one, to the version’s findings otherwise; None without open findings
DependencyDirect when the SBOM lists it among the project’s own dependencies, Transitive otherwise, Not known when the SBOM does not say which components the project depends on directly (see Dependency paths)

Components with open findings come first, the most severe first, then every component by name and version. A page holds 100 components; asking for a page past the last shows the last.

When some links of the SBOM’s dependency graph could not be followed (components without a package URL, or a reference shared by several packages), the page says so: a direct dependency whose link was lost shows as Transitive.

The read API’s /components returns the same components as JSON, by package URL, without these filters.