Citation and evidence

Open-source license

34 min full readUpdated 83 references

This article's verification

Report a problem with this article

Edit article
More

Use this article

Raw MarkdownExplore connections

Improve this page

Revision historyDiscuss this article

Topics

AI Policy & RegulationOpen Source AISoftware Development

Cite this article

An open-source license is a software license that complies with the Open Source Definition (OSD), a ten-point standard maintained by the Open Source Initiative (OSI). In the OSI's own summary, such licenses allow software to be "freely used, modified, and shared".[1] The definition asks for more than visible source code: a license must permit free redistribution, modification and derived works, and it may not discriminate against persons, groups or fields of endeavor.[2] A license becomes "OSI-approved" after a public review on the OSI's license-review mailing list and a vote of the OSI board.[3]

Open-source licenses are usually sorted into two families. Permissive licenses such as the MIT License, the BSD licenses and the Apache License 2.0 ask for little more than the preservation of notices, and code under them can be built into proprietary products. Copyleft licenses such as the GNU General Public License (GPL) require modified versions to be distributed under the same license.[4] Licenses that publish source code but restrict production use or attach conditions to offering the software as a service, such as the Business Source License and the Server Side Public License, are called source-available and are not open source.[5][6]

In artificial intelligence the concept is under strain. Frameworks such as PyTorch and TensorFlow carry ordinary open-source licenses,[7][8] but the trained weights of a model are learned parameters, not source code written by a programmer,[9] and whether copyright covers them at all is not settled law.[10][11] Model developers have responded in different ways: some apply software licenses such as Apache 2.0 or MIT to weights,[12] some write custom terms such as the Llama Community License,[13] some adopt use-restricted OpenRAIL licenses,[14] and some use OpenMDW, a permissive license drafted for model releases.[15] The OSI's Open Source AI Definition (OSAID), released in October 2024, sets a separate standard for when an AI system, or a component such as a model or its weights, can be called open source.[9][16]

The Open Source Definition

Origin

The label "open source" was adopted at a strategy session in Palo Alto, California, on February 3, 1998, shortly after Netscape announced the release of its browser's source code. The participants wanted a single label for the collaborative development approach that was distinct from "free software", which they saw as philosophically and politically focused.[17] The OSI was founded later that month by Eric Raymond and Bruce Perens. The OSD was written at the same time by revising the Debian Free Software Guidelines, which Perens had drafted and the Debian project had adopted in 1997, and removing the references specific to Debian.[17][18]

By October 1999 the OSI had published its first formal list of approved licenses. Clause 10 was added to the definition in 2004 to deal with click-wrap licensing; the OSI describes the text as otherwise stable since its inception, with only minor clarifications of wording.[17] The current text is version 1.9.[2]

The ten criteria

No.CriterionWhat it requires
1Free redistributionNo restriction on selling or giving away the software as part of an aggregate distribution, and no royalty or fee for doing so
2Source codeThe program includes source code, or a well-publicized way to obtain it, in the form a programmer would prefer for modifying it; deliberately obfuscated code does not qualify
3Derived worksModifications and derived works are allowed and can be distributed under the same terms as the original
4Integrity of the author's source codeModified source may be restricted only if patch files are allowed; software built from modified source must be distributable; a different name or version number may be required
5No discrimination against persons or groupsThe license must not discriminate against any person or group of persons
6No discrimination against fields of endeavorThe license cannot, for example, bar use in a business or in genetic research
7Distribution of licenseThe rights pass to everyone who receives the program, without their having to accept an additional license
8License must not be specific to a productThe rights do not depend on the program being part of a particular distribution
9License must not restrict other softwareNo conditions on other software distributed alongside it
10License must be technology-neutralNo provision depends on an individual technology or style of interface

Expanded article table

The table paraphrases the OSD.[2] Criteria 5 and 6 are the ones the OSI cited when it assessed Meta's Llama licenses, and criterion 6 is the one the authors of the OpenRAIL licenses name as the reason their licenses do not qualify.[67][68][14] The OSI's FAQ puts the consequence plainly: all open-source software can be used for commercial purposes, a licensor cannot restrict how people use an open-source program, and an open-source license cannot be used to keep a program away from people the author disapproves of.[4]

OSI approval

Anyone may submit a license to the OSI's license-review mailing list, and anyone may join the list and comment. The OSI describes approval as a consensus process in which no single person, board members included, can approve or reject a license. A decision is normally due 60 days after submission; the License Committee then sends a recommendation to the OSI board, which votes on it.[3] Under a motion the board passed in May 2026, the License Committee may also reject submissions itself under certain conditions; in September 2026 it reported four such rejections, each for poor drafting.[77]

The process separates "legacy" licenses, which have been in use for at least five years by more than twenty projects maintained by unrelated entities, from new ones. A new license must meet the OSD and several further standards: it must be reusable by any licensor, must not put the licensor in a more favored position than licensees, must fill a gap that existing licenses do not fill, and must be possible to comply with. The OSI gives the Server Side Public License as an example of a license that fails the last test.[3]

The OSI groups approved licenses into categories that include "Popular / Strong Community", "Special Purpose", "Redundant with more popular", "Non-Reusable", "Superseded" and "Voluntarily retired".[1] The categories date from a campaign against license proliferation that the OSI began in 2004 and that produced a committee report in 2006.[17][19] As of November 2026 the "Popular / Strong Community" group holds twelve licenses: Apache 2.0, MIT, the 2-clause and 3-clause BSD licenses, GPL versions 2 and 3, the Library GPL version 2 and Lesser GPL versions 2.1 and 3, the Mozilla Public License 2.0, the Eclipse Public License 2.0 and the Common Development and Distribution License 1.0.[20]

