Analysis & detection
What is License Compliance?
Identifying the licences of your dependencies and flagging ones that conflict with your policy.
Every dependency carries licence obligations, and some, copyleft terms in particular, can impose requirements on how you distribute your own software. Licence scanning identifies each package's licence, usually via SPDX identifiers, and checks it against an allowlist or blocklist.
This is legal risk rather than security risk, which is why it tends to be a procurement or compliance requirement rather than an engineering one. It matters most when shipping software to customers rather than running it as a service.
Top 12 License Compliance tools
Every tool in the directory documented as supporting License Compliance, 11 fully, 1 partially, with what its own documentation says.
Support is not the same as parity, since some implementations are narrower in scope, gated to a higher plan tier, or maintained only for existing customers. The note under each tool is what its own documentation describes.
- 1
SPDX identification with allowlists, blocklists, category policies and license inventory reporting.
- 2AikidoCode Security Platform
SPDX identification, permitted/restricted/forbidden policies, org-wide enforcement, compliance reports
- 3Checkmarx OneCode Security Platform
Effective License designation, Full/Partial/No copyleft classification, license severity, and source-path evidence.
- 4CodeAnt AIPR Review
License compliance checking with risky-license identification as part of SCA
- 5
SCA captures per-dependency license; enforced via blocking rule; License Enforcement named at Growth
- 6
SPDX license identification, category rules and custom overrides across transitive dependencies; rides on SCA billing.
- 7GitHub Advanced SecurityCode Security PlatformFree on public repos; add-on: Code Security for private/internal
dependency review deny-licenses blocks disallowed licenses; open source license compliance policy across repos
- 8SemgrepCode Security Platform
License detection with policies to flag or block disallowed licenses; all SCA languages except Dart and Elixir.
- 9SnykCode Security Platform
SPDX-aligned catalog, default severities, OR/AND dual licenses, custom license policies, org Licenses tab.
- 10
License policy management and enforcement ships inside the separately subscribed SCA product.
- 11
License-risk ratings per component; policy rules block high-risk, non-OSS or unrecognized licenses
- 12
Only via a custom BUGBOT.md rule naming specific licenses; no native license policy engine
What to look for
- Whether policies can be configured per licence category and per repository
- Detection of transitive dependency licences, not just direct ones
- How dual-licensed and unlicensed packages are handled
- Whether a merge can be blocked on a policy violation
Related terms
FAQ
What is License Compliance?
Identifying the licences of your dependencies and flagging ones that conflict with your policy.
How many tools support License Compliance?
12 of the 20 tools tracked in this directory support License Compliance, 11 fully and 1 partially, including Codacy, Aikido, Checkmarx One, CodeAnt AI, Corgea. Support is not the same as parity, since some implementations are narrower in scope, gated to a higher plan tier, or maintained only for existing customers. The note under each tool is what its own documentation describes.
What should you look for in License Compliance?
Whether policies can be configured per licence category and per repository. Detection of transitive dependency licences, not just direct ones. How dual-licensed and unlicensed packages are handled. Whether a merge can be blocked on a policy violation.