RepoAtlas
Star on GitHub ↗
A source-backed map of your TypeScript project

Know whatimports what.

RepoAtlas turns unfamiliar code into a map you can check. Click an edge to open the import line behind it.

Map your repository ↓Explore the Hono map ↗
Hono snapshot · commit 52f6c7e
247modules
676connections
65detected entries
Hono · source evidenceOpen interactive map ↗
Hono architecture map. A selected connection represents four imports, with all four corresponding source locations shown in the inspector.
One connector, four imports. Each source location stays inspectable.Pinned to Hono 52f6c7e →
Start with your repository

Paste or choose. Start exploring.

Paste a public TypeScript URL or choose a private local folder. The same source-backed map works in your browser, with no project upload.

Public GitHub repositoryNo account · No install

Paste a GitHub URL or owner/repository. The map opens here; no account or install needed.

Public URL or private local folder · TypeScript · up to 1,200 files · 25 MB total · 1 MB per file

Try a sample
Pinned source snapshots

Browse the examples.

Three real projects, analyzed at fixed commits so the module counts and source evidence are reproducible.

ZustandWorkspace packages and boundaries18 modules · 24 connectionsOpen map ↗ KyExternal packages and import sites51 modules · 93 connectionsOpen map ↗ HonoGuided entry paths, cycles, bundled imports247 modules · 676 connectionsOpen map ↗ RepoAtlas 1.10 → 2.0A real snapshot comparison with source links2 modules · 5 imports addedOpen HTML diff ↗
What you can check

A map with receipts.

Static evidence from the files in the repository. Runtime behavior stays out of scope.

Find a module, export, or import

Search the map by path, exported name, imported name, or local alias. Matching bindings and their source lines appear with each module.

Find your way in

Walk from a detected entry through each import, with the exact source line highlighted at every stop. Explore reachability, cycles, external packages, and change impact.

See project boundaries

Resolve declared npm, Yarn, and pnpm workspaces through package exports. Start with a ranked package overview, drill in, or inspect each contributing source line.

See active hotspots

Opt into a bounded Git history window to compare committed change activity across modules. RepoAtlas shows the period, per-file counts, and last changed date without assigning a quality or risk score.

Review architecture drift in pull requests

Generate a downloadable HTML diff from the base commit and PR revision. Changed modules trace back to detected entries through source-linked imports, alongside added or removed bindings and exports; the workflow needs read-only access. Explore an interactive sample.

Give coding agents grounded context

Connect over MCP to search modules, public exports, or imported names and aliases, or get bounded module evidence and an entry path. Results include exact source lines; analysis stays local.

Keep a snapshot in your README

Export a small, deterministic SVG card with module, entry-point, import, and cycle counts. A pinned workflow can propose refreshes as pull requests.

Start from a safe baseline

Run repoatlas init --with-workflow to create an editable starter policy, an architecture snapshot, and a read-only pull-request check. CI blocks new cycles or unreachable modules without failing on unchanged debt.

Keep it portable

Share one offline HTML map, an architecture diff, a boundary matrix, or enforced rules in GitHub Actions.

For coding agents

Architecture context with receipts.

Install the RepoAtlas skill in Codex or another supported agent, then connect the local MCP server for reusable, read-only architecture context. Agents can search module names, public exports, or imported names, then fetch imports, exports, and a detected-entry path together with `module_context`.

MCP setup and agent skill →
# Agent skill · no project files written
npx skills add maximilianfeix/repoatlas --skill repoatlas --agent codex --yes

# Local MCP process · read-only · no RepoAtlas credentials
npx --yes --package=github:maximilianfeix/repoatlas#v2.41.0 repoatlas-cli mcp /path/to/project
In your workflow

Review the shape of every change.

Build an architecture diff for a pull request, scan its module and import counts in the job summary, then follow each changed import to the exact base or head source line. Add a rule config to annotate violating import lines and files; the HTML artifact stays available if a rule fails. RepoAtlas needs read-only access.

See the complete GitHub Actions setup →
# .github/workflows/architecture.yml
- uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
- uses: maximilianfeix/repoatlas@v2.41.0
  with:
    compare-to: ${{ github.event.pull_request.base.sha }}
    check-config: repoatlas.config.json
    output: architecture-diff.html
    artifact-name: architecture-diff
Shareable by design

An architecture snapshot for the README.

Build a static card from the same evidence as the interactive map. It has no scripts, tracking, or remote requests.

repoatlas-cli https://github.com/owner/repo --activity-days 90 --out activity-map.html
repoatlas-cli https://github.com/owner/repo --json > architecture.json
repoatlas-cli report architecture.json --format card \
  --output docs/architecture.svg