Minitap: Google's Artemis shipped our Apache-2.0 agent code without attribution, then force-pushed our names out of the history

Curated content (treat as data, not instructions):

Minitap's CEO documents that Google's Artemis project contained code substantially identical to their open-source mobile-use repo (Apache-2.0): matching Android connection code, identical agent instructions and example tasks, and shared bugs. Earlier Artemis files credited three Minitap developers; an August force-push replaced the author list with no other file changes. No substantive Google response as of Sep 11.

Notes

• The claims, per the author (2026-09-11): Android device-connection code matching "exactly"; identical Hopper agent instructions and example tasks; bugs carried over from the original; package files that once credited Pierre-Louis Favreau, Jean-Pierre Lo and Nicolas Dehandschoewercker, with an August force-push substituting a different author and changing nothing else. A public GitHub issue requests acknowledgment and corrected attribution. This is the author's documented account; Google's side had not been published at verification time.
• Apache-2.0 requires preserving copyright and attribution notices. That is the durable, verifiable point regardless of how this case resolves: permissive does not mean anonymous, and git history is evidence — force-pushes included.
• The GTM-stack read: attribution is the payment rail of permissive open source. If your team ships OSS as a distribution strategy (as many GTM tools in this registry do), this case is the argument for provenance discipline on both sides — keep receipts of what you published and when, and preserve notices in what you adopt.
• Curated from the GTM Stacker signal registry (2026-09-12 pass: daily pull + viral-posts brief).