Minitap Says Google Shipped Its Open Source Code Without Credit

Minitap, the company behind the open source Artemis project, has accused Google of shipping code derived from Artemis without carrying forward the required attribution. The claim appeared in a Minitap blog post titled "I Expected Better From Google," and Google has not responded publicly. The dispute turns on a narrow but consequential point: whether the license notice and author credit survived the trip from Minitap's repository into a Google release.

The mechanics of the complaint matter more than the accusation itself. Permissive licenses such as Apache 2.0 and MIT do not forbid commercial reuse, but they do require redistributors to preserve copyright notices and, under some terms, flag modifications. If Minitap's comparison of its repository against the shipped product holds, the failure is procedural rather than a case of outright code theft. That line separates routine reuse, which open source is designed to permit, from a compliance problem that carries legal weight even when the code is free to use.

The evidence so far rests on Minitap's own file comparison. No independent audit has been published, and Google has neither confirmed nor denied the overlap. The technical community has not yet had time to diff the relevant files line by line, which means the allegation remains specific but unverified. Until that audit arrives or Google issues a statement, the case sits in the familiar gap between a credible claim and a proven one.

Attribution fights have become a recurring feature of the AI and software industry, where code moves quickly between research repositories, internal forks, and shipped products. Large vendors maintain review processes meant to catch license obligations before release, but those processes depend on engineers correctly tracing the provenance of every dependency and copied snippet. When a small team spots its work inside a big vendor's output, the resolution is usually quiet: a credit line or a license file added after the fact, with no public argument.

The practical stakes for Minitap are reputational and potentially legal, since license terms are enforceable regardless of whether the underlying code is freely available. For Google, the cost is the appearance of taking from a smaller project without acknowledgment, a charge that carries particular weight in a community that treats attribution as a baseline norm. The company's next move, whether a correction or continued silence, will shape how the episode is remembered.

What to watch next is concrete: whether Google confirms the code overlap, whether it adds the missing credit, and whether Minitap files a formal license complaint. The broader question is how many similar cases never surface, because most small projects lack the resources to monitor what large vendors ship. Until an audit or an official statement lands, the claim stays contested but specific.