lizardbyte/sunshine · Architecture
A static read of how lizardbyte/sunshine 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
9
Modules parsed
4 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.
- src_assets/common/assets/web/locale.js1 importers · radius 1
- src_assets/common/assets/web/Notification.vue1 importers · radius 1
- src_assets/common/assets/web/sunshine.css1 importers · radius 1
- src_assets/common/assets/web/public/assets/locale/en.json1 importers · radius 2
- src_assets/common/assets/web/init.js0 importers · radius 0
- src_assets/common/assets/web/fetch_utils.js0 importers · radius 0
Modules (1)
Source directories grouped from the import graph. Each links to a per-module page with its files and how it couples to the rest.
- src_assets/common/assets/web5 files · 3 in-degree
Ask AI about lizardbyte/sunshine
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.