Skip to content
BENIBIX Learn

Permissive License

Development🚀 Product & ReleasesSoftware Licenses

Also known as Permissive Licence, Permissive Open Source License, Non-Copyleft License

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

Think of it like

It is like a free recipe. Cook it, change it or sell the cake. Just keep the cook's name on it.

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.

Definition

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 code

json
"license": "MIT"
This is the license line in a package.json file. MIT is one with few rules.
The ones with the fewest rules sit on the left of the line.

Common mistake

Dropping the notice when you copy the code. Keeping it is the one rule. This is a plain summary, not legal advice.

Key takeaways

  1. 1
    Few rules. Use it, change it, sell it.
  2. 2
    Keep the notice. Copyright and license text stay.
  3. 3
    No need to share. Your changes can stay closed.

Compare

Learn it properly