|
| 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 | +**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.** |
| 5 | + |
| 6 | +Yes, I am authorized to act on the copyright owner's behalf. |
| 7 | + |
| 8 | +**Are you submitting a revised DMCA notice after GitHub Trust & Safety requested you make changes to your original notice?** |
| 9 | + |
| 10 | +Yes |
| 11 | + |
| 12 | +**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.** |
| 13 | + |
| 14 | +4284952 |
| 15 | + |
| 16 | +**Does your claim involve content on GitHub or npm.js?** |
| 17 | + |
| 18 | +GitHub |
| 19 | + |
| 20 | +**Please describe the nature of your copyright ownership or authorization to act on the owner's behalf.** |
| 21 | + |
| 22 | +Jeppesen ForeFlight is the rightful owner of the intellectual property and proprietary assets contained within the referenced repository. The content has been developed internally and is not authorized for public distribution in any form. |
| 23 | + |
| 24 | +I am authorized to act on behalf of Jeppesen ForeFlight in matters related to intellectual property protection, security, and enforcement. This includes initiating takedown requests and engaging with third parties to prevent unauthorized disclosure or misuse of our assets. |
| 25 | + |
| 26 | +**Please provide a detailed description of the original copyrighted work that has allegedly been infringed.** |
| 27 | + |
| 28 | +The original copyrighted work consists of proprietary software components, internal code structures, and associated resources developed and maintained by Jeppesen ForeFlight as part of its aviation technology platform. This includes application logic, configuration frameworks, APIs, compiled binaries, and supporting documentation that are integral to the operation, security, and performance of our services. |
| 29 | + |
| 30 | +These materials are not open source and are strictly restricted to authorized internal use and controlled distribution. They are protected under applicable copyright laws and form a critical part of Jeppesen ForeFlight’s intellectual property portfolio. |
| 31 | + |
| 32 | +The content identified in the referenced repository reproduces and/or exposes portions of these proprietary assets without authorization. This includes code and related materials that appear to be directly copied or derived from our internal systems. |
| 33 | + |
| 34 | +Additionally, we have identified a [private] thread ([private]) associated with this repository that provides further context on the intent and distribution of the material. The discussion indicates awareness and active sharing of the repository in a manner that promotes unauthorized access and dissemination of proprietary content. This reinforces our assessment that the exposure is not incidental, but a deliberate act that contributes to infringement and misuse of Jeppesen ForeFlight’s intellectual property. |
| 35 | + |
| 36 | +**If the original work referenced above is available online, please provide a URL.** |
| 37 | + |
| 38 | +https://github.com/StarNumber12046/Marinvent |
| 39 | + |
| 40 | +**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.** |
| 41 | + |
| 42 | +**Based on the above, I confirm that:** |
| 43 | + |
| 44 | +The entire repository is infringing |
| 45 | + |
| 46 | +**Identify the full repository URL that is infringing:** |
| 47 | + |
| 48 | +https://github.com/StarNumber12046/Marinvent |
| 49 | + |
| 50 | +**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.** |
| 51 | + |
| 52 | +Yes |
| 53 | + |
| 54 | +**What technological measures do you have in place and how do they effectively control access to your copyrighted material?** |
| 55 | + |
| 56 | +Access to Jeppesen ForeFlight’s proprietary code and related assets is restricted through enterprise access controls, including authentication mechanisms, role-based access, and controlled internal repositories. These measures are designed to prevent unauthorized access, distribution, or exposure of copyrighted material. |
| 57 | + |
| 58 | +**How is the accused project designed to circumvent your technological protection measures?** |
| 59 | + |
| 60 | +The accused project appears to redistribute and expose proprietary Jeppesen ForeFlight code and related assets outside of our controlled environment, thereby bypassing the access controls we have in place. |
| 61 | + |
| 62 | +Access to our copyrighted materials is restricted through authenticated, role-based systems and controlled internal repositories. The content in the repository is not obtained through any authorized distribution channel, which indicates that these protections have been circumvented, either through unauthorized extraction, reuse of restricted materials, or redistribution of compiled and/or decompiled components. |
| 63 | + |
| 64 | +By making this content publicly accessible, the project effectively nullifies the intended access restrictions and enables unauthorized use and further dissemination of protected intellectual property. |
| 65 | + |
| 66 | +**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:** |
| 67 | + |
| 68 | +**Is the work licensed under an open source license?** |
| 69 | + |
| 70 | +No |
| 71 | + |
| 72 | +**What would be the best solution for the alleged infringement?** |
| 73 | + |
| 74 | +Reported content must be removed |
| 75 | + |
| 76 | +**Do you have the alleged infringer’s contact information? If so, please provide it.** |
| 77 | + |
| 78 | +No |
| 79 | + |
| 80 | +**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.** |
| 81 | + |
| 82 | +**I have taken <a href="https://www.lumendatabase.org/topics/22">fair use</a> into consideration.** |
| 83 | + |
| 84 | +**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.** |
| 85 | + |
| 86 | +**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>.** |
| 87 | + |
| 88 | +**So that we can get back to you, please provide either your telephone number or physical address.** |
| 89 | + |
| 90 | +[private] |
| 91 | + |
| 92 | +**Please type your full name for your signature.** |
| 93 | + |
| 94 | +[private] |
0 commit comments