Skip to content

Commit 8f05a65

Browse files
author
dmca-sync-bot
committed
Process DMCA request
1 parent 9237bd3 commit 8f05a65

File tree

1 file changed

+96
-0
lines changed

1 file changed

+96
-0
lines changed
Lines changed: 96 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,96 @@
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+
[private] have been working on code for a project that was intended to remain private and accessible only to a limited group of community members. However, one individual copied the repository and made it public without authorization. This person is now publicly presenting themselves as the owner of the code. In the past, the same individual has copied other community projects, violated software and hardware licenses, and sold open-source hardware in multiple online stores without proper compliance. They currently maintain over 700 forks of various open-source projects, with no meaningful collaboration, using GitHub primarily as a means to replicate code and hardware designs for personal gain.
20+
21+
**Please provide a detailed description of the original copyrighted work that has allegedly been infringed.**
22+
23+
The specific GitHub repository in question is https://github.com/denjhang/msx-picoverse, which is an outdated copy of [private] [private] [private] [private] that remains hosted [private] on [private] at [private]. All of the code in the public copy is [private]. The individual simply duplicated the repository, made it public, and has since behaved as if they were the original author in front of the community. As a result, multiple websites now reference that repository as the original work, when in fact it is a direct and unauthorized copy.
24+
25+
**If the original work referenced above is available online, please provide a URL.**
26+
27+
[private]
28+
29+
**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.**
30+
31+
**Based on the above, I confirm that:**
32+
33+
The entire repository is infringing
34+
35+
**Identify the full repository URL that is infringing:**
36+
37+
https://github.com/denjhang/msx-picoverse
38+
39+
**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.**
40+
41+
Yes
42+
43+
**What technological measures do you have in place and how do they effectively control access to your copyrighted material?**
44+
45+
The repository is [private] on [private]. Public copies should not exist.
46+
47+
**How is the accused project designed to circumvent your technological protection measures?**
48+
49+
The repository is [private] on [private]. Public copies should not exist.
50+
51+
**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:**
52+
53+
https://github.com/denjhang/msx-picoverse
54+
https://github.com/joskwanten/msx-picoverse
55+
https://github.com/jacaba1/msx-picoverse
56+
https://github.com/mmdas/msx-picoverse
57+
https://github.com/PanykSystem/msx-picoverse
58+
https://github.com/RebelliousX/msx-picoverse
59+
https://github.com/taupter/msx-picoverse
60+
https://github.com/VWarlock/MSX_msx-picoverse
61+
62+
**Based on the representative number of forks I have reviewed, I believe that all or most of the forks are infringing to the same extent as the parent repository.**
63+
64+
**Is the work licensed under an open source license?**
65+
66+
Yes
67+
68+
**Which license?**
69+
70+
other
71+
72+
**How do you believe the license is being violated?**
73+
74+
Yes, the person is selling products based on the original code.
75+
76+
**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.**
77+
78+
The repository is [private] on [private]. Public copies should not exist.
79+
80+
**Do you have the alleged infringer’s contact information? If so, please provide it.**
81+
82+
**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.**
83+
84+
**I have taken <a href="https://www.lumendatabase.org/topics/22">fair use</a> into consideration.**
85+
86+
**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.**
87+
88+
**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>.**
89+
90+
**So that we can get back to you, please provide either your telephone number or physical address.**
91+
92+
[private]
93+
94+
**Please type your full name for your signature.**
95+
96+
[private]

0 commit comments

Comments
 (0)