Merge pull request #16700 from github/updates

Added 2024/11/2024-11-26-vocaloid.md

2024/11/2024-11-25-black-jet-mobility.md

@@ -0,0 +1,88 @@
+**Are you the copyright holder or authorized to act on the copyright owner's behalf?**
+
+Yes, I am the copyright holder.
+
+**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’m writing to urgently request the removal of a repository that contains our company’s proprietary source code and sensitive credentials.
+
+The repository in question is located at:  
+https://github.com/softking0503/BlackJet-Admin  
+https://github.com/LuckyMan012359/blackJet-reactProject
+
+This repository contains:  
+1. Our proprietary source code for an entire server, uploaded without our permission.  
+2. .env files that expose private keys and credentials, putting our systems and security at risk.
+
+This content was uploaded illegally, potentially by a former developer. It violates our copyright and compromises our confidential information.
+
+Please take down this repository and disable any forks or copies as soon as possible.
+
+Owner Information:  
+Company: Black Jet Mobility Pty Ltd  
+Contact: [private]
+
+**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.**
+
+This repository contains:  
+1. Our proprietary source code for an entire server, uploaded without our permission.  
+2. .env files that expose private keys and credentials, putting our systems and security at risk.
+
+**What files should be taken down? Please provide URLs for each file, or if the entire repository, the repository’s URL.**
+
+Both repositories must be permanently removed (not simply made private), and the offending users' accounts should be banned.  
+https://github.com/softking0503/BlackJet-Admin  
+https://github.com/LuckyMan012359/blackJet-reactProject
+
+**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.**
+
+These are the ones we have found so far:  
+https://github.com/softking0503/BlackJet-Admin  
+https://github.com/LuckyMan012359/blackJet-reactProject
+
+**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 as we cannot be sure who leaked our private code
+
+**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]  
+[private]  
+
+Black Jet Mobility Pty Ltd  
+[private]  
+[private]  
+[private]  
+[private]  
+
+**Please type your full legal name below to sign this request.**
+
+[private]  

2024/11/2024-11-25-lenovo-2.md

@@ -0,0 +1,30 @@
+Dear Github DMCA team, 
+
+
+GroupSense and Lenovo have discovered a Github repository containing proprietary code which is being illegally distributed. 
+
+
+The repository is here - https://github.com/shywolf91/Lenovo-U1-Tool
+
+
+The infringer’s contact information and profile page is here - https://github.com/shywolf91. 
+
+
+The code contained in this repository is proprietary code owned by Lenovo (not to be made available for public consumption) and was leaked on GitHub. I hereby ask for the entire repository and all 6 associated forks to be removed from your site. 
+
+
+I have read and understand Github’s guidelines for making a DMCA Takedown request. I attest that I am making this request as an authorized agent of Lenovo, with their explicit permission, in response to their request. 
+
+
+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.
+
+
+
+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 will be happy to answer any further questions or concerns.
+
+[private]  
+GroupSense  
+[private]  
+[private]  

2024/11/2024-11-25-lenovo-3.md

@@ -0,0 +1,32 @@
+Dear Github DMCA team, 
+
+
+GroupSense and Lenovo have discovered a Github repository containing proprietary code which is being illegally distributed. 
+
+
+The repository is here - https://github.com/rm-evolveu/Lenovo-U1-Tool
+
+
+The infringer’s contact information and profile page is here - https://github.com/rm-evolveu. 
+
+
+The code contained in this repository is proprietary code owned by Lenovo (not to be made available for public consumption) and was leaked on GitHub. I hereby ask for the entire repository and all 6 associated forks to be removed from your site. 
+
+
+I have read and understand Github’s guidelines for making a DMCA Takedown request. I attest that I am making this request as an authorized agent of Lenovo, with their explicit permission, in response to their request. 
+
+
+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.
+
+
+
+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 will be happy to answer any further questions or concerns.
+
+
+
+[private]  
+GroupSense  
+[private]  
+[private]  

2024/11/2024-11-25-lenovo-4.md

@@ -0,0 +1,32 @@
+Dear Github DMCA team, 
+
+
+GroupSense and Lenovo have discovered a Github repository containing proprietary code which is being illegally distributed. 
+
+
+The repository is here - https://github.com/CHITTIMOTU/Lenovo-U1-Tool
+
+
+The infringer’s contact information and profile page is here - https://github.com/CHITTIMOTU. 
+
+
+The code contained in this repository is proprietary code owned by Lenovo (not to be made available for public consumption) and was leaked on GitHub. I hereby ask for the entire repository and all 6 associated forks to be removed from your site. 
+
+
+I have read and understand Github’s guidelines for making a DMCA Takedown request. I attest that I am making this request as an authorized agent of Lenovo, with their explicit permission, in response to their request. 
+
+
+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.
+
+
+
+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 will be happy to answer any further questions or concerns.
+
+
+
+[private]  
+GroupSense  
+[private]  
+[private]  

