mrs4s/go-cqhttp · Architecture
A static read of how mrs4s/go-cqhttp is wired together — module coupling, layering, and circular dependencies — derived from its import graph.
A
Architecture grade
score 99/100
0
Import cycles
lower is better
86
Modules parsed
112 edges
98%
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.
- global/buffer.go21 importers · radius 29
- internal/base/feature.go18 importers · radius 30
- coolq/api.go9 importers · radius 11
- internal/download/download.go9 importers · radius 19
- db/database.go9 importers · radius 19
- pkg/onebot/attr.go8 importers · radius 14
- modules/config/config.go6 importers · radius 7
- modules/api/api.go4 importers · radius 4
Modules (11)
Source directories grouped from the import graph. Each links to a per-module page with its files and how it couples to the rest.
- global4 files · 21 in-degree
- internal/base2 files · 18 in-degree
- coolq7 files · 9 in-degree
- db2 files · 9 in-degree
- modules/api2 files · 4 in-degree
- global/terminal3 files · 2 in-degree
- server6 files · 1 in-degree
- db/leveldb5 files · 1 in-degree
- cmd/gocq3 files · 1 in-degree
- modules/silk2 files · 1 in-degree
- db/sqlite32 files · 1 in-degree
Ask AI about mrs4s/go-cqhttp
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 questionInformational only. RepoPilot summarises public signals at the time of analysis; they can be incomplete or stale. Not professional, security, or legal advice.