Citation and evidence

BSD licenses

16 min full readUpdated 40 references

This article's verification

Report a problem with this article

Edit article
More

Use this article

Raw MarkdownExplore connections

Improve this page

Revision historyDiscuss this article

Topics

Open Source AISoftware Development

Cite this article

The BSD licenses are a family of short, permissive software licenses that descend from the terms the University of California, Berkeley used to distribute the Berkeley Software Distribution (BSD), its version of the Unix operating system. The members of the family grant broad permission to redistribute and use software in source and binary form, with or without modification, provided that copyright notices and a warranty disclaimer are kept; they differ in how many extra conditions they add.[1][2][3] The four-clause original added an advertising requirement that Berkeley withdrew for its own code in 1999, the three-clause "new" or "modified" version keeps a non-endorsement clause, the two-clause "simplified" version drops that too, and the Zero-Clause BSD license (0BSD) removes even the notice requirement.[1][2][3][4][14] The 2-clause and 3-clause versions are approved by the Open Source Initiative (OSI), and the Free Software Foundation (FSF) classifies the 2-clause and 3-clause texts as free software licenses compatible with the GNU General Public License (GPL), while describing the original four-clause text as free but GPL-incompatible.[10][11][19]

In machine learning, the 3-clause license covers several core scientific Python libraries, including scikit-learn, NumPy, SciPy, pandas and Jupyter, and PyTorch is distributed under a BSD-style license with a 3-clause structure.[22][23][24][25][26][27] Some trained models are also published under BSD terms on Hugging Face, although researchers have questioned whether software licenses are the right instrument for model parameters.[30][32][37]

Overview

Common nameSPDX identifierOther namesConditions beyond the disclaimerOSI approvedFSF assessment
Original BSD licenseBSD-4-Clause4-clause, "Old" BSDRetain notice in source; reproduce notice for binaries; advertising acknowledgement; no endorsementNo[1]Free, GPL-incompatible[19]
Modified BSD licenseBSD-3-Clause"New" or "Revised" BSDRetain notice in source; reproduce notice for binaries; no endorsementYes[10]Free, GPL-compatible[19]
FreeBSD licenseBSD-2-Clause"Simplified" BSDRetain notice in source; reproduce notice for binariesYes[11]Free, GPL-compatible[19]
Zero-Clause BSD0BSDOriginally approved as "Free Public License 1.0.0"NoneYes[12]Free, GPL-compatible, with cautions about removed notices[19]

Expanded article table

The SPDX License List, the standard catalogue of license identifiers used in package metadata, names the three classic texts BSD 4-Clause "Original" or "Old", BSD 3-Clause "New" or "Revised", and BSD 2-Clause "Simplified".[1][2][3] OSI notes that the 3-clause text has also been called the "New BSD License" or "Modified BSD License", and that the 2-clause text has also been called the "Simplified BSD License" and the "FreeBSD License".[10][11] The FSF uses "original BSD license", "modified BSD license" and "FreeBSD license" for the same three texts.[19]

History

Berkeley Software Distribution

The license takes its name from the software it was written for. Marshall Kirk McKusick's history of Berkeley Unix, published in the 1999 O'Reilly collection Open Sources: Voices from the Open Source Revolution, records that graduate student Bill Joy put together the first "Berkeley Software Distribution" early in 1977, and that later releases (2BSD, 4BSD, 4.1BSD, 4.2BSD and 4.3BSD) grew into a full Unix system.[13] Up to the 4.3BSD-Tahoe release, every recipient of BSD first had to obtain a source license from AT&T, whose Unix the Berkeley system was built on.[13]

Berkeley's first freely redistributable release was Networking Release 1, which shipped in June 1989 and contained the TCP/IP networking code and supporting utilities, code that McKusick says had been developed entirely by Berkeley and its contributors. McKusick describes its terms as liberal: a licensee could release the code, modified or not, in source or binary form, without paying royalties to Berkeley, and the only requirements were that the copyright notices in the source files stay intact and that products using the code say in their documentation that they contained code from the University of California and its contributors. Berkeley charged $1,000 for a tape, but anyone could copy the release from someone who already had it.[13] Networking Release 2 followed in June 1991 under the same terms.[13]

