Good. While I don't condone anything illegal, influential code like this is nearly always better made public.
Claude Code's source code has been leaked via a map file in their NPM registry
861–870 of 1001 posts
Re: Claude Code's source code has been leaked via a map file in their NPM registry
#862[dead]
Re: Claude Code's source code has been leaked via a map file in their NPM registry
#863Earlier quoted context omitted.
" - it’s not like it’s something special (Claude is, this cli thingy isn’t)" How do you know? Have you checked the source? Do you know how exactly context is created, memory files, skills? Subagents created with tasks? I don't, but am checking right now. Then I will judge.
bc I build stuff like this myself - it doesn’t take anything to build a wrapper client around a good llm, including using another llm.
So .. the stuff you build yourself, you point it to claude then it runs just as productive as Claude CLI? Did you try?
Re: Claude Code's source code has been leaked via a map file in their NPM registry
#864Really surprising how many people are downplaying this leak! "Google and OpenAi have already open sourced their Agents, so this leak isn't that relevant " What Google and OpenAi have open sourced is their Agents SDK, a toolkit, not the secret sauce of how their flagship agents are wired under the hood! expect the takedown hammer on the tweet, the R2 link, and any public repos soon
> What Google and OpenAi have open sourced is their Agents SDK, a toolkit, not the secret sauce of how their flagship agents are wired under the hood And how is that any different? Claude Code is a harness, similar to open source ones like Codex, Gemini CLI, OpenCode etc. Their prompts were already public because you could connect it to your own LLM gateway and see everything. The code was transpiled javascript which…
[deleted]
Re: Claude Code's source code has been leaked via a map file in their NPM registry
#865Earlier quoted context omitted.
> One thing we know for sure is LLMs write code differently than we do. Kind of. One thing we do know for certain is that LLMs degrade in performance with context length. You will undoubtedly get worse results if the LLM has to reason through long functions and high LOC files. You might get to a working state eventually, but only after burning many more tokens than if given the right amount of context. > The worst ou…
> They became popular because teams across the industry analyzed code responsible for bugs/SEVs, and all found high correlation between these metrics and shipping defects. Yes, based on research of human code. LLMs write code differently. We should question whether the human research applies to LLMs at all. (You wouldn't take your assumptions about chimp research and apply them to parrots without confirming first) >…
They write code differently but that doesn't mean that's the kind of code they prefer to read. Don't ascribe too much intention to a stochastic process.
Their coding style is above all else a symptom of their very limited context window and complete amnesia for anything that's not in the window.
Re: Claude Code's source code has been leaked via a map file in their NPM registry
#866Earlier quoted context omitted.
An LLM company using regexes for sentiment analysis? That's like a truck company using horses to transport parts. Weird choice.
Oh it’s worse than that. This one ended up getting my account banned: https://github.com/anthropics/claude-code/issues/22284
... and closed for inactivity like basically every issue in the repo, of course.
Re: Claude Code's source code has been leaked via a map file in their NPM registry
#867There's a bunch of unreleased features and update schedules in the source, cool to see. One neat one is the /buddy feature, an easter egg planned for release tomorrow for April fools. It's a little virtual pet, sort of like Tamagotchi, randomly generated with 18 species, rarities, stats, hats, custom eyes. The random generation algorithm is all in the code though, deterministic based on you account's UUID in your cla…
Congrats on the legendary, happy with my uncommon ghost, turned it into a holographic trading card via Gemini instead of ASCII.
The stats bars and rarity colors are all derived from the UUID roll.
Fun rabbit hole: https://github.com/dyz2102/buddy-card
Re: Claude Code's source code has been leaked via a map file in their NPM registry
#868Earlier quoted context omitted.
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…
Can't you just instruct Claude Code to use your signing keys? I understand you may say "I won't." But my point is that someone can.
The people who signed my keys trust me to be an honest human actor that chose this as the singular identity they signed for the human body they met in person.
I -could- burn my 16+ years of reputation by letting a bot start signing commits as me, and I could also set my house on fire. I have very strong incentive not to do so as my aggregate trust is very expensive and the humans that signed me would be unlikely to sign a second if I ruined the reputation of my first.
This incentive structure is why web of trust actually works pretty well, and is the best "proof of human" we are likely ever going to have while respecting privacy and anonymity for those that need it.
Re: Claude Code's source code has been leaked via a map file in their NPM registry
#869Earlier quoted context omitted.
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…
With 5400+ people I am betting that you have at least one person in your 'web of trust' that no longer deserves that trust. That's one of the intrinsic problems with webs of trust (and with democracy...), you extend your trust but it does not automatically revoke when the person can no longer be trusted.
Of course! There are always edge cases, but I would suspect the number of bots signed by reputable keys to be near 0%, and the honest human score in this trust graph to be well over 90%.
Compare to how much we should trust any random unsigned key signing commits, or unsigned commits, in which the trust should be 0% unless you have reviewed the code yourself.
Re: Claude Code's source code has been leaked via a map file in their NPM registry
#870Earlier quoted context omitted.
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…
You can only prove that all contributions are pushed by those humans, and you can quite explicitly/clearly not prove that those humans didn't use any AI prior to pushing.
I absolutely do not care what autocomplete tools someone used. Only that they as humans own and sign what is submitted so it is attached to their very expensive reputations they do not want to lose.