How licenses are classified
Each license is sorted into an obligation-based category by keyword matching on the recorded license name:
Those categories roll up into a risk signal you can filter by:
- Low — permissive licenses; typically just attribution.
- Review — weak-copyleft obligations (LGPL/MPL-style) to review before release.
- Restrictive — the strongest obligations: strong and network copyleft (GPL/AGPL-style).
- Unverified — license is unknown and should be clarified.
This classification is informational, not legal advice. It is derived from the
license name to help you find and review obligations, so compound or non-standard
strings may classify imprecisely. Confirm those against the package’s actual
terms. Where Supply Chain Intel is enabled, you can configure a separate
pull request rule
that matches license metadata.
Working with licenses
Open Assets → Repositories, select a repository, and go to Inventory → Licenses. The summary groups the detected licenses by obligation. Expand a license to review the packages that declare it.- Filter by risk to focus on the obligations that matter to your policy.
- Search by license identifier, for example
GPL-3.0-onlyorSSPL. - Select the branch to review the license data for its latest inventory.