Free software and other lists

The older term, free software, is defined by the Free Software Foundation (FSF) through four freedoms: to run the program for any purpose (freedom 0), to study and change it (freedom 1), to redistribute copies (freedom 2) and to distribute modified versions (freedom 3). The FSF says that open source rests on a different philosophy and a different practical definition, but that "nearly all open source programs are in fact free".[21] The FSF keeps its own list of licenses, which marks each one as free or nonfree and as compatible or incompatible with the GPL.[22]

The SPDX License List, a Linux Foundation project, assigns each license a short identifier such as MIT or Apache-2.0 and records whether the OSI has approved it and whether the FSF considers it free. A count of the machine-readable file for version 3.29.0 of the list, dated September 16, 2026, gives 740 license identifiers, 32 of them deprecated; 154 are flagged as OSI-approved and 127 as FSF free, or 141 and 109 among the 708 identifiers that are not deprecated. Several licenses, the GNU licenses among them, have more than one identifier.[23]

License families

LicenseSPDX identifierFamilyCondition on modified versionsExpress patent license
MIT LicenseMITPermissiveNone beyond keeping the copyright and permission notice [24]No [24]
3-Clause BSD licenseBSD-3-ClausePermissiveNone beyond keeping notices; the authors' names may not be used for endorsement [25]No [25]
Apache License 2.0Apache-2.0PermissivePass on a copy of the license, keep notices, mark changed files [26]Yes, section 3 [26]
Mozilla Public License 2.0MPL-2.0Weak (file-level) copyleftMPL-covered files stay under the MPL; the larger work may use other terms [27]Yes, section 2.1 [27]
GNU Lesser General Public License v3LGPL-3.0-only or LGPL-3.0-or-laterWeak copyleft for librariesThe library stays under the LGPL; programs that use it may carry other terms [28][29]Yes, through the GPLv3 terms it incorporates [28][30]
GNU General Public License v3GPL-3.0-only or GPL-3.0-or-laterStrong copyleftThe entire work, as a whole, is licensed under the GPL [30]Yes, section 11 [30]
GNU Affero General Public License v3AGPL-3.0-only or AGPL-3.0-or-laterNetwork copyleftAs the GPL, and users who interact with a modified version over a network must be offered its source [31]Yes, section 11 [31]

Expanded article table

Permissive licenses

The MIT License is short. It lets anyone "deal in the Software without restriction", on the condition that the copyright notice and the permission notice are included in all copies or substantial portions.[24] The 3-clause BSD license permits redistribution and use in source and binary forms if the notices are retained and the names of the copyright holder and contributors are not used to endorse derived products.[25] The original BSD license also required advertising that mentioned the software to carry an acknowledgement of the University of California, Berkeley, a clause the university removed in June 1999.[32] The Apache License 2.0, published in January 2004, is longer: redistributors must give recipients a copy of the license and mark the files they changed, and the text contains an express patent license.[26]

The OSI's FAQ explains that software under a non-copyleft license can be used as part of programs distributed under other licenses, proprietary ones included. It also cautions against using "permissive" as the opposite of copyleft, because that usage presents copyleft conditions as restrictions.[4] The FSF calls these licenses "lax, permissive non-copyleft" licenses and, among them, recommends Apache 2.0 for substantial programs because of its patent provisions.[22]

Copyleft licenses

The FSF describes copyleft as a method of making a program free while requiring all modified and extended versions to be free as well. It works through copyright: the author keeps the copyright and grants rights to use, modify and redistribute on the condition that the distribution terms stay unchanged.[33] The GNU Project's implementation is the GPL, which the OSI's FAQ calls a widely used copyleft license.[4] Version 1 is dated February 1989,[34] version 2 June 1991[35] and version 3 June 29, 2007.[30] Version 3 requires anyone who conveys a modified work to license "the entire work, as a whole" under the GPL.[30] The OSI notes that copyleft applies to actual derivatives of a work, and that merely distributing a copyleft program alongside another program does not bring the second one under the copyleft terms.[4]

Three variants adjust the reach of the condition:

  • The GNU Affero General Public License (AGPL), version 3 of which is dated November 19, 2007, is the GPL with one added requirement. Someone who runs a modified version on a server must offer the corresponding source to the users who interact with it over a network.[31][36]
  • The GNU Lesser General Public License (LGPL) is written for libraries. The FSF summarizes the difference from the GPL this way: the LGPL permits use of a library in proprietary programs, while the ordinary GPL makes it available only to free programs.[29]
  • The Mozilla Public License 2.0 uses what Mozilla calls "file-level" copyleft: changes to MPL-covered files must be shared, but those files can be combined with code under other licenses, open or proprietary.[37]

Public-domain dedications

Giving up copyright altogether is a different route from licensing. The OSI's position is that the public domain is not a license and so cannot go through its approval process, and it recommends applying an approved license to software. Creative Commons submitted its CC0 dedication to the OSI in February 2012 and later withdrew it after the review committee could not reach consensus; the most serious concern was a clause stating that no patent rights are waived or licensed.[4] The FSF considers both CC0 and the Unlicense compatible with the GPL but does not recommend CC0 for software, for the same patent reason.[22] The Unlicense is flagged as OSI-approved in the SPDX list.[23] Creative Commons itself recommends against using Creative Commons licenses for software, noting that they contain no specific terms about the distribution of source code and that software licenses often address patent rights.[38]

Patent grants

