License Types – Copyleft vs. Permissive

This article is a term explanation of license types – including exam questions and tags.

In a Nutshell

• Copyleft: strict sharing obligations (GPL, AGPL, LGPL)
• Permissive: flexible use, also proprietary (MIT, Apache, BSD)

Concise Technical Description

Open-source licenses define the rights and obligations when using, modifying, and distributing software. Copyleft licenses such as the GPL require derived works to be published under the same license in order to preserve the freedom of the code. Permissive licenses such as the MIT license or Apache license, on the other hand, allow almost unrestricted use, even in proprietary projects, as long as 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 regulate use, modification, distribution of software
• Copyleft: strict sharing obligations, e.g. GPL, AGPL, LGPL
• Permissive: freely usable, also proprietary, e.g. MIT, Apache, BSD
• IHK relevance, project documentation must contain license types and compliance
• Practical relevance, choice of license determines integratability into commercial products
• Security aspect, clear licenses prevent legal risks
• Cost-effectiveness, Permissive reduces integration costs, Copyleft promotes open-source ecosystem
• Documentation obligation, list license types used in project report, use SPDX

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 form
8. Open-source governance in the enterprise
9. Security aspect: auditability and compliance
10. License checking 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 published under Copyleft (GPL-3.0). Any derived software must also be GPL-licensed. With MIT, the code could be used in proprietary projects as well.

Advantages and Disadvantages

Copyleft

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

• Restrictions when integrating into proprietary systems
• Legal complexity with license mixing

Permissive

• High flexibility, also for commercial use
• Few legal hurdles
• High acceptance in enterprises

• Risk of “code exploitation” without feedback to the community
• Less control over further development

Typical Exam Questions (with Short Answer)

1. Difference between Copyleft and Permissive? Copyleft requires sharing under the same license, Permissive allows proprietary use.
2. Examples of Copyleft licenses? GPL, AGPL.
3. Examples of Permissive licenses? MIT, Apache-2.0.
4. What is weak copyleft? License form like LGPL that enforces copyleft only for certain parts.
5. Why is license choice important for IHK projects? Determines legal validity and must be documented.
6. Risks of license incompatibility? Legal conflicts, non-compliant software, project failure.
7. Economic advantage of Permissive licenses? Easier integration into commercial products, lower legal costs.
8. Integrate Copyleft code safely into proprietary products? Clean separation via Weak Copyleft (LGPL), Dual-Licensing, or permissive alternatives.

Most Important Sources

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