Google removed attribution to open-source developers from its Artemis project after copying their code without credit

How Google Erased the Original Authors

The company's AI division incorporated code from Minitap's mobile-use library into its Artemis repository, then stripped away the original authors' names in a subsequent commit. Minitap co-founder Nicolas Dehandschoewercker discovered the plagiarism when reviewing Google's public repository earlier this month.

Dehandschoewercker found his team's code in Artemis and confirmed their names appeared in the repository's git history before being deliberately removed. The change eliminated proper attribution that open-source licenses typically require. This pattern suggests Google intentionally copied the work while attempting to obscure its origins.

The mobile-use library was developed by Minitap for mobile device automation tasks. Google's version replicated core functionality without acknowledging the original creators. Open-source communities rely heavily on proper credit systems to maintain trust and encourage collaboration. When major corporations remove attributions, it undermines these foundational principles.

Open-source licenses vary in their requirements, but most mandate attribution preservation. The GNU General Public License and similar frameworks explicitly prohibit removing copyright notices. However, enforcement often depends on the original authors pursuing legal action.

What Legal Recourse Exists for Stolen Code?

Smaller companies like Minitap face significant challenges when confronting tech giants like Google. Legal costs can quickly exceed potential damages, especially when the infringing party has deep pockets. Many developers simply lack resources to fight prolonged battles against corporate behemoths.

The incident raises questions about how large technology companies treat open-source contributions. While these organizations benefit enormously from community-developed software, they sometimes fail to reciprocate with proper recognition. This double standard creates friction between corporate interests and grassroots development efforts.

Google's actions demonstrate a troubling pattern of leveraging community work while minimizing obligations. The company has faced similar controversies involving TensorFlow and other projects where attribution issues arose. These incidents collectively suggest systemic problems rather than isolated mistakes.

Moving forward, open-source advocates may push for stricter enforcement mechanisms. Some propose requiring corporate contributors to sign agreements guaranteeing attribution compliance. Others advocate for technical solutions that make removing credits more difficult.

Frequently Asked Questions

The broader implications extend beyond individual cases. When influential companies disregard attribution norms, it discourages innovation across the entire ecosystem. Developers invest time and effort expecting recognition, not exploitation.

Can open-source code legally be used without attribution? Most open-source licenses require attribution preservation. Removing credits violates these terms and may constitute copyright infringement, though enforcement varies.

What options do developers have against large corporations? Legal action remains possible but expensive. Community pressure and public exposure often prove more effective for smaller organizations facing resource disadvantages.

How can attribution theft be prevented? Stronger license enforcement, automated detection tools, and corporate accountability measures could reduce incidents while protecting contributor rights.