Making sure that your project license is compatible with the licenses of its dependencies is never an easy task, but this is required for legal purposes. To automate this process and avoid mistakes, you can use License audit currently supported by several Qodana linters:
Maven and Gradle
npm and Yarn
This feature is available under the Ultimate Plus license and its trial version.
How it works
License audit collects information about project and dependency licenses using configuration files of dependency management tools and files containing license texts. Based on the information collected, it builds the dependency tree containing information about:
The project license
Licenses of project dependencies
Licenses of the dependencies invoked by project dependencies
This tree shows which dependency licenses are (in)compatible with your project license.
For example, a project is licensed under the Apache-2.0 license and uses three dependencies licensed under the MIT, GPL-2.0-only, and Apache-2.0 licenses. This table explains which dependency licenses are compatible with the project license.
Compatible with the project license
Depending on the location of license information, the Qodana for JVM linter performs a sequence of steps to find it. First of all, it searches for any license references in the
LICENSE.* files. Next, it scans through the
pom.xml file. If necessary, it then scans through dependency source files. Otherwise, the linter requests the
The Qodana for JS linter using npm reads information about project and dependency licenses using configuration files of package management tools. The Qodana for PHP linter also reads license information from the Composer configuration file.
After Qodana has finished analyzing your project, the results become available in the report.
Run License audit
To run License audit, enable the
Below are the
qodana.yaml configuration samples that tell Qodana to install project dependencies and enable License audit:
You can also extend these samples using configuration options described below.
You can use the
dependencyIgnores option to ignore a license of a specific dependency in your project:
Allow or prohibit dependency licenses
You can override the license matrix and specify the list of dependency licenses that are allowed or prohibited for a specific project license.
In this snippet, the
keys key accepts application licenses, and the
prohibited keys accept the lists of allowed and prohibited dependency licenses respectively. As a result, the
AGPL-3.0-only becomes compatible with the
AFL-2.0 project license, while the
Apache-1.0 dependency license becomes incompatible.
All keys from this sample can accept several values:
Override a dependency license
You can override a dependency license identifier. This can be useful when a dependency is dual-licensed, and you want to omit some license, or when the license name cannot be detected from the dependency sources correctly.
Using this sample, you can tell Qodana to detect only the
GPL-2.0-with-classpath-exception licenses for
jaxb-runtime version 2.3.1.
In this sample,
url is optional.
Create custom dependencies
If you want to include the dependency that should be mentioned in the report but is impossible to detect from the project sources, you can use the
customDependencies key to specify it:
To view license audit results, in the inspection report click thetab.
License audit inspection results are grouped into a dependency tree.
If applicable, you can expand a specific dependency to see its dependency tree.
Using, you can switch between all project dependencies and dependencies which licenses are incompatible with the project license.
Underyou can find the list of project licenses. Using , you can view the rules of license compatibility.
You can download the list of dependencies in various formats.