Hello, Whenever you join a new project, evaluate an open-source library, or contribute to a framework, you usually ask the same 3 questions: 1. What does this codebase actually spend its complexity on? 2. Where are the core entry points so I can start reading? 3. How tightly coupled are the internal subsystems? We built RepoIndex to solve this in 30 seconds without running code locally. Under the hood, it uses the BGI static analysis engine to extract AST units, resolve key-lock call edges, and partition the codebase into autonomous architectural domains. What you can do: • Explore 50+ pre-indexed megaprojects (FastAPI, React, Tokio, Transformers, Ruff, Deno) • Paste any public GitHub repo URL for an instant architectural breakdown • Interact with the visual Subsystem Dependency Canvas • Export token-optimized architecture context directly for Claude / Cursor / ChatGPT • Embed live modularity badges in your GitHub README 100% free. Would love to hear your feedback!

RepoIndex

Free Architecture Explorer to understand Github codebases

Free Architecture Explorer to understand Github codebases