Review license findings
Open License compliance when you need to see which licenses and components conflict with your organization's license policy, either across the organization or for one project.
Review the organization roll-up
- Open License compliance in the organization sidebar.
- Use the summary cards for violation counts, how licenses break down against policy (allowed, denied, or mixed when project overrides disagree), and whether organization license enforcement is active.
- Use the licenses table to see each license's policy status, how many projects use it, occurrence and component counts, and first and last seen times.
- Select a license name to open a detail page with policy context, metrics, and the component findings for that license.
- On the detail page, use Edit policy to jump to Settings → License Compliance.
Organization-level findings use:
- The latest complete default-branch scan for each enabled GitHub or GitLab project
- Complete SBOM uploads linked to those projects
- The latest complete uploaded SBOM for each enabled Generic project
- Complete organization-level manual uploads that are not tied to a project
Review one project
- Open the project and then License compliance.
- Use File path to locate the component in source when the finding comes from a git-ref scan, or to read an image reference for Docker SBOMs. Uploaded SBOMs show File path as text.
Project findings use:
- GitHub and GitLab views use the selected build and also include complete SBOM uploads linked to that project alongside the latest default-branch scan results.
- Generic projects use the latest uploaded SBOM data.
Findings reflect the effective policy for that project: the organization default, or a project override when one is active.
Change the policy these findings use
Organization defaults live under Settings → License Compliance. To use different rules per project, open that project's Settings → License Compliance page.
See Set license policy for the override steps.