GitHub is home to hundreds of millions of code repositories, including some repositories that rightsholders would rather not see online.
For Nintendo, Switch emulators have become the main challenge, one that keeps rearing its head.
Most of these emulators were killed off long ago. Yuzu settled in February 2024, for example, Ryujinx shut down that October, and the successors that tried to keep edited versions online have been targeted in waves ever since.
These waves keep coming. Earlier this week, Nintendo filed seven separate DMCA anti-circumvention notices at GitHub, all on the same day, targeting a variety of Switch emulator repositories and their forks. The combined reach is substantial. In the seven notices, more than 400 repositories were targeted.
More Than 400 Repos
The most detailed notice targets suyu, an emulator that became popular after Yuzu’s collapse. Because the reported network was larger than 100 repositories, GitHub processed the notice against the entire network, which covered 311 repos.
The remaining six notices ranged from a lone repository to networks of a few dozen, including the independent Skyline emulator, as shown below.
| Parent repo (notice) | Project | Targets |
|---|---|---|
| vstyler96/suyu | suyu (yuzu successor) | 311 repos (full network) |
| skyline-emu/skyline | Skyline (Android, independent) | 29 repos (full network) |
| NicolasArvani/yuzu | yuzu fork | 14 repos (full network) |
| liushuyu/yuzu-android | yuzu (Android port) | 8 repos (full network) |
| exverge-0/yuzu-EA4176 | yuzu (Early Access build 4176) | 21 forks listed |
| irlbunny-archive/MonoNX | MonoNX (C#-based) | 17 forks listed |
| IpwnedU/yuzu-master | yuzu fork | Parent only |
For four of the seven notices, the table shows GitHub’s own count of the processed network, including the parent repo. For the other three, no network details were published, so the table shows the repositories named in the notice itself, including some that were redacted as “[private].”
The legal argument is the same in all seven. Nintendo argues that the emulators exist to bypass the encryption that protects its games, which violates the DMCA.
“During operation, the emulators at the reported repositories necessarily use unauthorized copies of these cryptographic keys to decrypt unauthorized copies of Nintendo Switch games, or ROMs, at or immediately before runtime without Nintendo’s authorization,” the notice read.
Most of these repositories now link to notices informing visitors that they were removed. In some cases, they point to a 404 error, suggesting that the developer voluntarily removed the repository after being notified.
Precedents Without a Trial
To back the circumvention argument, every notice cites two court decisions as precedents, neither of which was challenged in court.
The first is the 2024 consent judgment against Tropic Haze, the company behind Yuzu, which ended in a $2.4 million settlement. The second is newer: Nintendo’s case against streamer Jesse Keighin, aka “EveryGameGuru,” who was ordered to pay $17,500 last October after a Colorado court entered a default judgment against him.
One was a settlement, the other a default judgment after Keighin reportedly stopped responding and destroyed evidence. In neither case did a court weigh the emulator circumvention question on the merits.
At the takedown stage Nintendo does not need to show a legal precedent. GitHub says it reviews circumvention claims carefully and will “err on the side of the developer, and leave the content up” when validity is unclear. The Yuzu framework has made Nintendo’s notices close to routine anyway.
Defunct Skyline & Future Horizon
Among the targeted emulators Skyline stands out, as it was a Switch emulator for Android devices, not a yuzu fork. Skyline’s developers shut the project down voluntarily in 2023, but as is often the case, the open
This week, Nintendo’s takedown notice cleared a network of 29 Skyline repos, including code that has been dormant for years. This doesn’t necessarily deal with the problem permanently, as future takedown efforts are likely on the horizon.
Every emulator on this week’s list was already supposed to be gone. However, they were forked, mirrored, or revived, which put them on Nintendo’s radar again.
For Nintendo, getting these emulator repos removed from GitHub is the easy part. Keeping the code offline is a bigger challenge, as forks may reappear faster than the notices can remove them.