2024/11/2024-11-25-lenovo-5.md

@@ -0,0 +1,33 @@
+Dear Github DMCA team, 
+
+
+GroupSense and Lenovo have discovered a Github repository containing proprietary code which is being illegally distributed. 
+
+
+The repository is here - https://github.com/tannm102/Lenovo-U1-Tool
+
+
+The infringer’s contact information and profile page is here -https://github.com/tannm102. 
+
+
+
+The code contained in this repository is proprietary code owned by Lenovo (not to be made available for public consumption) and was leaked on GitHub. I hereby ask for the entire repository and all 6 associated forks to be removed from your site. 
+
+
+I have read and understand Github’s guidelines for making a DMCA Takedown request. I attest that I am making this request as an authorized agent of Lenovo, with their explicit permission, in response to their request. 
+
+
+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.
+
+
+
+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 will be happy to answer any further questions or concerns.
+
+
+
+[private]  
+GroupSense  
+[private]  
+[private]  

2024/11/2024-11-25-lenovo.md

@@ -0,0 +1,31 @@
+Dear Github DMCA team, 
+
+GroupSense and Lenovo have discovered a Github repository containing proprietary code which is being illegally distributed. 
+
+
+The repository is here - https://github.com/aybe/Lenovo-U1-Tool 
+
+
+The infringer’s contact information and profile page is here - https://github.com/aybe. 
+
+
+The code contained in this repository is proprietary code owned by Lenovo (not to be made available for public consumption) and was leaked on GitHub. I hereby ask for the entire repository and all 6 associated forks to be removed from your site. 
+
+
+I have read and understand Github’s guidelines for making a DMCA Takedown request. I attest that I am making this request as an authorized agent of Lenovo, with their explicit permission, in response to their request. 
+
+
+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.
+
+
+
+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 will be happy to answer any further questions or concerns.
+
+
+
+[private]  
+GroupSense  
+[private]  
+[private]

2024/11/2024-11-25-makerkit.md

@@ -0,0 +1,63 @@
+**Are you the copyright holder or authorized to act on the copyright owner's behalf?**
+
+Yes, I am the copyright holder.
+
+**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, [private], am the [private] and [private] of Makerkit, a commercial SaaS Starter Kit built with Next.js and Supabase. I have exclusive rights to reproduce, distribute, and sell Makerkit.
+
+GitHub users have published Makerkit's proprietary source code without authorization.
+
+These repositories contains Makerkit's copyrighted code. The entire contents of these repositories infringe on my exclusive rights as the copyright holder.
+
+**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.**
+
+The copyrighted work repository is the below:
+
+[private]
+
+**What files should be taken down? Please provide URLs for each file, or if the entire repository, the repository’s URL.**
+
+https://github.com/kodaneflash/next-supabase-saas-kit-turbo-MAKERKIT-STARTER-
+
+**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.**
+
+I have not found 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.**
+
+**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.**
+
+My phone number is [private]
+
+**Please type your full legal name below to sign this request.**
+
+[private]

2024/11/2024-11-25-pixelcraft.md

@@ -0,0 +1,75 @@
+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 the copyright holder.
+
+**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.**
+
+**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.**
+
+So I am a Unity Assets Store [private], I [private] and [private] tools on the store and other dev buy them, what I am reporting about is this tool:  
+https://assetstore.unity.com/packages/tools/integration/pixelcraft-dynamic-resolution-for-urp-270561  
+It is a performance optimization tool that tracks game's performance in the background and dynamically adjusts resolution to match performance target.
+
+And this is where it is posted on github:  
+https://github.com/devagame/URP-14-Extension/tree/main/Assets/Plugins/Smart%20Performance
+
+They are not allowed to publish the source code out in the open.
+
+**What files should be taken down? Please provide URLs for each file, or if the entire repository, the repository’s URL.**
+
+This folder named "Smart Performance" is the containing my tool:  
+https://github.com/devagame/URP-14-Extension/tree/main/Assets/Plugins/Smart%20Performance
+
+Ideally the entire repo should be removed as I have seen under the plugins folder where my tool resides a number of tools from other Unity Assets Store published in there as well.
+
+**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.**
+
+The seem to be a number of forks, only one of them seem public, and in that one I can't see my tool published there, tho other tools from other Unity Assets Store publishers are there so you might get DMCA complaints for those soon enough as I have notified some of those publishers about the existence of this repo.
+
+**Is the work licensed under an open source license?**
+
+No
+
+**What would be the best solution for the alleged infringement?**
+
+Repository can be made private
+
+**Do you have the alleged infringer’s contact information? If so, please provide it.**
+
+I don't
+
+**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]

2024/11/2024-11-25-realvirtual-io-2.md

