On April 1, 2026, Anthropic published Claude Code version 2.1.88 to npm. That release reportedly included a JavaScript source map file containing the full source code. The affected version has since been removed from npm.
https://www.npmjs.com/package/@anthropic-ai/claude-code?activeTab=versions
Link to tweet: https://x.com/Fried_rice/status/2038894956459290963
This market resolves YES if, before April 2, 2026, PT timezone, Anthropic makes an official public statement confirming that the leak occurred.
The format of the statement does not matter. It may be a tweet, blog post, YouTube video, press statement, or any other public communication, as long as it is clearly an official confirmation from Anthropic and leaves no reasonable doubt that the company is acknowledging the leak.
This market will resolve YES shortly after such confirmation is made.
This market resolves NO if, by April 2, 2026, PT timezone, Anthropic has not issued any official public confirmation of the leak.
1,000🏅 Top traders
| # | Trader | Total profit |
|---|---|---|
| 1 | Ṁ404 | |
| 2 | Ṁ72 | |
| 3 | Ṁ51 | |
| 4 | Ṁ29 | |
| 5 | Ṁ2 |
I'm resolving this market as YES.
From the market description:
> press statement, or any other public communication, as long as it is clearly an official confirmation from Anthropic and leaves no reasonable doubt that the company is acknowledging the leak.
There are several news sources with direct statement from Anthropic spokesperson, (some sources say it is Christopher Nulty):
- https://www.theverge.com/ai-artificial-intelligence/904776/anthropic-claude-source-code-leak — Mar 31, 2026, 10:24 PM UTC
- https://www.theguardian.com/technology/2026/apr/01/anthropic-claudes-code-leaks-ai — Wed 1 Apr 2026 20.17 BST
these reports are dated before the deadline.
“Earlier today, a Claude Code release included some internal source code. No sensitive customer data or credentials were involved or exposed,” Anthropic spokesperson Christopher Nulty says in an emailed statement to The Verge. “This was a release packaging issue caused by human error, not a security breach. We’re rolling out measures to prevent this from happening again.”