choosealicense.com/_licenses/isc.txt

---
title: ISC License
spdx-id: ISC
source: https://opensource.org/licenses/isc-license

description: A permissive license lets people do anything with your code with proper attribution and without warranty. The ISC license is functionally equivalent to the <a href="/licenses/bsd-2-clause/">BSD 2-Clause</a> and <a href="/licenses/mit/">MIT</a> licenses, removing some language that is no longer necessary.

how: Create a text file (typically named LICENSE or LICENSE.txt) in the root of your source code and copy the text of the license into the file. Replace [year] with the current year and [fullname] with the name (or names) of the copyright holders.

using:
  - Helix: https://github.com/tildeio/helix/blob/master/LICENSE
  - Node.js semver: https://github.com/npm/node-semver/blob/master/LICENSE
  - OpenStreetMap iD: https://github.com/openstreetmap/iD/blob/master/LICENSE.md

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

conditions:
  - include-copyright

limitations:
  - liability
  - warranty

---

ISC License

Copyright (c) [year], [fullname]

Permission to use, copy, modify, and/or distribute this software for any
purpose with or without fee is hereby granted, provided that the above
copyright notice and this permission notice appear in all copies.

THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES
WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
Adds ISC License 2013-07-17 02:52:32 +02:00			`---`
validate SPDX compliance 2015-03-07 19:38:52 +01:00			`title: ISC License`
spdx-id required, nickname only for licenses with customary short names 2016-05-24 23:21:13 +02:00			`spdx-id: ISC`
Use HTTPS if available 2017-10-01 10:02:19 +02:00			`source: https://opensource.org/licenses/isc-license`
Adds ISC License 2013-07-17 02:52:32 +02:00
add missing descriptions, missing property, slight desc tweaks 2016-04-04 19:56:29 +02:00			`description: A permissive license lets people do anything with your code with proper attribution and without warranty. The ISC license is functionally equivalent to the <a href="/licenses/bsd-2-clause/">BSD 2-Clause</a> and <a href="/licenses/mit/">MIT</a> licenses, removing some language that is no longer necessary.`
Adds ISC License 2013-07-17 02:52:32 +02:00
Remove recommendation to add email address to ISC Remove non-canonical license and usage text from f89201c 2015-09-02 01:28:18 +02:00			`how: Create a text file (typically named LICENSE or LICENSE.txt) in the root of your source code and copy the text of the license into the file. Replace [year] with the current year and [fullname] with the name (or names) of the copyright holders.`
Fix template parameter markers in ISC license. License template parameters are surrounded by square brackets, not angle brackets. Drop extension from source: as it's unnecessary. Add more details to description:. Add note: and filename:. Add private-use and sort permissions. 2013-07-19 20:54:03 +02:00
Add list of projects using ISC (closes #377) 2016-03-28 20:06:40 +02:00			`using:`
ISC examples 2017-11-26 05:38:49 +01:00			`- Helix: https://github.com/tildeio/helix/blob/master/LICENSE`
Add list of projects using ISC (closes #377) 2016-03-28 20:06:40 +02:00			`- Node.js semver: https://github.com/npm/node-semver/blob/master/LICENSE`
Example project moved its license file, update 2017-04-22 03:20:47 +02:00			`- OpenStreetMap iD: https://github.com/openstreetmap/iD/blob/master/LICENSE.md`
Add list of projects using ISC (closes #377) 2016-03-28 20:06:40 +02: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 22:33:15 +01:00			`permissions:`
Adds ISC License 2013-07-17 02:52:32 +02:00			`- commercial-use`
			`- distribution`
Fix template parameter markers in ISC license. License template parameters are surrounded by square brackets, not angle brackets. Drop extension from source: as it's unnecessary. Add more details to description:. Add note: and filename:. Add private-use and sort permissions. 2013-07-19 20:54:03 +02:00			`- modifications`
			`- private-use`
Adds ISC License 2013-07-17 02:52:32 +02:00
sort license properties in the order permissions > conditions > limitations (fixes #387) 2016-08-22 19:25:24 +02:00			`conditions:`
			`- include-copyright`

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 22:33:15 +01:00			`limitations:`
no-liability -> liability, warranty rename and add tag and associated descriptions fixes #412 2016-12-12 23:29:25 +01:00			`- liability`
			`- warranty`
sort license properties in the order permissions > conditions > limitations (fixes #387) 2016-08-22 19:25:24 +02:00
Adds ISC License 2013-07-17 02:52:32 +02:00			`---`

Add name of license to ISC license text 2016-03-15 19:13:39 +01:00			`ISC License`

Remove recommendation to add email address to ISC Remove non-canonical license and usage text from f89201c 2015-09-02 01:28:18 +02:00			`Copyright (c) [year], [fullname]`
Adds ISC License 2013-07-17 02:52:32 +02:00
			`Permission to use, copy, modify, and/or distribute this software for any`
			`purpose with or without fee is hereby granted, provided that the above`
			`copyright notice and this permission notice appear in all copies.`

			`THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES`
			`WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF`
			`MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR`
			`ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES`
			`WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN`
			`ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF`
			`OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.`