Your codebase, as a living map.
Every file, directory and module re-forge scanned · laid out by how they depend on each other. By default nodes are heat-coloured by how recently they changed and sized by commit churn, so hotspots and where the team is working jump out; toggle to Module colour anytime. Hover for path, last author and recency. Structure + git metadata only · never your source.
A scan reads the repo on your machine · the dashboard can't reach your working tree, so nothing here starts one. Run reforge scan inside the repo (or let the repo-graph GitHub Action run on push), then check below · the new graph lands within seconds of the scan finishing.
drag to pan · scroll to zoom
Tenant-isolated by Postgres RLS · you only ever see your own org's graph. The graph stores structure only (paths, kinds, languages, line counts and import/contains edges); your source code is never sent or stored. Read through the dashboard's token-scoped proxy to the ingest /v1/repo-graph endpoint.