# github/gov-takedowns: the repository where GitHub publishes government removal requests > GitHub's gov-takedowns repository is a public archive of complete government takedown notices, filed by jurisdiction and posted verbatim apart from redactions. It is a transparency record, not a tool, and it is worth reading before you treat any single notice as a statement of fact. **github/gov-takedowns** — Text of government takedown notices as received. GitHub does not endorse or adopt any assertion contained in the following notices. - Repository: https://github.com/github/gov-takedowns - Stars: 3,182 · Forks: 182 - Language: Unknown - License: not declared - Published: 2026-09-24 · Updated: 2026-09-24 · Language: en - Canonical page: https://hysenlabs.com/projects/github-gov-takedowns ## What github/gov-takedowns actually is, and who reads it This is a document repository. It holds the text of government takedown notices as GitHub received them, and GitHub states that it does not endorse or adopt any assertion contained in them. There is no application to run, no library to import, no CLI. The unit of content is a notice file, grouped into folders by jurisdiction: China, Germany, Hong Kong, India, Russia, Singapore, South Korea and Spain appear at the top level, alongside README.md, CONTRIBUTING.md and CODE_OF_CONDUCT.md. The audience is narrow and fairly specific. Journalists and researchers who need the primary document rather than a summary. Engineers who got a notification that their repository was blocked in one country and want to see how comparable notices were worded. Policy people tracking which agencies make these requests and under what claimed legal basis. If you are looking for a way to automate takedown handling or to appeal a notice, this repository is not that. It is the public record that sits at the end of GitHub's internal process. ## The four conditions GitHub applies before a notice is complete The README sets out a filter that decides whether a request enters this repository at all. A notice counts as complete only if it comes from a relevant, official government agency, identifies the illegal content, and specifies the source of illegality in that jurisdiction, whether a law or a court order. All three have to hold. A request that names content but cites no law, or that arrives from a party that is not an official agency, does not meet the bar described in the README. That threshold is the most useful thing in the document, because it tells you what the archive is not. It is not a log of every government complaint GitHub receives. It is not a record of takedowns processed under GitHub's own Terms of Service. The README is explicit that Terms of Service violations reported by governments are handled the same way as violations reported by anyone else, and are tracked separately in GitHub's Transparency Center rather than posted here. So a country with a large number of ordinary abuse reports and no complete government notice will show up as an empty or absent folder, and that absence carries information about the legal route taken, not about how much content was removed. ## What happens between a notice arriving and a file appearing in the folder The README describes a sequence. When a complete notice arrives, GitHub notifies the affected users about the specific content alleged to violate the law and tells them this is a legal takedown request. The notification includes the ability to appeal. GitHub limits the geographic scope of the takedown where it can, and includes that scope in the notification. Then the official request that led to the takedown is posted in this repository. The order matters for anyone reading the archive as a timeline. The notice is posted after the takedown and after the affected user has been told, so the repository is a downstream artefact, not a live feed. The README also notes that notices are posted unchanged apart from redactions of personal information. That single sentence explains most of the gaps you will notice in the files: names, addresses and similar details are removed, and the surrounding legal text is left as the agency wrote it, including whatever claims about illegality the agency chose to make. The geographic limitation step is worth flagging as a design choice with a cost. It reduces the blast radius of a national court order, but it also means two users viewing the same repository from different countries can see different content, and the notice file is often the only place that difference is documented. ## Reading the archive: browse the jurisdiction folders directly There is nothing to install. The README gives no setup instructions, no package name and no configuration, because the repository is a set of Markdown and notice files. The practical first use is to open the repository on GitHub and read the folder for the jurisdiction you care about, since the notices are plain text and render in the browser. The repository root lists one directory per jurisdiction, matching the folders named in the README's own description of the project. Open the folder for the country whose notice you want, then open an individual notice file inside it. Each entry is the notice document itself. The redactions are visible as removed personal information, and the legal citation the agency supplied is part of the text. The useful workflow for comparison is to read several notices from the same folder side by side, because the value of the archive is in seeing how different agencies describe the same category of illegality. The README does not document any search, export or query mechanism, so cross-jurisdiction comparison is a manual reading task rather than something the repository automates. ## The limits: a notice in this repository is not a finding of wrongdoing The README spends a paragraph on this and it deserves to be repeated, because it is the most common misreading of the archive. A posted notice means GitHub received the notice on the indicated date. It does not mean the content was unlawful or wrong. It does not mean the user named in the notice has done anything wrong. GitHub states that it makes no judgment about the merit of the claims. That is a real limitation on what you can conclude from the files. An agency can send a complete request that satisfies all three conditions and still be wrong on the merits, and the repository will contain it either way, because the posting rule is about completeness and provenance, not about whether the claim is correct. The second limitation is coverage. Because the archive only holds notices that meet the completeness test and led to removal, it systematically undercounts government pressure. Requests that were rejected as incomplete, or that were handled as Terms of Service violations, do not appear. A researcher counting files per country and treating the totals as a measure of censorship volume would be reading the wrong signal. The third limitation is that GitHub does not accept pull requests here. The README explains why: the notices are verbatim from the notifying government. So if you spot an error, a missing notice or a redaction you think went too far, there is no contribution path through this repository. Discussion is expected to relate to the stated purpose, and the project ships a Contributor Code of Conduct that applies to participation. ## How it differs from Lumen and from GitHub's own Transparency Center The closest comparison is Lumen, the database formerly known as Chilling Effects, which collects takedown notices of many kinds from many platforms, including copyright complaints and requests that did not result in removal. The difference in approach is scope and filtering. Lumen is broad and aggregating; it wants volume across senders and platforms. github/gov-takedowns is narrow and curated by a single company, and it only contains notices that GitHub judged complete and acted on. If you want to see the long tail of demands that platforms resisted or ignored, Lumen is the better fit. If you want the specific documents behind a removal on GitHub, with the jurisdiction folder structure that implies, this repository is the primary source. The second comparison is GitHub's own Transparency Center, which the README links. The Transparency Center is where GitHub reports on these takedowns in aggregate and also tracks government takedowns processed under its Terms of Service. The repository is the raw material; the Transparency Center is the reporting layer built on top of it. For a count or a trend line, use the Transparency Center, because the repository does not aggregate anything. For the exact wording an agency used, use the repository, because the Transparency Center will not reproduce it. ## Maintenance, licence and what the repository does not tell you The last push to the default branch was on 2026-09-10, and the repository is not archived. Activity here is driven entirely by incoming notices, so a quiet period means no complete government requests were posted, not that the project is dormant. There are no releases, which is expected for a document archive: versioning happens through commits to the notice files themselves, and there is no changelog to follow. The licence is not stated in the repository, and the README does not discuss reuse terms. That matters if you plan to republish notice text in bulk or in a dataset. The notices are government documents posted verbatim, but the repository itself carries no declared licence, so anyone building on it should check the repository for a licence file before redistributing, rather than assuming one applies. This is a description of what the repository shows, not legal advice. Upgrade cost is close to zero in the software sense and non-trivial in the research sense. There is no dependency to update. But the archive changes underneath you as notices are added, so a citation should include the jurisdiction folder and the notice file, and a snapshot if you need the text to stay fixed. The README does not document any rollback or correction process for a posted notice, which follows from the no-pull-requests rule: once a notice is posted, the repository offers no described mechanism for revising it. ## Conclusion Read github/gov-takedowns if you want the primary documents behind a government removal on GitHub, or if you are studying how jurisdictions phrase illegal-content claims. Do not read it as a record of wrongdoing: the README states plainly that a posted notice does not mean the content was unlawful or that the named user did anything wrong. Before citing the repository, open the country folder for the jurisdiction you care about and check whether a notice for that removal is actually present, because the README describes the posting step as part of the process but does not promise that every takedown appears here. ## FAQ ### What is a takedown notice and how does it work in github/gov-takedowns? A government takedown notice is a request from an official agency to remove content declared unlawful in its jurisdiction. The README states that GitHub treats a request as complete only when it comes from a relevant official agency, identifies the illegal content, and specifies the source of illegality, and only complete requests end up posted in this repository. ### Does github/gov-takedowns cover DMCA takedown notices? The repository is described as holding government takedown requests that led to content removal based on local law. The README does not mention DMCA notices, and it says government takedowns processed under GitHub's Terms of Service are tracked in the Transparency Center instead. ### Does a notice in github/gov-takedowns mean the content was illegal? No. The README states that a posted notice only means GitHub received it on the indicated date, and that it does not mean the content was unlawful or wrong, nor that the named user did anything wrong. GitHub says it makes no judgment about the merit of the claims. ### Can I submit a pull request to github/gov-takedowns? No. The README states that pull requests are not accepted because the notices are posted verbatim from the notifying government. Discussion is expected to relate to the repository's purpose, and the Contributor Code of Conduct applies to participation. ### Which countries appear in github/gov-takedowns? The repository root contains folders for China, Germany, Hong Kong, India, Russia, Singapore, South Korea and Spain. Each folder holds the notices filed for that jurisdiction. ## Sources - [github/gov-takedowns on GitHub](https://github.com/github/gov-takedowns) - [Issues](https://github.com/github/gov-takedowns/issues) - [README](https://github.com/github/gov-takedowns/blob/master/README.md) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/github-gov-takedowns