Unix System Laboratories (USL), the AT&T subsidiary that sold Unix, then sued Berkeley Software Design, Inc. (BSDI), a company that had begun selling a commercially supported system built from the Networking Release 2 code in January 1992, and later refiled the suit against both BSDI and the University of California. McKusick writes that a settlement was reached in January 1994: three files were removed from the 18,000 in Networking Release 2, minor changes were made to other files, and USL copyrights were added to about 70 files that remained freely redistributable. The resulting 4.4BSD-Lite was released in June 1994 under terms identical to those of the networking releases.[13] The FreeBSD Project reproduces the 4.4BSD copyright notice, which carries four conditions: retain the notice in source code, reproduce it in the documentation of binary distributions, display the acknowledgement "This product includes software developed by the University of California, Berkeley and its contributors" in all advertising materials that mention the software, and do not use the name of the University or its contributors to endorse or promote derived products without permission.[14]

The advertising clause

The third condition became the family's main point of contention. In his essay "The BSD License Problem", published by the GNU Project, Richard Stallman argues that the clause caused little difficulty while only Berkeley used it, but that other developers copied it with their own names in place of the University of California, so that a system assembled from many such programs would need many different acknowledgement sentences in any advertisement. He writes that he counted 75 of these sentences in a 1997 version of NetBSD.[15]

Stallman's account of the campaign against the clause is as follows: around 1996 the FreeBSD developers decided to remove it from their own code, the developers of Flick at the University of Utah removed it in May 1998, and Dean Hal Varian of the University of California took up the issue with the university administration. Stallman dates the university's decision to June 1999, after two years of discussion.[15] The announcement that the FreeBSD Project reproduces is a letter dated July 22, 1999, from William Hoskins, Director of the Office of Technology Licensing at UC Berkeley, addressed "To All Licensees, Distributors of Any Version of BSD". It states that, effective immediately, licensees and distributors no longer have to include the acknowledgement in advertising materials, and that the advertising paragraph of the BSD files containing it is deleted.[14] SPDX records the same change in its notes on the original license and keeps a separate identifier, BSD-4-Clause-UC, for the Berkeley-specific version of the four-clause text.[1][5]

The letter applied only to code whose copyright the university held. The NetBSD Foundation, which had also used a four-clause license, says that in 2008, after a vote of its membership, it changed its recommended license to a two-clause BSD license and changed the code contributed to the Foundation to the new license. Its explanation cites concerns about the old advertising clause and says that developers no longer considered the endorsement clause useful.[17] The FreeBSD Project's own copyright notice for its code is the two-clause text.[16]

Zero-Clause BSD

Zero-Clause BSD is a later and textually separate addition. OSI's license page records that it was submitted on August 30, 2015, by Christian Bundy and approved on October 14, 2015, under the name "Free Public License 1.0.0", and notes that despite its name it is an alteration of the ISC license and is not textually derived from the BSD family.[12] Rob Landley, who uses 0BSD for his Toybox command-line utilities, describes it as the OpenBSD project's suggested template license with the half sentence requiring the license text to be copied removed, and says he intended it as a public-domain-equivalent license. Landley writes that he asked Kirk McKusick for permission to call it a BSD license.[18]

Terms

Conditions

All the classic members of the family share the same grant: "Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met".[1][2][3] The conditions then stack:

  1. Source retention. Redistributions of source code must keep the copyright notice, the list of conditions and the disclaimer. Every version except 0BSD has this condition.[1][2][3]
  2. Binary reproduction. Redistributions in binary form must reproduce the notice, conditions and disclaimer in the documentation or other materials provided with the distribution. This appears in the 2-, 3- and 4-clause texts.[1][2][3]
  3. Advertising acknowledgement. Only the 4-clause text requires advertising materials that mention the software's features or use to carry an acknowledgement naming the developer.[1]
  4. Non-endorsement. The 3- and 4-clause texts forbid using the name of the copyright holder or contributors to endorse or promote derived products without specific prior written permission.[1][2]

None of the texts requires that modified versions be released under the same license or that source code be published, which is what makes them permissive rather than copyleft licenses.[1][2][3][19] Each ends with a disclaimer stating that the software is provided "AS IS", disclaiming implied warranties of merchantability and fitness for a particular purpose, and excluding liability for direct, indirect, incidental, special, exemplary or consequential damages.[1][2][3]

0BSD replaces this structure with a single grant, "Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is hereby granted", followed by a disclaimer, and has no condition at all.[4]

Patents

