RepoPilot

canopy-network/canopy · Architecture

A static read of how canopy-network/canopy 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
400
Modules parsed
470 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.

  • lib/crypto/address.go58 importers · radius 74
  • lib/block.go53 importers · radius 54
  • cmd/rpc/web/explorer/src/lib/utils.ts29 importers · radius 49
  • cmd/rpc/web/explorer/src/hooks/useApi.ts21 importers · radius 28
  • cmd/rpc/web/explorer/src/components/AnimatedNumber.tsx16 importers · radius 32
  • fsm/account.go13 importers · radius 17
  • cmd/rpc/web/wallet/src/actions/fields/types.ts13 importers · radius 15
  • cmd/rpc/web/explorer/src/components/ui/badgeStyles.ts12 importers · radius 27

Modules (24)

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)

  • cmd/rpc/web/explorer/src/components/token-swaps/TokenSwapsPage.tsx to cmd/rpc/web/explorer/src/components/token-swaps/RecentSwapsTable.tsx to cmd/rpc/web/explorer/src/components/token-swaps/TokenSwapsPage.tsx

Ask AI about canopy-network/canopy

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.