halfrost/leetcode-go · Architecture
A static read of how halfrost/leetcode-go is wired together — module coupling, layering, and circular dependencies — derived from its import graph.
A
Architecture grade
score 100/100
0
Import cycles
lower is better
274
Modules parsed
9 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.
- ctl/util/util.go6 importers · radius 6
- ctl/models/lcproblems.go3 importers · radius 3
- ctl/render.go0 importers · radius 0
- ctl/statistic.go0 importers · radius 0
- ctl/template_render.go0 importers · radius 0
- ctl/label.go0 importers · radius 0
- ctl/models/tagproblem.go0 importers · radius 0
- ctl/pdf.go0 importers · radius 0
Ask AI about halfrost/leetcode-go
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.