Merge pull request #17987 from github/updates

Added 2025/06/2025-06-25-homigrad-rework.md

Author: dmca-sync-bot

2025/06/2025-06-25-homigrad-rework.md

@@ -0,0 +1,92 @@
+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.**
+
+[private] one of the [private] of the Homigrad Rework project and one of the [private] to its [private]. The [private] of the [private] ([private]) has given me every right to file a DMCA complaint. [private] also the [private] of some parts of the code and the [private] of some commits.
+
+**Please provide a detailed description of the original copyrighted work that has allegedly been infringed.**
+
+The repository attached in this complaint is a repository with a Garry's mod game server build called Homigrad REWORK. It consists entirely of our code/code, which we are authorized to use. The Homigrad REWORK [private] has always been private and its code has never been publicly distributed.
+
+**If the original work referenced above is available online, please provide a URL.**
+
+[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/chechensky/homigrad-rework-2025
+
+**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?**
+
+I maintain multiple layers of access control for [private] code:  
+1. Source code resides in a private [private] [private] with permissions limited strictly to trusted administrators;  
+2. Server-side code is kept on a private server accessible only via SSH/RCON/FTP, secured with strong passwords and unique access tokens;  
+Both the repository and server environments are not publicly accessible—no direct public hosting or download links are available.
+
+These combined measures effectively restrict access to authorized personnel only. Without valid credentials, neither the repository nor the server content is accessible to any third party.
+
+**How is the accused project designed to circumvent your technological protection measures?**
+
+The infringing party obtained a complete copy of our server-side code—never publicly released—by exploiting a backdoor in our private server environment.
+
+This method bypassed all technological protections in place:  
+1.Accessing server files directly without SSH/RCON/FTP authentication;  
+2. No repository access was granted—they never had credentials for the private repo;  
+The code was then uploaded to a public GitHub repo (https://github.com/chechensky/homigrad-rework-2025), circumventing all our access controls.
+
+Thus, the infringer unlawfully bypassed every layer of technical protection we had set up, obtaining and publishing content to which they never had authorized access.
+
+**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.**
+
+github.com/chechensky  
+[private]
+
+**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]