Skip to content

Commit 092098f

Browse files
Merge pull request #20206 from github/updates
Added 2026/04/2026-04-06-source-code.md
2 parents 17c8c46 + 14866fc commit 092098f

1 file changed

Lines changed: 70 additions & 0 deletions

File tree

2026/04/2026-04-06-source-code.md

Lines changed: 70 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,70 @@
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+
We are the original developers of the website and hold the rights to its content in collaboration with the copyright owner. Our involvement includes the design, development, and maintenance of the site over multiple years, as documented in our internal records and associated repositories.
16+
17+
We are authorized to act on behalf of the copyright owner in matters concerning the protection and enforcement of these rights, including addressing unauthorized distribution or reproduction of the website’s content.
18+
19+
**Please provide a detailed description of the original copyrighted work that has allegedly been infringed.**
20+
21+
The website in question was developed collaboratively by us and the copyright owner, as evidenced by the [private] repositories we have provided, which show that the project has been in development for several years. The Original url is our repo is privated since the beginning to have users not see the files and keeping it private
22+
23+
Due to a minor security oversight, the website was unintentionally made publicly accessible on our web hosting environment. As a result, a small number of users were able to download the site. Unfortunately, one of those individuals subsequently uploaded the content to GitHub without authorization.
24+
25+
**If the original work referenced above is available online, please provide a URL.**
26+
27+
[private]
28+
[private]
29+
30+
**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.**
31+
32+
**Based on the above, I confirm that:**
33+
34+
The entire repository is infringing
35+
36+
**Identify the full repository URL that is infringing:**
37+
38+
https://github.com/lootedvyza/PSXGems-Gambling-Website
39+
40+
**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.**
41+
42+
No
43+
44+
**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:**
45+
46+
**Is the work licensed under an open source license?**
47+
48+
No
49+
50+
**What would be the best solution for the alleged infringement?**
51+
52+
Reported content must be removed
53+
54+
**Do you have the alleged infringer’s contact information? If so, please provide it.**
55+
56+
**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.**
57+
58+
**I have taken <a href="https://www.lumendatabase.org/topics/22">fair use</a> into consideration.**
59+
60+
**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.**
61+
62+
**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>.**
63+
64+
**So that we can get back to you, please provide either your telephone number or physical address.**
65+
66+
[private]
67+
68+
**Please type your full name for your signature.**
69+
70+
[private]

0 commit comments

Comments
 (0)