Photopea Copyright Dispute: GitHub DMCA Challenges and the Impact of AI-Driven Cloning

GitHub Refuses Takedown of Modified Photopea Repositories

IvanK_net, the developer of the web-based photo editor Photopea, has reported that GitHub refused to honor a DMCA takedown notice regarding dozens of repositories containing "cracked" versions of his software. These repositories reportedly use AI models to scrape the JavaScript code from Photopea.com, remove advertisements, and republish the code as new products.

According to the developer, GitHub's response stated they were "unable to confirm a violation of 17 U.S. Code § 1201." This specific section of the law pertains to the circumvention of technological measures that control access to copyrighted works, rather than the act of copyright infringement itself.

Legal Nuances of the DMCA Takedown

Technical and legal observers suggest that the failure of the takedown request may stem from the specific legal code cited in the report.

Section 1201 vs. Section 512

Industry analysts note that 17 U.S. Code § 1201 is often a high bar because it requires proof that a "technological measure" (like encryption or a digital lock) was bypassed. Since Photopea's source code is delivered as JavaScript to the browser, it may not qualify as a protected technological measure under this specific statute.

Experts suggest that a standard copyright infringement notice under 17 U.S. Code § 512(c) would be more appropriate, as it focuses on the unauthorized reproduction of the work rather than the method used to access it.

The Role of Legal Representation

There is a strong consensus among the community that professional legal counsel is necessary to compel GitHub to act.

"That is the one guaranteed route to get GitHub to sit up and take the action they should already have taken on your behalf."

Legal practitioners emphasize that while the developer may have a clear case of copyright infringement, the administrative process at large platforms like GitHub often relies on automated or low-level reviews that may miss the nuance of a self-filed report.

The Threat of AI-Driven Software Reproduction

This incident highlights a broader shift in software intellectual property (IP) protection caused by Large Language Models (LLMs).

From "Cracking" to "Clean-Room" Reproduction

While the current repositories may be direct copies of the code, commenters warn of a transition toward "clean-room" reproduction. In this scenario, an AI is used to generate a rigorous test suite based on the original software's behavior, and a separate AI then writes entirely new code to pass those tests. This process could potentially create a feature-perfect clone that does not violate traditional copyright law because the literal source code was not copied.

The Erosion of Client-Side Moats

The case underscores the vulnerability of proprietary software delivered via client-side JavaScript. Because the code must be sent to the user's browser to execute, it is inherently accessible. Suggestions for mitigating this risk include:

• WebAssembly (Wasm): Moving critical logic from JavaScript to compiled Wasm binaries to make reverse engineering more difficult.
• Server-Side Processing: Shifting "magic sauce" algorithms to the server, where the code is never exposed to the client.
• Trademark Protection: Relying on trademarks and brand identity rather than just code copyright, as trademarks protect the name and logo regardless of how the software is implemented.

Community Perspectives on Monetization and Ethics

The dispute has sparked a debate regarding the ethics of "cloning" and the impact of aggressive monetization.

Some users argue that the incentive for these clones is the intrusive nature of the ads on the original site, suggesting that a more user-friendly monetization model would reduce the demand for cracked versions. Others point out the irony of a tool that clones Photoshop's UI and functionality now complaining about being cloned itself, though others counter that the complexity of Photopea's hundreds of thousands of lines of code constitutes a significant original work that deserves protection regardless of its inspiration.