Google stole open source code without crediting the authors (Artemis/Minitap)

Google's Artemis project incorporated open-source code from Minitap without attribution.

Minitap, a company specializing in autonomous QA agents, has accused Google of using its open-source code in Google's Artemis project without proper attribution. Minitap identified specific code segments and even identical instructions within the Artemis repository that matched their own open-source mobile-use project. They discovered that their names, originally present in an older version's author history, were removed in a subsequent force push by an unknown author before Minitap investigated. Minitap claims this violates the Apache 2.0 license under which mobile-use was distributed, requiring copyright and attribution notices to be preserved. The company has contacted Google and opened a public issue requesting acknowledgment and proper crediting of their contribution to the Artemis project. Minitap's CEO expressed disappointment, citing Google's history of supporting open source and the importance of attribution for the open-source community.

This incident highlights a growing tension in the AI development space where rapid innovation often outpaces established norms for open-source attribution and licensing. For companies like Google, the pressure to release new products quickly can lead to oversights in crediting external contributions, potentially alienating smaller developers and the broader open-source community. Conversely, for projects like Minitap, ensuring their contributions are recognized is crucial for building reputation and fostering further collaboration, making such perceived transgressions a significant concern.

The implications extend to the sustainability of open-source development itself. If developers feel their work is being appropriated without credit, it could disincentivize future contributions, impacting the very ecosystem that fuels much of technological advancement. The resolution of this dispute, whether through Google's acknowledgment and correction or a continued impasse, will likely influence how similar projects approach code sharing and attribution in the future, setting precedents for developer-company interactions in this rapidly evolving field.