Skip to content

Commit 4eed6a8

Browse files
author
dmca-sync-bot
committed
Process DMCA request
1 parent b2022fc commit 4eed6a8

File tree

1 file changed

+74
-0
lines changed

1 file changed

+74
-0
lines changed

2025/12/2025-12-17-mesta.md

Lines changed: 74 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,74 @@
1+
**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.**
2+
3+
Yes, I am authorized to act on the copyright owner's behalf.
4+
5+
**Are you submitting a revised DMCA notice after GitHub Trust & Safety requested you make changes to your original notice?**
6+
7+
No
8+
9+
**Does your claim involve content on GitHub or npm.js?**
10+
11+
GitHub
12+
13+
**Please describe the nature of your copyright ownership or authorization to act on the owner's behalf.**
14+
15+
The copyrighted work consists of proprietary source code and related materials developed by employees and contractors of Mesta in the course of their employment or engagement, with all intellectual property rights assigned to and owned exclusively by Mesta. The code is maintained in private, internal repositories and has never been authorized for public distribution. I am duly authorized to act on behalf of Mesta, the copyright owner, with respect to enforcement of its exclusive rights, including submission of takedown requests for unauthorized copies of its source code.
16+
17+
**Please provide a detailed description of the original copyrighted work that has allegedly been infringed.**
18+
19+
The copyrighted work consists of Mesta’s proprietary backend application source code, including but not limited to application logic, APIs, system architecture, configuration files, database interaction layers, authentication and authorization mechanisms, business rules, and supporting scripts and libraries (collectively, the “Mesta Codebase”). The code was developed by Mesta’s employees and contractors within the scope of their employment or engagement and is owned exclusively by Mesta pursuant to intellectual property assignment and confidentiality obligations.
20+
The Mesta Codebase supports Mesta’s internal and customer-facing technology infrastructure and embodies original expression in its structure, sequence, organization, logic flows, naming conventions, and implementation choices. It is maintained in private, access-restricted repositories and internal systems and is not open source, has not been licensed for public use, and has never been authorized for publication or distribution on public platforms such as GitHub.
21+
The material posted in the identified GitHub repository reproduces substantial portions of this proprietary source code without authorization, including files, directories, and implementations that are identical or substantially similar to Mesta’s internal codebase.
22+
23+
**If the original work referenced above is available online, please provide a URL.**
24+
25+
www.mesta.xyz
26+
27+
**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.**
28+
29+
**Based on the above, I confirm that:**
30+
31+
The entire repository is infringing
32+
33+
**Identify the full repository URL that is infringing:**
34+
35+
https://github.com/travis-aplus/Mesta-Api
36+
37+
**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.**
38+
39+
No
40+
41+
**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:**
42+
43+
**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.**
44+
45+
**Is the work licensed under an open source license?**
46+
47+
No
48+
49+
**What would be the best solution for the alleged infringement?**
50+
51+
Reported content must be removed
52+
53+
**Do you have the alleged infringer’s contact information? If so, please provide it.**
54+
55+
Last name: [private]
56+
First name: [private]
57+
DOB: [private]
58+
Address: [private]
59+
60+
**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.**
61+
62+
**I have taken <a href="https://www.lumendatabase.org/topics/22">fair use</a> into consideration.**
63+
64+
**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.**
65+
66+
**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>.**
67+
68+
**So that we can get back to you, please provide either your telephone number or physical address.**
69+
70+
[private]
71+
72+
**Please type your full name for your signature.**
73+
74+
[private]

0 commit comments

Comments
 (0)