orchardcms/orchardcore · Architecture
A static read of how orchardcms/orchardcore 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
12
Modules parsed
2 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/OrchardCore.Modules/OrchardCore.Apis.GraphQL/Assets/css/graphiql-orchard.css1 importers · radius 1
- src/OrchardCore.Modules/OrchardCore.AuditTrail/Assets/scss/styles.scss1 importers · radius 1
- src/OrchardCore.Modules/OrchardCore.Apis.GraphQL/Assets/js/App.tsx0 importers · radius 0
- src/OrchardCore.Modules/OrchardCore.AuditTrail/Assets/js/App.tsx0 importers · radius 0
Ask AI about orchardcms/orchardcore
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.