Developer activity networks
Weekly contribution timelines and collaboration graphs show who works together across modules — not just commit counts.
Engineering intelligence
Map your codebase.
Understand your impact.
Decode contribution patterns, ownership trees, and complexity hotspots — from any public GitHub repository.
GitHub activity intelligence
Analyze any repository
Map ownership, collaboration, and complexity hotspots from public Git history — or use a showcase demo.
or try a showcase
Live GitHub API ready
Showcase demos offline
Tokens stay local
Built for engineering teams
CodeAtlas turns Git history into maps you can act on — ownership risk, collaboration, and refactor priorities.
Knowledge ownership maps
Interactive trees surface folders with low bus factor so you can plan pairing and reduce single-person risk.
Hotspots & churn
Complexity vs. change-frequency quadrants highlight files that deserve refactoring before they become liabilities.
Frequently asked questions
How metrics work, rate limits, and how your tokens are handled.
How does CodeAtlas fetch metrics?
It queries GitHub for commits, contributors, languages, and the repository tree, then derives ownership shares, collaboration links, and hotspot scores. When a developer dominates more than ~60% of recent change, that signals elevated knowledge-silo risk.
What is the bus factor?
The bus factor estimates how many people would need to leave before critical knowledge is at risk. A bus factor of 1 means a single engineer owns the bulk of a module — a high operational risk.
How are hotspots identified?
We combine change frequency (churn across recent commits) with an approximate complexity score. Files that are both complex and frequently edited rise into the critical quadrant for refactor prioritization.
Does the public API have rate limits?
Yes — unauthenticated GitHub access is about 60 requests per hour. Use PAT in the navbar to save a Personal Access Token and raise the limit to 5,000/hour.
Can I analyze private repositories?
Yes. Save a GitHub PAT with the repo scope. CodeAtlas will use it from your browser to load private metadata and build the same dashboards.
Are access tokens secure?
Tokens stay client-side in localStorage and are sent only to GitHub over HTTPS. Nothing is uploaded to a CodeAtlas backend.