What is the commercial risk of strong copyleft licenses like GPL and AGPL?

Strong copyleft licenses require any proprietary software that links or integrates with them to be released under the same open-source terms. AGPL additionally triggers this obligation over network/cloud interactions.

What are Permissive licenses?

Permissive licenses like MIT, Apache-2.0, BSD-2-Clause, and BSD-3-Clause grant unrestricted commercial reuse without requiring your proprietary source code to be disclosed.

Open Source License & Legal Compliance Analyzer

Analyze open source dependencies across your supply chain. Categorize licenses into Permissive, Weak Copyleft, and Viral Copyleft (GPL / AGPL). Evaluate commercial use readiness 100% offline.

DEPENDENCY LIST / CSV / PACKAGE.JSON 0 lines

AUDIT RESULTS & LEGAL RISK BREAKDOWN 0 packages evaluated

Package Name	License (SPDX)	Risk Category	Commercial Use Guidance
Paste a dependency license list or load a sample.

Frequently Asked Questions

What is the difference between Weak Copyleft and Strong Copyleft?

Weak copyleft (e.g. MPL-2.0, LGPL-3.0) requires source code changes to the library itself to be disclosed, but allows your surrounding application code to remain proprietary. Strong copyleft (e.g. GPL, AGPL) treats dynamic or static linking as creating a derivative work, requiring the whole project to be open-sourced.

How are SPDX dual-license expressions evaluated?

Expressions with OR (e.g. MIT OR GPL-2.0) allow you to choose the more permissive option (MIT). Expressions with AND require adhering to the terms of both licenses simultaneously.