The 2-, 3- and 4-clause texts say nothing about patents.[1][2][3] Two less common variants address the gap from opposite directions. The BSD 3-Clause Clear License adds a sentence stating that no express or implied licenses to any party's patent rights are granted; SPDX lists it as not OSI-approved, and the FSF, while classing it as a free license compatible with GPLv2 and GPLv3, advises users to consider whether the licensor might want to sue for patent infringement.[8][19] The BSD-2-Clause Plus Patent License (BSD-2-Clause-Patent), which OSI has approved, adds an express patent license from each copyright holder and contributor covering claims necessarily infringed by their contributions; SPDX's note on it says it was designed as a simple permissive license that is compatible with GPL version 2 and includes an express patent grant.[7] The FSF's general advice is that the Apache License 2.0 is preferable to the BSD licenses for substantial programs because it deals with patents.[19]

Variants

VariantSPDX identifierDifference from the classic texts
BSD 1-ClauseBSD-1-ClauseOnly the source-retention condition; OSI-approved[6]
BSD-2-Clause Plus PatentBSD-2-Clause-Patent2-clause text plus an express patent license; OSI-approved[7]
BSD 3-Clause ClearBSD-3-Clause-Clear3-clause text plus a statement that no patent rights are granted; not OSI-approved[8]
BSD-4-Clause (University of California-Specific)BSD-4-Clause-UC4-clause text naming the Regents of the University of California[5]
BSD 2-Clause FreeBSDBSD-2-Clause-FreeBSD2-clause text with a closing "views and conclusions" sentence; deprecated identifier[9]
Eclipse Distribution License 1.0BSD-3-ClauseDifferent name, but SPDX treats the text as a match for BSD-3-Clause[2]

Expanded article table

SPDX deprecated the BSD-2-Clause-FreeBSD identifier, saying a more general variant had been added and that FreeBSD community members had indicated the final sentence is not part of that project's code license.[9] The current FreeBSD copyright page still prints the "views and conclusions" sentence after the license text.[16]

Compatibility with the GPL

The FSF's license list describes the original BSD license as a "lax, permissive non-copyleft free software license" with a serious flaw, the advertising clause, which does not make software non-free but causes practical problems including incompatibility with the GNU GPL. It urges developers not to use that license for new software while saying there is no reason not to use programs already released under it.[19] The modified (3-clause) and FreeBSD (2-clause) licenses are listed as GPL-compatible.[19]

The FSF also cautions against the phrase "the BSD license", because it implies there is only one text and could lead a developer to copy the flawed original by accident; Stallman's essay asks people to name the specific license, suggests other permissive licenses such as Expat (the MIT License text) or the FreeBSD license for new non-copyleft software, and names Apache 2.0 as the FSF's recommended non-copyleft license.[15][19] On 0BSD, the FSF says it can operate as a GPL-compatible free software license, but warns that if notices are removed from a program, recipients cannot safely rely on the license, and that it considers the FreeBSD license the wiser choice for a short permissive license.[19]

Adoption

Usage measurements vary with method. A 2015 GitHub analysis of licensed public repositories found BSD 3-clause in 4.53 percent and BSD 2-clause in 1.70 percent, against 44.69 percent for MIT.[20] OSI's count of human pageviews on its license pages during 2025 ranked BSD 3-Clause third (214,000 pageviews) and BSD 2-Clause fourth (128,000), behind MIT and Apache 2.0, with 0BSD eleventh (21,000); OSI notes that the figures exclude bots and probably undercount readers who use ad blockers.[21] Pageviews measure interest in license documentation, not the number of projects using a license.

Use in AI and machine learning

Software

The 3-clause license is common in the Python libraries that much deep learning and data-science work depends on. As of November 2026, the license files of scikit-learn, pandas, Jupyter Notebook and IPython are headed "BSD 3-Clause License", and NumPy and SciPy carry the same three conditions under their own copyright lines.[22][23][24][25][26][40] Salesforce's LAVIS library is also released under the 3-clause license.[39]

PyTorch's LICENSE file collects copyright lines under the headings "From PyTorch" and "From Caffe2", followed by the three BSD conditions; its non-endorsement clause names Facebook, Deepmind Technologies, NYU, NEC Laboratories America and IDIAP Research Institute.[27] When checked in November 2026, GitHub's automated license detection reported the repository's license as "NOASSERTION" rather than a specific SPDX identifier, so a project's label can depend on which tool reads it.[28]

A BSD license on part of a project does not always cover the whole repository. As of November 2026, the top-level LICENSE file of the Weaviate vector database says that source code outside a "wl" directory is under BSD-3-Clause, while code inside that directory is copyright Weaviate BV and available only under a separate enterprise license, and that the BSD license does not grant the right to use those features or circumvent a license key.[29]

Model weights

