RepoPilot

theopfr/somo · Architecture

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

ArchitectureSecurity & risksDependenciesLicenseMaintenanceAlternativesVsFull analysis
A
Architecture grade
score 100/100
0
Import cycles
lower is better
16
Modules parsed
27 edges
100%
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.

  • src/schemas.rs8 importers · radius 8
  • src/utils.rs4 importers · radius 4
  • src/connections/common.rs3 importers · radius 4
  • src/config.rs2 importers · radius 2
  • src/markdown.rs2 importers · radius 2
  • src/services.rs2 importers · radius 2
  • src/connections/mod.rs1 importers · radius 1
  • src/view.rs1 importers · radius 1

Modules (2)

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 theopfr/somo

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

What does this repo do, in one paragraph?How would I get started using it?What are the main alternatives?Show me the entry point.
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.