@@ -0,0 +1,84 @@
+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).
+
+---
+
+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 the copyright holder.
+
+**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.**
+
+We are the owner of realvirtual.io (https://realvirtual.io) a software sold over the Unity Asset Store and under copyright, see here: https://assetstore.unity.com/packages/tools/integration/realvirtual-io-digital-twin-professional-6-301340 and here https://assetstore.unity.com/packages/tools/integration/realvirtual-io-digital-twin-starter-2022-225899. We have seen a github repository where our source code is posted including our copyright notice.
+
+**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.**
+
+Our protected software code is part of a Github Project. Everything here is under our copyright. In some scripts our copyright notice is still present.  
+https://github.com/isaddiq/CraneProjectUnity/tree/main/Assets/game4automation
+
+**What files should be taken down? Please provide URLs for each file, or if the entire repository, the repository’s URL.**
+
+https://github.com/isaddiq/CraneProjectUnity/tree/main/Assets/game4automation
+
+**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.**
+
+Yes
+
+**What technological measures do you have in place and how do they effectively control access to your copyrighted material?**
+
+We are selling over the Unity Asset Store and Users need to agree to the license conditions and that source code is not allowed to be shared.
+
+**How is the accused project designed to circumvent your technological protection measures?**
+
+It is publishing our protected source code.
+
+**<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.**
+
+We did not found any 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 we don't
+
+**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]  
+Phone: [private]  
+realvirtual [private]  
+[private]  
+[private]  
+
+**Please type your full legal name below to sign this request.**
+
+[private]  

2024/11/2024-11-25-realvirtual-io-3.md

@@ -0,0 +1,84 @@
+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).
+
+---
+
+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 the copyright holder.
+
+**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.**
+
+We are the owner of realvirtual.io (https://realvirtual.io) a software sold over the Unity Asset Store and under copyright, see here: https://assetstore.unity.com/packages/tools/integration/realvirtual-io-digital-twin-professional-6-301340 and here https://assetstore.unity.com/packages/tools/integration/realvirtual-io-digital-twin-starter-2022-225899. We have seen a github repository where our source code is posted including our copyright notice.
+
+**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.**
+
+Our protected software code is part of a Github Project. Everything here is under our copyright. In some scripts our copyright notice is still present.  
+https://github.com/Nabiliii/Unity_matster_thesis_crane/tree/main/Assets/game4automation
+
+**What files should be taken down? Please provide URLs for each file, or if the entire repository, the repository’s URL.**
+
+https://github.com/Nabiliii/Unity_matster_thesis_crane/tree/main/Assets/game4automation
+
+**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.**
+
+Yes
+
+**What technological measures do you have in place and how do they effectively control access to your copyrighted material?**
+
+We are selling over the Unity Asset Store and Users need to agree to the license conditions and that source code is not allowed to be shared.
+
+**How is the accused project designed to circumvent your technological protection measures?**
+
+It is publishing our protected source code.
+
+**<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.**
+
+We did not found any 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 we don't
+
+**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]  
+Phone: [private]  
+realvirtual [private]  
+[private]  
+[private]  
+
+**Please type your full legal name below to sign this request.**
+
+[private]  

2024/11/2024-11-25-realvirtual-io.md

@@ -0,0 +1,84 @@
+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).
+
+---
+
+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 the copyright holder.
+
+**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.**
+
+We are the owner of realvirtual.io (https://realvirtual.io) a software sold over the Unity Asset Store and under copyright, see here: https://assetstore.unity.com/packages/tools/integration/realvirtual-io-digital-twin-professional-6-301340 and here https://assetstore.unity.com/packages/tools/integration/realvirtual-io-digital-twin-starter-2022-225899. We have seen a github repository where our source code is posted including our copyright notice.
+
+**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.**
+
+Our protected software code is part of a Github Project. Everything here is under our copyright. In some scripts our copyright notice is still present.  
+https://github.com/witruuueyt/FestoAR/tree/master/Assets/game4automation
+
+**What files should be taken down? Please provide URLs for each file, or if the entire repository, the repository’s URL.**
+
+https://github.com/witruuueyt/FestoAR/tree/master/Assets/game4automation
+
+**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.**
+
+Yes
+
+**What technological measures do you have in place and how do they effectively control access to your copyrighted material?**
+
+We are selling over the Unity Asset Store and Users need to agree to the license conditions and that source code is not allowed to be shared.
+
+**How is the accused project designed to circumvent your technological protection measures?**
+
+It is publishing our protected source code.
+
+**<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.**
+
+We did not found any 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 we don't
+
+**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]  
+Phone: [private]  
+realvirtual [private]  
+[private]  
+[private]  
+
+**Please type your full legal name below to sign this request.**
+
+[private]  

2024/11/2024-11-25-sabel-systems.md

