Skip to content

Commit 94f7f5a

Browse files
author
dmca-sync-bot
committed
Process DMCA request
1 parent bce9d76 commit 94f7f5a

1 file changed

Lines changed: 83 additions & 0 deletions

File tree

2026/07/2026-07-08-mutiny.md

Lines changed: 83 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,83 @@
1+
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).
2+
3+
---
4+
5+
**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.**
6+
7+
Yes, I am the copyright holder.
8+
9+
**Are you submitting a revised DMCA notice after GitHub Trust & Safety requested you make changes to your original notice?**
10+
11+
No
12+
13+
**Does your claim involve content on GitHub or npm.js?**
14+
15+
GitHub
16+
17+
**Please describe the nature of your copyright ownership or authorization to act on the owner's behalf.**
18+
19+
The server-side Lua source for the MUTINY
20+
Garry's Mod server, authored by [private] and privately hosted. It is not publicly
21+
licensed. The leaked files are verbatim copies of my private source.
22+
The original work is located at: [private]
23+
24+
**Please provide a detailed description of the original copyrighted work that has allegedly been infringed.**
25+
26+
The infringing material is located at:
27+
https://github.com/FrankPye1/mutinyleak1
28+
29+
**If the original work referenced above is available online, please provide a URL.**
30+
31+
https://github.com/FrankPye1/mutinyleak1
32+
33+
**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.**
34+
35+
**Based on the above, I confirm that:**
36+
37+
The entire repository is infringing
38+
39+
**Identify the full repository URL that is infringing:**
40+
41+
https://github.com/FrankPye1/mutinyleak1
42+
43+
**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.**
44+
45+
Yes
46+
47+
**What technological measures do you have in place and how do they effectively control access to your copyrighted material?**
48+
49+
Access was only limited to team members through [private].
50+
51+
This team member was fired from the company after months of poor performance and had a local copy saved to their computer.
52+
53+
**How is the accused project designed to circumvent your technological protection measures?**
54+
55+
It is the entire source code in full unedited.
56+
57+
**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:**
58+
59+
**Is the work licensed under an open source license?**
60+
61+
No
62+
63+
**What would be the best solution for the alleged infringement?**
64+
65+
Reported content must be removed
66+
67+
**Do you have the alleged infringer’s contact information? If so, please provide it.**
68+
69+
**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.**
70+
71+
**I have taken <a href="https://www.lumendatabase.org/topics/22">fair use</a> into consideration.**
72+
73+
**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.**
74+
75+
**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>.**
76+
77+
**So that we can get back to you, please provide either your telephone number or physical address.**
78+
79+
[private]
80+
81+
**Please type your full name for your signature.**
82+
83+
[private]

0 commit comments

Comments
 (0)