Which licence github

You can filter repositories based on their license or license family using the license qualifier and the exact license keyword:. When you search by a family license, your results will include all licenses in that family. For example, when you use the query license:gpl , your results will include repositories licensed under GNU General Public License v2. For more information, see " Searching for repositories.

If your repository is using a license that isn't listed on the Choose a License website , you can request including the license. If your repository is using a license that is listed on the Choose a License website and it's not displaying clearly at the top of the repository page, it may contain multiple licenses or other complexity. The license picker is only available when you create a new project on GitHub.

You can manually add a license using the browser. For more information on adding a license to a repository, see " Adding a license to a repository. The goal of GitHub's open source licensing efforts is to provide a starting point to help you make an informed choice.

GitHub displays license information to help users get information about open source licenses and the projects that use them. For that reason, GitHub provides the information on an "as-is" basis and makes no warranties regarding any information or licenses provided on or through it, and disclaims liability for damages resulting from using the license information.

All GitHub docs are open source. See something that's wrong or unclear? Submit a pull request. For more information, see " Setting your commit email address. Click Commit new file. All GitHub docs are open source. See something that's wrong or unclear?

Submit a pull request. Or, learn how to contribute. GitHub Docs. Healthy contributions. Maintaining safety. Using wikis. Adding a license to a repository. In this article Including an open source license in your repository. If patented material was used in the creation of the software, it grants the right for users to use it. If the user sues anyone over the use of the patented material, they lose the right to use the software.

Ezequiel Foncubierta pointed something important for GPL licenses: The license of your source code must be compatible with the license of the open source code you are linking to. This is where people tends to make more mistakes. Modifications to the software can be release under any license. It offers the same patent usage protection as GPLv3. It explicitly prohibits the use of trademarked names found in the project. Changes made to the source code may not be documented. It offers no explicit position on patent usage.

The license and copyright notice must be included in the documentation of the compiled version of the source code as opposed to only in the source code. React is now MIT licensed. You are now able to sue Facebook and still use React. What a relief! Applying a license to your open source projects Licensing your projects is easy.

GitHub makes it even easier: Open your GitHub repository in a browser. In the root directory, click on Create new file. Click on Choose a license template.

Pick one of the licenses all the ones mentioned in this article are there. Once chosen, click on Review and submit. Commit the file. In summary… One of the most restrictive licenses is GPL.