{
  "id": "mit-license",
  "title": "MIT License",
  "lang": "en",
  "source_lang": "en",
  "summary": "The MIT License is a permissive free and open-source software license allowing broad reuse, modification, and distribution while requiring preservation of copyright and permission notices.",
  "category": "society",
  "subcategory": "law",
  "type": "work",
  "aliases": [
    "MIT license",
    "Expat License"
  ],
  "generated_at": "2026-11-03",
  "model": "pro/gpt-6.1-sol",
  "url": "https://aiwiki.page/en/mit-license/",
  "translations": {
    "zh-Hans": {
      "url": "https://aiwiki.page/zh/mit-license/",
      "json": "https://aiwiki.page/zh/mit-license.json"
    }
  },
  "sections": [
    {
      "heading": "",
      "text": "The MIT License is a permissive software license that allows software to be used, copied, modified, published, distributed, sublicensed, and sold, provided that its copyright notice and permission notice are retained in copies or substantial portions of the software. It is recognized as both a free software license and an open-source software license. Unlike licenses that require distributed adaptations to remain open source, it permits incorporation into proprietary products without requiring disclosure of their source code. Its short text combines a broad grant of permission with a notice-preservation condition and a disclaimer of warranties and liability."
    },
    {
      "heading": "Origins and terminology",
      "text": "The license takes its name from the Massachusetts Institute of Technology, whose software-distribution practices helped establish a family of short, permissive licenses. Historically, “MIT license” has not always identified a single text: related licenses circulated with MIT-associated software and the X Window System.\n\nIn contemporary software licensing, MIT License usually means the standardized text assigned the identifier MIT by SPDX, a system for identifying licenses and communicating software licensing information. The Free Software Foundation also calls this text the Expat License, distinguishing it from other MIT-associated licenses.\n\n“X11 License” is sometimes used loosely as a synonym, but the separately recognized X11 license contains additional wording, including a restriction on using specified names in advertising or promotion. The actual license text, rather than its informal name alone, determines the permissions and conditions attached to a software release."
    },
    {
      "heading": "Permissions and conditions",
      "text": "Broad rights of reuse\n\nThe MIT License grants permission, free of charge, to anyone obtaining a copy of the software and associated documentation to deal in them “without restriction,” subject to its stated condition. Its express permissions include:\n\n- Use: running the software for private, educational, organizational, or commercial purposes.\n- Copying and distribution: sharing original or modified copies, including as part of a larger product.\n- Modification: changing the software and creating a derivative work.\n- Publication and sublicensing: publishing the software and granting downstream permissions.\n- Sale: charging for copies, products incorporating the software, or related services.\n\nThe license does not require payment to the original author, registration of users, publication of modifications, or contribution of changes back to the original project. It also does not restrict particular fields of use.\n\n“Free of charge” describes the permission granted by the licensor; it does not prohibit recipients from selling the software.\n\nPreservation of notices\n\nThe central condition states:\n\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\n\nThis preserves identification of the copyright holder and the permission under which the software was supplied. Distributions commonly retain the complete license text, including its disclaimer, in a LICENSE file, a third-party notices document, or accompanying documentation.\n\nThe condition is not a general requirement to display an author’s name in an application’s user interface or advertising. Nor does the standard text require modified files to be marked as changed.\n\nThe phrase “substantial portions” is not defined by the license itself. Its application can depend on the material copied and relevant law; the license supplies no universal line-count or percentage threshold.\n\nProprietary distribution\n\nMIT-licensed code may be incorporated into software distributed under proprietary terms. A distributor need not disclose its own source code merely because the product contains an MIT-licensed component.\n\nHowever, the original notice-preservation condition still applies to the included material. Permission to sublicense does not allow a distributor to erase the upstream copyright notice or disregard the conditions under which it received the code. Proprietary terms covering a larger product do not change the original author’s ownership of the MIT-licensed portions."
    },
    {
      "heading": "Warranty and liability provisions",
      "text": "The license supplies the software “AS IS”, without express or implied warranties, including warranties of merchantability, fitness for a particular purpose, and noninfringement. It also states that authors and copyright holders are not liable for claims, damages, or other liability arising from the software or its use, whether in contract, tort, or otherwise.\n\nThese clauses distinguish permission to use software from a promise that it will work correctly, remain secure, or avoid infringing third-party rights. The license itself creates no obligation to provide maintenance, updates, technical support, or security fixes.\n\nThe legal effect of disclaimers depends on applicable law and the circumstances of a transaction. Mandatory consumer protection rules and other legal limits may affect their enforceability. A separate agreement may also create warranties or support obligations beyond those in the license."
    },
    {
      "heading": "Relationship to other licenses",
      "text": "Copyleft licenses\n\nThe MIT License is non-copyleft. Copyleft licenses impose conditions intended to preserve specified freedoms in redistributed software or adaptations. The GNU General Public License (GPL), for example, generally requires covered distributed modified works to remain under GPL terms and requires corresponding source code to be made available in the circumstances it specifies.\n\nMIT-licensed code can generally be incorporated into a GPL-covered work because its conditions are compatible with the GPL. The MIT notice must still be preserved, while distribution of the combined work must satisfy the applicable GPL requirements. The reverse does not follow: GPL-covered code cannot simply be redistributed under the MIT License alone without authorization from the relevant rights holders.\n\nOther permissive licenses\n\nThe two-clause BSD license and ISC license have broadly similar purposes, allowing extensive reuse with limited conditions and warranty disclaimers. Their wording differs, so they remain distinct licenses.\n\nThe Apache License 2.0 is also permissive but contains more detailed provisions, including an express patent license, patent-litigation termination terms, and additional notice requirements. These differences can matter when selecting licenses or combining components.\n\nPublic domain\n\nMIT-licensed software is not necessarily in the public domain. Copyright normally remains with its holders, and permission is granted subject to a condition. A public-domain work, by contrast, is not subject to copyright restrictions in the relevant jurisdiction. The practical freedom to reuse MIT-licensed code is broad, but its legal basis is a license rather than the absence of copyright."
    },
    {
      "heading": "Patents, trademarks, and other limits",
      "text": "The standard MIT text contains no express patent grant comparable to the one in Apache License 2.0. Whether particular circumstances support an implied patent license is a separate legal question; the text should not be understood as an explicit, comprehensive patent clearance.\n\nIt also contains no express grant of trademark rights. Permission to reuse a program’s code does not by itself authorize use of its name or logo in a way that infringes trademark rights or suggests endorsement.\n\nThe license grants only rights that the licensor can lawfully grant. It does not establish that every bundled dependency, image, dataset, or documentation file has the same license, nor does it guarantee that a contributor owns all rights in submitted material."
    },
    {
      "heading": "Use in software projects",
      "text": "Projects commonly apply the MIT License by distributing its standard text with a copyright notice identifying the relevant holder or holders. Source files may also contain license headers or SPDX expressions such as SPDX-License-Identifier: MIT, which help automated tools identify the applicable license. Such identifiers identify licensing terms; they are not themselves the full grant of permission.\n\nIn a multi-component project, a repository-level license does not necessarily override separate licenses attached to dependencies or particular files. The scope of an MIT declaration therefore depends on the release’s contents and notices, not merely on the presence of a file named LICENSE.\n\nThe license’s brevity and compatibility facilitate reuse in libraries, development tools, and commercial software. That same permissiveness allows downstream recipients to keep modifications proprietary: it enables sharing but does not require continued public development or reciprocal publication of improvements."
    }
  ],
  "links": [
    "free-software",
    "open-source-software",
    "massachusetts-institute-of-technology",
    "copyright",
    "consumer-protection",
    "copyleft",
    "gnu-general-public-license",
    "apache-license",
    "public-domain",
    "patent",
    "trademark"
  ],
  "sources": [],
  "license": "https://creativecommons.org/licenses/by/4.0/"
}