@@ -0,0 +1,69 @@
+**Are you the copyright holder or authorized to act on the copyright owner's behalf?**
+
+Yes, I am the copyright holder.
+
+**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 a representative of Luxemborug Privacy LLC, a subsidiary of Sabel Systems Technology Solutions, LLC in [private]  
+The code that was published was taken from our internal repository
+
+**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.**
+
+The code was a tool that was coded for the purpose of applying hard-disk encryption. It somehow made its way onto a forum online where it was then abused and published to github.
+
+**What files should be taken down? Please provide URLs for each file, or if the entire repository, the repository’s URL.**
+
+I have attached a URL for each file along with associated forks/repositories that I request to be removed  
+https://github.com/0x25bit/Khalsa-Crypt  
+https://github.com/CPT-Jack-A-Castle/Khalsa-Crypt  
+https://github.com/kkirta/Khalsa-Crypt  
+https://github.com/pitbullcan/Khalsa-Crypt  
+https://github.com/Yeah9782/Khalsa-Crypt  
+
+**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, as stated previously:  
+I have attached a URL for each file along with associated forks/repositories that I wish to be removed  
+https://github.com/0x25bit/Khalsa-Crypt  
+https://github.com/CPT-Jack-A-Castle/Khalsa-Crypt  
+https://github.com/kkirta/Khalsa-Crypt  
+https://github.com/pitbullcan/Khalsa-Crypt  
+https://github.com/Yeah9782/Khalsa-Crypt  
+
+**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.**
+
+**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]

2024/11/2024-11-25-software-code.md

@@ -0,0 +1,132 @@
+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).
+
+---
+
+**Are you the copyright holder or authorized to act on the copyright owner's behalf?**
+
+Yes, I am the copyright holder.
+
+**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] and [private] of the copyrighted material in question. As the [private], I hold exclusive rights to reproduce, distribute, and display this material, as granted under copyright law. This includes [specific type of work, e.g., software code, written documentation, images, designs, etc.], which was developed and published by me or under my direct supervision.
+
+**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.**
+
+Description of the Original Copyrighted Works  
+The copyrighted works in question consist of proprietary software code and associated materials, which were developed privately within protected repositories and are not intended for public distribution or unauthorized use. The works include:
+
+PLF Customer API  
+A proprietary API designed to manage customer-related functionalities and data within a secure environment. This work was developed and maintained under strict confidentiality and has never been released publicly.
+
+Infringing Repository URL: https://github.com/clising793/plf-customer-api  
+PLF Data API  
+A secure API responsible for handling data-related operations within the project. This codebase was privately stored and is part of a larger ecosystem of interdependent software solutions. Unauthorized access and publication of this repository directly infringe upon its copyright.
+
+Infringing Repository URL: https://github.com/clising793/plf-data-api  
+[private] Site (Next.js)  
+A proprietary Next.js web application developed for internal or client use under the brand "[private]." The application and its code were stored within [private] and contain intellectual property belonging exclusively to the copyright owner.
+
+Infringing Repository URL: https://github.com/clising793/marchcroft-site-nextjs  
+URL to the Original Copyrighted Works  
+These works were originally stored in private repositories that are not accessible to the public. The repositories were protected under access control measures to ensure confidentiality. Any public posting or distribution of these materials without explicit authorization is in violation of copyright law.
+
+**What files should be taken down? Please provide URLs for each file, or if the entire repository, the repository’s URL.**
+
+Infringing Repository URL: https://github.com/clising793/marchcroft-site-nextjs  
+Infringing Repository URL: https://github.com/clising793/plf-data-api  
+Infringing Repository URL: https://github.com/clising793/plf-customer-api
+
+**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.**
+
+Yes
+
+**What technological measures do you have in place and how do they effectively control access to your copyrighted material?**
+
+Technological Measures in Place  
+Private Repository Access Control:  
+The copyrighted works are stored in [private] on platforms such as [private]. These repositories are configured with access controls that only allow authorized users to view, modify, or clone the content. The following measures ensure effective control:
+
+User Authentication: Access is restricted to users authenticated via unique credentials (username and password) or SSH keys.  
+Two-Factor Authentication (2FA): Enforced 2FA adds an additional layer of security to ensure that only verified users can access the repositories.  
+Role-Based Permissions: Different levels of access (e.g., read-only, contributor, admin) are assigned based on roles, ensuring that users can only perform actions necessary for their responsibilities.  
+Access Logs and Monitoring:  
+Detailed logs track all activities within the repositories, including:
+
+User logins, file access, downloads, and modifications.  
+Repository cloning activities, which are closely monitored to detect any unauthorized actions.  
+Encryption:
+
+Data Transmission Encryption: All data is transmitted securely using SSL/TLS protocols to prevent interception during access.  
+At-Rest Encryption: Repository data is encrypted on the server to safeguard it against breaches.  
+IP Whitelisting (Optional):  
+For certain projects, access is restricted to specific IP addresses, ensuring that even valid credentials cannot be used outside designated locations or networks.
+
+Repository Access Policies:
+
+Access to repositories is reviewed regularly, and permissions are revoked when no longer required.  
+Sensitive projects are subject to stricter policies that limit collaboration to trusted contributors.
+
+**How is the accused project designed to circumvent your technological protection measures?**
+
+1. Unauthorized Access to [private]  
+The repositories where my copyrighted material was stored were private, with access strictly limited to authorized users via access control measures such as username/password combinations, SSH keys, and two-factor authentication (2FA). The accused project suggests that:
+
+Repository Cloning Without Authorization: The accused party gained access to [private] without my permission, potentially by using stolen or shared credentials, exploiting a security vulnerability, or bypassing authentication mechanisms.
+Circumvention of Access Logs: If access logs show no authorized activity matching the accused party, it indicates that they may have intentionally circumvented access logging mechanisms.  
+
+2. Bypassing Access Control Policies  
+The accused party bypassed access control policies by:
+
+Exploiting Authorized Access: It is possible that someone with authorized access violated the terms of use by sharing the content with the accused party. This constitutes a breach of confidentiality and circumvents the protections designed to restrict access to authorized users only.  
+Hacking or Cracking Access Controls: There may have been deliberate attempts to hack into the private repositories, such as brute-forcing passwords, exploiting API tokens, or bypassing SSH key requirements.  
+
+3. Unauthorized Distribution and Hosting  
+The accused project bypassed protections by:
+
+Illegally Obtaining and Replicating the Content: By acquiring and hosting my copyrighted material on a public repository, the accused party has effectively undermined the access restrictions that keep the content private.  
+Circumventing Attribution and Licensing: The accused project has redistributed the material without acknowledgment or adherence to the licensing terms of the copyrighted work.
+
+**<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.**
+
+N/A
+
+**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.**
+
+I have evidence of the person admitting the crime  
+[private]  
+
+Location: [private]  
+LinkedIn: [private]  
+Telegram: [private]  
+
+**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]

