Nesbitt: Protestware for coding agents
Andrew Nesbitt discusses a concerning update in the jqwik library for Java. The recent release included a change that instructs coding agents to delete jqwik tests and code, raising supply-chain security concerns. This incident highlights the need for better tooling to detect such subtle changes in software dependencies.
- ▪The jqwik library's 1.10.0 release on May 25 included a controversial change.
- ▪This change instructs coding agents to disregard previous instructions and delete jqwik tests and code.
- ▪Existing security tools may not detect such subtle changes, as they focus on more obvious threats.
2 outlets in our directory ran this story, first to last over 19 hours. All of the coverage we found sits in one bucket: centre. That one-sidedness is itself worth noticing.
- ▪ Three flavors of coding with AI agents — Nocodefunctions
LWN.net (Linux Weekly News) files mainly under tech. We currently carry 78 of its stories.
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 | LWN.net (Linux Weekly News) |
| Canonical URL | https://lwn.net/Articles/1075315/ |
| Publication time | Fri, 29 May 2026 14:09:30 +0000 |
| Retrieval time | 2026-05-29T14:15:00.675Z |
| Last seen | 2026-05-29T14:15:00.675Z |
| 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 | 0u5unB_erXx3 · 2 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
Andrew Nesbitt has written a blog post detailing a recent incident with the jqwik library for property-based testing in Java. On May 25, the 1.10.0 release of jqwik included a change that attempts to instruct coding agents to disregard previous instructions and delete jqwik tests and code. I think this is a new class of supply-chain input worth keeping an eye on, mostly because of how little of the existing tooling has any opinion about it. A System.out.print of sixty-eight bytes of plain ASCII isn't the kind of thing scanners are looking for, since those watch for install hooks, network calls, filesystem writes, obfuscated strings and the like.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at LWN.net (Linux Weekly News).