Skip to content

Commit 477f8f1

Browse files
author
dmca-sync-bot
committed
Process DMCA request
1 parent 15f941d commit 477f8f1

File tree

1 file changed

+93
-0
lines changed

1 file changed

+93
-0
lines changed

2025/12/2025-12-10-cerva.md

Lines changed: 93 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,93 @@
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+
**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.**
6+
7+
Yes, I am authorized to act on the copyright owner's behalf.
8+
9+
**Are you submitting a revised DMCA notice after GitHub Trust & Safety requested you make changes to your original notice?**
10+
11+
Yes
12+
13+
**Please provide the Zendesk ticket number of your previously submitted notice. Zendesk ticket numbers are 7 digit ID numbers located in the subject line or body of your confirmation email.**
14+
15+
3935671
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 an authorized representative of Ceva Inc. (https://www.ceva-ip.com/), the legal owner of the copyrighted software and related intellectual property contained in the repository. As part of my role at the company, I am authorized to act on behalf of the copyright owner in matters involving intellectual property protection, including submitting DMCA takedown notices.
24+
25+
**Please provide a detailed description of the original copyrighted work that has allegedly been infringed.**
26+
27+
The infringed work consists of proprietary source code and related documentation developed by Ceva Inc. and its subsidiaries as part of its Wi-Fi technology intellectual property. This includes unique algorithms, architecture, configuration files, and implementation code that are confidential, and not publicly distributed and are protected under copyright law.
28+
29+
**If the original work referenced above is available online, please provide a URL.**
30+
31+
Not available online
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+
[private]
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+
Our company employs standard technological and organizational measures to control access to our copyrighted software and internal repositories.
50+
Access to the source code is restricted to authorized employees, contractors and customers through authenticated user accounts, role-based permissions, and controlled development environments.
51+
52+
**How is the accused project designed to circumvent your technological protection measures?**
53+
54+
By copying and publishing our restricted source code in a public repository, the accused project bypasses the private access controls we use to protect the material. This undermines the technological measures designed to limit access to authorized users only.
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+
https://github.com/Headcrabed/ceva_wifi6
59+
https://github.com/jakibaki/ceva_wifi6
60+
https://github.com/lurenjia1213/ceva_wifi6
61+
https://github.com/mfkiwl/ceva_wifi6
62+
https://github.com/raresifrim/ceva_wifi6
63+
https://github.com/sionsi/ceva_wifi6
64+
https://github.com/std-microblock/ceva_wifi6
65+
https://github.com/yichun79/ceva_wifi6
66+
67+
**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.**
68+
69+
**Is the work licensed under an open source license?**
70+
71+
No
72+
73+
**What would be the best solution for the alleged infringement?**
74+
75+
Reported content must be removed
76+
77+
**Do you have the alleged infringer’s contact information? If so, please provide it.**
78+
79+
**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.**
80+
81+
**I have taken <a href="https://www.lumendatabase.org/topics/22">fair use</a> into consideration.**
82+
83+
**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.**
84+
85+
**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>.**
86+
87+
**So that we can get back to you, please provide either your telephone number or physical address.**
88+
89+
[private]
90+
91+
**Please type your full name for your signature.**
92+
93+
[private]

0 commit comments

Comments
 (0)