Skip to content

Commit 405c817

Browse files
Merge pull request #20332 from github/updates
Added 2026/04/2026-04-09-w3f.md
2 parents 16519ef + 1109cfc commit 405c817

File tree

1 file changed

+93
-0
lines changed

1 file changed

+93
-0
lines changed

2026/04/2026-04-09-w3f.md

Lines changed: 93 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,93 @@
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 authorized to act on the copyright owner's behalf.
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 [private] and [private] [private] for Web 3.0 Technologies Foundation (W3F). W3F is the owner of Polkadot trademark.
24+
25+
the infringing person is copying Polkadot/Parity Technologies Ltd repos and replaces names and credits (mostly using AI tooling), like "(C) Parity Technologies (UK) Ltd" becomes "(C) [private]", and "Polkadot" becomes "[private]", etc.
26+
27+
they also reference a website that is very similar to the polkadot.com website.
28+
29+
they also use a very similar variation of our Polkadot logo, under the name Pezkuwi
30+
31+
**Please provide a detailed description of the original copyrighted work that has allegedly been infringed.**
32+
33+
this is the original copyrighted repo https://github.com/paritytech/polkadot-sdk
34+
35+
here you see how it has been amended with some AI model https://github.com/pezkuwichain/pezkuwi-sdk/commit/f2deb2b2968d6d6e06753240564a73b2aa7de5e0
36+
37+
**If the original work referenced above is available online, please provide a URL.**
38+
39+
**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.**
40+
41+
**Based on the above, I confirm that:**
42+
43+
The entire repository is infringing
44+
45+
**Identify the full repository URL that is infringing:**
46+
47+
https://github.com/pezkuwichain/pezkuwi-sdk
48+
49+
**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.**
50+
51+
No
52+
53+
**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:**
54+
55+
**Is the work licensed under an open source license?**
56+
57+
Yes
58+
59+
**Which license?**
60+
61+
apache-license-2.0
62+
63+
**How do you believe the license is being violated?**
64+
65+
when you use or redistribute the software (source or binary), even if is open source, you typically must:
66+
67+
- Include a copy of the Apache 2.0 license text with the distribution. (the user did not)
68+
69+
- Preserve copyright, license, and attribution notices that are already in the work. (the user did not)
70+
71+
State significant changes you made (commonly done in headers, changelog, or a notice). (the user did not)
72+
73+
**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.**
74+
75+
adequate mentioning of the use of the license as mentioned above
76+
77+
**Do you have the alleged infringer’s contact information? If so, please provide it.**
78+
79+
**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.**
80+
81+
**I have taken <a href="https://www.lumendatabase.org/topics/22">fair use</a> into consideration.**
82+
83+
**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.**
84+
85+
**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>.**
86+
87+
**So that we can get back to you, please provide either your telephone number or physical address.**
88+
89+
[private]
90+
91+
**Please type your full name for your signature.**
92+
93+
[private]

0 commit comments

Comments
 (0)