GitHub published a policy update linking recent transparency data to legislation enacted or discussed by U.S. states during 2026, warning that rules designed for consumer-facing services could, through broad language, extend to code repositories, developer tools, and open-source infrastructure.
Sharp Increase in Reported Requests
Data from the first half of 2026 showed 708 government requests to remove content, compared with 98 requests during all of 2025. However, GitHub explained that the comparison does not indicate a comparable increase in removals or moderation practices; the new methodology includes all incoming requests, whether based on local law, the terms of service, or simply a request to remove content, and also counts duplicate requests concerning the same content.
According to the company, removals carried out under local laws or because of violations of the terms of service remain relatively rare, while GitHub continues to publish requests concerning content that an entity considers illegal within its jurisdiction in its government takedown request repository.
AI Content Transparency
During the 2026 U.S. legislative session, GitHub focused on proposals concerning content provenance, meaning the availability of information showing whether content was created or modified using artificial intelligence. In California, the company said, its engagement and that of the open-source community contributed to amendments to the AI transparency bill SB 1000, formerly known as SB 942.
Earlier wording included, under certain circumstances, the revocation of software licenses, which GitHub considered fundamentally incompatible with common open-source licenses that cannot be withdrawn. In its later version, the bill moved to a narrower approach focused on notification and response. SB 1000 was referred on August 30, 2026, and was awaiting the signature of California Governor Gavin Newsom by September 30, 2026, when the update was published.
By contrast, the amendments requested by GitHub to AB 2713, which aims to clarify the application of content-provenance requirements to platforms, were not adopted. The company believes that the definitions in the underlying law, AB 853, for certain platforms could include code repositories and developer infrastructure services, potentially creating legal ambiguity and enforcement difficulties. GitHub therefore expects this issue to remain a priority next year.
Age Verification and Youth Safety
The company also addressed age-verification and online youth-safety laws. In California, its position on AB 1043 focused on preventing the requirements from extending to open-source operating systems, development tools, and services not directed at consumers. In Colorado, it said amendments to SB 26 addressed key concerns regarding open-source software and developer infrastructure, while HB 5511 was enacted in Illinois with implementation issues remaining that GitHub believes require subsequent amendments.
What Is Changing in Practice?
These issues show that the regulatory impact does not stop at platforms targeting end users. A broad legal definition of a file-sharing platform or an AI service could place code repositories under obligations not originally designed for the nature of open-source work. GitHub’s core assessment is that involving developers and technical experts early in the drafting of laws could reduce conflicts between protection objectives and software-development mechanisms.
The company also said it is following the periodic review of exemptions under Section 1201 of the DMCA, including requests concerning investigations into compliance with free-software licenses, academic text and data mining, and the renewal of the good-faith security research exemption. It is also monitoring discussions about youth access to AI tools, calling for a distinction between consumer-facing conversational services and tools for learning, creativity, and software development.
certi.news analysis: The most important value of the update is not the number 708 itself, but the clarification that the measurement method changed and that the figure cannot be interpreted on its own as an indicator of an escalation in removals. At the legislative level, the open question is how to draft AI and youth-safety laws so that they target the intended services without imposing inappropriate obligations on open-source infrastructure. The outcomes of SB 1000, amendments to AB 2713, and the implementation of age-verification laws remain points requiring actual monitoring before their ultimate impact can be assessed.