You’ve probably seen it — a random GitHub repo with no LICENSE file, and yet people clone it, fork it, and build on top of it like it’s free real estate.
Spoiler: it’s not.
🧾 No License Means No Rights
If a project doesn’t include a license, you can’t legally use, modify, or distribute the code.
GitHub’s terms of service let you view the code, but that’s it.
Without an explicit license, the author keeps all rights reserved, whether they meant to or not.
So that “cool open source tool” with no license? Technically closed source.
📜 Popular Licenses in Plain English
- MIT — Do whatever you want, just don’t sue me.
- GPL — You can use this, but if you modify and distribute it, your code must also be open source.
- Apache 2.0 — Like MIT, but adds patent protection.
- BSD 3-Clause — Clean, minimal, and business-friendly.
- Unlicense — Public domain. Take it, run with it.
Each one sets a tone — permissive, protective, or viral. The trick is choosing based on how you want your project to spread (or not).
⚖️ Why It Matters
GitHub feels open, but the law doesn’t care about vibes.
If you want people to actually use your work, add a license.
If you’re using someone else’s repo, check theirs before shipping it in production.
Licenses are the handshake of open source.
Skip it, and no one really knows what’s allowed.