Understand the code you’re using
Licenses, without the legal maze.
Can I use it for work? Can I change it? Do I have to share my changes? Start with the license shown on a project page, then read its plain-English guide.
Permissive · keep the notices
MIT
You can use it, change it, self-host it and sell it. Keep the original copyright and license notice with copies of the code. You don’t have to publish your changes. The authors don’t promise it will work.
Explain this license →Permissive · notices and patent terms
Apache 2.0
You can use, change and sell it, including in closed-source products. When sharing copies, include the license, keep required notices and mark changed files. It includes a contributor patent grant with conditions, but no trademark permission or warranty.
Explain this license →Copyleft · share source with recipients
GPL v3
You can run it and change it privately. If you give others copies of the program or a modified version, provide the corresponding source under the GPL. You can charge money. Running it as a web service alone doesn’t trigger that source-sharing requirement.
Explain this license →Copyleft · includes modified network services
AGPL v3
You can use and change it, even commercially. If people use your modified version over a network, offer them its corresponding source under the AGPL. Sharing copies has source-sharing duties too. Sharing source code is different from sharing users’ content.
Explain this license →Permissive · keep the notices
ISC
You can use, change, self-host and distribute it, with or without charging money. Keep the original copyright and permission notice with copies. You don’t have to publish your changes. The authors don’t provide a warranty.
Explain this license →Check the actual terms
Missing or unfamiliar license
We haven’t established reuse permission. Public code on GitHub doesn’t by itself give you permission to copy, change or sell it. Read the actual terms or ask the maintainer before reusing the code.
Explain this license →These are general summaries of the linked license texts. The project’s own license, exceptions and separately licensed components govern. Code permission and hosting costs are separate.