CACrown ArchivesThe cinema collection
Menu
Research dossier · Science & Nature

MIT License

permissive free software license

Specimen drawers, botanical folios and brass scientific instruments under study light
Science and natureInterpretive dossier study · Crown Archives visual atlas
Record originEnglish Wikipedia
Text licenseCC BY-SA 4.0
Source revisionAug 19, 2026
Entity authorityQ334661
Source-derived summary

The MIT License is a permissive software license originating at the Massachusetts Institute of Technology (MIT) in the late 1980s. As a permissive license, it puts few restrictions on reuse and has high license compatibility.

Unlike copyleft software licenses, the MIT License allows reuse within proprietary software, provided that all copies of the software or its substantial portions include a copy of the terms of the MIT License and also a copyright notice. In 2015 and from at least 2020 through 2025, the MIT License was the most popular software license on GitHub.

Notable projects that use the MIT License include the X Window System, Ruby on Rails, Node.js, Lua, jQuery, .NET, Angular, and React.

License terms

The MIT License has the identifier MIT in the SPDX License List. It is also known as the "Expat License" (see § Ambiguity and variants). It has the following terms:

Copyright (c) <year> <copyright holders>

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

History

Computer scientist Jerry Saltzer has published his recollections of its early development, along with documentary evidence. According to Saltzer, the idea for the license came when working on a TCP/IP implementation in the Computer Systems Research (CSR) Group of the MIT Laboratory for Computer Science (MIT-LCS).

Editorial summary

The public source identifies “MIT License” as permissive free software license. This brief keeps that definition visible, then builds a research path around License, permissive and free.

Editorial reviewA sound reference starting point where classification, measurement and the date of the underlying evidence remain visible. The current lead gives the account dated anchors—2015, 2020, 2025—that can be checked directly. The authority record carries competing date values—1984-01, 1988-01-01, 1984-01-25—which should remain separate until their references and qualifiers are resolved. Its value is orientation rather than verdict, with License, permissive and free providing the first useful test.
Editorial analysis

Why this record matters

A short description can identify a subject without explaining its stakes. For “MIT License”, the useful work is to connect “permissive free software license” to the records capable of establishing context and consequence.

Evidence profile

Stable identifiers, scientific names and standards terminology offer the best bridge between this overview and specialist evidence. The source revision retrieved here is dated Aug 19, 2026. The linked authority identifier is Q334661. 3 of 3 selected statements include explicit references; 0 carry qualifiers and 0 use preferred rank. The first chronological checks are 2015, 2020 and 2025.

Critical limits

A general summary may omit uncertainty, sample limits or methodological disagreement that is explicit in the technical record. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.

How to read it

Check terminology, classification and the date of the cited evidence. Scientific names and technical consensus can change while older records retain historical value.

Best used for
  • Current terminology
  • Classification context
  • Finding cited technical literature
Verify next

Primary datasets, specimen catalogues, standards bodies and the most recent peer-reviewed literature.

Three-step research path

  1. Establish the record: confirm the title “MIT License”, its source revision and the description used here.
  2. Expand the search: follow MIT License primary sources, MIT License archive and License research across catalogues and specialist indexes.
  3. Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.

Questions for further research

  1. Which source most directly establishes the central claim about “MIT License”?
  2. Is the terminology current, historical or disputed?
  3. Has classification or technical consensus changed since the cited source?
Subject index

Search terms from this dossier

Source & attribution

This entry incorporates text from MIT License” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.