9 problem cycle groups reported in this report scope.
Key Findings
NCCD is 1.17. Use it as a same-project dependency-shape baseline; inspect cycles and concrete paths before interpreting a change.
ARV and GRV describe JVM public-surface breadth: ARV 0.82, GRV 0.67. This surface is broad enough to inspect against package roles, marked public classes, and real callers.
No Safe Havens or repository governance records are active; all findings are treated as active structural findings.
Highest-Value Targets
- detekt-api.main:dev.detekt.apiNested cycle participant, fan-in 44 / fan-out 1, distance 0.69, visibility 0.94
- detekt-api.main:dev.detekt.api.internalNested cycle participant, fan-in 18 / fan-out 1, distance 0.55, visibility 1.00
- detekt-metrics.main:dev.detekt.metricsNested cycle participant, distance 0.75, visibility 0.94
- detekt-core.main:dev.detekt.coreNested cycle participant, fan-in 6 / fan-out 9, visibility 1.00
- detekt-tooling.main:dev.detekt.tooling.apiArchitectural cycle participant, fan-in 11 / fan-out 2, visibility 1.00
- 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.
- 9 problem cycle groups reported in this report scope.
- First package to inspect: detekt-api.main:dev.detekt.api (Nested cycle participant, fan-in 44 / fan-out 1, distance 0.69, visibility 0.94).
- Largest cycle group: Problem cycle 5 with 5 packages.
Evidence Summary
Same-project dependency-shape baseline; compare only on an equivalent analysis basis.
Unweighted average of package Relative Visibility; each package contributes equally.
Public JVM classes divided by all JVM classes across the graph.
Cycle clusters remain in the report scope.
Precise graph statistics remain available below so the report stays auditable.
| CCD | Cumulative Component Dependency | 451.00 |
|---|---|---|
| ACD | Average Component Dependency | 6.26 |
| RACD | Relative Average Component Dependency | 0.09 |
| NCCD | Normalized Cumulative Component Dependency | 1.17 |
| ARV | Average Relative Visibility | 0.82 |
| GRV | Global Relative Visibility | 0.67 |
Architecture Overview Focus
This profile reads the whole model first: cycle posture, highest inspection target, and any governance context that changes how warnings should be interpreted.
Start by comparing the cycle map with the cycle groups table.
Nested cycle participant, fan-in 44 / fan-out 1, distance 0.69, visibility 0.94
Safe Havens, exclusions, and repository governance shape which findings remain active warnings.
Report Basis
Structural Map
Topology, cycle-only topology, and Matrix figures show broad packages structure and cycle evidence from complementary angles.
How do packages and subsystems depend on each other in this report?
Which packages depend on which other packages?
Hierarchy & Size
Composition figures show how code size and packages are distributed through the selected scope.
Where is the analysed codebase concentrated across the package hierarchy?
How does the same hierarchy read as nested containment rather than radial depth?
Governance Summary
Metric Notes
CCD, ACD, RACD, and NCCD describe structural graph shape. Package tables include fan-in, fan-out, instability, and line count. Dependency scope: compiled JVM dependencies. ARV is the unweighted average of package Relative Visibility; GRV is public JVM classes divided by all JVM classes across the graph. They describe public-surface breadth, not actual reachability or a universal architecture-health target.