xiaomi/soar · Architecture

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

Architecture Security & risks Dependencies License Maintenance Alternatives Vs Full analysis

Architecture grade

score 100/100

Import cycles

lower is better

Modules parsed

60 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.

common/cases.go38 importers · radius 38
database/doc.go8 importers · radius 8
ast/doc.go7 importers · radius 7
env/doc.go5 importers · radius 5
advisor/doc.go2 importers · radius 2
cmd/soar/soar.go0 importers · radius 0
cmd/soar/tool.go0 importers · radius 0
advisor/index.go0 importers · radius 0

Modules (5)

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

database14 files · 8 in-degree
ast13 files · 7 in-degree
env3 files · 5 in-degree
advisor9 files · 2 in-degree
cmd/soar3 files · 0 in-degree

Ask AI about xiaomi/soar

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.