Government policy is reshaping the landscape in which developers work, collaborate, and contribute to open source projects. This reality underscores GitHub's commitment to both disclosing how it handles official requests and equipping the developer community with information about legislative proposals that could alter their work.

GitHub is releasing updated Transparency Center data, reviewing an exceptionally busy 2026 state legislative session, and identifying several policy areas that will command attention in the coming months.

Government takedown requests: methodology changes drive reported increase

A striking shift appears in GitHub's H1 2026 Transparency Center data: government takedown requests jumped to 708 in the first six months of 2026, compared with 98 across all of 2025. The surge primarily stems from how GitHub now counts these requests rather than from shifts in its moderation approach.

Beginning with the H1 2025 update, GitHub broadened its reporting scope to capture every government takedown request it receives, regardless of whether the request cites local law, a Terms of Service breach, or simply demands content removal. The company also refined its internal counting system to register all requests received, including multiple requests targeting identical content.

The elevated figures therefore represent the breadth of government reporting activity GitHub encounters, not a proportional rise in actual content removals. Takedowns executed under local law or for Terms of Service infractions remain uncommon, and requests concerning content deemed illegal in a given jurisdiction continue to be made public through GitHub's government takedowns repository.

State legislatures tackle AI transparency and age verification

Throughout 2026, GitHub has engaged with state policymakers on multiple fronts, particularly regarding age assurance—mechanisms for confirming user age to deliver age-appropriate content—and content provenance, which documents whether material was created or modified using artificial intelligence.

GitHub publishes these policy updates to enable developers to grasp how proposed laws might touch the tools they depend on and the open source initiatives they support. These communications also highlight victories, particularly those achieved through open source community advocacy and lawmakers gaining deeper insight into how open source development operates.

Content provenance and AI transparency

In California, sustained pressure from GitHub and the wider open source sector contributed to improvements in the California AI Transparency Act (SB 1000, formerly SB 942). This legislation aims to enable people to recognize the source of digital material by retaining and displaying data about whether AI created or modified the content. Earlier drafts would have mandated that providers cancel licenses under specific conditions—a requirement at odds with standard open source licenses, which cannot be revoked.

The final version adopted a more focused notice-and-response framework that eliminated the core incompatibility with open source licensing. From an open source standpoint, the revised bill represents significant improvement, though questions about how it will be applied remain unresolved. SB 1000 was enrolled on August 30, 2026 and awaits California Governor Gavin Newsom's signature by September 30, 2026.

GitHub has also been engaged with AB 2713, a companion measure designed to clarify how the California AI Transparency Act's content provenance rules function in practice, particularly for online services. The underlying statute, AB 853, characterizes "large online platform," "file-sharing platform," and "GenAI hosting platform" in language that might encompass developer infrastructure such as code repositories. GitHub contends these definitions do not reflect the law's actual purpose and that applying them to code hosting would introduce legal risk for open source developer infrastructure and create practical obstacles without addressing the harms the Act targets. Governor Newsom's signing statement the previous year called for follow-up legislation in 2026 addressing technical feasibility, and GitHub advocated for AB 2713 with amendments to narrow these definitions. The requested amendments were not included this session, so GitHub expects this matter to resurface as a priority in the next legislative cycle.

Age assurance and youth online safety

Age assurance emerged as a central concern. Legislation designed for consumer applications can produce unintended effects when expansive language captures open source operating systems, developer tools, and other infrastructure that function in fundamentally different ways.

In California, GitHub's work on the Digital Age Assurance Act (AB 1043) has centered on preventing age assurance rules from applying to open source operating systems, developer tools, and other services lacking a consumer orientation. Colorado's modifications to the Age Attestation on Computing Devices law (SB 26) addressed significant worries about effects on open source software and developer infrastructure, demonstrating what coordinated action by the open source community can achieve. In Illinois, the Children's Social Media Safety Act (HB 5511) became law with unresolved concerns remaining. GitHub plans to continue partnering with policymakers and other stakeholders on amendments to resolve implementation hurdles and unintended consequences for open source.

These legislative battles underscored a recurring theme in 2026: developers possess crucial technical knowledge that policymakers need when crafting rules affecting the software ecosystem. Enabling developers to share their expertise with lawmakers at early stages of policy development can yield more effective and practical legislation.

Priorities for the months ahead

As policy continues to influence how developers build, work together, and engage in open source, GitHub intends to ensure developers maintain a seat at the table. This involves monitoring emerging policy questions, helping developers grasp their implications, bringing technical knowledge to decision-makers, and partnering with open source organizations on policies that benefit developers and the wider ecosystem.

GitHub is monitoring the DMCA Section 1201 triennial rulemaking, a periodic process that evaluates temporary exemptions permitting developers and researchers to circumvent technological safeguards for lawful purposes. The current round encompasses petitions relevant to developers, such as FOSS license-compliance inquiries, scholarly text and data mining, and continuation of the good-faith security research exemption that GitHub has backed in earlier proceedings. GitHub is also participating in emerging conversations about young people's use of AI systems, aiming to help policymakers distinguish between consumer-focused conversational platforms and tools for education, development, and software creation.

Open source and open source AI will remain central to GitHub's policy agenda. As policymakers address mounting concerns about artificial intelligence—spanning cybersecurity, safety, and international competition—GitHub wants to guarantee that developers and the open source community have input. This entails deepening policymakers' understanding of how open source is built, assembling a wider network of open source partners, and giving developers channels to shape policy as these conversations progress. GitHub will persist in working together on responses to new challenges while championing policies that sustain a robust and well-funded open source ecosystem and safeguard the openness, investigation, teamwork, and creativity that open development enables.