GitHub Repo Doctor — GitHub repository analyzer
GitHub Repo Doctor is a free GitHub repository analyzer that helps you understand any codebase fast. Analyze a public repository instantly, or connect a private one with read-only access, to get an explainable 0–100 health score, an architecture map, an interactive dependency graph, a searchable code explorer, a secret scan and analysis of open GitHub issues. The core analysis is deterministic — computed from real repository signals, not guessed — and optional AI explanations (using your own free Groq key) describe the code using only files that actually exist.
How GitHub Repo Doctor works
Analyze a GitHub repository in about a minute:
- Paste a GitHub URL — e.g. https://github.com/owner/repo — or connect GitHub to analyze a private repository.
- Repo Doctor reads the file tree once and fetches only a bounded set of key files (public repos use GitHub’s public API; private repos go through a read-only server proxy).
- Explore the dashboard — health score, tech stack, architecture map, dependency graph, code explorer, important files, security and activity.
- Open the code explorer or dependency graph to inspect files and their real import relationships, and open the issues view to triage open GitHub issues.
- Optionally add a free Groq key to have AI explain a file or an issue, grounded in the real code.
What GitHub Repo Doctor checks
- Repository health score. A deterministic 0–100 score with a letter grade, from real signals — documentation, testing, dependencies, security, maintainability and structure — never a random AI number.
- Architecture map. An evidence-based view of the layers that actually exist (frontend, API/services, data, deployment) with per-layer file counts.
- Dependency graph. An interactive map built from real imports (ES import/require, dynamic import, TypeScript and Python) resolved against the file tree — edges appear only when an import resolves to a real file.
- Security scan. Flags obviously exposed keys and credentials, always masked, and never sends sensitive files to AI.
Explore your codebase and issues
- Code explorer. Search the file tree, open any source file with syntax highlighting, and jump to related files detected from real imports.
- GitHub issues analysis. Browse open issues, filter and sort them, and see the source files each issue most likely affects — matched from the issue text against the real file tree.
- Private repository analysis. Connect a read-only GitHub App to analyze private repositories; the installation token stays server-side and is never exposed to the browser.
- AI-assisted explanations. Ask AI to explain a file or an issue. Prompts are limited to real, redacted context — never your whole codebase, secrets or .env files.
What is GitHub Repo Doctor?+
GitHub Repo Doctor is a free GitHub repository analyzer. It reads a repository and produces a health-and-architecture report: an overview, the detected tech stack, a searchable code explorer, an interactive dependency graph, an explainable 0–100 health score, the most important files, a scan for obviously exposed secrets, and analysis of open GitHub issues.
Can I analyze a private GitHub repository?+
Yes. Public repositories work instantly with no sign-in. For a private repository you connect GitHub with read-only access (a GitHub App you can revoke anytime); private-repository reads go through a server-side proxy, so no GitHub token is ever exposed to your browser.
Do I need a GitHub token or password?+
No password or personal token. Public repositories use GitHub’s public API directly from your browser. For private repositories you authorize a read-only GitHub App; the credentials stay on the server and the browser never receives a token.
Is the health score AI-generated?+
No. The score is deterministic — every point comes from a real signal in the repository (README and license, tests and CI, lockfile and dependency count, exposed-secret findings, activity and contributors, project structure). AI, if used, only explains the results; it never sets the score.
How does the dependency graph work?+
It builds relationships from actual imports — ES import/export, CommonJS require, dynamic import, TypeScript and Python imports — resolved against the real file tree. An edge appears only when an import resolves to a file that truly exists; it never guesses relationships from similar filenames.
Is my data private?+
Public analysis runs in your browser against GitHub’s public API; private analysis runs through a read-only server proxy. The optional AI explanation sends only a small, redacted slice of the repository (a structured summary and a few truncated excerpts) to Groq using your own API key — never detected secrets, .env files, or the whole codebase.
Does the AI invent files or vulnerabilities?+
No. The deterministic analysis only reports what it actually finds, and the AI is constrained to the real files provided and told never to invent files, functions or facts. Dependency version and vulnerability checks are not claimed — verify those with npm audit or GitHub Dependabot.
What about very large repositories?+
The tool reads the file tree once and fetches only a bounded set of files, skipping node_modules, build output, binaries and media. The dependency graph shows a focused, explorable subset rather than thousands of nodes at once, and long issue lists are virtualized, so even large repositories stay responsive.