Homeglossary

Open-Source License

An open-source license is a legal license that grants people defined rights to use, inspect, modify, and share software source code. It sets the conditions that make collaborative reuse lawful. The specific license determines obligations such as preserving notices, disclosing source code, or addressing patent rights.

What Is an Open-Source License?

An open-source license is a legal license that grants rights to use, inspect, modify, and share software source code. It enables collaborative reuse while setting conditions users must follow.

Software is protected by copyright when created. An open-source license gives advance permission to copy and distribute it under stated terms. Publicly posting code, including in a repository, does not create these permissions. Without a license, people may view code but usually cannot legally reuse it.

The Open Source Initiative lists licenses that meet its Open Source Definition. A valid license defines recipient rights and obligations when sharing code.

How Open-Source Licensing Works

Licensing creates a chain of permissions and conditions. Duties depend on the license and how software is used or distributed.

  1. The copyright holder chooses a license that matches the project's goals.
  2. The project publishes source code with the license text, copyright notices, and required notices.
  3. Users may run, copy, study, modify, and redistribute code within the license terms.
  4. When distributing original or modified code, users meet conditions such as retaining notices, providing source code, or using compatible terms.
  5. Contributors submit changes under project rules, which may include a contributor license agreement or developer certificate of origin.

Internal use often has fewer obligations than distribution. A company may modify components for its own systems without releasing changes, while customer distribution can trigger notice or source-code duties. AGPL can also set conditions when modified software is offered over a network.

Key Rights and Conditions in an Open-Source License

Most licenses include a copyright notice and permission grant. They address redistribution, modified versions, and combining code with other software. Many require attribution, license text, or notices so downstream users know the code's origin. Good source attribution practices help manage these duties.

Licenses commonly disclaim warranties and limit liability. Authors generally do not promise code is safe, fit for a purpose, or maintained. Apache-2.0 includes an express patent license and patent-retaliation clause, which can matter when contributors hold related patents.

Copyright permission is not trademark permission. A project may allow code reuse while restricting its name, logo, or branding. Contributor agreements can confirm contributors may submit code and grant the project needed rights.

Types of Open-Source Licenses: Permissive, Copyleft, and File-Level Copyleft

License types are often grouped by what happens when modified code is distributed. These categories are useful shortcuts, not substitutes for reading the license.

TypeSource-sharing requirementProprietary useExamples and typical fit
PermissiveUsually retain notices and license text. Modified source usually need not be published.Generally allowed, including in closed products.MIT, BSD, Apache-2.0. Often used for libraries and broad adoption.
Strong copyleftDistributed derivative works generally must provide corresponding source under the same license.Use is allowed, but distributing covered derivatives as closed source generally is not.GPL-3.0. AGPL-3.0 extends source-sharing expectations to certain network services.
Weak or file-level copyleftChanges to covered files or libraries must be shared, while separate code may sometimes use another license.Often possible with careful boundaries.LGPL-3.0 and MPL-2.0. Common when balancing sharing with adoption.
Public-domain-style dedicationTerms aim to waive rights broadly, subject to local law and fallback terms.Usually broadly allowed.CC0 and Unlicense. They are not interchangeable with OSI-approved software licenses.

Common Open-Source Licenses and What Makes Them Different

Comparing licenses requires more than comparing length. Patent terms, distribution methods, and component relationships can change the result.

LicensePractical distinctionKey obligations
MITShort, permissive, and widely understood.Include copyright and license notice in substantial copies.
BSD variantsPermissive licenses with variant-specific wording.Retain notices. The 3-clause version restricts endorsement using contributors' names.
Apache-2.0Permissive with an express patent grant.Retain notices, state significant changes, and preserve NOTICE content where required.
GPL-3.0Strong copyleft designed to keep distributed covered derivatives open.Provide corresponding source and license covered distributed works under GPL terms.
AGPL-3.0GPL-style copyleft that addresses network use.Offer corresponding source to users interacting with a modified covered program over a network.
LGPL-3.0Weaker copyleft for libraries, with complex linking considerations.Share covered library modifications and preserve users' ability to modify or replace the library.
MPL-2.0File-level copyleft, often easier to combine with proprietary files.Make source for modified MPL-covered files available when distributing them.

