standard templates
includes boilerplate for MIT, Apache-2.0, BSD-3-Clause, and GPL-v3. covers the vast majority of use cases.
generate open-source license files in three seconds.
licenseme provides boilerplate text for the most common open-source licenses. select a license, input your name and the year, and copy the result.
licenseme is a generator for open-source license text. it supports MIT, Apache-2.0, BSD-3-Clause, and GPL-v3. you select the license, type your name and the current year, and it spits out the correctly formatted text.
nobody memorizes the MIT license. digging through old repositories to copy and paste a license file usually results in leaving the wrong year or the wrong author name in the text. licenseme gives you a clean slate every time.
this is for developers who just want to publish their code and move on. it removes the friction of figuring out which bracketed variables need to be replaced in standard legal templates.
includes boilerplate for MIT, Apache-2.0, BSD-3-Clause, and GPL-v3. covers the vast majority of use cases.
injects your name and the current year into the correct placeholders automatically. no manual editing needed.
one-click copy to clipboard. paste it into your repository and move on with your life.
generate licenses directly from your terminal. pipe the output straight into a LICENSE file.
we just give you the text. we do not try to explain copyright law to you.
generate an MIT license for your new project.
// input
licenseme mit --author 'voiddo' --year 2024 > LICENSE
// output
MIT License Copyright (c) 2024 voiddo Permission is hereby granted...
the tool injected the provided variables into the standard template and wrote it to a file.
every time we open-sourced a small utility, we had to go find another repository, copy the license file, and manually edit the year and author name. it is a trivial task, but it breaks your flow.
we got tired of seeing projects with no license because the author was too lazy to figure out the boilerplate. licenseme removes the last excuse for not putting an open-source license on your code.
yes. the text is pulled directly from the standard templates provided by the open source initiative.
no. modifying standard open-source licenses defeats the purpose of standardization. if you need custom terms, hire a lawyer.
not currently. it is strictly focused on software licenses.
absolutely not. we are software engineers, not lawyers. use at your own risk.
// just put a license on your code.