Copyright permission does not by itself settle whether a user may practice patents that read on the code, and licenses differ on the point. The MIT and BSD texts do not mention patents.[24][25] Under section 3 of the Apache License 2.0, each contributor grants a perpetual, worldwide, royalty-free patent license covering the patent claims that its contribution necessarily infringes. The grant ends for any licensee who files patent litigation alleging that the work infringes.[26] Section 11 of GPL version 3 has each contributor grant a royalty-free license under its essential patent claims,[30] and the Mozilla Public License 2.0 pairs a patent grant in section 2.1 with a termination clause in section 5.2 for licensees who start patent litigation over the software.[27]

Stephen O'Grady of the analyst firm RedMonk wrote in March 2026 that Apache has tended to be the preferred license for commercial open-source use partly because of these provisions, in contrast to the MIT License's silence on patents.[39]

License compatibility

The FSF's GPL FAQ defines two licenses as compatible when code under both can be combined into a larger work in a way that satisfies both at once.[40] Compatibility often runs in one direction only. The Apache Software Foundation puts it this way: Apache 2.0 software can be included in GPL version 3 projects, but GPL version 3 software cannot be included in Apache projects.[41]

CombinationResult
MIT (Expat) or 3-clause BSD code in a GPL workCompatible [22]
Apache 2.0 code in a GPL version 3 workCompatible [22][41]
Apache 2.0 code in a GPL version 2 workNot compatible in the FSF's view, because of the patent termination and indemnification provisions [22][41]
GPL version 3 code in an Apache Software Foundation projectNot accepted; the combined work would have to be distributed under GPL version 3 [41]
Original (4-clause) BSD code with GPL codeIncompatible, because the advertising clause is an added restriction [40]
GPL version 2 only with GPL version 3Incompatible, unless the version 2 code says "version 2 or later" [40]
MPL 2.0 code with GPL, LGPL or AGPL codeCompatible through section 3.3, unless the MPL code is marked "Incompatible With Secondary Licenses" [27][37]
GPL version 3 code with AGPL version 3 codeCan be combined under section 13 of each license [30][31]

Expanded article table

Version choices therefore matter. The Linux kernel, for instance, is provided under GPL version 2 only, with a system-call exception.[42]

Usage

License proliferation was an early concern. The OSI's 2006 committee report recorded three complaints that went under that name: that there were too many licenses to choose among, that some licenses do not work together, and that distributions covered by many licenses are hard to understand.[19]

Interest is concentrated on a few licenses. By the OSI's count of page views from human visitors to its license pages in 2025, MIT drew 1.53 million, Apache 2.0 344,000, the 3-clause and 2-clause BSD licenses 214,000 and 128,000, and GPL versions 2 and 3 76,000 and 55,000.[43] Reviewing repository and package data in March 2026, O'Grady described a long shift from copyleft toward permissive licenses and estimated that permissive licenses became the majority at some point between 2014 and 2017. In his GitHub Archive sample the permissive share fell from 82% in 2022 to 73% in 2025, a change he said might be a sampling artifact. He also cautioned that most hosted repositories, likely 80% or more in the largest source, carry no license at all.[39]

Enforcement

A United States appeals court has treated the terms of an open-source license as conditions enforceable under copyright law. In Jacobsen v. Katzer, decided on August 13, 2008, the United States Court of Appeals for the Federal Circuit held that the terms of the Artistic License, under which a group of developers had published model-railroad software free of charge, were enforceable copyright conditions. It vacated a district court's denial of a preliminary injunction, which had rested on the view that violating the license terms might be a breach of contract but did not create liability for copyright infringement. The court wrote that the absence of payment in open-source licensing should not be presumed to mean an absence of economic consideration.[44] The OSI was among the organizations that filed an amicus brief in support of open-source licensing in the case.[17]

Source-available licenses that are not open source

Several licenses publish source code while withholding rights the OSD requires; the business models behind them are discussed in open core.

LicenseStewardMain restrictionOSI status
Business Source License 1.1MariaDBNon-production use only, unless the licensor adds an Additional Use Grant; each version converts to a Change License on the Change Date or its fourth anniversary, whichever comes first [6]Not approved; the license text says it "is not an Open Source license" [6][23]
Server Side Public LicenseMongoDBBased on GPL version 3; a party offering the software as a service must release the software it uses to run that service under the same license [45]Not approved; submitted to the OSI and withdrawn [45][5]
Elastic License 2.0ElasticNo providing the software to third parties as a hosted or managed service; no circumventing license-key functionality [46]Not approved [23]

Expanded article table

In January 2021 the OSI board called the Server Side Public License a "fauxpen" license and said it is deceptive to describe software under a license the OSI has not approved as open source.[5] O'Grady's 2026 survey found source-available licenses too rare to measure statistically, though strategically relevant because of the projects that use them.[39]

Several companies have moved widely used projects from open-source licenses to licenses of this kind. Elastic announced on January 14, 2021 that, starting with version 7.11, Elasticsearch and Kibana would move from Apache 2.0 to a choice of the Server Side Public License or the Elastic License.[78] HashiCorp announced on August 10, 2023 that future releases of its products would move from the Mozilla Public License 2.0 to the Business Source License 1.1, while its APIs, SDKs and almost all other libraries stayed under the MPL.[79] Redis announced on March 20, 2024 that, starting with Redis 7.4, it would replace the 3-clause BSD license with a choice of its own Redis Source Available License version 2 or the Server Side Public License.[80] Two of the three later added an OSI-approved option alongside the others: Elastic said on August 29, 2024 that it would add the AGPL, and Redis added AGPL version 3 on May 1, 2025, starting with Redis 8.[81][82]