Open Source, Free Software, Source-Available, and Public Domain

These terms overlap but are not identical. Free software refers to user freedoms, not zero price. Open source emphasizes rights to inspect, modify, and redistribute code under an approved license. Software can be sold and still be open source.

Source-available software permits viewing source but may prohibit commercial use, modification, or redistribution, so it is not necessarily open source. Code with no license remains copyrighted, even on GitHub. Public-domain material has no enforceable copyright restrictions, or seeks to waive them, but effects vary across countries and it does not automatically provide structured license terms.

Why Open-Source Licenses Matter

Clear licensing supports sharing and commercial use by giving participants known rights and obligations.

  • Creators can encourage adoption while stating reuse terms.
  • Developers can inspect code for quality, security, and interoperability.
  • Businesses can use components commercially when they meet applicable terms.
  • Schools, nonprofits, and public bodies can adapt software instead of starting from scratch.
  • Organizations can reduce dependence on one vendor by retaining the ability to maintain or replace software.
  • Shared standards, including an OpenAPI specification, can help independently developed systems connect.

Practical Limits and Risks of Open-Source Software

Open source is not risk-free or maintenance-free. The license is only one part of responsible software use.

  • Compliance can be difficult with many direct and transitive dependencies.
  • Some licenses are incompatible when code is combined or distributed in certain ways.
  • Security fixes, updates, and maintenance remain the user's responsibility unless support is purchased.
  • Code provenance may be unclear, especially for copied snippets or unreviewed contributions.
  • Abandoned dependencies can create operational and security risk.
  • Copyleft obligations may not fit a planned closed-source distribution model.
  • Patent, export, privacy, and sector-specific requirements may need separate review.
  • Most licenses provide no warranty, service-level commitment, or indemnity.

How to Choose an Open-Source License for a Project

Start with the outcome you want for users, contributors, and commercial adopters. Established licenses are usually safer and easier to understand than custom wording.

  1. Identify whether your goal is maximum adoption, reciprocal sharing, or community governance.
  2. Decide whether proprietary reuse should be allowed.
  3. Consider whether an express patent grant matters to the project and contributors.
  4. Assess whether hosted or network use should trigger source-sharing obligations.
  5. Review dependency licenses and confirm compatibility with planned distribution.
  6. Select an established license from trusted resources such as Choose a License.
  7. Add the complete license text, copyright notices, and required notices to the repository.
  8. Document contribution rules before accepting substantial outside code.

A reusable library seeking broad commercial adoption may choose MIT or Apache-2.0. A community-maintained application whose maintainers want distributed improvements available may prefer GPL-3.0. The right choice depends on goals, not popularity.

Using Open-Source Code Responsibly

Teams should treat license compliance as routine engineering work, not a release-day task. This is practical guidance, not legal advice.

  • Keep an inventory of direct and transitive dependencies, versions, and licenses.
  • Read each dependency's license file, notices, and documentation rather than relying on a package label.
  • Retain required attribution, copyright statements, and notices in distributed products.
  • Check license compatibility before combining code or shipping a product.
  • Record file modifications when the license requires it.
  • Maintain a software bill of materials when appropriate for the product and customers.
  • Seek qualified legal advice when an issue creates material business, patent, or distribution risk.

Common Open-Source Licensing Mistakes

Many licensing problems come from assumptions rather than bad intent. Basic controls prevent most of them.

  • Publishing a repository with no license and assuming public visibility grants reuse rights.
  • Copying code snippets without knowing their source, license, or contributor history.
  • Deleting copyright notices or third-party acknowledgments during packaging.
  • Assuming every GitHub project is open source.
  • Mixing incompatible licenses without reviewing how components interact.
  • Overlooking transitive dependencies that enter through another package.
  • Confusing permission to use code with permission to use a project's trademark or logo.
  • Changing a project's license without confirming contributor rights allow the change.
Start Building
on Emergent today
Start Building