2024/11/2024-11-25-stimulsoft-2.md

@@ -0,0 +1,81 @@
+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).
+
+---
+
+One or more repositories in this DMCA takedown notice has been processed in accordance with GitHub's prohibition on sharing unauthorized product licensing keys, software for generating unauthorized product licensing keys, and/or software for bypassing checks for product licensing keys.
+
+You can learn more in [GitHub's Acceptable Use Policies](https://docs.github.com/en/github/site-policy/github-acceptable-use-policies).
+
+---
+
+**Are you the copyright holder or authorized to act on the copyright owner's behalf?**
+
+Yes, I am the copyright holder.
+
+**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.**
+
+Hello,
+
+I am a [private] of Stimulsoft Company. We have noted that there is an issue with the GitHub repository: https://github.com/behnamasaei/MokebManager/blob/b77e0b6e48d07f2aac38ae0988a7b394a504f98a/MokebManagerNg/aspnet-core/src/MokebManagerNg.HttpApi.Host/license.key#L1 Regrettably, it has come to our attention that the illegally generated license key codes have been uploaded and is publicly accessible within the project, alongside our product files and libraries. This situation is in direct violation of our Developer License Agreement (DLA) and is strictly prohibited.
+
+The license key is located by the next path MokebManager/MokebManagerNg/aspnet-core/src/MokebManagerNg.HttpApi.Host/license.key
+
+We request your immediate attention to rectify this matter.
+
+**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.**
+
+The license key file codes, located here MokebManager/MokebManagerNg/aspnet-core/src/MokebManagerNg.HttpApi.Host/license.key (license.key) were not generated by us but generated by someone. This is a cracked license key code.
+
+**What files should be taken down? Please provide URLs for each file, or if the entire repository, the repository’s URL.**
+
+The file license.key should be taken down
+
+The file is located by the following path MokebManager/MokebManagerNg/aspnet-core/src/MokebManagerNg.HttpApi.Host/license.key
+
+**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.**
+
+no forks found
+
+**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.**
+
+I do not have infringer’s contact information.
+
+**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]

2024/11/2024-11-25-stimulsoft-3.md

@@ -0,0 +1,81 @@
+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).
+
+---
+
+One or more repositories in this DMCA takedown notice has been processed in accordance with GitHub's prohibition on sharing unauthorized product licensing keys, software for generating unauthorized product licensing keys, and/or software for bypassing checks for product licensing keys.
+
+You can learn more in [GitHub's Acceptable Use Policies](https://docs.github.com/en/github/site-policy/github-acceptable-use-policies).
+
+---
+
+**Are you the copyright holder or authorized to act on the copyright owner's behalf?**
+
+Yes, I am the copyright holder.
+
+**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.**
+
+Hello,
+
+I am a [private] of Stimulsoft Company. We have noted that there is an issue with the GitHub repository: https://github.com/iqbalrafli13/larvelJqgrid/blob/d0ca49b77c1a149764cd4108bcc9eed482fedbde/public/plugin/stimulsoft-report/2021.2.2/stimulsoft/license.key#L1 Regrettably, it has come to our attention that the illegally generated license key codes have been uploaded and is publicly accessible within the project, alongside our product files and libraries. This situation is in direct violation of our Developer License Agreement (DLA) and is strictly prohibited.
+
+The license key is located by the next path larvelJqgrid/public/plugin/stimulsoft-report/2021.2.2/stimulsoft/license.key
+
+We request your immediate attention to rectify this matter.
+
+**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.**
+
+The license key file codes, located here larvelJqgrid/public/plugin/stimulsoft-report/2021.2.2/stimulsoft/license.key (license.key) were not generated by us but generated by someone. This is a cracked license key code.
+
+**What files should be taken down? Please provide URLs for each file, or if the entire repository, the repository’s URL.**
+
+The file license.key should be taken down
+
+The file is located by the following path larvelJqgrid/public/plugin/stimulsoft-report/2021.2.2/stimulsoft/license.key
+
+**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.**
+
+no forks found.
+
+**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.**
+
+I have no infringer’s contact information.
+
+**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]