In artificial intelligence

Licenses on AI software

The code used to build and run models is licensed like any other software. The table gives the license in the LICENSE or COPYING file of each project's repository as of November 2026.

ProjectLicenseFamily
PyTorch3-clause BSD [7]Permissive
TensorFlowApache 2.0 [8]Permissive
JAXApache 2.0 [47]Permissive
scikit-learn3-clause BSD [48]Permissive
Hugging Face TransformersApache 2.0 [49]Permissive
llama.cppMIT [50]Permissive
OllamaMIT [51]Permissive
vLLMApache 2.0 [52]Permissive
ComfyUIGPL version 3 [53]Copyleft
AUTOMATIC1111 Stable Diffusion web UIAGPL version 3 [54]Network copyleft

Expanded article table

Why model weights strain the concept

Software licenses assume a work with source code. The OSD defines source code as the preferred form in which a programmer would modify the program.[2] A trained model has no single equivalent, and several problems follow.

The first is what counts as source. The OSAID answers that the preferred form for modifying a machine-learning system has three parts: detailed information about the training data, the complete code used to train and run the system, and the parameters.[9] A release of weights alone, even under an OSI-approved license, lacks the first two, and the OSI describes such "open weights" releases as short of open-source AI.[55]

A second question is whether a software license fits weights. The authors of the Model Openness Framework argue that open-source licenses cover a model's architecture, which is code, but that parameters are data and are better governed by open-data licenses such as CDLA-Permissive-2.0. They write that most permissive software licenses do not refer to data and do not address the modification and redistribution of parameters, a gap they call "a legal gray area that remains untested", while still listing OSI-approved licenses as acceptable for parameters.[56] The Linux Foundation's Matt White has written that models combine components subject to overlapping intellectual-property regimes, including copyright, database rights and trade secrets, which vary across jurisdictions.[15]

A third is whether weights are protected at all, since open-source licenses rest on copyright. Legal scholars Peter Henderson and Mark Lemley argue that model weights and model outputs "are largely not copyrightable, making it unclear whether there is even anything to be licensed".[11] The OSAID takes no position: the OSI's FAQ says the question will become clearer as courts address it, and the definition speaks of parameters being available under "OSI-approved terms" instead of "licenses" for that reason.[57][9]

Outputs and mixed terms raise further problems. The Linux Foundation's submission of OpenMDW to the OSI observed that existing OSI-approved licenses are generally silent about model outputs, while commercial model providers have written terms that restrict them.[58] The OSI reported in November 2026 that some developers publish code under an OSI-approved license while restricting the weights through an acceptable use policy or terms of use, and that an approved license on the code does not by itself make a model meet the OSAID.[59]

Standard software licenses on weights

Many open-weight models are published under ordinary software licenses. The Hugging Face repositories of DeepSeek-R1 and OpenAI's gpt-oss are tagged MIT and Apache 2.0 respectively,[60][61] and Google announced on April 2, 2026 that Gemma 4 was released under Apache 2.0, describing those models as the first in the Gemma family under an OSI-approved license.[62]

O'Grady scanned the roughly 2.9 million models on Hugging Face in May 2026. Almost 70% carried no license. Among those that did, Apache was about 2.5 times as common as MIT, the next most used license; the OpenRAIL family was the largest category that was neither OSI-approved nor specific to one model; and more than two thirds carried an OSI-approved license. He warned that the tags can be wrong, for example where a model tagged Apache was trained using Llama, or where a "Modified MIT License" is neither MIT nor open source.[12] The OSI likewise reported in November 2026 that more models were being released under OSI-approved licenses, particularly MIT and Apache 2.0.[59]

Use-restricted licenses

Responsible AI Licenses (RAIL) contain behavioral-use clauses that permit or restrict specific uses of an AI artifact and, where derivatives are allowed, require downstream use to follow the same restrictions.[63] A Hugging Face blog post of August 31, 2022 presented the OpenRAIL family as AI-specific licenses that allow open access, use and distribution of AI artifacts while requiring responsible use.[64] A February 2024 paper by Daniel McDuff and co-authors counted on the order of 40,000 software and model repositories using such licenses at the end of 2023, and named BLOOM, Llama 2 and Stable Diffusion among the models licensed with behavioral-use clauses.[65]

The RAIL initiative's own FAQ states that OpenRAIL licenses are not open-source licenses under the OSD, because they restrict use of the licensed artifact.[14] The FSF published a critique in April 2026 that calls RAIL licenses nonfree and unethical and argues that licenses restricting how software can be used should be opposed.[66]

Custom model licenses

Other developers write their own terms. The OSI said of the Llama 2 license in July 2023 that it fails OSD criteria 5 and 6, because it restricts commercial use for some users and limits use through an acceptable use policy; it repeated the assessment for the Llama 3 series in February 2025.[67][68] The Llama 4 Community License grants a non-exclusive, non-transferable license, incorporates an acceptable use policy, and requires a licensee whose products or services had more than 700 million monthly active users in the month before the Llama 4 release date to request a license from Meta, which Meta may grant at its sole discretion.[13] The FSF lists the Llama 3.1 license as nonfree.[22]

Hugging Face's license list has dedicated identifiers for the Llama 2 through Llama 4 agreements and for the Gemma Terms of Use, plus a catch-all other value for licenses it does not list.[69] Terms also change between versions of the same model family. O'Grady noted in September 2026 that Moonshot adopted a more restrictive license for Kimi K3 than for its predecessor, and that the 2.4-trillion-parameter Qwen3.8-Max checkpoint was released under what he called a commercially restrictive source-available license.[10] The open-weight license comparison sets out the commercial terms of the most used model licenses, and the list of open-weight models records the license of each release.

