Sign in with GitHub
Authenticate with a personal access token to analyze any public repository. Everything runs client-side.
What it does
Paste any public GitHub repository and get a clean breakdown of how it's built — no cloning, no local setup, nothing to install.
File breakdown by extension
Walks a repository's entire Git tree and counts every file — split by code vs. non-code and by extension (.ts, .py, .go, .md, whatever's actually in there).
Repository health, one click away
Stars, forks, open issues & PRs, license, topics, and how recently it was pushed to — pulled from the same request that starts analysis, so it costs nothing extra.
Pull request velocity
Exact open/merged/closed counts straight from GitHub's own totals, plus median time-to-merge and average age of open PRs from an unbiased sample — accurate on repos with tens of thousands of PRs.
Search that keeps up as you type
Instant, local filtering across title, author, branch, labels, and description, with GitHub-style qualifiers like is:open and author:name. Deep search hands off to GitHub's own index when you need to reach comments too.
Runs entirely in your browser
No backend, no signup beyond your own GitHub token, no data stored anywhere but this tab.
Frequently asked questions
Do I need to clone the repository?
No — analysis happens entirely through GitHub's REST API, directly from your browser. Nothing is downloaded to your machine or a server, no matter how large the repo is.
What GitHub token permissions does this need?
A personal access token with read-only public_repo access is enough — create one at github.com/settings/tokens. It's stored only in this browser and used solely to talk to GitHub's own API.
How is pull request velocity calculated?
Open, merged, and closed-without-merge counts come straight from GitHub's Search API totals, not just whatever's loaded on screen. Median time-to-merge and average open-PR age come from a spread sample across the repository's history, so the numbers stay accurate even on repos with tens of thousands of PRs.
Does this work on renamed or transferred repositories?
Yes — if a repository has moved (for example, facebook/react is now react/react), the tool resolves GitHub's current canonical name automatically before running any analysis.
Is my token ever sent anywhere besides GitHub?
No. Every request goes straight from your browser to api.github.com under a strict content security policy that blocks the page from talking to anywhere else.