2024/11/2024-11-25-stimulsoft-4.md

@@ -0,0 +1,81 @@
+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).
+
+---
+
+One or more repositories in this DMCA takedown notice has been processed in accordance with GitHub's prohibition on sharing unauthorized product licensing keys, software for generating unauthorized product licensing keys, and/or software for bypassing checks for product licensing keys.
+
+You can learn more in [GitHub's Acceptable Use Policies](https://docs.github.com/en/github/site-policy/github-acceptable-use-policies).
+
+---
+
+**Are you the copyright holder or authorized to act on the copyright owner's behalf?**
+
+Yes, I am the copyright holder.
+
+**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.**
+
+Hello,
+
+I am a [private] of Stimulsoft Company. We have noted that there is an issue with the GitHub repository: https://github.com/EliasMerati/MyEMShop/blob/db6b9277b61c4f8e5395e697b8cae45ca384ff17/MyEMShop.EndPoint/wwwroot/Reports/license.key#L1 Regrettably, it has come to our attention that the illegally generated license key codes have been uploaded and is publicly accessible within the project, alongside our product files and libraries. This situation is in direct violation of our Developer License Agreement (DLA) and is strictly prohibited.
+
+The license key is located by the next path MyEMShop/MyEMShop.EndPoint/wwwroot/Reports/license.key
+
+We request your immediate attention to rectify this matter.
+
+**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.**
+
+The license key file codes, located here MyEMShop/MyEMShop.EndPoint/wwwroot/Reports/license.key (license.key) were not generated by us but generated by someone. This is a cracked license key code.
+
+**What files should be taken down? Please provide URLs for each file, or if the entire repository, the repository’s URL.**
+
+The file license.key should be taken down
+
+The file is located by the following path MyEMShop/MyEMShop.EndPoint/wwwroot/Reports/license.key
+
+**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.**
+
+I found no 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.**
+
+I have no infringer’s contact information.
+
+**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]

2024/11/2024-11-25-stimulsoft-5.md

@@ -0,0 +1,81 @@
+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).
+
+---
+
+One or more repositories in this DMCA takedown notice has been processed in accordance with GitHub's prohibition on sharing unauthorized product licensing keys, software for generating unauthorized product licensing keys, and/or software for bypassing checks for product licensing keys.
+
+You can learn more in [GitHub's Acceptable Use Policies](https://docs.github.com/en/github/site-policy/github-acceptable-use-policies).
+
+---
+
+**Are you the copyright holder or authorized to act on the copyright owner's behalf?**
+
+Yes, I am the copyright holder.
+
+**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.**
+
+Hello,
+
+I am a [private] of Stimulsoft Company. We have noted that there is an issue with the GitHub repository: https://github.com/iqbalrafli13/training/blob/625035e39a9105b5672f354db4bd25480c875356/view/lib/stimulsoft-report/2021.3.6/stimulsoft/license.key#L1 Regrettably, it has come to our attention that the illegally generated license key codes have been uploaded and is publicly accessible within the project, alongside our product files and libraries. This situation is in direct violation of our Developer License Agreement (DLA) and is strictly prohibited.
+
+The license key is located by the next path training/view/lib/stimulsoft-report/2021.3.6/stimulsoft/license.key
+
+We request your immediate attention to rectify this matter.
+
+**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.**
+
+The license key file codes, located here training/view/lib/stimulsoft-report/2021.3.6/stimulsoft/license.key (license.key) were not generated by us but generated by someone. This is a cracked license key code.
+
+**What files should be taken down? Please provide URLs for each file, or if the entire repository, the repository’s URL.**
+
+The file license.key should be taken down
+
+The file is located by the following path training/view/lib/stimulsoft-report/2021.3.6/stimulsoft/license.key
+
+**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.**
+
+no forks found.
+
+**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.**
+
+I have no infringer’s contact information.
+
+**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]

2024/11/2024-11-25-stimulsoft.md

