src/cli/print.ts This is the single worst function in the codebase by every metric: - 3,167 lines long (the file itself is 5,594 lines) - 12 levels of nesting at its deepest - ~486 branch points of cyclomatic complexity - 12 parameters + an options object with 16 sub-properties - Defines 21 inner functions and closures - Handles: agent run loop, SIGINT, rate-limits, AWS auth, MCP lifecycle, plugin install/refresh, wo…
the claude code team ethos, as far as i’ve been lead to understand— which i agree with, mind you— is that there is no point in code-reviewing ai-generated code… simply update your spec(s) and regenerate. it is just a completely different way of interacting with the world. but it clearly works for them, so people throwing up their hands should at least take notice of the fact that they are absolutely not competing wit…
Claude Code's source code has been leaked via a map file in their NPM registry
751–760 of 1001 posts
Re: Claude Code's source code has been leaked via a map file in their NPM registry
#752[1] https://www.tasking.com/documentation/smartcode/ctc/referenc...
Re: Claude Code's source code has been leaked via a map file in their NPM registry
#753Gemini CLI and Codex are open source anyway. I doubt there was much of a moat there anyway. The cool kids are using things like https://pi.dev/ anyway.
There is _a lot_ of moat. Claude subscriptions are limited to Claude Code. There are proxies to impersonate Claude Code specifically for this, but Anthropic has a number of fingerprinting measures both client and server side to flag and ban these.
With the release of this source code, Anthropic basically lost the lock-in game, any proxy can now perfectly mimic Claude Code.
Re: Claude Code's source code has been leaked via a map file in their NPM registry
#754Earlier quoted context omitted.
(I mostly agree with you, but) devils advocate: most people already do that with dependencies, so why not move the line even further up?
Because you trust that your dependencies are not vibe coded and have been reviewed by humans.
Re: Claude Code's source code has been leaked via a map file in their NPM registry
#755Earlier quoted context omitted.
So, think of it as a business man: You don't really care if your customers swear or whatever, but you know that it'll generate bad headlines. So you gotta do something. Just like a door lock isn't designed for a master criminal, you don't need to design your filter for some master swearer; no, you design it good enough that it gives the impression that further tries are futile. So yeah, you do what's less intesive to…
This door lock doesn’t even work against people speaking French, so I think they could have tried a mite harder.
Re: Claude Code's source code has been leaked via a map file in their NPM registry
#756Also, not sure why anthropic doesn’t just make their cli open source - it’s not like it’s something special (Claude is, this cli thingy isn’t)
Re: Claude Code's source code has been leaked via a map file in their NPM registry
#757Earlier quoted context omitted.
Probably a lot of my prompts have been logged then. I’ve used wtf so many times I’ve lost track. But I guess Claude hasn’t
Did you notice a change in quality after you went foul?
It’s about a once a week or less event. A bit annoying sometimes, but not a deal breaker
Re: Claude Code's source code has been leaked via a map file in their NPM registry
#758Re: Claude Code's source code has been leaked via a map file in their NPM registry
#759wondering whether it was a human mistake or a CLAUDE model error.
Re: Claude Code's source code has been leaked via a map file in their NPM registry
#760Obfuscated ts/js code is not machine code to begin with, so not sure what’s the big deal. Also, not sure why anthropic doesn’t just make their cli open source - it’s not like it’s something special (Claude is, this cli thingy isn’t)
They don't want everyone to see how poorly it's implemented and that the whole thing is a big fragile mess riddled with bugs. That's my experience anyway.
For instance, just recently their little CLI -> browser oauth login flow was generating malformed URLs and URLs pointing to a localhost port instead of their real website.