From 041ce26d9fd1b0f107c478aaa1b11d3b95ca1aa7 Mon Sep 17 00:00:00 2001 From: dmca-sync-bot Date: Fri, 4 Sep 2026 14:38:11 +0000 Subject: [PATCH] Process DMCA request --- 2026/09/2026-09-03-sakuraa-development.md | 107 ++++++++++++++++++++++ 1 file changed, 107 insertions(+) create mode 100644 2026/09/2026-09-03-sakuraa-development.md diff --git a/2026/09/2026-09-03-sakuraa-development.md b/2026/09/2026-09-03-sakuraa-development.md new file mode 100644 index 0000000000..dbaf338381 --- /dev/null +++ b/2026/09/2026-09-03-sakuraa-development.md @@ -0,0 +1,107 @@ +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). + +--- + +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? If you are submitting this notice on behalf of a company, please be sure to use an email address on the company's domain. If you use a personal email address for a notice submitted on behalf of a company, we may not be able to process it.** + +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 an authorized representative of Sakuraa Development LLC, a [private] limited liability company, acting as its designated agent for [private] [private]. Sakuraa Development LLC is the author and owner of all copyright and distribution rights in the work described below. Written authorization is on file and available on request. + +**Please provide a detailed description of the original copyrighted work that has allegedly been infringed.** + +"Sakuraa Camera Mod" is a proprietary commercial software modification for the video game Gorilla Tag, authored and owned by Sakuraa Development LLC, first published in its commercial form on June 1, 2024. + +The software is not distributed as a standalone assembly. It is delivered through an injector, and the underlying .NET assembly is never provided to end users in a directly accessible form. Licensed users receive functionality; they do not receive the assembly. Obtaining it requires defeating the delivery mechanism through reverse engineering. + +The work has never been published in source form, released under any open-source license, or otherwise made available for redistribution or derivative use. + +**If the original work referenced above is available online, please provide a URL.** + +https://gtagcamera.com + +**We ask that a DMCA takedown notice list every specific file in the repository that is infringing, unless the entire contents of the repository are infringing on your copyright. Please clearly state that the entire repository is infringing, OR provide the specific files within the repository you would like removed.** + +**Based on the above, I confirm that:** + +Specific files within the repository are infringing + +**Identify only the specific file URLs within the repository that is infringing:** + +https://github.com/devcurly/SakuraaSource/tree/main/SakMerge/SakMerge +https://github.com/devcurly/SakuraaSource/tree/main/SakuraaCastingMod/SakuraaCastingMod +https://github.com/devcurly/SakuraaSource/tree/main/GorillaRigUtil/GorillaRigUtil + +These paths contain decompiled output of our proprietary assembly. Given the file count, infringing content is identified at the directory level; a representative sample of files within each path has been reviewed. Every file within these three paths is infringing. + +We do not claim the rest of the repository. Third-party libraries ([private], [private], [private]), [private] framework artifacts produced by decompilation, and tooling authored by the account holder are excluded. + +**Do you claim to have any technological measures in place to control access to your copyrighted content? Please see our Complaints about Anti-Circumvention Technology if you are unsure.** + +Yes + +**What technological measures do you have in place and how do they effectively control access to your copyrighted material?** + +Access to the copyrighted assembly is controlled by multiple layers of digital rights management and anti-reverse-engineering protection. We do not enumerate them here, as this notice is published publicly and disclosure would undermine their effectiveness. + +In general terms: the software is not distributed as a standalone assembly — it is delivered through an injector, and the assembly is never provided to end users in a directly accessible form. The assembly is further protected by transformations that render its code unreadable and not reconstructible by ordinary means, and by licensing controls that restrict operation to holders of a valid license issued by Sakuraa Development LLC. + +The effect of these measures is that no user, licensed or otherwise, obtains readable access to the copyrighted code through any authorized channel. + +**How is the accused project designed to circumvent your technological protection measures?** + +The reported material is readable source code reconstructed from a protected assembly, which could only have been produced by defeating the measures described above. + +The effect is visible in the reported files themselves: the code throughout bears the signature of control flow flattening, a protection transformation applied to our assembly. Its presence in the published output confirms both that our protections were applied to the binary and that they were defeated in order to produce this repository. Publishing the result makes the protected code openly available and defeats the purpose of those measures. + +The repository additionally contains tooling authored by the account holder that supports circumvention, at [private] and [private]. We do not claim copyright in that tooling and have excluded it from our infringement claim, but identify it here as relevant to this question. + +**If you are reporting an allegedly infringing fork, please note that each fork is a distinct repository and must be identified separately. Please read more about forks. As forks may often contain different material than in the parent repository, if you believe any of the repositories or files in the forks are infringing, please list each fork URL below:** + +**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.** + +We do not have contact information for the account holder. The individuals involved in distributing this material operate under alternate accounts and appear to conceal their identities deliberately. + +The identifiers known to us are the GitHub username "[private]" and the commit author identity "[private]," which appears throughout the repository's commit history and differs from the account name. + +**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 have read and understand GitHub's Guide to Submitting a DMCA Takedown Notice.** + +**So that we can get back to you, please provide either your telephone number or physical address.** + +[private] + +**Please type your full name for your signature.** + +[private]