License Types – Copyleft vs. Permissive

This article provides a definition of license types including exam questions and key tags.

In a Nutshell

• Copyleft: strict share-alike obligations (GPL, AGPL, LGPL)
• Permissive: flexible use, including proprietary projects (MIT, Apache, BSD)

Core Technical Overview

Open source licenses define rights and obligations around software use, modification, and distribution. Copyleft licenses like the GPL require derived works to be published under the same license, preserving the freedom of the code. Permissive licenses such as the MIT License or Apache License allow nearly unrestricted use, even in proprietary projects, provided copyright and license notices are retained. Both license types are standardized in the SPDX License List and are legally binding.

Exam-Relevant Key Points

• License types govern use, modification, and distribution of software
• Copyleft: strict share-alike obligations, e.g. GPL, AGPL, LGPL
• Permissive: freely usable, including proprietary work, e.g. MIT, Apache, BSD
• IHK relevance: project documentation must include license types and compliance details
• Practical impact: license choice determines compatibility with commercial products
• Security aspect: clear licenses prevent legal risk
• Cost-benefit: permissive licenses reduce integration costs; copyleft fosters the open source ecosystem
• Documentation requirement: list used license types in project reports; use SPDX identifiers

Core Components

1. Copyleft licenses (strong copyleft: GPL, AGPL)
2. Weak copyleft (LGPL, MPL)
3. Permissive licenses (MIT, BSD, Apache)
4. License texts and headers
5. SPDX-License-Identifier
6. License compatibility and conflicts
7. Dual-licensing as a special case
8. Open source governance in the enterprise
9. Security aspect: auditability and compliance
10. License scanning in CI/CD (scanners, SBOM)

Practical Example

// SPDX-License-Identifier: GPL-3.0-or-later
function calc(a, b) {
  return a + b
}

Explanation: This snippet is released under copyleft (GPL-3.0). Any derived software must also be GPL-licensed. Under the MIT License, the code could be used in proprietary projects.

Pros and Cons

Copyleft

• Ensures software remains free
• Encourages community contributions
• Clear rules against proprietary appropriation

• Restricts integration into proprietary systems
• Legal complexity when mixing licenses

Permissive

• High flexibility, including commercial use
• Minimal legal barriers
• Strong adoption in enterprises

• Risk of code exploitation without community contribution
• Less control over further development

Common Exam Questions (with Short Answers)

1. What is the difference between copyleft and permissive? Copyleft requires distribution under the same license; permissive allows proprietary use.
2. Give examples of copyleft licenses. GPL, AGPL.
3. Give examples of permissive licenses. MIT, Apache-2.0.
4. What is weak copyleft? A license form like LGPL that enforces copyleft obligations only for certain components.
5. Why is license choice important for IHK projects? It determines legal compliance and must be documented.
6. What are the risks of license incompatibility? Legal conflicts, non-compliant software, project failure.
7. What is the economic advantage of permissive licenses? Easier integration into commercial products; lower legal costs.
8. How can you safely integrate copyleft code into proprietary products? Use clean separation via weak copyleft (LGPL), dual-licensing, or permissive alternatives.

Key Resources

1. https://opensource.org/licenses
2. https://spdx.org/licenses/
3. https://www.gnu.org/licenses/licenses.html