LLMpediaThe first transparent, open encyclopedia generated by LLMs

MIT License

Generated by GPT-5-mini
Note: This article was automatically generated by a large language model (LLM) from purely parametric knowledge (no retrieval). It may contain inaccuracies or hallucinations. This encyclopedia is part of a research project currently under review.
Article Genealogy
Parent: GitLab Hop 3
Expansion Funnel Raw 70 → Dedup 4 → NER 3 → Enqueued 2
1. Extracted70
2. After dedup4 (None)
3. After NER3 (None)
Rejected: 1 (not NE: 1)
4. Enqueued2 (None)
Similarity rejected: 1
MIT License
NameMIT License
Originated1980s
AuthorMassachusetts Institute of Technology

MIT License The MIT License is a permissive free software license originating at Massachusetts Institute of Technology that permits reuse within proprietary software provided attribution is retained. It is widely used by projects hosted on GitHub, endorsed by organizations such as the Free Software Foundation and accepted by entities including the Apache Software Foundation, Eclipse Foundation, and Linux Foundation. The license’s brevity and clear grant of rights make it a default choice for developers from institutions like Harvard University, Stanford University, Carnegie Mellon University, and corporations such as Microsoft and Google.

Overview

The license grants broad rights to copy, modify, merge, publish, distribute, sublicense, and sell copies of software created at institutions such as Massachusetts Institute of Technology and companies like IBM, Oracle Corporation, Intel, and Adobe Inc.. It requires that the original copyright notice and permission notice be included in all copies or substantial portions distributed to recipients, a practice followed by projects at Mozilla Foundation, KDE, GNOME Foundation, and Canonical Ltd.. Because it imposes minimal restrictions, the MIT License is often compared in popularity with licenses used by projects on SourceForge, Bitbucket, and GitLab.

History and Origin

The license was crafted at Massachusetts Institute of Technology in the late 20th century, emerging from an environment that produced projects like the Project Athena initiative and collaborations with corporations such as Digital Equipment Corporation and Xerox PARC. Its adoption accelerated with the rise of open source movements, influenced by milestones like the publication of the GNU General Public License and the founding of the Open Source Initiative. Early adopters included academic and corporate projects affiliated with MIT Media Lab, Laboratory for Computer Science, and collaborations with Bell Labs-era researchers who contributed to permissive licensing practices.

Terms and Conditions

Key provisions require inclusion of the copyright notice and permission notice in all copies, an attribution practice used by projects at Apache Software Foundation incubator and by contributors from Red Hat and Canonical Ltd.. The license contains a grant of rights covering use, copy, modify, merge, publish, distribute, sublicense, and sell, terms frequently invoked in repositories belonging to Google Summer of Code participants and contributors from Facebook’s open projects. It includes a disclaimer of warranty and limitation of liability clause similar in effect to provisions found in agreements used by Apple Inc., Nokia, and Samsung Electronics when releasing sample code. The minimal conditions make it compatible with proprietary relicensing, a feature exploited by companies such as Microsoft and Amazon Web Services.

Comparison with Other Licenses

Compared with copyleft licenses like the GNU General Public License and the Affero General Public License, the MIT License does not require derivative works to be distributed under the same terms, a contrast highlighted by projects from Debian and discussions within the Free Software Foundation. Against permissive alternatives such as the BSD 2-Clause and BSD 3-Clause licenses, the MIT License is similar in spirit to software releases from University of California, Berkeley and projects affiliated with FreeBSD and OpenBSD, though wording differences can affect patent and advertising provisions debated by organizations like the Open Source Initiative and legal teams at Intel and Qualcomm. The MIT License’s brevity is often preferred over longer frameworks like the Apache License 2.0 by corporations such as JetBrains and startups spun out of Y Combinator.

Usage and Adoption

High-profile projects under the MIT License include libraries and frameworks supported by communities at Node.js Foundation, React (web framework), contributors linked to Facebook, and tooling used in services by Netflix. Major code hosting platforms—GitHub, GitLab, and Bitbucket—report large numbers of repositories licensed under the MIT terms, a trend mirrored in corporate open source programs from Microsoft Azure and Google Cloud Platform. Universities such as Massachusetts Institute of Technology, Princeton University, and Yale University often release sample code and research software under the MIT License to encourage reuse by industry partners like Siemens and General Electric.

Legal analyses by law firms advising clients including Morrison & Foerster and Wilson Sonsini note that the MIT License’s brevity can create questions about patent grants and contributor obligations, matters litigated in cases involving entities like Oracle Corporation and interpreted in guidance from bar associations in jurisdictions such as United States federal courts and courts in United Kingdom. Compliance primarily hinges on preserving notices; failure to do so has prompted corrective actions by projects at Apache Software Foundation and advisories from organizations like the Software Freedom Law Center. For companies engaging in mergers and acquisitions, patent assignment and indemnity concerns lead legal teams at Goldman Sachs, Morgan Stanley, and Deloitte to recommend additional agreements when integrating MIT-licensed code into proprietary products. Internationally, adoption involves interplay with statutes in countries such as Germany, France, Japan, and Australia where courts have interpreted waiver and warranty disclaimers in different ways.

Category:Software licenses