Why Claude Code's Source Code Leaked — And It Wasn't Simple Human Error

TL;DR: Claude Code's source leak wasn't a developer slipping up during a release. It was a silent CI pipeline failure combined with an overly permissive cloud storage bucket — two independent mistakes that became catastrophic when they happened at the same time. The root cause of this Claude Code source code leak is strikingly similar to the App Store web frontend leak from about five months ago, where the Svelte + TypeScript source was accidentally exposed. For an engineering project of Claude Code's scale, a CI/CD pipeline is a given, with build configurations and scripts that are locked down and consistent. It's highly unlikely that an individual developer made a one-off mistake during this particular release. So why wasn't the source map removed from the build artifacts? Why Wasn't the Source Map Removed? The answer lies in how production error monitoring works. If you're using a platform like Sentry to track runtime errors, you need source maps — there's no way around it. This mea