Repository profile
ponponon/claude_code_src
2026.3.31 claude code 意外把包含源码的文件上传到 npm 仓库，版本号是 2.1.88，其中 cli.js.map 文件有 57MB 的体积，claude code 的源码在该文件的 sourcesContent 字段里面，解压还原后有 70w 行代码
Why this page exists
Use this profile to move from awareness into adoption-oriented inspection.
Best next step
Check the summary, then compare it against similar projects before touching production.
Research posture
Momentum helps discovery. Fit, maintenance quality, and reversibility decide adoption.
Editorial summary
The Claude Code 2.1.88 Source Recovery project is an initiative to reconstruct the source code of the Claude Code CLI application from the `cli.js.map` file, which was inadvertently uploaded to npm. This repository houses the extracted source code, comprising approximately 700,000 lines, allowing developers and researchers to study the architecture, command system, and Model Context Protocol (MCP) implementation of Claude Code. It serves as a valuable resource for understanding the underlying design choices and technical structures utilized within the CLI framework.
Use cases for this project include educational purposes for developers looking to learn from a sophisticated CLI application, as well as research on command systems and terminal UI design using React and Ink. Additionally, it can assist in the evaluation of the MCP integration within command-line tools, providing insights that could inform the development of similar applications or enhancements to existing ones.
Adoption analysis
Best-fit use case
ponponon/claude_code_src is most useful to evaluate when your team is researching TypeScript ecosystem tooling. Compare its documented workflow with your runtime, deployment model, and maintenance capacity before adopting it.
Momentum signal
Recent tracked star growth is modest, so maintenance quality and fit may matter more than momentum. Daily and three-day changes are discovery signals, while total stars show accumulated awareness.
Adoption caution
Before adding it to production, review license terms, dependency footprint, security guidance, open issue quality, and whether there is a clear path to migrate away later.
What to inspect next
- 1Run the quick install in a disposable project before touching production code.
- 2Check whether the README clearly states the project scope and non-goals.
- 3Identify at least two alternatives so the decision is not based on one ranking page.
- 4Read recent issues and releases to understand maintenance rhythm, breaking changes, and common failure modes.