Open Source Licenses Compared: What the Coverage Left Out

Archi4 min read

licensinglegalopen-sourcecompliance

Contents
  1. The Comparison Everyone Runs, and Why It Misses
  2. MIT: Short, Silent, and Quick to Litigate
  3. What it does not say
  4. Apache 2.0: The Patent and Termination Machinery
  5. Termination and cure
  6. AGPLv3: The Network Clause and the Cure Clause
  7. The compatibility trap
  8. The Detail the Headlines Skip

The Comparison Everyone Runs, and Why It Misses#

Search for a guide to open source licenses and you get the same three-column table. Permissive on the left, copyleft on the right, a middle column for weak copyleft. MIT and Apache 2.0 at one end, GPL and AGPL at the other, with a row for commercial use and a row for distribution duties.

The table is not wrong. It is just answering a question most teams do not actually have. The question is not "which license is most free." It is "which clause will decide the argument we are about to have." Those arguments are rarely about copying source code. They are about patents, trademarks, and how long a company has to fix a mistake before its rights disappear.

Take three licenses that show up in almost every dependency audit: MIT, Apache 2.0 and AGPLv3. Read them for the clauses the comparison tables skip.

MIT: Short, Silent, and Quick to Litigate#

MIT is roughly 170 words. It grants permission to use, copy, modify, merge, publish, distribute, sublicense and sell, provided the copyright notice and permission notice travel with the code. It disclaims warranty and liability. That is the whole thing.

What it does not say#

MIT has no patent grant. It has no trademark clause. It has no termination provision describing what happens if you breach it. Those absences are not defects exactly, but they matter when money is on the line.

A patent grant in a license is a promise not to sue downstream users over patents the contributor holds. MIT makes no such promise. A contributor can license code under MIT on Monday and file an infringement claim over the same code on Tuesday, and the license text gives a court little to work with. Most contributors never do this. The point is that the license does not stop them, and the comparison table has no row for it.

Termination is the other gap. Some licenses spell out a cure period: a window to fix a violation before rights end automatically. MIT does not. If a downstream user fails to carry the copyright notice, the license's conditions are unmet, and the permission may simply not apply. Whether that means infringement from day one is a question courts answer case by case, not a question the license settles.

MIT remains a reasonable default for small libraries and internal tools. Just do not read its brevity as completeness.

Apache 2.0: The Patent and Termination Machinery#

Apache 2.0 is a longer document, and most of the extra length is the part people skip. Section 3 contains an express patent grant from each contributor, covering patent claims necessarily infringed by their contribution alone or by its combination with the project. That grant terminates if you file a patent suit alleging the software infringes. This is a mutual disarmament clause, and it is the single biggest practical difference between Apache 2.0 and MIT.

Termination and cure#

Section 4 covers redistribution duties. Section 7 disclaims warranty. But the clause that earns its keep in a dispute is the termination language: if you fail to comply, your rights under the license end automatically, with a reinstatement path if you cure the failure within 30 days of learning about it, and a permanent reinstatement if the copyright holder does not notify you within 60 days.

Thirty days is not generous. For a company that ships a product quarterly and relies on a compliance review, a month can pass before anyone reads the notice. But having a cure period at all is worth more than most teams realize. It converts a potential infringement claim into a deadline.

Apache 2.0 also addresses trademarks, though narrowly: it does not grant permission to use the licensor's trade names, trademarks or service marks, except as required for reasonable and customary use in describing the origin of the work. That sentence is why you cannot call your fork by the upstream project's name and expect the license to protect you.

AGPLv3: The Network Clause and the Cure Clause#

AGPLv3 gets treated as GPL with a scarier reputation. The real difference is one section: if users interact with a modified version over a network, they must be offered the corresponding source. Running the software on a server is not distribution under GPLv3. Under AGPLv3 it can trigger the source offer anyway.

That clause gets the headlines. The clause that gets missed is section 8, which gives a cure path. A first-time violation can be cured within 30 days of receiving notice, and the license is reinstated permanently. The cure only applies if the violation is the first time the party has received notice from that copyright holder and the party cures within the window. Repeat offenders get no such grace.

The compatibility trap#

AGPLv3 is not compatible with GPLv2-only code. Combining them in one program creates a licensing problem neither project is obliged to solve. This is the detail that sinks internal audits, and it appears in none of the three-column tables.

The Detail the Headlines Skip#

The license comparison genre treats these documents as positions on a spectrum from permissive to restrictive. In practice they are contracts with different failure modes. MIT fails quietly, in a courtroom, over a patent. Apache 2.0 fails on a 30-day clock. AGPLv3 fails on a network boundary and a first-notice rule.

None of that makes one license safer. A team that ships a SaaS product and never reads section 13 of AGPLv3 is exposed in a way that no amount of MIT adoption in its dependency tree will offset. A team that copies Apache 2.0 code into a product and strips the NOTICE file has a 30-day problem it may not know about until day 31.

Run the license scan. Then read the clauses the scan does not summarize: patent grants, trademark limits, cure periods, compatibility. That is where the argument will be.

More articles