choosealicense.com/_licenses/bsd-3-clause.txt

---
title: BSD 3-Clause "New" or "Revised" License
spdx-id: BSD-3-Clause
hidden: false

description: A permissive license similar to the <a href="/licenses/bsd-2-clause/">BSD 2-Clause License</a>, but with a 3rd clause that prohibits others from using the name of the copyright holder or its contributors to promote derived products without written consent.

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:
  Flutter: https://github.com/flutter/flutter/blob/master/LICENSE
  LevelDB: https://github.com/google/leveldb/blob/master/LICENSE
  Quill: https://github.com/quilljs/quill/blob/develop/LICENSE

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

conditions:
  - include-copyright

limitations:
  - liability
  - warranty

---

BSD 3-Clause License

Copyright (c) [year], [fullname]

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the above copyright notice, this
   list of conditions and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice,
   this list of conditions and the following disclaimer in the documentation
   and/or other materials provided with the distribution.

3. Neither the name of the copyright holder nor the names of its
   contributors may be used to endorse or promote products derived from
   this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE
FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
First pass at Jekylification * Move licenses to license template * Move home / about to page template * Move annotations to config file, included via annotations.js * Move license metadata to YML Front matter * Automate the presentation of license metadata * Move sidebar to include * Add _site to gitignore 2013-04-09 12:41:25 -04:00			`---`
use SPDX license list 3.0 2017-12-29 14:30:08 -08:00			`title: BSD 3-Clause "New" or "Revised" License`
spdx-id required, nickname only for licenses with customary short names 2016-05-24 16:21:13 -05:00			`spdx-id: BSD-3-Clause`
hidden: false for 'popular' licenses - document criteria for whether a license is hidden - needed for license spectrum on /licenses OR - on 'popular' list at https://opensource.org/licenses (some other list could be used in the future) - adjust license properties and tests accordingly This gets non-hidden list back close to what it was before #386 and (pending licensee vendoring this change, licensee release, and github.com licensee dependency version bump) some commonly requested licenses (eg #413 #449) will reappear in the github.com license drop-down. 2016-09-26 11:20:44 -07:00			`hidden: false`
First pass at Jekylification * Move licenses to license template * Move home / about to page template * Move annotations to config file, included via annotations.js * Move license metadata to YML Front matter * Automate the presentation of license metadata * Move sidebar to include * Add _site to gitignore 2013-04-09 12:41:25 -04:00
BSD-3-Clause description: copyright holder rather than project 2021-03-23 13:53:07 -07:00			`description: A permissive license similar to the <a href="/licenses/bsd-2-clause/">BSD 2-Clause License</a>, but with a 3rd clause that prohibits others from using the name of the copyright holder or its contributors to promote derived products without written consent.`
add descriptions to bsd-3 and agpl 2015-02-26 14:10:55 -05:00
Remove superfluous instruction from bsd-3-clause* 'how' field 2019-02-15 12:51:55 -08: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.`
First pass at Jekylification * Move licenses to license template * Move home / about to page template * Move annotations to config file, included via annotations.js * Move license metadata to YML Front matter * Automate the presentation of license metadata * Move sidebar to include * Add _site to gitignore 2013-04-09 12:41:25 -04:00
make `using` required for new licenses 2017-05-30 14:17:13 -07:00			`using:`
Update BSD-3-Clause examples because d3 is now ISC licensed 2021-07-05 21:31:41 -07:00			`Flutter: https://github.com/flutter/flutter/blob/master/LICENSE`
Convert license `using` array to map 2020-10-03 11:34:50 +03:00			`LevelDB: https://github.com/google/leveldb/blob/master/LICENSE`
			`Quill: https://github.com/quilljs/quill/blob/develop/LICENSE`
