GNU General Public License
The GNU General Public License (GNU GPL or GPL) is a family of free software licenses published by the Free Software Foundation (FSF) that let anyone run, study, copy, modify and redistribute a program, on the condition that copies and modified versions passed on to others carry the same freedoms and come with source code.[1][4] This condition is called copyleft: the FSF describes it as a way of using copyright that requires all modified and extended versions of a program to be free as well.[4] Three versions of the GPL exist: version 1 (February 1989), version 2 (June 1991) and version 3 (29 June 2007).[3][2][1] The family also includes the GNU Lesser General Public License (LGPL), a weaker copyleft written for libraries, and the GNU Affero General Public License (AGPL), which adds a source-code obligation for software that users reach over a network.[4][9][10][12]
The GPL is the license of the Linux kernel (version 2 only) and of most GNU software.[16][5] In AI, several widely used tools carry GPL-family licenses, including ComfyUI, the AUTOMATIC1111 Stable Diffusion web UI and Ultralytics YOLO.[24][25][28] The FSF has said that its criteria for a free machine learning application would cover training data and model parameters as well as code.[20]
Overview
| Property | GNU GPL |
|---|---|
| Publisher | Free Software Foundation |
| Versions | 1.0 (February 1989), 2.0 (June 1991), 3.0 (29 June 2007) |
| Type | Copyleft free software license |
| SPDX identifiers | GPL-1.0-only, GPL-1.0-or-later, GPL-2.0-only, GPL-2.0-or-later, GPL-3.0-only, GPL-3.0-or-later |
| OSI approved | Yes (v2 and v3) |
| Source required with binaries | Yes |
| Modified versions licensed under | The same license |
| Express patent license | Version 3 only |
| Related licenses | LGPL (weaker copyleft), AGPL (network copyleft) |
Sources: license texts and the SPDX License List.[1][2][3][17]
History
Origins in GNU Emacs
Richard Stallman left his job at MIT in January 1984 to start writing software for the GNU project, and he founded the Free Software Foundation in 1985.[5] In his account of the project, he writes that GNU needed distribution terms that would stop its software from being turned into proprietary software, and that the method chosen was copyleft. He took the word from a letter that Don Hopkins mailed him in 1984 or 1985, whose envelope carried a saying that paired "copyleft" with the phrase "all rights reversed."[5]
The license that became the GPL began as a program-specific license for GNU Emacs, which Stallman released in 1985. According to Sam Williams' biography Free as in Freedom, it let users modify GNU Emacs as long as they published their modifications and kept derivative works under the same terms.[6] Other programmers soon wanted to reuse it: in November 1986 John Gilmore emailed Stallman suggesting that "EMACS" be replaced in the license with "SOFTWARE" or a similar word. Williams writes that Stallman, then working on a debugger, removed the Emacs-specific references and turned the text into a general license for GNU software, which became the GNU General Public License.[6]
Versions 1 and 2
Version 1 is dated February 1989.[3] Its preamble set out the political aim that the later versions kept: to guarantee users the freedom to share and change free software, to make sure they receive source code or can get it, and to forbid anyone to deny them those rights.[3] Version 2 followed in June 1991.[2] According to the FSF, Stallman wrote both versions with legal advice from the firm Perkins, Smith & Cohen.[7]
Version 2 added two sections that version 1 lacks. Section 7 says that if a court order, patent claim or other obligation prevents a distributor from meeting the license's conditions, the distributor may not distribute the program at all.[2] Section 8 lets a copyright holder exclude countries where distribution is restricted by patents or copyrighted interfaces.[2][3] Like version 1, it let authors offer their program under "any later version" of the license, so that users could choose newer FSF versions.[2][3]
Linus Torvalds switched the Linux kernel from his earlier license to the GPL with version 0.12, which Williams describes as the first release of Linux to include a fully integrated version of the GNU C Compiler.[6] The FSF dates this re-release to 1992 and describes it as the step that, combined with GNU, produced a complete free operating system for PCs.[7]
Version 3
Stallman began revising the license in 2005, and in January 2006 the FSF started a public review process with legal advice from the Software Freedom Law Center.[7] The FSF released version 3 on 29 June 2007, after four published drafts in eighteen months and thousands of public comments.[7][8] In its announcement the FSF called the GPL "the world's most popular free software license" and stated that "almost three quarters of all free software packages" used it; both statements were the FSF's own claims at the time.[7]
An FSF guide to the new version, written by Brett Smith, names three threats that version 3 was meant to answer:[8]
- Tivoization: devices that run GPL software but use hardware locks so that the owner cannot run modified versions.
- Laws prohibiting free software: legislation such as the US Digital Millennium Copyright Act and the European Union Copyright Directive, which make it a crime to write or share software that can break digital restrictions.
- Discriminatory patent deals: the guide cites Microsoft's promise not to sue free software users for patent infringement only if they obtained the software from a vendor paying Microsoft.
The FSF said that more than fifteen GNU programs would move to version 3 on the day of release.[7] The press release also noted that the licensing of Linux was for its developers to decide.[7] The kernel has stayed on version 2: its documentation states that it is provided under the GNU General Public License version 2 only, with an explicit exception for the system-call interface.[16]
How the license works
Freedoms and conditions
The GPL grants permission to run, copy, modify and distribute the program. Version 3 states that it "explicitly affirms your unlimited permission to run the unmodified Program", and that making and running copies that are not conveyed to others carries no conditions.[1] Distributors may charge any price for copies.[1][15] The conditions apply when a program is passed on: a distributor must keep copyright and warranty notices intact, give recipients a copy of the license, and license any modified version "as a whole" under the same terms.[1][2]
Copyleft is what separates the GPL from permissive licenses such as the MIT License and the Apache License, which let a distributor ship modified versions under proprietary terms. The FSF's essay on copyleft explains the reasoning: if a program is simply placed in the public domain, a middleman can make changes and distribute the result as a proprietary product, so the people who receive that version do not get the freedoms the original author intended.[4]
Private modification is allowed. The FSF's FAQ says the GPL does not require a modified version to be released, and that a company may modify a GPL program and use it internally without distributing it. Once the modified version is released to the public, its source must be made available to its users under the GPL.[15]
Source code
Both versions define source code as "the preferred form of the work for making modifications to it."[1][2] Version 2 required anyone distributing a binary to include the source, or a written offer valid for at least three years to supply it at no more than the cost of distribution.[2] Version 3 keeps that structure but adds ways to provide "Corresponding Source", including network download and peer-to-peer transfer, and defines the term to include the scripts needed to build, install and run the work.[1]
For "User Products" (consumer goods and things designed for a dwelling), version 3 also requires "Installation Information": the keys or procedures needed to install modified software on the device. The requirement does not apply if nobody, including the manufacturer, can install modified code, for example when the software is in ROM.[1] This is the license's answer to tivoization.[8]
Combined works, linking and aggregation
The GPL's reach depends on what counts as a single work. The FSF's position is that linking a GPL program with other modules, statically or dynamically, makes a combined work, so the GPL covers the whole combination.[15] By contrast, an "aggregate" (separate programs that are merely distributed together on the same medium) does not bring the other programs under the GPL.[1][15] The FAQ acknowledges that the line between two programs and one program with two parts "is a legal question, which ultimately judges will decide", and suggests looking at both the communication mechanism (pipes, sockets and command-line arguments versus shared address space) and what information is exchanged.[15]
The license does not, in general, cover a program's output. The FSF's FAQ says that the output of a program is not normally covered by the copyright on the program's code, with exceptions when the output copies substantial parts of the program itself, such as text or art built into it.[15] Version 3 states the same principle: the output of a covered work is covered only if its content is itself a covered work.[1]
Patents, anti-circumvention and termination
Version 2 has no express patent license; it deals with patents through section 7 and a preamble statement that any patent must be licensed for everyone's free use or not licensed at all.[2] Version 3 adds an express patent license: each contributor grants recipients a royalty-free license under the contributor's "essential patent claims."[1] It also bars a distributor from conveying the program if it pays a software distributor under an arrangement in which that distributor grants a discriminatory patent license to some of the recipients, unless the arrangement was made before 28 March 2007.[1]
Section 3 of version 3 says that no covered work counts as an effective technological protection measure under laws that implement article 11 of the 1996 WIPO Copyright Treaty, and that a distributor waives any power to forbid circumvention when users exercise their rights under the license.[1] The FSF's guide stresses that this neutralizes such laws for GPL software without forbidding digital rights management features.[8]
Termination also changed. Under version 2, any distribution outside the license's terms automatically ends the violator's rights.[2] Version 3 adds a cure period: rights are restored provisionally once the violation stops, become permanent if the copyright holder does not give notice of the violation within 60 days after it stops, and are restored permanently for a first-time violator who fixes the problem within 30 days of notice.[1]
Version choice
Both versions let a program specify a version "or any later version", in which case the recipient may follow that version or any later one the FSF publishes. A program that names no version may be used under any version ever published.[1][2] Version 3 adds that a program may designate a proxy who can approve future versions.[1] The FSF's FAQ explains that code under GPL version 2 only cannot be combined with GPLv3 code, while code under "version 2 or later" can, because version 3 is one of the options it permits.[15]
The GPL family
The FSF describes the GPL as the specific implementation of copyleft it uses for most GNU software, and it publishes related copyleft licenses for particular situations.[4][5]
| License | Current version | Main difference from the GPL |
|---|---|---|
| GNU GPL | 3 (29 June 2007) | Baseline copyleft |
| GNU LGPL | 3 (29 June 2007) | Allows proprietary programs to link to the library |
| GNU AGPL | 3 (19 November 2007) | Modified versions offered over a network must offer their source to users |
| GNU FDL | 1.3 (3 November 2008) | Copyleft for manuals and documentation |
Sources: license texts and the FSF's copyleft page.[1][10][12][33][4]
Lesser GPL
The LGPL's predecessor was the GNU Library General Public License, version 2. Version 2.1 (February 1999) was the first released version of the Lesser GPL, and its header says it counts as the successor of the library license, hence the number 2.1.[9] Its preamble says the name reflects that it "does Less to protect the user's freedom" than the ordinary GPL, and that the FSF uses it for certain libraries to permit linking them into non-free programs.[9] LGPL version 3 is written as the text of GPLv3 plus a set of additional permissions.[10]
The FSF treats the choice as strategy. In "Why you shouldn't use the Lesser GPL for your next library", it argues that the ordinary GPL gives free software developers an advantage when a library offers a unique capability, and that the LGPL makes sense when the same features are readily available to proprietary developers through other libraries. That reasoning is why the GNU C library uses the LGPL.[11] Under the FSF's reading, static linking against an LGPL library requires providing the application in a form that lets users relink it with a modified library, while dynamic linking against a copy already on the user's computer does not require shipping the library's source.[15]
Affero GPL
The first Affero General Public License was GPL version 2 with an extra section, 2(d), that Affero added with the FSF's approval to cover programs distributed through web services; the FSF lists it as copyleft but incompatible with the GPL and superseded by the GNU AGPL version 3.[14]
The GNU AGPL version 3, dated 19 November 2007, adds one requirement to GPLv3. Section 13 says that if you modify the program, your modified version "must prominently offer all users interacting with it remotely through a computer network" an opportunity to get its Corresponding Source from a network server at no charge.[12] The FSF explains the reason: a developer who modifies a server program and only runs it on a server never distributes copies, so under the ordinary GPL the changes need never be shared.[13] GPLv3 itself says that mere interaction with a user over a network, without transferring a copy, is not "conveying."[1] Section 13 of each license allows code under the two licenses to be combined in one program.[1][12]
The FSF has said the AGPL does not solve what it calls "Service as a Software Substitute", since receiving a server program's source does not give users control over computing done on someone else's server.[13]
Compatibility
The FSF maintains a list of licenses with its judgment of whether each is compatible with the GPL.[14] Notable entries include:
| License | Compatible with GPLv2 | Compatible with GPLv3 | Note |
|---|---|---|---|
| GPLv2 only | Yes | No | "Version 2 or later" code can be used under v3[15] |
| Apache License 2.0 | No | Yes | Incompatible with v2 because of its patent termination and indemnification terms[14] |
| Expat (MIT) | Yes | Yes | Lax permissive license, compatible with the GNU GPL[14] |
| Affero GPL v1 | No | No | Superseded by AGPLv3[14] |
The incompatibility between GPLv2 and GPLv3 follows from their different terms. The FSF gives the example of termination, where version 3 is more lenient than version 2, so combining code under the two would violate section 6 of GPLv2.[15]
Enforcement and court cases
Because the GPL is a copyright license, a distributor who does not follow its terms has no other permission to copy or distribute the program, which version 2 states directly.[2] US courts have also considered whether the GPL works as a contract.
In Artifex Software v. Hancom, Artifex offered its Ghostscript PDF interpreter under a commercial license and, alternatively, under a GNU license (the Affero GPL, according to one summary of the case). Hancom, a South Korean company, incorporated Ghostscript into its Hancom Office suite, and Artifex sued for breach of contract and copyright infringement. In 2017 Judge Jacqueline Scott Corley of the US District Court for the Northern District of California denied Hancom's motion to dismiss. The court rejected the argument that there was no contract because Hancom never signed the GPL, pointing to the license's statement that a user who does not obtain a commercial license agrees to its terms.[22][23] A later ruling that year let a jury use the value of the commercial license as a basis for damages, and the parties settled confidentially.[22]
In October 2021 the Software Freedom Conservancy (SFC) sued Vizio in the Superior Court of California for Orange County, alleging that the television maker had refused, after repeated requests, to provide source code under GPLv2 and LGPLv2.1 for the software on which its SmartCast platform is built. SFC asked for specific performance and argued that it could enforce the licenses as a third-party beneficiary. On 29 December 2023 the court denied Vizio's motion for summary judgment, holding that the contract claim was not preempted by the Copyright Act and that whether SFC is a third-party beneficiary was a triable issue. SFC has described it as "the first case that focuses on the rights of individual consumers as third-party beneficiaries of the GPL."[21]
Later rulings split the issues. According to a May 2026 summary by the law firm Baker Botts, a December 2025 order sided with Vizio on a narrower question, finding that GPLv2 requires a distributor to share source code but does not require it to permit reinstallation of modified code or to keep the device working after such modification; SFC said it had never argued for that requirement and called the ruling irrelevant. In February 2026 the judge ruled that the case must go to trial because factual disputes remained, both on whether a buyer can enforce the licenses and on SFC's separate claim that Vizio made a direct promise to provide source code when an SFC employee requested it. Baker Botts reported that trial was scheduled for August 2026.[32] The summary also notes that GPLv3, unlike GPLv2, does require installation information for consumer devices.[32][1]
Use in AI software and models
AI projects under GPL-family licenses
Several widely used AI applications and tools are under GPL-family terms, though many others are not; llama.cpp, for example, is MIT-licensed.[29]
| Project | Field | License |
|---|---|---|
| ComfyUI | Node-graph interface for generating images, video, audio and 3D | GPLv3[24] |
| AUTOMATIC1111 Stable Diffusion web UI | Browser interface for Stable Diffusion | AGPLv3[25] |
| Fooocus | Image generation software | GPLv3[26] |
| TextGen (oobabooga, formerly text-generation-webui) | Desktop app for running LLMs locally | AGPLv3[27] |
| Ultralytics YOLO | Computer vision models and library | AGPLv3, with a separate commercial license[28][19] |
| R | Software environment for statistical computing | GPL-2 or GPL-3[30] |
| Weka | Java machine learning workbench | GNU GPL[31] |
Some vendors offer the same code under the AGPL and under a paid license, an arrangement known as dual licensing.[23] Ultralytics' licensing page tells users of its YOLO code, models or fine-tuned models to either open-source their entire project under AGPL-3.0 or buy an Ultralytics Enterprise License. The company says this applies even to internal use and to models trained from scratch, and that in its guidance compliance includes publishing model weights "where applicable."[19] That is the company's own reading of the license. The FSF's FAQ describes the AGPL's trigger as offering a modified version to users over a network, and says that private, internal modification is permitted under the GPL.[15]
Model weights and the source-code question
The GPL was written for software, and its key obligation depends on the definition of source code as "the preferred form of the work for making modifications to it."[1] The FSF's FAQ says the GPL can be applied to any kind of work as long as it is clear what that source code is.[15] The license text does not mention trained neural network weights.
In October 2024 the FSF announced that it was preparing criteria for "free machine learning applications". The announcement notes that model parameters are produced by running training software over training data but "are not necessarily the result of translating anything written by a human author", so training data "is not the 'source code' of model parameters in the usual sense."[20] The FSF stated that an ML application cannot be called free unless its software, its training data and the scripts that process that data all respect the four freedoms, and that granting the four freedoms may also require releasing the model parameters with permission to use and redistribute them and modified versions of them.[20] At the time of that announcement, the working group had reached its conclusion and was drafting the exact text of the definition.[20]
These questions sit alongside the separate debate over open-source AI, the Open Source AI Definition published by the Open Source Initiative, and the custom licenses used for many open-weight models, such as the Llama Community License and OpenRAIL. Those model licenses are not GPL-family licenses.
Hosted models and the network gap
Many AI systems are offered as hosted services rather than distributed as software. Under GPLv3, running a modified program on a server for users who interact with it, without transferring a copy, is not conveying, so it triggers no source obligation.[1][15] The FSF's FAQ uses the example of a company running a modified GPL program on a website, which does not have to release its changes; the answer differs if the program is under the AGPL.[15] Some AI tools with browser-based interfaces, such as the AUTOMATIC1111 web UI, use the AGPL, under which a modified version must offer its source to users who interact with it over a network.[25][12]
Model hubs and license metadata
The Hugging Face Hub lets repository owners declare a license in the card metadata. Its list of identifiers includes gpl-2.0, gpl-3.0, lgpl-2.1, lgpl-3.0 and agpl-3.0, alongside permissive, Creative Commons and AI-specific licenses.[18] The SPDX License List, used for machine-readable license tags in software, distinguishes "-only" from "-or-later" variants (for example GPL-3.0-only and GPL-3.0-or-later) and marks the older identifiers without the suffix as deprecated.[17]
Continue reading
- MIT LicenseThe MIT License is a short, permissive software license. It grants broad permission to use, copy, modify, merge, publish, distribute, sublicense, and sell covered software, subject to one express preservation…Mentioned 4 times above
- Apache License 2.0The Apache License, Version 2.0 is a permissive open source software license published by the Apache Software Foundation (ASF) in January 2004 and approved by the ASF board on January 21, 2004.Mentioned twice above
- Open Source AI DefinitionThe Open Source AI Definition (OSAID) is a document published by the Open Source Initiative (OSI) that states what an artificial intelligence system must make available, and under what termsListed in See also
- BSD licensesThe BSD licenses are a family of short, permissive software licenses that descend from the terms the University of California, Berkeley used to distribute the Berkeley Software Distribution (BSD)Listed in See also
- Creative Commons licensesCreative Commons licenses are a set of standardized public copyright licenses, published by the nonprofit organization Creative Commons, that let a creator grant the public permission to copy, share and in…Listed in See also
- Open-Weight LLM License ComparisonAs of November 2026, the most widely used licenses that put no user, revenue or use conditions on commercial use of open-weight LLMs are two standard, OSI-approved ones: Apache-2.0 (Alibaba's Qwen3, most of…Listed in See also
More from See also
More to read
References
- ^1 ^2 ^3 ^4 ^5 ^6 ^7 ^8 ^9 ^10 ^11 ^12 ^13 ^14 ^15 ^16 ^17 ^18 ^19 ^20 ^21 ^22 ^23Free Software Foundation. "GNU General Public License, version 3". GNU Project, 29 June 2007. gnu.org/...gpl-3.0.en
- ^1 ^2 ^3 ^4 ^5 ^6 ^7 ^8 ^9 ^10 ^11 ^12 ^13Free Software Foundation. "GNU General Public License, version 2". GNU Project, June 1991. gnu.org/...gpl-2.0.en
- ^1 ^2 ^3 ^4 ^5 ^6Free Software Foundation. "GNU General Public License, version 1". GNU Project, February 1989. gnu.org/...gpl-1.0.en
- ^1 ^2 ^3 ^4 ^5 ^6Free Software Foundation. "What is Copyleft?". GNU Project. gnu.org/...copyleft.en
- ^1 ^2 ^3 ^4Stallman, Richard. "The GNU Project" (originally published in the book Open Sources). GNU Project. gnu.org/...thegnuproject.en
- ^1 ^2 ^3Williams, Sam. "Free as in Freedom: Richard Stallman's Crusade for Free Software", Chapter 9. O'Reilly, March 2002. oreilly.com/...ch09
- ^1 ^2 ^3 ^4 ^5 ^6 ^7Free Software Foundation. "FSF releases the GNU General Public License, version 3". FSF News, 29 June 2007. fsf.org/...gplv3_launched
- ^1 ^2 ^3 ^4Smith, Brett. "A Quick Guide to GPLv3". GNU Project. gnu.org/...quick-guide-gplv3.en
- ^1 ^2 ^3Free Software Foundation. "GNU Lesser General Public License, version 2.1". GNU Project, February 1999. gnu.org/...lgpl-2.1.en
- ^1 ^2 ^3Free Software Foundation. "GNU Lesser General Public License, version 3". GNU Project, 29 June 2007. gnu.org/...lgpl-3.0.en
- ^Free Software Foundation. "Why you shouldn't use the Lesser GPL for your next library". GNU Project. gnu.org/...why-not-lgpl.en
- ^1 ^2 ^3 ^4 ^5Free Software Foundation. "GNU Affero General Public License, version 3". GNU Project, 19 November 2007. gnu.org/...agpl-3.0.en
- ^1 ^2Free Software Foundation. "Why the GNU Affero GPL". GNU Project. gnu.org/...why-affero-gpl.en
- ^1 ^2 ^3 ^4 ^5Free Software Foundation. "Various Licenses and Comments about Them". GNU Project. gnu.org/...license-list.en
- ^1 ^2 ^3 ^4 ^5 ^6 ^7 ^8 ^9 ^10 ^11 ^12 ^13 ^14Free Software Foundation. "Frequently Asked Questions about the GNU Licenses". GNU Project. gnu.org/...gpl-faq.en
- ^1 ^2The Linux Kernel documentation. "Linux kernel licensing rules". kernel.org. kernel.org/...license-rules
- ^1 ^2SPDX. "SPDX License List data" (licenses.json). GitHub, retrieved 18 November 2026. github.com/...license-list-data
- ^Hugging Face. "Licenses". Hugging Face Hub documentation. huggingface.co/...repositories-licenses
- ^1 ^2Ultralytics. "Ultralytics License". Ultralytics. ultralytics.com/license
- ^1 ^2 ^3 ^4Free Software Foundation. "FSF is working on freedom in machine learning applications". FSF News, 22 October 2024. fsf.org/...reedom-in-machine-learning-applications
- ^Lee, Victoria; Stevenson, Christopher. "SFC v. Vizio survives motion for summary judgment on third-party beneficiary issue". DLA Piper, 16 January 2024. dlapiper.com/...t-on-third-party-beneficiary-issue
- ^1 ^2Black Duck. "Is breach of the GPL license breach of contract?". Black Duck Blog, 2 January 2018. blackduck.com/...breach-gpl-license-breach-contract
- ^1 ^2Koo, Hean L.; Gatto, James G. "Important Open Source Ruling Confirms Enforceability of Dual-Licensing and Breach of GPL for Failing to Distribute Source Code". National Law Review, 15 May 2017. natlawreview.com/...-dual-licensing-and-breach-gpl
- ^1 ^2Comfy-Org. "ComfyUI LICENSE". GitHub. github.com/...LICENSE
- ^1 ^2 ^3AUTOMATIC1111. "stable-diffusion-webui LICENSE.txt". GitHub. github.com/...LICENSE.txt
- ^lllyasviel. "Fooocus LICENSE". GitHub. github.com/...LICENSE
- ^oobabooga. "textgen LICENSE". GitHub. github.com/...LICENSE
- ^1 ^2Ultralytics. "ultralytics LICENSE". GitHub. github.com/...LICENSE
- ^ggml-org. "llama.cpp" repository (license: MIT). GitHub. github.com/...llama.cpp
- ^The R Foundation. "R Licenses". The R Project for Statistical Computing. r-project.org/Licenses
- ^University of Waikato. "Weka 3 - Data Mining with Open Source Machine Learning Software in Java". ml.cms.waikato.ac.nz/weka
- ^1 ^2Baker Botts L.L.P. "When Consumers Enforce Open Source: The SFC v. Vizio Case". Baker Botts client update, May 2026. bakerbotts.com/...when-consumers-enforce-open-source
- ^Free Software Foundation. "GNU Free Documentation License, version 1.3". GNU Project, 3 November 2008. gnu.org/...fdl-1.3.en
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 · 4,181 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 18, 2026: 96 claims checked against 36 cited and independent sources; 2 material and 4 minor corrections applied before publication.
Cite this page: AI Wiki. "GNU General Public License." aiwiki.ai, updated 18 Nov 2026, fact-checked 18 Nov 2026. CC BY 4.0. https://aiwiki.ai/wiki/gnu_general_public_license