The Hugging Face Hub lets model publishers declare a license in the model card metadata, with tags for the BSD family (bsd), the 2-clause license (bsd-2-clause), the 3-clause license (bsd-3-clause) and the 3-clause Clear license (bsd-3-clause-clear).[30] Searching the Hub by the bsd-3-clause tag and sorting by downloads in November 2026 returned, among others, Salesforce's BLIP image-captioning and visual question answering checkpoints, an Audio Spectrogram Transformer fine-tuned on AudioSet published under MIT's organization account, and image classifiers from the timm collection.[31][32][34] The BLIP checkpoints follow the code: Salesforce's BLIP GitHub repository is itself under the 3-clause license.[33] Other releases use different members of the family. The Pi3 visual geometry model is tagged bsd-2-clause, and Qualcomm's MobileWan video generation model lists both bsd-3-clause-clear and a separate Qualcomm responsible AI license, so the BSD tag alone does not describe every term that applies.[35][36]

Applying a source-code license to model weights raises questions the texts were not written for. The BSD conditions are phrased in terms of "source code" and "binary form", and the texts do not mention data or trained parameters.[2][3] The authors of the Model Openness Framework argue that model parameters are data and are more aptly governed by open data licenses than by open-source software licenses, and the framework names CDLA-Permissive-2.0 as its preferred license for parameters; for software code, the same paper names the MIT, Apache 2.0 and 3-Clause BSD licenses as prominent examples of OSI-approved open-source licenses.[37] The OSI's Open Source AI Definition 1.0 requires code to be available under OSI-approved licenses and parameters under OSI-approved terms, noting that parameters may be free by their nature or may need a license or other legal instrument.[38] A BSD license on a model's code therefore says nothing on its own about the license of its weights or training data; each artifact's terms have to be read separately, as with other open weights releases.

Continue reading

More to read

Topics:Open Source AISoftware Development

