Code towers
Packages stack by size and coupling — see architectural weight at a glance.
Code intelligence
Your Code as a City.
CodeCityScape builds a full module dependency graph from real imports — not guesses — and renders it as a live 3D city. Change frequency, test coverage, architecture health, and CVE exposure are all layered on the same map, updated on every commit.
- Live dependency graph from real imports
- Test coverage painted as building floors
- CVE propagation mapped to your architecture
- Architectural health score — cycles, violations, dead code
- PR status check + comment on every review
- Change heatmap & commit replay
- Team ownership territories
Free tier available · No credit card required
Live preview · procedural city · commit replay
Inside the product
Explore structure, coverage, and change
The three views your team will live in — from macro architecture down to per-file coverage.
Test coverage
File-level coverage overlay to find untested critical paths (Team+).
Timeline
How the graph evolved with commits and releases over time.
How your team uses it
From every PR to the Monday standup
CodeCityScape surfaces in the places your team already works — PR comments, alert emails, and the scene you open when something goes wrong.
In every PR review
Risk visible before merge
Every PR triggers a status check posted automatically to GitHub: health delta, new circular dependencies, and coverage change. Click through to watch the change ripple across the dependency graph before a single reviewer approves it.
Monday morning standup
Architecture truth, live
The city re-indexes on every merge. No stale diagrams, no missing services. Circular dependencies glow red — found by Tarjan's algorithm, exact modules listed. Layer violations are scored 0–100 with the sprint they first appeared.
Before any release
Coverage gaps you can see
Test coverage is painted as floors on every tower. A module at 23% isn't a statistic — it's a visually empty building sitting next to the modules that import it. Share the scene with your team via a public snapshot link — no account needed.
CVE triage
Vulnerability mapped to your architecture
One critical CVE lights up 31 modules in red. BFS propagation shows exactly which teams own affected paths. The exposure is a map, not a list — the "Dismiss" button stops getting clicked.
Built for every role
One tool, five different jobs done
The city is the shared surface. What each person sees on it — and what they do next — depends on the role.
Lead developer / tech lead
Instant architecture truth. No more "what does this actually depend on" archaeology — the graph is live and you didn't have to draw it.
Engineering manager
A health score you can show in a board review without building slides. Point at the city and say "this district is the problem" — everyone in the room gets it.
PR reviewer
Impact depth in the PR comment. The check tells you what changed and how far it propagates before you read a single line of diff.
New joiner
An actual map of the codebase on day one. Explore the city, click towers, and understand ownership before you touch a file.
Security / platform team
CVE propagation depth shown visually — only the modules your team owns that are actually affected. Not a filtered list; a spatial picture.
QA manager
Coverage gaps shown spatially against the modules that changed. When a PR touches a low-coverage path or a dependency shifts, you see the exposure before testing begins — not after a defect escapes.
How it works
From repo to city in four steps
No agents to install, no scripts to run. Point CodeCityScape at your repo and keep working.
- Step 1
Connect your repository
Authorize a repo — public or private — in seconds. We never store your source.
- Step 2
We index your code
Parsers extract modules, dependencies, and change history across 11+ languages.
- Step 3
Explore the city
Fly through your repo, replay commits, and overlay coverage to spot risk fast.
- Step 4
Visualise Impact
Review the changes, enabling informed decisions to be made.
Languages
Languages we index today
First-class parsing and dependency edges for the stacks below. We expand coverage regularly — if you need another language or dialect for your org, tell us.
TypeScriptJavaScriptPythonGoRustJavaKotlinRubyGroovyC / C++C#
Need Swift, PHP, or something else? Request a language — we prioritize by customer demand.
Ready to see your repo as a city?
Connect a repository in under a minute. Free tier available.