Henderson and Lemley question whether restrictive model terms can be enforced. Writing in December 2024, they said that, apart from some account suspensions on platforms, no model creator had tried to enforce such terms with monetary penalties or injunctive relief, and they argued that many of the provisions should be unenforceable because they chill good-faith research and constrain competition.[11]

Licenses written for models

OpenMDW (Open Model, Data and Weights) is a permissive license that the Linux Foundation introduced in 2025 for model releases.[15] It defines "Model Materials" as a model's architecture and parameters together with related data, documentation and software, and it grants permission to deal in them without restriction under all copyright, patent, database and trade secret rights. Its conditions are to keep a copy of the agreement and the notices of origin. The rights end for a licensee who brings a patent or copyright suit alleging that the materials infringe, unless the suit answers one first brought against the licensee, and the license imposes no restrictions on outputs.[70]

The text of version 1.1 was added to the project's repository on May 19, 2026,[83] and the Linux Foundation announced its release on May 28, when NVIDIA said it would adopt the license for future releases of its Cosmos, Isaac GR00T, Ising and Nemotron model families.[71] The Linux Foundation submitted OpenMDW-1.1 to the OSI's license-review list on August 13, 2026.[58] O'Grady wrote in September that the review thread had passed 90 messages and that approval was not certain.[10] On November 10, 2026 the OSI described two AI-specific licenses, ModelGo and OpenMDW, as awaiting its approval.[59] Neither appeared on the OSI's list of approved licenses on November 19, 2026.[1]

Regulation

Legal definitions have begun to depend on the term. Article 53(2) of the EU AI Act exempts providers of general-purpose AI models from some documentation obligations when the model is released under "a free and open-source licence that allows for the access, usage, modification, and distribution of the model" and its parameters, architecture information and usage information are public. The exemption does not apply to models with systemic risk.[72]

The European Commission's guidelines on these obligations, published in July 2025, list restrictions that disqualify a license: limits to non-commercial or research-only use, prohibitions on distribution, usage restrictions triggered by user-scale thresholds, and requirements to obtain separate commercial licenses for specific use cases. The guidelines do allow specific, safety-oriented terms that reasonably restrict use posing a significant risk to public safety, security or fundamental rights, if they are proportionate and non-discriminatory.[73]

The G7's "Vision on AI Openness Opportunities and Shared Language" of May 29, 2026 treats openness as a spectrum with four tiers. It separates "Open Weights AI", released with weights and deployment code under an open-source license, from "Weights Available AI", released under a license with commercial, geographical or use-case restrictions, and its glossary points to the OSI and GNU lists for recognized open-source licenses.[74] Applying the typology to his sample in June 2026, O'Grady found that of 40 openly released models half used an OSI-approved license and half did not, and that none met either of the two open-source tiers.[75]

Criticism of "open" labels

Researchers have questioned how far the software concept transfers. In a 2024 Nature perspective, David Gray Widder, Meredith Whittaker and Sarah Myers West wrote that claims about "open" AI often apply understandings of openness imported from free and open-source software incorrectly, and concluded that openness alone does not disturb the concentration of power in AI.[76] The Model Openness Framework authors attribute part of the mislabeling of models as "open source" to confusion about what open-source licenses were designed to cover, and note that the practice has been called openwashing.[56]

Timeline

DateEvent
1989-02GNU General Public License version 1 [34]
1991-06GPL version 2 [35]
1997-07-05Debian ratifies its Social Contract, which contains the Debian Free Software Guidelines [18]
1998-02"Open source" label adopted; OSI founded; Open Source Definition written [17]
1999-06University of California removes the BSD advertising clause [32]
1999-10OSI has published its first list of approved licenses [17]
2004-01Apache License 2.0 [26]
2007-06-29GPL version 3 and LGPL version 3 [30][28]
2007-11-19AGPL version 3 [31]
2008-08-13Jacobsen v. Katzer decided [44]
2018-10-16MongoDB releases from this date use the Server Side Public License [45]
2021-01-14Elastic announces a move from Apache 2.0 to the Server Side Public License and the Elastic License [78]
2021-01-19OSI board statement that the SSPL is not open source [5]
2022-08-31Hugging Face blog post presents the OpenRAIL licenses [64]
2023-07-20OSI says the Llama 2 license is not open source [67]
2023-08-10HashiCorp announces a move from the Mozilla Public License 2.0 to the Business Source License 1.1 [79]
2024-03-20Redis announces a move from the 3-clause BSD license to source-available licenses [80]
2024-10-28Open Source AI Definition 1.0 [16]
2025-05-22Linux Foundation blog post presents OpenMDW [15]
2025-07-18European Commission publishes guidelines for general-purpose AI model providers [73]
2026-04-02Google announces Gemma 4 under Apache 2.0 [62]
2026-05-28Linux Foundation announces the release of OpenMDW-1.1 [71]
2026-05-29G7 Vision on AI Openness [74]
2026-08-13OpenMDW-1.1 submitted to the OSI for approval [58]

Expanded article table

Continue reading

More from See also

More to read

Topics:AI Policy & RegulationOpen Source AISoftware Development

