Getting Started with Snyk License Compliance Management
Feature availability
This feature is available with Enterprise plans. See pricing plans for more details.
Get started with Snyk license compliance management, to check compliance for the open source licenses in your code.
The Snyk Default License Policy defines how Snyk identifies potential license issues in the open-source packages your Projects are using. This policy applies to all Organizations created in your Group.
Ensure you have:
To take effective action based on license issues, you need to define policies defining these actions, based on license types. Policies provide a way to capture different requirements within an Organization, based on factors such as line of business. Work with your legal team to create policies that are specific to your company.
To open your Snyk Group default license policy, select the Policies menu option in your Group:
Access Group policies
Each policy contains rules, detailing which licenses are acceptable and which are forbidden for use, together with a severity level that indicates how severe the license violation is. For example, severity levels for internal-only license issues may be less severe than for those released externally.
You can create and edit multiple license policies for Organizations. See Create a license policy and rules for details.
Snyk’s Git-based integrations support license scanning as part of the regular workflow. During scanning, license issues appear as a filterable list in the Issues tab:
Issues overview within a dependency project
This example shows a high-severity issue for a GPL-2.0 license, with accompanying instructions as defined in the policies for that license.
You can also view license issues using the Snyk CLI tool, after running snyk test:
License issue overview in Snyk CLI
View dependencies
Snyk shows license issues in both your direct and transitive dependencies, in the Dependencies tab:
Dependencies overview within a dependency project
Click the tree icon (
) to view a full dependency tree. This shows the dependency that introduced the license issue:
Dependencies overview - tree view
You can view and share detailed lists of licenses being used by all Projects in your Organization, and see a report that lists all the Open Source components and licenses along with copyright information.
You can now take action to resolve the license issues identified during the scan, to help you build and deploy your application without outstanding licensing issues.
The actions you take depend on the license conditions and on your policies. For example, if a license violation is surfaced, this issue can be mitigated by either approaching your legal team or by replacing the dependency which added the violation.
Last modified 11d ago