@@ -0,0 +1,83 @@
+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).
+
+---
+
+One or more repositories in this DMCA takedown notice has been processed in accordance with GitHub's prohibition on sharing unauthorized product licensing keys, software for generating unauthorized product licensing keys, and/or software for bypassing checks for product licensing keys.
+
+You can learn more in [GitHub's Acceptable Use Policies](https://docs.github.com/en/github/site-policy/github-acceptable-use-policies).
+
+---
+
+
+
+**Are you the copyright holder or authorized to act on the copyright owner's behalf?**
+
+Yes, I am the copyright holder.
+
+**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.**
+
+Hello,
+
+I am a [private] of Stimulsoft Company. We have noted that there is an issue with the GitHub repository: https://github.com/SinaJangjoo/Azmoon/blob/740517504bf669bc9d2f57e8db909edd5c3f5489/Azmoon/wwwroot/stimulsoft/license.key#L1 Regrettably, it has come to our attention that the illegally generated license key codes have been uploaded and is publicly accessible within the project, alongside our product files and libraries. This situation is in direct violation of our Developer License Agreement (DLA) and is strictly prohibited.
+
+The license key is located by the next path Azmoon/Azmoon/wwwroot/stimulsoft/license.key
+
+We request your immediate attention to rectify this matter.
+
+**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.**
+
+The license key file codes, located here Azmoon/Azmoon/wwwroot/stimulsoft/license.key (license.key) were not generated by us but generated by someone. This is a cracked license key code.
+
+**What files should be taken down? Please provide URLs for each file, or if the entire repository, the repository’s URL.**
+
+The file license.key should be taken down
+
+The file is located by the following path Azmoon/Azmoon/wwwroot/stimulsoft/license.key
+
+**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.**
+
+no forks found
+
+**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.**
+
+I do not have infringer’s contact information.
+
+**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]

2024/11/2024-11-25-the-game-hacking-bible.md

@@ -0,0 +1,152 @@
+**Are you the copyright holder or authorized to act on the copyright owner's behalf?**
+
+Yes, I am the copyright holder.
+
+**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, [private], am the copyright holder of “The Game Hacking Bible” in addition to all the content published on our website GuidedHacking.com
+
+The files hosted on your website violate our copyright, all these URLS must be deleted because they contain our copyrighted content:  
+https://github.com/FixInc/assault-cube-trainer  
+https://github.com/OpenMoblle/AssaultCube-Trainer-1  
+https://github.com/beerandgin/edit-memory  
+https://github.com/pMatoso/edit-memory  
+https://github.com/rayeur/edit-memory  
+https://github.com/speeri2018/edit-memory  
+https://github.com/XeCrash/edit-memory-c-  
+https://github.com/Z3USI0TA/edit-memory  
+https://github.com/METAMONDESU/External-Assault-Cube-Trainer  
+
+All the content on our website is exported to a PDF and copyrighted with the title "The Game Hacking Bible", represented by the copyright certificate listed below.
+
+Originally Published at this URL:  
+https://guidedhacking.com
+
+Our Copyright Certificate is attached, you can verify it here:  
+https://www.ic.gc.ca/app/opic-cipo/cpyrghts/dtls.do?fileNum=1210282&type=1&lang=eng
+
+Copyrighted Work Name: The Game Hacking Bible  
+Copyrighted Work Type: Digital Course (text and videos) teaching game hacking.
+
+Originally Published at this URL:  
+https://guidedhacking.com/
+
+Copyright Holder: [private]  
+Copyright Holder Email: [private]  
+Copyright Holder Phone Number: [private]  
+
+Copyright Holder Address:  
+Guided Hacking LLC  
+[private]  
+[private]  
+[private]  
+
+Our Copyright Certificate is attached, you can verify it here:  
+https://www.ic.gc.ca/app/opic-cipo/cpyrghts/dtls.do?fileNum=1210282&type=1&lang=eng
+
+Our Registered Trademarks:  
+http://tsdr.uspto.gov/#caseNumber=98598107&caseType=SERIAL_NO&searchType=statusSearch  
+http://tsdr.uspto.gov/#caseNumber=98598145&caseType=SERIAL_NO&searchType=statusSearch
+
+I am the site owner and sole copyright holder for each of the domains cited above. This letter is official notification under Section 512(c) of the Digital Millennium Copyright Act (”DMCA”), and I seek the removal of the aforementioned infringing material from your servers.
+
+Your site does not have any right or permission to reproduce, sell or display my websites in any way, shape or form. I am providing this notice in good faith and with the reasonable belief that rights I own are being infringed.
+
+Under penalty of perjury I certify that the information contained in the notification is both true and accurate, and I am the copyright owner and therefore have the authority to act on behalf of the owner of the copyright(s) involved.
+
+Please take these down in accordance with your DMCA policy as soon as possible.
+
+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 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 taken fair use into consideration.
+
+I have read and understand GitHub's Guide to Submitting a DMCA Takedown Notice.
+
+Please reply to this email if you need any additional information.
+
+Thank you.
+
+**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.**
+
+Copyrighted Work Name: The Game Hacking Bible  
+Copyrighted Work Type: Digital Course  
+Copyrighted Work Description: Digital course containing text, source code, images & videos, teaching game hacking, reverse engineering & cybersecurity.
+
+All the content on our website is exported to a PDF and copyrighted with the title "The Game Hacking Bible", represented by the copyright certificate listed below.
+
+Originally Published at this URL:  
+https://guidedhacking.com
+
+Our Copyright Certificate is attached, you can verify it here:  
+https://www.ic.gc.ca/app/opic-cipo/cpyrghts/dtls.do?fileNum=1210282&type=1&lang=eng
+
+**What files should be taken down? Please provide URLs for each file, or if the entire repository, the repository’s URL.**
+
+https://github.com/FixInc/assault-cube-trainer  
+https://github.com/OpenMoblle/AssaultCube-Trainer-1  
+https://github.com/beerandgin/edit-memory  
+https://github.com/pMatoso/edit-memory  
+https://github.com/rayeur/edit-memory  
+https://github.com/speeri2018/edit-memory  
+https://github.com/XeCrash/edit-memory-c-  
+https://github.com/Z3USI0TA/edit-memory  
+https://github.com/METAMONDESU/External-Assault-Cube-Trainer  
+
+**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. These are all forks from the last DMCA takedown I sent to Github.
+
+**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.**
+
+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 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 taken fair use into consideration.  
+I have read and understand GitHub's Guide to Submitting a DMCA Takedown Notice.
+
+**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]  
+
+Guided Hacking LLC  
+[private]  
+[private]  
+[private]  
+
+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 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 taken fair use into consideration.  
+I have read and understand GitHub's Guide to Submitting a DMCA Takedown Notice.  
+
+**Please type your full legal name below to sign this request.**
+
+[private]  

