Glossary

What is the BSD License?

Introduction

The BSD License encompasses a range of permissive free software licenses that are particularly noted for their minimal restrictions on the redistribution of covered software. These licenses originated from the Berkeley Software Distribution (BSD) operating system, a Unix derivative developed at the University of California, Berkeley. Known for their straightforward and lenient terms, BSD licenses facilitate the wide adoption and incorporation of BSD-licensed code into both open-source and proprietary projects​. 

Types of BSD Licenses

Original BSD (4-Clause)

This license included a controversial advertising clause, requiring all advertisements of the software to display an acknowledgment of the author.

Modified BSD (3-Clause)

A streamlined version of the original, removing the advertising clause while retaining the requirement to acknowledge the authors.

Simplified BSD (2-Clause)

Further simplified, it retains only the basic clauses, ensuring acknowledgment of the original authors and a disclaimer of liability.

BSD Zero Clause

Also known as the "Free Public License," this version eliminates all conditions and requirements, dedicating the work to the public domain.

Key Features and Clauses

Permissive Nature

BSD licenses allow users to freely use, modify, and distribute the software, even in proprietary products.

Redistribution and Use

Redistribution, with or without modification, is permitted under specific conditions, such as retaining the original copyright notice and disclaimers.

Disclaimer of Warranty

The licenses include a disclaimer of warranties, protecting the authors from legal liability.

Comparisons and Compatibility

BSD vs. Other Open Source Licenses

Compared to copyleft licenses like the GPL, BSD licenses are more permissive, allowing for the integration of BSD-licensed code into proprietary software.

Compatibility with GNU GPL

While the BSD License is generally compatible with the GPL, the GPL's copyleft provisions do not reciprocate, preventing the reverse integration of GPL-licensed code into BSD-licensed projects.

Explore our open source license compliance solutions for effective management. 

Usage and Applications

Examples in Software Projects

Many high-profile projects use BSD licenses, including the FreeBSD operating system, the Apache HTTP Server, and various components of macOS.

Best Practices for Using BSD Licenses

When using BSD-licensed code, it's important to adhere to the clauses, particularly the requirement to acknowledge the original authors and include the license text in redistributed versions.

Learn more about open source license compliance.

Implicit Patent Waivers

Some interpretations suggest that BSD licenses imply a patent license, allowing users to use patented technology included in the software.

Patent Rights Concerns

While the permissiveness of BSD licenses can be advantageous, it also means there are fewer explicit protections against patent litigation compared to more restrictive licenses.

For insights on triaging open source software risk, read here. 

Pros and Cons of BSD Licenses

Pros:

  • Permissiveness: Allows for wide usage, including in proprietary software.
  • Simplicity: Easy to understand and comply with.
  • Flexibility: Suitable for a variety of projects and business models.

Cons:

  • Lack of Copyleft: Does not ensure that modifications and derivative works remain open source.
  • Patent Protections: Limited explicit protections against patent claims.

Using Open Source Libraries in Closed Source Software

When using open source libraries in closed source software, it's crucial to understand the specific licenses under which these libraries are distributed. While permissive licenses like BSD and MIT allow for easy integration into proprietary software, copyleft licenses like the GNU GPL impose stricter conditions that may require the entire software to be open-sourced if GPL-licensed code is used​.

Delve deeper into understanding OSS licensing

Conclusion

The BSD License family offers a range of options that are particularly well-suited for projects needing a permissive, flexible licensing model. Depending on your project's needs, you might also consider the MIT, Apache, or GPL licenses, each offering unique benefits and protections.

Resources

SOFTWARE COMPOSITION ANALYSIS

Get a Demo

Revenera's end-to-end solution delivers a complete, accurate SBOM while managing license compliance and security.