References

  1. ^1 ^2 ^3 ^4 ^5 ^6 ^7 ^8 ^9 ^10 ^11 ^12 ^13SPDX License List. "BSD 4-Clause 'Original' or 'Old' License". spdx.org. spdx.org/...BSD-4-Clause
  2. ^1 ^2 ^3 ^4 ^5 ^6 ^7 ^8 ^9 ^10 ^11 ^12SPDX License List. "BSD 3-Clause 'New' or 'Revised' License". spdx.org. spdx.org/...BSD-3-Clause
  3. ^1 ^2 ^3 ^4 ^5 ^6 ^7 ^8 ^9 ^10SPDX License List. "BSD 2-Clause 'Simplified' License". spdx.org. spdx.org/...BSD-2-Clause
  4. ^1 ^2SPDX License List. "BSD Zero Clause License". spdx.org. spdx.org/...0BSD
  5. ^1 ^2SPDX License List. "BSD-4-Clause (University of California-Specific)". spdx.org. spdx.org/...BSD-4-Clause-UC
  6. ^SPDX License List. "BSD 1-Clause License". spdx.org. spdx.org/...BSD-1-Clause
  7. ^1 ^2SPDX License List. "BSD-2-Clause Plus Patent License". spdx.org. spdx.org/...BSD-2-Clause-Patent
  8. ^1 ^2SPDX License List. "BSD 3-Clause Clear License". spdx.org. spdx.org/...BSD-3-Clause-Clear
  9. ^1 ^2SPDX License List. "BSD 2-Clause FreeBSD License". spdx.org. spdx.org/...BSD-2-Clause-FreeBSD
  10. ^1 ^2 ^3Open Source Initiative. "The 3-Clause BSD License". opensource.org. opensource.org/...bsd-3-clause
  11. ^1 ^2 ^3Open Source Initiative. "The 2-Clause BSD License". opensource.org. opensource.org/...bsd-2-clause
  12. ^1 ^2Open Source Initiative. "Zero-Clause BSD". opensource.org. opensource.org/...0bsd
  13. ^1 ^2 ^3 ^4 ^5Marshall Kirk McKusick. "Twenty Years of Berkeley Unix: From AT&T-Owned to Freely Redistributable". Open Sources: Voices from the Open Source Revolution, O'Reilly, January 1999. oreilly.com/...kirkmck
  14. ^1 ^2 ^3The FreeBSD Project. "The 4.4BSD Copyright". freebsd.org. freebsd.org/...license
  15. ^1 ^2 ^3Richard Stallman. "The BSD License Problem". GNU Project, Free Software Foundation. gnu.org/...bsd
  16. ^1 ^2The FreeBSD Project. "The FreeBSD Copyright". freebsd.org. freebsd.org/...freebsd-license
  17. ^The NetBSD Foundation. "NetBSD Licensing and Redistribution". netbsd.org. netbsd.org/...redistribution
  18. ^Rob Landley. "Toybox License". landley.net. landley.net/...license
  19. ^1 ^2 ^3 ^4 ^5 ^6 ^7 ^8 ^9 ^10 ^11 ^12 ^13Free Software Foundation. "Various Licenses and Comments about Them". GNU Project. gnu.org/...license-list
  20. ^Ben Balter. "Open source license usage on GitHub.com". The GitHub Blog, March 9, 2015. github.blog/...-source-license-usage-on-github-com
  21. ^Nick Vidal. "Top Open Source licenses in 2025". Open Source Initiative, December 17, 2025. opensource.org/...top-open-source-licenses-in-2025
  22. ^1 ^2scikit-learn developers. "COPYING". scikit-learn GitHub repository. github.com/...COPYING
  23. ^1 ^2NumPy Developers. "LICENSE.txt". NumPy GitHub repository. github.com/...LICENSE.txt
  24. ^1 ^2SciPy Developers. "LICENSE.txt". SciPy GitHub repository. github.com/...LICENSE.txt
  25. ^1 ^2pandas development team. "LICENSE". pandas GitHub repository. github.com/...LICENSE
  26. ^1 ^2Jupyter Development Team. "LICENSE". Jupyter Notebook GitHub repository. github.com/...LICENSE
  27. ^1 ^2PyTorch contributors. "LICENSE". PyTorch GitHub repository. github.com/...LICENSE
  28. ^GitHub REST API. "pytorch/pytorch" repository metadata, license field. Accessed November 18, 2026. api.github.com/...pytorch
  29. ^Weaviate. "LICENSE". Weaviate GitHub repository. github.com/...LICENSE
  30. ^1 ^2Hugging Face. "Licenses". Hugging Face Hub documentation. huggingface.co/...repositories-licenses
  31. ^Hugging Face. Models API, filter license:bsd-3-clause sorted by downloads. Accessed November 18, 2026. huggingface.co/...models
  32. ^1 ^2Salesforce. "Salesforce/blip-image-captioning-base" model card. Hugging Face. huggingface.co/...blip-image-captioning-base
  33. ^Salesforce. "LICENSE.txt". BLIP GitHub repository. github.com/...LICENSE.txt
  34. ^Hugging Face. "MIT/ast-finetuned-audioset-10-10-0.4593" model card. huggingface.co/...-finetuned-audioset-10-10-0.4593
  35. ^"yyfz233/Pi3" model card. Hugging Face. huggingface.co/...Pi3
  36. ^Qualcomm AI Research. "Qualcomm-AI-Research/mobilewan" model card. Hugging Face. huggingface.co/...mobilewan
  37. ^1 ^2Matt White, Ibrahim Haddad, Cailean Osborne, Xiao-Yang Yanglet Liu, Ahmed Abdelmonsef, Sachin Mathew Varghese, Arnaud Le Hors. "The Model Openness Framework: Promoting Completeness and Openness for Reproducibility, Transparency, and Usability in Artificial Intelligence". arXiv:2403.13784, 2024. arxiv.org/...2403.13784
  38. ^Open Source Initiative. "The Open Source AI Definition 1.0". opensource.org. opensource.org/...open-source-ai-definition
  39. ^Salesforce. "LICENSE.txt". LAVIS GitHub repository. github.com/...LICENSE.txt
  40. ^IPython Development Team. "LICENSE". IPython GitHub repository. github.com/...LICENSE

Improve this article

Add missing citations, update stale details, or write a clearer explanation. Anyone can edit: changes go live when you publish, and every edit is checked by an editor.

1 revision · v1 · 3,157 words · full history

Fact-checks are independent of edits: a reviewer re-verifies the article against its sources and stamps the date. How we verify

Research and drafting on this wiki are AI-assisted, under named human editorial standards. How AI is used here

Reviewer note: Independent fact-check before publication on November 18, 2026: 78 claims checked against 41 cited and independent sources; 1 material and 2 minor corrections applied before publication.

Cite this page: AI Wiki. "BSD licenses." aiwiki.ai, updated 18 Nov 2026, fact-checked 18 Nov 2026. CC BY 4.0. https://aiwiki.ai/wiki/bsd_licenses

Edit article