Choosing an Open Source License
It’s easy to get caught up in code. Sharing your code isn’t everything, though: it’s also important to tell people how they can use that code. Choosing an open source…
It’s easy to get caught up in code. Sharing your code isn’t everything, though: it’s also important to tell people how they can use that code.
Choosing an open source license can be confusing. We’ve created ChooseALicense.com to help you make that decision.
You can see a breakdown of what’s required, what’s permitted, and what’s forbidden for each license:
When you’ve made your choice, copy it to your clipboard with one click:
Have any suggestions? ChooseALicense.com itself is open source. Send us a Pull Request with your changes.
Licenses on GitHub.com
Now that we have all these licenses in one happy home, we want to help people choose their licenses on GitHub, too. When you create a new repository you’ll see a new license picker:
To get started, simply point your browser at choosealicense.com, or for more information, you can dive into the full documentation. Happy licensing!
Written by
Related posts
OpenClaw went viral. Meet the maintainers building and securing it.
OpenClaw is the fastest-growing project in GitHub history. Peter Steinberger and several maintainers share what they learned in the project’s first six months.
What 50 open source projects taught us about security in the AI era
See how the open source projects in Session 4 of the GitHub Secure Open Source Fund combined AI-assisted workflows, maintainer expertise, GitHub security tools, expert guidance, and funding to improve project security.
Your contributors are AI-first now. Is your project?
AI contributors are already in your queue. AutoGPT maintainer Nicholas Tindle shares the repo instructions, gates, and boundaries that keep maintainers in control.