News / Software, Web & Apps
GitHub Updates Transparency on Government Requests and Commits to U.S. AI and Age Verification Laws Published on 29 September 2026 by Christ-loisele (4 min read)
GitHub has revised its reporting methodology in its Transparency Center, revealing a spectacular rise in government removal requests. The company has also outlined its stance on U.S. legislative projects regarding age assurance and the traceability of AI-generated content, with implications for developers and open-source licenses.
Expanded Methodology Reveals Surge in Government Removal Requests
GitHub announced on September 29, 2026 a major update to its reporting methodology in its Transparency Center, now including all removal requests from governments, whether legally justified or not, and even in cases of duplication. As a result, the number of these requests jumped from 98 in 2025 to 708 in the first half of 2026, an increase attributed exclusively to this methodological change and not to any modification in the platform’s moderation practices, according to GitHub.
These legislative exchanges mark progress, especially when they rely on the commitment of the open-source community and a better understanding of this model’s specifics by policymakers.
Logo: GitHub (CC BY 4.0) Impact of U.S. AI and Age Verification Laws: GitHub Advocates for Technical Adjustments
During the 2026 legislative session in the United States, GitHub closely monitored several bills aimed at regulating artificial intelligence and age verification for users. In California, the California AI Transparency Act (SB 1000) , initially known as SB 942, was amended to adopt a ‘notice-and-response’ approach, a measure designed to resolve conflicts with irrevocable open-source licenses, as GitHub explains. This change addresses a requirement deemed fundamentally incompatible with open-source licenses, according to the company.
GitHub also opposed proposed definitions in bills AB 853 and AB 2713 , fearing they could classify development infrastructures, such as code repositories, as ‘large online platforms’ or ‘hosting platforms for generative AI models.’ Such classifications, GitHub warns, could create legal uncertainty for open-source infrastructures , particularly due to their decentralized and collaborative nature.
Additionally, the company worked with lawmakers on the Digital Age Assurance Act (AB 1043) to prevent open-source operating systems or development tools from facing disproportionate obligations. In Colorado, the SB 26 Computer Device Age Verification Law was modified to mitigate impacts on open-source software, following discussions with GitHub.
A Strategy to Engage and Protect Open-Source Developers
GitHub emphasizes the need to clarify how open-source software operates for policymakers, noting that current legislative proposals struggle to distinguish the specifics of this ecosystem. The company has adopted a position of support contingent on amendments for several bills, such as AB 2713, pending further clarification on technical definitions. This approach aims to avoid unforeseen legal consequences for developers and open-source infrastructures.
California Governor Gavin Newsom had indeed encouraged, in a signing message in 2025, legislative follow-ups in 2026 to assess the technical feasibility of the California AI Transparency Act. GitHub views these exchanges as progress, particularly thanks to the commitment of the open-source community and a better understanding of the issues by lawmakers.
What this changes here: risks for African developers and public administrations
For businesses and administrations in Benin and West Africa, these American legislative developments could have indirect repercussions, particularly if similar frameworks were locally transposed. For example, overly broad definitions of « online platform » or « digital infrastructure » could, in the future, include open-source code repositories used by public or private projects, leading to complex and costly compliance obligations. Local developers, often dependent on open-source tools for solutions tailored to African needs, could face legal uncertainties, especially if laws inspired by these models were adopted without consulting industry stakeholders.
Furthermore, requirements for traceability of AI-generated content or age verification, if extended to local services, could impose additional administrative burdens on platforms hosted in Africa. Administrations, already constrained by limited budgets, would then need to carefully evaluate the adoption of technologies subject to fluctuating regulations, risking project delays due to poorly anticipated compliance issues.
Sources 
