Skip to content

Commit 6512666

Browse files
author
dmca-sync-bot
committed
Process DMCA request
1 parent 8623e4a commit 6512666

1 file changed

Lines changed: 86 additions & 0 deletions

File tree

2026/04/2026-04-08-php-max-bot.md

Lines changed: 86 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,86 @@
1+
Before disabling any content in relation to this takedown notice, GitHub
2+
- contacted the owners of some or all of the affected repositories to give them an opportunity to [make changes](https://docs.github.com/en/github/site-policy/dmca-takedown-policy#a-how-does-this-actually-work).
3+
- provided information on how to [submit a DMCA Counter Notice](https://docs.github.com/en/articles/guide-to-submitting-a-dmca-counter-notice).
4+
5+
To learn about when and why GitHub may process some notices this way, please visit our [README](https://github.com/github/dmca/blob/master/README.md#anatomy-of-a-takedown-notice).
6+
7+
---
8+
9+
**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.**
10+
11+
Yes, I am the copyright holder.
12+
13+
**Are you submitting a revised DMCA notice after GitHub Trust & Safety requested you make changes to your original notice?**
14+
15+
No
16+
17+
**Does your claim involve content on GitHub or npm.js?**
18+
19+
GitHub
20+
21+
**Please describe the nature of your copyright ownership or authorization to act on the owner's behalf.**
22+
23+
I am the [private] [private] and [private] copyright holder of the work in question. [private] [private] wrote the code and published it under the GPL license.
24+
25+
**Please provide a detailed description of the original copyrighted work that has allegedly been infringed.**
26+
27+
The original work is a PHP Max bot (php-max-bot). The authorship attribution is documented in the commit history of [private] repository. The user NaggaDIM-DEV cloned my entire repository and replaced the original copyright and authorship comments in the source code with their own, falsely presenting themselves as the author.
28+
29+
**If the original work referenced above is available online, please provide a URL.**
30+
31+
https://github.com/GrayHoax/php-max-bot
32+
The specific commit establishing authorship: [private]
33+
34+
**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.**
35+
36+
**Based on the above, I confirm that:**
37+
38+
The entire repository is infringing
39+
40+
**Identify the full repository URL that is infringing:**
41+
42+
https://github.com/NaggaDIM-DEV/php-max-bot
43+
44+
**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.**
45+
46+
No
47+
48+
**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:**
49+
50+
https://github.com/NaggaDIM-DEV/php-max-bot
51+
52+
**Is the work licensed under an open source license?**
53+
54+
Yes
55+
56+
**Which license?**
57+
58+
gnu-general-public-license-v3.0
59+
60+
**How do you believe the license is being violated?**
61+
62+
The GPL license (GPLv2 Section 1 and Section 2(c); GPLv3 Section 4 and Section 7(b)) requires that original copyright notices be preserved in all copies and derivative works. The user removed [private] original authorship and copyright notices and replaced them with their own, which violates the license terms and constitutes false attribution.
63+
64+
**What changes can be made to bring the project into compliance with the license? For example, adding attribution, adding a license, making the repository private.**
65+
66+
The user must restore the original authorship and copyright notices as they appear in [private] original repository. Any modifications made by the user should be attributed separately (e.g., "Modified by [name]"). If the user is unwilling to restore proper attribution, the repository should be taken down.
67+
68+
**Do you have the alleged infringer’s contact information? If so, please provide it.**
69+
70+
I only know their GitHub username: NaggaDIM-DEV. Their GitHub profile: https://github.com/NaggaDIM-DEV
71+
72+
**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.**
73+
74+
**I have taken <a href="https://www.lumendatabase.org/topics/22">fair use</a> into consideration.**
75+
76+
**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.**
77+
78+
**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>.**
79+
80+
**So that we can get back to you, please provide either your telephone number or physical address.**
81+
82+
[private]
83+
84+
**Please type your full name for your signature.**
85+
86+
[private]

0 commit comments

Comments
 (0)