Kotlin project · Cycle evidence
Detekt Architecture Report
This report uses Detekt's compiled Kotlin/JVM classes to show a whole-project architecture overview, nine cycle groups, compact hotspot diagnostics, and capped detailed registers in the Evidence Appendix.
- Report packages
- 67
- Dependency edges
- 198
- Cycle groups
- 9
- Chapters
- 4
- Report date
- 31 Jul 2026
Why we included this report
We selected Detekt as the Kotlin case because its build provides 2,328 compiled Kotlin/JVM classes across 32 production roots.
Its nine cycle groups let Cycle Evidence start with the all-cycles overview and then trace the exact package dependencies that keep each loop closed. Hotspot Risk follows with the packages where dependencies, exposed code, or tightly connected internals may make change harder to contain.
Selected evidence
- Global architecture model
- Architecture Overview, Cycle Evidence, and Hotspot Risk
- One diagram for each cycle group, with an extra view only when it adds relationships not already shown
- Short diagnostic lists that explain why each package or dependency was selected
- Evidence Appendix with at most 50 rows in each detailed register
Choose what you want to understand
If this is your first Architecture Report, start with Architecture Overview for the big picture. Then choose the question you care about; each description explains what that chapter will help you understand. Each link opens the chapter in the full report.
- 01 Architecture OverviewStart here to see how Detekt's compiled Kotlin code is divided into packages, how those packages connect, and where dependencies cluster or form loops.
-
02
Cycle EvidenceSee all nine dependency loops together, then trace each one through the packages and relationships that keep it closed.
To see how the same cycle evidence reads in a TypeScript project, open Vue Core's chapter. Compare Vue Core’s Cycle Evidence
- 03 Hotspot RiskFind packages where changes may spread widely, then see whether the pressure comes from incoming dependencies, exposed code, or tightly connected internals.
- 04 Evidence AppendixUse the capped package-metric and dependency registers when a deeper review or handoff needs more literal evidence than the short diagnostic lists.
What this report covers
- Source revision
- 5afa793bc4f24779b50738b5aeb60974e00d3cdf
- Licence
- Apache-2.0
- Language and evidence
- Kotlin · compiled JVM bytecode from 32 production roots
- Project scale
- 2,328 compiled classes
- Report contents
- Whole project + Cycle Evidence + Hotspot Risk + detailed evidence appendix
- Report date
- 31 July 2026
- AtlasArc version
- 1.0.0
How to use this case
Context here, evidence in the report
Use this page to understand the project snapshot and scope. Open the report to inspect the architecture chapters themselves.
View project sourceHow this example was prepared
-
Use the recorded source revision
Check out the Detekt revision linked on this page.
-
Build the production classes
Use Gradle 9.5.1 and JDK 21 to build the project.
-
Choose the project evidence
Select the 32 production roots containing the compiled Kotlin/JVM classes.
-
Choose the report chapters
Include Architecture Overview, Cycle Evidence, Hotspot Risk, and detailed evidence tables with a 50-row maximum.
Source and attribution
Open-source project. Pinned example.
Detekt is analyzed from the pinned source revision above under Apache-2.0 . The project name identifies the analyzed open-source snapshot; publication here does not imply affiliation with or endorsement by its maintainers.