2024/11/2024-11-26-boss-menu.md

@@ -0,0 +1,66 @@
+**Are you the copyright holder or authorized to act on the copyright owner's behalf?**
+
+Yes, I am the copyright holder.
+
+**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 the code as [private] acquired all intellectual property rights through a service contract on [private]. The developer explicitly and fully transferred all rights to the code to [private], as evidenced by our contractual agreement and [private]'s terms of service.
+
+I can provide the contract/messages confirming this rights transfer.
+
+**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.**
+
+The code in question is a Boss Menu management system that [private] commissioned and own the full rights to through [private]. The code is currently hosted without authorization at: https://github.com/YehonataNNDev/YN-BossMenu  
+As the [private] of this code through a completed [private] contract, [private] did not authorize its public posting or distribution. The entire repository contains [private] proprietary code.
+
+**What files should be taken down? Please provide URLs for each file, or if the entire repository, the repository’s URL.**
+
+https://github.com/YehonataNNDev/YN-BossMenu
+
+**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.**
+
+Forks:  
+https://github.com/iSentrie/esx_bossmenu  
+https://github.com/darkosiel/esx_bossmenu  
+https://github.com/densuz/YN-BossMenu  
+https://github.com/hasidu/YN-BossMenu  
+https://github.com/MINHLD92/YN-BossMenu  
+https://github.com/SuperCocoPower/YN-BossMenu  
+
+**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.**
+
+**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]

2024/11/2024-11-26-vocaloid.md

@@ -0,0 +1,71 @@
+One or more repositories in this DMCA takedown notice has been processed in accordance with GitHub's prohibition on sharing unauthorized product licensing keys, software for generating unauthorized product licensing keys, and/or software for bypassing checks for product licensing keys.
+
+You can learn more in [GitHub's Acceptable Use Policies](https://docs.github.com/en/github/site-policy/github-acceptable-use-policies).
+
+---
+
+**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.**
+
+We have been commissioned by YAMAHA CORPORATION to file a deletion complaint.  
+And YAMAHA CORPORATION has registered “VOCALOID” related marks throughout the world.  
+United States: No.3107203; Japan: No.4722616  
+VOCALOID is a voice synthesis technology developed by Yamaha, as well as the collective name for its related products. To use this product, it is necessary to purchase an official version and its corresponding serial number.
+
+**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.**
+
+The reported link below offer for download illegally distributed VOCALOID voice components:  
+a. https://github.com/RigoLigoRLC/Vocaloid_Retial  
+Mocaloid is an experimental synthesis engine that replaces the traditional VOCALOID engine with the Moresample synthesis engine. This engine unlawfully integrates and extracts essential samples and tagging information from the copyrighted Vocaloid Daisy VoiceBank, delivering this data to Moresample for synthesis. Such unauthorized use of the Daisy VoiceBank infringes on my copyright by repurposing protected data and technology without consent.
+
+**What files should be taken down? Please provide URLs for each file, or if the entire repository, the repository’s URL.**
+
+n/a
+
+**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.**
+
+a. https://github.com/harrett/Vocaloid_Retial  
+b. https://github.com/ibretiv/Vocaloid_Retial  
+c. https://github.com/uselessbug/Vocaloid_Retrial  
+
+**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.**
+
+**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]  
+[private]  
+
+**Please type your full legal name below to sign this request.**
+
+[private]