From e2932d1d58e1463a3512e689719e5e6a4a3a44cb Mon Sep 17 00:00:00 2001 From: dmca-sync-bot Date: Mon, 20 Jul 2026 19:25:21 +0000 Subject: [PATCH] Process DMCA request --- 2026/07/2026-07-20-dimensional.md | 44 +++++++++++++++++++++++++++++++ 1 file changed, 44 insertions(+) create mode 100644 2026/07/2026-07-20-dimensional.md diff --git a/2026/07/2026-07-20-dimensional.md b/2026/07/2026-07-20-dimensional.md new file mode 100644 index 0000000000..b296b07400 --- /dev/null +++ b/2026/07/2026-07-20-dimensional.md @@ -0,0 +1,44 @@ +[private] +[private] +[private] + +Goodwin Procter LLP +[private] +[private] +[private] +[private] + +Attn: DMCA Agent +[private] +[private] + +RE: Request for Immediate Removal of Dimensional, Inc. Stolen Trade Secrets and Copyrights from GitHub Repositories; DMCA Takedown Notice + +To Whom it May Concern: + +Our firm represents Dimensional, Inc. (“Dimensional”) and I write to follow up on my April 27, 2026 and May 20, 2026 letters, on behalf of Dimensional to request that GitHub remove code taken from Dimensional without authorization by a former consultant, [private] (“[private]”) [private] , and committed by [private] into other non-Dimensional GitHub repositories. I have read and understand GitHub’s Guide to Filing a DMCA Notice, and reformatted Dimensional’s takedown request accordingly. We hereby reiterate Dimensional’s request that GitHub immediately (1) remove all of private Dimensional code from the public view and (2) remove access to any Dimensional’s code added by [private] to any private GitHub repositories that are not controlled by Dimensional. + +In particular, we appreciate GitHub’s May 22, 2026 email to us advising that “at least one of the repositories in [our] takedown notice has been forked” and identifying the following forked repository: https://github.com/ArchAnalytica/vector_navigation_stack/network/members. We have investigated this and we do wish to have the following forks in this repository disabled as they contain private Dimensional code that was misappropriated by [private], as described in our prior letters: + +https://github.com/ngo275/vector_navigation_stack +https://github.com/ArchAnalytica/vector_navigation_stack +https://github.com/binbin2002/vector_navigation_stack +https://github.com/datbuiq/vector_navigation_stack_chk +https://github.com/yangfengzzz/vector_navigation_stack +https://github.com/yusenthebot/vector_navigation_stack + +As noted in our prior takedown notices, it recently came to Dimensional’ s attention that [private], [private], took Dimensional’s code from Dimensional’s private GitHub repository ([private]) and copied it into a public repository on GitHub for “[private],” without authorization, available here: [private]. A list of 83 of Dimensional’s trade secrets, copyrighted materials, and IP taken by [private] without authorization and committed by [private] to the [private] public repository is attached hereto as Exhibit A (the “Compromised IP”). + +Some or all of these trade secrets, copyrighted materials, and IP are also present in the forked repositories identified by GitHub in its aforementioned May 22 email. The Compromised IP that [private] committed to [private]’ public repository and within the forked repository identified by GitHub is owned by Dimensional and constitutes Dimensional’s confidential and proprietary trade secrets and copyrighted materials, which it takes substantial efforts to keep confidential. Indeed, [private] executed a Confidential Inventions and Assignment Agreement before he began working for Dimensional and as a precondition to him being granted access to Dimensional’s private GitHub repository. Dimensional also conveyed to [private] multiple times that this code was confidential and proprietary—something [private] acknowledged. To remedy the infringement, Dimensional requests that GitHub promptly remove the Compromised IP from public view and remove [private] access to the Compromised IP as quickly as possible in hopes of mitigating this substantial risk of irreparable harm to its business. While, under normal circumstances we would ask that GitHub delete this copyrighted material from [private] private GitHub account, evidence of [private] wrongdoing must be preserved for potential civil and criminal action against [private]. Thus, we ask GitHub to cut off public access and [private] access to Dimensional’s stolen copyrighted materials but preserve the evidence on its back end servers. The unauthorized use of the Company’s copyrighted materials on the GitHub website constitutes a violation of the DMCA, copyright infringement, state common law torts, and violation of unfair + +[private] + +trade statutes. This letter constitutes notice to GitHub under the DMCA and, to avoid liability, it must “act[] expeditiously to remove, or disable access to, the [infringing] material.” If it does not, Dimensional would likely be entitled to injunctive and monetary relief. Please promptly confirm that you have removed the infringing materials from GitHub’s website. + +Both Dimensional and 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 (Dimensional), or its agent, or the law. I have taken fair use into consideration. I swear, under penalty of perjury, that the information in this notification is accurate and that I am authorized to act on behalf of the owner (Dimensional), of an exclusive right that is allegedly infringed. + +If you have any questions or need additional information to facilitate this request, please do not hesitate to reach out. Dimensional reserves its rights to pursue this matter through all available legal means. Nothing herein should be constituted as a waiver by Dimensional of any right to relief to which it is entitled. + +Warm Regards, +[private] +[private]