RepoPilot

ruvnet/ruview · Architecture

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

A
Architecture grade
score 94/100
1
Import cycles
lower is better
276
Modules parsed
155 edges
97%
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.

  • dashboard/src/store/appStore.ts12 importers · radius 14
  • harness/ruview/src/tools.js7 importers · radius 7
  • dashboard/src/transport/NvsimClient.ts6 importers · radius 18
  • harness/homecore/src/repo-trust.js6 importers · radius 10
  • harness/homecore/src/process-runner.js4 importers · radius 10
  • harness/ruview/src/process-runner.js4 importers · radius 13
  • harness/homecore/src/brain.js4 importers · radius 9
  • harness/homecore/src/kernel.js4 importers · radius 7

Modules (20)

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

Circular dependencies (1)

  • dashboard/src/components/nv-app.ts to dashboard/src/components/nv-rail.ts to dashboard/src/components/nv-app.ts

Ask AI about ruvnet/ruview

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.