Skip to content

Commit 68d6dfd

Browse files
author
dmca-sync-bot
committed
Process DMCA request
1 parent b363d61 commit 68d6dfd

1 file changed

Lines changed: 85 additions & 0 deletions

File tree

Lines changed: 85 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,85 @@
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+
I am the [private] [private] and copyright owner of the source code and content published in [private] GitHub repository. [private] wrote, developed, and uploaded this code [private], and I hold full rights to the material. I have not given permission to anyone, including the reported user, to copy, upload, or distribute [private] work.
20+
21+
**Please provide a detailed description of the original copyrighted work that has allegedly been infringed.**
22+
23+
The original copyrighted work consists of a complete software project that [private] authored and published on [private] GitHub repository. This includes the source code files, folder structure, UI implementation, backend logic, styling files, assets, and the README documentation. All components of this project were created by [private]. The reported user has reproduced and uploaded the same project- including code, file structure, and documentation- on their GitHub account without [private] permission, thereby infringing on [private] copyright.
24+
25+
**If the original work referenced above is available online, please provide a URL.**
26+
27+
https://github.com/Nandukumar-koribilli/Smart_Kisan
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/kattakoushik/Tecos_clone
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 copyrighted material is controlled through GitHub's platform-level protections, including repository ownership, commit authorship verification, and permission settings. These measures ensure that only [private], as the owner, can modify or publish the original work. The infringing user bypassed these controls by copying and re-uploading [private] content to their own repository without authorization
46+
47+
**How is the accused project designed to circumvent your technological protection measures?**
48+
49+
The accused project circumvents my protection
50+
51+
measures by copying [private] source code and documentation from [private] original GitHub repository and re-uploading it into a separate repository without authorization. While GitHub allows public viewing, only the rightful owner can publish or manage the original content. By copying and presenting [private] work as their own, the accused user bypassed GitHub's built-in authorship verification and repository ownership mechanisms, which serve as the platform's technological protection measures.
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+
https://github.com/kattakoushik/Tecos_clone
56+
57+
**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.**
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+
https://github.com/kattakoushik
70+
71+
**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.**
72+
73+
**I have taken <a href="https://www.lumendatabase.org/topics/22">fair use</a> into consideration.**
74+
75+
**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.**
76+
77+
**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>.**
78+
79+
**So that we can get back to you, please provide either your telephone number or physical address.**
80+
81+
[private]
82+
83+
**Please type your full name for your signature.**
84+
85+
[private]

0 commit comments

Comments
 (0)