Evidence · DiggingBeagle record
Anthropic partial retraction of March 31 GitHub DMCA notice
GitHub-hosted first-party retraction dated April 1 states the notice was withdrawn for all repositories except one originally named mirror and 96 individually listed forks; asks GitHub to restore repositories affected by network-wide processing. Copyright enforcement record, not evidence of a newly exploited software vulnerability.
- Published
- Apr 1, 2026
- Publisher
- Anthropic via GitHub DMCA repository
- Source role
- primary disclosure
Evidence record
GitHub-hosted first-party retraction dated April 1 states the notice was withdrawn for all repositories except one originally named mirror and 96 individually listed forks; asks GitHub to restore repositories affected by network-wide processing. Copyright enforcement record, not evidence of a newly exploited software vulnerability.
Claim-level citations (2)
- supportsClaude Code release exposed proprietary agent harness source through a debugging artifact: The GitHub takedown response swept in roughly 8,100 repositories according to TechCrunch, but an April 1 partial retraction withdrew notices for all except one named mirror and 96 listed forks. Neither figure measures model compromise or affected customers.
April 1 notice first and second sentences: scope of partial retraction
- supportsClaude Code release exposed proprietary agent harness source through a debugging artifact: Anthropic's April 1 partial notice retraction requested restoration of affected GitHub fork-network repositories other than a named mirror and 96 individual forks. TechCrunch subsequently quoted Anthropic saying GitHub had restored affected forks. This was a copyright enforcement response, not proof that the accidentally released source could be recalled.
Retraction body, sentence beginning We retract the notice as to all repositories except