make `using` required for new licenses 2017-05-30 14:17:13 -07: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:`
First pass at Jekylification * Move licenses to license template * Move home / about to page template * Move annotations to config file, included via annotations.js * Move license metadata to YML Front matter * Automate the presentation of license metadata * Move sidebar to include * Add _site to gitignore 2013-04-09 12:41:25 -04:00			`- commercial-use`
			`- modifications`
			`- distribution`
Add private-use to every license There is no license that prohibits private use. 2013-10-30 09:59:15 -07:00			`- private-use`
First pass at Jekylification * Move licenses to license template * Move home / about to page template * Move annotations to config file, included via annotations.js * Move license metadata to YML Front matter * Automate the presentation of license metadata * Move sidebar to include * Add _site to gitignore 2013-04-09 12:41:25 -04:00
sort license properties in the order permissions > conditions > limitations (fixes #387) 2016-08-22 18:25:24 +01: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 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
First pass at Jekylification * Move licenses to license template * Move home / about to page template * Move annotations to config file, included via annotations.js * Move license metadata to YML Front matter * Automate the presentation of license metadata * Move sidebar to include * Add _site to gitignore 2013-04-09 12:41:25 -04:00			`---`

consistent self-id of bsd-2/3, mit following isc in #371 2016-03-15 14:51:19 -07:00			`BSD 3-Clause License`

No more interpolating << 2013-07-17 11:57:57 -05:00			`Copyright (c) [year], [fullname]`
First pass at Jekylification * Move licenses to license template * Move home / about to page template * Move annotations to config file, included via annotations.js * Move license metadata to YML Front matter * Automate the presentation of license metadata * Move sidebar to include * Add _site to gitignore 2013-04-09 12:41:25 -04:00
Resolves Issue #74 2013-10-31 17:29:24 -05:00			`Redistribution and use in source and binary forms, with or without`
			`modification, are permitted provided that the following conditions are met:`
licenses: pre-format bsd license texts The license text is shown as preformatted text; therefore we need to wrap it to a sane length (like 80 characters) to keep it readable. In addition, we must do any formatting or indentation in the source file. Both BSD licenses contain a list of conditions that should be indented like a list, with blank lines in between. We could also potentially number the clauses; FreeBSD does in its copy, but the OSI versions do not. 2013-06-15 04:33:30 -04:00
BSD-2/3-Clause numbered list, uses SPDX and OSI have numbered lists for these licenses 2018-08-18 16:17:46 -07:00			`1. Redistributions of source code must retain the above copyright notice, this`
			`list of conditions and the following disclaimer.`
licenses: pre-format bsd license texts The license text is shown as preformatted text; therefore we need to wrap it to a sane length (like 80 characters) to keep it readable. In addition, we must do any formatting or indentation in the source file. Both BSD licenses contain a list of conditions that should be indented like a list, with blank lines in between. We could also potentially number the clauses; FreeBSD does in its copy, but the OSI versions do not. 2013-06-15 04:33:30 -04:00
BSD-2/3-Clause numbered list, uses SPDX and OSI have numbered lists for these licenses 2018-08-18 16:17:46 -07:00			`2. Redistributions in binary form must reproduce the above copyright notice,`
			`this list of conditions and the following disclaimer in the documentation`
			`and/or other materials provided with the distribution.`
licenses: pre-format bsd license texts The license text is shown as preformatted text; therefore we need to wrap it to a sane length (like 80 characters) to keep it readable. In addition, we must do any formatting or indentation in the source file. Both BSD licenses contain a list of conditions that should be indented like a list, with blank lines in between. We could also potentially number the clauses; FreeBSD does in its copy, but the OSI versions do not. 2013-06-15 04:33:30 -04:00
BSD-2/3-Clause numbered list, uses SPDX and OSI have numbered lists for these licenses 2018-08-18 16:17:46 -07:00			`3. Neither the name of the copyright holder nor the names of its`
			`contributors may be used to endorse or promote products derived from`
			`this software without specific prior written permission.`
licenses: pre-format bsd license texts The license text is shown as preformatted text; therefore we need to wrap it to a sane length (like 80 characters) to keep it readable. In addition, we must do any formatting or indentation in the source file. Both BSD licenses contain a list of conditions that should be indented like a list, with blank lines in between. We could also potentially number the clauses; FreeBSD does in its copy, but the OSI versions do not. 2013-06-15 04:33:30 -04:00
Resolves Issue #74 2013-10-31 17:29:24 -05:00			`THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"`
			`AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE`
			`IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE`
			`DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE`
			`FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL`
			`DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR`
			`SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER`
			`CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,`
			`OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE`
make ISC primary BSD-style license 2014-06-14 14:59:49 -04:00			`OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.`