WARNING: THIS SITE IS A MIRROR OF GITHUB.COM / IT CANNOT LOGIN OR REGISTER ACCOUNTS / THE CONTENTS ARE PROVIDED AS-IS / THIS SITE ASSUMES NO RESPONSIBILITY FOR ANY DISPLAYED CONTENT OR LINKS / IF YOU FOUND SOMETHING MAY NOT GOOD FOR EVERYONE, CONTACT ADMIN AT ilovescratch@foxmail.com
Skip to content

Commit 74dd591

Browse files
author
dmca-sync-bot
committed
Process DMCA request
1 parent fdb270a commit 74dd591

File tree

1 file changed

+99
-0
lines changed

1 file changed

+99
-0
lines changed

2025/11/2025-11-12-mentari.md

Lines changed: 99 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,99 @@
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 the [private] and copyright holder of the project titled "Mentari-UNPAM", which was published on [private] GitHub account (github.com/Lukman754/Mentari-Unpam).
24+
This project, including its structure, code, and documentation, was entirely developed by [private].
25+
I have not authorized any person to redistribute, modify, or publish [private] work elsewhere.
26+
27+
**Please provide a detailed description of the original copyrighted work that has allegedly been infringed.**
28+
29+
The original project is an educational extension named Mentari, designed for [private], which includes HTML, CSS, JavaScript, and manifest files specifically structured for a browser extension.
30+
The infringing repository copied [private] entire source code and structure, renamed the project using the same name “Mentari-UNPAM”, and removed [private] name entirely from all files, replacing it with the name “B-Test3301”.
31+
32+
The MIT License [private] used requires that [private] copyright notice remains intact, but the infringer replaced it with:
33+
34+
"Copyright (c) 2025 B-Test3301"
35+
36+
This constitutes a clear license violation and false authorship claim.
37+
38+
**If the original work referenced above is available online, please provide a URL.**
39+
40+
https://github.com/lukman754/Mentari-Unpam
41+
42+
**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.**
43+
44+
**Based on the above, I confirm that:**
45+
46+
The entire repository is infringing
47+
48+
**Identify the full repository URL that is infringing:**
49+
50+
https://github.com/B-Test3301/Mentari-Unpam
51+
52+
**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.**
53+
54+
No
55+
56+
**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:**
57+
58+
**Is the work licensed under an open source license?**
59+
60+
Yes
61+
62+
**Which license?**
63+
64+
mit-license
65+
66+
**How do you believe the license is being violated?**
67+
68+
The infringer removed [private] name from the LICENSE file, replaced it with their own (“B-Test3301”), and distributed the work publicly as their own creation.
69+
This directly violates the MIT License’s requirement to retain the original copyright notice in all copies and substantial portions of the Software.
70+
71+
**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.**
72+
73+
To comply with the MIT License, the infringing repository must:
74+
75+
- Restore [private] full copyright attribution (“Copyright (c) 2025 [private]”).
76+
- Remove all false author names.
77+
- Or make the repository private or delete it entirely if attribution cannot be restored.
78+
79+
**Do you have the alleged infringer’s contact information? If so, please provide it.**
80+
81+
GitHub username: B-Test3301
82+
Profile URL: https://github.com/B-Test3301
83+
(No email available)
84+
85+
**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.**
86+
87+
**I have taken <a href="https://www.lumendatabase.org/topics/22">fair use</a> into consideration.**
88+
89+
**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.**
90+
91+
**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>.**
92+
93+
**So that we can get back to you, please provide either your telephone number or physical address.**
94+
95+
[private]
96+
97+
**Please type your full name for your signature.**
98+
99+
[private]

0 commit comments

Comments
 (0)