Process DMCA request

2025/03/2025-03-05-metagravity.md

@@ -0,0 +1,78 @@
+Before disabling any content in relation to this takedown notice, GitHub
+- contacted the owners of some or all of the affected repositories to give them an opportunity to [make changes](https://docs.github.com/en/github/site-policy/dmca-takedown-policy#a-how-does-this-actually-work).
+- provided information on how to [submit a DMCA Counter Notice](https://docs.github.com/en/articles/guide-to-submitting-a-dmca-counter-notice).
+
+To learn about when and why GitHub may process some notices this way, please visit our [README](https://github.com/github/dmca/blob/master/README.md#anatomy-of-a-takedown-notice).
+
+---
+
+**Are you the copyright holder or authorized to act on the copyright owner's behalf?**
+
+Yes, I am authorized to act on the copyright owner's behalf.
+
+**Are you submitting a revised DMCA notice after GitHub Trust & Safety requested you make changes to your original notice?**
+
+No
+
+**Does your claim involve content on GitHub or npm.js?**
+
+GitHub
+
+**Please describe the nature of your copyright ownership or authorization to act on the owner's behalf.**
+
+I am the [private] of [private] of metaGravity ltd and am as such authorised to speak on behalf of the company in matters including but not limited to software engineering, security, our software, IP and hardware assets.
+
+**Please provide a detailed description of the original copyrighted work that has allegedly been infringed. If possible, include a URL to where it is posted online.**
+
+[private]  
+[private]
+
+These [private] contain previous versions of our cloud platform management tool internally known as (the) Platform. It includes a system that allows users to create and manage virtual machines and related cloud resources using the MetaGravity Platform. It relies on ansible and terraform to orchestrate said resources in [private], [private] and [private] via a MetaGravity created [private]. If necessary we can supply internal documentation, tech design and diagrams.  
+The above [private] are owned by MetaGravity. No collaborator has the right to share them without written consent. The only people with access to this [private] are current employees or past employees who did not fulfil their end of the offboarding as agreed in their contract.  
+We allow past employees to share code when doing so does not infringe on the company's rights or otherwise harms it in any way.
+The user leonchist ( https://github.com/leonchist ) has forked both the above repos. This caused a security issue since they originally contained sensitive information pertaining to access and security.
+
+**What files should be taken down? Please provide URLs for each file, or if the entire repository, the repository’s URL.**
+
+These repos should be taken down:  
+https://github.com/leonchist/Binarite_CLI_V1  
+https://github.com/leonchist/Binarite-CLI-v2
+
+**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.**
+
+No
+
+**<a href="https://docs.github.com/articles/dmca-takedown-policy#b-what-about-forks-or-whats-a-fork">Have you searched for any forks</a> of the allegedly infringing files or repositories? Each fork is a distinct repository and must be identified separately if you believe it is infringing and wish to have it taken down.**
+
+Yes. We have not managed to find any other forks.
+
+**Is the work licensed under an open source license?**
+
+No
+
+**What would be the best solution for the alleged infringement?**
+
+Reported content must be removed
+
+**Do you have the alleged infringer’s contact information? If so, please provide it.**
+
+No. All we have is the user page: https://github.com/leonchist  
+If we could contact them we would have.  
+We would much prefer a conversation to this route. We would ask them to please take down the repos and share what they needed in a legal and not harmful way after a conversation with the company.  
+We understand that there are fair and good reasons to share work one might have been part of creating. We're all coders. We've all been there. But as it stands there is an unidentified user sharing private (company owned) repos without permission. If possible we would love it if github could ask them to reach out to us for a conversation.
+
+**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 <a href="https://www.lumendatabase.org/topics/22">fair use</a> into consideration.**
+
+**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.**
+
+**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>.**
+
+**So that we can get back to you, please provide either your telephone number or physical address.**
+
+[private]  
+
+**Please type your full legal name below to sign this request.**
+
+[private]