License comparison
MIT vs BSD-3-Clause: notices and endorsement
A closed product can include either license without a duty to publish its own source. MIT requires its copyright and permission notice in copies or substantial portions. BSD-3-Clause explicitly places its copyright notice, conditions and disclaimer in source distributions and in materials accompanying binaries. Its third clause also bars using the copyright holder's or contributors' names to endorse your derived product without permission.
Compare the permissions, limits and obligations recorded in each guide. Read the license text for the full conditions that apply to your release.
Permissions
MIT
Commercial use
You may ship the code inside a paid product. The license does not restrict commercial use.
Modify
You may change the code, including keeping those changes private, unless a later obligation says otherwise.
Distribute
You may give copies to others. Distribution is what usually turns notice and source duties into real work.
Sublicense
You may include the code under your own product terms, so long as you still meet this license's conditions.
Private use
Use inside your company, including internal forks, does not by itself trigger distribution duties.
BSD-3-Clause
Commercial use
You may ship the code inside a paid product. The license does not restrict commercial use.
Modify
You may change the code, including keeping those changes private, unless a later obligation says otherwise.
Distribute
You may give copies to others. Distribution is what usually turns notice and source duties into real work.
Sublicense
You may include the code under your own product terms, so long as you still meet this license's conditions.
Private use
Use inside your company, including internal forks, does not by itself trigger distribution duties.
Limits
MIT
Hold liable
The authors disclaim warranty. Recipients cannot hold them liable for damages arising from the software, except where law forbids that disclaimer.
Use trademark
The license is not a trademark license. Names, logos and product marks stay with their owners unless a separate grant says otherwise.
Patent grant
The text does not grant patents. If buyers want an express patent grant, Apache-2.0 is the usual alternative.
BSD-3-Clause
Hold liable
The authors disclaim warranty. Recipients cannot hold them liable for damages arising from the software, except where law forbids that disclaimer.
Use trademark
The license is not a trademark license. Names, logos and product marks stay with their owners unless a separate grant says otherwise.
Patent grant
The text does not grant patents. If buyers want an express patent grant, Apache-2.0 is the usual alternative.
Endorse with names
You may not use the names of the University, the authors, or contributors to endorse derived products without prior written permission.
Obligations
MIT
Include copyright
Keep the copyright line with every copy or substantial portion you distribute.
Include license
Keep the license text with every copy or substantial portion you distribute. A web page is not a substitute for notices inside a shipped artifact.
Substantial portion
MIT names copies or substantial portions. Keep the copyright line and the permission notice with both whole packages and excerpts you vendor.
BSD-3-Clause
Include copyright
Keep the copyright line with every copy or substantial portion you distribute.
Include license
Keep the license text with every copy or substantial portion you distribute. A web page is not a substitute for notices inside a shipped artifact.
Binary materials
For a binary, reproduce the copyright, the conditions, and the disclaimer in the documentation or other materials that accompany it, not only in the source tree.
License texts
Practical guidance for procurement review, not legal advice. Confirm high-stakes use with counsel.