GitHub Repo Analyzer
Paste a public GitHub repository URL to get an instant health score, language and contributor breakdown, commit history insights, and a dependency-hygiene audit — fetched directly from the GitHub API in your browser.
How it works
- Paste a GitHub URL, or just owner/repo, and click Analyze.
- The tool queries the public GitHub REST API in a Web Worker, so even large repositories don't freeze the page.
- Browse the Overview, Code, Contributors, History, and Dependencies tabs, then export the report as JSON or Markdown.
What it analyzes
- Repository health — README, license, CI, tests, SECURITY.md, contributing guide, releases, and recent activity
- Language breakdown, largest files, directory structure, and detected build/config files
- Top contributors, bus-factor risk, and a commit-activity heatmap
- Recent commits, conventional-commit adherence, branches, tags, and releases
- Dependency-hygiene checks for package.json, requirements.txt, pom.xml, Cargo.toml, go.mod, and Gemfile — pin discipline and lockfile presence, not a CVE scan
Free online GitHub repo analyzer — runs entirely in your browser
This tool calls the public GitHub REST API directly from your browser to build a full picture of a repository: how healthy its maintenance practices look, who's actually contributing, how active its commit history is, and whether its declared dependencies follow basic hygiene. Without a token it runs a lite analysis inside GitHub's 60-requests-per-hour limit; adding a free personal access token (kept in memory only, never persisted) raises that to 5,000/hour and unlocks commit-activity heatmaps, PR velocity, and deeper history. Large repositories are fetched and parsed inside a Web Worker so the page never freezes. Share a result with the auto-generated ?repo= link, or export the report as JSON, Markdown, or a copy-paste summary.
Frequently Asked Questions
- How do I analyze a GitHub repository online?
- Paste a public GitHub repo URL — or just "owner/repo" — into the box above and click Analyze. The tool calls the GitHub API directly from your browser and renders stats, health, contributors, and dependency hygiene as a dashboard.
- Can I see repo stats without cloning?
- Yes. Every metric — languages, contributors, commit history, dependency manifests — comes from GitHub's REST API. No git clone, checkout, or local install is needed.
- Do I need a GitHub token?
- No. Without a token the tool runs in "lite mode" using GitHub's 60-requests-per-hour unauthenticated limit, covering overview, languages, code, contributors, and recent commits. Adding a free personal access token raises the limit to 5,000/hour and unlocks the commit-activity heatmap, PR velocity, and branch/tag counts.
- How is the health score calculated?
- It is a composite of 8 equally-weighted checks: README present, license present, a CONTRIBUTING guide, a SECURITY.md, CI configuration, a tests directory, a push within the last 120 days, and at least one tagged release.
- Is my data sent to a server?
- No. Every request goes directly from your browser to api.github.com — Hexabench has no backend for this tool and never sees your token, the repository contents, or the analysis output.
- Is the dependency check a vulnerability scanner?
- No — it checks hygiene, not CVEs: pinned vs. unpinned versions, lockfile presence, and whether Dependabot is configured. Real vulnerability scanning needs a CVE database, which this client-side tool intentionally does not attempt.
- Does this work on private repositories?
- Not in this version — analysis is scoped to public repositories only, even if you supply a personal access token.
- Why do some sections say "add a token"?
- Data like the commit-activity heatmap, PR velocity, and branch/tag counts needs extra API calls that would exhaust the 60/hour unauthenticated limit quickly, so they are skipped in lite mode and appear automatically once a token is added.