Architecture of repowise-dev/repowise

Input enters through the repowise command defined in packages/cli/src/repowise/cli/main.py, which indexes a repository, generates its docs and checks its health. The engine in packages/core does the core work: it parses the code, builds the dependency graph and git history, and writes wiki pages, health reports and recorded decisions. Call resolution in packages/core/src/repowise/core/ingestion/call_resolver.py decides which function calls which, and each edge in the graph records how it was resolved. The server package exposes this index over HTTP and MCP, and packages/server/src/repowise/server/mcp_server/tool_answer/answer.py builds the cited answers that agents receive. The dead code analyzer in packages/core/src/repowise/core/analysis/dead_code/analyzer.py flags unused code by confidence tier. The api-client package in packages/api-client/src/index.ts wraps calls to the server with a configurable base URL and token.

• packages: 4,547 files and 733,208 lines of code
• tests: 2,170 files and 460,994 lines of code
• scripts: 20 files and 4,139 lines of code
• ci: 4 files and 184 lines of code
• docker: 2 files and 95 lines of code
• docs: 2 files and 18 lines of code
• examples: 1 file and 52 lines of code
• root: 1 file and 76 lines of code

By file count: Python 4,709 files, TypeScript 2,016 files, JavaScript 12 files, Shell 8 files, Dockerfile 1 file, Makefile 1 file.

Repowise documents repowise in 5,578 pages generated from the source, 117 of them written explanations of the repository and its modules.