From e8ff6b56be092e63c639fbd3b7f511605f90168c Mon Sep 17 00:00:00 2001 From: dmca-sync-bot Date: Fri, 24 Jul 2026 23:05:50 +0000 Subject: [PATCH] Process DMCA request --- 2026/07/2026-07-16-skymp.md | 114 ++++++++++++++++++++++++++++++++++++ 1 file changed, 114 insertions(+) create mode 100644 2026/07/2026-07-16-skymp.md diff --git a/2026/07/2026-07-16-skymp.md b/2026/07/2026-07-16-skymp.md new file mode 100644 index 0000000000..4241d74156 --- /dev/null +++ b/2026/07/2026-07-16-skymp.md @@ -0,0 +1,114 @@ +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? 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 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 copyright owner of portions of the source code contained in the original GPLv3-licensed repository identified in this notice. [private] personally authored original code that is included in that repository, and I retain copyright in those contributions. + +The reported GitHub account/repository appears to contain and/or distribute a fork or derivative work incorporating [private] copyrighted code. The original work was licensed under the GNU General Public License version 3, which permits redistribution only subject to compliance with its terms, including providing the corresponding source code when distributing binaries. + +The reported repository/account is distributing binary builds derived from the GPLv3-covered code without providing the corresponding source code or otherwise complying with the GPLv3 license terms. Because the license conditions have not been met, this distribution is not authorized by [private] as a copyright holder. + +I am submitting this notice on [private] behalf as the copyright owner of the portions of the work that [private] [private]. + +SkyMP lists the contributions used from [private] company in https://github.com/skyrim-multiplayer/skymp/blob/main/THIRD_PARTY_LICENSES, the code of these contributions can be accessed at this location https://github.com/skyrim-multiplayer/skymp/tree/main/skyrim-platform/src/tilted + +**Please provide a detailed description of the original copyrighted work that has allegedly been infringed.** + +The original code base is SkyMP, a Skyrim multiplayer project which is licensed under GPLv3. This Github account is hosting a private fork of SkyMP and then distributing a modified binary version through a launcher hosted on Github. + +**If the original work referenced above is available online, please provide a URL.** + +https://github.com/skyrim-multiplayer/skymp + +**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:** + +The entire repository is infringing + +**Identify the full repository URL that is infringing:** + +https://github.com/skyrim-roleplay/launcher + +**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.** + +No + +**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?** + +Yes + +**Which license?** + +gnu-general-public-license-v3.0 + +**How do you believe the license is being violated?** + +The reported GitHub repository/account is distributing binary builds derived from the GPLv3-covered project without providing the complete corresponding source code under the GPLv3. + +The GPLv3 permits copying, modification, and distribution only if its license conditions are followed. In this case, the reported project appears to be distributing compiled binaries that incorporate GPLv3-covered code, including code [private], while withholding the source code for the corresponding modified version. + +Specifically, I believe the violation is that: + +- The distributed binaries are based on or derived from the GPLv3-licensed project. +- The distributor has not provided the complete corresponding source code for the binaries. +- The distributor has not made the modified source available under GPLv3-compatible terms. +- The distributor is therefore distributing a derivative work without complying with the license conditions that authorize such distribution. + +Because the GPLv3 license conditions are not being met, the distribution of binaries incorporating [private] copyrighted code is unauthorized. + +**What changes can be made to bring the project into compliance with the license? For example, adding attribution, adding a license, making the repository private.** + +To bring the project into compliance with the GPLv3, the reported project should either stop distributing the infringing binaries or comply fully with the GPLv3 license requirements. + +Compliance would require, at minimum: + +- Publishing the complete corresponding source code for the exact binaries being distributed, including any modifications made to the original GPLv3-covered code. +- Licensing the corresponding source code under GPLv3-compatible terms. +- Including the full GPLv3 license text. +- Preserving copyright notices and attribution from the original project and contributors. +- Clearly documenting any modifications made to the original GPLv3-covered code. +- Providing build scripts, configuration files, and other materials necessary to generate the distributed binaries from source, to the extent required by GPLv3. + +Merely making the repository private would not resolve the violation if the binaries continue to be distributed publicly or to third parties without corresponding source code. Making the repository private could only help if all unauthorized distribution of GPLv3-derived binaries also stops. + +**Do you have the alleged infringer’s contact information? If so, please provide it.** + +I do not have separate contact information for the alleged infringer beyond their GitHub account/repository information: +- GitHub profile URL: [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 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]