You're offline — showing cached data where available.
repo-visualizer$ git log --stat --remote
a3f9c1d
See a repo's history before you clone it.
Paste any public GitHub repo. Get its commit rhythm, its people, its languages, and the tone of its issues — rendered like a diff, not a dashboard.
try
Unauthenticated GitHub API — capped at 60 requests/hour per IP. One repo lookup uses about 5.
Kept in memory for this tab only — never saved to disk, never sent anywhere but api.github.com. Create a token with no scopes (public read access is enough).
## health.score
One number built from the signals below — commit recency, contributor concentration, issue resolution, and documentation. A heuristic, not a certification.
—/100
## commits.log
Weekly commit volume from the most recent history on the default branch.
Top contributors by commit count, most active first.
## languages.stats
Share of the codebase by byte count, as reported by GitHub's linguist.
## issues.diff
Open vs. closed counts, plus a keyword-based read of issue titles — not real sentiment analysis, a quick lexicon scan.
## repo.summary AI · runs in your browser
A small instruction-following model downloads once and runs entirely on your device in a background thread — no server, no API key and no cost. It's briefed on the repo's languages, activity, structure, and README, then writes its own summary.