quantumnous/new-api · Architecture
A static read of how quantumnous/new-api 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
400
Modules parsed
584 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/api_type.go208 importers · radius 208
- model/ability.go102 importers · radius 103
- constant/api_type.go79 importers · radius 225
- logger/logger.go42 importers · radius 57
- pkg/jsplugin/cli.go38 importers · radius 38
- i18n/i18n.go20 importers · radius 22
- dto/channel_constraints.go20 importers · radius 110
- relay/alpha_search_handler.go16 importers · radius 16
Modules (9)
Source directories grouped from the import graph. Each links to a per-module page with its files and how it couples to the rest.
- common9 files · 208 in-degree
- model24 files · 102 in-degree
- pkg/jsplugin9 files · 38 in-degree
- middleware23 files · 15 in-degree
- plugins8 files · 11 in-degree
- pkg/billingexpr7 files · 6 in-degree
- oauth6 files · 5 in-degree
- pkg/perf_metrics2 files · 3 in-degree
- controller94 files · 1 in-degree
Ask AI about quantumnous/new-api
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.