choosealicense.com/_licenses/unlicense.txt

---
title: The Unlicense
spdx-id: Unlicense
source: https://unlicense.org/UNLICENSE
hidden: false

description: A license with no conditions whatsoever which dedicates works to the public domain. Unlicensed works, modifications, and larger works may be distributed under different terms and without source code.

how: Create a text file (typically named UNLICENSE or UNLICENSE.txt) in the root of your source code and copy the text of the license disclaimer into the file.

using:
  - youtube-dl: https://github.com/rg3/youtube-dl/blob/master/LICENSE
  - kakoune: https://github.com/mawww/kakoune/blob/master/UNLICENSE
  - RDF.rb: https://github.com/ruby-rdf/rdf/blob/master/UNLICENSE

permissions:
  - private-use
  - commercial-use
  - modifications
  - distribution

conditions: []

limitations:
  - liability
  - warranty

---

This is free and unencumbered software released into the public domain.

Anyone is free to copy, modify, publish, use, compile, sell, or distribute
this software, either in source code form or as a compiled binary, for any
purpose, commercial or non-commercial, and by any means.

In jurisdictions that recognize copyright laws, the author or authors of this
software dedicate any and all copyright interest in the software to the public
domain. We make this dedication for the benefit of the public at large and to
the detriment of our heirs and
successors. We intend this dedication to be an overt act of relinquishment in
perpetuity of all present and future rights to this software under copyright
law.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN
ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

For more information, please refer to <http://unlicense.org/>
Add public domain license 2013-07-10 11:20:40 -07:00			`---`
validate SPDX compliance 2015-03-07 13:38:52 -05:00			`title: The Unlicense`
spdx-id required, nickname only for licenses with customary short names 2016-05-24 16:21:13 -05:00			`spdx-id: Unlicense`
Use HTTPS if available 2017-10-01 10:02:19 +02:00			`source: https://unlicense.org/UNLICENSE`
re-add optional hidden field, default to true licenses on /licenses have `hidden: false` set fixes #434 2016-06-14 10:35:44 -07:00			`hidden: false`
add source back to unlinces 2014-06-17 13:08:07 -04:00
Include 'copyleft', 'permissive', and 'public domain' in descriptions Feedback from @waldyrious at https://github.com/github/choosealicense.com/pull/396#issuecomment-213912884 2016-04-24 10:06:46 -07:00			`description: A license with no conditions whatsoever which dedicates works to the public domain. Unlicensed works, modifications, and larger works may be distributed under different terms and without source code.`
Rework descriptions of 7 listed on /licenses - primarily functional - drop self-naming - minimize requiring significant understanding of other licenses or copyright - should be excruciatingly bland for anyone who already knows the licenses well; newcomers shouldn't have to deal with baggage immediately Probably a few more words should be added to the xGPLv3s about their stronger patent terms. Licenses not listed on /licenses could be described in similar style. 2016-04-23 21:15:06 -07:00
Use the unlicense instead of CC0 to represent the public domain 2013-07-16 01:11:04 -05:00			`how: Create a text file (typically named UNLICENSE or UNLICENSE.txt) in the root of your source code and copy the text of the license disclaimer into the file.`
Add public domain license 2013-07-10 11:20:40 -07:00
unlicense: add 3 popular projects using it 2016-08-22 18:24:02 +01:00			`using:`
			`- youtube-dl: https://github.com/rg3/youtube-dl/blob/master/LICENSE`
unlicense: fix typo "kakokune" -->"kakoune" 2016-08-22 20:03:52 +01:00			`- kakoune: https://github.com/mawww/kakoune/blob/master/UNLICENSE`
Replace dual-licensed example with RDF.rb 2017-06-10 12:45:38 -05:00			`- RDF.rb: https://github.com/ruby-rdf/rdf/blob/master/UNLICENSE`
unlicense: add 3 popular projects using it 2016-08-22 18:24:02 +01:00
rename/order license properties better reflect how licenses work and are structured grant (permissions) conditioned on (conditions) with limitations Permissions coming first combats mistaken but apparently widespread impression that licenses impose conditions, even such that without a license, there would be no conditions/work would be in the public domain. Requirements->Conditions emphasizes that they are pertinent if one wants to take advantage of permissions. Forbiddens->Limitations is more accurate: in most cases licenses don't give permission to hold licensors liable, in some cases to use licensors' trademarks or patents, but a licensee does not lose the permissions granted by the license if the licensee holds licensor liable, etc. Also emphasizes that there are limitatations on the license grant, not that the license imposes prohibitions. The most concise place to see both the rename and reorder is in _includes/license-overview.html I did not reorder the appearance of the groups of properties in license source files (.txt files in _licenses) as those orderings are not used to render anything on the webiste. Might do so later. 2016-03-01 13:33:15 -08:00			`permissions:`
Fixing CTKI pb 2013-07-23 15:37:43 +02:00			`- private-use`
Add public domain license 2013-07-10 11:20:40 -07:00			`- commercial-use`
			`- modifications`
			`- distribution`

drop "dedication" from family name, fix #289; drop double empty condition properties 2016-03-07 15:43:39 -08:00			`conditions: []`

rename/order license properties better reflect how licenses work and are structured grant (permissions) conditioned on (conditions) with limitations Permissions coming first combats mistaken but apparently widespread impression that licenses impose conditions, even such that without a license, there would be no conditions/work would be in the public domain. Requirements->Conditions emphasizes that they are pertinent if one wants to take advantage of permissions. Forbiddens->Limitations is more accurate: in most cases licenses don't give permission to hold licensors liable, in some cases to use licensors' trademarks or patents, but a licensee does not lose the permissions granted by the license if the licensee holds licensor liable, etc. Also emphasizes that there are limitatations on the license grant, not that the license imposes prohibitions. The most concise place to see both the rename and reorder is in _includes/license-overview.html I did not reorder the appearance of the groups of properties in license source files (.txt files in _licenses) as those orderings are not used to render anything on the webiste. Might do so later. 2016-03-01 13:33:15 -08:00			`limitations:`
no-liability -> liability, warranty rename and add tag and associated descriptions fixes #412 2016-12-12 14:29:25 -08:00			`- liability`
			`- warranty`
sort license properties in the order permissions > conditions > limitations (fixes #387) 2016-08-22 18:25:24 +01:00
Add public domain license 2013-07-10 11:20:40 -07:00			`---`
Normalize sorting of license properties Properties are now consistently sorted across all license files, appearing in the following order: title nickname tab-slug redirect_from category variant featured hidden source description how note using required permitted forbidden 2015-03-13 04:13:03 +00:00
Use the unlicense instead of CC0 to represent the public domain 2013-07-16 01:11:04 -05:00			`This is free and unencumbered software released into the public domain.`

Source SPDX HTML, wrap with pandoc to get closer to usable form 2017-11-19 13:49:31 -08:00			`Anyone is free to copy, modify, publish, use, compile, sell, or distribute`
			`this software, either in source code form or as a compiled binary, for any`
			`purpose, commercial or non-commercial, and by any means.`

			`In jurisdictions that recognize copyright laws, the author or authors of this`
			`software dedicate any and all copyright interest in the software to the public`
			`domain. We make this dedication for the benefit of the public at large and to`
			`the detriment of our heirs and`
			`successors. We intend this dedication to be an overt act of relinquishment in`
			`perpetuity of all present and future rights to this software under copyright`
			`law.`

			`THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR`
			`IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,`
			`FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE`
			`AUTHORS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN`
			`ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION`
			`WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.`

			`For more information, please refer to <http://unlicense.org/>`