What's Wrong with GitHub - GNU Project - Free Software Foundation
Skip to main text We are here to promote your freedom Our work begins by asking ourselves, “Is it free?” because our purpose is to respect your individual user needs, autonomy, and right to decide for yourself. We empower people to build a future built on free software that, above all, puts the user first. By supporting our work, you help support everyone's rights. Please help us reach our goal of $400,000 USD! Donate Read more GNU Operating System Supported by the Free Software Foundation Site navigation Skip ABOUT GNU = PHILOSOPHY = LICENSES EDUCATION SOFTWARE DISTROS DOCS MALWARE HELP GNU AUDIO & VIDEO GNU ART FUN GNU'S WHO?
SOFTWARE DIRECTORY HARDWARE SITEMAP / Philosophy / Essays & articles / Cultural & social issues / Network services / What's Wrong with GitHub By Jacob Bachmeyer and Richard Stallman Software developers, the GNU Project urges you to avoid hosting your repositories on GitHub. This is to avoid being on the receiving end of harmful practices, and avoid leading others to be victims too. This article focuses on a few of GitHub's worst problems, and the wrongs and harm they can do: (1) GitHub promotes vague and confusing licensing practices; (2) it demands that visitors run nonfree JavaScript for most operations; (3) some of the “services” it offers are actually SaaSS (Service as a Software Substitute) dis-services; (4) it attempts to subvert the distributed architecture of Git.
While Git is free software, GitHub is not software at all. It is a website that provides a range of features, from a simple repository-hosting service to a variety of SaaSS dis-services. The sheer variety of features GitHub offers makes writing a fair critique of the site difficult, because each one calls for an evaluation on moral grounds—both for the job it does, and for the implementation of that job. This article focuses on a few of GitHub's worst problems, beginning with an area where GitHub has shown at least some improvement over the years, mentioning the website's near-uselessness for users who refuse the JavaScript Trap and the SaaSS “AI” [1] dis-services, and ending on GitHub's model of being a central hub in a distributed system.
GitHub seems to operate as much like a walled garden as it can without outright breaking compatibility with Git. Because Git is free software, GitHub cannot forcibly tether Git to itself, but it can bait users to adopt workflows that nonetheless tie the users to GitHub. Sometimes the worst handcuffs are not iron, but silk. GitHub offers convenience in centralization, and this makes little frictions insidious: one-click merge only works from a pull request, which can only be made from a “fork” hosted on GitHub; links to GitHub accounts replace email addresses in the web UI; continuous integration runs on GitHub servers by default.
Little by little, the Internet-spanning plains of Git become the walled garden of GitHub. The full solution to the problems caused by hosting your package on GitHub is to host your package on a site that doesn't have those problems . But if you can't do that right away, at least publish an email address in your README so people who don't use GitHub can communicate with you about your program, host the web pages about using your program on a website that doesn't require nonfree software to read those pages, and always refer to the web pages there.
Promotion of Vague and Unclear Licensing Practices When GitHub first began offering repository hosting in early 2008, it was completely silent on the matter of properly licensing free software, and this silence led to a proliferation of public repositories with no declared license whatsoever. In 2013, GitHub set up a “ Choose a License ” site to help users select free licenses for new software. As of this writing in 2026, that site gives ill-advised advice for the application of the GPL, stating that merely copying the text of the license into a file in a repository is sufficient.
The FSF's lawyers recommend to us, and in turn we recommend to developers, to put a license notice in each substantive file , to ensure that users are aware of their rights and obligations under the GPL. GitHub mentions this only as an “optional step.” Without the standard GPL notice, there is nothing to say whether the program is licensed under GPL version N only, or under GPL version N-or-later . GitHub mentions this only in an aside about SPDX license identifiers.
Extensive Use of Nonfree JavaScript GitHub's website sends lots of JavaScript code to the browser, and much of that code is nonfree. Because the site fails to gracefully degrade, users who refuse the JavaScript Trap find that any interaction beyond simply viewing repositories is impossible, and even many of the file-viewing links no longer work. There are workarounds for this. The standard free Git command-line tools can clone repositories from GitHub, and there is a public REST API and free command-line tool that can handle at least some interaction with the site.
However, the command-line tool GitHub provides for that REST API, while technically free software under Expat license terms , nonetheless cannot be recommended because GitHub has decided to add spyware features in the form of “telemetry” to it. This is exceptionally ridiculous, because the tool's main purpose is to use a web-based API; GitHub could obtain usage information from their own server logs rather than from users' computers.
GitHub Copilot is SaaSS GitHub started a controversy with the introduction of “GitHub Copilot” that has only grown with the capabilities of the tool. GitHub Copilot began as an “AI” [1] code-completion tool, with an early demonstration of producing the body of a function given only its header comment, and has grown into an “AI” “agent” claimed to be able to function as a development team member. Copilot has always been controversial.
The initial code-completion tool used a model that had been trained on a wide variety of code, under a wide variety of licenses, and was quickly found to be able to reproduce lengthy sections of well-known text verbatim, including the preamble of the GNU General Public License and the Zen of Python. This ability to regurgitate its training material has led to doubts about the legal status of code suggested by Copilot.
GitHub offers indemnification to higher-tier Copilot subscribers, although it remains unclear how indemnity would work if the demand were to be GPL compliance rather than money. Later expansions of Copilot's capabilities have brought more controversy. GitHub added a “feature” allowing users to have Copilot write a bug report, which is then submitted as an issue with minimal indication that Copilot was used to generate it.
These Copilot-assisted issues have been drowning maintainers of projects on GitHub in slop when users fail to proofread their issues and correct Copilot's errors. GitHub, of course, refuses to allow maintainers to block Copilot-generated issues from being submitted. The legal risks of using LLM code suggestions and the social harms of burying maintainers in slop are universal, applying even to free models run locally, but what GitHub does is bad in another way: Copilot is SaaSS , and its models run on remote servers where users have no control over them.
This has produced some of the usual SaaSS abuses: forced “upgrades” that users find to be inferior to the previous versions, and price increases at the whim of the vendor. Copilot subscriptions originally provided access to basic features (mostly the code suggestions) and a certain number of “premium requests” (other interactions and more complex agentic tasks) each month. In early 2026, GitHub announced a policy change: all subscriptions would be forced to move to a token-based billing model that charges for the actual computing resources used, which is only loosely under the user's control.
GitHub could impose this change on users because Copilot is SaaS
The rest of this page is on the live site.