AtlasArc
Release notes Install free
All showcases

Kotlin-heavy · JVM evidence

Detekt Architecture Report

This report analyzes Detekt from 32 Kotlin/JVM production roots and 2,328 compiled classes. Headless export leaves IDE-only complexity metrics unavailable instead of zero-filling them.

Open generated report Printable Version
Report packages
67
Dependency edges
198
Cycle groups
9
Chapters
3
Generation
21.519 s
Case brief

Why this report

Detekt uses Kotlin/JVM bytecode-backed dependency evidence from compiled classes—the same JVM acquisition path as Java, with no separate Kotlin source parser.

The standard global composition supplies the common Architecture Overview, dedicated cycle evidence for nine report-model groups, and Hotspot Risk without adding focused or governance sections that this case does not need.

Selected evidence

  • Global architecture model
  • Architecture Overview, Cycle Evidence, and Hotspot Risk
  • One compact map per SCC; an additional map only when its focused node-and-edge evidence is a strict superset
  • Top 100 table rows
Generated contents

Read the evidence

The report index is the canonical entry point. These direct chapter links expose the generated reading order without copying or rewriting its findings here.

  1. 01 Architecture OverviewWhole-model basis, structure, signals, and shared orientation for the Kotlin/JVM project.
  2. 02 Cycle EvidenceThe nine report-model cycle groups with their generated maps and dependency evidence.

    To see how the same cycle evidence reads in a TypeScript project, open Vue Core's chapter. Compare Vue Core’s Cycle Evidence

  3. 03 Hotspot RiskBoundary Risk, Visibility Surface, and Internal Tangles subsystem diagrams; Coupling, Visibility, and Abstractness / Instability hotspot rankings; package metrics.
Start at report index Open Printable Version
Pinned provenance

Analysis basis and integrity

Source revision
5afa793bc4f24779b50738b5aeb60974e00d3cdf
Licence
Apache-2.0
Analysis source
Kotlin/JVM bytecode from 32 production roots and 2,328 compiled classes
Build verification
Gradle build -x dokkaGenerate passed · 318 actionable tasks
Report selection
Global architecture, compact SCC maps with strict-evidence additional maps, top 100
Generated
2026-07-31T22:45:00Z
Generator
AtlasArc 1.0.1+736db9b9
Output
5 HTML files · 3,302,495 bytes
Portable folder SHA-256
0dc424af2eafebfc379f761ddf1505133e15b74b078538a427f01f3beb8142ea
Structural SHA-256
ac5ca689e9fe82ee2c47bc58a846374533ed4aa17247fbac7119967e1fe8ea93
Generation time
21.519 seconds

Output contract

Generated HTML is unchanged

The report folder is published byte-for-byte. This page supplies context and attribution outside that generated output.

Open pinned source revision
Reproduce the analysis basis

  1. Pin the source

    Check out the recorded Detekt revision. The definitive generation checkout retained only its pre-existing untracked tmp directory.

  2. Use the workstation trust store when required

    On the Norton-inspected Windows generation workstation, keep TLS verification enabled and route Gradle/JVM trust through the native Windows root store.

    $env:JAVA_TOOL_OPTIONS='-Djavax.net.ssl.trustStore=NONE -Djavax.net.ssl.trustStoreType=Windows-ROOT'

  3. Run the verified build contract

    Build the production outputs with the recorded Gradle and JDK versions.

    .\gradlew.bat build -x dokkaGenerate

  4. Load compiled Kotlin/JVM output

    Select the 32 production roots as the bytecode-backed Analysis Source, then choose the standard global report with additional cycle maps and top 100 rows. An additional map is emitted only when its focused node-and-edge evidence strictly extends the compact map.

  5. Verify the output

    Generate with AtlasArc 1.0.1+736db9b9 and compare the folder and structural SHA-256 values above.

Read with care

Caveats and safeguards

  • The Printable Version keeps its place

    A colour-coded report route stays in the spare margin on wide screens, follows the current chapter, and prints once beneath the dossier header. It is deliberately absent from standalone chapter files.

  • Headless JVM metric boundary

    IntelliJ PSI cyclomatic and cognitive complexity are unavailable in the headless acquisition path and are omitted instead of zero-filled.

  • The matrix guard is visible

    The overview and Printable Version carry an explicit guard notice for the 167-unit rendered matrix. The report retains its topology, cycles, rankings, and other selected evidence.

  • PKIX was environmental

    Norton HTTPS inspection re-signed Maven Central traffic on the generation workstation. The successful build used Windows-ROOT trust; TLS verification was not disabled and the failure was not attributed to Detekt.

  • Windows path controls

    No-space temporary and Gradle-cache aliases prevented upstream Kotlin Analysis API tasks from treating an encoded user-profile path as a literal filesystem path.

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.

Read the report contract Compare all showcases