Add a license to your project in seconds. Choose MIT, Apache 2.0, a BSD variant, ISC, MPL 2.0, GPL, LGPL, AGPL, the Unlicense or 0BSD, enter your name and year, and download a ready-to-commit LICENSE file with the exact official text — plus the header to put in each source file.
| Type | Licenses |
|---|---|
| Permissive | MIT, Apache 2.0, BSD, ISC |
| Weak copyleft | MPL 2.0, LGPL v3 |
| Strong copyleft | GPL v3, AGPL v3 |
| Public domain | Unlicense, 0BSD |
MIT or Apache 2.0 for maximum adoption; GPL if derivatives must stay open source.
Yes — loaded from the SPDX License List.
Apache 2.0 adds an explicit patent grant and requires noting changes.
At the root of your repository, named LICENSE (or COPYING for GNU licenses).
No.
License texts are fetched from the SPDX License List data, the canonical source used by GitHub and package registries, so the wording is exact. MIT is also bundled for offline use. Only the copyright placeholders are filled — <year>, [yyyy], <copyright holders>, [name of copyright owner] and similar forms. The file is named LICENSE, or COPYING for GNU licenses. A per-file header is generated as well: the GNU 'how to apply' notice for GPL-family licenses, or a copyright line with an SPDX-License-Identifier tag for the others. A one-line summary of each license's obligations helps you choose.