References

  1. ^1 ^2 ^3Open Source Initiative. "OSI Approved Licenses". opensource.org, accessed November 19, 2026. opensource.org/licenses
  2. ^1 ^2 ^3 ^4Open Source Initiative. "The Open Source Definition" (version 1.9). opensource.org, last modified February 16, 2024. opensource.org/osd
  3. ^1 ^2 ^3Open Source Initiative. "The License Review process". opensource.org, last modified March 13, 2024. opensource.org/...review-process
  4. ^1 ^2 ^3 ^4 ^5 ^6Open Source Initiative. "Frequently Answered Questions". opensource.org, last modified January 21, 2025. opensource.org/faq
  5. ^1 ^2 ^3 ^4OSI Board of Directors. "The SSPL is Not an Open Source License". Open Source Initiative, January 19, 2021. opensource.org/...pl-is-not-an-open-source-license
  6. ^1 ^2 ^3MariaDB. "Business Source License 1.1". mariadb.com, accessed November 19, 2026. mariadb.com/bsl11
  7. ^1 ^2PyTorch. "LICENSE". GitHub repository pytorch/pytorch, accessed November 19, 2026. raw.githubusercontent.com/...LICENSE
  8. ^1 ^2TensorFlow. "LICENSE". GitHub repository tensorflow/tensorflow, accessed November 19, 2026. raw.githubusercontent.com/...LICENSE
  9. ^1 ^2 ^3 ^4Open Source Initiative. "The Open Source AI Definition - 1.0". opensource.org, accessed November 19, 2026. opensource.org/...open-source-ai-definition
  10. ^1 ^2 ^3O'Grady, Stephen. "How to Think About Open Weight Models". RedMonk tecosystems, September 3, 2026. redmonk.com/...open-weight-models
  11. ^1 ^2 ^3Henderson, Peter; Lemley, Mark A. "The Mirage of Artificial Intelligence Terms of Use Restrictions". arXiv:2412.07066, December 10, 2024 (forthcoming, Indiana Law Journal). arxiv.org/...2412.07066
  12. ^1 ^2O'Grady, Stephen. "License Distribution on Hugging Face". RedMonk tecosystems, May 12, 2026. redmonk.com/...hugging-face-licensing
  13. ^1 ^2Meta. "Llama 4 Community License Agreement". llama.com, accessed November 19, 2026. llama.com/...license
  14. ^1 ^2 ^3Responsible AI Licenses (RAIL). "FAQ". licenses.ai, accessed November 19, 2026. licenses.ai/faq-2
  15. ^1 ^2 ^3 ^4White, Matt. "The Open Source Legacy and AI's Licensing Challenge". The Linux Foundation, May 22, 2025. linuxfoundation.org/...and-ais-licensing-challenge
  16. ^1 ^2Open Source Initiative. "The Open Source Initiative Announces the Release of the Industry's First Open Source AI Definition". opensource.org, October 28, 2024. opensource.org/...-first-open-source-ai-definition
  17. ^1 ^2 ^3 ^4 ^5 ^6 ^7Open Source Initiative. "History of the Open Source Initiative". opensource.org, last modified June 3, 2025. opensource.org/history
  18. ^1 ^2Debian Project. "Debian Social Contract" (version 1.0 ratified July 5, 1997; version 1.2 ratified October 1, 2022). debian.org. debian.org/social_contract
  19. ^1 ^2Open Source Initiative. "Report of License Proliferation Committee and draft FAQ". opensource.org, page created July 31, 2006, last modified January 25, 2023. opensource.org/proliferation-report
  20. ^Open Source Initiative. "OSI Approved Licenses" (category filter: Popular / Strong Community). opensource.org, accessed November 19, 2026. opensource.org/licenses
  21. ^Free Software Foundation. "What is Free Software?". GNU Project, accessed November 19, 2026. gnu.org/...free-sw
  22. ^1 ^2 ^3 ^4 ^5 ^6 ^7Free Software Foundation. "Various Licenses and Comments about Them". GNU Project, accessed November 19, 2026. gnu.org/...license-list
  23. ^1 ^2 ^3 ^4SPDX. "SPDX License List", version 3.29.0, September 16, 2026 (counts taken from the machine-readable file at spdx.org/licenses/licenses.json). spdx.org/licenses
  24. ^1 ^2 ^3 ^4Open Source Initiative. "The MIT License". opensource.org, accessed November 19, 2026. opensource.org/...mit
  25. ^1 ^2 ^3 ^4Open Source Initiative. "The 3-Clause BSD License". opensource.org, accessed November 19, 2026. opensource.org/...bsd-3-clause
  26. ^1 ^2 ^3 ^4 ^5Apache Software Foundation. "Apache License, Version 2.0". apache.org, January 2004. apache.org/...LICENSE-2.0
  27. ^1 ^2 ^3 ^4Mozilla. "Mozilla Public License, version 2.0". mozilla.org, accessed November 19, 2026. mozilla.org/...2.0
  28. ^1 ^2 ^3Free Software Foundation. "GNU Lesser General Public License", version 3, June 29, 2007. GNU Project. gnu.org/...lgpl-3.0
  29. ^1 ^2Free Software Foundation. "Why you shouldn't use the Lesser GPL for your next library". GNU Project, accessed November 19, 2026. gnu.org/...why-not-lgpl
  30. ^1 ^2 ^3 ^4 ^5 ^6 ^7 ^8Free Software Foundation. "GNU General Public License", version 3, June 29, 2007. GNU Project. gnu.org/...gpl-3.0
  31. ^1 ^2 ^3 ^4 ^5Free Software Foundation. "GNU Affero General Public License", version 3, November 19, 2007. GNU Project. gnu.org/...agpl-3.0
  32. ^1 ^2Stallman, Richard. "The BSD License Problem". GNU Project, accessed November 19, 2026. gnu.org/...bsd
  33. ^Free Software Foundation. "What is Copyleft?". GNU Project, accessed November 19, 2026. gnu.org/...copyleft
  34. ^1 ^2Free Software Foundation. "GNU General Public License, version 1", February 1989. GNU Project. gnu.org/...gpl-1.0
  35. ^1 ^2Free Software Foundation. "GNU General Public License, version 2", June 1991. GNU Project. gnu.org/...gpl-2.0
  36. ^Free Software Foundation. "Why the GNU Affero GPL". GNU Project, accessed November 19, 2026. gnu.org/...why-affero-gpl
  37. ^1 ^2Mozilla. "MPL 2.0 FAQ". mozilla.org, last updated January 30, 2024. mozilla.org/...FAQ
  38. ^Creative Commons. "Frequently Asked Questions" ("Can I apply a Creative Commons license to software?"). creativecommons.org, accessed November 19, 2026. creativecommons.org/faq
  39. ^1 ^2 ^3O'Grady, Stephen. "The State of Open Source Licensing in 2026". RedMonk tecosystems, March 25, 2026. redmonk.com/...open-source-licensing-2026
  40. ^1 ^2 ^3Free Software Foundation. "Frequently Asked Questions about the GNU Licenses". GNU Project, accessed November 19, 2026. gnu.org/...gpl-faq
  41. ^1 ^2 ^3 ^4Apache Software Foundation. "Apache License v2.0 and GPL Compatibility". apache.org, accessed November 19, 2026. apache.org/...GPL-compatibility
  42. ^The Linux Kernel documentation. "Linux kernel licensing rules". docs.kernel.org, accessed November 19, 2026. docs.kernel.org/...license-rules
  43. ^Vidal, Nick. "Top Open Source licenses in 2025". Open Source Initiative, December 17, 2025. opensource.org/...top-open-source-licenses-in-2025
  44. ^1 ^2United States Court of Appeals for the Federal Circuit. Jacobsen v. Katzer, No. 2008-1001, decided August 13, 2008. cafc.uscourts.gov/...08-1001.pdf
  45. ^1 ^2 ^3MongoDB. "Server Side Public License FAQ". mongodb.com, accessed November 19, 2026. mongodb.com/...faq
  46. ^Elastic. "Elastic License 2.0". elastic.co, accessed November 19, 2026. elastic.co/...elastic-license
  47. ^JAX. "LICENSE". GitHub repository jax-ml/jax, accessed November 19, 2026. raw.githubusercontent.com/...LICENSE
  48. ^scikit-learn developers. "COPYING". GitHub repository scikit-learn/scikit-learn, accessed November 19, 2026. raw.githubusercontent.com/...COPYING
  49. ^The Hugging Face team. "LICENSE". GitHub repository huggingface/transformers, accessed November 19, 2026. raw.githubusercontent.com/...LICENSE
  50. ^The ggml authors. "LICENSE". GitHub repository ggml-org/llama.cpp, accessed November 19, 2026. raw.githubusercontent.com/...LICENSE
  51. ^Ollama. "LICENSE". GitHub repository ollama/ollama, accessed November 19, 2026. raw.githubusercontent.com/...LICENSE
  52. ^vLLM. "LICENSE". GitHub repository vllm-project/vllm, accessed November 19, 2026. raw.githubusercontent.com/...LICENSE
  53. ^Comfy Org. "LICENSE". GitHub repository Comfy-Org/ComfyUI (formerly comfyanonymous/ComfyUI), accessed November 19, 2026. raw.githubusercontent.com/...LICENSE
  54. ^AUTOMATIC1111. "LICENSE.txt". GitHub repository AUTOMATIC1111/stable-diffusion-webui, accessed November 19, 2026. raw.githubusercontent.com/...LICENSE.txt
  55. ^Open Source Initiative. "Open Weights: not quite what you've been told". opensource.org, accessed November 19, 2026. opensource.org/...open-weights
  56. ^1 ^2White, Matt; Haddad, Ibrahim; Osborne, Cailean; Liu, Xiao-Yang Yanglet; Abdelmonsef, Ahmed; Varghese, Sachin; Le Hors, Arnaud. "The Model Openness Framework: Promoting Completeness and Openness for Reproducibility, Transparency, and Usability in Artificial Intelligence". arXiv:2403.13784, March 20, 2024 (version 6, October 18, 2024). arxiv.org/...2403.13784
  57. ^Open Source Initiative. "OSAID FAQs". opensource.org, accessed November 19, 2026. opensource.org/...faq
  58. ^1 ^2 ^3Dolan, Michael. "For Approval: OpenMDW License Agreement, versions 1.1 (OpenMDW-1.1)". OSI license-review mailing list, August 13, 2026. lists.opensource.org/...006125
  59. ^1 ^2 ^3Toscano, Gabriel. "Open Source AI Salons: Shaping the OSAID, Together". Open Source Initiative, November 10, 2026. opensource.org/...alons-shaping-the-osaid-together
  60. ^Hugging Face. "deepseek-ai/DeepSeek-R1" (Hub API model record; license tag mit). Accessed November 19, 2026. huggingface.co/...DeepSeek-R1
  61. ^Hugging Face. "openai/gpt-oss-120b" (Hub API model record; license tag apache-2.0). Accessed November 19, 2026. huggingface.co/...gpt-oss-120b
  62. ^1 ^2Castelly, Nia; casari, amanda; Lacombe, Olivier. "Gemma 4: Expanding the Gemmaverse with Apache 2.0". Google Open Source Blog, April 2, 2026. opensource.googleblog.com/...averse-with-apache-20
  63. ^Responsible AI Licenses (RAIL). "Responsible AI Licenses". licenses.ai, accessed November 19, 2026. licenses.ai
  64. ^1 ^2Muñoz Ferrandis, Carlos. "OpenRAIL: Towards open and responsible AI licensing frameworks". Hugging Face blog, August 31, 2022. huggingface.co/...open_rail
  65. ^McDuff, Daniel; Korjakow, Tim; Cambo, Scott; Benjamin, Jesse Josua; Lee, Jenny; Jernite, Yacine; Muñoz Ferrandis, Carlos; Gokaslan, Aaron; Tarkowski, Alek; Lindley, Joseph; Cooper, A. Feder; Contractor, Danish. "On the Standardization of Behavioral Use Clauses and Their Adoption for Responsible Licensing of AI". arXiv:2402.05979, February 7, 2024. arxiv.org/...2402.05979
  66. ^Siewicz, Krzysztof. "RAIL: Nonfree and unethical". Free Software Foundation, April 22, 2026. fsf.org/...rail-are-nonfree-and-unethical
  67. ^1 ^2 ^3Maffulli, Stefano. "Meta's LLaMa license is not Open Source". Open Source Initiative, July 20, 2023. opensource.org/...ama-2-license-is-not-open-source
  68. ^1 ^2Maris, Jordan. "Meta's LLaMa license is still not Open Source". Open Source Initiative, February 18, 2025. opensource.org/...license-is-still-not-open-source
  69. ^Hugging Face. "Licenses". Hugging Face Hub documentation, accessed November 19, 2026. huggingface.co/...repositories-licenses
  70. ^OpenMDW project. "OpenMDW License Agreement, version 1.1 (OpenMDW-1.1)". GitHub repository OpenMDW/OpenMDW, accessed November 19, 2026. raw.githubusercontent.com/...LICENSE.OpenMDW-1.1
  71. ^1 ^2The Linux Foundation. "Linux Foundation Releases OpenMDW-1.1; NVIDIA Adopts OpenMDW for Cosmos, Isaac GR00T, Ising and Nemotron, AI Model Families". May 28, 2026. linuxfoundation.org/...-nemotron-ai-model-families
  72. ^European Union. "Article 53: Obligations for Providers of General-Purpose AI Models", Regulation (EU) 2024/1689. EU Artificial Intelligence Act explorer, accessed November 19, 2026. artificialintelligenceact.eu/...53
  73. ^1 ^2European Commission. "Commission Guidelines on the scope of the obligations for providers of general-purpose AI models established by Regulation (EU) 2024/1689 (AI Act)", section 4.2.1. Published July 18, 2025; text C(2025) 7719 final dated November 19, 2025. digital-strategy.ec.europa.eu/...dels-under-ai-act
  74. ^1 ^2G7 Digital and Technology Ministers. "G7 Vision on AI Openness Opportunities and Shared Language". May 29, 2026. G7 Information Centre, University of Toronto. g7.utoronto.ca/...260529-vision
  75. ^O'Grady, Stephen. "The G7 on Open Source vs Open Weights". RedMonk tecosystems, June 2, 2026. redmonk.com/...g7-open-weights
  76. ^Widder, David Gray; Whittaker, Meredith; West, Sarah Myers. "Why 'open' AI systems are actually closed, and why this matters". Nature 635, 827-833, November 27, 2024. nature.com/...s41586-024-08141-1
  77. ^Open Source Initiative. "2026-09-24 Board Meeting" (minutes, approved October 23, 2026). opensource.org, published November 13, 2026. opensource.org/...2026-09-24
  78. ^1 ^2Banon, Shay. "Doubling down on open, Part II". Elastic blog, January 14, 2021. elastic.co/...licensing-change
  79. ^1 ^2Dadgar, Armon. "HashiCorp adopts Business Source License". HashiCorp blog, August 10, 2023 (archived copy of January 2, 2025). web.archive.org/...-adopts-business-source-license
  80. ^1 ^2Redis. "Redis Adopts Dual Source-Available Licensing". Redis blog, March 20, 2024. redis.io/...adopts-dual-source-available-licensing
  81. ^Banon, Shay. "Elasticsearch Is Open Source. Again!". Elastic blog, August 29, 2024. elastic.co/...elasticsearch-is-open-source-again
  82. ^Trollope, Rowan. "Redis is now available under the AGPLv3 open source license". Redis blog, May 1, 2025. redis.io/...agplv3
  83. ^OpenMDW project. Commit history of "1.1/LICENSE.OpenMDW-1.1" (commit "Add OpenMDW-1.1 and make conforming updates", May 19, 2026 UTC). GitHub repository OpenMDW/OpenMDW, accessed November 19, 2026. github.com/...LICENSE.OpenMDW-1.1

Improve this article

Add missing citations, update stale details, or write a clearer explanation. Anyone can edit: changes go live when you publish, and every edit is checked by an editor.

1 revision · v1 · 6,838 words · full history

Fact-checks are independent of edits: a reviewer re-verifies the article against its sources and stamps the date. How we verify

Research and drafting on this wiki are AI-assisted, under named human editorial standards. How AI is used here

Reviewer note: Independent fact-check before publication on November 19, 2026: 168 claims checked against 97 cited and independent sources; 1 material and 12 minor corrections applied before publication.

Cite this page: AI Wiki. "Open-source license." aiwiki.ai, updated 18 Nov 2026, fact-checked 18 Nov 2026. CC BY 4.0. https://aiwiki.ai/wiki/open_source_license

Edit article

What links here