|
| 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 the copyright holder. |
| 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 | +4220775 |
| 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, [private], am the [private] [private] and copyright holder of the Entitely platform. [private] wrote all 480+ commits in the original repository. The infringing repository (https://github.com/DLME2024/Land-Dev-Parcel) contains [private] entire codebase. The Git history itself shows all commits attributed to [private] GitHub account ([private]). The copied repo even still references [private] original clone URL in the README. No other person contributed to this codebase. |
| 24 | + |
| 25 | +**Please provide a detailed description of the original copyrighted work that has allegedly been infringed.** |
| 26 | + |
| 27 | +Entitely is a full-stack AI-powered predevelopment automation platform for real estate that [private] designed and built from scratch. It performs parcel analysis, zoning lookup, wetlands mapping, FEMA flood zone analysis, and opportunity zone identification for [private] properties. The frontend is built with Next.js 14, TypeScript, Tailwind CSS, and Leaflet. The backend uses Python and FastAPI with Anthropic Claude AI integration. Data sources include NJ MOD-IV, FEMA NFHL, USFWS NWI, and Census API. The live application is deployed at https://entitely.vercel.app. The entire codebase was written solely by [private]. |
| 28 | + |
| 29 | +IMPORTANT CLARIFICATION: The infringing repository (DLME2024/Land-Dev-Parcel) is NOT a GitHub fork. It was not created using GitHub's "Fork" button and does not maintain a fork relationship with [private] original repo. The user cloned [private] repository and re-pushed the entire codebase as a new, independent repository under their own account, severing all attribution and connection to [private] original work. This is distinct from forking under GitHub's TOS Section D5. A fork preserves a visible link to the original repository and credits the original author — none of that exists here. The infringing repo shows 0 forks on GitHub's fork graph because it is listed as a standalone repository. The only contributor listed is [private] (@[private]) because they copied [private] entire Git history. The README still contains [private] original clone URL ([private]). The user made no modifications — it is a verbatim copy. At the time the code was copied, [private] repository did not include an open-source license, meaning all rights were reserved. No permission was granted for anyone to copy, redistribute, or republish [private] code outside of GitHub's built-in fork mechanism. |
| 30 | + |
| 31 | +**If the original work referenced above is available online, please provide a URL.** |
| 32 | + |
| 33 | +[private] and https://entitely.vercel.app |
| 34 | + |
| 35 | +**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.** |
| 36 | + |
| 37 | +**Based on the above, I confirm that:** |
| 38 | + |
| 39 | +The entire repository is infringing |
| 40 | + |
| 41 | +**Identify the full repository URL that is infringing:** |
| 42 | + |
| 43 | +https://github.com/DLME2024/Land-Dev-Parcel |
| 44 | + |
| 45 | +**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.** |
| 46 | + |
| 47 | +Yes |
| 48 | + |
| 49 | +**What technological measures do you have in place and how do they effectively control access to your copyrighted material?** |
| 50 | + |
| 51 | +The repository is set to [private] on [private], which restricts access to only authorized users. GitHub's [private] repository setting prevents anyone who has not been explicitly granted access from viewing, cloning, or downloading the code. |
| 52 | + |
| 53 | +**How is the accused project designed to circumvent your technological protection measures?** |
| 54 | + |
| 55 | +The repository was public at the time it was copied. The accused party cloned the repository and re-uploaded the entire codebase to a new public repository under their own account (DLME2024/Land-Dev-Parcel). The repository has since been made private to prevent further unauthorized copying. |
| 56 | + |
| 57 | +**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:** |
| 58 | + |
| 59 | +**Is the work licensed under an open source license?** |
| 60 | + |
| 61 | +No |
| 62 | + |
| 63 | +**What would be the best solution for the alleged infringement?** |
| 64 | + |
| 65 | +Reported content must be removed |
| 66 | + |
| 67 | +**Do you have the alleged infringer’s contact information? If so, please provide it.** |
| 68 | + |
| 69 | +No. The infringing party's GitHub account is DLME2024. I do not have any other contact information for this user. |
| 70 | + |
| 71 | +**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.** |
| 72 | + |
| 73 | +**I have taken <a href="https://www.lumendatabase.org/topics/22">fair use</a> into consideration.** |
| 74 | + |
| 75 | +**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.** |
| 76 | + |
| 77 | +**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>.** |
| 78 | + |
| 79 | +**So that we can get back to you, please provide either your telephone number or physical address.** |
| 80 | + |
| 81 | +[private] |
| 82 | + |
| 83 | +**Please type your full name for your signature.** |
| 84 | + |
| 85 | +[private] |
0 commit comments