Skip to content

Commit 79483b4

Browse files
Merge pull request #13193 from github/updates
Sync changes from upstream repository
2 parents b2ef7f0 + 55d3177 commit 79483b4

File tree

1 file changed

+67
-0
lines changed

1 file changed

+67
-0
lines changed

2023/03/2023-03-30-leaning-tech.md

Lines changed: 67 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,67 @@
1+
**Are you the copyright holder or authorized to act on the copyright owner's behalf?**
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+
I am the [private] of Leaning Technologies Ltd, owner of the copyright to CheerpX for Flash
16+
17+
**Please provide a detailed description of the original copyrighted work that has allegedly been infringed. If possible, include a URL to where it is posted online.**
18+
19+
CheerpX for Flash is a static JavaScript/WebAssembly library (constituted of multiple files including several binaries) that when added to a web page with Flash content, it transforms it on the fly into pure HTML5. Organisations self-host CheerpX for Flash (on private or publicly accessible servers) and integrate it with their applications.
20+
21+
These files were sourced from a legitimate licensee of CheerpX for Flash, which is hosting CheerpX for Flash on a publicly accessible server.
22+
23+
**What files should be taken down? Please provide URLs for each file, or if the entire repository, the repository’s URL.**
24+
25+
https://github.com/Sploder-Saptarshi/cheerpx-for-flash
26+
27+
**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.**
28+
29+
No
30+
31+
**<a href="https://docs.github.com/articles/dmca-takedown-policy#b-what-about-forks-or-whats-a-fork">Have you searched for any forks</a> of the allegedly infringing files or repositories? Each fork is a distinct repository and must be identified separately if you believe it is infringing and wish to have it taken down.**
32+
33+
No forks that we can find.
34+
35+
**Is the work licensed under an open source license?**
36+
37+
No
38+
39+
**What would be the best solution for the alleged infringement?**
40+
41+
Reported content must be removed
42+
43+
**Do you have the alleged infringer’s contact information? If so, please provide it.**
44+
45+
**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.**
46+
47+
**I have taken <a href="https://www.lumendatabase.org/topics/22">fair use</a> into consideration.**
48+
49+
**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.**
50+
51+
**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>.**
52+
53+
**So that we can get back to you, please provide either your telephone number or physical address.**
54+
55+
Correspondence address: Leaning Technologies, [private], [private], [private], [private], United Kingdom
56+
Phone number [private]: [private]
57+
Phone number [private]: [private]
58+
59+
**Please type your full legal name below to sign this request.**
60+
61+
[private]
62+
63+
64+
65+
66+
67+

0 commit comments

Comments
 (0)