Background
GitHub handles Digital Millennium Copyright Act (DMCA) claims with a goal to maximize the availability of code by limiting disruption for legitimate projects. Accordingly, we designed our DMCA Takedown Policy to safeguard developer interests against overreaching and ambiguous takedown requests. Each time we receive a valid DMCA takedown notice, we redact personal information, as well as any reported URLs where we were unable to determine there was a violation. We then post the notice to a public DMCA repository .
Access the complete data set on our GitHub repo or download the individual CSV files.
Access the complete data set on our GitHub repo or download the individual CSV files.
Access the complete data set on our GitHub repo or download the individual CSV files.
About circumvention claims
Within our DMCA reporting, we also look specifically at takedown notices that allege circumvention of a technological protection measure under Section 1201 of the DMCA. GitHub requires additional information for a DMCA takedown notice to be complete and actionable where it alleges circumvention. Our DMCA Takedown Policy includes a section that specifically addresses circumvention claims and outlines our policy with respect to how we stand up for developers when reviewing and processing such claims.
Access the complete data set on our GitHub repo or download the individual CSV files.
How to read this chart
Each data point corresponds to the number of projects taken down and the number of takedown notices processed during a calendar year half. Calendar year halves with more takedown notices processed appear higher on the chart and calendar year halves with more projects taken down appear farther to the right. Each data point is connected in chronological order.