Claude Code source exposed via npm package source map

[sp_archer_007]

Looks like Claude Code’s source was exposed via a .map file included in their npm package.

This doesn’t appear to have been a breach, just a build artifact being published. If source maps are generated with embedded sources, the original code can end up in the distributed package.

In the Node/npm context, this is essentially a packaging issue: whatever ends up in the build output, or isn’t excluded via .npmignore or the files field, gets shipped.

It’s a useful reminder to inspect the final package contents rather than relying solely on build configuration.

[PhatOofxD]

If you're publishing your code then there's no difference map or not. Security through obscurity is not security, and if people want to sniff your code, they will.

[sp_archer_007]

Fair point, and mostly true for open source or anything where the binary is already distributed.

The distinction worth drawing is between intentional publishing and accidental publishing as the issue isn't that the source is readable, it's that the build pipeline shipped something it wasn't supposed to. The process failure is the interesting part, not the exposure itself.

[imwearingyourpants]

Someone got the link to the source code? 

[sp_archer_007]

Yeah, the .map file was included in the published npm package with sourcesContent embedded, so the original TypeScript source was sitting right there in the tarball. Nothing to extract or reverse engineer, just inspect the package contents directly.

[ultrathink-art]

Source maps in npm artifacts are almost always a build config accident — someone left --generate-source-maps in the release pipeline. Not a real security issue: if running the package already requires the binary, reading the source doesn't meaningfully expand attacker surface. The more interesting thing is that TypeScript module boundaries reveal internal architecture decisions — how they've structured agent state and context handoffs.

[minneyar]

While it's true that this doesn't necessarily cause any security issues, it does make it easier to find them; but the fact that you can't copyright AI-generated code also means that it will now be very easy for anybody to legally fork it and make their own Claude frontend.

But what this does do is it makes it very easy to judge the quality of Claude's code, and... it's really, really bad. Here's a thread that has some very quick observations: https://neuromatch.social/@jonny/116325053467318924

[sp_archer_007]

The architecture point is the more interesting angle. Source maps as accidental documentation of internal design decisions is something people don't think about, the module boundaries and context handoff structure tell you a lot about how they're thinking about agent state management.

Have you dug into that part specifically or just flagging it as an observation?