Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Claude Code's source code has been leaked via a map file in their NPM registry

twitter.com

Post reply on HN
Print view View original

631–640 of 1001 posts

Re: Claude Code's source code has been leaked via a map file in their NPM registry

#631

Post by mmh0000 »

SoftTalker wrote: post #521
integralid wrote: post #423

Earlier quoted context omitted.

I always type "please continue". I guess being polite is not a good idea.

Always seems strange to me that people say "please" and "thank you" to LLMs.

It actually works really well if you suck up to the AI.

"Please do x"

"Thank you, that works great! Please do y now."

"You're so smart!"

lol. It really works though! At least in my experience, Claude gets almost hostile or "annoyed" when I'm not nice enough to it. And I swear it purposefully acts like a "malicious genie" when I'm not nice enough. "It works, exactly like you requested, but what you requested is stupid. Let me show you how stupid you are."

But, when I'm nice, it is way more open, like "Are you sure you really want to do X? You probably want X+Y."

Re: Claude Code's source code has been leaked via a map file in their NPM registry

#632

Post by breatheoften »

encoderer wrote: post #622
arcanemachiner wrote: post #609

Earlier quoted context omitted.

I wish. Claude Code is clearly a pile of vibe-coded garbage. The UI is janky and jumps all over the place, especially during longer sessions. (Which also have a several second delay to render. In a terminal). Lately, it's been crashing if I hold the Backspace key down for too long. Being open-source would be the best thing to happen to them. At least they would finally get a pair of human eyes looking at their codeba…

As a point of reference, I’m a heavy cc user and I’ve had a few bugs but I’ve never had the terminal glitches like this. I use iterm on macOS sequoia.

To offer the opposite anecdotal evidence point -- claude scrolls to the top of the chat history almost capriciously often (more often than not) for me using iterm on tahoe

Re: Claude Code's source code has been leaked via a map file in their NPM registry

#633

Post by stackghost »

lynx97 wrote: post #630
stackghost wrote: post #606

Earlier quoted context omitted.

I am actively building non-magical human verification technology that doesn't require you uploading your retinal scans or ID to billionaires or incompetent outsourcing firms.

Great! Lets do the CAPTCHA-test: Will I, as a 100% blind user, be able to complete your process?

I think so? Can you use a smartphone?

edit: can't reply, the rate-limiting is such an awful UX

Re: Claude Code's source code has been leaked via a map file in their NPM registry

#634

Post by Normal_gaussian »

hanspagel wrote: post #629
foob wrote: post #552

Amusingly, they deprecated it with a message of "Unpublished" instead of actually unpublishing it [1]. When you use npm unpublish it removes the package version from the registry, when you use npm deprecate it leaves it there and simply marks the package as deprecated with your message. I have to imagine the point was to make it harder for people to download the source map, so to deprecate it with this message gives…

You can’t unpublish a npm package with more than 100 downloads I think.

The policy is https://docs.npmjs.com/policies/unpublish

    Packages published less than 72 hours ago
    
    For newly created packages, as long as no other packages in the npm Public Registry depend on your package, you can unpublish anytime within the first 72 hours after publishing.
There are 231+ packages that depend on this one, and I imagine they mostly use permissive enough version ranges that this was included.

Re: Claude Code's source code has been leaked via a map file in their NPM registry

#635

Post by eclipxe »

knome wrote: post #584
keeganpoppen wrote: post #529

Earlier quoted context omitted.

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…

>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.

Why?

Re: Claude Code's source code has been leaked via a map file in their NPM registry

#636

Post by stackghost »

RockRobotRock wrote: post #215
0x3f wrote: post #134

Earlier 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.

>There's no magical human verification technology coming to save us. Except for the one Sam Altman is building.

Scam Altman is not trustworthy. I hope nobody gives him their biometrics. I certainly would never.

Re: Claude Code's source code has been leaked via a map file in their NPM registry

#637

Post by skeledrew »

BoppreH wrote: post #113

Undercover mode also pretends to be human, which I'm less ok with: https://github.com/chatgptprojects/claude-code/blob/642c7f94...

Heh, this is what people who are hostile against AI-generated contributions get. I always figured it'd happen soon enough, and here it is in the wild. Who knows where else it's happening...

Re: Claude Code's source code has been leaked via a map file in their NPM registry

#639

Post by kolkov »

weakfish wrote: post #390
kolkov wrote: post #351

[flagged]

Is the thank you to Claude sarcasm? That seems like a fairly long logical leap, and LLMs have no ideological motivation

"Is the Claude thank you sarcasm?" — Mostly. But the sequence is real: we filed #39755 asking for source access on March 27, the source map shipped on March 31. The actual explanation is simpler — Bun generates source maps by default, and nobody checked the build output. Which is itself the point: 64K lines of code with no build verification process.
Post reply on HN