RepoPilot

usefathom/fathom · Architecture

A static read of how usefathom/fathom is wired together — module coupling, layering, and circular dependencies — derived from its import graph.

A
Architecture grade
score 99/100
0
Import cycles
lower is better
71
Modules parsed
56 edges
98%
Layeredness
clean-layer ratio

Most-depended-on modules

These are the highest-fan-in files — change them and the blast radius is largest. Read them first.

  • pkg/models/page_stats.go12 importers · radius 17
  • assets/src/js/lib/client.js9 importers · radius 10
  • pkg/datastore/datastore.go7 importers · radius 9
  • assets/src/js/lib/numbers.js4 importers · radius 7
  • assets/src/js/lib/util.js3 importers · radius 4
  • pkg/datastore/sqlstore/config.go2 importers · radius 11
  • assets/src/js/pages/dashboard.js1 importers · radius 1
  • pkg/aggregator/aggregator.go1 importers · radius 1

Modules (7)

Source directories grouped from the import graph. Each links to a per-module page with its files and how it couples to the rest.

Ask AI about usefathom/fathom

Grounded in the actual source code. Pick a starter question or write your own.

Or write your own question

Informational only. RepoPilot summarises public signals at the time of analysis; they can be incomplete or stale. Not professional, security, or legal advice.