Library · Open Source

Patent Retaliation Clauses in Open Source Licenses: What They Terminate and Why It Matters

Patent retaliation clauses in open source licenses automatically end your right to use the software if you sue anyone over patents, and understanding exactly how they work can prevent an expensive surprise

2026-11-10 · open source · patent licensing · license termination · apache license

Open source licenses are not just about source code access — many of them contain patent retaliation clauses that can terminate your rights automatically the moment you file certain patent lawsuits. If your company ships products built on open source software, these clauses deserve the same attention you give to your patent enforcement strategy. Getting the relationship between the two wrong can cost you your entire license.

What a Patent Retaliation Clause Actually Does

A patent retaliation clause — sometimes called a patent termination clause — is a condition written into an open source license that says: if you assert a patent claim against someone in connection with the licensed software, your rights under that license end.

The core idea is defensive. Open source communities want contributors and users to have confidence that participating in a project will not expose them to patent suits from other participants. The retaliation clause is the enforcement mechanism for that norm.

The termination is typically automatic. You do not receive a notice and cure period. The moment you file the covered lawsuit, your license terminates by its own terms. Whether anyone sends you a letter is irrelevant to whether termination has occurred.

Which Licenses Contain These Clauses and What Triggers Them

Retaliation clauses appear in a wide range of commonly used licenses, but they vary significantly in scope.

Apache License 2.0

The Apache 2.0 license terminates your patent license — not your copyright license — if you file a patent infringement action alleging that any work licensed under Apache 2.0 directly or as a contributor version infringes your patent. The termination is surgical: it ends your right to the patent grants from every contributor to every Apache-licensed project you use, not just the project involved in the lawsuit.

GPLv3 and AGPLv3

GPLv3 and AGPLv3 include a retaliation clause under Section 10. If you initiate patent litigation alleging that any work conveyed under GPLv3 infringes a patent, your license from all contributors terminates. GPLv3 also contains a broader anti-tivoization and patent peace structure designed to prevent contributors from weaponizing patents against downstream users.

Mozilla Public License 2.0

The MPL 2.0 terminates your rights under the license if you make a patent claim that the covered software infringes your patents. The MPL version also distinguishes between defensive and offensive assertions in certain contexts, so the precise language matters.

Licenses Without Strong Retaliation Clauses

MIT, BSD, and ISC licenses do not contain patent retaliation clauses. They also do not contain express patent grants. That combination creates a different risk profile: you get no patent protection from contributors, but you also face no termination exposure from your own enforcement activity.

How This Interacts with Your Patent Strategy

If your company enforces patents — whether offensively against competitors or defensively in response to a demand — your legal team needs to map which open source licenses govern your production dependencies before litigation commences.

The Dependency Problem

Most companies have dozens or hundreds of open source dependencies, often layered through third-party libraries and frameworks. A retaliation clause in a license governing a deep dependency can still terminate your rights to that dependency even if the lawsuit has nothing to do with it. The trigger is typically any covered patent claim, not a claim specifically about the licensed software.

Contributor vs. Third-Party Patents

Some clauses only trigger when you sue a contributor to the specific project. Others trigger when you sue anyone over any patent. Reading the exact language is not optional — the difference between "a contributor" and "any party" can be the difference between a narrow exposure and a broad one.

Defensive Use Exceptions

Several licenses, including MPL 2.0 and some versions of the Common Development and Distribution License, carve out exceptions for defensive patent assertions — meaning if someone sues you for patent infringement first, your retaliatory counterclaim may not trigger termination. These exceptions are not universal, and they are not always symmetrical.

Practical Takeaways

Draft it, search it, check it — with a human in the loop.

YourPatentAI drafts provisional and non-provisional applications, runs prior-art search with IDS export, and checks claims for §§ 102, 103 and 112 issues before you file.

Get YourPatentAILearn more

This guide is general education, not legal advice, and does not create an attorney–client relationship. For your specific situation, talk to a registered patent attorney.