GitHub logs 708 government takedown requests in H1 2026 as reporting scope widens

What the transparency data shows

GitHub's latest Transparency Center update covers the first half of 2026, and the headline figure is a large one: the company received 708 government takedown requests in those six months, against 98 for all of 2025. According to GitHub, that jump mostly reflects a change in how it counts requests rather than any shift in moderation behavior.

Since its H1 2025 report, GitHub has recorded every government takedown request it receives — whether it cites local law, alleges a Terms of Service violation, or simply asks for content to be removed — and now counts duplicate requests about the same content separately. Actual removals under local law or the Terms of Service remain relatively rare, GitHub says, and requests involving material deemed unlawful in a particular jurisdiction are still published in its government takedowns repository. In other words, the 708 number measures inbound government reporting activity, not a proportional rise in takedowns.

California's AI transparency law

The rest of the post looks back at what GitHub calls an unusually active 2026 US state legislative session, focusing on two clusters of legislation: AI content provenance and age assurance.

On provenance, GitHub describes its work on California's AI Transparency Act (SB 1000, previously SB 942), which preserves and displays information about whether content was created or altered by AI. Earlier drafts would have required providers to revoke licenses in certain circumstances, which GitHub argues is at odds with open source licensing, since widely used open source licenses are irrevocable. After engagement from GitHub and the broader open source community, the bill moved to a narrower notice-and-response model that, in GitHub's view, resolves the conflict. SB 1000 was enrolled on August 30, 2026 and was awaiting Governor Gavin Newsom's signature by September 30 at the time of publication.

A follow-up bill, AB 2713, is intended to refine how those provenance requirements apply in practice, particularly to platforms. GitHub's concern is that the underlying law, AB 853, defines "large online platform," "file-sharing platform" and "GenAI hosting platform" broadly enough that code repositories could be captured. GitHub argues that extending the rules to code hosting would create legal uncertainty for open source infrastructure without addressing the risks the act targets. It took a support-if-amended position on AB 2713; the amendments were not adopted this session, and GitHub expects to return to the issue next year.

Age assurance reaches developer tools

Age assurance — verifying users' ages online to deliver age-appropriate experiences — was the other major theme. GitHub's consistent argument is that laws written for consumer-facing services behave strangely when their definitions sweep in open source operating systems, developer tools and other infrastructure that works very differently.

In California, GitHub says its engagement on the Digital Age Assurance Act (AB 1043) focused on keeping non-consumer-facing open source software out of scope. In Colorado, changes to the Age Attestation on Computing Devices law (SB 26) addressed the open source concerns GitHub had raised, which it cites as evidence that coordinated community engagement pays off. In Illinois, the Children's Social Media Safety Act (HB 5511) was signed into law with what GitHub calls important issues still unresolved, and the company says it will keep working with policymakers on amendments.

What GitHub is watching next

Looking ahead, GitHub is following the DMCA Section 1201 triennial rulemaking, where current petitions include exemptions relevant to FOSS license-compliance investigations, scholarly text and data mining, and renewal of the good-faith security research exemption GitHub has supported in earlier cycles. It is also engaging on debates about young people's access to AI tools, arguing that policymakers should distinguish consumer-facing conversational services from tools for learning, creating and building software. Open source and open source AI, GitHub says, will remain its central policy focus.

Why it matters

The takedown figure will grab attention, but the methodology note is what developers should read closely — it changes how GitHub's reports compare with earlier ones and with those of other platforms. The legislative recap is the more consequential story. Bills drafted for social platforms and generative AI services increasingly reach developer infrastructure through broad definitions, and the divergent outcomes in California, Colorado and Illinois suggest that early technical input from the open source community can change what actually becomes law. GitHub's approach — publishing takedown data, tracking state bills and supplying technical context to legislators — is a template for how the platform hosting much of the world's open source code intends to defend it.