4 Attachment(s)
DMCA Notices Took Down 20,517 GitHub Projects Last Year
GitHub received more than 2,000 valid DMCA takedown notices last year, which resulted in the removal of over 20,000 projects. Targeted repositories included pirate apps and games, as well as hundreds of RARBG backups. The number of takedowns has increased significantly in recent years. However, legitimate projects have grown faster and GitHub says it continues to take a developer-first approach.
With over 420 million code repositories, GitHub takes pride in being the largest and most advanced development platform in the world.
As with other platforms that host user-generated content, this massive code library occasionally runs into copyright infringement troubles.
Pirate Devs
In some cases, people use code without obtaining permission from the creators, while others use GitHub to store pirated books or even music. And there are also developers whose projects are seen as pirate tools or apps, which often leads to copyright holder complaints.
A few high-profile takedowns have grabbed headlines over the years, including the RIAA’s takedown of YouTube-DL, which was later reversed.
Other rightsholders were more successful, with GitHub removing a variety of piracy apps last year, including Vancedflix and CloudStream. Following the demise of the original torrent site, hundreds of RARBG magnet link repos were taken down as well.
The RARBG repositories appeared online last May, quickly after the popular torrent site closed its doors. In response, some archivists collected the site’s magnet links and posted them on GitHub. Others copied these repositories to keep the data safe, but most of this effort was nullified by a single takedown request.
20,517 Downed Repos
This week, GitHub updated its latest transparency report with the latest data, revealing the total number of notices received and projects affected. The report shows that the platform processed a little over 2,000 takedown notices in 2023, which affected 20,517 repositories.
Of all notices received, just 35 were contested or retracted, and a total of 65 repositories remained online as a result.
As seen above, most repositories were taken down in March. After looking at the reported notices we couldn’t immediately find one responsible for this large uptick, but with many hundreds of “Eaglercraft” repositories flagged by Minecraft’s parent company Mojang, that certainly left a mark.
GitHub says that it will continue to take a developer-first, approach to content moderation, minimizing the disruption of software projects while protecting developer privacy. These transparency reports and the publicly posted takedown notices are a means to that end.
The transparency report also shines light on how takedown activity evolves as the platform grows. This historical data shows that, in relative terms, the number of repositories on GitHub grows faster than the takedowns.
For example, Github hosted just under 40 million repositories in 2015, of which 8,268 were taken offline. Today, the platform has more than ten times as many repositories, yet takedowns failed to triple in the same period. In fact, the number of takedowns in 2023 is lower than a year earlier.
Surge in Circumvention Notices Explained
Last year, GitHub did report a notable uptick in DMCA circumvention claims. These more than quadrupled compared to the years before and this wasn’t just a fluke, as the most recent transparency report shows.
At least initially, the reasons for this were unclear, prompting GitHub to launch an investigation. The results of this exploration, released this week, show that the explanation is quite straightforward.
In the fall of 2021, GitHub updated its DMCA takedown submission form with questions explicitly related to circumvention. Providing that option triggered many more submitters to tick that box, raising the number of ‘circumvention’ claims.
These additional circumvention ‘claims’ don’t necessarily mean that more notices were processed for this reason. According to GitHub, many of these notices were processed for other reasons instead, including as regular takedown notices.
“[W]hile significantly more notices we process allege circumvention, the rate at which we process takedown notices because of circumvention hasn’t accelerated,” GitHub writes.
Processing circumvention notices is quite costly for the company as all requests are reviewed by a team of lawyers and engineers, to ensure that developers’ projects are not taken down without valid reasons.
This extra scrutiny was first brought to the fore during the youtube-dl takedown saga, after which GitHub launched a million dollar Developer Defense Fund.
GitHub is now actively engaged in policymaking in this area. The company previously urged the US Copyright Office to expand the DMCA anti-circumvention exemptions to benefit developers, while eliminating FUD.
All in all, it’s good to see that GitHub remains committed to takedown transparency, and we will keep monitoring these and other trends going forward.
