8 problem cycle groups reported in this report scope.
Key Findings
NCCD is 1.50. Use it as a same-project dependency-shape baseline; inspect cycles and concrete paths before interpreting a change.
JVM public-surface metrics are not available for this analysis.
No Safe Havens or repository governance records are active; all findings are treated as active structural findings.
Source Folders Worth a Closer Look
Each one stood out for more than one independent reason in this report.
- packages.shared.srcStood out for 2 independent reasons: unusually depended on while relying on relatively little (Fan-in 25, Instability 0.04); part of Problem cycle 4 (architectural cycle).
- The report reads package structure and dependency evidence; it does not know what the code is meant to do.
- Coverage metrics are not loaded, so coverage-dependent risk readings are unavailable.
- Package exclusions are disabled for this report context.
What This Report Says
Read this report as cycle-first evidence: resolve or consciously accept the reported cycle groups before treating lower-level metrics as optimization work.
- 8 problem cycle groups reported in this report scope.
- Worth a closer look: packages.shared.src stood out for 2 independent reasons (unusually depended on while relying on relatively little (Fan-in 25, Instability 0.04); part of Problem cycle 4 (architectural cycle)).
- Largest cycle group: Problem cycle 5 with 4 source folders.
Evidence Summary
Same-project dependency-shape baseline; compare only on an equivalent analysis basis.
Cycle clusters remain in the report scope.
Precise graph statistics remain available below so the report stays auditable.
| CCD | Cumulative Component Dependency | 231.00 |
|---|---|---|
| ACD | Average Component Dependency | 7.45 |
| RACD | Relative Average Component Dependency | 0.25 |
| NCCD | Normalized Cumulative Component Dependency | 1.50 |
| ARV | Average Relative Visibility | n/a |
| GRV | Global Relative Visibility | n/a |
Architecture Overview Focus
This profile reads the whole model first: cycle posture, architecture units that stood out for more than one strict reason, and any governance context that changes how warnings should be interpreted.
Start by comparing the cycle map with the cycle groups table.
Stood out for 2 independent reasons: unusually depended on while relying on relatively little (Fan-in 25, Instability 0.04); part of Problem cycle 4 (architectural cycle).
Safe Havens, exclusions, and repository governance shape which findings remain active warnings.
Suggested Next Steps
4 source folders participate in this architectural cycle group. Use the cycle table and topology figure to decide whether to break the loop or record an explicit governance decision.
This source folder stood out in more than one part of the report. Stood out for 2 independent reasons: unusually depended on while relying on relatively little (Fan-in 25, Instability 0.04); part of Problem cycle 4 (architectural cycle).
Report Basis
Structural Map
Topology, cycle-only topology, and Matrix figures show broad source folders structure and cycle evidence from complementary angles.
How do source folders and subsystems depend on each other in this report?
- Focus
- project root
- Filter
- All visible source folders
- Heatmap
- Off
- Nodes
- Source Folders and grouping folders
- Edges
- Source Folder dependencies; line width follows dependency weight
- Border colour
- Cycle, Safe Haven, intentional governance, and debt status from the model
Which source folders depend on which other source folders?
- Focus
- project root
- Filter
- All visible source folders
- Heatmap
- Off
- Report Matrix
- 46 origin rows (ceiling 50)
- Target columns
- 25 carrying dependencies · 2 empty restored · 19 empty omitted
- Problem cycles
- 8 of 8 kept at exact package detail
- Printable scale
- Estimated 100%
- Rollup safeguard
- Use less package detail below 55%
- Rows
- Origin source folders
- Columns
- Target source folders
- Cells
- source file dependency count and cycle/heatmap styling where applicable
- Every origin row remains visible. After preserving dependency-bearing targets, AtlasArc returned as many empty target columns as fit at natural size.
|
arc-templates
|
dist
|
packages
|
compiler-core
|
src
|
compat
|
transforms
|
compiler-dom
|
src
|
transforms
|
compiler-sfc
|
src
|
script
|
style
|
template
|
compiler-ssr
|
src
|
transforms
|
reactivity
|
src
|
runtime-core
|
src
|
compat
|
components
|
helpers
|
runtime-dom
|
src
|
components
|
directives
|
helpers
|
modules
|
runtime-test
|
src
|
server-renderer
|
src
|
helpers
|
shared
|
src
|
vue
|
vue-compat
|
src
|
src
|
react-dom
|
teacup
|
lib
|
vue-core
|
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ▼ arc-templates | - | |||||||||||||||||||||||||||||||||||||||||||||
| dist | - | |||||||||||||||||||||||||||||||||||||||||||||
| ▼ packages | - | |||||||||||||||||||||||||||||||||||||||||||||
| ▼ compiler-core | - | |||||||||||||||||||||||||||||||||||||||||||||
| ▼ src | - | 3 | 26 | 7 | ||||||||||||||||||||||||||||||||||||||||||
| compat | 3 | - | ||||||||||||||||||||||||||||||||||||||||||||
| transforms | 61 | 1 | - | 12 | ||||||||||||||||||||||||||||||||||||||||||
| ▼ compiler-dom | - | |||||||||||||||||||||||||||||||||||||||||||||
| ▼ src | 4 | - | 10 | 2 | ||||||||||||||||||||||||||||||||||||||||||
| transforms | 9 | 11 | - | 3 | ||||||||||||||||||||||||||||||||||||||||||
| ▼ compiler-sfc | - | |||||||||||||||||||||||||||||||||||||||||||||
| ▼ src | 3 | 4 | - | 18 | 7 | 2 | 1 | 3 | ||||||||||||||||||||||||||||||||||||||
| script | 6 | 5 | - | 1 | 4 | 3 | ||||||||||||||||||||||||||||||||||||||||
| style | 1 | 1 | - | 2 | ||||||||||||||||||||||||||||||||||||||||||
| template | 2 | - | 2 | 3 | ||||||||||||||||||||||||||||||||||||||||||
| ▼ compiler-ssr | - | |||||||||||||||||||||||||||||||||||||||||||||
| ▼ src | 4 | - | 14 | 1 | ||||||||||||||||||||||||||||||||||||||||||
| transforms | 13 | 19 | - | 2 | ||||||||||||||||||||||||||||||||||||||||||
| ▼ reactivity | - | |||||||||||||||||||||||||||||||||||||||||||||
| src | - | 8 | ||||||||||||||||||||||||||||||||||||||||||||
| ▼ runtime-core | - | |||||||||||||||||||||||||||||||||||||||||||||
| ▼ src | 19 | - | 20 | 16 | 17 | 28 | ||||||||||||||||||||||||||||||||||||||||
| compat | 2 | 26 | - | 6 | 15 | |||||||||||||||||||||||||||||||||||||||||
| components | 1 | 27 | - | 1 | 4 | |||||||||||||||||||||||||||||||||||||||||
| helpers | 3 | 19 | - | 8 | ||||||||||||||||||||||||||||||||||||||||||
| ▼ runtime-dom | - | |||||||||||||||||||||||||||||||||||||||||||||
| ▼ src | 3 | - | 2 | 3 | 2 | 5 | 3 | |||||||||||||||||||||||||||||||||||||||
| components | 2 | - | 1 | 2 | ||||||||||||||||||||||||||||||||||||||||||
| directives | 2 | - | 1 | 2 | ||||||||||||||||||||||||||||||||||||||||||
| helpers | 2 | - | 2 | |||||||||||||||||||||||||||||||||||||||||||
| modules | 4 | 1 | 1 | 1 | 1 | - | 4 | |||||||||||||||||||||||||||||||||||||||
| ▼ runtime-test | - | |||||||||||||||||||||||||||||||||||||||||||||
| src | 1 | 1 | - | 4 | ||||||||||||||||||||||||||||||||||||||||||
| ▼ server-renderer | - | |||||||||||||||||||||||||||||||||||||||||||||
| ▼ src | 4 | - | 12 | 4 | 1 | |||||||||||||||||||||||||||||||||||||||||
| helpers | 1 | 6 | 4 | - | 7 | |||||||||||||||||||||||||||||||||||||||||
| ▼ shared | - | |||||||||||||||||||||||||||||||||||||||||||||
| src | 1 | - | ||||||||||||||||||||||||||||||||||||||||||||
| ▼ vue | - | |||||||||||||||||||||||||||||||||||||||||||||
| ▼ vue-compat | - | |||||||||||||||||||||||||||||||||||||||||||||
| src | 1 | 1 | 1 | 5 | 2 | - | ||||||||||||||||||||||||||||||||||||||||
| src | 1 | 3 | 1 | - | ||||||||||||||||||||||||||||||||||||||||||
| react-dom | - | |||||||||||||||||||||||||||||||||||||||||||||
| ▼ teacup | - | |||||||||||||||||||||||||||||||||||||||||||||
| lib | - | |||||||||||||||||||||||||||||||||||||||||||||
| vue-core | - |
Hierarchy & Size
Composition figures show how code size and source folders are distributed through the selected scope.
Where is the analysed codebase concentrated across the source folder hierarchy?
- Focus
- project root
- View
- Sunburst
- Size metric
- Lines of code
- Heatmap
- Off
- Arc
- Source Folder hierarchy segment
- Arc size
- Relative lines of code
- Colour
- Hierarchy depth
How does the same hierarchy read as nested containment rather than radial depth?
- Focus
- project root
- View
- Circle Pack
- Size metric
- Lines of code
- Heatmap
- Off
- Circle
- Source Folder hierarchy segment
- Area
- Relative lines of code
- Colour
- Hierarchy depth
Governance Summary
Metric Notes
CCD, ACD, RACD, and NCCD describe structural graph shape. Source Folder diagnostics use fan-in, fan-out, instability, and line count. Dependency scope: source architecture dependencies. Type-only imports are included as source coupling. This analysis did not provide abstractness, arv, distance, grv, relativeVisibility; AtlasArc omits those metrics rather than treating them as zero.