GitHub repository visualizer for architecture and dependencies

What the map shows

The same scan feeds several views of one repository.

• Architecture: files grouped into modules, with the imports between modules as a network
• Dependency graph: every resolved import, and the reverse links that show what depends on a file
• Cycles: groups of modules that import each other
• Hotspots: large, central, frequently changed files ranked for review
• History: commit activity on each file, visible as cranes and weathering in the skyline

Onboarding and code review

Opening an unfamiliar repository usually means reading folders until the important file turns up. In the city the important file is the tall building every road leads to. Clicking it shows what it exports and imports, who changed it last and what would be affected by changing it — the questions a new contributor or a reviewer asks first.

Share and embed

Every city has a public page with a written description of the project, a link you can share, a preview image for social posts and a badge for your README that links back to the city.

Questions

How do I visualize a GitHub repository?

Paste owner/name or the repository URL into RepoVerse and press enter. Public repositories need no account; for most projects the city is ready in under a minute.

Can I visualize a private repository?

Yes, with a GitHub sign-in that grants access. The token is used only to fetch that repository, and private cities are not shown publicly.

Does it show the dependency graph between files?

Yes. Every resolved import is a road between two buildings, and selecting a file highlights both what it imports and what imports it.

Related

• 3D code visualization: walk through a codebase as a cityTurn any GitHub repository into an explorable 3D city: folders become districts, files become buildings sized by code, imports become roads, git history shapes the skyline.
• GitHub security scanner for code, secrets and dependenciesScan a GitHub repository for injection flaws, leaked secrets and vulnerable dependencies. Data-flow traces from request to sink, lockfile-aware, with fixes.
• Dependency vulnerability scanner that reads your lockfileCheck npm, yarn, pnpm, PyPI, Cargo, Composer and RubyGems lockfiles against the OSV vulnerability database. Exact installed versions, transitive paths and fixed releases.