|
| 1 | +Dear GitHub Copyright Team, |
| 2 | + |
| 3 | +I have read and understand GitHub's Guide to Filing a DMCA Notice. |
| 4 | + |
| 5 | +1. Copyrighted Work |
| 6 | +I am the copyright owner of the original source code contained in [private] private [private] repository. |
| 7 | + |
| 8 | +Repository Owner: [private] |
| 9 | + |
| 10 | +Repository Name: [private] |
| 11 | + |
| 12 | +Repository URL: |
| 13 | +[private] |
| 14 | + |
| 15 | +This repository is private and contains [private] original proprietary source code. [private] created and own the work contained in this repository. The repository was developed by [private] and has never been publicly released. |
| 16 | + |
| 17 | +2. Infringing Material |
| 18 | +The infringing repository is: |
| 19 | + |
| 20 | +Repository Owner: MohammadSiddiq05 |
| 21 | + |
| 22 | +Repository Name: flynget-mobile-application |
| 23 | + |
| 24 | +Repository URL: |
| 25 | +https://github.com/MohammadSiddiq05/flynget-mobile-application |
| 26 | + |
| 27 | +The individual identified above previously had collaborator access to [private] private repository. That access was granted solely for the purpose of collaborating on [private] project. It did not authorize copying, reproducing, retaining, or creating a separate repository containing [private] copyrighted source code. |
| 28 | + |
| 29 | +Without [private] authorization, the individual created a separate GitHub repository using [private] project. Since they already had a local copy of [private] repository through their collaborator access, they created their own repository under their GitHub account and pushed [private] project to that repository. |
| 30 | + |
| 31 | +The infringing repository is an unauthorized copy of [private] private repository. |
| 32 | + |
| 33 | +The copied repository contains substantially identical content, including but not limited to: |
| 34 | + |
| 35 | +The complete React Native Expo application. |
| 36 | +The same project structure and directory hierarchy. |
| 37 | +The same source code. |
| 38 | +The same backend integration. |
| 39 | +The same assets and resources. |
| 40 | +The same package configuration files. |
| 41 | +The same project configuration. |
| 42 | +The same environment configuration (.env). |
| 43 | +Other proprietary project files. |
| 44 | +This was not an independently developed project. It is a reproduction of [private] entire private repository. |
| 45 | + |
| 46 | +3. How [private] Discovered the Infringing Repository |
| 47 | +Because the infringing repository was private, [private] could not have discovered it through GitHub search. |
| 48 | + |
| 49 | +[private] discovered the repository because the alleged infringer sent [private] a GitHub collaborator invitation to their newly created private repository. |
| 50 | + |
| 51 | +After viewing the repository through that invitation, [private] discovered that it contained [private] project copied from [private] private repository. |
| 52 | + |
| 53 | +[private] also viewed the deployed version of the project associated with that repository. The deployed application was substantially identical to [private] own project, further confirming that the repository was created from [private] copyrighted work rather than independently developed. |
| 54 | + |
| 55 | +The deployed project link is avilable on repository you can view the proj from there its same as [private] |
| 56 | + |
| 57 | +you can also view the both repository .creation date and also the commit history and code |
| 58 | + |
| 59 | +I am attaching supporting evidence, including screenshots of: |
| 60 | + |
| 61 | +The collaborator invitation. |
| 62 | +The infringing private repository. |
| 63 | +The deployment associated with the repository. |
| 64 | +[private] original private repository. |
| 65 | +Additional screenshots demonstrating that the contents are substantially identical. |
| 66 | +4. Remedy Requested |
| 67 | +I respectfully request that GitHub remove the infringing repository because it contains an unauthorized copy of [private] copyrighted private repository. |
| 68 | + |
| 69 | +If GitHub requires any additional information or evidence, I am willing to provide it promptly. |
| 70 | + |
| 71 | +5. Contact Information |
| 72 | +Name: [private] |
| 73 | + |
| 74 | +GitHub Username: [private] |
| 75 | + |
| 76 | +Email: [private] |
| 77 | + |
| 78 | +Phone: [private] |
| 79 | + |
| 80 | +Address: |
| 81 | + |
| 82 | +[private] |
| 83 | + |
| 84 | +6. Alleged Infringer |
| 85 | +GitHub Username: MohammadSiddiq05 |
| 86 | + |
| 87 | +Repository: |
| 88 | +https://github.com/MohammadSiddiq05/flynget-mobile-application |
| 89 | + |
| 90 | +7. Good Faith Statement |
| 91 | +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. I have taken fair use into consideration. |
| 92 | + |
| 93 | +8. Statement Under Penalty of Perjury |
| 94 | +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. |
| 95 | + |
| 96 | +9. Electronic Signature |
| 97 | +[private] |
0 commit comments