This article was accepted into the corpus but its outbound wikilinks were never NER-processed — typical at the deepest BFS hop or when the run's entity cap was reached. No expansion funnel to show.
| BSD-3-Clause | |
|---|---|
| Name | BSD-3-Clause |
| Type | permissive free software license |
| Spdx | BSD-3-Clause |
| Notable software | FreeBSD, NetBSD, OpenBSD, PostgreSQL, X.org |
BSD-3-Clause is a permissive free software license originating from the University of California, Berkeley, used to govern redistribution and modification of source code in many NetBSD, FreeBSD, OpenBSD, PostgreSQL, X.org and other projects. It balances attribution requirements with minimal conditions, permitting proprietary relicensing while preserving credit to original contributors affiliated with institutions such as the University of California, Berkeley and companies like Apple Inc., Microsoft, IBM, Intel Corporation. The license is approved by organizations such as the Open Source Initiative and is recognized by standards bodies including the Free Software Foundation in pragmatic contexts.
The BSD-3-Clause emerged from the broader family of Berkeley Software Distribution releases associated with DARPA-funded research at the University of California, Berkeley and subsequent distributions maintained by projects like Berkeley Software Distribution (BSD) derivatives. It is employed by projects hosted at repositories and platforms including GitHub, GitLab, SourceForge, Bitbucket, and served as the license for codebases in corporations such as Red Hat, Canonical (company), SUSE, Oracle Corporation, and Nokia. The license is concise and widely adopted in ecosystems that include Linux kernel-adjacent software, network stacks in Cisco Systems devices, and embedded systems produced by firms like ARM Holdings and Qualcomm. Prominent academic adopters include the Massachusetts Institute of Technology, Stanford University, Carnegie Mellon University, and Princeton University.
Key provisions require preservation of copyright notices and disclaimers in source and binary redistributions, and a prohibition on using the names of contributors for endorsement without permission. These terms have been referenced in corporate policies at Google LLC, Facebook, Inc. / Meta Platforms, Inc., Amazon (company), and in procurement guidance from agencies such as the National Institute of Standards and Technology when evaluating software from vendors like SAP SE and VMware, Inc.. The permissive clause enables relicensing by entities including Adobe Systems, Autodesk, Siemens, and Siemens Healthineers for integration into proprietary offerings. The disclaimer of warranty and limitation of liability echoes formulations seen in licenses used by Apache Software Foundation projects and in legal frameworks considered by firms such as Accenture and Deloitte.
Compared with the original two-clause and the four-clause historical variants associated with the University of California, Berkeley and the Regents of the University of California, the three-clause form removes the advertising clause present in older notices tied to projects like 4.2BSD and BSD Unix. In contrast to copyleft licenses such as GNU General Public License versions used by GNU Project, the three-clause BSD allows incorporation into proprietary codebases similar to licenses from the MIT License and the permissive terms favored by Creative Commons-adjacent software projects. Corporate comparisons involve legal teams at Microsoft Corporation and Apple Inc. weighing BSD-3-Clause against Mozilla Public License choices in decisions for contributions to projects like Firefox and Thunderbird from the Mozilla Foundation.
The BSD-3-Clause is used by operating system projects such as FreeBSD, NetBSD, and OpenBSD and in network software stacks like OpenSSH, BIND, and ISC DHCP maintained by organizations including the Internet Systems Consortium. It is also prevalent in databases like PostgreSQL and middleware like libjpeg and zlib-adjacent projects historically distributed by entities such as The Apache Software Foundation and Eclipse Foundation. Major cloud and infrastructure companies—Amazon Web Services, Google Cloud Platform, Microsoft Azure—host services that run software under this license, and vendors like Dell Technologies, Hewlett Packard Enterprise, Lenovo ship firmware and drivers with BSD-3-Clause code. Academic use spans repositories at arXiv-linked projects and collaborations with institutions such as Harvard University and Yale University.
Legal compatibility with other licenses is an important consideration for legal departments at corporations like IBM, Oracle, Canonical, and Red Hat. BSD-3-Clause is generally compatible with permissive licenses such as the MIT License and compatible with proprietary integration, but must be reconciled when combined with strong copyleft licenses like the GNU General Public License in complex dependency graphs examined by compliance teams at Black Duck Software-audited firms and open source program offices at Netflix. Patent considerations have been evaluated in contexts involving Intel Corporation, Qualcomm, and ARM Limited, while trademark and endorsement restrictions have been scrutinized by organizations such as Wikimedia Foundation and Linux Foundation when hosting projects that reuse BSD-3-Clause code.
The lineage traces to the Berkeley Software Distribution releases developed under sponsorship from entities such as Defense Advanced Research Projects Agency and transitioned through stewardship by the University of California, later influencing licensing choices at companies like Sun Microsystems, Oracle Corporation, and Apple Inc.. The three-clause form became standardized as projects migrated to distributed version control systems pioneered by Linus Torvalds and platforms like GitHub and Bitbucket. Legal refinement and community adoption involved stakeholders from the Open Source Initiative, the Free Software Foundation, academic legal scholars at Stanford Law School and Harvard Law School, and policy groups such as Electronic Frontier Foundation.