Skip to content

Commit b3f5e03

Browse files
author
dmca-sync-bot
committed
Process DMCA request
1 parent b4f8ef8 commit b3f5e03

1 file changed

Lines changed: 89 additions & 0 deletions

File tree

2026/03/2026-03-27-abstract.md

Lines changed: 89 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,89 @@
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+
One or more repositories in this DMCA takedown notice has been processed in accordance with GitHub's prohibition on sharing unauthorized product licensing keys, software for generating unauthorized product licensing keys, and/or software for bypassing checks for product licensing keys.
6+
7+
You can learn more in [GitHub's Acceptable Use Policies](https://docs.github.com/en/github/site-policy/github-acceptable-use-policies).
8+
9+
---
10+
11+
**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.**
12+
13+
Yes, I am the copyright holder.
14+
15+
**Are you submitting a revised DMCA notice after GitHub Trust & Safety requested you make changes to your original notice?**
16+
17+
No
18+
19+
**Does your claim involve content on GitHub or npm.js?**
20+
21+
GitHub
22+
23+
**Please describe the nature of your copyright ownership or authorization to act on the owner's behalf.**
24+
25+
I am the [private] [private] and copyright owner of the software project called Λbstract. The software was developed by [private] across several private Git repositories beginning in April and continuing through the present. The project includes more than 250 total commits across its development history and version 1.6 was released on July 17. The repository reported in this notice appeared on July 24 and distributes a modified unauthorized build of [private] software.
26+
27+
**Please provide a detailed description of the original copyrighted work that has allegedly been infringed.**
28+
29+
Λbstract is proprietary software that [private] developed and distribute privately to authorized users. It contains a licensing verification mechanism implemented in the file popup.js which sends a request to [private] authorization server to determine whether a user is allowed to use the software and for how long. If authorization fails, the software prevents activation of its functionality. The project was developed across multiple private repositories starting April 7 and currently contains over 100 commits in the active repository alone.
30+
31+
**If the original work referenced above is available online, please provide a URL.**
32+
33+
**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.**
34+
35+
**Based on the above, I confirm that:**
36+
37+
The entire repository is infringing
38+
39+
**Identify the full repository URL that is infringing:**
40+
41+
https://github.com/alialtay44/lothlorien
42+
43+
**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.**
44+
45+
Yes
46+
47+
**What technological measures do you have in place and how do they effectively control access to your copyrighted material?**
48+
49+
Λbstract contains a licensing verification mechanism implemented in the file popup.js. When the software is used, it sends a request to [private] authorization server to verify whether the user is permitted to run the software and for how long the license remains valid. The server checks a database of authorized users and returns whether the user is allowed and the expiration time. If the verification fails or the license is expired, the software blocks activation of its functionality and prevents the bot from running. This server-side license verification system is designed to control access to the paid software and prevent unauthorized use.
50+
51+
**How is the accused project designed to circumvent your technological protection measures?**
52+
53+
The reported repository distributes a ZIP archive containing a modified build of [private] software. In the original implementation, the licensing system verifies authorization using [private] server endpoint. In the distributed build contained in the repository, this verification mechanism has been modified so that the authorization request is redirected to a different endpoint controlled by the distributor instead of [private] original server. This modification allows the software to bypass the original license-verification system and enables unauthorized users to run the software without obtaining a valid license from [private].
54+
55+
**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:**
56+
57+
**Is the work licensed under an open source license?**
58+
59+
No
60+
61+
**What would be the best solution for the alleged infringement?**
62+
63+
Reported content must be removed
64+
65+
**Do you have the alleged infringer’s contact information? If so, please provide it.**
66+
67+
GitHub username: alialtay44
68+
69+
Repository distributing the infringing material:
70+
https://github.com/alialtay44/lothlorien
71+
72+
Direct file containing the infringing software:
73+
https://github.com/alialtay44/lothlorien/blob/main/lothlorien.zip
74+
75+
**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.**
76+
77+
**I have taken <a href="https://www.lumendatabase.org/topics/22">fair use</a> into consideration.**
78+
79+
**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.**
80+
81+
**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>.**
82+
83+
**So that we can get back to you, please provide either your telephone number or physical address.**
84+
85+
[private]
86+
87+
**Please type your full name for your signature.**
88+
89+
[private]

0 commit comments

Comments
 (0)