Merge pull request #20939 from github/updates

Added 2026/06/2026-06-23-euphoria.md

Author: dmca-sync-bot

2026/06/2026-06-23-euphoria.md

@@ -0,0 +1,81 @@
+While GitHub did not find sufficient information to determine a valid anti-circumvention claim, we determined that this takedown notice contains other valid copyright claim(s).
+
+---
+
+**Are you the copyright holder or authorized to act on the copyright owner's behalf? If you are submitting this notice on behalf of a company, please be sure to use an email address on the company's domain. If you use a personal email address for a notice submitted on behalf of a company, we may not be able to process it.**
+
+Yes, I am authorized to act on the copyright owner's behalf.
+
+**Are you submitting a revised DMCA notice after GitHub Trust & Safety requested you make changes to your original notice?**
+
+No
+
+**Does your claim involve content on GitHub or npm.js?**
+
+GitHub
+
+**Please describe the nature of your copyright ownership or authorization to act on the owner's behalf.**
+
+I am authorized to act on behalf of the copyright owner. The reported repository contains proprietary source code owned by our organization. The material was maintained in a private [private] organization repository and was only accessible to authorized contributors. The uploader obtained access through their contributor role but did not have authorization to publish, distribute, or make the source code publicly available.
+
+**Please provide a detailed description of the original copyrighted work that has allegedly been infringed.**
+
+The entire repository is infringing. The repository contains the complete leaked source code from our private organization repository, including software source files and related project assets. The work has never been released under an open source license and public distribution is unauthorized.
+
+**If the original work referenced above is available online, please provide a URL.**
+
+The original work was stored in a private [private] organization repository and is not publicly available. We have a public website for the project: https://euphoria.rip/ - which is a domain owned by our org owner, [private], and this is the leaked code/repository for the client: https://github.com/nazunawtf/OpenEuphoria
+
+This is our private repository on our org with all the commit history- you can see that nazunawtf was a contributor up until today: [private]
+
+**We ask that a DMCA takedown notice list every specific file in the repository that is infringing, unless the entire contents of the repository are infringing on your copyright. Please clearly state that the entire repository is infringing, OR provide the specific files within the repository you would like removed.**
+
+**Based on the above, I confirm that:**
+
+The entire repository is infringing
+
+**Identify the full repository URL that is infringing:**
+
+https://github.com/nazunawtf/OpenEuphoria
+
+**Do you claim to have any technological measures in place to control access to your copyrighted content? Please see our <a href="https://docs.github.com/articles/guide-to-submitting-a-dmca-takedown-notice#complaints-about-anti-circumvention-technology">Complaints about Anti-Circumvention Technology</a> if you are unsure.**
+
+Yes
+
+**What technological measures do you have in place and how do they effectively control access to your copyrighted material?**
+
+The source code was protected by [private] private repository access controls. Access was restricted to authorized collaborators.
+
+**How is the accused project designed to circumvent your technological protection measures?**
+
+The accused project does not circumvent any technological protection measures. The source code was accessed through authorized access to a private [private] repository and was later publicly redistributed without authorization.
+
+The uploader has indicated they intend to republish the material after removal. This further demonstrates that the public distribution is intentional and not authorized by the copyright owner.
+
+**If you are reporting an allegedly infringing fork, please note that each fork is a distinct repository and <i>must be identified separately</i>. Please read more about <a href="https://docs.github.com/articles/dmca-takedown-policy#b-what-about-forks-or-whats-a-fork">forks.</a> As forks may often contain different material than in the parent repository, if you believe any of the repositories or files in the forks are infringing, please list each fork URL below:**
+
+**Is the work licensed under an open source license?**
+
+No
+
+**What would be the best solution for the alleged infringement?**
+
+Reported content must be removed
+
+**Do you have the alleged infringer’s contact information? If so, please provide it.**
+
+**I have a good faith belief that use of the copyrighted materials described above on the infringing web pages is not authorized by the copyright owner, or its agent, or the law.**
+
+**I have taken <a href="https://www.lumendatabase.org/topics/22">fair use</a> into consideration.**
+
+**I swear, under penalty of perjury, that the information in this notification is accurate and that I am the copyright owner, or am authorized to act on behalf of the owner, of an exclusive right that is allegedly infringed.**
+
+**I have read and understand GitHub's <a href="https://docs.github.com/articles/guide-to-submitting-a-dmca-takedown-notice/">Guide to Submitting a DMCA Takedown Notice</a>.**
+
+**So that we can get back to you, please provide either your telephone number or physical address.**
+
+[private]
+
+**Please type your full name for your signature.**
+
+[private]