OOmnistu

Blog / Startup Guides

Startup Guides

Open source licenses explained: MIT, GPL, Apache and what no license means

What an open source license actually grants, how MIT, Apache 2.0, GPL and AGPL differ, and what it means when a project has no license at all.

OOmnistu
Reviewed 2026-11-20 · 4 min read

Every open source project you depend on comes with a license, and the license is the whole reason you may use it: open source licenses grant permission to use, modify and share software for any purpose, subject to conditions that preserve its provenance and openness. Choose a License, the GitHub-maintained guide, puts the stakes plainly - businesses and savvy developers won't touch a project without this protection. Here is how the main licenses differ.

No license means no permission

A project with no license offers no explicit permission to use, modify or share anything in it, and without that protection businesses and savvy developers won't touch it. If a dependency you need has no license, the guide's advice is simple: ask its maintainers to add one.

The permissive end: MIT, Apache 2.0, the Unlicense

At the simple end sit the permissive licenses. MIT is short and to the point: do almost anything with the code, including shipping closed-source versions, as long as you preserve the copyright and license notice. Apache 2.0 works the same way but adds an express grant of patent rights from contributors and asks you to state changes. The Unlicense goes further and dedicates the work to the public domain with no conditions at all.

The copyleft end: GPL, LGPL, MPL, AGPL

Copyleft licenses add conditions that keep improvements open when software is distributed. The GNU GPLv3 lets people do almost anything with the code, but if you convey a modified work, or a larger work built on the Program, it must be under the same license with its source code available; private use and modifications you do not convey carry no conditions. The LGPL softens that for libraries used through their interfaces, the Mozilla Public License applies copyleft per file, and the AGPL adds a network clause: if you modify the Program and let users interact with it remotely over a network, you must offer those users the Corresponding Source of your version. Interaction over a network alone is not conveying under the GPL definitions; this is a separate condition the AGPL adds.

How to choose

The guide's own flow is three questions. If you are joining a community, use the license it already prefers - your project will fit right in. If you want it simple and permissive, that is the MIT license. If you care about sharing improvements, that is the GPLv3. The spectrum runs from the AGPL's conditions down to the Unlicense's none, and the popular choices - MIT and GPL - sit inside it rather than at its edges.

The calm version

A license is a permission slip, and its conditions are the price of reuse. Pick for the community you want to be part of, keep the notices the license asks for, and never ship a dependency that has no license at all.

Sources: choosealicense.com - the home page (how to choose, what no license means) and the licenses reference (permissions, conditions and limitations for MIT, Apache 2.0, LGPL, MPL 2.0, GPLv3, AGPLv3 and the Unlicense), plus the full license texts of GPLv3 and AGPLv3 (conveying definition, private use, section 13 remote network interaction).

Frequently asked questions

Is MIT or GPL better?

They answer different goals. MIT lets people do almost anything with your code, including closed-source versions, if they keep the copyright and license notice. GPLv3 allows the same freedoms but requires works you distribute - including larger works built on it - to stay under the same license with source available; private use and modification are unrestricted.

What happens if a project has no license?

It grants no explicit permission to use, modify or share the code, so businesses and savvy developers won't touch it. If it's a dependency, ask its maintainers to add one.

How is Apache 2.0 different from MIT?

Both are permissive, but Apache 2.0 adds an express grant of patent rights from contributors and requires you to state changes; MIT's only condition is preserving the notice.

What is special about the AGPL?

Its network clause: if you modify the Program and users interact with it remotely over a network, you must offer those users the Corresponding Source of your modified version. Network interaction alone is not conveying under the GPL definitions - the AGPL adds this as a separate condition.