meolu/walle-web · Architecture
A static read of how meolu/walle-web is wired together — module coupling, layering, and circular dependencies — derived from its import graph.
A
Architecture grade
score 88/100
2
Import cycles
lower is better
136
Modules parsed
208 edges
96%
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.
- walle/service/extensions.py21 importers · radius 59
- walle/service/rbac/role.py18 importers · radius 61
- walle/model/user.py16 importers · radius 42
- walle/model/database.py14 importers · radius 56
- walle/api/api.py13 importers · radius 13
- tests/utils.py10 importers · radius 10
- tests/factories.py8 importers · radius 8
- walle/service/code.py8 importers · radius 63
Circular dependencies (2)
- walle/service/notice/__init__.py → walle/service/notice/dingding.py → walle/service/notice/__init__.py
- walle/service/notice/__init__.py → walle/service/notice/email.py → walle/service/notice/__init__.py
Ask AI about meolu/walle-web
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.