They have an interesting regex for detecting negative sentiment in users prompt which is then logged (explicit content): https://github.com/chatgptprojects/claude-code/blob/642c7f94... I guess these words are to be avoided...
An LLM company using regexes for sentiment analysis? That's like a truck company using horses to transport parts. Weird choice.
Claude Code's source code has been leaked via a map file in their NPM registry
721–730 of 1001 posts
Re: Claude Code's source code has been leaked via a map file in their NPM registry
#722I'd agree if it was launch-and-forget scenario.
But this code has to be maintained and expanded with new features. Things like lack of comments, dead code, meaningless variable names will result in more slop in future releases, more tokens to process this mess every time (like paying tech-debt results in better outcomes in emerging projects).
Re: Claude Code's source code has been leaked via a map file in their NPM registry
#723Earlier quoted context omitted.
>there is no point in code-reviewing ai-generated code the idea that you should just blindly trust code you are responsible for without bothering to review it is ludicrous.
(I mostly agree with you, but) devils advocate: most people already do that with dependencies, so why not move the line even further up?
Yeah we get supply chain attacks (like the axios thing today) with dependencies, but on the whole I think this is much safer than YOLO git-push-force-origin-main-ing some vibe-coded trash that nobody has ever run before.
I also think this isn't really true for the FAANGs, who ostensibly vendor and heavily review many of their dependencies because of the potential impacts they face from them being wrong. For us small potatoes I think "reviewing the code in your repository" is a common sense quality check.
Re: Claude Code's source code has been leaked via a map file in their NPM registry
#724Earlier quoted context omitted.
You'll never win this battle, so why waste feelings and energy on it? That's where the internet is headed. There's no magical human verification technology coming to save us.
I can prove all contributions to stagex are by humans because we all belong to a 25 year old web of trust with 5444 endorser keys including most redhat, debian, ubuntu, and fedora maintainers, with all of our own maintainer keys in smartcards we tap to sign every review and commit, and we do background checks on every new maintainer. I am completely serious. We have always had a working proof of human system called W…
Re: Claude Code's source code has been leaked via a map file in their NPM registry
#725Earlier quoted context omitted.
Fatalism will also not fix anything. But I suppose death comes for us all, yes? Why do anything at all?
I feel that fatalism, especially when people treat it as some sort of personal philosophy, is kind of lazy. It requires no effort to say "fuck this, nothing matters anyway", and then justify doing literally nothing.
Re: Claude Code's source code has been leaked via a map file in their NPM registry
#726This leak is actually a massive win. Now the whole community can study Claude Code’s architecture and build even better coding agents and open-source solutions.
Re: Claude Code's source code has been leaked via a map file in their NPM registry
#727Re: Claude Code's source code has been leaked via a map file in their NPM registry
#728Earlier quoted context omitted.
A defining work of the "just vibes" era.
You fail to mention the prior decades of really bad software engineers writing awful code -- off of which these models trained.
Re: Claude Code's source code has been leaked via a map file in their NPM registry
#729Would be interesting to run this through Malus [1] or literally just Claude Code and get open source Claude Code out of it. I jest, but in a world where these models have been trained on gigatons of open source I don't even see the moral problem. IANAL, don't actually do this. https://malus.sh/
Re: Claude Code's source code has been leaked via a map file in their NPM registry
#730I think this is ultimately caused by a Bun bug which I reported, which means source maps are exposed in production: https://github.com/oven-sh/bun/issues/28001 Claude code uses (and Anthropic owns) Bun, so my guess is they're doing a production build, expecting it not to output source maps, but it is.