Skip to content
BENIBIX Learn

Permissive License vs Copyleft

People think a permissive license and copyleft are both just open source, so the rules match, and they do not. A permissive license asks you to keep the notice, and your own code can stay closed. Copyleft asks more. If you hand out a changed copy, you must share its code under the same license.

Development🚀 Product & Releases

Permissive License

A license with few rules. Keep the notice, and use the code as you like.

A permissive license is an open source license with very few rules. You may use, change and share the code, even inside a paid, closed product. The main rule is to keep the copyright and license notice with the code. You do not have to share your own changes. MIT, BSD and Apache 2.0 are the best known.

Example
Lucy's company sells a closed app that uses an MIT library. They keep the MIT notice in the app's credits, and that is all they owe.
Why it matters
Firms can use this kind of code with little risk, so it spreads far. That is why many big libraries pick one.
Full entry
Development🚀 Product & Releases

Copyleft

A rule in some open licenses. If you share a changed copy, its code must stay open.

Copyleft is a rule in some open source licenses that keeps changed copies open too. You may use, change and share the code. But if you hand out a changed version, you must share its code under the same license. So nobody can take the code, close it and sell it as a secret. The GNU GPL is the best-known copyleft license.

Example
Jack changes a GPL tool and sells copies to customers. Copyleft means he must give those customers his changed code too.
Why it matters
It keeps a shared project shared. Some companies avoid copyleft code in closed products, so check before you use it.
Full entry

In one line

Permissive License
A license with few rules. Keep the notice, and use the code as you like.
Copyleft
A rule in some open licenses. If you share a changed copy, its code must stay open.