GitHub credits broader counting rules for most of its jump to 708 government takedown requests

Taken at face value, 708 requests in six months is about 7.2 times the full 2025 count ^[1]. For that ratio to say something about moderation, both periods would need the same counting rules, and removals would need to climb with requests. GitHub says neither is the case ^[2][5].

The duplicate rule changes the unit being counted. Under it, an agency that resends the same notice adds to the count each time ^[4]. Anyone who has switched a dashboard from unique visitors to raw hits mid-quarter has seen this chart before. GitHub wrote that the higher number "reflects the volume of government reporting activity GitHub receives, not a corresponding increase in content removals" ^[7].

The before-and-after is also less clean than the headline pair suggests. GitHub first described the broader scope in its H1 2025 update ^[6], so part of 2025 may already have been counted under it. The post does not date the duplicate change, split the new total by legal basis or by duplicates, or give a removal figure.

For tracking what governments actually want removed, I would read the government takedowns repository over the headline count. GitHub still publishes requests about content deemed unlawful in a particular jurisdiction there ^[8].

The legislative half of the post turns on a licensing detail. Earlier drafts of California's AI Transparency Act, SB 1000 (previously SB 942), would have required providers to revoke licenses under certain circumstances ^[9]. GitHub said that requirement was incompatible with widely used open source licenses, which are irrevocable ^[9]. The enrolled text moved to a narrower notice-and-response approach. GitHub says that resolved the conflict, though implementation questions remain ^[10].

The open question sits in the law already on the books. AB 853 defines "large online platform," "file-sharing platform," and "GenAI hosting platform" in terms GitHub says could be read to cover code repositories ^[12]. Newsom's signing message last year encouraged follow-up legislation in 2026 on technical feasibility ^[15]. AB 2713 is a follow-up bill meant to refine how the Act's provenance requirements apply in practice, particularly to platforms ^[18]. GitHub says applying the current definitions to code hosting could create legal uncertainty for open source developer infrastructure without addressing the risks the Act was designed to target ^[14].

Of the two, I think the definitions matter more to teams that host or publish code. The licensing conflict in SB 1000 was fixed in the bill text ^[10]. The platform definitions in AB 853 remain as enacted ^[13].