Google stole open source code without crediting the authors (Artemis/Minitap)
BlogI expected better from GoogleWhat we found in Artemis, and why open-source credit matters.We opened Google’s Artemis repository and recognised code we had written for mobile-use. We opened the repository and started looking through it. My reaction was pretty immediate:“What the fuck?
- ▪BlogI expected better from GoogleWhat we found in Artemis, and why open-source credit matters.We opened Google’s Artemis repository and recognised code we had written for mobile-use.
- ▪We opened the repository and started looking through it.
- ▪My reaction was pretty immediate:“What the fuck?
Hacker News (Front Page) files mainly under programming. We currently carry 1,500 of its stories. Top-voted stories on Hacker News.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | minitap |
| Canonical URL | https://www.minitap.ai/blog/i-expected-better-from-google |
| Publication time | Sat, 12 Sep 2026 02:39:39 +0000 |
| Retrieval time | 2026-09-12T03:27:50.927Z |
| Last seen | 2026-09-12T03:27:50.927Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | lrsxK-kuXOhg · 1 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
BlogI expected better from GoogleWhat we found in Artemis, and why open-source credit matters.We opened Google’s Artemis repository and recognised code we had written for mobile-use. Then we found our names in its history—and the change that removed them.Nicolas DehandschoewerckerCEO & Co-Founder, Minitap·September 11, 2026·7 minTopWhat we recognisedSharing code should make collaboration easierOur benchmark results have also been hard to get heardWe’ve contacted GoogleWhat disappoints meBlogBlogAbout minitapminitap is the autonomous QA agent that keeps mobile teams shipping fast.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at minitap.
Discussion
0 commentsMore from minitap
