On August 17, 2026, Nintendo of America sent 7 DMCA takedown notices to GitHub. Adding up GitHub's annotations and the URLs listed in the notices brings the total to 405 repositories. However, this figure does not represent 405 independent emulators or development teams. 311 of them—about 76.8% of the total—belonged to a single fork network rooted at vstyler96/suyu. Checking the 7 parent repositories on August 23 (Japan time) showed that 5 returned HTTP 451, while the other 2 were accessible but had nothing left at their root except a README.md file. The number of repositories named in the notices, how GitHub applied enforcement across the networks, and the current visible state of the parent repos are three separate figures.
Where the 405 figure comes from across 7 notices
GitHub's public DMCA record lists all 7 notices as received on August 17. Adding up the parent repository and fork counts for each notice yields 311, 18, 1, 8, 24, 14, and 29—totaling 405. Here's the breakdown:
| Notice | Parent Repository | Repos Processed by GitHub |
|---|---|---|
| 1 | vstyler96/suyu | 311 |
| 2 | irlbunny-archive/MonoNX | 18 |
| 3 | IpwnedU/yuzu-master | 1 |
| 4 | liushuyu/yuzu-android | 8 |
| 5 | exverge-0/yuzu-EA4176 | 24 |
| 6 | NicolasArvani/yuzu | 14 |
| 7 | skyline-emu/skyline | 29 |
The largest figure, 311, represents a single network combining the Suyu parent and its forks. The remaining six notices add up to just 94 repositories combined. The "400+" headline number reflects the total repositories processed under the notices on GitHub—it does not mean that many distinct codebases were involved.
It's also worth noting that the number of URLs listed in a notice doesn't always match GitHub's processed count. For example, the yuzu-EA4176 figure of 24 consists of 1 parent repo, 21 forks confirmed via public URLs, and 2 additional forks withheld as private information. Meanwhile, for yuzu-android, NicolasArvani/yuzu, and Skyline, GitHub noted that the repositories were being actively forked at the time of the notice, and counted the network as it stood at processing time—8, 14, and 29 respectively. The 405 total reflects these processing-time counts.
The dates on the notice files also don't indicate takedown dates or court rulings. GitHub's DMCA repository states that the file date reflects when the notice was received, and that listing a notice does not constitute a finding of illegal or wrongful conduct.
The conditions under which GitHub can process an entire fork network at once
Normally, GitHub does not automatically disable forks when it disables a parent repository. Forks are owned by different users and may contain different content or serve different uses, so rights holders generally need to investigate and identify individual forks in their notices.
However, when forks are actively multiplying at the time of a notice and the rights holder has identified all existing forks, GitHub can apply a valid claim to the entire network as it exists at processing time. For networks exceeding 100 repositories, this requires the claimant to review a representative sample and swear that the rest contain the same infringing material. The 311 repositories in the Suyu notice were processed under this over-100 provision, covering the entire network including the parent. A claim against one parent repository can thus extend to the whole fork network as it existed at the time of processing.
All 7 notices share a common annotation stating that GitHub gave the repository owners a chance to make changes before disabling access, and provided information about filing a counter-notice. For cases involving fixable content, GitHub gives owners about one business day to make corrections. If the owner removes the specified material and the rights holder accepts the fix, the repository can avoid being disabled entirely. Under GitHub's policy, this means that within the same batch of notices, some parent repos may end up returning HTTP 451 while others survive with only a README remaining.
The figure of 405 is the product of the URLs Nintendo listed in its notices combined with GitHub's fork-handling policy. It reflects how extensively the code had branched out on GitHub more than it reflects diversity among distinct codebases.
Nintendo's claim centers on circumvention of technological protection measures
In its notices, Nintendo cited the technological protection measures (TPM) used for the Switch console and its games—specifically, encryption relying on prod.keys. Nintendo's argument is that because the targeted emulators decrypt games using unauthorized keys either immediately before or during execution, this constitutes circumvention, or trafficking in circumvention technology, in violation of 17 U.S.C. §1201(a)(1) and (a)(2).
Section 1201(a)(2) of that law prohibits manufacturing, providing, or trafficking in any technology, product, or service primarily designed to circumvent a technological measure that effectively controls access to a copyrighted work. Nintendo's argument here is not that the repositories distributed the ROMs themselves, but that they distributed software responsible for decryption at runtime. How the targeted projects might counter this characterization depends on each project's specific implementation and what it actually distributes.
GitHub states that claims involving circumvention technology are reviewed by both technical and legal experts, and that when a determination cannot be made, the platform errs on the side of keeping the content up in favor of developers. Still, platform-level review is not a court proceeding. The public notice page itself states explicitly that a listing is a record of a received claim, not a finding that the targeted user engaged in illegal conduct.
Nintendo also cited the final judgment in the 2024 case Nintendo v. Tropic Haze in its notices. Based on a joint motion by the parties, that ruling found that Yuzu decrypted Switch games using unauthorized encryption keys, and ordered a $2.4 million payment along with a permanent injunction barring Yuzu's provision and distribution, among other things. However, that permanent injunction applies to Tropic Haze and related parties—it is not a blanket order that automatically extends to every repository named in the current notices.
The 7 parent repositories haven't uniformly disappeared
As of the August 23 (Japan time) check, 5 of the repositories—vstyler96/suyu, the redirect destination for MonoNX, liushuyu/yuzu-android, exverge-0/yuzu-EA4176, and NicolasArvani/yuzu—returned HTTP 451. By contrast, IpwnedU/yuzu-master and skyline-emu/skyline were accessible with HTTP 200, but checking their root directories via the GitHub API showed that both contained nothing but a README.md file.
| Parent Repository Status | Count | Content Confirmed on August 23 |
|---|---|---|
| HTTP 451 | 5 | Inaccessible for legal reasons |
| HTTP 200 | 2 | Root contains only README.md |
Under GitHub's policy, access remains blocked unless the owner modifies the specified material, but making such corrections can allow the repository itself to survive. That said, these HTTP statuses reflect observations as of August 23 and could change following subsequent counter-notices or further corrections.
The yuzu-master README directs users to a source archived on archive.org. The Skyline README states that development has ended and that, in response to a request from Nintendo's authorized representative, the owner removed the source code from all branches and tags under their control. Whether a parent repository on GitHub still responds is a separate question from whether the original complete source code still exists anywhere.
Moreover, a takedown or source removal on GitHub does not allow one to conclude that the code has vanished from local copies, other hosting services, or archives. We have not individually verified the current status of all 405 repositories. If a valid counter-notice is filed and Nintendo wishes to maintain the takedown, GitHub's policy would next require legal proceedings seeking an injunction. Whether the README-only repositories restore their code, or whether the repositories returning 451 file counter-notices, will determine whether this round of enforcement becomes a permanent block on distribution or not.