Executive summary
Kotlin/dokka is rated At risk because critical security findings are open, most of them in the build pipeline. Its score is held back in part because it has buttons or links with no name. It scores 41 out of 100, which the At risk rating leaves unchanged.
Accessibility, at 28, is the weakest lens and counts most in the score. The best first step is making the controls keyboard-usable, worth about 6 points. Labelling the form fields and buttons comes next, worth about 4 points. Raising Accessibility to 70 would lift the score to about 51.
Sixty-five pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Thirty-four known security holes in the packages the code depends on can be used by attackers, and seventeen secrets can leak from the build pipeline. Pinning each tool to an exact version, updating the vulnerable packages and limiting each secret to its own step would close these risks. The ten buttons or links with no name need a name, even when they only show an icon.
The product code is 44,953 lines, about €98,000 to rebuild.
If Accessibility rose from 28 to 70, the lowest score rated Strong, the score would rise from 41 to about 51.
New since the last survey: 117 findings
- Code Duplication · Edited copy of a member (66 corresponding lines) dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/transformers/documentables/DocumentableReplacerTransformer.kt
- Code Duplication · Edited copy of a member (46 corresponding lines) dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/signatures/KotlinSignatureProvider.kt
- Code Duplication · Edited copy of a member (22 corresponding lines) dokka-subprojects/core/src/main/kotlin/org/jetbrains/dokka/pages/utils.kt
- Code Duplication · Edited copy of a member (32 corresponding lines) dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/renderers/DefaultRenderer.kt
- Code Duplication · Edited copy of a member (24 corresponding lines) dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/translators/documentables/PageContentBuilder.kt
- Code Duplication · Edited copy of a member (22 corresponding lines) dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/transformers/pages/DefaultSamplesTransformer.kt
- Code Duplication · Edited copy of a member (15 corresponding lines) dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/transformers/documentables/DocumentableReplacerTransformer.kt
- Code Duplication · Edited copies of one member (3 members, 14+ corresponding lines) dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/transformers/documentables/DocumentableReplacerTransformer.kt
- Code Duplication · Edited copy of a member (15 corresponding lines) dokka-subprojects/plugin-kotlin-as-java/src/main/kotlin/org/jetbrains/dokka/kotlinAsJava/converters/KotlinToJavaConverter.kt
- Code Duplication · Edited copy of a member (13 corresponding lines) dokka-runners/dokka-gradle-plugin/src/classicMain/kotlin/tasks/DokkaTask.kt
- Code Duplication · Edited copy of a member (13 corresponding lines) dokka-subprojects/analysis-kotlin-symbols/src/main/kotlin/org/jetbrains/dokka/analysis/kotlin/symbols/services/SymbolFullClassHierarchyBuilder.kt
- Code Duplication · Edited copy of a member (12 corresponding lines) dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/transformers/documentables/DocumentableVisibilityFilterTransformer.kt
- Code Duplication · Edited copy of a member (16 corresponding lines) dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/transformers/pages/DefaultSamplesTransformer.kt
- Code Duplication · Edited copy of a member (18 corresponding lines) dokka-subprojects/core/src/main/kotlin/org/jetbrains/dokka/model/Documentable.kt
- Code Duplication · Edited copy of a member (6 corresponding lines) dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/transformers/documentables/DocumentableReplacerTransformer.kt
- Code Duplication · Edited copies of one member (4 members, 16+ corresponding lines) dokka-subprojects/core/src/main/kotlin/org/jetbrains/dokka/model/Documentable.kt
- Code Duplication · Edited copies of one member (3 members, 8+ corresponding lines) dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/transformers/documentables/DocumentableReplacerTransformer.kt
- Code Duplication · Edited copy of a member (6 corresponding lines) dokka-subprojects/analysis-java-psi/src/main/kotlin/org/jetbrains/dokka/analysis/java/util/CoreCopyPaste.kt
- Code Duplication · Edited copy of a member (10 corresponding lines) dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/signatures/KotlinSignatureProvider.kt
- Code Duplication · Edited copy of a member (10 corresponding lines) dokka-subprojects/plugin-javadoc/src/main/kotlin/org/jetbrains/dokka/javadoc/signatures/JavadocSignatureProvider.kt
- Code Duplication · Edited copy of a member (7 corresponding lines) dokka-subprojects/analysis-kotlin-symbols/src/main/kotlin/org/jetbrains/dokka/analysis/kotlin/symbols/translators/AnnotationTranslator.kt
- Code Duplication · Edited copy of a member (9 corresponding lines) dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/renderers/DefaultRenderer.kt
- Code Duplication · Edited copy of a member (8 corresponding lines) dokka-subprojects/plugin-kotlin-as-java/src/main/kotlin/org/jetbrains/dokka/kotlinAsJava/jvmOverloads.kt
- Code Duplication · Edited copy of a member (8 corresponding lines) dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/transformers/documentables/EmptyPackagesFilterTransformer.kt
- Code Duplication · Edited copy of a member (8 corresponding lines) dokka-subprojects/analysis-kotlin-symbols/src/main/kotlin/org/jetbrains/dokka/analysis/kotlin/symbols/services/KotlinDocumentableSourceLanguageParser.kt
- Code Duplication · Edited copy of a member (5 corresponding lines) dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/signatures/KotlinSignatureUtils.kt
- Code Duplication · Edited copy of a member (2 corresponding lines) dokka-subprojects/core/src/main/kotlin/org/jetbrains/dokka/pages/PageNodes.kt
- Code Duplication · Edited copy of a member (1 corresponding lines) dokka-subprojects/core/src/main/kotlin/org/jetbrains/dokka/pages/PageNodes.kt
- Code Duplication · Edited copy of a member (3 corresponding lines) dokka-subprojects/analysis-java-psi/src/main/kotlin/org/jetbrains/dokka/analysis/java/parsers/DokkaPsiParser.kt
- Code Duplication · Edited copies of one member (3 members, 10+ corresponding lines) dokka-subprojects/analysis-java-psi/src/main/kotlin/org/jetbrains/dokka/analysis/java/doccomment/JavaDocComment.kt
- Code Duplication · Edited copy of a member (5 corresponding lines) dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/transformers/documentables/DeprecatedDocumentableFilterTransformer.kt
- Code Duplication · Edited copy of a member (4 corresponding lines) dokka-subprojects/plugin-kotlin-playground-samples/src/main/kotlin/org/jetbrains/dokka/kotlinPlaygroundSamples/KotlinPlaygroundSamplesInstaller.kt
- Code Duplication · Edited copy of a member (5 corresponding lines) dokka-subprojects/core/src/main/kotlin/org/jetbrains/dokka/model/Documentable.kt
- Code Duplication · Duplicated block (21 lines × 2) dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/renderers/DefaultRenderer.kt
- Code Duplication · Duplicated block (21 lines × 2) dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/signatures/KotlinSignatureProvider.kt
- Code Duplication · Duplicated block (16–17 lines × 2) dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/transformers/pages/DefaultSamplesTransformer.kt
- Code Duplication · Duplicated block (15 lines × 2) dokka-subprojects/core/src/main/kotlin/org/jetbrains/dokka/model/Documentable.kt
- Code Duplication · Duplicated block (15 lines × 2) dokka-subprojects/core/src/main/kotlin/org/jetbrains/dokka/model/Documentable.kt
- Code Duplication · Duplicated block (15 lines × 2) dokka-subprojects/core/src/main/kotlin/org/jetbrains/dokka/model/Documentable.kt
- Code Duplication · Duplicated block (7–13 lines × 3) dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/transformers/documentables/DocumentableVisibilityFilterTransformer.kt
- Code Duplication · Duplicated block (13 lines × 2) dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/transformers/pages/DefaultSamplesTransformer.kt
- Code Duplication · Duplicated block (11–12 lines × 2) dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/transformers/documentables/SuppressedByConditionDocumentableFilterTransformer.kt
- Code Duplication · Duplicated block (25 lines × 2) dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/transformers/pages/DefaultSamplesTransformer.kt
- Code Duplication · Duplicated block (11 lines × 4) dokka-subprojects/analysis-kotlin-symbols/src/main/kotlin/org/jetbrains/dokka/analysis/kotlin/symbols/translators/DefaultSymbolToDocumentableTranslator.kt
- Code Duplication · Duplicated block (11 lines × 2) dokka-runners/dokka-gradle-plugin/src/main/kotlin/tasks/DokkaGenerateTask.kt
- Code Duplication · Duplicated block (11 lines × 2) dokka-subprojects/analysis-java-psi/src/main/kotlin/org/jetbrains/dokka/analysis/java/util/PsiUtil.kt
- Code Duplication · Duplicated block (10 lines × 2) dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/signatures/KotlinSignatureProvider.kt
- Code Duplication · Duplicated block (8–9 lines × 3) dokka-subprojects/analysis-kotlin-symbols/src/main/kotlin/org/jetbrains/dokka/analysis/kotlin/symbols/translators/DefaultSymbolToDocumentableTranslator.kt
- Code Duplication · Duplicated block (7 lines × 3) dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/transformers/documentables/DocumentableReplacerTransformer.kt
- Code Duplication · Duplicated block (7 lines × 2) dokka-subprojects/core/src/main/kotlin/org/jetbrains/dokka/transformers/documentation/DefaultDocumentableMerger.kt
- Code Duplication · Duplicated block (7 lines × 2) dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/transformers/documentables/DocumentableReplacerTransformer.kt
- Code Duplication · Duplicated block (6 lines × 3) dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/transformers/documentables/SuppressedByConditionDocumentableFilterTransformer.kt
- Code Duplication · Duplicated block (7 lines × 2) dokka-subprojects/core/src/main/kotlin/org/jetbrains/dokka/transformers/documentation/DefaultDocumentableMerger.kt
- Code Duplication · Duplicated block (5 lines × 4) dokka-subprojects/analysis-kotlin-symbols/src/main/kotlin/org/jetbrains/dokka/analysis/kotlin/symbols/translators/DefaultSymbolToDocumentableTranslator.kt
- Code Duplication · Duplicated block (5 lines × 4) dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/transformers/documentables/DocumentableReplacerTransformer.kt
- Code Duplication · Duplicated block (5 lines × 4) dokka-subprojects/plugin-kotlin-as-java/src/main/kotlin/org/jetbrains/dokka/kotlinAsJava/transformers/JvmNameDocumentableTransformer.kt
- Code Duplication · Duplicated block (5 lines × 3) dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/transformers/documentables/SuppressedByConditionDocumentableFilterTransformer.kt
- Code Duplication · Duplicated block (5 lines × 2) dokka-subprojects/analysis-kotlin-symbols/src/main/kotlin/org/jetbrains/dokka/analysis/kotlin/symbols/translators/DefaultSymbolToDocumentableTranslator.kt
- Code Duplication · Duplicated block (2–5 lines × 7) dokka-subprojects/core/src/main/kotlin/org/jetbrains/dokka/transformers/documentation/DefaultDocumentableMerger.kt
- Code Duplication · Duplicated block (5 lines × 2) dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/transformers/documentables/DocumentableReplacerTransformer.kt
- Code Duplication · Duplicated block (5 lines × 2) dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/transformers/documentables/DocumentableReplacerTransformer.kt
- Code Duplication · Duplicated block (9 lines × 4) dokka-subprojects/analysis-java-psi/src/main/kotlin/org/jetbrains/dokka/analysis/java/util/StdlibUtil.kt
- Code Duplication · Duplicated block (11 lines × 2) dokka-subprojects/plugin-all-modules-page/src/main/kotlin/org/jetbrains/dokka/allModulesPage/AllModulesPageGeneration.kt
- Code Duplication · Duplicated block (8 lines × 2) dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/renderers/html/htmlPreprocessors.kt
- Code Duplication · Duplicated block (6 lines × 4) dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/transformers/pages/annotations/SinceKotlinTransformer.kt
- Code Duplication · Edited copy of a member (11 corresponding lines) dokka-subprojects/core-test-api/src/main/kotlin/org/jetbrains/dokka/testApi/configuration.kt
- Code Duplication · Duplicated block (5 lines × 2) dokka-subprojects/plugin-javadoc/src/main/kotlin/org/jetbrains/dokka/javadoc/signatures/JavadocSignatureProvider.kt
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Cyclomatic Complexity · Complex function resize (cyclomatic 19, cognitive 24) REDACTED
- Cyclomatic Complexity · Complex function _setOption (cyclomatic 19, cognitive 23) REDACTED
- Cyclomatic Complexity · Complex function _setContainment (cyclomatic 19, cognitive 22) REDACTED
- Cyclomatic Complexity · Complex function _setContainment (cyclomatic 19, cognitive 18) REDACTED
- Cyclomatic Complexity · Complex function _refreshValue (cyclomatic 18, cognitive 33) REDACTED
- Cyclomatic Complexity · Complex function _optionDatepicker (cyclomatic 18, cognitive 25) REDACTED
- Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 18, cognitive 22) REDACTED
- Cyclomatic Complexity · Complex function _mouseMove (cyclomatic 18, cognitive 20) REDACTED
- Cyclomatic Complexity · Complex function keydown (cyclomatic 18, cognitive 13) REDACTED
- Cyclomatic Complexity · Complex function _hideDatepicker (cyclomatic 17, cognitive 33) REDACTED
- Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 17, cognitive 17) REDACTED
- Cyclomatic Complexity · Complex function _eventHandler (cyclomatic 17, cognitive 15) REDACTED
- Cyclomatic Complexity · Complex function set (cyclomatic 16, cognitive 24) REDACTED
- Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 16, cognitive 18) REDACTED
- Cyclomatic Complexity · Complex function _setOption (cyclomatic 16, cognitive 13) REDACTED
- Cyclomatic Complexity · Complex function _intersectsWith (cyclomatic 15, cognitive 17) REDACTED
- Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 15, cognitive 14) REDACTED
- Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 15, cognitive 14) REDACTED
- Cyclomatic Complexity · Complex function _checkOffset (cyclomatic 14, cognitive 13) REDACTED
- Cyclomatic Complexity · Complex function _animate (cyclomatic 14, cognitive 11) REDACTED
- Exception handling · Swallowed exception (empty catch) REDACTED
- Exception handling · Swallowed exception (empty catch) REDACTED
- Exception handling · Swallowed exception (empty catch) REDACTED
- Exception handling · Swallowed exception (empty catch) REDACTED
- Exception handling · Swallowed exception (empty catch) REDACTED
- Exception handling · Swallowed exception (empty catch) REDACTED
- Exception handling · Swallowed exception (empty catch) REDACTED
- Exception handling · Swallowed exception (empty catch) dokka-subprojects/plugin-javadoc/src/main/resources/static_res/jquery/external/jquery/jquery.js
Fixed since the last survey: 67 findings
- Code Duplication · Duplicated block (21 lines × 2) dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/renderers/DefaultRenderer.kt
- Code Duplication · Duplicated block (16–17 lines × 2) dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/transformers/pages/DefaultSamplesTransformer.kt
- Code Duplication · Duplicated block (13 lines × 2) dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/transformers/pages/DefaultSamplesTransformer.kt
- Code Duplication · Duplicated block (12 lines × 2) dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/transformers/pages/DefaultSamplesTransformer.kt
- Code Duplication · Duplicated block (11 lines × 2) dokka-runners/dokka-gradle-plugin/src/main/kotlin/tasks/DokkaGenerateTask.kt
- Code Duplication · Duplicated block (11 lines × 2) dokka-subprojects/analysis-java-psi/src/main/kotlin/org/jetbrains/dokka/analysis/java/util/PsiUtil.kt
- Code Duplication · Duplicated block (10 lines × 2) dokka-subprojects/analysis-kotlin-symbols/src/main/kotlin/org/jetbrains/dokka/analysis/kotlin/symbols/translators/DefaultSymbolToDocumentableTranslator.kt
- Code Duplication · Duplicated block (10 lines × 2) dokka-subprojects/analysis-kotlin-symbols/src/main/kotlin/org/jetbrains/dokka/analysis/kotlin/symbols/translators/DefaultSymbolToDocumentableTranslator.kt
- Code Duplication · Duplicated block (8–9 lines × 3) dokka-subprojects/analysis-kotlin-symbols/src/main/kotlin/org/jetbrains/dokka/analysis/kotlin/symbols/translators/DefaultSymbolToDocumentableTranslator.kt
- Code Duplication · Duplicated block (6 lines × 2) dokka-subprojects/core/src/main/kotlin/org/jetbrains/dokka/transformers/documentation/DefaultDocumentableMerger.kt
- Code Duplication · Duplicated block (6 lines × 2) dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/transformers/documentables/DocumentableReplacerTransformer.kt
- Code Duplication · Duplicated block (6 lines × 2) dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/transformers/documentables/DocumentableReplacerTransformer.kt
- Code Duplication · Duplicated block (6 lines × 2) dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/transformers/documentables/SuppressedByConditionDocumentableFilterTransformer.kt
- Code Duplication · Duplicated block (6 lines × 2) dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/transformers/pages/DefaultSamplesTransformer.kt
- Code Duplication · Duplicated block (5 lines × 4) dokka-subprojects/analysis-kotlin-symbols/src/main/kotlin/org/jetbrains/dokka/analysis/kotlin/symbols/translators/DefaultSymbolToDocumentableTranslator.kt
- Code Duplication · Duplicated block (5 lines × 4) dokka-subprojects/plugin-kotlin-as-java/src/main/kotlin/org/jetbrains/dokka/kotlinAsJava/transformers/JvmNameDocumentableTransformer.kt
- Code Duplication · Duplicated block (2–5 lines × 7) dokka-subprojects/core/src/main/kotlin/org/jetbrains/dokka/transformers/documentation/DefaultDocumentableMerger.kt
- Code Duplication · Duplicated block (5 lines × 2) dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/transformers/documentables/DocumentableReplacerTransformer.kt
- Code Duplication · Duplicated block (5 lines × 2) dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/transformers/documentables/DocumentableReplacerTransformer.kt
- Code Duplication · Duplicated block (5 lines × 2) dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/transformers/documentables/DocumentableReplacerTransformer.kt
- Code Duplication · Duplicated block (5 lines × 2) dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/transformers/documentables/SuppressedByConditionDocumentableFilterTransformer.kt
- Code Duplication · Duplicated block (9 lines × 4) dokka-subprojects/analysis-java-psi/src/main/kotlin/org/jetbrains/dokka/analysis/java/util/StdlibUtil.kt
- Code Duplication · Duplicated block (11 lines × 2) dokka-subprojects/plugin-all-modules-page/src/main/kotlin/org/jetbrains/dokka/allModulesPage/AllModulesPageGeneration.kt
- Code Duplication · Duplicated block (8 lines × 2) dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/renderers/html/htmlPreprocessors.kt
- Code Duplication · Duplicated block (6 lines × 4) dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/transformers/pages/annotations/SinceKotlinTransformer.kt
- Code Duplication · Duplicated block (5 lines × 2) dokka-subprojects/plugin-javadoc/src/main/kotlin/org/jetbrains/dokka/javadoc/signatures/JavadocSignatureProvider.kt
- Secrets (history) · High secret: WD-SECRET-0005 plugins/base/frontend/package-lock.json
- Static Analysis (SAST) · Medium: watchdog-regexp-from-parameter-ts dokka-subprojects/plugin-javadoc/src/main/resources/static_res/jquery/external/jquery/jquery.js
- Static Analysis (SAST) · Medium: watchdog-regexp-from-parameter-ts dokka-subprojects/plugin-javadoc/src/main/resources/static_res/jquery/external/jquery/jquery.js
- Static Analysis (SAST) · Medium: watchdog-regexp-from-parameter-ts dokka-subprojects/plugin-javadoc/src/main/resources/static_res/jquery/external/jquery/jquery.js
- Static Analysis (SAST) · Medium: watchdog-regex-match-index-beyond-capture-groups-js dokka-subprojects/plugin-javadoc/src/main/resources/static_res/jquery/external/jquery/jquery.js
- Static Analysis (SAST) · Medium: watchdog-regex-match-index-beyond-capture-groups-js REDACTED
- Static Analysis (SAST) · Medium: watchdog-regex-match-index-beyond-capture-groups-js REDACTED
- Static Analysis (SAST) · Medium: watchdog-regex-match-index-beyond-capture-groups-js REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
- Code Duplication · Duplicated block (5 lines × 2 locations) REDACTED
- Exception handling · Swallowed exception (empty catch) REDACTED
- Exception handling · Swallowed exception (empty catch) REDACTED
- Exception handling · Swallowed exception (empty catch) REDACTED
- Exception handling · Swallowed exception (empty catch) REDACTED
- Exception handling · Swallowed exception (empty catch) REDACTED
- Exception handling · Swallowed exception (empty catch) REDACTED
- Exception handling · Swallowed exception (empty catch) REDACTED
- Exception handling · Swallowed exception (empty catch) dokka-subprojects/plugin-javadoc/src/main/resources/static_res/jquery/external/jquery/jquery.js
- Exception handling · Swallowed exception (empty catch) dokka-subprojects/plugin-javadoc/src/main/resources/static_res/jquery/external/jquery/jquery.js
- Exception handling · Swallowed exception (empty catch) dokka-subprojects/plugin-javadoc/src/main/resources/static_res/jquery/external/jquery/jquery.js
- Exception handling · Swallowed exception (empty catch) dokka-subprojects/plugin-javadoc/src/main/resources/static_res/jquery/external/jquery/jquery.js
- Exception handling · Swallowed exception (empty catch) dokka-subprojects/plugin-javadoc/src/main/resources/static_res/jquery/external/jquery/jquery.js
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement dokka-integration-tests/gradle/projects/ui-showcase/previousDocVersions/0.9/styles/style.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement dokka-integration-tests/gradle/projects/ui-showcase/previousDocVersions/0.9/styles/style.css
- Visual & motion safety · Animation without a prefers-reduced-motion guard examples/gradle/dokka-versioning-multimodule-example/previousDocVersions/0.9/styles/style.css
- Visual & motion safety · Animation without a prefers-reduced-motion guard examples/gradle/dokka-versioning-multimodule-example/previousDocVersions/0.9/styles/style.css
- Visual & motion safety · Animation without a prefers-reduced-motion guard dokka-integration-tests/gradle/projects/ui-showcase/previousDocVersions/1.9/styles/style.css
- Visual & motion safety · Animation without a prefers-reduced-motion guard dokka-integration-tests/gradle/projects/ui-showcase/previousDocVersions/1.9/styles/style.css
- Visual & motion safety · Animation without a prefers-reduced-motion guard dokka-integration-tests/gradle/projects/ui-showcase/previousDocVersions/1.8/styles/style.css
- Visual & motion safety · Animation without a prefers-reduced-motion guard dokka-integration-tests/gradle/projects/ui-showcase/previousDocVersions/1.8/styles/style.css
- Visual & motion safety · Animation without a prefers-reduced-motion guard dokka-integration-tests/gradle/projects/ui-showcase/previousDocVersions/1.5/styles/style.css
- Visual & motion safety · Animation without a prefers-reduced-motion guard dokka-integration-tests/gradle/projects/ui-showcase/previousDocVersions/1.5/styles/style.css
- Visual & motion safety · Animation without a prefers-reduced-motion guard dokka-integration-tests/gradle/projects/ui-showcase/previousDocVersions/1.0/styles/style.css
- Visual & motion safety · Animation without a prefers-reduced-motion guard dokka-integration-tests/gradle/projects/ui-showcase/previousDocVersions/1.0/styles/style.css
- Visual & motion safety · Animation without a prefers-reduced-motion guard dokka-integration-tests/gradle/projects/ui-showcase/previousDocVersions/0.9/styles/style.css
- Visual & motion safety · Animation without a prefers-reduced-motion guard dokka-integration-tests/gradle/projects/ui-showcase/previousDocVersions/0.9/styles/style.css
- A11y enforcement · Accessibility enforcement below the top rung
Rebuild cost: about €98,000 · Estimate
| Cost to rebuild | €33,000 to €160,000, for 542 to 1,719 hours of work, about 0.7 person-years for 1 to 2 engineers |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 41. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Medium: 44,953 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 links | 2 utilities | 3 DokkaConfiguration | 4 model.doc | 5 model.properties.ExtraProperty | 6 plugability | 7 analysis.java.parsers.doctag | 8 base.resolvers.external | 9 model.properties | 10 model.Annotations | 11 model | 12 analysis.java.parsers | 13 analysis.kotlin.internal | 14 pages | 15 analysis.java | 16 base.resolvers.local | 17 base.templating | 18 base.transformers.pages.comments | 19 renderers | 20 transformers.documentation | 21 transformers.pages | 22 org.jetbrains.dokka | 23 analysis.kotlin.symbols.plugin | 24 base.renderers | 25 base.transformers.documentables | 26 base.translators.documentables | 27 javadoc.pages | 28 templates | 29 analysis.kotlin.symbols.translators | 30 base.renderers.html | 31 base.signatures | 32 gradle | 33 javadoc.renderer | 34 analysis.kotlin.symbols.services | 35 base | 36 javadoc.signatures | 37 kotlinAsJava.signatures | 38 allModulesPage | 39 javadoc | 40 kotlinAsJava.translators |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 links | ||||||||||||||||||||||||||||||||||||||||
| 2 utilities | ||||||||||||||||||||||||||||||||||||||||
| 3 DokkaConfiguration | 2 | |||||||||||||||||||||||||||||||||||||||
| 4 model.doc | 4 | 3 | ||||||||||||||||||||||||||||||||||||||
| 5 model.properties.ExtraProperty | 1 | |||||||||||||||||||||||||||||||||||||||
| 6 plugability | 3 | 6 | ||||||||||||||||||||||||||||||||||||||
| 7 analysis.java.parsers.doctag | 1 | 2 | 3 | 3 | 1 | 3 | 5 | |||||||||||||||||||||||||||||||||
| 8 base.resolvers.external | 3 | 3 | ||||||||||||||||||||||||||||||||||||||
| 9 model.properties | 3 | |||||||||||||||||||||||||||||||||||||||
| 10 model.Annotations | 1 | 1 | 1 | 3 | ||||||||||||||||||||||||||||||||||||
| 11 model | 23 | 32 | 14 | 13 | 53 | 3 | 3 | |||||||||||||||||||||||||||||||||
| 12 analysis.java.parsers | 1 | 1 | 5 | 17 | 1 | 1 | 1 | 9 | 3 | |||||||||||||||||||||||||||||||
| 13 analysis.kotlin.internal | 4 | 5 | 1 | 3 | 6 | |||||||||||||||||||||||||||||||||||
| 14 pages | 8 | 3 | 18 | 24 | ||||||||||||||||||||||||||||||||||||
| 15 analysis.java | 4 | 1 | 7 | 1 | 2 | 3 | ||||||||||||||||||||||||||||||||||
| 16 base.resolvers.local | 4 | 4 | 2 | 5 | 10 | |||||||||||||||||||||||||||||||||||
| 17 base.templating | 1 | 1 | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||
| 18 base.transformers.pages.comments | 2 | 2 | 2 | 6 | ||||||||||||||||||||||||||||||||||||
| 19 renderers | 1 | |||||||||||||||||||||||||||||||||||||||
| 20 transformers.documentation | 4 | 1 | 2 | 1 | 21 | 1 | ||||||||||||||||||||||||||||||||||
| 21 transformers.pages | 4 | |||||||||||||||||||||||||||||||||||||||
| 22 org.jetbrains.dokka | 6 | 24 | 3 | 2 | 3 | 1 | ||||||||||||||||||||||||||||||||||
| 23 analysis.kotlin.symbols.plugin | 1 | 3 | 6 | 1 | 1 | 6 | 4 | |||||||||||||||||||||||||||||||||
| 24 base.renderers | 1 | 4 | 3 | 24 | 1 | 1 | 3 | |||||||||||||||||||||||||||||||||
| 25 base.transformers.documentables | 5 | 6 | 1 | 1 | 17 | 2 | 3 | 48 | 1 | 11 | ||||||||||||||||||||||||||||||
| 26 base.translators.documentables | 4 | 4 | 5 | 8 | 1 | 1 | 3 | 1 | 13 | 2 | 16 | 3 | 1 | 3 | 2 | |||||||||||||||||||||||||
| 27 javadoc.pages | 23 | 1 | 1 | 13 | 26 | 2 | 62 | 5 | ||||||||||||||||||||||||||||||||
| 28 templates | 5 | 10 | 2 | 1 | 7 | |||||||||||||||||||||||||||||||||||
| 29 analysis.kotlin.symbols.translators | 5 | 3 | 3 | 2 | 1 | 4 | 27 | 2 | 3 | 2 | ||||||||||||||||||||||||||||||
| 30 base.renderers.html | 3 | 9 | 1 | 4 | 1 | 45 | 1 | 8 | 1 | 1 | 1 | |||||||||||||||||||||||||||||
| 31 base.signatures | 2 | 1 | 3 | 1 | 1 | 2 | 26 | 5 | 1 | 1 | 1 | |||||||||||||||||||||||||||||
| 32 gradle | 4 | 21 | ||||||||||||||||||||||||||||||||||||||
| 33 javadoc.renderer | 1 | 3 | 1 | 13 | 2 | 1 | 1 | 1 | 11 | |||||||||||||||||||||||||||||||
| 34 analysis.kotlin.symbols.services | 4 | 2 | 7 | 6 | 8 | 8 | 3 | 4 | 2 | |||||||||||||||||||||||||||||||
| 35 base | 5 | 1 | 1 | 1 | 1 | 1 | 4 | 1 | 2 | 1 | 1 | |||||||||||||||||||||||||||||
| 36 javadoc.signatures | 1 | 1 | 1 | 1 | 9 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||
| 37 kotlinAsJava.signatures | 1 | 1 | 1 | 1 | 9 | 2 | 1 | 1 | 4 | |||||||||||||||||||||||||||||||
| 38 allModulesPage | 3 | 2 | 2 | 9 | 1 | 1 | 1 | 4 | 3 | 1 | 1 | 3 | 3 | 1 | 1 | |||||||||||||||||||||||||
| 39 javadoc | 1 | 6 | 5 | 2 | 1 | 2 | 3 | 1 | 7 | 2 | 1 | |||||||||||||||||||||||||||||
| 40 kotlinAsJava.translators | 2 | 1 | 2 | 2 | 2 | 2 | 1 | 1 | 2 | 2 |
3→22 DokkaConfiguration uses org.jetbrains.dokka part of a loop✕
- Connections
- 2 pairs of types, where a type in DokkaConfiguration uses a type in org.jetbrains.dokka.
- The types involved
org.jetbrains.dokka.DokkaConfiguration.DokkaSourceSet→org.jetbrains.dokka.DokkaSourceSetIDorg.jetbrains.dokka.DokkaConfiguration.DokkaSourceSet→org.jetbrains.dokka.Platform
- Direction
- DokkaConfiguration uses org.jetbrains.dokka, so a change to org.jetbrains.dokka can break DokkaConfiguration, while a change to DokkaConfiguration can't break org.jetbrains.dokka.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
4→1 model.doc uses links✕
- Connections
- 4 pairs of types, where a type in model.doc uses a type in links.
- The types involved
org.jetbrains.dokka.model.doc.DocumentationLink→org.jetbrains.dokka.links.DRIorg.jetbrains.dokka.model.doc.Param→org.jetbrains.dokka.links.DRIorg.jetbrains.dokka.model.doc.See→org.jetbrains.dokka.links.DRIorg.jetbrains.dokka.model.doc.Throws→org.jetbrains.dokka.links.DRI
- Direction
- model.doc uses links, so a change to links can break model.doc, while a change to model.doc can't break links.
- Position
- Below the diagonal: model.doc uses a module listed above it, which is the healthy direction.
4→11 model.doc uses model part of a loop✕
- Connections
- 3 pairs of types, where a type in model.doc uses a type in model.
- The types involved
org.jetbrains.dokka.model.doc.DocTag→org.jetbrains.dokka.model.WithChildrenorg.jetbrains.dokka.model.doc.DocumentationNode→org.jetbrains.dokka.model.WithChildrenorg.jetbrains.dokka.model.doc.TagWrapper→org.jetbrains.dokka.model.WithChildren
- Direction
- model.doc uses model, so a change to model can break model.doc, while a change to model.doc can't break model.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
5→9 model.properties.ExtraProperty uses model.properties part of a loop✕
- Connections
- 1 pair of types, where a type in model.properties.ExtraProperty uses a type in model.properties.
- The types involved
org.jetbrains.dokka.model.properties.ExtraProperty.Key→org.jetbrains.dokka.model.properties.MergeStrategy
- Direction
- model.properties.ExtraProperty uses model.properties, so a change to model.properties can break model.properties.ExtraProperty, while a change to model.properties.ExtraProperty can't break model.properties.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→2 plugability uses utilities✕
- Connections
- 3 pairs of types, where a type in plugability uses a type in utilities.
- The types involved
org.jetbrains.dokka.plugability.DokkaContext→org.jetbrains.dokka.utilities.DokkaLoggerorg.jetbrains.dokka.plugability.DokkaContextConfigurationImpl→org.jetbrains.dokka.utilities.DokkaLoggerorg.jetbrains.dokka.plugability.DokkaPlugin→org.jetbrains.dokka.utilities.DokkaLogger
- Direction
- plugability uses utilities, so a change to utilities can break plugability, while a change to plugability can't break utilities.
- Position
- Below the diagonal: plugability uses a module listed above it, which is the healthy direction.
6→22 plugability uses org.jetbrains.dokka part of a loop✕
- Connections
- 6 pairs of types, where a type in plugability uses a type in org.jetbrains.dokka.
- The types involved
org.jetbrains.dokka.plugability.DokkaContext→org.jetbrains.dokka.DokkaConfigurationorg.jetbrains.dokka.plugability.DokkaContextConfigurationImpl→org.jetbrains.dokka.DokkaConfigurationorg.jetbrains.dokka.plugability.DokkaPlugin→org.jetbrains.dokka.DokkaConfigurationorg.jetbrains.dokka.plugability.ExtendingDSL→org.jetbrains.dokka.DokkaConfigurationorg.jetbrains.dokka.plugability.Extension→org.jetbrains.dokka.DokkaConfigurationorg.jetbrains.dokka.plugability.ExtensionBuilder→org.jetbrains.dokka.DokkaConfiguration
- Direction
- plugability uses org.jetbrains.dokka, so a change to org.jetbrains.dokka can break plugability, while a change to plugability can't break org.jetbrains.dokka.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→1 analysis.java.parsers.doctag uses links✕
- Connections
- 1 pair of types, where a type in analysis.java.parsers.doctag uses a type in links.
- The types involved
org.jetbrains.dokka.analysis.java.parsers.doctag.DocTagParserContext→org.jetbrains.dokka.links.DRI
- Direction
- analysis.java.parsers.doctag uses links, so a change to links can break analysis.java.parsers.doctag, while a change to analysis.java.parsers.doctag can't break links.
- Position
- Below the diagonal: analysis.java.parsers.doctag uses a module listed above it, which is the healthy direction.
7→2 analysis.java.parsers.doctag uses utilities✕
- Connections
- 2 pairs of types, where a type in analysis.java.parsers.doctag uses a type in utilities.
- The types involved
org.jetbrains.dokka.analysis.java.parsers.doctag.DefaultSnippetToHtmlConverter→org.jetbrains.dokka.utilities.DokkaLoggerorg.jetbrains.dokka.analysis.java.parsers.doctag.PsiElementToHtmlConverter→org.jetbrains.dokka.utilities.DokkaLogger
- Direction
- analysis.java.parsers.doctag uses utilities, so a change to utilities can break analysis.java.parsers.doctag, while a change to analysis.java.parsers.doctag can't break utilities.
- Position
- Below the diagonal: analysis.java.parsers.doctag uses a module listed above it, which is the healthy direction.
7→3 analysis.java.parsers.doctag uses DokkaConfiguration✕
- Connections
- 3 pairs of types, where a type in analysis.java.parsers.doctag uses a type in DokkaConfiguration.
- The types involved
org.jetbrains.dokka.analysis.java.parsers.doctag.DefaultSnippetToHtmlConverter→org.jetbrains.dokka.DokkaConfiguration.DokkaSourceSetorg.jetbrains.dokka.analysis.java.parsers.doctag.PsiDocTagParser→org.jetbrains.dokka.DokkaConfiguration.DokkaSourceSetorg.jetbrains.dokka.analysis.java.parsers.doctag.PsiElementToHtmlConverter→org.jetbrains.dokka.DokkaConfiguration.DokkaSourceSet
- Direction
- analysis.java.parsers.doctag uses DokkaConfiguration, so a change to DokkaConfiguration can break analysis.java.parsers.doctag, while a change to analysis.java.parsers.doctag can't break DokkaConfiguration.
- Position
- Below the diagonal: analysis.java.parsers.doctag uses a module listed above it, which is the healthy direction.
7→4 analysis.java.parsers.doctag uses model.doc✕
- Connections
- 3 pairs of types, where a type in analysis.java.parsers.doctag uses a type in model.doc.
- The types involved
org.jetbrains.dokka.analysis.java.parsers.doctag.DocTagParserContext→org.jetbrains.dokka.model.doc.DocumentationNodeorg.jetbrains.dokka.analysis.java.parsers.doctag.HtmlToDocTagConverter→org.jetbrains.dokka.model.doc.DocTagorg.jetbrains.dokka.analysis.java.parsers.doctag.PsiDocTagParser→org.jetbrains.dokka.model.doc.DocTag
- Direction
- analysis.java.parsers.doctag uses model.doc, so a change to model.doc can break analysis.java.parsers.doctag, while a change to analysis.java.parsers.doctag can't break model.doc.
- Position
- Below the diagonal: analysis.java.parsers.doctag uses a module listed above it, which is the healthy direction.
7→6 analysis.java.parsers.doctag uses plugability✕
- Connections
- 1 pair of types, where a type in analysis.java.parsers.doctag uses a type in plugability.
- The types involved
org.jetbrains.dokka.analysis.java.parsers.doctag.PsiDocTagParser→org.jetbrains.dokka.plugability.DokkaContext
- Direction
- analysis.java.parsers.doctag uses plugability, so a change to plugability can break analysis.java.parsers.doctag, while a change to analysis.java.parsers.doctag can't break plugability.
- Position
- Below the diagonal: analysis.java.parsers.doctag uses a module listed above it, which is the healthy direction.
7→12 analysis.java.parsers.doctag uses analysis.java.parsers part of a loop✕
- Connections
- 3 pairs of types, where a type in analysis.java.parsers.doctag uses a type in analysis.java.parsers.
- The types involved
org.jetbrains.dokka.analysis.java.parsers.doctag.InheritDocTagResolver→org.jetbrains.dokka.analysis.java.parsers.CommentResolutionContextorg.jetbrains.dokka.analysis.java.parsers.doctag.PsiDocTagParser→org.jetbrains.dokka.analysis.java.parsers.CommentResolutionContextorg.jetbrains.dokka.analysis.java.parsers.doctag.PsiElementToHtmlConverter→org.jetbrains.dokka.analysis.java.parsers.CommentResolutionContext
- Direction
- analysis.java.parsers.doctag uses analysis.java.parsers, so a change to analysis.java.parsers can break analysis.java.parsers.doctag, while a change to analysis.java.parsers.doctag can't break analysis.java.parsers.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→15 analysis.java.parsers.doctag uses analysis.java part of a loop✕
- Connections
- 5 pairs of types, where a type in analysis.java.parsers.doctag uses a type in analysis.java.
- The types involved
org.jetbrains.dokka.analysis.java.parsers.doctag.HtmlParserState→org.jetbrains.dokka.analysis.java.JavadocTagorg.jetbrains.dokka.analysis.java.parsers.doctag.HtmlParsingResult→org.jetbrains.dokka.analysis.java.JavadocTagorg.jetbrains.dokka.analysis.java.parsers.doctag.InheritDocTagResolver→org.jetbrains.dokka.analysis.java.JavadocTagorg.jetbrains.dokka.analysis.java.parsers.doctag.InheritDocTagResolver→org.jetbrains.dokka.analysis.java.ParamJavadocTagorg.jetbrains.dokka.analysis.java.parsers.doctag.InheritDocTagResolver→org.jetbrains.dokka.analysis.java.ThrowingExceptionJavadocTag
- Direction
- analysis.java.parsers.doctag uses analysis.java, so a change to analysis.java can break analysis.java.parsers.doctag, while a change to analysis.java.parsers.doctag can't break analysis.java.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→1 base.resolvers.external uses links✕
- Connections
- 3 pairs of types, where a type in base.resolvers.external uses a type in links.
- The types involved
org.jetbrains.dokka.base.resolvers.external.DefaultExternalLocationProvider→org.jetbrains.dokka.links.DRIorg.jetbrains.dokka.base.resolvers.external.Dokka010ExternalLocationProvider→org.jetbrains.dokka.links.DRIorg.jetbrains.dokka.base.resolvers.external.ExternalLocationProvider→org.jetbrains.dokka.links.DRI
- Direction
- base.resolvers.external uses links, so a change to links can break base.resolvers.external, while a change to base.resolvers.external can't break links.
- Position
- Below the diagonal: base.resolvers.external uses a module listed above it, which is the healthy direction.
8→6 base.resolvers.external uses plugability✕
- Connections
- 3 pairs of types, where a type in base.resolvers.external uses a type in plugability.
- The types involved
org.jetbrains.dokka.base.resolvers.external.DefaultExternalLocationProvider→org.jetbrains.dokka.plugability.DokkaContextorg.jetbrains.dokka.base.resolvers.external.DefaultExternalLocationProviderFactory→org.jetbrains.dokka.plugability.DokkaContextorg.jetbrains.dokka.base.resolvers.external.Dokka010ExternalLocationProvider→org.jetbrains.dokka.plugability.DokkaContext
- Direction
- base.resolvers.external uses plugability, so a change to plugability can break base.resolvers.external, while a change to base.resolvers.external can't break plugability.
- Position
- Below the diagonal: base.resolvers.external uses a module listed above it, which is the healthy direction.
9→5 model.properties uses model.properties.ExtraProperty✕
- Connections
- 3 pairs of types, where a type in model.properties uses a type in model.properties.ExtraProperty.
- The types involved
org.jetbrains.dokka.model.properties.CalculatedProperty→org.jetbrains.dokka.model.properties.ExtraProperty.Keyorg.jetbrains.dokka.model.properties.ExtraProperty→org.jetbrains.dokka.model.properties.ExtraProperty.Keyorg.jetbrains.dokka.model.properties.PropertyContainer→org.jetbrains.dokka.model.properties.ExtraProperty.Key
- Direction
- model.properties uses model.properties.ExtraProperty, so a change to model.properties.ExtraProperty can break model.properties, while a change to model.properties can't break model.properties.ExtraProperty.
- Position
- Below the diagonal: model.properties uses a module listed above it, which is the healthy direction.
10→1 model.Annotations uses links✕
- Connections
- 1 pair of types, where a type in model.Annotations uses a type in links.
- The types involved
org.jetbrains.dokka.model.Annotations.Annotation→org.jetbrains.dokka.links.DRI
- Direction
- model.Annotations uses links, so a change to links can break model.Annotations, while a change to model.Annotations can't break links.
- Position
- Below the diagonal: model.Annotations uses a module listed above it, which is the healthy direction.
10→5 model.Annotations uses model.properties.ExtraProperty✕
- Connections
- 1 pair of types, where a type in model.Annotations uses a type in model.properties.ExtraProperty.
- The types involved
org.jetbrains.dokka.model.Annotations.Companion→org.jetbrains.dokka.model.properties.ExtraProperty.Key
- Direction
- model.Annotations uses model.properties.ExtraProperty, so a change to model.properties.ExtraProperty can break model.Annotations, while a change to model.Annotations can't break model.properties.ExtraProperty.
- Position
- Below the diagonal: model.Annotations uses a module listed above it, which is the healthy direction.
10→9 model.Annotations uses model.properties✕
- Connections
- 1 pair of types, where a type in model.Annotations uses a type in model.properties.
- The types involved
org.jetbrains.dokka.model.Annotations.Companion→org.jetbrains.dokka.model.properties.MergeStrategy
- Direction
- model.Annotations uses model.properties, so a change to model.properties can break model.Annotations, while a change to model.Annotations can't break model.properties.
- Position
- Below the diagonal: model.Annotations uses a module listed above it, which is the healthy direction.
10→11 model.Annotations uses model part of a loop✕
- Connections
- 3 pairs of types, where a type in model.Annotations uses a type in model.
- The types involved
org.jetbrains.dokka.model.Annotations.Annotation→org.jetbrains.dokka.model.AnnotationParameterValueorg.jetbrains.dokka.model.Annotations.Companion→org.jetbrains.dokka.model.AnnotationTargetorg.jetbrains.dokka.model.Annotations.Companion→org.jetbrains.dokka.model.Annotations
- Direction
- model.Annotations uses model, so a change to model can break model.Annotations, while a change to model.Annotations can't break model.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→1 model uses links✕
- Connections
- 23 pairs of types, where a type in model uses a type in links.
- The types involved
org.jetbrains.dokka.model.CheckedExceptions→org.jetbrains.dokka.links.DRIorg.jetbrains.dokka.model.ClassValue→org.jetbrains.dokka.links.DRIorg.jetbrains.dokka.model.DAnnotation→org.jetbrains.dokka.links.DRIorg.jetbrains.dokka.model.DClass→org.jetbrains.dokka.links.DRIorg.jetbrains.dokka.model.DEnum→org.jetbrains.dokka.links.DRIorg.jetbrains.dokka.model.DEnumEntry→org.jetbrains.dokka.links.DRIorg.jetbrains.dokka.model.DFunction→org.jetbrains.dokka.links.DRIorg.jetbrains.dokka.model.DInterface→org.jetbrains.dokka.links.DRIorg.jetbrains.dokka.model.DModule→org.jetbrains.dokka.links.DRIorg.jetbrains.dokka.model.DObject→org.jetbrains.dokka.links.DRIorg.jetbrains.dokka.model.DPackage→org.jetbrains.dokka.links.DRIorg.jetbrains.dokka.model.DParameter→org.jetbrains.dokka.links.DRIorg.jetbrains.dokka.model.DProperty→org.jetbrains.dokka.links.DRIorg.jetbrains.dokka.model.DTypeAlias→org.jetbrains.dokka.links.DRIorg.jetbrains.dokka.model.DTypeParameter→org.jetbrains.dokka.links.DRIorg.jetbrains.dokka.model.Documentable→org.jetbrains.dokka.links.DRIorg.jetbrains.dokka.model.DocumentableKt→org.jetbrains.dokka.links.DRIorg.jetbrains.dokka.model.EnumValue→org.jetbrains.dokka.links.DRIorg.jetbrains.dokka.model.FunctionalTypeConstructor→org.jetbrains.dokka.links.DRIorg.jetbrains.dokka.model.GenericTypeConstructor→org.jetbrains.dokka.links.DRIorg.jetbrains.dokka.model.InheritedMember→org.jetbrains.dokka.links.DRIorg.jetbrains.dokka.model.TypeConstructor→org.jetbrains.dokka.links.DRIorg.jetbrains.dokka.model.TypeParameter→org.jetbrains.dokka.links.DRI
- Direction
- model uses links, so a change to links can break model, while a change to model can't break links.
- Position
- Below the diagonal: model uses a module listed above it, which is the healthy direction.
11→3 model uses DokkaConfiguration✕
- Connections
- 32 pairs of types, where a type in model uses a type in DokkaConfiguration. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
org.jetbrains.dokka.model.ActualTypealias→org.jetbrains.dokka.DokkaConfiguration.DokkaSourceSetorg.jetbrains.dokka.model.AdditionalModifiers→org.jetbrains.dokka.DokkaConfiguration.DokkaSourceSetorg.jetbrains.dokka.model.Annotations→org.jetbrains.dokka.DokkaConfiguration.DokkaSourceSetorg.jetbrains.dokka.model.CheckedExceptions→org.jetbrains.dokka.DokkaConfiguration.DokkaSourceSetorg.jetbrains.dokka.model.CompositeSourceSetID→org.jetbrains.dokka.DokkaConfiguration.DokkaSourceSetorg.jetbrains.dokka.model.DAnnotation→org.jetbrains.dokka.DokkaConfiguration.DokkaSourceSetorg.jetbrains.dokka.model.DClass→org.jetbrains.dokka.DokkaConfiguration.DokkaSourceSetorg.jetbrains.dokka.model.DEnum→org.jetbrains.dokka.DokkaConfiguration.DokkaSourceSetorg.jetbrains.dokka.model.DEnumEntry→org.jetbrains.dokka.DokkaConfiguration.DokkaSourceSetorg.jetbrains.dokka.model.DFunction→org.jetbrains.dokka.DokkaConfiguration.DokkaSourceSetorg.jetbrains.dokka.model.DInterface→org.jetbrains.dokka.DokkaConfiguration.DokkaSourceSetorg.jetbrains.dokka.model.DModule→org.jetbrains.dokka.DokkaConfiguration.DokkaSourceSetorg.jetbrains.dokka.model.DObject→org.jetbrains.dokka.DokkaConfiguration.DokkaSourceSetorg.jetbrains.dokka.model.DPackage→org.jetbrains.dokka.DokkaConfiguration.DokkaSourceSetorg.jetbrains.dokka.model.DParameter→org.jetbrains.dokka.DokkaConfiguration.DokkaSourceSetorg.jetbrains.dokka.model.DProperty→org.jetbrains.dokka.DokkaConfiguration.DokkaSourceSetorg.jetbrains.dokka.model.DTypeAlias→org.jetbrains.dokka.DokkaConfiguration.DokkaSourceSetorg.jetbrains.dokka.model.DTypeParameter→org.jetbrains.dokka.DokkaConfiguration.DokkaSourceSetorg.jetbrains.dokka.model.DefaultValue→org.jetbrains.dokka.DokkaConfiguration.DokkaSourceSetorg.jetbrains.dokka.model.DisplaySourceSet→org.jetbrains.dokka.DokkaConfiguration.DokkaSourceSetorg.jetbrains.dokka.model.DisplaySourceSetCaches→org.jetbrains.dokka.DokkaConfiguration.DokkaSourceSetorg.jetbrains.dokka.model.Documentable→org.jetbrains.dokka.DokkaConfiguration.DokkaSourceSetorg.jetbrains.dokka.model.DocumentableKt→org.jetbrains.dokka.DokkaConfiguration.DokkaSourceSetorg.jetbrains.dokka.model.DocumentableUtilsKt→org.jetbrains.dokka.DokkaConfiguration.DokkaSourceSetorg.jetbrains.dokka.model.ExceptionInSupertypes→org.jetbrains.dokka.DokkaConfiguration.DokkaSourceSet
- Direction
- model uses DokkaConfiguration, so a change to DokkaConfiguration can break model, while a change to model can't break DokkaConfiguration.
- Position
- Below the diagonal: model uses a module listed above it, which is the healthy direction.
11→4 model uses model.doc✕
- Connections
- 14 pairs of types, where a type in model uses a type in model.doc.
- The types involved
org.jetbrains.dokka.model.DAnnotation→org.jetbrains.dokka.model.doc.DocumentationNodeorg.jetbrains.dokka.model.DClass→org.jetbrains.dokka.model.doc.DocumentationNodeorg.jetbrains.dokka.model.DEnum→org.jetbrains.dokka.model.doc.DocumentationNodeorg.jetbrains.dokka.model.DEnumEntry→org.jetbrains.dokka.model.doc.DocumentationNodeorg.jetbrains.dokka.model.DFunction→org.jetbrains.dokka.model.doc.DocumentationNodeorg.jetbrains.dokka.model.DInterface→org.jetbrains.dokka.model.doc.DocumentationNodeorg.jetbrains.dokka.model.DModule→org.jetbrains.dokka.model.doc.DocumentationNodeorg.jetbrains.dokka.model.DObject→org.jetbrains.dokka.model.doc.DocumentationNodeorg.jetbrains.dokka.model.DPackage→org.jetbrains.dokka.model.doc.DocumentationNodeorg.jetbrains.dokka.model.DParameter→org.jetbrains.dokka.model.doc.DocumentationNodeorg.jetbrains.dokka.model.DProperty→org.jetbrains.dokka.model.doc.DocumentationNodeorg.jetbrains.dokka.model.DTypeAlias→org.jetbrains.dokka.model.doc.DocumentationNodeorg.jetbrains.dokka.model.DTypeParameter→org.jetbrains.dokka.model.doc.DocumentationNodeorg.jetbrains.dokka.model.Documentable→org.jetbrains.dokka.model.doc.DocumentationNode
- Direction
- model uses model.doc, so a change to model.doc can break model, while a change to model can't break model.doc.
- Position
- Below the diagonal: model uses a module listed above it, which is the healthy direction.
11→5 model uses model.properties.ExtraProperty✕
- Connections
- 13 pairs of types, where a type in model uses a type in model.properties.ExtraProperty.
- The types involved
org.jetbrains.dokka.model.ActualTypealias→org.jetbrains.dokka.model.properties.ExtraProperty.Keyorg.jetbrains.dokka.model.AdditionalModifiers→org.jetbrains.dokka.model.properties.ExtraProperty.Keyorg.jetbrains.dokka.model.Annotations→org.jetbrains.dokka.model.properties.ExtraProperty.Keyorg.jetbrains.dokka.model.CheckedExceptions→org.jetbrains.dokka.model.properties.ExtraProperty.Keyorg.jetbrains.dokka.model.DefaultValue→org.jetbrains.dokka.model.properties.ExtraProperty.Keyorg.jetbrains.dokka.model.ExceptionInSupertypes→org.jetbrains.dokka.model.properties.ExtraProperty.Keyorg.jetbrains.dokka.model.ImplementedInterfaces→org.jetbrains.dokka.model.properties.ExtraProperty.Keyorg.jetbrains.dokka.model.InheritedMember→org.jetbrains.dokka.model.properties.ExtraProperty.Keyorg.jetbrains.dokka.model.IsAlsoParameter→org.jetbrains.dokka.model.properties.ExtraProperty.Keyorg.jetbrains.dokka.model.IsCompanion→org.jetbrains.dokka.model.properties.ExtraProperty.Keyorg.jetbrains.dokka.model.IsVar→org.jetbrains.dokka.model.properties.ExtraProperty.Keyorg.jetbrains.dokka.model.ObviousMember→org.jetbrains.dokka.model.properties.ExtraProperty.Keyorg.jetbrains.dokka.model.PrimaryConstructorExtra→org.jetbrains.dokka.model.properties.ExtraProperty.Key
- Direction
- model uses model.properties.ExtraProperty, so a change to model.properties.ExtraProperty can break model, while a change to model can't break model.properties.ExtraProperty.
- Position
- Below the diagonal: model uses a module listed above it, which is the healthy direction.
11→9 model uses model.properties✕
- Connections
- 53 pairs of types, where a type in model uses a type in model.properties. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
org.jetbrains.dokka.model.ActualTypealias→org.jetbrains.dokka.model.properties.ExtraPropertyorg.jetbrains.dokka.model.AdditionalModifiers→org.jetbrains.dokka.model.properties.ExtraPropertyorg.jetbrains.dokka.model.Annotations→org.jetbrains.dokka.model.properties.ExtraPropertyorg.jetbrains.dokka.model.CheckedExceptions→org.jetbrains.dokka.model.properties.ExtraPropertyorg.jetbrains.dokka.model.DAnnotation→org.jetbrains.dokka.model.properties.PropertyContainerorg.jetbrains.dokka.model.DAnnotation→org.jetbrains.dokka.model.properties.WithExtraPropertiesorg.jetbrains.dokka.model.DClass→org.jetbrains.dokka.model.properties.PropertyContainerorg.jetbrains.dokka.model.DClass→org.jetbrains.dokka.model.properties.WithExtraPropertiesorg.jetbrains.dokka.model.DEnum→org.jetbrains.dokka.model.properties.PropertyContainerorg.jetbrains.dokka.model.DEnum→org.jetbrains.dokka.model.properties.WithExtraPropertiesorg.jetbrains.dokka.model.DEnumEntry→org.jetbrains.dokka.model.properties.PropertyContainerorg.jetbrains.dokka.model.DEnumEntry→org.jetbrains.dokka.model.properties.WithExtraPropertiesorg.jetbrains.dokka.model.DFunction→org.jetbrains.dokka.model.properties.PropertyContainerorg.jetbrains.dokka.model.DFunction→org.jetbrains.dokka.model.properties.WithExtraPropertiesorg.jetbrains.dokka.model.DInterface→org.jetbrains.dokka.model.properties.PropertyContainerorg.jetbrains.dokka.model.DInterface→org.jetbrains.dokka.model.properties.WithExtraPropertiesorg.jetbrains.dokka.model.DModule→org.jetbrains.dokka.model.properties.PropertyContainerorg.jetbrains.dokka.model.DModule→org.jetbrains.dokka.model.properties.WithExtraPropertiesorg.jetbrains.dokka.model.DObject→org.jetbrains.dokka.model.properties.PropertyContainerorg.jetbrains.dokka.model.DObject→org.jetbrains.dokka.model.properties.WithExtraPropertiesorg.jetbrains.dokka.model.DPackage→org.jetbrains.dokka.model.properties.PropertyContainerorg.jetbrains.dokka.model.DPackage→org.jetbrains.dokka.model.properties.WithExtraPropertiesorg.jetbrains.dokka.model.DParameter→org.jetbrains.dokka.model.properties.PropertyContainerorg.jetbrains.dokka.model.DParameter→org.jetbrains.dokka.model.properties.WithExtraPropertiesorg.jetbrains.dokka.model.DProperty→org.jetbrains.dokka.model.properties.PropertyContainer
- Direction
- model uses model.properties, so a change to model.properties can break model, while a change to model can't break model.properties.
- Position
- Below the diagonal: model uses a module listed above it, which is the healthy direction.
11→10 model uses model.Annotations✕
- Connections
- 3 pairs of types, where a type in model uses a type in model.Annotations.
- The types involved
org.jetbrains.dokka.model.AnnotationValue→org.jetbrains.dokka.model.Annotations.Annotationorg.jetbrains.dokka.model.Annotations→org.jetbrains.dokka.model.Annotations.Annotationorg.jetbrains.dokka.model.Annotations→org.jetbrains.dokka.model.Annotations.AnnotationScope
- Direction
- model uses model.Annotations, so a change to model.Annotations can break model, while a change to model can't break model.Annotations.
- Position
- Below the diagonal: model uses a module listed above it, which is the healthy direction.
11→22 model uses org.jetbrains.dokka part of a loop✕
- Connections
- 3 pairs of types, where a type in model uses a type in org.jetbrains.dokka.
- The types involved
org.jetbrains.dokka.model.CompositeSourceSetID→org.jetbrains.dokka.DokkaSourceSetIDorg.jetbrains.dokka.model.DisplaySourceSet→org.jetbrains.dokka.Platformorg.jetbrains.dokka.model.DisplaySourceSetKt→org.jetbrains.dokka.DokkaSourceSetID
- Direction
- model uses org.jetbrains.dokka, so a change to org.jetbrains.dokka can break model, while a change to model can't break org.jetbrains.dokka.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→1 analysis.java.parsers uses links✕
- Connections
- 1 pair of types, where a type in analysis.java.parsers uses a type in links.
- The types involved
org.jetbrains.dokka.analysis.java.parsers.DokkaPsiParser→org.jetbrains.dokka.links.DRI
- Direction
- analysis.java.parsers uses links, so a change to links can break analysis.java.parsers, while a change to analysis.java.parsers can't break links.
- Position
- Below the diagonal: analysis.java.parsers uses a module listed above it, which is the healthy direction.
12→2 analysis.java.parsers uses utilities✕
- Connections
- 1 pair of types, where a type in analysis.java.parsers uses a type in utilities.
- The types involved
org.jetbrains.dokka.analysis.java.parsers.DokkaPsiParser→org.jetbrains.dokka.utilities.DokkaLogger
- Direction
- analysis.java.parsers uses utilities, so a change to utilities can break analysis.java.parsers, while a change to analysis.java.parsers can't break utilities.
- Position
- Below the diagonal: analysis.java.parsers uses a module listed above it, which is the healthy direction.
12→3 analysis.java.parsers uses DokkaConfiguration✕
- Connections
- 5 pairs of types, where a type in analysis.java.parsers uses a type in DokkaConfiguration.
- The types involved
org.jetbrains.dokka.analysis.java.parsers.DocCommentParser→org.jetbrains.dokka.DokkaConfiguration.DokkaSourceSetorg.jetbrains.dokka.analysis.java.parsers.DokkaPsiParser→org.jetbrains.dokka.DokkaConfiguration.DokkaSourceSetorg.jetbrains.dokka.analysis.java.parsers.JavaDocumentationParser→org.jetbrains.dokka.DokkaConfiguration.DokkaSourceSetorg.jetbrains.dokka.analysis.java.parsers.JavaPsiDocCommentParser→org.jetbrains.dokka.DokkaConfiguration.DokkaSourceSetorg.jetbrains.dokka.analysis.java.parsers.JavadocParser→org.jetbrains.dokka.DokkaConfiguration.DokkaSourceSet
- Direction
- analysis.java.parsers uses DokkaConfiguration, so a change to DokkaConfiguration can break analysis.java.parsers, while a change to analysis.java.parsers can't break DokkaConfiguration.
- Position
- Below the diagonal: analysis.java.parsers uses a module listed above it, which is the healthy direction.
12→4 analysis.java.parsers uses model.doc✕
- Connections
- 17 pairs of types, where a type in analysis.java.parsers uses a type in model.doc.
- The types involved
org.jetbrains.dokka.analysis.java.parsers.DocCommentParser→org.jetbrains.dokka.model.doc.DocumentationNodeorg.jetbrains.dokka.analysis.java.parsers.DokkaPsiParser→org.jetbrains.dokka.model.doc.DocumentationNodeorg.jetbrains.dokka.analysis.java.parsers.JavaDocumentationParser→org.jetbrains.dokka.model.doc.DocumentationNodeorg.jetbrains.dokka.analysis.java.parsers.JavaPsiDocCommentParser→org.jetbrains.dokka.model.doc.Authororg.jetbrains.dokka.analysis.java.parsers.JavaPsiDocCommentParser→org.jetbrains.dokka.model.doc.CustomDocTagorg.jetbrains.dokka.analysis.java.parsers.JavaPsiDocCommentParser→org.jetbrains.dokka.model.doc.CustomTagWrapperorg.jetbrains.dokka.analysis.java.parsers.JavaPsiDocCommentParser→org.jetbrains.dokka.model.doc.Deprecatedorg.jetbrains.dokka.analysis.java.parsers.JavaPsiDocCommentParser→org.jetbrains.dokka.model.doc.Descriptionorg.jetbrains.dokka.analysis.java.parsers.JavaPsiDocCommentParser→org.jetbrains.dokka.model.doc.DocTagorg.jetbrains.dokka.analysis.java.parsers.JavaPsiDocCommentParser→org.jetbrains.dokka.model.doc.DocumentationLinkorg.jetbrains.dokka.analysis.java.parsers.JavaPsiDocCommentParser→org.jetbrains.dokka.model.doc.DocumentationNodeorg.jetbrains.dokka.analysis.java.parsers.JavaPsiDocCommentParser→org.jetbrains.dokka.model.doc.Returnorg.jetbrains.dokka.analysis.java.parsers.JavaPsiDocCommentParser→org.jetbrains.dokka.model.doc.Seeorg.jetbrains.dokka.analysis.java.parsers.JavaPsiDocCommentParser→org.jetbrains.dokka.model.doc.Sinceorg.jetbrains.dokka.analysis.java.parsers.JavaPsiDocCommentParser→org.jetbrains.dokka.model.doc.TagWrapperorg.jetbrains.dokka.analysis.java.parsers.JavaPsiDocCommentParser→org.jetbrains.dokka.model.doc.Throwsorg.jetbrains.dokka.analysis.java.parsers.JavadocParser→org.jetbrains.dokka.model.doc.DocumentationNode
- Direction
- analysis.java.parsers uses model.doc, so a change to model.doc can break analysis.java.parsers, while a change to analysis.java.parsers can't break model.doc.
- Position
- Below the diagonal: analysis.java.parsers uses a module listed above it, which is the healthy direction.
12→7 analysis.java.parsers uses analysis.java.parsers.doctag✕
- Connections
- 1 pair of types, where a type in analysis.java.parsers uses a type in analysis.java.parsers.doctag.
- The types involved
org.jetbrains.dokka.analysis.java.parsers.JavaPsiDocCommentParser→org.jetbrains.dokka.analysis.java.parsers.doctag.PsiDocTagParser
- Direction
- analysis.java.parsers uses analysis.java.parsers.doctag, so a change to analysis.java.parsers.doctag can break analysis.java.parsers, while a change to analysis.java.parsers can't break analysis.java.parsers.doctag.
- Position
- Below the diagonal: analysis.java.parsers uses a module listed above it, which is the healthy direction.
12→9 analysis.java.parsers uses model.properties✕
- Connections
- 1 pair of types, where a type in analysis.java.parsers uses a type in model.properties.
- The types involved
org.jetbrains.dokka.analysis.java.parsers.DokkaPsiParser→org.jetbrains.dokka.model.properties.PropertyContainer
- Direction
- analysis.java.parsers uses model.properties, so a change to model.properties can break analysis.java.parsers, while a change to analysis.java.parsers can't break model.properties.
- Position
- Below the diagonal: analysis.java.parsers uses a module listed above it, which is the healthy direction.
12→10 analysis.java.parsers uses model.Annotations✕
- Connections
- 1 pair of types, where a type in analysis.java.parsers uses a type in model.Annotations.
- The types involved
org.jetbrains.dokka.analysis.java.parsers.DokkaPsiParser→org.jetbrains.dokka.model.Annotations.Annotation
- Direction
- analysis.java.parsers uses model.Annotations, so a change to model.Annotations can break analysis.java.parsers, while a change to analysis.java.parsers can't break model.Annotations.
- Position
- Below the diagonal: analysis.java.parsers uses a module listed above it, which is the healthy direction.
12→11 analysis.java.parsers uses model✕
- Connections
- 9 pairs of types, where a type in analysis.java.parsers uses a type in model.
- The types involved
org.jetbrains.dokka.analysis.java.parsers.DokkaPsiParser→org.jetbrains.dokka.model.DClasslikeorg.jetbrains.dokka.analysis.java.parsers.DokkaPsiParser→org.jetbrains.dokka.model.DFunctionorg.jetbrains.dokka.analysis.java.parsers.DokkaPsiParser→org.jetbrains.dokka.model.DPackageorg.jetbrains.dokka.analysis.java.parsers.DokkaPsiParser→org.jetbrains.dokka.model.DPropertyorg.jetbrains.dokka.analysis.java.parsers.DokkaPsiParser→org.jetbrains.dokka.model.DTypeParameterorg.jetbrains.dokka.analysis.java.parsers.DokkaPsiParser→org.jetbrains.dokka.model.DocumentableSourceorg.jetbrains.dokka.analysis.java.parsers.DokkaPsiParser→org.jetbrains.dokka.model.ExceptionInSupertypesorg.jetbrains.dokka.analysis.java.parsers.DokkaPsiParser→org.jetbrains.dokka.model.JavaModifierorg.jetbrains.dokka.analysis.java.parsers.DokkaPsiParser→org.jetbrains.dokka.model.Visibility
- Direction
- analysis.java.parsers uses model, so a change to model can break analysis.java.parsers, while a change to analysis.java.parsers can't break model.
- Position
- Below the diagonal: analysis.java.parsers uses a module listed above it, which is the healthy direction.
12→15 analysis.java.parsers uses analysis.java part of a loop✕
- Connections
- 3 pairs of types, where a type in analysis.java.parsers uses a type in analysis.java.
- The types involved
org.jetbrains.dokka.analysis.java.parsers.CommentResolutionContext→org.jetbrains.dokka.analysis.java.JavadocTagorg.jetbrains.dokka.analysis.java.parsers.DokkaPsiParser→org.jetbrains.dokka.analysis.java.BreakingAbstractionKotlinLightMethodCheckerorg.jetbrains.dokka.analysis.java.parsers.DokkaPsiParser→org.jetbrains.dokka.analysis.java.SyntheticElementDocumentationProvider
- Direction
- analysis.java.parsers uses analysis.java, so a change to analysis.java can break analysis.java.parsers, while a change to analysis.java.parsers can't break analysis.java.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→1 analysis.kotlin.internal uses links✕
- Connections
- 4 pairs of types, where a type in analysis.kotlin.internal uses a type in links.
- The types involved
org.jetbrains.dokka.analysis.kotlin.internal.FullClassHierarchyBuilder→org.jetbrains.dokka.links.DRIorg.jetbrains.dokka.analysis.kotlin.internal.InheritanceBuilder→org.jetbrains.dokka.links.DRIorg.jetbrains.dokka.analysis.kotlin.internal.InheritanceNode→org.jetbrains.dokka.links.DRIorg.jetbrains.dokka.analysis.kotlin.internal.KotlinToJavaService→org.jetbrains.dokka.links.DRI
- Direction
- analysis.kotlin.internal uses links, so a change to links can break analysis.kotlin.internal, while a change to analysis.kotlin.internal can't break links.
- Position
- Below the diagonal: analysis.kotlin.internal uses a module listed above it, which is the healthy direction.
13→3 analysis.kotlin.internal uses DokkaConfiguration✕
- Connections
- 5 pairs of types, where a type in analysis.kotlin.internal uses a type in DokkaConfiguration.
- The types involved
org.jetbrains.dokka.analysis.kotlin.internal.DocumentableSourceLanguageParser→org.jetbrains.dokka.DokkaConfiguration.DokkaSourceSetorg.jetbrains.dokka.analysis.kotlin.internal.FullClassHierarchyBuilder→org.jetbrains.dokka.DokkaConfiguration.DokkaSourceSetorg.jetbrains.dokka.analysis.kotlin.internal.ModuleAndPackageDocumentationReader→org.jetbrains.dokka.DokkaConfiguration.DokkaModuleDescriptionorg.jetbrains.dokka.analysis.kotlin.internal.ModuleAndPackageDocumentationReader→org.jetbrains.dokka.DokkaConfiguration.DokkaSourceSetorg.jetbrains.dokka.analysis.kotlin.internal.SyntheticDocumentableDetector→org.jetbrains.dokka.DokkaConfiguration.DokkaSourceSet
- Direction
- analysis.kotlin.internal uses DokkaConfiguration, so a change to DokkaConfiguration can break analysis.kotlin.internal, while a change to analysis.kotlin.internal can't break DokkaConfiguration.
- Position
- Below the diagonal: analysis.kotlin.internal uses a module listed above it, which is the healthy direction.
13→4 analysis.kotlin.internal uses model.doc✕
- Connections
- 1 pair of types, where a type in analysis.kotlin.internal uses a type in model.doc.
- The types involved
org.jetbrains.dokka.analysis.kotlin.internal.ModuleAndPackageDocumentationReader→org.jetbrains.dokka.model.doc.DocumentationNode
- Direction
- analysis.kotlin.internal uses model.doc, so a change to model.doc can break analysis.kotlin.internal, while a change to analysis.kotlin.internal can't break model.doc.
- Position
- Below the diagonal: analysis.kotlin.internal uses a module listed above it, which is the healthy direction.
13→6 analysis.kotlin.internal uses plugability✕
- Connections
- 3 pairs of types, where a type in analysis.kotlin.internal uses a type in plugability.
- The types involved
org.jetbrains.dokka.analysis.kotlin.internal.InternalKotlinAnalysisPlugin→org.jetbrains.dokka.plugability.DokkaPluginorg.jetbrains.dokka.analysis.kotlin.internal.InternalKotlinAnalysisPlugin→org.jetbrains.dokka.plugability.ExtensionPointorg.jetbrains.dokka.analysis.kotlin.internal.InternalKotlinAnalysisPlugin→org.jetbrains.dokka.plugability.PluginApiPreviewAcknowledgement
- Direction
- analysis.kotlin.internal uses plugability, so a change to plugability can break analysis.kotlin.internal, while a change to analysis.kotlin.internal can't break plugability.
- Position
- Below the diagonal: analysis.kotlin.internal uses a module listed above it, which is the healthy direction.
13→11 analysis.kotlin.internal uses model✕
- Connections
- 6 pairs of types, where a type in analysis.kotlin.internal uses a type in model.
- The types involved
org.jetbrains.dokka.analysis.kotlin.internal.DocumentableSourceLanguageParser→org.jetbrains.dokka.model.Documentableorg.jetbrains.dokka.analysis.kotlin.internal.FullClassHierarchyBuilder→org.jetbrains.dokka.model.DModuleorg.jetbrains.dokka.analysis.kotlin.internal.InheritanceBuilder→org.jetbrains.dokka.model.Documentableorg.jetbrains.dokka.analysis.kotlin.internal.ModuleAndPackageDocumentationReader→org.jetbrains.dokka.model.DModuleorg.jetbrains.dokka.analysis.kotlin.internal.ModuleAndPackageDocumentationReader→org.jetbrains.dokka.model.DPackageorg.jetbrains.dokka.analysis.kotlin.internal.SyntheticDocumentableDetector→org.jetbrains.dokka.model.Documentable
- Direction
- analysis.kotlin.internal uses model, so a change to model can break analysis.kotlin.internal, while a change to analysis.kotlin.internal can't break model.
- Position
- Below the diagonal: analysis.kotlin.internal uses a module listed above it, which is the healthy direction.
14→1 pages uses links✕
- Connections
- 8 pairs of types, where a type in pages uses a type in links.
- The types involved
org.jetbrains.dokka.pages.ClasslikePageNode→org.jetbrains.dokka.links.DRIorg.jetbrains.dokka.pages.ContentDRILink→org.jetbrains.dokka.links.DRIorg.jetbrains.dokka.pages.ContentPage→org.jetbrains.dokka.links.DRIorg.jetbrains.dokka.pages.DCI→org.jetbrains.dokka.links.DRIorg.jetbrains.dokka.pages.MemberPageNode→org.jetbrains.dokka.links.DRIorg.jetbrains.dokka.pages.ModulePageNode→org.jetbrains.dokka.links.DRIorg.jetbrains.dokka.pages.MultimoduleRootPageNode→org.jetbrains.dokka.links.DRIorg.jetbrains.dokka.pages.PackagePageNode→org.jetbrains.dokka.links.DRI
- Direction
- pages uses links, so a change to links can break pages, while a change to pages can't break links.
- Position
- Below the diagonal: pages uses a module listed above it, which is the healthy direction.
14→5 pages uses model.properties.ExtraProperty✕
- Connections
- 3 pairs of types, where a type in pages uses a type in model.properties.ExtraProperty.
- The types involved
org.jetbrains.dokka.pages.HtmlContent→org.jetbrains.dokka.model.properties.ExtraProperty.Keyorg.jetbrains.dokka.pages.SimpleAttr→org.jetbrains.dokka.model.properties.ExtraProperty.Keyorg.jetbrains.dokka.pages.TabbedContentTypeExtra→org.jetbrains.dokka.model.properties.ExtraProperty.Key
- Direction
- pages uses model.properties.ExtraProperty, so a change to model.properties.ExtraProperty can break pages, while a change to pages can't break model.properties.ExtraProperty.
- Position
- Below the diagonal: pages uses a module listed above it, which is the healthy direction.
14→9 pages uses model.properties✕
- Connections
- 18 pairs of types, where a type in pages uses a type in model.properties.
- The types involved
org.jetbrains.dokka.pages.ContentBreakLine→org.jetbrains.dokka.model.properties.PropertyContainerorg.jetbrains.dokka.pages.ContentCodeBlock→org.jetbrains.dokka.model.properties.PropertyContainerorg.jetbrains.dokka.pages.ContentCodeInline→org.jetbrains.dokka.model.properties.PropertyContainerorg.jetbrains.dokka.pages.ContentDRILink→org.jetbrains.dokka.model.properties.PropertyContainerorg.jetbrains.dokka.pages.ContentDivergentGroup→org.jetbrains.dokka.model.properties.PropertyContainerorg.jetbrains.dokka.pages.ContentDivergentInstance→org.jetbrains.dokka.model.properties.PropertyContainerorg.jetbrains.dokka.pages.ContentEmbeddedResource→org.jetbrains.dokka.model.properties.PropertyContainerorg.jetbrains.dokka.pages.ContentGroup→org.jetbrains.dokka.model.properties.PropertyContainerorg.jetbrains.dokka.pages.ContentHeader→org.jetbrains.dokka.model.properties.PropertyContainerorg.jetbrains.dokka.pages.ContentList→org.jetbrains.dokka.model.properties.PropertyContainerorg.jetbrains.dokka.pages.ContentNode→org.jetbrains.dokka.model.properties.WithExtraPropertiesorg.jetbrains.dokka.pages.ContentResolvedLink→org.jetbrains.dokka.model.properties.PropertyContainerorg.jetbrains.dokka.pages.ContentTable→org.jetbrains.dokka.model.properties.PropertyContainerorg.jetbrains.dokka.pages.ContentText→org.jetbrains.dokka.model.properties.PropertyContainerorg.jetbrains.dokka.pages.HtmlContent→org.jetbrains.dokka.model.properties.ExtraPropertyorg.jetbrains.dokka.pages.PlatformHintedContent→org.jetbrains.dokka.model.properties.PropertyContainerorg.jetbrains.dokka.pages.SimpleAttr→org.jetbrains.dokka.model.properties.ExtraPropertyorg.jetbrains.dokka.pages.TabbedContentTypeExtra→org.jetbrains.dokka.model.properties.ExtraProperty
- Direction
- pages uses model.properties, so a change to model.properties can break pages, while a change to pages can't break model.properties.
- Position
- Below the diagonal: pages uses a module listed above it, which is the healthy direction.
14→11 pages uses model✕
- Connections
- 24 pairs of types, where a type in pages uses a type in model.
- The types involved
org.jetbrains.dokka.pages.ClasslikePageNode→org.jetbrains.dokka.model.Documentableorg.jetbrains.dokka.pages.ContentBreakLine→org.jetbrains.dokka.model.DisplaySourceSetorg.jetbrains.dokka.pages.ContentCodeBlock→org.jetbrains.dokka.model.DisplaySourceSetorg.jetbrains.dokka.pages.ContentCodeInline→org.jetbrains.dokka.model.DisplaySourceSetorg.jetbrains.dokka.pages.ContentComposite→org.jetbrains.dokka.model.DisplaySourceSetorg.jetbrains.dokka.pages.ContentDRILink→org.jetbrains.dokka.model.DisplaySourceSetorg.jetbrains.dokka.pages.ContentDivergentGroup→org.jetbrains.dokka.model.DisplaySourceSetorg.jetbrains.dokka.pages.ContentDivergentInstance→org.jetbrains.dokka.model.DisplaySourceSetorg.jetbrains.dokka.pages.ContentEmbeddedResource→org.jetbrains.dokka.model.DisplaySourceSetorg.jetbrains.dokka.pages.ContentGroup→org.jetbrains.dokka.model.DisplaySourceSetorg.jetbrains.dokka.pages.ContentHeader→org.jetbrains.dokka.model.DisplaySourceSetorg.jetbrains.dokka.pages.ContentList→org.jetbrains.dokka.model.DisplaySourceSetorg.jetbrains.dokka.pages.ContentNode→org.jetbrains.dokka.model.DisplaySourceSetorg.jetbrains.dokka.pages.ContentNode→org.jetbrains.dokka.model.WithChildrenorg.jetbrains.dokka.pages.ContentPage→org.jetbrains.dokka.model.Documentableorg.jetbrains.dokka.pages.ContentResolvedLink→org.jetbrains.dokka.model.DisplaySourceSetorg.jetbrains.dokka.pages.ContentTable→org.jetbrains.dokka.model.DisplaySourceSetorg.jetbrains.dokka.pages.ContentText→org.jetbrains.dokka.model.DisplaySourceSetorg.jetbrains.dokka.pages.MemberPageNode→org.jetbrains.dokka.model.Documentableorg.jetbrains.dokka.pages.ModulePageNode→org.jetbrains.dokka.model.Documentableorg.jetbrains.dokka.pages.PackagePageNode→org.jetbrains.dokka.model.Documentableorg.jetbrains.dokka.pages.PageNode→org.jetbrains.dokka.model.WithChildrenorg.jetbrains.dokka.pages.PlatformHintedContent→org.jetbrains.dokka.model.DisplaySourceSetorg.jetbrains.dokka.pages.WithDocumentables→org.jetbrains.dokka.model.Documentable
- Direction
- pages uses model, so a change to model can break pages, while a change to pages can't break model.
- Position
- Below the diagonal: pages uses a module listed above it, which is the healthy direction.
15→3 analysis.java uses DokkaConfiguration✕
- Connections
- 4 pairs of types, where a type in analysis.java uses a type in DokkaConfiguration.
- The types involved
org.jetbrains.dokka.analysis.java.DefaultPsiToDocumentableTranslator→org.jetbrains.dokka.DokkaConfiguration.DokkaSourceSetorg.jetbrains.dokka.analysis.java.ProjectProvider→org.jetbrains.dokka.DokkaConfiguration.DokkaSourceSetorg.jetbrains.dokka.analysis.java.SourceRootsExtractor→org.jetbrains.dokka.DokkaConfiguration.DokkaSourceSetorg.jetbrains.dokka.analysis.java.SyntheticElementDocumentationProvider→org.jetbrains.dokka.DokkaConfiguration.DokkaSourceSet
- Direction
- analysis.java uses DokkaConfiguration, so a change to DokkaConfiguration can break analysis.java, while a change to analysis.java can't break DokkaConfiguration.
- Position
- Below the diagonal: analysis.java uses a module listed above it, which is the healthy direction.
15→4 analysis.java uses model.doc✕
- Connections
- 1 pair of types, where a type in analysis.java uses a type in model.doc.
- The types involved
org.jetbrains.dokka.analysis.java.SyntheticElementDocumentationProvider→org.jetbrains.dokka.model.doc.DocumentationNode
- Direction
- analysis.java uses model.doc, so a change to model.doc can break analysis.java, while a change to analysis.java can't break model.doc.
- Position
- Below the diagonal: analysis.java uses a module listed above it, which is the healthy direction.
15→6 analysis.java uses plugability✕
- Connections
- 7 pairs of types, where a type in analysis.java uses a type in plugability.
- The types involved
org.jetbrains.dokka.analysis.java.DefaultPsiToDocumentableTranslator→org.jetbrains.dokka.plugability.DokkaContextorg.jetbrains.dokka.analysis.java.JavaAnalysisPlugin→org.jetbrains.dokka.plugability.DokkaPluginorg.jetbrains.dokka.analysis.java.JavaAnalysisPlugin→org.jetbrains.dokka.plugability.Extensionorg.jetbrains.dokka.analysis.java.JavaAnalysisPlugin→org.jetbrains.dokka.plugability.ExtensionPointorg.jetbrains.dokka.analysis.java.JavaAnalysisPlugin→org.jetbrains.dokka.plugability.PluginApiPreviewAcknowledgementorg.jetbrains.dokka.analysis.java.ProjectProvider→org.jetbrains.dokka.plugability.DokkaContextorg.jetbrains.dokka.analysis.java.SourceRootsExtractor→org.jetbrains.dokka.plugability.DokkaContext
- Direction
- analysis.java uses plugability, so a change to plugability can break analysis.java, while a change to analysis.java can't break plugability.
- Position
- Below the diagonal: analysis.java uses a module listed above it, which is the healthy direction.
15→7 analysis.java uses analysis.java.parsers.doctag✕
- Connections
- 1 pair of types, where a type in analysis.java uses a type in analysis.java.parsers.doctag.
- The types involved
org.jetbrains.dokka.analysis.java.JavaAnalysisPlugin→org.jetbrains.dokka.analysis.java.parsers.doctag.InheritDocTagContentProvider
- Direction
- analysis.java uses analysis.java.parsers.doctag, so a change to analysis.java.parsers.doctag can break analysis.java, while a change to analysis.java can't break analysis.java.parsers.doctag.
- Position
- Below the diagonal: analysis.java uses a module listed above it, which is the healthy direction.
15→11 analysis.java uses model✕
- Connections
- 2 pairs of types, where a type in analysis.java uses a type in model.
- The types involved
org.jetbrains.dokka.analysis.java.DefaultPsiToDocumentableTranslator→org.jetbrains.dokka.model.DModuleorg.jetbrains.dokka.analysis.java.DefaultPsiToDocumentableTranslatorKt→org.jetbrains.dokka.model.JavaVisibility
- Direction
- analysis.java uses model, so a change to model can break analysis.java, while a change to analysis.java can't break model.
- Position
- Below the diagonal: analysis.java uses a module listed above it, which is the healthy direction.
15→12 analysis.java uses analysis.java.parsers✕
- Connections
- 3 pairs of types, where a type in analysis.java uses a type in analysis.java.parsers.
- The types involved
org.jetbrains.dokka.analysis.java.DefaultPsiToDocumentableTranslator→org.jetbrains.dokka.analysis.java.parsers.DokkaPsiParserorg.jetbrains.dokka.analysis.java.JavaAnalysisPlugin→org.jetbrains.dokka.analysis.java.parsers.DocCommentParserorg.jetbrains.dokka.analysis.java.SyntheticElementDocumentationProvider→org.jetbrains.dokka.analysis.java.parsers.JavadocParser
- Direction
- analysis.java uses analysis.java.parsers, so a change to analysis.java.parsers can break analysis.java, while a change to analysis.java can't break analysis.java.parsers.
- Position
- Below the diagonal: analysis.java uses a module listed above it, which is the healthy direction.
16→1 base.resolvers.local uses links✕
- Connections
- 4 pairs of types, where a type in base.resolvers.local uses a type in links.
- The types involved
org.jetbrains.dokka.base.resolvers.local.DefaultLocationProvider→org.jetbrains.dokka.links.DRIorg.jetbrains.dokka.base.resolvers.local.DokkaLocationProvider→org.jetbrains.dokka.links.DRIorg.jetbrains.dokka.base.resolvers.local.LocationProvider→org.jetbrains.dokka.links.DRIorg.jetbrains.dokka.base.resolvers.local.LocationProviderKt→org.jetbrains.dokka.links.DRI
- Direction
- base.resolvers.local uses links, so a change to links can break base.resolvers.local, while a change to base.resolvers.local can't break links.
- Position
- Below the diagonal: base.resolvers.local uses a module listed above it, which is the healthy direction.
16→6 base.resolvers.local uses plugability✕
- Connections
- 4 pairs of types, where a type in base.resolvers.local uses a type in plugability.
- The types involved
org.jetbrains.dokka.base.resolvers.local.DefaultLocationProvider→org.jetbrains.dokka.plugability.DokkaContextorg.jetbrains.dokka.base.resolvers.local.DokkaBaseLocationProvider→org.jetbrains.dokka.plugability.DokkaContextorg.jetbrains.dokka.base.resolvers.local.DokkaLocationProvider→org.jetbrains.dokka.plugability.DokkaContextorg.jetbrains.dokka.base.resolvers.local.DokkaLocationProviderFactory→org.jetbrains.dokka.plugability.DokkaContext
- Direction
- base.resolvers.local uses plugability, so a change to plugability can break base.resolvers.local, while a change to base.resolvers.local can't break plugability.
- Position
- Below the diagonal: base.resolvers.local uses a module listed above it, which is the healthy direction.
16→8 base.resolvers.local uses base.resolvers.external✕
- Connections
- 2 pairs of types, where a type in base.resolvers.local uses a type in base.resolvers.external.
- The types involved
org.jetbrains.dokka.base.resolvers.local.DefaultLocationProvider→org.jetbrains.dokka.base.resolvers.external.ExternalLocationProviderorg.jetbrains.dokka.base.resolvers.local.DefaultLocationProvider→org.jetbrains.dokka.base.resolvers.external.ExternalLocationProviderFactory
- Direction
- base.resolvers.local uses base.resolvers.external, so a change to base.resolvers.external can break base.resolvers.local, while a change to base.resolvers.local can't break base.resolvers.external.
- Position
- Below the diagonal: base.resolvers.local uses a module listed above it, which is the healthy direction.
16→11 base.resolvers.local uses model✕
- Connections
- 5 pairs of types, where a type in base.resolvers.local uses a type in model.
- The types involved
org.jetbrains.dokka.base.resolvers.local.DefaultLocationProvider→org.jetbrains.dokka.model.DisplaySourceSetorg.jetbrains.dokka.base.resolvers.local.DokkaBaseLocationProvider→org.jetbrains.dokka.model.DisplaySourceSetorg.jetbrains.dokka.base.resolvers.local.DokkaLocationProvider→org.jetbrains.dokka.model.DisplaySourceSetorg.jetbrains.dokka.base.resolvers.local.LocationProvider→org.jetbrains.dokka.model.DisplaySourceSetorg.jetbrains.dokka.base.resolvers.local.LocationProviderKt→org.jetbrains.dokka.model.DisplaySourceSet
- Direction
- base.resolvers.local uses model, so a change to model can break base.resolvers.local, while a change to base.resolvers.local can't break model.
- Position
- Below the diagonal: base.resolvers.local uses a module listed above it, which is the healthy direction.
16→14 base.resolvers.local uses pages✕
- Connections
- 10 pairs of types, where a type in base.resolvers.local uses a type in pages.
- The types involved
org.jetbrains.dokka.base.resolvers.local.DefaultLocationProvider→org.jetbrains.dokka.pages.RootPageNodeorg.jetbrains.dokka.base.resolvers.local.DokkaBaseLocationProvider→org.jetbrains.dokka.pages.DCIorg.jetbrains.dokka.base.resolvers.local.DokkaBaseLocationProvider→org.jetbrains.dokka.pages.RootPageNodeorg.jetbrains.dokka.base.resolvers.local.DokkaLocationProvider→org.jetbrains.dokka.pages.ContentPageorg.jetbrains.dokka.base.resolvers.local.DokkaLocationProvider→org.jetbrains.dokka.pages.PageNodeorg.jetbrains.dokka.base.resolvers.local.DokkaLocationProvider→org.jetbrains.dokka.pages.RootPageNodeorg.jetbrains.dokka.base.resolvers.local.DokkaLocationProviderFactory→org.jetbrains.dokka.pages.RootPageNodeorg.jetbrains.dokka.base.resolvers.local.LocationProvider→org.jetbrains.dokka.pages.PageNodeorg.jetbrains.dokka.base.resolvers.local.LocationProviderFactory→org.jetbrains.dokka.pages.RootPageNodeorg.jetbrains.dokka.base.resolvers.local.LocationProviderKt→org.jetbrains.dokka.pages.PageNode
- Direction
- base.resolvers.local uses pages, so a change to pages can break base.resolvers.local, while a change to base.resolvers.local can't break pages.
- Position
- Below the diagonal: base.resolvers.local uses a module listed above it, which is the healthy direction.
17→1 base.templating uses links✕
- Connections
- 1 pair of types, where a type in base.templating uses a type in links.
- The types involved
org.jetbrains.dokka.base.templating.ResolveLinkCommand→org.jetbrains.dokka.links.DRI
- Direction
- base.templating uses links, so a change to links can break base.templating, while a change to base.templating can't break links.
- Position
- Below the diagonal: base.templating uses a module listed above it, which is the healthy direction.
17→5 base.templating uses model.properties.ExtraProperty✕
- Connections
- 1 pair of types, where a type in base.templating uses a type in model.properties.ExtraProperty.
- The types involved
org.jetbrains.dokka.base.templating.InsertTemplateExtra→org.jetbrains.dokka.model.properties.ExtraProperty.Key
- Direction
- base.templating uses model.properties.ExtraProperty, so a change to model.properties.ExtraProperty can break base.templating, while a change to base.templating can't break model.properties.ExtraProperty.
- Position
- Below the diagonal: base.templating uses a module listed above it, which is the healthy direction.
17→9 base.templating uses model.properties✕
- Connections
- 1 pair of types, where a type in base.templating uses a type in model.properties.
- The types involved
org.jetbrains.dokka.base.templating.InsertTemplateExtra→org.jetbrains.dokka.model.properties.ExtraProperty
- Direction
- base.templating uses model.properties, so a change to model.properties can break base.templating, while a change to base.templating can't break model.properties.
- Position
- Below the diagonal: base.templating uses a module listed above it, which is the healthy direction.
17→14 base.templating uses pages✕
- Connections
- 1 pair of types, where a type in base.templating uses a type in pages.
- The types involved
org.jetbrains.dokka.base.templating.InsertTemplateExtra→org.jetbrains.dokka.pages.ContentNode
- Direction
- base.templating uses pages, so a change to pages can break base.templating, while a change to base.templating can't break pages.
- Position
- Below the diagonal: base.templating uses a module listed above it, which is the healthy direction.
17→30 base.templating uses base.renderers.html part of a loop✕
- Connections
- 2 pairs of types, where a type in base.templating uses a type in base.renderers.html.
- The types involved
org.jetbrains.dokka.base.templating.AddToSearch→org.jetbrains.dokka.base.renderers.html.SearchRecordorg.jetbrains.dokka.base.templating.ImmediateHtmlCommandConsumer→org.jetbrains.dokka.base.renderers.html.TemplateCommand
- Direction
- base.templating uses base.renderers.html, so a change to base.renderers.html can break base.templating, while a change to base.templating can't break base.renderers.html.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→3 base.transformers.pages.comments uses DokkaConfiguration✕
- Connections
- 2 pairs of types, where a type in base.transformers.pages.comments uses a type in DokkaConfiguration.
- The types involved
org.jetbrains.dokka.base.transformers.pages.comments.CommentsToContentConverter→org.jetbrains.dokka.DokkaConfiguration.DokkaSourceSetorg.jetbrains.dokka.base.transformers.pages.comments.DocTagToContentConverter→org.jetbrains.dokka.DokkaConfiguration.DokkaSourceSet
- Direction
- base.transformers.pages.comments uses DokkaConfiguration, so a change to DokkaConfiguration can break base.transformers.pages.comments, while a change to base.transformers.pages.comments can't break DokkaConfiguration.
- Position
- Below the diagonal: base.transformers.pages.comments uses a module listed above it, which is the healthy direction.
18→4 base.transformers.pages.comments uses model.doc✕
- Connections
- 2 pairs of types, where a type in base.transformers.pages.comments uses a type in model.doc.
- The types involved
org.jetbrains.dokka.base.transformers.pages.comments.CommentsToContentConverter→org.jetbrains.dokka.model.doc.DocTagorg.jetbrains.dokka.base.transformers.pages.comments.DocTagToContentConverter→org.jetbrains.dokka.model.doc.DocTag
- Direction
- base.transformers.pages.comments uses model.doc, so a change to model.doc can break base.transformers.pages.comments, while a change to base.transformers.pages.comments can't break model.doc.
- Position
- Below the diagonal: base.transformers.pages.comments uses a module listed above it, which is the healthy direction.
18→9 base.transformers.pages.comments uses model.properties✕
- Connections
- 2 pairs of types, where a type in base.transformers.pages.comments uses a type in model.properties.
- The types involved
org.jetbrains.dokka.base.transformers.pages.comments.CommentsToContentConverter→org.jetbrains.dokka.model.properties.PropertyContainerorg.jetbrains.dokka.base.transformers.pages.comments.DocTagToContentConverter→org.jetbrains.dokka.model.properties.PropertyContainer
- Direction
- base.transformers.pages.comments uses model.properties, so a change to model.properties can break base.transformers.pages.comments, while a change to base.transformers.pages.comments can't break model.properties.
- Position
- Below the diagonal: base.transformers.pages.comments uses a module listed above it, which is the healthy direction.
18→14 base.transformers.pages.comments uses pages✕
- Connections
- 6 pairs of types, where a type in base.transformers.pages.comments uses a type in pages.
- The types involved
org.jetbrains.dokka.base.transformers.pages.comments.CommentsToContentConverter→org.jetbrains.dokka.pages.ContentNodeorg.jetbrains.dokka.base.transformers.pages.comments.CommentsToContentConverter→org.jetbrains.dokka.pages.DCIorg.jetbrains.dokka.base.transformers.pages.comments.CommentsToContentConverter→org.jetbrains.dokka.pages.Styleorg.jetbrains.dokka.base.transformers.pages.comments.DocTagToContentConverter→org.jetbrains.dokka.pages.ContentNodeorg.jetbrains.dokka.base.transformers.pages.comments.DocTagToContentConverter→org.jetbrains.dokka.pages.DCIorg.jetbrains.dokka.base.transformers.pages.comments.DocTagToContentConverter→org.jetbrains.dokka.pages.Style
- Direction
- base.transformers.pages.comments uses pages, so a change to pages can break base.transformers.pages.comments, while a change to base.transformers.pages.comments can't break pages.
- Position
- Below the diagonal: base.transformers.pages.comments uses a module listed above it, which is the healthy direction.
19→14 renderers uses pages✕
- Connections
- 1 pair of types, where a type in renderers uses a type in pages.
- The types involved
org.jetbrains.dokka.renderers.Renderer→org.jetbrains.dokka.pages.RootPageNode
- Direction
- renderers uses pages, so a change to pages can break renderers, while a change to renderers can't break pages.
- Position
- Below the diagonal: renderers uses a module listed above it, which is the healthy direction.
20→3 transformers.documentation uses DokkaConfiguration✕
- Connections
- 4 pairs of types, where a type in transformers.documentation uses a type in DokkaConfiguration.
- The types involved
org.jetbrains.dokka.transformers.documentation.ClashingDriIdentifier→org.jetbrains.dokka.DokkaConfiguration.DokkaSourceSetorg.jetbrains.dokka.transformers.documentation.DefaultDocumentableMerger→org.jetbrains.dokka.DokkaConfiguration.DokkaSourceSetorg.jetbrains.dokka.transformers.documentation.PreMergeDocumentableTransformerKt→org.jetbrains.dokka.DokkaConfiguration.DokkaSourceSetorg.jetbrains.dokka.transformers.documentation.PreMergeDocumentableTransformerKt→org.jetbrains.dokka.DokkaConfiguration.PackageOptions
- Direction
- transformers.documentation uses DokkaConfiguration, so a change to DokkaConfiguration can break transformers.documentation, while a change to transformers.documentation can't break DokkaConfiguration.
- Position
- Below the diagonal: transformers.documentation uses a module listed above it, which is the healthy direction.
20→5 transformers.documentation uses model.properties.ExtraProperty✕
- Connections
- 1 pair of types, where a type in transformers.documentation uses a type in model.properties.ExtraProperty.
- The types involved
org.jetbrains.dokka.transformers.documentation.ClashingDriIdentifier→org.jetbrains.dokka.model.properties.ExtraProperty.Key
- Direction
- transformers.documentation uses model.properties.ExtraProperty, so a change to model.properties.ExtraProperty can break transformers.documentation, while a change to transformers.documentation can't break model.properties.ExtraProperty.
- Position
- Below the diagonal: transformers.documentation uses a module listed above it, which is the healthy direction.
20→6 transformers.documentation uses plugability✕
- Connections
- 2 pairs of types, where a type in transformers.documentation uses a type in plugability.
- The types involved
org.jetbrains.dokka.transformers.documentation.DefaultDocumentableMerger→org.jetbrains.dokka.plugability.DokkaContextorg.jetbrains.dokka.transformers.documentation.DocumentableTransformer→org.jetbrains.dokka.plugability.DokkaContext
- Direction
- transformers.documentation uses plugability, so a change to plugability can break transformers.documentation, while a change to transformers.documentation can't break plugability.
- Position
- Below the diagonal: transformers.documentation uses a module listed above it, which is the healthy direction.
20→9 transformers.documentation uses model.properties✕
- Connections
- 1 pair of types, where a type in transformers.documentation uses a type in model.properties.
- The types involved
org.jetbrains.dokka.transformers.documentation.ClashingDriIdentifier→org.jetbrains.dokka.model.properties.ExtraProperty
- Direction
- transformers.documentation uses model.properties, so a change to model.properties can break transformers.documentation, while a change to transformers.documentation can't break model.properties.
- Position
- Below the diagonal: transformers.documentation uses a module listed above it, which is the healthy direction.
20→11 transformers.documentation uses model✕
- Connections
- 21 pairs of types, where a type in transformers.documentation uses a type in model.
- The types involved
org.jetbrains.dokka.transformers.documentation.ClashingDriIdentifier→org.jetbrains.dokka.model.Documentableorg.jetbrains.dokka.transformers.documentation.DefaultDocumentableMerger→org.jetbrains.dokka.model.DAnnotationorg.jetbrains.dokka.transformers.documentation.DefaultDocumentableMerger→org.jetbrains.dokka.model.DClassorg.jetbrains.dokka.transformers.documentation.DefaultDocumentableMerger→org.jetbrains.dokka.model.DClasslikeorg.jetbrains.dokka.transformers.documentation.DefaultDocumentableMerger→org.jetbrains.dokka.model.DEnumorg.jetbrains.dokka.transformers.documentation.DefaultDocumentableMerger→org.jetbrains.dokka.model.DEnumEntryorg.jetbrains.dokka.transformers.documentation.DefaultDocumentableMerger→org.jetbrains.dokka.model.DFunctionorg.jetbrains.dokka.transformers.documentation.DefaultDocumentableMerger→org.jetbrains.dokka.model.DInterfaceorg.jetbrains.dokka.transformers.documentation.DefaultDocumentableMerger→org.jetbrains.dokka.model.DModuleorg.jetbrains.dokka.transformers.documentation.DefaultDocumentableMerger→org.jetbrains.dokka.model.DObjectorg.jetbrains.dokka.transformers.documentation.DefaultDocumentableMerger→org.jetbrains.dokka.model.DPackageorg.jetbrains.dokka.transformers.documentation.DefaultDocumentableMerger→org.jetbrains.dokka.model.DParameterorg.jetbrains.dokka.transformers.documentation.DefaultDocumentableMerger→org.jetbrains.dokka.model.DPropertyorg.jetbrains.dokka.transformers.documentation.DefaultDocumentableMerger→org.jetbrains.dokka.model.DTypeAliasorg.jetbrains.dokka.transformers.documentation.DefaultDocumentableMerger→org.jetbrains.dokka.model.DTypeParameterorg.jetbrains.dokka.transformers.documentation.DocumentableMerger→org.jetbrains.dokka.model.DModuleorg.jetbrains.dokka.transformers.documentation.DocumentableToPageTranslator→org.jetbrains.dokka.model.DModuleorg.jetbrains.dokka.transformers.documentation.DocumentableTransformer→org.jetbrains.dokka.model.DModuleorg.jetbrains.dokka.transformers.documentation.PreMergeDocumentableTransformer→org.jetbrains.dokka.model.DModuleorg.jetbrains.dokka.transformers.documentation.PreMergeDocumentableTransformerKt→org.jetbrains.dokka.model.Documentableorg.jetbrains.dokka.transformers.documentation.PreMergeDocumentableTransformerKt→org.jetbrains.dokka.model.DocumentableSource
- Direction
- transformers.documentation uses model, so a change to model can break transformers.documentation, while a change to transformers.documentation can't break model.
- Position
- Below the diagonal: transformers.documentation uses a module listed above it, which is the healthy direction.
20→14 transformers.documentation uses pages✕
- Connections
- 1 pair of types, where a type in transformers.documentation uses a type in pages.
- The types involved
org.jetbrains.dokka.transformers.documentation.DocumentableToPageTranslator→org.jetbrains.dokka.pages.RootPageNode
- Direction
- transformers.documentation uses pages, so a change to pages can break transformers.documentation, while a change to transformers.documentation can't break pages.
- Position
- Below the diagonal: transformers.documentation uses a module listed above it, which is the healthy direction.
21→14 transformers.pages uses pages✕
- Connections
- 4 pairs of types, where a type in transformers.pages uses a type in pages.
- The types involved
org.jetbrains.dokka.transformers.pages.PageCreator→org.jetbrains.dokka.pages.RootPageNodeorg.jetbrains.dokka.transformers.pages.PageTransformer→org.jetbrains.dokka.pages.RootPageNodeorg.jetbrains.dokka.transformers.pages.PageTransformerBuildersKt→org.jetbrains.dokka.pages.PageNodeorg.jetbrains.dokka.transformers.pages.PageTransformerBuildersKt→org.jetbrains.dokka.pages.RootPageNode
- Direction
- transformers.pages uses pages, so a change to pages can break transformers.pages, while a change to transformers.pages can't break pages.
- Position
- Below the diagonal: transformers.pages uses a module listed above it, which is the healthy direction.
22→2 org.jetbrains.dokka uses utilities✕
- Connections
- 6 pairs of types, where a type in org.jetbrains.dokka uses a type in utilities.
- The types involved
org.jetbrains.dokka.DokkaBootstrapImpl→org.jetbrains.dokka.utilities.DokkaLoggerorg.jetbrains.dokka.DokkaGenerator→org.jetbrains.dokka.utilities.DokkaLoggerorg.jetbrains.dokka.DokkaGeneratorKt→org.jetbrains.dokka.utilities.DokkaLoggerorg.jetbrains.dokka.GlobalArguments→org.jetbrains.dokka.utilities.DokkaLoggerorg.jetbrains.dokka.GlobalArguments→org.jetbrains.dokka.utilities.LoggingLevelorg.jetbrains.dokka.Timer→org.jetbrains.dokka.utilities.DokkaLogger
- Direction
- org.jetbrains.dokka uses utilities, so a change to utilities can break org.jetbrains.dokka, while a change to org.jetbrains.dokka can't break utilities.
- Position
- Below the diagonal: org.jetbrains.dokka uses a module listed above it, which is the healthy direction.
22→3 org.jetbrains.dokka uses DokkaConfiguration✕
- Connections
- 24 pairs of types, where a type in org.jetbrains.dokka uses a type in DokkaConfiguration.
- The types involved
org.jetbrains.dokka.ArgTypeArgument→org.jetbrains.dokka.DokkaConfiguration.DokkaSourceSetorg.jetbrains.dokka.ArgTypePlugin→org.jetbrains.dokka.DokkaConfiguration.PluginConfigurationorg.jetbrains.dokka.ArgTypeSourceLinkDefinition→org.jetbrains.dokka.DokkaConfiguration.SourceLinkDefinitionorg.jetbrains.dokka.ArgTypeVisibility→org.jetbrains.dokka.DokkaConfiguration.Visibilityorg.jetbrains.dokka.DokkaConfiguration→org.jetbrains.dokka.DokkaConfiguration.DokkaModuleDescriptionorg.jetbrains.dokka.DokkaConfiguration→org.jetbrains.dokka.DokkaConfiguration.DokkaSourceSetorg.jetbrains.dokka.DokkaConfiguration→org.jetbrains.dokka.DokkaConfiguration.PluginConfigurationorg.jetbrains.dokka.DokkaDefaults→org.jetbrains.dokka.DokkaConfiguration.Visibilityorg.jetbrains.dokka.DokkaModuleDescriptionImpl→org.jetbrains.dokka.DokkaConfiguration.DokkaModuleDescriptionorg.jetbrains.dokka.DokkaSourceSetImpl→org.jetbrains.dokka.DokkaConfiguration.DokkaSourceSetorg.jetbrains.dokka.DokkaSourceSetImpl→org.jetbrains.dokka.DokkaConfiguration.Visibilityorg.jetbrains.dokka.ExternalDocumentationLinkImpl→org.jetbrains.dokka.DokkaConfiguration.ExternalDocumentationLinkorg.jetbrains.dokka.GlobalArguments→org.jetbrains.dokka.DokkaConfiguration.DokkaModuleDescriptionorg.jetbrains.dokka.GlobalArguments→org.jetbrains.dokka.DokkaConfiguration.DokkaSourceSetorg.jetbrains.dokka.GlobalArguments→org.jetbrains.dokka.DokkaConfiguration.PluginConfigurationorg.jetbrains.dokka.LinkMapperKt→org.jetbrains.dokka.DokkaConfiguration.DokkaSourceSetorg.jetbrains.dokka.LinkMapperKt→org.jetbrains.dokka.DokkaConfiguration.ExternalDocumentationLinkorg.jetbrains.dokka.PackageOptionsImpl→org.jetbrains.dokka.DokkaConfiguration.PackageOptionsorg.jetbrains.dokka.PackageOptionsImpl→org.jetbrains.dokka.DokkaConfiguration.Visibilityorg.jetbrains.dokka.PackageOptionsParserKt→org.jetbrains.dokka.DokkaConfiguration.PackageOptionsorg.jetbrains.dokka.PluginConfigurationImpl→org.jetbrains.dokka.DokkaConfiguration.PluginConfigurationorg.jetbrains.dokka.PluginConfigurationImpl→org.jetbrains.dokka.DokkaConfiguration.SerializationFormatorg.jetbrains.dokka.SourceLinkDefinitionImpl→org.jetbrains.dokka.DokkaConfiguration.SourceLinkDefinitionorg.jetbrains.dokka.SourceSetArgumentsParserKt→org.jetbrains.dokka.DokkaConfiguration.DokkaSourceSet
- Direction
- org.jetbrains.dokka uses DokkaConfiguration, so a change to DokkaConfiguration can break org.jetbrains.dokka, while a change to org.jetbrains.dokka can't break DokkaConfiguration.
- Position
- Below the diagonal: org.jetbrains.dokka uses a module listed above it, which is the healthy direction.
22→6 org.jetbrains.dokka uses plugability✕
- Connections
- 3 pairs of types, where a type in org.jetbrains.dokka uses a type in plugability.
- The types involved
org.jetbrains.dokka.CoreExtensions→org.jetbrains.dokka.plugability.ExtensionPointorg.jetbrains.dokka.DokkaGenerator→org.jetbrains.dokka.plugability.DokkaContextorg.jetbrains.dokka.DokkaGenerator→org.jetbrains.dokka.plugability.DokkaPlugin
- Direction
- org.jetbrains.dokka uses plugability, so a change to plugability can break org.jetbrains.dokka, while a change to org.jetbrains.dokka can't break plugability.
- Position
- Below the diagonal: org.jetbrains.dokka uses a module listed above it, which is the healthy direction.
22→19 org.jetbrains.dokka uses renderers✕
- Connections
- 2 pairs of types, where a type in org.jetbrains.dokka uses a type in renderers.
- The types involved
org.jetbrains.dokka.CoreExtensions→org.jetbrains.dokka.renderers.PostActionorg.jetbrains.dokka.CoreExtensions→org.jetbrains.dokka.renderers.Renderer
- Direction
- org.jetbrains.dokka uses renderers, so a change to renderers can break org.jetbrains.dokka, while a change to org.jetbrains.dokka can't break renderers.
- Position
- Below the diagonal: org.jetbrains.dokka uses a module listed above it, which is the healthy direction.
22→20 org.jetbrains.dokka uses transformers.documentation✕
- Connections
- 3 pairs of types, where a type in org.jetbrains.dokka uses a type in transformers.documentation.
- The types involved
org.jetbrains.dokka.CoreExtensions→org.jetbrains.dokka.transformers.documentation.DocumentableMergerorg.jetbrains.dokka.CoreExtensions→org.jetbrains.dokka.transformers.documentation.DocumentableToPageTranslatororg.jetbrains.dokka.CoreExtensions→org.jetbrains.dokka.transformers.documentation.DocumentableTransformer
- Direction
- org.jetbrains.dokka uses transformers.documentation, so a change to transformers.documentation can break org.jetbrains.dokka, while a change to org.jetbrains.dokka can't break transformers.documentation.
- Position
- Below the diagonal: org.jetbrains.dokka uses a module listed above it, which is the healthy direction.
22→21 org.jetbrains.dokka uses transformers.pages✕
- Connections
- 1 pair of types, where a type in org.jetbrains.dokka uses a type in transformers.pages.
- The types involved
org.jetbrains.dokka.CoreExtensions→org.jetbrains.dokka.transformers.pages.PageTransformer
- Direction
- org.jetbrains.dokka uses transformers.pages, so a change to transformers.pages can break org.jetbrains.dokka, while a change to org.jetbrains.dokka can't break transformers.pages.
- Position
- Below the diagonal: org.jetbrains.dokka uses a module listed above it, which is the healthy direction.
23→2 analysis.kotlin.symbols.plugin uses utilities✕
- Connections
- 1 pair of types, where a type in analysis.kotlin.symbols.plugin uses a type in utilities.
- The types involved
org.jetbrains.dokka.analysis.kotlin.symbols.plugin.KotlinAnalysisKt→org.jetbrains.dokka.utilities.DokkaLogger
- Direction
- analysis.kotlin.symbols.plugin uses utilities, so a change to utilities can break analysis.kotlin.symbols.plugin, while a change to analysis.kotlin.symbols.plugin can't break utilities.
- Position
- Below the diagonal: analysis.kotlin.symbols.plugin uses a module listed above it, which is the healthy direction.
23→3 analysis.kotlin.symbols.plugin uses DokkaConfiguration✕
- Connections
- 3 pairs of types, where a type in analysis.kotlin.symbols.plugin uses a type in DokkaConfiguration.
- The types involved
org.jetbrains.dokka.analysis.kotlin.symbols.plugin.AnalysisContextKt→org.jetbrains.dokka.DokkaConfiguration.DokkaSourceSetorg.jetbrains.dokka.analysis.kotlin.symbols.plugin.KotlinAnalysis→org.jetbrains.dokka.DokkaConfiguration.DokkaSourceSetorg.jetbrains.dokka.analysis.kotlin.symbols.plugin.KotlinAnalysisKt→org.jetbrains.dokka.DokkaConfiguration.DokkaSourceSet
- Direction
- analysis.kotlin.symbols.plugin uses DokkaConfiguration, so a change to DokkaConfiguration can break analysis.kotlin.symbols.plugin, while a change to analysis.kotlin.symbols.plugin can't break DokkaConfiguration.
- Position
- Below the diagonal: analysis.kotlin.symbols.plugin uses a module listed above it, which is the healthy direction.
23→6 analysis.kotlin.symbols.plugin uses plugability✕
- Connections
- 6 pairs of types, where a type in analysis.kotlin.symbols.plugin uses a type in plugability.
- The types involved
org.jetbrains.dokka.analysis.kotlin.symbols.plugin.AnalysisContextKt→org.jetbrains.dokka.plugability.DokkaContextorg.jetbrains.dokka.analysis.kotlin.symbols.plugin.SourceRootIndependentChecker→org.jetbrains.dokka.plugability.DokkaContextorg.jetbrains.dokka.analysis.kotlin.symbols.plugin.SymbolsAnalysisPlugin→org.jetbrains.dokka.plugability.DokkaPluginorg.jetbrains.dokka.analysis.kotlin.symbols.plugin.SymbolsAnalysisPlugin→org.jetbrains.dokka.plugability.Extensionorg.jetbrains.dokka.analysis.kotlin.symbols.plugin.SymbolsAnalysisPlugin→org.jetbrains.dokka.plugability.ExtensionPointorg.jetbrains.dokka.analysis.kotlin.symbols.plugin.SymbolsAnalysisPlugin→org.jetbrains.dokka.plugability.PluginApiPreviewAcknowledgement
- Direction
- analysis.kotlin.symbols.plugin uses plugability, so a change to plugability can break analysis.kotlin.symbols.plugin, while a change to analysis.kotlin.symbols.plugin can't break plugability.
- Position
- Below the diagonal: analysis.kotlin.symbols.plugin uses a module listed above it, which is the healthy direction.
23→7 analysis.kotlin.symbols.plugin uses analysis.java.parsers.doctag✕
- Connections
- 1 pair of types, where a type in analysis.kotlin.symbols.plugin uses a type in analysis.java.parsers.doctag.
- The types involved
org.jetbrains.dokka.analysis.kotlin.symbols.plugin.SymbolsAnalysisPlugin→org.jetbrains.dokka.analysis.java.parsers.doctag.InheritDocTagContentProvider
- Direction
- analysis.kotlin.symbols.plugin uses analysis.java.parsers.doctag, so a change to analysis.java.parsers.doctag can break analysis.kotlin.symbols.plugin, while a change to analysis.kotlin.symbols.plugin can't break analysis.java.parsers.doctag.
- Position
- Below the diagonal: analysis.kotlin.symbols.plugin uses a module listed above it, which is the healthy direction.
23→12 analysis.kotlin.symbols.plugin uses analysis.java.parsers✕
- Connections
- 1 pair of types, where a type in analysis.kotlin.symbols.plugin uses a type in analysis.java.parsers.
- The types involved
org.jetbrains.dokka.analysis.kotlin.symbols.plugin.SymbolsAnalysisPlugin→org.jetbrains.dokka.analysis.java.parsers.DocCommentParser
- Direction
- analysis.kotlin.symbols.plugin uses analysis.java.parsers, so a change to analysis.java.parsers can break analysis.kotlin.symbols.plugin, while a change to analysis.kotlin.symbols.plugin can't break analysis.java.parsers.
- Position
- Below the diagonal: analysis.kotlin.symbols.plugin uses a module listed above it, which is the healthy direction.
23→13 analysis.kotlin.symbols.plugin uses analysis.kotlin.internal✕
- Connections
- 6 pairs of types, where a type in analysis.kotlin.symbols.plugin uses a type in analysis.kotlin.internal.
- The types involved
org.jetbrains.dokka.analysis.kotlin.symbols.plugin.SymbolsAnalysisPlugin→org.jetbrains.dokka.analysis.kotlin.internal.DocumentableSourceLanguageParserorg.jetbrains.dokka.analysis.kotlin.symbols.plugin.SymbolsAnalysisPlugin→org.jetbrains.dokka.analysis.kotlin.internal.FullClassHierarchyBuilderorg.jetbrains.dokka.analysis.kotlin.symbols.plugin.SymbolsAnalysisPlugin→org.jetbrains.dokka.analysis.kotlin.internal.InheritanceBuilderorg.jetbrains.dokka.analysis.kotlin.symbols.plugin.SymbolsAnalysisPlugin→org.jetbrains.dokka.analysis.kotlin.internal.KotlinToJavaServiceorg.jetbrains.dokka.analysis.kotlin.symbols.plugin.SymbolsAnalysisPlugin→org.jetbrains.dokka.analysis.kotlin.internal.ModuleAndPackageDocumentationReaderorg.jetbrains.dokka.analysis.kotlin.symbols.plugin.SymbolsAnalysisPlugin→org.jetbrains.dokka.analysis.kotlin.internal.SyntheticDocumentableDetector
- Direction
- analysis.kotlin.symbols.plugin uses analysis.kotlin.internal, so a change to analysis.kotlin.internal can break analysis.kotlin.symbols.plugin, while a change to analysis.kotlin.symbols.plugin can't break analysis.kotlin.internal.
- Position
- Below the diagonal: analysis.kotlin.symbols.plugin uses a module listed above it, which is the healthy direction.
23→15 analysis.kotlin.symbols.plugin uses analysis.java✕
- Connections
- 4 pairs of types, where a type in analysis.kotlin.symbols.plugin uses a type in analysis.java.
- The types involved
org.jetbrains.dokka.analysis.kotlin.symbols.plugin.SymbolsAnalysisPlugin→org.jetbrains.dokka.analysis.java.BreakingAbstractionKotlinLightMethodCheckerorg.jetbrains.dokka.analysis.kotlin.symbols.plugin.SymbolsAnalysisPlugin→org.jetbrains.dokka.analysis.java.JavaAnalysisPluginorg.jetbrains.dokka.analysis.kotlin.symbols.plugin.SymbolsAnalysisPlugin→org.jetbrains.dokka.analysis.java.ProjectProviderorg.jetbrains.dokka.analysis.kotlin.symbols.plugin.SymbolsAnalysisPlugin→org.jetbrains.dokka.analysis.java.SourceRootsExtractor
- Direction
- analysis.kotlin.symbols.plugin uses analysis.java, so a change to analysis.java can break analysis.kotlin.symbols.plugin, while a change to analysis.kotlin.symbols.plugin can't break analysis.java.
- Position
- Below the diagonal: analysis.kotlin.symbols.plugin uses a module listed above it, which is the healthy direction.
24→1 base.renderers uses links✕
- Connections
- 1 pair of types, where a type in base.renderers uses a type in links.
- The types involved
org.jetbrains.dokka.base.renderers.PageIdKt→org.jetbrains.dokka.links.DRI
- Direction
- base.renderers uses links, so a change to links can break base.renderers, while a change to base.renderers can't break links.
- Position
- Below the diagonal: base.renderers uses a module listed above it, which is the healthy direction.
24→6 base.renderers uses plugability✕
- Connections
- 4 pairs of types, where a type in base.renderers uses a type in plugability.
- The types involved
org.jetbrains.dokka.base.renderers.DefaultRenderer→org.jetbrains.dokka.plugability.DokkaContextorg.jetbrains.dokka.base.renderers.FileWriter→org.jetbrains.dokka.plugability.DokkaContextorg.jetbrains.dokka.base.renderers.PackageListCreator→org.jetbrains.dokka.plugability.DokkaContextorg.jetbrains.dokka.base.renderers.PackageListService→org.jetbrains.dokka.plugability.DokkaContext
- Direction
- base.renderers uses plugability, so a change to plugability can break base.renderers, while a change to base.renderers can't break plugability.
- Position
- Below the diagonal: base.renderers uses a module listed above it, which is the healthy direction.
24→11 base.renderers uses model✕
- Connections
- 3 pairs of types, where a type in base.renderers uses a type in model.
- The types involved
org.jetbrains.dokka.base.renderers.DefaultRenderer→org.jetbrains.dokka.model.DisplaySourceSetorg.jetbrains.dokka.base.renderers.DefaultRendererKt→org.jetbrains.dokka.model.DisplaySourceSetorg.jetbrains.dokka.base.renderers.PageIdKt→org.jetbrains.dokka.model.DisplaySourceSet
- Direction
- base.renderers uses model, so a change to model can break base.renderers, while a change to base.renderers can't break model.
- Position
- Below the diagonal: base.renderers uses a module listed above it, which is the healthy direction.
24→14 base.renderers uses pages✕
- Connections
- 24 pairs of types, where a type in base.renderers uses a type in pages.
- The types involved
org.jetbrains.dokka.base.renderers.DefaultRenderer→org.jetbrains.dokka.pages.ContentBreakLineorg.jetbrains.dokka.base.renderers.DefaultRenderer→org.jetbrains.dokka.pages.ContentCodeBlockorg.jetbrains.dokka.base.renderers.DefaultRenderer→org.jetbrains.dokka.pages.ContentCodeInlineorg.jetbrains.dokka.base.renderers.DefaultRenderer→org.jetbrains.dokka.pages.ContentDRILinkorg.jetbrains.dokka.base.renderers.DefaultRenderer→org.jetbrains.dokka.pages.ContentDivergentGrouporg.jetbrains.dokka.base.renderers.DefaultRenderer→org.jetbrains.dokka.pages.ContentDivergentInstanceorg.jetbrains.dokka.base.renderers.DefaultRenderer→org.jetbrains.dokka.pages.ContentEmbeddedResourceorg.jetbrains.dokka.base.renderers.DefaultRenderer→org.jetbrains.dokka.pages.ContentGrouporg.jetbrains.dokka.base.renderers.DefaultRenderer→org.jetbrains.dokka.pages.ContentHeaderorg.jetbrains.dokka.base.renderers.DefaultRenderer→org.jetbrains.dokka.pages.ContentListorg.jetbrains.dokka.base.renderers.DefaultRenderer→org.jetbrains.dokka.pages.ContentNodeorg.jetbrains.dokka.base.renderers.DefaultRenderer→org.jetbrains.dokka.pages.ContentPageorg.jetbrains.dokka.base.renderers.DefaultRenderer→org.jetbrains.dokka.pages.ContentResolvedLinkorg.jetbrains.dokka.base.renderers.DefaultRenderer→org.jetbrains.dokka.pages.ContentTableorg.jetbrains.dokka.base.renderers.DefaultRenderer→org.jetbrains.dokka.pages.ContentTextorg.jetbrains.dokka.base.renderers.DefaultRenderer→org.jetbrains.dokka.pages.PageNodeorg.jetbrains.dokka.base.renderers.DefaultRenderer→org.jetbrains.dokka.pages.PlatformHintedContentorg.jetbrains.dokka.base.renderers.DefaultRenderer→org.jetbrains.dokka.pages.RootPageNodeorg.jetbrains.dokka.base.renderers.PackageListCreator→org.jetbrains.dokka.pages.ModulePageorg.jetbrains.dokka.base.renderers.PackageListCreator→org.jetbrains.dokka.pages.RendererSpecificPageorg.jetbrains.dokka.base.renderers.PackageListCreator→org.jetbrains.dokka.pages.RootPageNodeorg.jetbrains.dokka.base.renderers.PackageListService→org.jetbrains.dokka.pages.ModulePageorg.jetbrains.dokka.base.renderers.PackageListService→org.jetbrains.dokka.pages.RootPageNodeorg.jetbrains.dokka.base.renderers.RootCreator→org.jetbrains.dokka.pages.RootPageNode
- Direction
- base.renderers uses pages, so a change to pages can break base.renderers, while a change to base.renderers can't break pages.
- Position
- Below the diagonal: base.renderers uses a module listed above it, which is the healthy direction.
24→16 base.renderers uses base.resolvers.local✕
- Connections
- 1 pair of types, where a type in base.renderers uses a type in base.resolvers.local.
- The types involved
org.jetbrains.dokka.base.renderers.DefaultRenderer→org.jetbrains.dokka.base.resolvers.local.LocationProvider
- Direction
- base.renderers uses base.resolvers.local, so a change to base.resolvers.local can break base.renderers, while a change to base.renderers can't break base.resolvers.local.
- Position
- Below the diagonal: base.renderers uses a module listed above it, which is the healthy direction.
24→19 base.renderers uses renderers✕
- Connections
- 1 pair of types, where a type in base.renderers uses a type in renderers.
- The types involved
org.jetbrains.dokka.base.renderers.DefaultRenderer→org.jetbrains.dokka.renderers.Renderer
- Direction
- base.renderers uses renderers, so a change to renderers can break base.renderers, while a change to base.renderers can't break renderers.
- Position
- Below the diagonal: base.renderers uses a module listed above it, which is the healthy direction.
24→21 base.renderers uses transformers.pages✕
- Connections
- 3 pairs of types, where a type in base.renderers uses a type in transformers.pages.
- The types involved
org.jetbrains.dokka.base.renderers.DefaultRenderer→org.jetbrains.dokka.transformers.pages.PageTransformerorg.jetbrains.dokka.base.renderers.PackageListCreator→org.jetbrains.dokka.transformers.pages.PageTransformerorg.jetbrains.dokka.base.renderers.RootCreator→org.jetbrains.dokka.transformers.pages.PageTransformer
- Direction
- base.renderers uses transformers.pages, so a change to transformers.pages can break base.renderers, while a change to base.renderers can't break transformers.pages.
- Position
- Below the diagonal: base.renderers uses a module listed above it, which is the healthy direction.
25→1 base.transformers.documentables uses links✕
- Connections
- 5 pairs of types, where a type in base.transformers.documentables uses a type in links.
- The types involved
org.jetbrains.dokka.base.transformers.documentables.ActualTypealiasAdder→org.jetbrains.dokka.links.DRIorg.jetbrains.dokka.base.transformers.documentables.ExtensionExtractorTransformer→org.jetbrains.dokka.links.DRIorg.jetbrains.dokka.base.transformers.documentables.InheritorsExtractorTransformer→org.jetbrains.dokka.links.DRIorg.jetbrains.dokka.base.transformers.documentables.InheritorsInfo→org.jetbrains.dokka.links.DRIorg.jetbrains.dokka.base.transformers.documentables.JvmMappedMethodsDocumentableFilterTransformer→org.jetbrains.dokka.links.DRI
- Direction
- base.transformers.documentables uses links, so a change to links can break base.transformers.documentables, while a change to base.transformers.documentables can't break links.
- Position
- Below the diagonal: base.transformers.documentables uses a module listed above it, which is the healthy direction.
25→3 base.transformers.documentables uses DokkaConfiguration✕
- Connections
- 6 pairs of types, where a type in base.transformers.documentables uses a type in DokkaConfiguration.
- The types involved
org.jetbrains.dokka.base.transformers.documentables.ExtensionExtractorTransformer→org.jetbrains.dokka.DokkaConfiguration.DokkaSourceSetorg.jetbrains.dokka.base.transformers.documentables.InheritorsExtractorTransformer→org.jetbrains.dokka.DokkaConfiguration.DokkaSourceSetorg.jetbrains.dokka.base.transformers.documentables.InheritorsInfo→org.jetbrains.dokka.DokkaConfiguration.DokkaSourceSetorg.jetbrains.dokka.base.transformers.documentables.ModuleAndPackageDocumentationTransformer→org.jetbrains.dokka.DokkaConfiguration.DokkaSourceSetorg.jetbrains.dokka.base.transformers.documentables.ReportUndocumentedTransformer→org.jetbrains.dokka.DokkaConfiguration.DokkaSourceSetorg.jetbrains.dokka.base.transformers.documentables.ReportUndocumentedTransformer→org.jetbrains.dokka.DokkaConfiguration.PackageOptions
- Direction
- base.transformers.documentables uses DokkaConfiguration, so a change to DokkaConfiguration can break base.transformers.documentables, while a change to base.transformers.documentables can't break DokkaConfiguration.
- Position
- Below the diagonal: base.transformers.documentables uses a module listed above it, which is the healthy direction.
25→4 base.transformers.documentables uses model.doc✕
- Connections
- 1 pair of types, where a type in base.transformers.documentables uses a type in model.doc.
- The types involved
org.jetbrains.dokka.base.transformers.documentables.ModuleAndPackageDocumentationTransformer→org.jetbrains.dokka.model.doc.DocumentationNode
- Direction
- base.transformers.documentables uses model.doc, so a change to model.doc can break base.transformers.documentables, while a change to base.transformers.documentables can't break model.doc.
- Position
- Below the diagonal: base.transformers.documentables uses a module listed above it, which is the healthy direction.
25→5 base.transformers.documentables uses model.properties.ExtraProperty✕
- Connections
- 1 pair of types, where a type in base.transformers.documentables uses a type in model.properties.ExtraProperty.
- The types involved
org.jetbrains.dokka.base.transformers.documentables.InheritorsInfo→org.jetbrains.dokka.model.properties.ExtraProperty.Key
- Direction
- base.transformers.documentables uses model.properties.ExtraProperty, so a change to model.properties.ExtraProperty can break base.transformers.documentables, while a change to base.transformers.documentables can't break model.properties.ExtraProperty.
- Position
- Below the diagonal: base.transformers.documentables uses a module listed above it, which is the healthy direction.
25→6 base.transformers.documentables uses plugability✕
- Connections
- 17 pairs of types, where a type in base.transformers.documentables uses a type in plugability.
- The types involved
org.jetbrains.dokka.base.transformers.documentables.ActualTypealiasAdder→org.jetbrains.dokka.plugability.DokkaContextorg.jetbrains.dokka.base.transformers.documentables.DeprecatedDocumentableFilterTransformer→org.jetbrains.dokka.plugability.DokkaContextorg.jetbrains.dokka.base.transformers.documentables.DocumentableReplacerTransformer→org.jetbrains.dokka.plugability.DokkaContextorg.jetbrains.dokka.base.transformers.documentables.DocumentableVisibilityFilterTransformer→org.jetbrains.dokka.plugability.DokkaContextorg.jetbrains.dokka.base.transformers.documentables.EmptyPackagesFilterTransformer→org.jetbrains.dokka.plugability.DokkaContextorg.jetbrains.dokka.base.transformers.documentables.ExtensionExtractorTransformer→org.jetbrains.dokka.plugability.DokkaContextorg.jetbrains.dokka.base.transformers.documentables.InheritedEntriesDocumentableFilterTransformer→org.jetbrains.dokka.plugability.DokkaContextorg.jetbrains.dokka.base.transformers.documentables.InheritorsExtractorTransformer→org.jetbrains.dokka.plugability.DokkaContextorg.jetbrains.dokka.base.transformers.documentables.JvmMappedMethodsDocumentableFilterTransformer→org.jetbrains.dokka.plugability.DokkaContextorg.jetbrains.dokka.base.transformers.documentables.KotlinArrayDocumentableReplacerTransformer→org.jetbrains.dokka.plugability.DokkaContextorg.jetbrains.dokka.base.transformers.documentables.ModuleAndPackageDocumentationTransformer→org.jetbrains.dokka.plugability.DokkaContextorg.jetbrains.dokka.base.transformers.documentables.ObviousFunctionsDocumentableFilterTransformer→org.jetbrains.dokka.plugability.DokkaContextorg.jetbrains.dokka.base.transformers.documentables.ReportUndocumentedTransformer→org.jetbrains.dokka.plugability.DokkaContextorg.jetbrains.dokka.base.transformers.documentables.SuppressTagDocumentableFilter→org.jetbrains.dokka.plugability.DokkaContextorg.jetbrains.dokka.base.transformers.documentables.SuppressedByAnnotationsDocumentableFilterTransformer→org.jetbrains.dokka.plugability.DokkaContextorg.jetbrains.dokka.base.transformers.documentables.SuppressedByConditionDocumentableFilterTransformer→org.jetbrains.dokka.plugability.DokkaContextorg.jetbrains.dokka.base.transformers.documentables.SuppressedByConfigurationDocumentableFilterTransformer→org.jetbrains.dokka.plugability.DokkaContext
- Direction
- base.transformers.documentables uses plugability, so a change to plugability can break base.transformers.documentables, while a change to base.transformers.documentables can't break plugability.
- Position
- Below the diagonal: base.transformers.documentables uses a module listed above it, which is the healthy direction.
25→9 base.transformers.documentables uses model.properties✕
- Connections
- 2 pairs of types, where a type in base.transformers.documentables uses a type in model.properties.
- The types involved
org.jetbrains.dokka.base.transformers.documentables.CallableExtensions→org.jetbrains.dokka.model.properties.ExtraPropertyorg.jetbrains.dokka.base.transformers.documentables.InheritorsInfo→org.jetbrains.dokka.model.properties.ExtraProperty
- Direction
- base.transformers.documentables uses model.properties, so a change to model.properties can break base.transformers.documentables, while a change to base.transformers.documentables can't break model.properties.
- Position
- Below the diagonal: base.transformers.documentables uses a module listed above it, which is the healthy direction.
25→10 base.transformers.documentables uses model.Annotations✕
- Connections
- 3 pairs of types, where a type in base.transformers.documentables uses a type in model.Annotations.
- The types involved
org.jetbrains.dokka.base.transformers.documentables.DeprecatedDocumentableFilterTransformer→org.jetbrains.dokka.model.Annotations.Annotationorg.jetbrains.dokka.base.transformers.documentables.SuppressedByAnnotationsDocumentableFilterTransformer→org.jetbrains.dokka.model.Annotations.Annotationorg.jetbrains.dokka.base.transformers.documentables.UtilsKt→org.jetbrains.dokka.model.Annotations.Annotation
- Direction
- base.transformers.documentables uses model.Annotations, so a change to model.Annotations can break base.transformers.documentables, while a change to base.transformers.documentables can't break model.Annotations.
- Position
- Below the diagonal: base.transformers.documentables uses a module listed above it, which is the healthy direction.
25→11 base.transformers.documentables uses model✕
- Connections
- 48 pairs of types, where a type in base.transformers.documentables uses a type in model. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
org.jetbrains.dokka.base.transformers.documentables.ActualTypealiasAdder→org.jetbrains.dokka.model.DClasslikeorg.jetbrains.dokka.base.transformers.documentables.ActualTypealiasAdder→org.jetbrains.dokka.model.DModuleorg.jetbrains.dokka.base.transformers.documentables.ActualTypealiasAdder→org.jetbrains.dokka.model.DTypeAliasorg.jetbrains.dokka.base.transformers.documentables.CallableExtensions→org.jetbrains.dokka.model.Callableorg.jetbrains.dokka.base.transformers.documentables.DeprecatedDocumentableFilterTransformer→org.jetbrains.dokka.model.Documentableorg.jetbrains.dokka.base.transformers.documentables.DocumentableReplacerTransformer→org.jetbrains.dokka.model.Boundorg.jetbrains.dokka.base.transformers.documentables.DocumentableReplacerTransformer→org.jetbrains.dokka.model.DClasslikeorg.jetbrains.dokka.base.transformers.documentables.DocumentableReplacerTransformer→org.jetbrains.dokka.model.DEnumEntryorg.jetbrains.dokka.base.transformers.documentables.DocumentableReplacerTransformer→org.jetbrains.dokka.model.DFunctionorg.jetbrains.dokka.base.transformers.documentables.DocumentableReplacerTransformer→org.jetbrains.dokka.model.DModuleorg.jetbrains.dokka.base.transformers.documentables.DocumentableReplacerTransformer→org.jetbrains.dokka.model.DPackageorg.jetbrains.dokka.base.transformers.documentables.DocumentableReplacerTransformer→org.jetbrains.dokka.model.DParameterorg.jetbrains.dokka.base.transformers.documentables.DocumentableReplacerTransformer→org.jetbrains.dokka.model.DPropertyorg.jetbrains.dokka.base.transformers.documentables.DocumentableReplacerTransformer→org.jetbrains.dokka.model.DTypeAliasorg.jetbrains.dokka.base.transformers.documentables.DocumentableReplacerTransformer→org.jetbrains.dokka.model.DTypeParameterorg.jetbrains.dokka.base.transformers.documentables.DocumentableReplacerTransformer→org.jetbrains.dokka.model.FunctionalTypeConstructororg.jetbrains.dokka.base.transformers.documentables.DocumentableReplacerTransformer→org.jetbrains.dokka.model.GenericTypeConstructororg.jetbrains.dokka.base.transformers.documentables.DocumentableReplacerTransformer→org.jetbrains.dokka.model.Projectionorg.jetbrains.dokka.base.transformers.documentables.DocumentableReplacerTransformer→org.jetbrains.dokka.model.Varianceorg.jetbrains.dokka.base.transformers.documentables.DocumentableVisibilityFilterTransformer→org.jetbrains.dokka.model.DModuleorg.jetbrains.dokka.base.transformers.documentables.EmptyModulesFilterTransformer→org.jetbrains.dokka.model.DModuleorg.jetbrains.dokka.base.transformers.documentables.EmptyPackagesFilterTransformer→org.jetbrains.dokka.model.DModuleorg.jetbrains.dokka.base.transformers.documentables.ExtensionExtractorTransformer→org.jetbrains.dokka.model.Boundorg.jetbrains.dokka.base.transformers.documentables.ExtensionExtractorTransformer→org.jetbrains.dokka.model.Callableorg.jetbrains.dokka.base.transformers.documentables.ExtensionExtractorTransformer→org.jetbrains.dokka.model.DModule
- Direction
- base.transformers.documentables uses model, so a change to model can break base.transformers.documentables, while a change to base.transformers.documentables can't break model.
- Position
- Below the diagonal: base.transformers.documentables uses a module listed above it, which is the healthy direction.
25→13 base.transformers.documentables uses analysis.kotlin.internal✕
- Connections
- 1 pair of types, where a type in base.transformers.documentables uses a type in analysis.kotlin.internal.
- The types involved
org.jetbrains.dokka.base.transformers.documentables.ModuleAndPackageDocumentationTransformer→org.jetbrains.dokka.analysis.kotlin.internal.ModuleAndPackageDocumentationReader
- Direction
- base.transformers.documentables uses analysis.kotlin.internal, so a change to analysis.kotlin.internal can break base.transformers.documentables, while a change to base.transformers.documentables can't break analysis.kotlin.internal.
- Position
- Below the diagonal: base.transformers.documentables uses a module listed above it, which is the healthy direction.
25→20 base.transformers.documentables uses transformers.documentation✕
- Connections
- 11 pairs of types, where a type in base.transformers.documentables uses a type in transformers.documentation.
- The types involved
org.jetbrains.dokka.base.transformers.documentables.ActualTypealiasAdder→org.jetbrains.dokka.transformers.documentation.DocumentableTransformerorg.jetbrains.dokka.base.transformers.documentables.DocumentableReplacerTransformer→org.jetbrains.dokka.transformers.documentation.PreMergeDocumentableTransformerorg.jetbrains.dokka.base.transformers.documentables.DocumentableVisibilityFilterTransformer→org.jetbrains.dokka.transformers.documentation.PreMergeDocumentableTransformerorg.jetbrains.dokka.base.transformers.documentables.EmptyModulesFilterTransformer→org.jetbrains.dokka.transformers.documentation.PreMergeDocumentableTransformerorg.jetbrains.dokka.base.transformers.documentables.EmptyPackagesFilterTransformer→org.jetbrains.dokka.transformers.documentation.PreMergeDocumentableTransformerorg.jetbrains.dokka.base.transformers.documentables.ExtensionExtractorTransformer→org.jetbrains.dokka.transformers.documentation.DocumentableTransformerorg.jetbrains.dokka.base.transformers.documentables.InheritorsExtractorTransformer→org.jetbrains.dokka.transformers.documentation.DocumentableTransformerorg.jetbrains.dokka.base.transformers.documentables.ModuleAndPackageDocumentationTransformer→org.jetbrains.dokka.transformers.documentation.PreMergeDocumentableTransformerorg.jetbrains.dokka.base.transformers.documentables.ReportUndocumentedTransformer→org.jetbrains.dokka.transformers.documentation.DocumentableTransformerorg.jetbrains.dokka.base.transformers.documentables.SuppressedByConditionDocumentableFilterTransformer→org.jetbrains.dokka.transformers.documentation.PreMergeDocumentableTransformerorg.jetbrains.dokka.base.transformers.documentables.SuppressedByConfigurationDocumentableFilterTransformer→org.jetbrains.dokka.transformers.documentation.PreMergeDocumentableTransformer
- Direction
- base.transformers.documentables uses transformers.documentation, so a change to transformers.documentation can break base.transformers.documentables, while a change to base.transformers.documentables can't break transformers.documentation.
- Position
- Below the diagonal: base.transformers.documentables uses a module listed above it, which is the healthy direction.
26→1 base.translators.documentables uses links✕
- Connections
- 4 pairs of types, where a type in base.translators.documentables uses a type in links.
- The types involved
org.jetbrains.dokka.base.translators.documentables.DefaultPageCreator→org.jetbrains.dokka.links.DRIorg.jetbrains.dokka.base.translators.documentables.DefaultPageCreatorKt→org.jetbrains.dokka.links.DRIorg.jetbrains.dokka.base.translators.documentables.DescriptionSectionsKt→org.jetbrains.dokka.links.DRIorg.jetbrains.dokka.base.translators.documentables.PageContentBuilder→org.jetbrains.dokka.links.DRI
- Direction
- base.translators.documentables uses links, so a change to links can break base.translators.documentables, while a change to base.translators.documentables can't break links.
- Position
- Below the diagonal: base.translators.documentables uses a module listed above it, which is the healthy direction.
26→2 base.translators.documentables uses utilities✕
- Connections
- 4 pairs of types, where a type in base.translators.documentables uses a type in utilities.
- The types involved
org.jetbrains.dokka.base.translators.documentables.DefaultDocumentableToPageTranslator→org.jetbrains.dokka.utilities.DokkaLoggerorg.jetbrains.dokka.base.translators.documentables.DefaultPageCreator→org.jetbrains.dokka.utilities.DokkaLoggerorg.jetbrains.dokka.base.translators.documentables.DescriptionSectionsKt→org.jetbrains.dokka.utilities.DokkaLoggerorg.jetbrains.dokka.base.translators.documentables.PageContentBuilder→org.jetbrains.dokka.utilities.DokkaLogger
- Direction
- base.translators.documentables uses utilities, so a change to utilities can break base.translators.documentables, while a change to base.translators.documentables can't break utilities.
- Position
- Below the diagonal: base.translators.documentables uses a module listed above it, which is the healthy direction.
26→3 base.translators.documentables uses DokkaConfiguration✕
- Connections
- 5 pairs of types, where a type in base.translators.documentables uses a type in DokkaConfiguration.
- The types involved
org.jetbrains.dokka.base.translators.documentables.DefaultPageCreator→org.jetbrains.dokka.DokkaConfiguration.DokkaSourceSetorg.jetbrains.dokka.base.translators.documentables.DefaultPageCreatorKt→org.jetbrains.dokka.DokkaConfiguration.DokkaSourceSetorg.jetbrains.dokka.base.translators.documentables.DeprecationSectionCreatorKt→org.jetbrains.dokka.DokkaConfiguration.DokkaSourceSetorg.jetbrains.dokka.base.translators.documentables.DescriptionSectionsKt→org.jetbrains.dokka.DokkaConfiguration.DokkaSourceSetorg.jetbrains.dokka.base.translators.documentables.PageContentBuilder→org.jetbrains.dokka.DokkaConfiguration.DokkaSourceSet
- Direction
- base.translators.documentables uses DokkaConfiguration, so a change to DokkaConfiguration can break base.translators.documentables, while a change to base.translators.documentables can't break DokkaConfiguration.
- Position
- Below the diagonal: base.translators.documentables uses a module listed above it, which is the healthy direction.
26→4 base.translators.documentables uses model.doc✕
- Connections
- 8 pairs of types, where a type in base.translators.documentables uses a type in model.doc.
- The types involved
org.jetbrains.dokka.base.translators.documentables.BriefFromContentNodesKt→org.jetbrains.dokka.model.doc.DocTagorg.jetbrains.dokka.base.translators.documentables.DefaultPageCreator→org.jetbrains.dokka.model.doc.CustomTagWrapperorg.jetbrains.dokka.base.translators.documentables.DefaultPageCreator→org.jetbrains.dokka.model.doc.TagWrapperorg.jetbrains.dokka.base.translators.documentables.DefaultPageCreatorKt→org.jetbrains.dokka.model.doc.CustomTagWrapperorg.jetbrains.dokka.base.translators.documentables.DefaultPageCreatorKt→org.jetbrains.dokka.model.doc.Descriptionorg.jetbrains.dokka.base.translators.documentables.DefaultPageCreatorKt→org.jetbrains.dokka.model.doc.TagWrapperorg.jetbrains.dokka.base.translators.documentables.DescriptionSectionsKt→org.jetbrains.dokka.model.doc.Paramorg.jetbrains.dokka.base.translators.documentables.DescriptionSectionsKt→org.jetbrains.dokka.model.doc.TagWrapper
- Direction
- base.translators.documentables uses model.doc, so a change to model.doc can break base.translators.documentables, while a change to base.translators.documentables can't break model.doc.
- Position
- Below the diagonal: base.translators.documentables uses a module listed above it, which is the healthy direction.
26→5 base.translators.documentables uses model.properties.ExtraProperty✕
- Connections
- 1 pair of types, where a type in base.translators.documentables uses a type in model.properties.ExtraProperty.
- The types involved
org.jetbrains.dokka.base.translators.documentables.DriClashAwareName→org.jetbrains.dokka.model.properties.ExtraProperty.Key
- Direction
- base.translators.documentables uses model.properties.ExtraProperty, so a change to model.properties.ExtraProperty can break base.translators.documentables, while a change to base.translators.documentables can't break model.properties.ExtraProperty.
- Position
- Below the diagonal: base.translators.documentables uses a module listed above it, which is the healthy direction.
26→6 base.translators.documentables uses plugability✕
- Connections
- 1 pair of types, where a type in base.translators.documentables uses a type in plugability.
- The types involved
org.jetbrains.dokka.base.translators.documentables.DefaultDocumentableToPageTranslator→org.jetbrains.dokka.plugability.DokkaContext
- Direction
- base.translators.documentables uses plugability, so a change to plugability can break base.translators.documentables, while a change to base.translators.documentables can't break plugability.
- Position
- Below the diagonal: base.translators.documentables uses a module listed above it, which is the healthy direction.
26→9 base.translators.documentables uses model.properties✕
- Connections
- 3 pairs of types, where a type in base.translators.documentables uses a type in model.properties.
- The types involved
org.jetbrains.dokka.base.translators.documentables.DefaultPageCreator→org.jetbrains.dokka.model.properties.PropertyContainerorg.jetbrains.dokka.base.translators.documentables.DriClashAwareName→org.jetbrains.dokka.model.properties.ExtraPropertyorg.jetbrains.dokka.base.translators.documentables.PageContentBuilder→org.jetbrains.dokka.model.properties.PropertyContainer
- Direction
- base.translators.documentables uses model.properties, so a change to model.properties can break base.translators.documentables, while a change to base.translators.documentables can't break model.properties.
- Position
- Below the diagonal: base.translators.documentables uses a module listed above it, which is the healthy direction.
26→10 base.translators.documentables uses model.Annotations✕
- Connections
- 1 pair of types, where a type in base.translators.documentables uses a type in model.Annotations.
- The types involved
org.jetbrains.dokka.base.translators.documentables.DeprecationSectionCreatorKt→org.jetbrains.dokka.model.Annotations.Annotation
- Direction
- base.translators.documentables uses model.Annotations, so a change to model.Annotations can break base.translators.documentables, while a change to base.translators.documentables can't break model.Annotations.
- Position
- Below the diagonal: base.translators.documentables uses a module listed above it, which is the healthy direction.
26→11 base.translators.documentables uses model✕
- Connections
- 13 pairs of types, where a type in base.translators.documentables uses a type in model.
- The types involved
org.jetbrains.dokka.base.translators.documentables.DefaultDocumentableToPageTranslator→org.jetbrains.dokka.model.DModuleorg.jetbrains.dokka.base.translators.documentables.DefaultPageCreator→org.jetbrains.dokka.model.DEnumEntryorg.jetbrains.dokka.base.translators.documentables.DefaultPageCreator→org.jetbrains.dokka.model.DFunctionorg.jetbrains.dokka.base.translators.documentables.DefaultPageCreator→org.jetbrains.dokka.model.DModuleorg.jetbrains.dokka.base.translators.documentables.DefaultPageCreator→org.jetbrains.dokka.model.DPackageorg.jetbrains.dokka.base.translators.documentables.DefaultPageCreator→org.jetbrains.dokka.model.DPropertyorg.jetbrains.dokka.base.translators.documentables.DefaultPageCreator→org.jetbrains.dokka.model.Documentableorg.jetbrains.dokka.base.translators.documentables.DefaultPageCreator→org.jetbrains.dokka.model.WithScopeorg.jetbrains.dokka.base.translators.documentables.DefaultPageCreatorKt→org.jetbrains.dokka.model.Documentableorg.jetbrains.dokka.base.translators.documentables.DeprecationSectionCreatorKt→org.jetbrains.dokka.model.Documentableorg.jetbrains.dokka.base.translators.documentables.DescriptionSectionsKt→org.jetbrains.dokka.model.Documentableorg.jetbrains.dokka.base.translators.documentables.DriClashAwareName→org.jetbrains.dokka.model.Documentableorg.jetbrains.dokka.base.translators.documentables.PageContentBuilder→org.jetbrains.dokka.model.Documentable
- Direction
- base.translators.documentables uses model, so a change to model can break base.translators.documentables, while a change to base.translators.documentables can't break model.
- Position
- Below the diagonal: base.translators.documentables uses a module listed above it, which is the healthy direction.
26→13 base.translators.documentables uses analysis.kotlin.internal✕
- Connections
- 2 pairs of types, where a type in base.translators.documentables uses a type in analysis.kotlin.internal.
- The types involved
org.jetbrains.dokka.base.translators.documentables.DefaultDocumentableToPageTranslator→org.jetbrains.dokka.analysis.kotlin.internal.DocumentableSourceLanguageParserorg.jetbrains.dokka.base.translators.documentables.DefaultPageCreator→org.jetbrains.dokka.analysis.kotlin.internal.DocumentableSourceLanguageParser
- Direction
- base.translators.documentables uses analysis.kotlin.internal, so a change to analysis.kotlin.internal can break base.translators.documentables, while a change to base.translators.documentables can't break analysis.kotlin.internal.
- Position
- Below the diagonal: base.translators.documentables uses a module listed above it, which is the healthy direction.
26→14 base.translators.documentables uses pages✕
- Connections
- 16 pairs of types, where a type in base.translators.documentables uses a type in pages.
- The types involved
org.jetbrains.dokka.base.translators.documentables.BriefFromContentNodesKt→org.jetbrains.dokka.pages.ContentNodeorg.jetbrains.dokka.base.translators.documentables.BriefFromContentNodesKt→org.jetbrains.dokka.pages.ContentTextorg.jetbrains.dokka.base.translators.documentables.DefaultDocumentableToPageTranslator→org.jetbrains.dokka.pages.ModulePageNodeorg.jetbrains.dokka.base.translators.documentables.DefaultPageCreator→org.jetbrains.dokka.pages.BasicTabbedContentTypeorg.jetbrains.dokka.base.translators.documentables.DefaultPageCreator→org.jetbrains.dokka.pages.ClasslikePageNodeorg.jetbrains.dokka.base.translators.documentables.DefaultPageCreator→org.jetbrains.dokka.pages.ContentGrouporg.jetbrains.dokka.base.translators.documentables.DefaultPageCreator→org.jetbrains.dokka.pages.ContentKindorg.jetbrains.dokka.base.translators.documentables.DefaultPageCreator→org.jetbrains.dokka.pages.ContentNodeorg.jetbrains.dokka.base.translators.documentables.DefaultPageCreator→org.jetbrains.dokka.pages.MemberPageNodeorg.jetbrains.dokka.base.translators.documentables.DefaultPageCreator→org.jetbrains.dokka.pages.ModulePageNodeorg.jetbrains.dokka.base.translators.documentables.DefaultPageCreator→org.jetbrains.dokka.pages.PackagePageNodeorg.jetbrains.dokka.base.translators.documentables.DescriptionSectionsKt→org.jetbrains.dokka.pages.ContentKindorg.jetbrains.dokka.base.translators.documentables.PageContentBuilder→org.jetbrains.dokka.pages.ContentGrouporg.jetbrains.dokka.base.translators.documentables.PageContentBuilder→org.jetbrains.dokka.pages.ContentNodeorg.jetbrains.dokka.base.translators.documentables.PageContentBuilder→org.jetbrains.dokka.pages.Kindorg.jetbrains.dokka.base.translators.documentables.PageContentBuilder→org.jetbrains.dokka.pages.Style
- Direction
- base.translators.documentables uses pages, so a change to pages can break base.translators.documentables, while a change to base.translators.documentables can't break pages.
- Position
- Below the diagonal: base.translators.documentables uses a module listed above it, which is the healthy direction.
26→18 base.translators.documentables uses base.transformers.pages.comments✕
- Connections
- 3 pairs of types, where a type in base.translators.documentables uses a type in base.transformers.pages.comments.
- The types involved
org.jetbrains.dokka.base.translators.documentables.DefaultDocumentableToPageTranslator→org.jetbrains.dokka.base.transformers.pages.comments.CommentsToContentConverterorg.jetbrains.dokka.base.translators.documentables.DefaultPageCreator→org.jetbrains.dokka.base.transformers.pages.comments.CommentsToContentConverterorg.jetbrains.dokka.base.translators.documentables.PageContentBuilder→org.jetbrains.dokka.base.transformers.pages.comments.CommentsToContentConverter
- Direction
- base.translators.documentables uses base.transformers.pages.comments, so a change to base.transformers.pages.comments can break base.translators.documentables, while a change to base.translators.documentables can't break base.transformers.pages.comments.
- Position
- Below the diagonal: base.translators.documentables uses a module listed above it, which is the healthy direction.
26→20 base.translators.documentables uses transformers.documentation✕
- Connections
- 1 pair of types, where a type in base.translators.documentables uses a type in transformers.documentation.
- The types involved
org.jetbrains.dokka.base.translators.documentables.DefaultDocumentableToPageTranslator→org.jetbrains.dokka.transformers.documentation.DocumentableToPageTranslator
- Direction
- base.translators.documentables uses transformers.documentation, so a change to transformers.documentation can break base.translators.documentables, while a change to base.translators.documentables can't break transformers.documentation.
- Position
- Below the diagonal: base.translators.documentables uses a module listed above it, which is the healthy direction.
26→31 base.translators.documentables uses base.signatures part of a loop✕
- Connections
- 3 pairs of types, where a type in base.translators.documentables uses a type in base.signatures.
- The types involved
org.jetbrains.dokka.base.translators.documentables.DefaultDocumentableToPageTranslator→org.jetbrains.dokka.base.signatures.SignatureProviderorg.jetbrains.dokka.base.translators.documentables.DefaultPageCreator→org.jetbrains.dokka.base.signatures.SignatureProviderorg.jetbrains.dokka.base.translators.documentables.PageContentBuilder→org.jetbrains.dokka.base.signatures.SignatureProvider
- Direction
- base.translators.documentables uses base.signatures, so a change to base.signatures can break base.translators.documentables, while a change to base.translators.documentables can't break base.signatures.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
26→35 base.translators.documentables uses base part of a loop✕
- Connections
- 2 pairs of types, where a type in base.translators.documentables uses a type in base.
- The types involved
org.jetbrains.dokka.base.translators.documentables.DefaultDocumentableToPageTranslator→org.jetbrains.dokka.base.DokkaBaseConfigurationorg.jetbrains.dokka.base.translators.documentables.DefaultPageCreator→org.jetbrains.dokka.base.DokkaBaseConfiguration
- Direction
- base.translators.documentables uses base, so a change to base can break base.translators.documentables, while a change to base.translators.documentables can't break base.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
27→1 javadoc.pages uses links✕
- Connections
- 23 pairs of types, where a type in javadoc.pages uses a type in links.
- The types involved
org.jetbrains.dokka.javadoc.pages.AllClassesPage→org.jetbrains.dokka.links.DRIorg.jetbrains.dokka.javadoc.pages.AnchorableJavadocNode→org.jetbrains.dokka.links.DRIorg.jetbrains.dokka.javadoc.pages.DeprecatedNode→org.jetbrains.dokka.links.DRIorg.jetbrains.dokka.javadoc.pages.DeprecatedPage→org.jetbrains.dokka.links.DRIorg.jetbrains.dokka.javadoc.pages.EmptyNode→org.jetbrains.dokka.links.DRIorg.jetbrains.dokka.javadoc.pages.IndexPage→org.jetbrains.dokka.links.DRIorg.jetbrains.dokka.javadoc.pages.JavadocClasslikePageNode→org.jetbrains.dokka.links.DRIorg.jetbrains.dokka.javadoc.pages.JavadocContentGroup→org.jetbrains.dokka.links.DRIorg.jetbrains.dokka.javadoc.pages.JavadocContentNode→org.jetbrains.dokka.links.DRIorg.jetbrains.dokka.javadoc.pages.JavadocContentNodesKt→org.jetbrains.dokka.links.DRIorg.jetbrains.dokka.javadoc.pages.JavadocEntryNode→org.jetbrains.dokka.links.DRIorg.jetbrains.dokka.javadoc.pages.JavadocFunctionNode→org.jetbrains.dokka.links.DRIorg.jetbrains.dokka.javadoc.pages.JavadocModulePageNode→org.jetbrains.dokka.links.DRIorg.jetbrains.dokka.javadoc.pages.JavadocPackagePageNode→org.jetbrains.dokka.links.DRIorg.jetbrains.dokka.javadoc.pages.JavadocParameterNode→org.jetbrains.dokka.links.DRIorg.jetbrains.dokka.javadoc.pages.JavadocPropertyNode→org.jetbrains.dokka.links.DRIorg.jetbrains.dokka.javadoc.pages.JavadocSignatureContentNode→org.jetbrains.dokka.links.DRIorg.jetbrains.dokka.javadoc.pages.LeafListNode→org.jetbrains.dokka.links.DRIorg.jetbrains.dokka.javadoc.pages.LinkJavadocListEntry→org.jetbrains.dokka.links.DRIorg.jetbrains.dokka.javadoc.pages.NavigableJavadocNode→org.jetbrains.dokka.links.DRIorg.jetbrains.dokka.javadoc.pages.RootListNode→org.jetbrains.dokka.links.DRIorg.jetbrains.dokka.javadoc.pages.TitleNode→org.jetbrains.dokka.links.DRIorg.jetbrains.dokka.javadoc.pages.TreeViewPage→org.jetbrains.dokka.links.DRI
- Direction
- javadoc.pages uses links, so a change to links can break javadoc.pages, while a change to javadoc.pages can't break links.
- Position
- Below the diagonal: javadoc.pages uses a module listed above it, which is the healthy direction.
27→5 javadoc.pages uses model.properties.ExtraProperty✕
- Connections
- 1 pair of types, where a type in javadoc.pages uses a type in model.properties.ExtraProperty.
- The types involved
org.jetbrains.dokka.javadoc.pages.JavadocIndexExtra→org.jetbrains.dokka.model.properties.ExtraProperty.Key
- Direction
- javadoc.pages uses model.properties.ExtraProperty, so a change to model.properties.ExtraProperty can break javadoc.pages, while a change to javadoc.pages can't break model.properties.ExtraProperty.
- Position
- Below the diagonal: javadoc.pages uses a module listed above it, which is the healthy direction.
27→6 javadoc.pages uses plugability✕
- Connections
- 1 pair of types, where a type in javadoc.pages uses a type in plugability.
- The types involved
org.jetbrains.dokka.javadoc.pages.TreeViewInstaller→org.jetbrains.dokka.plugability.DokkaContext
- Direction
- javadoc.pages uses plugability, so a change to plugability can break javadoc.pages, while a change to javadoc.pages can't break plugability.
- Position
- Below the diagonal: javadoc.pages uses a module listed above it, which is the healthy direction.
27→9 javadoc.pages uses model.properties✕
- Connections
- 13 pairs of types, where a type in javadoc.pages uses a type in model.properties.
- The types involved
org.jetbrains.dokka.javadoc.pages.EmptyNode→org.jetbrains.dokka.model.properties.PropertyContainerorg.jetbrains.dokka.javadoc.pages.JavadocClasslikePageNode→org.jetbrains.dokka.model.properties.PropertyContainerorg.jetbrains.dokka.javadoc.pages.JavadocContentGroup→org.jetbrains.dokka.model.properties.PropertyContainerorg.jetbrains.dokka.javadoc.pages.JavadocContentNode→org.jetbrains.dokka.model.properties.PropertyContainerorg.jetbrains.dokka.javadoc.pages.JavadocEntryNode→org.jetbrains.dokka.model.properties.PropertyContainerorg.jetbrains.dokka.javadoc.pages.JavadocFunctionNode→org.jetbrains.dokka.model.properties.PropertyContainerorg.jetbrains.dokka.javadoc.pages.JavadocIndexExtra→org.jetbrains.dokka.model.properties.ExtraPropertyorg.jetbrains.dokka.javadoc.pages.JavadocModulePageNode→org.jetbrains.dokka.model.properties.PropertyContainerorg.jetbrains.dokka.javadoc.pages.JavadocParameterNode→org.jetbrains.dokka.model.properties.PropertyContainerorg.jetbrains.dokka.javadoc.pages.JavadocPropertyNode→org.jetbrains.dokka.model.properties.PropertyContainerorg.jetbrains.dokka.javadoc.pages.TitleNode→org.jetbrains.dokka.model.properties.PropertyContainerorg.jetbrains.dokka.javadoc.pages.WithJavadocExtra→org.jetbrains.dokka.model.properties.PropertyContainerorg.jetbrains.dokka.javadoc.pages.WithJavadocExtra→org.jetbrains.dokka.model.properties.WithExtraProperties
- Direction
- javadoc.pages uses model.properties, so a change to model.properties can break javadoc.pages, while a change to javadoc.pages can't break model.properties.
- Position
- Below the diagonal: javadoc.pages uses a module listed above it, which is the healthy direction.
27→11 javadoc.pages uses model✕
- Connections
- 26 pairs of types, where a type in javadoc.pages uses a type in model. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
org.jetbrains.dokka.javadoc.pages.AllClassesPage→org.jetbrains.dokka.model.Documentableorg.jetbrains.dokka.javadoc.pages.DeprecatedPage→org.jetbrains.dokka.model.DisplaySourceSetorg.jetbrains.dokka.javadoc.pages.DeprecatedPage→org.jetbrains.dokka.model.Documentableorg.jetbrains.dokka.javadoc.pages.EmptyNode→org.jetbrains.dokka.model.DisplaySourceSetorg.jetbrains.dokka.javadoc.pages.IndexPage→org.jetbrains.dokka.model.DisplaySourceSetorg.jetbrains.dokka.javadoc.pages.IndexPage→org.jetbrains.dokka.model.Documentableorg.jetbrains.dokka.javadoc.pages.JavaContentGroupBuilder→org.jetbrains.dokka.model.DisplaySourceSetorg.jetbrains.dokka.javadoc.pages.JavadocClasslikePageNode→org.jetbrains.dokka.model.DClasslikeorg.jetbrains.dokka.javadoc.pages.JavadocClasslikePageNode→org.jetbrains.dokka.model.Documentableorg.jetbrains.dokka.javadoc.pages.JavadocContentGroup→org.jetbrains.dokka.model.DisplaySourceSetorg.jetbrains.dokka.javadoc.pages.JavadocContentNode→org.jetbrains.dokka.model.DisplaySourceSetorg.jetbrains.dokka.javadoc.pages.JavadocEntryNode→org.jetbrains.dokka.model.DEnumEntryorg.jetbrains.dokka.javadoc.pages.JavadocFunctionNode→org.jetbrains.dokka.model.DFunctionorg.jetbrains.dokka.javadoc.pages.JavadocIndexExtra→org.jetbrains.dokka.model.Documentableorg.jetbrains.dokka.javadoc.pages.JavadocModulePageNode→org.jetbrains.dokka.model.DModuleorg.jetbrains.dokka.javadoc.pages.JavadocModulePageNode→org.jetbrains.dokka.model.Documentableorg.jetbrains.dokka.javadoc.pages.JavadocPackagePageNode→org.jetbrains.dokka.model.Documentableorg.jetbrains.dokka.javadoc.pages.JavadocParameterNode→org.jetbrains.dokka.model.Boundorg.jetbrains.dokka.javadoc.pages.JavadocParameterNode→org.jetbrains.dokka.model.DParameterorg.jetbrains.dokka.javadoc.pages.JavadocPropertyNode→org.jetbrains.dokka.model.DPropertyorg.jetbrains.dokka.javadoc.pages.JavadocSignatureContentNode→org.jetbrains.dokka.model.DisplaySourceSetorg.jetbrains.dokka.javadoc.pages.LeafListNode→org.jetbrains.dokka.model.DisplaySourceSetorg.jetbrains.dokka.javadoc.pages.LinkJavadocListEntry→org.jetbrains.dokka.model.DisplaySourceSetorg.jetbrains.dokka.javadoc.pages.RootListNode→org.jetbrains.dokka.model.DisplaySourceSetorg.jetbrains.dokka.javadoc.pages.TitleNode→org.jetbrains.dokka.model.DisplaySourceSet
- Direction
- javadoc.pages uses model, so a change to model can break javadoc.pages, while a change to javadoc.pages can't break model.
- Position
- Below the diagonal: javadoc.pages uses a module listed above it, which is the healthy direction.
27→13 javadoc.pages uses analysis.kotlin.internal✕
- Connections
- 2 pairs of types, where a type in javadoc.pages uses a type in analysis.kotlin.internal.
- The types involved
org.jetbrains.dokka.javadoc.pages.TreeViewPage→org.jetbrains.dokka.analysis.kotlin.internal.InheritanceBuilderorg.jetbrains.dokka.javadoc.pages.TreeViewPage→org.jetbrains.dokka.analysis.kotlin.internal.InheritanceNode
- Direction
- javadoc.pages uses analysis.kotlin.internal, so a change to analysis.kotlin.internal can break javadoc.pages, while a change to javadoc.pages can't break analysis.kotlin.internal.
- Position
- Below the diagonal: javadoc.pages uses a module listed above it, which is the healthy direction.
27→14 javadoc.pages uses pages✕
- Connections
- 62 pairs of types, where a type in javadoc.pages uses a type in pages. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
org.jetbrains.dokka.javadoc.pages.AllClassesPage→org.jetbrains.dokka.pages.ContentNodeorg.jetbrains.dokka.javadoc.pages.AllClassesPage→org.jetbrains.dokka.pages.ContentPageorg.jetbrains.dokka.javadoc.pages.AllClassesPage→org.jetbrains.dokka.pages.PageNodeorg.jetbrains.dokka.javadoc.pages.AllClassesPageInstaller→org.jetbrains.dokka.pages.RootPageNodeorg.jetbrains.dokka.javadoc.pages.DeprecatedNode→org.jetbrains.dokka.pages.ContentNodeorg.jetbrains.dokka.javadoc.pages.DeprecatedPage→org.jetbrains.dokka.pages.ContentNodeorg.jetbrains.dokka.javadoc.pages.DeprecatedPage→org.jetbrains.dokka.pages.ContentPageorg.jetbrains.dokka.javadoc.pages.DeprecatedPage→org.jetbrains.dokka.pages.PageNodeorg.jetbrains.dokka.javadoc.pages.DeprecatedPageCreator→org.jetbrains.dokka.pages.RootPageNodeorg.jetbrains.dokka.javadoc.pages.EmptyNode→org.jetbrains.dokka.pages.ContentNodeorg.jetbrains.dokka.javadoc.pages.EmptyNode→org.jetbrains.dokka.pages.DCIorg.jetbrains.dokka.javadoc.pages.EmptyNode→org.jetbrains.dokka.pages.Kindorg.jetbrains.dokka.javadoc.pages.EmptyNode→org.jetbrains.dokka.pages.Styleorg.jetbrains.dokka.javadoc.pages.IndexGenerator→org.jetbrains.dokka.pages.RootPageNodeorg.jetbrains.dokka.javadoc.pages.IndexPage→org.jetbrains.dokka.pages.ContentNodeorg.jetbrains.dokka.javadoc.pages.IndexPage→org.jetbrains.dokka.pages.ContentPageorg.jetbrains.dokka.javadoc.pages.IndexPage→org.jetbrains.dokka.pages.PageNodeorg.jetbrains.dokka.javadoc.pages.JavadocClasslikePageNode→org.jetbrains.dokka.pages.ClasslikePageorg.jetbrains.dokka.javadoc.pages.JavadocClasslikePageNode→org.jetbrains.dokka.pages.ContentNodeorg.jetbrains.dokka.javadoc.pages.JavadocClasslikePageNode→org.jetbrains.dokka.pages.ContentPageorg.jetbrains.dokka.javadoc.pages.JavadocClasslikePageNode→org.jetbrains.dokka.pages.PageNodeorg.jetbrains.dokka.javadoc.pages.JavadocContentGroup→org.jetbrains.dokka.pages.ContentNodeorg.jetbrains.dokka.javadoc.pages.JavadocContentGroup→org.jetbrains.dokka.pages.Kindorg.jetbrains.dokka.javadoc.pages.JavadocContentKind→org.jetbrains.dokka.pages.Kindorg.jetbrains.dokka.javadoc.pages.JavadocContentNode→org.jetbrains.dokka.pages.ContentNode
- Direction
- javadoc.pages uses pages, so a change to pages can break javadoc.pages, while a change to javadoc.pages can't break pages.
- Position
- Below the diagonal: javadoc.pages uses a module listed above it, which is the healthy direction.
27→21 javadoc.pages uses transformers.pages✕
- Connections
- 5 pairs of types, where a type in javadoc.pages uses a type in transformers.pages.
- The types involved
org.jetbrains.dokka.javadoc.pages.AllClassesPageInstaller→org.jetbrains.dokka.transformers.pages.PageTransformerorg.jetbrains.dokka.javadoc.pages.DeprecatedPageCreator→org.jetbrains.dokka.transformers.pages.PageTransformerorg.jetbrains.dokka.javadoc.pages.IndexGenerator→org.jetbrains.dokka.transformers.pages.PageTransformerorg.jetbrains.dokka.javadoc.pages.ResourcesInstaller→org.jetbrains.dokka.transformers.pages.PageTransformerorg.jetbrains.dokka.javadoc.pages.TreeViewInstaller→org.jetbrains.dokka.transformers.pages.PageTransformer
- Direction
- javadoc.pages uses transformers.pages, so a change to transformers.pages can break javadoc.pages, while a change to javadoc.pages can't break transformers.pages.
- Position
- Below the diagonal: javadoc.pages uses a module listed above it, which is the healthy direction.
28→3 templates uses DokkaConfiguration✕
- Connections
- 5 pairs of types, where a type in templates uses a type in DokkaConfiguration.
- The types involved
org.jetbrains.dokka.templates.DefaultSubmoduleTemplateProcessor→org.jetbrains.dokka.DokkaConfiguration.DokkaModuleDescriptionorg.jetbrains.dokka.templates.DirectiveBasedHtmlTemplateProcessingStrategy→org.jetbrains.dokka.DokkaConfiguration.DokkaModuleDescriptionorg.jetbrains.dokka.templates.FallbackTemplateProcessingStrategy→org.jetbrains.dokka.DokkaConfiguration.DokkaModuleDescriptionorg.jetbrains.dokka.templates.SubmoduleTemplateProcessor→org.jetbrains.dokka.DokkaConfiguration.DokkaModuleDescriptionorg.jetbrains.dokka.templates.TemplateProcessingStrategy→org.jetbrains.dokka.DokkaConfiguration.DokkaModuleDescription
- Direction
- templates uses DokkaConfiguration, so a change to DokkaConfiguration can break templates, while a change to templates can't break DokkaConfiguration.
- Position
- Below the diagonal: templates uses a module listed above it, which is the healthy direction.
28→6 templates uses plugability✕
- Connections
- 10 pairs of types, where a type in templates uses a type in plugability.
- The types involved
org.jetbrains.dokka.templates.AddToNavigationCommandHandler→org.jetbrains.dokka.plugability.DokkaContextorg.jetbrains.dokka.templates.DefaultMultiModuleTemplateProcessor→org.jetbrains.dokka.plugability.DokkaContextorg.jetbrains.dokka.templates.DefaultSubmoduleTemplateProcessor→org.jetbrains.dokka.plugability.DokkaContextorg.jetbrains.dokka.templates.DirectiveBasedHtmlTemplateProcessingStrategy→org.jetbrains.dokka.plugability.DokkaContextorg.jetbrains.dokka.templates.PathToRootSubstitutor→org.jetbrains.dokka.plugability.DokkaContextorg.jetbrains.dokka.templates.SubstitutionCommandHandler→org.jetbrains.dokka.plugability.DokkaContextorg.jetbrains.dokka.templates.TemplatingPlugin→org.jetbrains.dokka.plugability.DokkaPluginorg.jetbrains.dokka.templates.TemplatingPlugin→org.jetbrains.dokka.plugability.Extensionorg.jetbrains.dokka.templates.TemplatingPlugin→org.jetbrains.dokka.plugability.ExtensionPointorg.jetbrains.dokka.templates.TemplatingPlugin→org.jetbrains.dokka.plugability.PluginApiPreviewAcknowledgement
- Direction
- templates uses plugability, so a change to plugability can break templates, while a change to templates can't break plugability.
- Position
- Below the diagonal: templates uses a module listed above it, which is the healthy direction.
28→14 templates uses pages✕
- Connections
- 2 pairs of types, where a type in templates uses a type in pages.
- The types involved
org.jetbrains.dokka.templates.DefaultMultiModuleTemplateProcessor→org.jetbrains.dokka.pages.RootPageNodeorg.jetbrains.dokka.templates.MultiModuleTemplateProcessor→org.jetbrains.dokka.pages.RootPageNode
- Direction
- templates uses pages, so a change to pages can break templates, while a change to templates can't break pages.
- Position
- Below the diagonal: templates uses a module listed above it, which is the healthy direction.
28→16 templates uses base.resolvers.local✕
- Connections
- 1 pair of types, where a type in templates uses a type in base.resolvers.local.
- The types involved
org.jetbrains.dokka.templates.DefaultMultiModuleTemplateProcessor→org.jetbrains.dokka.base.resolvers.local.LocationProviderFactory
- Direction
- templates uses base.resolvers.local, so a change to base.resolvers.local can break templates, while a change to templates can't break base.resolvers.local.
- Position
- Below the diagonal: templates uses a module listed above it, which is the healthy direction.
28→17 templates uses base.templating✕
- Connections
- 7 pairs of types, where a type in templates uses a type in base.templating.
- The types involved
org.jetbrains.dokka.templates.AddToNavigationCommandHandler→org.jetbrains.dokka.base.templating.Commandorg.jetbrains.dokka.templates.CommandHandler→org.jetbrains.dokka.base.templating.Commandorg.jetbrains.dokka.templates.DirectiveBasedHtmlTemplateProcessingStrategy→org.jetbrains.dokka.base.templating.Commandorg.jetbrains.dokka.templates.PathToRootSubstitutor→org.jetbrains.dokka.base.templating.SubstitutionCommandorg.jetbrains.dokka.templates.SubstitutionCommandHandler→org.jetbrains.dokka.base.templating.Commandorg.jetbrains.dokka.templates.SubstitutionCommandHandler→org.jetbrains.dokka.base.templating.SubstitutionCommandorg.jetbrains.dokka.templates.Substitutor→org.jetbrains.dokka.base.templating.SubstitutionCommand
- Direction
- templates uses base.templating, so a change to base.templating can break templates, while a change to templates can't break base.templating.
- Position
- Below the diagonal: templates uses a module listed above it, which is the healthy direction.
29→1 analysis.kotlin.symbols.translators uses links✕
- Connections
- 5 pairs of types, where a type in analysis.kotlin.symbols.translators uses a type in links.
- The types involved
org.jetbrains.dokka.analysis.kotlin.symbols.translators.AnnotationTranslator→org.jetbrains.dokka.links.DRIorg.jetbrains.dokka.analysis.kotlin.symbols.translators.DRIFactoryKt→org.jetbrains.dokka.links.DRIorg.jetbrains.dokka.analysis.kotlin.symbols.translators.DRIFactoryKt→org.jetbrains.dokka.links.TypeReferenceorg.jetbrains.dokka.analysis.kotlin.symbols.translators.DokkaSymbolVisitor→org.jetbrains.dokka.links.DRIorg.jetbrains.dokka.analysis.kotlin.symbols.translators.TypeReferenceFactoryKt→org.jetbrains.dokka.links.TypeReference
- Direction
- analysis.kotlin.symbols.translators uses links, so a change to links can break analysis.kotlin.symbols.translators, while a change to analysis.kotlin.symbols.translators can't break links.
- Position
- Below the diagonal: analysis.kotlin.symbols.translators uses a module listed above it, which is the healthy direction.
29→2 analysis.kotlin.symbols.translators uses utilities✕
- Connections
- 3 pairs of types, where a type in analysis.kotlin.symbols.translators uses a type in utilities.
- The types involved
org.jetbrains.dokka.analysis.kotlin.symbols.translators.AnnotationTranslator→org.jetbrains.dokka.utilities.DokkaLoggerorg.jetbrains.dokka.analysis.kotlin.symbols.translators.DokkaSymbolVisitor→org.jetbrains.dokka.utilities.DokkaLoggerorg.jetbrains.dokka.analysis.kotlin.symbols.translators.TypeTranslator→org.jetbrains.dokka.utilities.DokkaLogger
- Direction
- analysis.kotlin.symbols.translators uses utilities, so a change to utilities can break analysis.kotlin.symbols.translators, while a change to analysis.kotlin.symbols.translators can't break utilities.
- Position
- Below the diagonal: analysis.kotlin.symbols.translators uses a module listed above it, which is the healthy direction.
29→3 analysis.kotlin.symbols.translators uses DokkaConfiguration✕
- Connections
- 3 pairs of types, where a type in analysis.kotlin.symbols.translators uses a type in DokkaConfiguration.
- The types involved
org.jetbrains.dokka.analysis.kotlin.symbols.translators.DefaultSymbolToDocumentableTranslator→org.jetbrains.dokka.DokkaConfiguration.DokkaSourceSetorg.jetbrains.dokka.analysis.kotlin.symbols.translators.DokkaSymbolVisitor→org.jetbrains.dokka.DokkaConfiguration.DokkaSourceSetorg.jetbrains.dokka.analysis.kotlin.symbols.translators.TypeTranslator→org.jetbrains.dokka.DokkaConfiguration.DokkaSourceSet
- Direction
- analysis.kotlin.symbols.translators uses DokkaConfiguration, so a change to DokkaConfiguration can break analysis.kotlin.symbols.translators, while a change to analysis.kotlin.symbols.translators can't break DokkaConfiguration.
- Position
- Below the diagonal: analysis.kotlin.symbols.translators uses a module listed above it, which is the healthy direction.
29→4 analysis.kotlin.symbols.translators uses model.doc✕
- Connections
- 2 pairs of types, where a type in analysis.kotlin.symbols.translators uses a type in model.doc.
- The types involved
org.jetbrains.dokka.analysis.kotlin.symbols.translators.DokkaSymbolVisitor→org.jetbrains.dokka.model.doc.DocumentationNodeorg.jetbrains.dokka.analysis.kotlin.symbols.translators.DokkaSymbolVisitor→org.jetbrains.dokka.model.doc.TagWrapper
- Direction
- analysis.kotlin.symbols.translators uses model.doc, so a change to model.doc can break analysis.kotlin.symbols.translators, while a change to analysis.kotlin.symbols.translators can't break model.doc.
- Position
- Below the diagonal: analysis.kotlin.symbols.translators uses a module listed above it, which is the healthy direction.
29→6 analysis.kotlin.symbols.translators uses plugability✕
- Connections
- 1 pair of types, where a type in analysis.kotlin.symbols.translators uses a type in plugability.
- The types involved
org.jetbrains.dokka.analysis.kotlin.symbols.translators.DefaultSymbolToDocumentableTranslator→org.jetbrains.dokka.plugability.DokkaContext
- Direction
- analysis.kotlin.symbols.translators uses plugability, so a change to plugability can break analysis.kotlin.symbols.translators, while a change to analysis.kotlin.symbols.translators can't break plugability.
- Position
- Below the diagonal: analysis.kotlin.symbols.translators uses a module listed above it, which is the healthy direction.
29→10 analysis.kotlin.symbols.translators uses model.Annotations✕
- Connections
- 4 pairs of types, where a type in analysis.kotlin.symbols.translators uses a type in model.Annotations.
- The types involved
org.jetbrains.dokka.analysis.kotlin.symbols.translators.AnnotationTranslator→org.jetbrains.dokka.model.Annotations.Annotationorg.jetbrains.dokka.analysis.kotlin.symbols.translators.AnnotationTranslator→org.jetbrains.dokka.model.Annotations.AnnotationScopeorg.jetbrains.dokka.analysis.kotlin.symbols.translators.DokkaSymbolVisitor→org.jetbrains.dokka.model.Annotations.Annotationorg.jetbrains.dokka.analysis.kotlin.symbols.translators.TypeTranslator→org.jetbrains.dokka.model.Annotations.Annotation
- Direction
- analysis.kotlin.symbols.translators uses model.Annotations, so a change to model.Annotations can break analysis.kotlin.symbols.translators, while a change to analysis.kotlin.symbols.translators can't break model.Annotations.
- Position
- Below the diagonal: analysis.kotlin.symbols.translators uses a module listed above it, which is the healthy direction.
29→11 analysis.kotlin.symbols.translators uses model✕
- Connections
- 27 pairs of types, where a type in analysis.kotlin.symbols.translators uses a type in model. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
org.jetbrains.dokka.analysis.kotlin.symbols.translators.AnnotationTranslator→org.jetbrains.dokka.model.AnnotationParameterValueorg.jetbrains.dokka.analysis.kotlin.symbols.translators.DefaultSymbolToDocumentableTranslator→org.jetbrains.dokka.model.DModuleorg.jetbrains.dokka.analysis.kotlin.symbols.translators.DefaultSymbolToDocumentableTranslatorKt→org.jetbrains.dokka.model.Varianceorg.jetbrains.dokka.analysis.kotlin.symbols.translators.DokkaSymbolVisitor→org.jetbrains.dokka.model.Boundorg.jetbrains.dokka.analysis.kotlin.symbols.translators.DokkaSymbolVisitor→org.jetbrains.dokka.model.CheckedExceptionsorg.jetbrains.dokka.analysis.kotlin.symbols.translators.DokkaSymbolVisitor→org.jetbrains.dokka.model.DClasslikeorg.jetbrains.dokka.analysis.kotlin.symbols.translators.DokkaSymbolVisitor→org.jetbrains.dokka.model.DEnumEntryorg.jetbrains.dokka.analysis.kotlin.symbols.translators.DokkaSymbolVisitor→org.jetbrains.dokka.model.DFunctionorg.jetbrains.dokka.analysis.kotlin.symbols.translators.DokkaSymbolVisitor→org.jetbrains.dokka.model.DModuleorg.jetbrains.dokka.analysis.kotlin.symbols.translators.DokkaSymbolVisitor→org.jetbrains.dokka.model.DPackageorg.jetbrains.dokka.analysis.kotlin.symbols.translators.DokkaSymbolVisitor→org.jetbrains.dokka.model.DParameterorg.jetbrains.dokka.analysis.kotlin.symbols.translators.DokkaSymbolVisitor→org.jetbrains.dokka.model.DPropertyorg.jetbrains.dokka.analysis.kotlin.symbols.translators.DokkaSymbolVisitor→org.jetbrains.dokka.model.DTypeAliasorg.jetbrains.dokka.analysis.kotlin.symbols.translators.DokkaSymbolVisitor→org.jetbrains.dokka.model.DTypeParameterorg.jetbrains.dokka.analysis.kotlin.symbols.translators.DokkaSymbolVisitor→org.jetbrains.dokka.model.DocumentableSourceorg.jetbrains.dokka.analysis.kotlin.symbols.translators.DokkaSymbolVisitor→org.jetbrains.dokka.model.ExceptionInSupertypesorg.jetbrains.dokka.analysis.kotlin.symbols.translators.DokkaSymbolVisitor→org.jetbrains.dokka.model.Expressionorg.jetbrains.dokka.analysis.kotlin.symbols.translators.DokkaSymbolVisitor→org.jetbrains.dokka.model.Modifierorg.jetbrains.dokka.analysis.kotlin.symbols.translators.DokkaSymbolVisitor→org.jetbrains.dokka.model.Visibilityorg.jetbrains.dokka.analysis.kotlin.symbols.translators.TypeTranslator→org.jetbrains.dokka.model.AncestryNodeorg.jetbrains.dokka.analysis.kotlin.symbols.translators.TypeTranslator→org.jetbrains.dokka.model.Boundorg.jetbrains.dokka.analysis.kotlin.symbols.translators.TypeTranslator→org.jetbrains.dokka.model.ClassKindorg.jetbrains.dokka.analysis.kotlin.symbols.translators.TypeTranslator→org.jetbrains.dokka.model.FunctionalTypeConstructororg.jetbrains.dokka.analysis.kotlin.symbols.translators.TypeTranslator→org.jetbrains.dokka.model.GenericTypeConstructororg.jetbrains.dokka.analysis.kotlin.symbols.translators.TypeTranslator→org.jetbrains.dokka.model.Projection
- Direction
- analysis.kotlin.symbols.translators uses model, so a change to model can break analysis.kotlin.symbols.translators, while a change to analysis.kotlin.symbols.translators can't break model.
- Position
- Below the diagonal: analysis.kotlin.symbols.translators uses a module listed above it, which is the healthy direction.
29→12 analysis.kotlin.symbols.translators uses analysis.java.parsers✕
- Connections
- 2 pairs of types, where a type in analysis.kotlin.symbols.translators uses a type in analysis.java.parsers.
- The types involved
org.jetbrains.dokka.analysis.kotlin.symbols.translators.DefaultSymbolToDocumentableTranslator→org.jetbrains.dokka.analysis.java.parsers.JavadocParserorg.jetbrains.dokka.analysis.kotlin.symbols.translators.DokkaSymbolVisitor→org.jetbrains.dokka.analysis.java.parsers.JavadocParser
- Direction
- analysis.kotlin.symbols.translators uses analysis.java.parsers, so a change to analysis.java.parsers can break analysis.kotlin.symbols.translators, while a change to analysis.kotlin.symbols.translators can't break analysis.java.parsers.
- Position
- Below the diagonal: analysis.kotlin.symbols.translators uses a module listed above it, which is the healthy direction.
29→15 analysis.kotlin.symbols.translators uses analysis.java✕
- Connections
- 3 pairs of types, where a type in analysis.kotlin.symbols.translators uses a type in analysis.java.
- The types involved
org.jetbrains.dokka.analysis.kotlin.symbols.translators.DefaultSymbolToDocumentableTranslator→org.jetbrains.dokka.analysis.java.BreakingAbstractionKotlinLightMethodCheckerorg.jetbrains.dokka.analysis.kotlin.symbols.translators.DokkaSymbolVisitor→org.jetbrains.dokka.analysis.java.BreakingAbstractionKotlinLightMethodCheckerorg.jetbrains.dokka.analysis.kotlin.symbols.translators.DokkaSymbolVisitor→org.jetbrains.dokka.analysis.java.SyntheticElementDocumentationProvider
- Direction
- analysis.kotlin.symbols.translators uses analysis.java, so a change to analysis.java can break analysis.kotlin.symbols.translators, while a change to analysis.kotlin.symbols.translators can't break analysis.java.
- Position
- Below the diagonal: analysis.kotlin.symbols.translators uses a module listed above it, which is the healthy direction.
29→23 analysis.kotlin.symbols.translators uses analysis.kotlin.symbols.plugin✕
- Connections
- 2 pairs of types, where a type in analysis.kotlin.symbols.translators uses a type in analysis.kotlin.symbols.plugin.
- The types involved
org.jetbrains.dokka.analysis.kotlin.symbols.translators.DefaultSymbolToDocumentableTranslator→org.jetbrains.dokka.analysis.kotlin.symbols.plugin.KotlinAnalysisorg.jetbrains.dokka.analysis.kotlin.symbols.translators.DokkaSymbolVisitor→org.jetbrains.dokka.analysis.kotlin.symbols.plugin.KotlinAnalysis
- Direction
- analysis.kotlin.symbols.translators uses analysis.kotlin.symbols.plugin, so a change to analysis.kotlin.symbols.plugin can break analysis.kotlin.symbols.translators, while a change to analysis.kotlin.symbols.translators can't break analysis.kotlin.symbols.plugin.
- Position
- Below the diagonal: analysis.kotlin.symbols.translators uses a module listed above it, which is the healthy direction.
30→1 base.renderers.html uses links✕
- Connections
- 3 pairs of types, where a type in base.renderers.html uses a type in links.
- The types involved
org.jetbrains.dokka.base.renderers.html.HtmlRenderer→org.jetbrains.dokka.links.DRIorg.jetbrains.dokka.base.renderers.html.NavigationNode→org.jetbrains.dokka.links.DRIorg.jetbrains.dokka.base.renderers.html.SearchbarDataInstallerKt→org.jetbrains.dokka.links.DRI
- Direction
- base.renderers.html uses links, so a change to links can break base.renderers.html, while a change to base.renderers.html can't break links.
- Position
- Below the diagonal: base.renderers.html uses a module listed above it, which is the healthy direction.
30→6 base.renderers.html uses plugability✕
- Connections
- 9 pairs of types, where a type in base.renderers.html uses a type in plugability.
- The types involved
org.jetbrains.dokka.base.renderers.html.CustomResourceInstaller→org.jetbrains.dokka.plugability.DokkaContextorg.jetbrains.dokka.base.renderers.html.HtmlRenderer→org.jetbrains.dokka.plugability.DokkaContextorg.jetbrains.dokka.base.renderers.html.NavigationDataProvider→org.jetbrains.dokka.plugability.DokkaContextorg.jetbrains.dokka.base.renderers.html.NavigationPage→org.jetbrains.dokka.plugability.DokkaContextorg.jetbrains.dokka.base.renderers.html.NavigationPageInstaller→org.jetbrains.dokka.plugability.DokkaContextorg.jetbrains.dokka.base.renderers.html.ScriptsInstaller→org.jetbrains.dokka.plugability.DokkaContextorg.jetbrains.dokka.base.renderers.html.SearchbarDataInstaller→org.jetbrains.dokka.plugability.DokkaContextorg.jetbrains.dokka.base.renderers.html.SourcesetDependencyAppender→org.jetbrains.dokka.plugability.DokkaContextorg.jetbrains.dokka.base.renderers.html.StylesInstaller→org.jetbrains.dokka.plugability.DokkaContext
- Direction
- base.renderers.html uses plugability, so a change to plugability can break base.renderers.html, while a change to base.renderers.html can't break plugability.
- Position
- Below the diagonal: base.renderers.html uses a module listed above it, which is the healthy direction.
30→9 base.renderers.html uses model.properties✕
- Connections
- 1 pair of types, where a type in base.renderers.html uses a type in model.properties.
- The types involved
org.jetbrains.dokka.base.renderers.html.HtmlRenderer→org.jetbrains.dokka.model.properties.PropertyContainer
- Direction
- base.renderers.html uses model.properties, so a change to model.properties can break base.renderers.html, while a change to base.renderers.html can't break model.properties.
- Position
- Below the diagonal: base.renderers.html uses a module listed above it, which is the healthy direction.
30→11 base.renderers.html uses model✕
- Connections
- 4 pairs of types, where a type in base.renderers.html uses a type in model.
- The types involved
org.jetbrains.dokka.base.renderers.html.HtmlRenderer→org.jetbrains.dokka.model.DisplaySourceSetorg.jetbrains.dokka.base.renderers.html.HtmlRenderer→org.jetbrains.dokka.model.Documentableorg.jetbrains.dokka.base.renderers.html.NavigationNode→org.jetbrains.dokka.model.DisplaySourceSetorg.jetbrains.dokka.base.renderers.html.NavigationNode→org.jetbrains.dokka.model.WithChildren
- Direction
- base.renderers.html uses model, so a change to model can break base.renderers.html, while a change to base.renderers.html can't break model.
- Position
- Below the diagonal: base.renderers.html uses a module listed above it, which is the healthy direction.
30→13 base.renderers.html uses analysis.kotlin.internal✕
- Connections
- 1 pair of types, where a type in base.renderers.html uses a type in analysis.kotlin.internal.
- The types involved
org.jetbrains.dokka.base.renderers.html.NavigationDataProvider→org.jetbrains.dokka.analysis.kotlin.internal.DocumentableSourceLanguageParser
- Direction
- base.renderers.html uses analysis.kotlin.internal, so a change to analysis.kotlin.internal can break base.renderers.html, while a change to base.renderers.html can't break analysis.kotlin.internal.
- Position
- Below the diagonal: base.renderers.html uses a module listed above it, which is the healthy direction.
30→14 base.renderers.html uses pages✕
- Connections
- 45 pairs of types, where a type in base.renderers.html uses a type in pages. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
org.jetbrains.dokka.base.renderers.html.AssetsInstaller→org.jetbrains.dokka.pages.RootPageNodeorg.jetbrains.dokka.base.renderers.html.ContentTab→org.jetbrains.dokka.pages.TabbedContentTypeorg.jetbrains.dokka.base.renderers.html.CustomResourceInstaller→org.jetbrains.dokka.pages.RendererSpecificResourcePageorg.jetbrains.dokka.base.renderers.html.CustomResourceInstaller→org.jetbrains.dokka.pages.RootPageNodeorg.jetbrains.dokka.base.renderers.html.HorizontalBreakLineStyle→org.jetbrains.dokka.pages.Styleorg.jetbrains.dokka.base.renderers.html.HtmlPreprocessorsKt→org.jetbrains.dokka.pages.RendererSpecificResourcePageorg.jetbrains.dokka.base.renderers.html.HtmlRenderer→org.jetbrains.dokka.pages.ClasslikePageorg.jetbrains.dokka.base.renderers.html.HtmlRenderer→org.jetbrains.dokka.pages.ContentBreakLineorg.jetbrains.dokka.base.renderers.html.HtmlRenderer→org.jetbrains.dokka.pages.ContentCodeBlockorg.jetbrains.dokka.base.renderers.html.HtmlRenderer→org.jetbrains.dokka.pages.ContentCodeInlineorg.jetbrains.dokka.base.renderers.html.HtmlRenderer→org.jetbrains.dokka.pages.ContentDRILinkorg.jetbrains.dokka.base.renderers.html.HtmlRenderer→org.jetbrains.dokka.pages.ContentDivergentGrouporg.jetbrains.dokka.base.renderers.html.HtmlRenderer→org.jetbrains.dokka.pages.ContentDivergentInstanceorg.jetbrains.dokka.base.renderers.html.HtmlRenderer→org.jetbrains.dokka.pages.ContentEmbeddedResourceorg.jetbrains.dokka.base.renderers.html.HtmlRenderer→org.jetbrains.dokka.pages.ContentGrouporg.jetbrains.dokka.base.renderers.html.HtmlRenderer→org.jetbrains.dokka.pages.ContentHeaderorg.jetbrains.dokka.base.renderers.html.HtmlRenderer→org.jetbrains.dokka.pages.ContentListorg.jetbrains.dokka.base.renderers.html.HtmlRenderer→org.jetbrains.dokka.pages.ContentNodeorg.jetbrains.dokka.base.renderers.html.HtmlRenderer→org.jetbrains.dokka.pages.ContentPageorg.jetbrains.dokka.base.renderers.html.HtmlRenderer→org.jetbrains.dokka.pages.ContentTableorg.jetbrains.dokka.base.renderers.html.HtmlRenderer→org.jetbrains.dokka.pages.ContentTextorg.jetbrains.dokka.base.renderers.html.HtmlRenderer→org.jetbrains.dokka.pages.PackagePageorg.jetbrains.dokka.base.renderers.html.HtmlRenderer→org.jetbrains.dokka.pages.PageNodeorg.jetbrains.dokka.base.renderers.html.HtmlRenderer→org.jetbrains.dokka.pages.PlatformHintedContentorg.jetbrains.dokka.base.renderers.html.HtmlRenderer→org.jetbrains.dokka.pages.RootPageNode
- Direction
- base.renderers.html uses pages, so a change to pages can break base.renderers.html, while a change to base.renderers.html can't break pages.
- Position
- Below the diagonal: base.renderers.html uses a module listed above it, which is the healthy direction.
30→17 base.renderers.html uses base.templating✕
- Connections
- 1 pair of types, where a type in base.renderers.html uses a type in base.templating.
- The types involved
org.jetbrains.dokka.base.renderers.html.TagsKt→org.jetbrains.dokka.base.templating.Command
- Direction
- base.renderers.html uses base.templating, so a change to base.templating can break base.renderers.html, while a change to base.renderers.html can't break base.templating.
- Position
- Below the diagonal: base.renderers.html uses a module listed above it, which is the healthy direction.
30→21 base.renderers.html uses transformers.pages✕
- Connections
- 8 pairs of types, where a type in base.renderers.html uses a type in transformers.pages.
- The types involved
org.jetbrains.dokka.base.renderers.html.AssetsInstaller→org.jetbrains.dokka.transformers.pages.PageTransformerorg.jetbrains.dokka.base.renderers.html.CustomResourceInstaller→org.jetbrains.dokka.transformers.pages.PageTransformerorg.jetbrains.dokka.base.renderers.html.HtmlRenderer→org.jetbrains.dokka.transformers.pages.PageTransformerorg.jetbrains.dokka.base.renderers.html.NavigationPageInstaller→org.jetbrains.dokka.transformers.pages.PageTransformerorg.jetbrains.dokka.base.renderers.html.ScriptsInstaller→org.jetbrains.dokka.transformers.pages.PageTransformerorg.jetbrains.dokka.base.renderers.html.SearchbarDataInstaller→org.jetbrains.dokka.transformers.pages.PageTransformerorg.jetbrains.dokka.base.renderers.html.SourcesetDependencyAppender→org.jetbrains.dokka.transformers.pages.PageTransformerorg.jetbrains.dokka.base.renderers.html.StylesInstaller→org.jetbrains.dokka.transformers.pages.PageTransformer
- Direction
- base.renderers.html uses transformers.pages, so a change to transformers.pages can break base.renderers.html, while a change to base.renderers.html can't break transformers.pages.
- Position
- Below the diagonal: base.renderers.html uses a module listed above it, which is the healthy direction.
30→22 base.renderers.html uses org.jetbrains.dokka✕
- Connections
- 1 pair of types, where a type in base.renderers.html uses a type in org.jetbrains.dokka.
- The types involved
org.jetbrains.dokka.base.renderers.html.HtmlRenderer→org.jetbrains.dokka.DokkaSourceSetID
- Direction
- base.renderers.html uses org.jetbrains.dokka, so a change to org.jetbrains.dokka can break base.renderers.html, while a change to base.renderers.html can't break org.jetbrains.dokka.
- Position
- Below the diagonal: base.renderers.html uses a module listed above it, which is the healthy direction.
30→24 base.renderers.html uses base.renderers✕
- Connections
- 1 pair of types, where a type in base.renderers.html uses a type in base.renderers.
- The types involved
org.jetbrains.dokka.base.renderers.html.HtmlRenderer→org.jetbrains.dokka.base.renderers.DefaultRenderer
- Direction
- base.renderers.html uses base.renderers, so a change to base.renderers can break base.renderers.html, while a change to base.renderers.html can't break base.renderers.
- Position
- Below the diagonal: base.renderers.html uses a module listed above it, which is the healthy direction.
30→35 base.renderers.html uses base part of a loop✕
- Connections
- 1 pair of types, where a type in base.renderers.html uses a type in base.
- The types involved
org.jetbrains.dokka.base.renderers.html.CustomResourceInstaller→org.jetbrains.dokka.base.DokkaBaseConfiguration
- Direction
- base.renderers.html uses base, so a change to base can break base.renderers.html, while a change to base.renderers.html can't break base.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
31→1 base.signatures uses links✕
- Connections
- 2 pairs of types, where a type in base.signatures uses a type in links.
- The types involved
org.jetbrains.dokka.base.signatures.KotlinSignatureProvider→org.jetbrains.dokka.links.DRIorg.jetbrains.dokka.base.signatures.KotlinSignatureUtils→org.jetbrains.dokka.links.DRI
- Direction
- base.signatures uses links, so a change to links can break base.signatures, while a change to base.signatures can't break links.
- Position
- Below the diagonal: base.signatures uses a module listed above it, which is the healthy direction.
31→2 base.signatures uses utilities✕
- Connections
- 1 pair of types, where a type in base.signatures uses a type in utilities.
- The types involved
org.jetbrains.dokka.base.signatures.KotlinSignatureProvider→org.jetbrains.dokka.utilities.DokkaLogger
- Direction
- base.signatures uses utilities, so a change to utilities can break base.signatures, while a change to base.signatures can't break utilities.
- Position
- Below the diagonal: base.signatures uses a module listed above it, which is the healthy direction.
31→3 base.signatures uses DokkaConfiguration✕
- Connections
- 3 pairs of types, where a type in base.signatures uses a type in DokkaConfiguration.
- The types involved
org.jetbrains.dokka.base.signatures.JvmSignatureUtils→org.jetbrains.dokka.DokkaConfiguration.DokkaSourceSetorg.jetbrains.dokka.base.signatures.KotlinSignatureProvider→org.jetbrains.dokka.DokkaConfiguration.DokkaSourceSetorg.jetbrains.dokka.base.signatures.KotlinSignatureUtils→org.jetbrains.dokka.DokkaConfiguration.DokkaSourceSet
- Direction
- base.signatures uses DokkaConfiguration, so a change to DokkaConfiguration can break base.signatures, while a change to base.signatures can't break DokkaConfiguration.
- Position
- Below the diagonal: base.signatures uses a module listed above it, which is the healthy direction.
31→6 base.signatures uses plugability✕
- Connections
- 1 pair of types, where a type in base.signatures uses a type in plugability.
- The types involved
org.jetbrains.dokka.base.signatures.KotlinSignatureProvider→org.jetbrains.dokka.plugability.DokkaContext
- Direction
- base.signatures uses plugability, so a change to plugability can break base.signatures, while a change to base.signatures can't break plugability.
- Position
- Below the diagonal: base.signatures uses a module listed above it, which is the healthy direction.
31→9 base.signatures uses model.properties✕
- Connections
- 1 pair of types, where a type in base.signatures uses a type in model.properties.
- The types involved
org.jetbrains.dokka.base.signatures.KotlinSignatureProvider→org.jetbrains.dokka.model.properties.WithExtraProperties
- Direction
- base.signatures uses model.properties, so a change to model.properties can break base.signatures, while a change to base.signatures can't break model.properties.
- Position
- Below the diagonal: base.signatures uses a module listed above it, which is the healthy direction.
31→10 base.signatures uses model.Annotations✕
- Connections
- 2 pairs of types, where a type in base.signatures uses a type in model.Annotations.
- The types involved
org.jetbrains.dokka.base.signatures.JvmSignatureUtils→org.jetbrains.dokka.model.Annotations.Annotationorg.jetbrains.dokka.base.signatures.KotlinSignatureUtils→org.jetbrains.dokka.model.Annotations.Annotation
- Direction
- base.signatures uses model.Annotations, so a change to model.Annotations can break base.signatures, while a change to base.signatures can't break model.Annotations.
- Position
- Below the diagonal: base.signatures uses a module listed above it, which is the healthy direction.
31→11 base.signatures uses model✕
- Connections
- 26 pairs of types, where a type in base.signatures uses a type in model. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
org.jetbrains.dokka.base.signatures.JvmSignatureUtils→org.jetbrains.dokka.model.AnnotationParameterValueorg.jetbrains.dokka.base.signatures.JvmSignatureUtils→org.jetbrains.dokka.model.AnnotationTargetorg.jetbrains.dokka.base.signatures.JvmSignatureUtils→org.jetbrains.dokka.model.Callableorg.jetbrains.dokka.base.signatures.JvmSignatureUtils→org.jetbrains.dokka.model.DFunctionorg.jetbrains.dokka.base.signatures.JvmSignatureUtils→org.jetbrains.dokka.model.DParameterorg.jetbrains.dokka.base.signatures.JvmSignatureUtils→org.jetbrains.dokka.model.DTypeParameterorg.jetbrains.dokka.base.signatures.JvmSignatureUtils→org.jetbrains.dokka.model.ExtraModifiersorg.jetbrains.dokka.base.signatures.KotlinSignatureProvider→org.jetbrains.dokka.model.Boundorg.jetbrains.dokka.base.signatures.KotlinSignatureProvider→org.jetbrains.dokka.model.DClasslikeorg.jetbrains.dokka.base.signatures.KotlinSignatureProvider→org.jetbrains.dokka.model.DEnumEntryorg.jetbrains.dokka.base.signatures.KotlinSignatureProvider→org.jetbrains.dokka.model.DFunctionorg.jetbrains.dokka.base.signatures.KotlinSignatureProvider→org.jetbrains.dokka.model.DPropertyorg.jetbrains.dokka.base.signatures.KotlinSignatureProvider→org.jetbrains.dokka.model.DTypeAliasorg.jetbrains.dokka.base.signatures.KotlinSignatureProvider→org.jetbrains.dokka.model.DTypeParameterorg.jetbrains.dokka.base.signatures.KotlinSignatureProvider→org.jetbrains.dokka.model.Documentableorg.jetbrains.dokka.base.signatures.KotlinSignatureProvider→org.jetbrains.dokka.model.Expressionorg.jetbrains.dokka.base.signatures.KotlinSignatureProvider→org.jetbrains.dokka.model.ExtraModifiersorg.jetbrains.dokka.base.signatures.KotlinSignatureProvider→org.jetbrains.dokka.model.FunctionalTypeConstructororg.jetbrains.dokka.base.signatures.KotlinSignatureProvider→org.jetbrains.dokka.model.Modifierorg.jetbrains.dokka.base.signatures.KotlinSignatureProvider→org.jetbrains.dokka.model.Projectionorg.jetbrains.dokka.base.signatures.KotlinSignatureProvider→org.jetbrains.dokka.model.Visibilityorg.jetbrains.dokka.base.signatures.KotlinSignatureProviderKt→org.jetbrains.dokka.model.Boundorg.jetbrains.dokka.base.signatures.KotlinSignatureProviderKt→org.jetbrains.dokka.model.GenericTypeConstructororg.jetbrains.dokka.base.signatures.KotlinSignatureUtils→org.jetbrains.dokka.model.AnnotationTargetorg.jetbrains.dokka.base.signatures.KotlinSignatureUtils→org.jetbrains.dokka.model.ExtraModifiers
- Direction
- base.signatures uses model, so a change to model can break base.signatures, while a change to base.signatures can't break model.
- Position
- Below the diagonal: base.signatures uses a module listed above it, which is the healthy direction.
31→14 base.signatures uses pages✕
- Connections
- 5 pairs of types, where a type in base.signatures uses a type in pages.
- The types involved
org.jetbrains.dokka.base.signatures.JvmSignatureUtils→org.jetbrains.dokka.pages.Styleorg.jetbrains.dokka.base.signatures.JvmSignatureUtils→org.jetbrains.dokka.pages.TextStyleorg.jetbrains.dokka.base.signatures.KotlinSignatureProvider→org.jetbrains.dokka.pages.ContentGrouporg.jetbrains.dokka.base.signatures.KotlinSignatureProvider→org.jetbrains.dokka.pages.ContentNodeorg.jetbrains.dokka.base.signatures.SignatureProvider→org.jetbrains.dokka.pages.ContentNode
- Direction
- base.signatures uses pages, so a change to pages can break base.signatures, while a change to base.signatures can't break pages.
- Position
- Below the diagonal: base.signatures uses a module listed above it, which is the healthy direction.
31→18 base.signatures uses base.transformers.pages.comments✕
- Connections
- 1 pair of types, where a type in base.signatures uses a type in base.transformers.pages.comments.
- The types involved
org.jetbrains.dokka.base.signatures.KotlinSignatureProvider→org.jetbrains.dokka.base.transformers.pages.comments.CommentsToContentConverter
- Direction
- base.signatures uses base.transformers.pages.comments, so a change to base.transformers.pages.comments can break base.signatures, while a change to base.signatures can't break base.transformers.pages.comments.
- Position
- Below the diagonal: base.signatures uses a module listed above it, which is the healthy direction.
31→22 base.signatures uses org.jetbrains.dokka✕
- Connections
- 1 pair of types, where a type in base.signatures uses a type in org.jetbrains.dokka.
- The types involved
org.jetbrains.dokka.base.signatures.KotlinSignatureProvider→org.jetbrains.dokka.Platform
- Direction
- base.signatures uses org.jetbrains.dokka, so a change to org.jetbrains.dokka can break base.signatures, while a change to base.signatures can't break org.jetbrains.dokka.
- Position
- Below the diagonal: base.signatures uses a module listed above it, which is the healthy direction.
31→26 base.signatures uses base.translators.documentables✕
- Connections
- 1 pair of types, where a type in base.signatures uses a type in base.translators.documentables.
- The types involved
org.jetbrains.dokka.base.signatures.KotlinSignatureProvider→org.jetbrains.dokka.base.translators.documentables.PageContentBuilder
- Direction
- base.signatures uses base.translators.documentables, so a change to base.translators.documentables can break base.signatures, while a change to base.signatures can't break base.translators.documentables.
- Position
- Below the diagonal: base.signatures uses a module listed above it, which is the healthy direction.
32→3 gradle uses DokkaConfiguration✕
- Connections
- 4 pairs of types, where a type in gradle uses a type in DokkaConfiguration.
- The types involved
org.jetbrains.dokka.gradle.AbstractDokkaTask→org.jetbrains.dokka.DokkaConfiguration.PluginConfigurationorg.jetbrains.dokka.gradle.GradleDokkaSourceSetBuilder→org.jetbrains.dokka.DokkaConfiguration.DokkaSourceSetorg.jetbrains.dokka.gradle.GradleDokkaSourceSetBuilder→org.jetbrains.dokka.DokkaConfiguration.Visibilityorg.jetbrains.dokka.gradle.GradlePackageOptionsBuilder→org.jetbrains.dokka.DokkaConfiguration.Visibility
- Direction
- gradle uses DokkaConfiguration, so a change to DokkaConfiguration can break gradle, while a change to gradle can't break DokkaConfiguration.
- Position
- Below the diagonal: gradle uses a module listed above it, which is the healthy direction.
32→22 gradle uses org.jetbrains.dokka✕
- Connections
- 21 pairs of types, where a type in gradle uses a type in org.jetbrains.dokka.
- The types involved
org.jetbrains.dokka.gradle.AbstractDokkaTask→org.jetbrains.dokka.DokkaConfigurationImplorg.jetbrains.dokka.gradle.AbstractDokkaTask→org.jetbrains.dokka.PluginConfigurationImplorg.jetbrains.dokka.gradle.CheckDependentSourceSetsKt→org.jetbrains.dokka.DokkaSourceSetIDorg.jetbrains.dokka.gradle.DokkaBootstrapFactoryKt→org.jetbrains.dokka.DokkaBootstraporg.jetbrains.dokka.gradle.DokkaCollectorTask→org.jetbrains.dokka.DokkaConfigurationImplorg.jetbrains.dokka.gradle.DokkaMultiModuleTask→org.jetbrains.dokka.DokkaConfigurationImplorg.jetbrains.dokka.gradle.DokkaSourceSetIDFactoryKt→org.jetbrains.dokka.DokkaSourceSetIDorg.jetbrains.dokka.gradle.DokkaSourceSetMapperKt→org.jetbrains.dokka.DokkaSourceSetImplorg.jetbrains.dokka.gradle.DokkaSourceSetMapperKt→org.jetbrains.dokka.ExternalDocumentationLinkImplorg.jetbrains.dokka.gradle.DokkaTask→org.jetbrains.dokka.DokkaConfigurationImplorg.jetbrains.dokka.gradle.DokkaTaskPartial→org.jetbrains.dokka.DokkaConfigurationImplorg.jetbrains.dokka.gradle.GradleDokkaSourceSetBuilder→org.jetbrains.dokka.DokkaConfigurationBuilderorg.jetbrains.dokka.gradle.GradleDokkaSourceSetBuilder→org.jetbrains.dokka.DokkaSourceSetIDorg.jetbrains.dokka.gradle.GradleDokkaSourceSetBuilder→org.jetbrains.dokka.DokkaSourceSetImplorg.jetbrains.dokka.gradle.GradleDokkaSourceSetBuilder→org.jetbrains.dokka.Platformorg.jetbrains.dokka.gradle.GradleExternalDocumentationLinkBuilder→org.jetbrains.dokka.DokkaConfigurationBuilderorg.jetbrains.dokka.gradle.GradleExternalDocumentationLinkBuilder→org.jetbrains.dokka.ExternalDocumentationLinkImplorg.jetbrains.dokka.gradle.GradlePackageOptionsBuilder→org.jetbrains.dokka.DokkaConfigurationBuilderorg.jetbrains.dokka.gradle.GradlePackageOptionsBuilder→org.jetbrains.dokka.PackageOptionsImplorg.jetbrains.dokka.gradle.GradleSourceLinkBuilder→org.jetbrains.dokka.DokkaConfigurationBuilderorg.jetbrains.dokka.gradle.GradleSourceLinkBuilder→org.jetbrains.dokka.SourceLinkDefinitionImpl
- Direction
- gradle uses org.jetbrains.dokka, so a change to org.jetbrains.dokka can break gradle, while a change to gradle can't break org.jetbrains.dokka.
- Position
- Below the diagonal: gradle uses a module listed above it, which is the healthy direction.
33→1 javadoc.renderer uses links✕
- Connections
- 1 pair of types, where a type in javadoc.renderer uses a type in links.
- The types involved
org.jetbrains.dokka.javadoc.renderer.SearchScriptsCreator→org.jetbrains.dokka.links.DRI
- Direction
- javadoc.renderer uses links, so a change to links can break javadoc.renderer, while a change to javadoc.renderer can't break links.
- Position
- Below the diagonal: javadoc.renderer uses a module listed above it, which is the healthy direction.
33→6 javadoc.renderer uses plugability✕
- Connections
- 3 pairs of types, where a type in javadoc.renderer uses a type in plugability.
- The types involved
org.jetbrains.dokka.javadoc.renderer.JavadocContentToHtmlTranslator→org.jetbrains.dokka.plugability.DokkaContextorg.jetbrains.dokka.javadoc.renderer.JavadocContentToTemplateMapTranslator→org.jetbrains.dokka.plugability.DokkaContextorg.jetbrains.dokka.javadoc.renderer.KorteJavadocRenderer→org.jetbrains.dokka.plugability.DokkaContext
- Direction
- javadoc.renderer uses plugability, so a change to plugability can break javadoc.renderer, while a change to javadoc.renderer can't break plugability.
- Position
- Below the diagonal: javadoc.renderer uses a module listed above it, which is the healthy direction.
33→11 javadoc.renderer uses model✕
- Connections
- 1 pair of types, where a type in javadoc.renderer uses a type in model.
- The types involved
org.jetbrains.dokka.javadoc.renderer.SearchScriptsCreator→org.jetbrains.dokka.model.DisplaySourceSet
- Direction
- javadoc.renderer uses model, so a change to model can break javadoc.renderer, while a change to javadoc.renderer can't break model.
- Position
- Below the diagonal: javadoc.renderer uses a module listed above it, which is the healthy direction.
33→14 javadoc.renderer uses pages✕
- Connections
- 13 pairs of types, where a type in javadoc.renderer uses a type in pages.
- The types involved
org.jetbrains.dokka.javadoc.renderer.JavadocContentToHtmlTranslator→org.jetbrains.dokka.pages.ContentCodeorg.jetbrains.dokka.javadoc.renderer.JavadocContentToHtmlTranslator→org.jetbrains.dokka.pages.ContentDRILinkorg.jetbrains.dokka.javadoc.renderer.JavadocContentToHtmlTranslator→org.jetbrains.dokka.pages.ContentNodeorg.jetbrains.dokka.javadoc.renderer.JavadocContentToHtmlTranslator→org.jetbrains.dokka.pages.ContentResolvedLinkorg.jetbrains.dokka.javadoc.renderer.JavadocContentToHtmlTranslator→org.jetbrains.dokka.pages.ContentTextorg.jetbrains.dokka.javadoc.renderer.JavadocContentToHtmlTranslator→org.jetbrains.dokka.pages.PageNodeorg.jetbrains.dokka.javadoc.renderer.KorteJavadocRenderer→org.jetbrains.dokka.pages.PageNodeorg.jetbrains.dokka.javadoc.renderer.KorteJavadocRenderer→org.jetbrains.dokka.pages.RendererSpecificPageorg.jetbrains.dokka.javadoc.renderer.KorteJavadocRenderer→org.jetbrains.dokka.pages.RootPageNodeorg.jetbrains.dokka.javadoc.renderer.SearchScriptsCreator→org.jetbrains.dokka.pages.ContentNodeorg.jetbrains.dokka.javadoc.renderer.SearchScriptsCreator→org.jetbrains.dokka.pages.RendererSpecificPageorg.jetbrains.dokka.javadoc.renderer.SearchScriptsCreator→org.jetbrains.dokka.pages.RootPageNodeorg.jetbrains.dokka.javadoc.renderer.SearchScriptsCreatorKt→org.jetbrains.dokka.pages.ContentNode
- Direction
- javadoc.renderer uses pages, so a change to pages can break javadoc.renderer, while a change to javadoc.renderer can't break pages.
- Position
- Below the diagonal: javadoc.renderer uses a module listed above it, which is the healthy direction.
33→16 javadoc.renderer uses base.resolvers.local✕
- Connections
- 2 pairs of types, where a type in javadoc.renderer uses a type in base.resolvers.local.
- The types involved
org.jetbrains.dokka.javadoc.renderer.JavadocContentToHtmlTranslator→org.jetbrains.dokka.base.resolvers.local.LocationProviderorg.jetbrains.dokka.javadoc.renderer.SearchScriptsCreator→org.jetbrains.dokka.base.resolvers.local.LocationProvider
- Direction
- javadoc.renderer uses base.resolvers.local, so a change to base.resolvers.local can break javadoc.renderer, while a change to javadoc.renderer can't break base.resolvers.local.
- Position
- Below the diagonal: javadoc.renderer uses a module listed above it, which is the healthy direction.
33→19 javadoc.renderer uses renderers✕
- Connections
- 1 pair of types, where a type in javadoc.renderer uses a type in renderers.
- The types involved
org.jetbrains.dokka.javadoc.renderer.KorteJavadocRenderer→org.jetbrains.dokka.renderers.Renderer
- Direction
- javadoc.renderer uses renderers, so a change to renderers can break javadoc.renderer, while a change to javadoc.renderer can't break renderers.
- Position
- Below the diagonal: javadoc.renderer uses a module listed above it, which is the healthy direction.
33→21 javadoc.renderer uses transformers.pages✕
- Connections
- 1 pair of types, where a type in javadoc.renderer uses a type in transformers.pages.
- The types involved
org.jetbrains.dokka.javadoc.renderer.KorteJavadocRenderer→org.jetbrains.dokka.transformers.pages.PageTransformer
- Direction
- javadoc.renderer uses transformers.pages, so a change to transformers.pages can break javadoc.renderer, while a change to javadoc.renderer can't break transformers.pages.
- Position
- Below the diagonal: javadoc.renderer uses a module listed above it, which is the healthy direction.
33→24 javadoc.renderer uses base.renderers✕
- Connections
- 1 pair of types, where a type in javadoc.renderer uses a type in base.renderers.
- The types involved
org.jetbrains.dokka.javadoc.renderer.KorteJavadocRenderer→org.jetbrains.dokka.base.renderers.OutputWriter
- Direction
- javadoc.renderer uses base.renderers, so a change to base.renderers can break javadoc.renderer, while a change to javadoc.renderer can't break base.renderers.
- Position
- Below the diagonal: javadoc.renderer uses a module listed above it, which is the healthy direction.
33→27 javadoc.renderer uses javadoc.pages✕
- Connections
- 11 pairs of types, where a type in javadoc.renderer uses a type in javadoc.pages.
- The types involved
org.jetbrains.dokka.javadoc.renderer.JavadocContentToHtmlTranslator→org.jetbrains.dokka.javadoc.pages.JavadocSignatureContentNodeorg.jetbrains.dokka.javadoc.renderer.JavadocContentToTemplateMapTranslator→org.jetbrains.dokka.javadoc.pages.JavadocPageNodeorg.jetbrains.dokka.javadoc.renderer.KorteJavadocRenderer→org.jetbrains.dokka.javadoc.pages.JavadocModulePageNodeorg.jetbrains.dokka.javadoc.renderer.KorteJavadocRenderer→org.jetbrains.dokka.javadoc.pages.JavadocPageNodeorg.jetbrains.dokka.javadoc.renderer.SearchRecordCreator→org.jetbrains.dokka.javadoc.pages.JavadocEntryNodeorg.jetbrains.dokka.javadoc.renderer.SearchRecordCreator→org.jetbrains.dokka.javadoc.pages.JavadocFunctionNodeorg.jetbrains.dokka.javadoc.renderer.SearchRecordCreator→org.jetbrains.dokka.javadoc.pages.JavadocPropertyNodeorg.jetbrains.dokka.javadoc.renderer.SearchScriptsCreator→org.jetbrains.dokka.javadoc.pages.JavadocClasslikePageNodeorg.jetbrains.dokka.javadoc.renderer.SearchScriptsCreator→org.jetbrains.dokka.javadoc.pages.JavadocFunctionNodeorg.jetbrains.dokka.javadoc.renderer.SearchScriptsCreator→org.jetbrains.dokka.javadoc.pages.JavadocModulePageNodeorg.jetbrains.dokka.javadoc.renderer.SearchScriptsCreator→org.jetbrains.dokka.javadoc.pages.JavadocPackagePageNode
- Direction
- javadoc.renderer uses javadoc.pages, so a change to javadoc.pages can break javadoc.renderer, while a change to javadoc.renderer can't break javadoc.pages.
- Position
- Below the diagonal: javadoc.renderer uses a module listed above it, which is the healthy direction.
34→1 analysis.kotlin.symbols.services uses links✕
- Connections
- 4 pairs of types, where a type in analysis.kotlin.symbols.services uses a type in links.
- The types involved
org.jetbrains.dokka.analysis.kotlin.symbols.services.SymbolExternalDocumentablesProvider→org.jetbrains.dokka.links.DRIorg.jetbrains.dokka.analysis.kotlin.symbols.services.SymbolFullClassHierarchyBuilder→org.jetbrains.dokka.links.DRIorg.jetbrains.dokka.analysis.kotlin.symbols.services.SymbolInheritanceBuilder→org.jetbrains.dokka.links.DRIorg.jetbrains.dokka.analysis.kotlin.symbols.services.SymbolKotlinToJavaMapper→org.jetbrains.dokka.links.DRI
- Direction
- analysis.kotlin.symbols.services uses links, so a change to links can break analysis.kotlin.symbols.services, while a change to analysis.kotlin.symbols.services can't break links.
- Position
- Below the diagonal: analysis.kotlin.symbols.services uses a module listed above it, which is the healthy direction.
34→2 analysis.kotlin.symbols.services uses utilities✕
- Connections
- 2 pairs of types, where a type in analysis.kotlin.symbols.services uses a type in utilities.
- The types involved
org.jetbrains.dokka.analysis.kotlin.symbols.services.SymbolFullClassHierarchyBuilder→org.jetbrains.dokka.utilities.DokkaLoggerorg.jetbrains.dokka.analysis.kotlin.symbols.services.SymbolSampleAnalysisEnvironment→org.jetbrains.dokka.utilities.DokkaLogger
- Direction
- analysis.kotlin.symbols.services uses utilities, so a change to utilities can break analysis.kotlin.symbols.services, while a change to analysis.kotlin.symbols.services can't break utilities.
- Position
- Below the diagonal: analysis.kotlin.symbols.services uses a module listed above it, which is the healthy direction.
34→3 analysis.kotlin.symbols.services uses DokkaConfiguration✕
- Connections
- 7 pairs of types, where a type in analysis.kotlin.symbols.services uses a type in DokkaConfiguration.
- The types involved
org.jetbrains.dokka.analysis.kotlin.symbols.services.KotlinAnalysisProjectProvider→org.jetbrains.dokka.DokkaConfiguration.DokkaSourceSetorg.jetbrains.dokka.analysis.kotlin.symbols.services.KotlinAnalysisSourceRootsExtractor→org.jetbrains.dokka.DokkaConfiguration.DokkaSourceSetorg.jetbrains.dokka.analysis.kotlin.symbols.services.KotlinDocumentableSourceLanguageParser→org.jetbrains.dokka.DokkaConfiguration.DokkaSourceSetorg.jetbrains.dokka.analysis.kotlin.symbols.services.SymbolExternalDocumentablesProvider→org.jetbrains.dokka.DokkaConfiguration.DokkaSourceSetorg.jetbrains.dokka.analysis.kotlin.symbols.services.SymbolFullClassHierarchyBuilder→org.jetbrains.dokka.DokkaConfiguration.DokkaSourceSetorg.jetbrains.dokka.analysis.kotlin.symbols.services.SymbolSampleAnalysisEnvironment→org.jetbrains.dokka.DokkaConfiguration.DokkaSourceSetorg.jetbrains.dokka.analysis.kotlin.symbols.services.SymbolSyntheticDocumentableDetector→org.jetbrains.dokka.DokkaConfiguration.DokkaSourceSet
- Direction
- analysis.kotlin.symbols.services uses DokkaConfiguration, so a change to DokkaConfiguration can break analysis.kotlin.symbols.services, while a change to analysis.kotlin.symbols.services can't break DokkaConfiguration.
- Position
- Below the diagonal: analysis.kotlin.symbols.services uses a module listed above it, which is the healthy direction.
34→6 analysis.kotlin.symbols.services uses plugability✕
- Connections
- 6 pairs of types, where a type in analysis.kotlin.symbols.services uses a type in plugability.
- The types involved
org.jetbrains.dokka.analysis.kotlin.symbols.services.KotlinAnalysisProjectProvider→org.jetbrains.dokka.plugability.DokkaContextorg.jetbrains.dokka.analysis.kotlin.symbols.services.KotlinAnalysisSourceRootsExtractor→org.jetbrains.dokka.plugability.DokkaContextorg.jetbrains.dokka.analysis.kotlin.symbols.services.SymbolExternalDocumentablesProvider→org.jetbrains.dokka.plugability.DokkaContextorg.jetbrains.dokka.analysis.kotlin.symbols.services.SymbolFullClassHierarchyBuilder→org.jetbrains.dokka.plugability.DokkaContextorg.jetbrains.dokka.analysis.kotlin.symbols.services.SymbolInheritanceBuilder→org.jetbrains.dokka.plugability.DokkaContextorg.jetbrains.dokka.analysis.kotlin.symbols.services.SymbolSampleAnalysisEnvironmentCreator→org.jetbrains.dokka.plugability.DokkaContext
- Direction
- analysis.kotlin.symbols.services uses plugability, so a change to plugability can break analysis.kotlin.symbols.services, while a change to analysis.kotlin.symbols.services can't break plugability.
- Position
- Below the diagonal: analysis.kotlin.symbols.services uses a module listed above it, which is the healthy direction.
34→11 analysis.kotlin.symbols.services uses model✕
- Connections
- 8 pairs of types, where a type in analysis.kotlin.symbols.services uses a type in model.
- The types involved
org.jetbrains.dokka.analysis.kotlin.symbols.services.KotlinDocumentableSourceLanguageParser→org.jetbrains.dokka.model.Documentableorg.jetbrains.dokka.analysis.kotlin.symbols.services.KtPsiDocumentableSource→org.jetbrains.dokka.model.DocumentableSourceorg.jetbrains.dokka.analysis.kotlin.symbols.services.SymbolExternalDocumentablesProvider→org.jetbrains.dokka.model.DClasslikeorg.jetbrains.dokka.analysis.kotlin.symbols.services.SymbolFullClassHierarchyBuilder→org.jetbrains.dokka.model.DModuleorg.jetbrains.dokka.analysis.kotlin.symbols.services.SymbolFullClassHierarchyBuilder→org.jetbrains.dokka.model.Documentableorg.jetbrains.dokka.analysis.kotlin.symbols.services.SymbolFullClassHierarchyBuilder→org.jetbrains.dokka.model.TypeConstructorWithKindorg.jetbrains.dokka.analysis.kotlin.symbols.services.SymbolInheritanceBuilder→org.jetbrains.dokka.model.Documentableorg.jetbrains.dokka.analysis.kotlin.symbols.services.SymbolSyntheticDocumentableDetector→org.jetbrains.dokka.model.Documentable
- Direction
- analysis.kotlin.symbols.services uses model, so a change to model can break analysis.kotlin.symbols.services, while a change to analysis.kotlin.symbols.services can't break model.
- Position
- Below the diagonal: analysis.kotlin.symbols.services uses a module listed above it, which is the healthy direction.
34→13 analysis.kotlin.symbols.services uses analysis.kotlin.internal✕
- Connections
- 8 pairs of types, where a type in analysis.kotlin.symbols.services uses a type in analysis.kotlin.internal.
- The types involved
org.jetbrains.dokka.analysis.kotlin.symbols.services.KotlinDocumentableSourceLanguageParser→org.jetbrains.dokka.analysis.kotlin.internal.DocumentableLanguageorg.jetbrains.dokka.analysis.kotlin.symbols.services.KotlinDocumentableSourceLanguageParser→org.jetbrains.dokka.analysis.kotlin.internal.DocumentableSourceLanguageParserorg.jetbrains.dokka.analysis.kotlin.symbols.services.SymbolFullClassHierarchyBuilder→org.jetbrains.dokka.analysis.kotlin.internal.FullClassHierarchyBuilderorg.jetbrains.dokka.analysis.kotlin.symbols.services.SymbolInheritanceBuilder→org.jetbrains.dokka.analysis.kotlin.internal.FullClassHierarchyBuilderorg.jetbrains.dokka.analysis.kotlin.symbols.services.SymbolInheritanceBuilder→org.jetbrains.dokka.analysis.kotlin.internal.InheritanceBuilderorg.jetbrains.dokka.analysis.kotlin.symbols.services.SymbolInheritanceBuilder→org.jetbrains.dokka.analysis.kotlin.internal.InheritanceNodeorg.jetbrains.dokka.analysis.kotlin.symbols.services.SymbolKotlinToJavaMapper→org.jetbrains.dokka.analysis.kotlin.internal.KotlinToJavaServiceorg.jetbrains.dokka.analysis.kotlin.symbols.services.SymbolSyntheticDocumentableDetector→org.jetbrains.dokka.analysis.kotlin.internal.SyntheticDocumentableDetector
- Direction
- analysis.kotlin.symbols.services uses analysis.kotlin.internal, so a change to analysis.kotlin.internal can break analysis.kotlin.symbols.services, while a change to analysis.kotlin.symbols.services can't break analysis.kotlin.internal.
- Position
- Below the diagonal: analysis.kotlin.symbols.services uses a module listed above it, which is the healthy direction.
34→15 analysis.kotlin.symbols.services uses analysis.java✕
- Connections
- 3 pairs of types, where a type in analysis.kotlin.symbols.services uses a type in analysis.java.
- The types involved
org.jetbrains.dokka.analysis.kotlin.symbols.services.KotlinAnalysisProjectProvider→org.jetbrains.dokka.analysis.java.ProjectProviderorg.jetbrains.dokka.analysis.kotlin.symbols.services.KotlinAnalysisSourceRootsExtractor→org.jetbrains.dokka.analysis.java.SourceRootsExtractororg.jetbrains.dokka.analysis.kotlin.symbols.services.SymbolExternalDocumentablesProvider→org.jetbrains.dokka.analysis.java.BreakingAbstractionKotlinLightMethodChecker
- Direction
- analysis.kotlin.symbols.services uses analysis.java, so a change to analysis.java can break analysis.kotlin.symbols.services, while a change to analysis.kotlin.symbols.services can't break analysis.java.
- Position
- Below the diagonal: analysis.kotlin.symbols.services uses a module listed above it, which is the healthy direction.
34→23 analysis.kotlin.symbols.services uses analysis.kotlin.symbols.plugin✕
- Connections
- 4 pairs of types, where a type in analysis.kotlin.symbols.services uses a type in analysis.kotlin.symbols.plugin.
- The types involved
org.jetbrains.dokka.analysis.kotlin.symbols.services.SymbolExternalDocumentablesProvider→org.jetbrains.dokka.analysis.kotlin.symbols.plugin.KotlinAnalysisorg.jetbrains.dokka.analysis.kotlin.symbols.services.SymbolFullClassHierarchyBuilder→org.jetbrains.dokka.analysis.kotlin.symbols.plugin.KotlinAnalysisorg.jetbrains.dokka.analysis.kotlin.symbols.services.SymbolSampleAnalysisEnvironment→org.jetbrains.dokka.analysis.kotlin.symbols.plugin.KotlinAnalysisorg.jetbrains.dokka.analysis.kotlin.symbols.services.SymbolSampleAnalysisEnvironmentCreator→org.jetbrains.dokka.analysis.kotlin.symbols.plugin.KotlinAnalysis
- Direction
- analysis.kotlin.symbols.services uses analysis.kotlin.symbols.plugin, so a change to analysis.kotlin.symbols.plugin can break analysis.kotlin.symbols.services, while a change to analysis.kotlin.symbols.services can't break analysis.kotlin.symbols.plugin.
- Position
- Below the diagonal: analysis.kotlin.symbols.services uses a module listed above it, which is the healthy direction.
34→29 analysis.kotlin.symbols.services uses analysis.kotlin.symbols.translators✕
- Connections
- 2 pairs of types, where a type in analysis.kotlin.symbols.services uses a type in analysis.kotlin.symbols.translators.
- The types involved
org.jetbrains.dokka.analysis.kotlin.symbols.services.SymbolFullClassHierarchyBuilder→org.jetbrains.dokka.analysis.kotlin.symbols.translators.Locationorg.jetbrains.dokka.analysis.kotlin.symbols.services.SymbolFullClassHierarchyBuilder→org.jetbrains.dokka.analysis.kotlin.symbols.translators.TypeTranslator
- Direction
- analysis.kotlin.symbols.services uses analysis.kotlin.symbols.translators, so a change to analysis.kotlin.symbols.translators can break analysis.kotlin.symbols.services, while a change to analysis.kotlin.symbols.services can't break analysis.kotlin.symbols.translators.
- Position
- Below the diagonal: analysis.kotlin.symbols.services uses a module listed above it, which is the healthy direction.
35→6 base uses plugability✕
- Connections
- 5 pairs of types, where a type in base uses a type in plugability.
- The types involved
org.jetbrains.dokka.base.DokkaBase→org.jetbrains.dokka.plugability.DokkaPluginorg.jetbrains.dokka.base.DokkaBase→org.jetbrains.dokka.plugability.Extensionorg.jetbrains.dokka.base.DokkaBase→org.jetbrains.dokka.plugability.ExtensionPointorg.jetbrains.dokka.base.DokkaBase→org.jetbrains.dokka.plugability.PluginApiPreviewAcknowledgementorg.jetbrains.dokka.base.DokkaBaseConfiguration→org.jetbrains.dokka.plugability.ConfigurableBlock
- Direction
- base uses plugability, so a change to plugability can break base, while a change to base can't break plugability.
- Position
- Below the diagonal: base uses a module listed above it, which is the healthy direction.
35→8 base uses base.resolvers.external✕
- Connections
- 1 pair of types, where a type in base uses a type in base.resolvers.external.
- The types involved
org.jetbrains.dokka.base.DokkaBase→org.jetbrains.dokka.base.resolvers.external.ExternalLocationProviderFactory
- Direction
- base uses base.resolvers.external, so a change to base.resolvers.external can break base, while a change to base can't break base.resolvers.external.
- Position
- Below the diagonal: base uses a module listed above it, which is the healthy direction.
35→16 base uses base.resolvers.local✕
- Connections
- 1 pair of types, where a type in base uses a type in base.resolvers.local.
- The types involved
org.jetbrains.dokka.base.DokkaBase→org.jetbrains.dokka.base.resolvers.local.LocationProviderFactory
- Direction
- base uses base.resolvers.local, so a change to base.resolvers.local can break base, while a change to base can't break base.resolvers.local.
- Position
- Below the diagonal: base uses a module listed above it, which is the healthy direction.
35→17 base uses base.templating✕
- Connections
- 1 pair of types, where a type in base uses a type in base.templating.
- The types involved
org.jetbrains.dokka.base.DokkaBase→org.jetbrains.dokka.base.templating.ImmediateHtmlCommandConsumer
- Direction
- base uses base.templating, so a change to base.templating can break base, while a change to base can't break base.templating.
- Position
- Below the diagonal: base uses a module listed above it, which is the healthy direction.
35→18 base uses base.transformers.pages.comments✕
- Connections
- 1 pair of types, where a type in base uses a type in base.transformers.pages.comments.
- The types involved
org.jetbrains.dokka.base.DokkaBase→org.jetbrains.dokka.base.transformers.pages.comments.CommentsToContentConverter
- Direction
- base uses base.transformers.pages.comments, so a change to base.transformers.pages.comments can break base, while a change to base can't break base.transformers.pages.comments.
- Position
- Below the diagonal: base uses a module listed above it, which is the healthy direction.
35→19 base uses renderers✕
- Connections
- 1 pair of types, where a type in base uses a type in renderers.
- The types involved
org.jetbrains.dokka.base.DokkaBase→org.jetbrains.dokka.renderers.Renderer
- Direction
- base uses renderers, so a change to renderers can break base, while a change to base can't break renderers.
- Position
- Below the diagonal: base uses a module listed above it, which is the healthy direction.
35→20 base uses transformers.documentation✕
- Connections
- 4 pairs of types, where a type in base uses a type in transformers.documentation.
- The types involved
org.jetbrains.dokka.base.DokkaBase→org.jetbrains.dokka.transformers.documentation.DocumentableMergerorg.jetbrains.dokka.base.DokkaBase→org.jetbrains.dokka.transformers.documentation.DocumentableToPageTranslatororg.jetbrains.dokka.base.DokkaBase→org.jetbrains.dokka.transformers.documentation.DocumentableTransformerorg.jetbrains.dokka.base.DokkaBase→org.jetbrains.dokka.transformers.documentation.PreMergeDocumentableTransformer
- Direction
- base uses transformers.documentation, so a change to transformers.documentation can break base, while a change to base can't break transformers.documentation.
- Position
- Below the diagonal: base uses a module listed above it, which is the healthy direction.
35→21 base uses transformers.pages✕
- Connections
- 1 pair of types, where a type in base uses a type in transformers.pages.
- The types involved
org.jetbrains.dokka.base.DokkaBase→org.jetbrains.dokka.transformers.pages.PageTransformer
- Direction
- base uses transformers.pages, so a change to transformers.pages can break base, while a change to base can't break transformers.pages.
- Position
- Below the diagonal: base uses a module listed above it, which is the healthy direction.
35→24 base uses base.renderers✕
- Connections
- 2 pairs of types, where a type in base uses a type in base.renderers.
- The types involved
org.jetbrains.dokka.base.DokkaBase→org.jetbrains.dokka.base.renderers.OutputWriterorg.jetbrains.dokka.base.DokkaBase→org.jetbrains.dokka.base.renderers.TabSortingStrategy
- Direction
- base uses base.renderers, so a change to base.renderers can break base, while a change to base can't break base.renderers.
- Position
- Below the diagonal: base uses a module listed above it, which is the healthy direction.
35→30 base uses base.renderers.html✕
- Connections
- 1 pair of types, where a type in base uses a type in base.renderers.html.
- The types involved
org.jetbrains.dokka.base.DokkaBase→org.jetbrains.dokka.base.renderers.html.HtmlCodeBlockRenderer
- Direction
- base uses base.renderers.html, so a change to base.renderers.html can break base, while a change to base can't break base.renderers.html.
- Position
- Below the diagonal: base uses a module listed above it, which is the healthy direction.
35→31 base uses base.signatures✕
- Connections
- 1 pair of types, where a type in base uses a type in base.signatures.
- The types involved
org.jetbrains.dokka.base.DokkaBase→org.jetbrains.dokka.base.signatures.SignatureProvider
- Direction
- base uses base.signatures, so a change to base.signatures can break base, while a change to base can't break base.signatures.
- Position
- Below the diagonal: base uses a module listed above it, which is the healthy direction.
36→2 javadoc.signatures uses utilities✕
- Connections
- 1 pair of types, where a type in javadoc.signatures uses a type in utilities.
- The types involved
org.jetbrains.dokka.javadoc.signatures.JavadocSignatureProvider→org.jetbrains.dokka.utilities.DokkaLogger
- Direction
- javadoc.signatures uses utilities, so a change to utilities can break javadoc.signatures, while a change to javadoc.signatures can't break utilities.
- Position
- Below the diagonal: javadoc.signatures uses a module listed above it, which is the healthy direction.
36→3 javadoc.signatures uses DokkaConfiguration✕
- Connections
- 1 pair of types, where a type in javadoc.signatures uses a type in DokkaConfiguration.
- The types involved
org.jetbrains.dokka.javadoc.signatures.JavadocSignatureProvider→org.jetbrains.dokka.DokkaConfiguration.DokkaSourceSet
- Direction
- javadoc.signatures uses DokkaConfiguration, so a change to DokkaConfiguration can break javadoc.signatures, while a change to javadoc.signatures can't break DokkaConfiguration.
- Position
- Below the diagonal: javadoc.signatures uses a module listed above it, which is the healthy direction.
36→6 javadoc.signatures uses plugability✕
- Connections
- 1 pair of types, where a type in javadoc.signatures uses a type in plugability.
- The types involved
org.jetbrains.dokka.javadoc.signatures.JavadocSignatureProvider→org.jetbrains.dokka.plugability.DokkaContext
- Direction
- javadoc.signatures uses plugability, so a change to plugability can break javadoc.signatures, while a change to javadoc.signatures can't break plugability.
- Position
- Below the diagonal: javadoc.signatures uses a module listed above it, which is the healthy direction.
36→9 javadoc.signatures uses model.properties✕
- Connections
- 1 pair of types, where a type in javadoc.signatures uses a type in model.properties.
- The types involved
org.jetbrains.dokka.javadoc.signatures.JavadocSignatureProvider→org.jetbrains.dokka.model.properties.PropertyContainer
- Direction
- javadoc.signatures uses model.properties, so a change to model.properties can break javadoc.signatures, while a change to javadoc.signatures can't break model.properties.
- Position
- Below the diagonal: javadoc.signatures uses a module listed above it, which is the healthy direction.
36→11 javadoc.signatures uses model✕
- Connections
- 9 pairs of types, where a type in javadoc.signatures uses a type in model.
- The types involved
org.jetbrains.dokka.javadoc.signatures.JavadocSignatureProvider→org.jetbrains.dokka.model.DClasslikeorg.jetbrains.dokka.javadoc.signatures.JavadocSignatureProvider→org.jetbrains.dokka.model.DEnumEntryorg.jetbrains.dokka.javadoc.signatures.JavadocSignatureProvider→org.jetbrains.dokka.model.DFunctionorg.jetbrains.dokka.javadoc.signatures.JavadocSignatureProvider→org.jetbrains.dokka.model.DParameterorg.jetbrains.dokka.javadoc.signatures.JavadocSignatureProvider→org.jetbrains.dokka.model.DPropertyorg.jetbrains.dokka.javadoc.signatures.JavadocSignatureProvider→org.jetbrains.dokka.model.DTypeParameterorg.jetbrains.dokka.javadoc.signatures.JavadocSignatureProvider→org.jetbrains.dokka.model.Documentableorg.jetbrains.dokka.javadoc.signatures.JavadocSignatureProvider→org.jetbrains.dokka.model.Modifierorg.jetbrains.dokka.javadoc.signatures.JavadocSignatureProvider→org.jetbrains.dokka.model.Projection
- Direction
- javadoc.signatures uses model, so a change to model can break javadoc.signatures, while a change to javadoc.signatures can't break model.
- Position
- Below the diagonal: javadoc.signatures uses a module listed above it, which is the healthy direction.
36→14 javadoc.signatures uses pages✕
- Connections
- 1 pair of types, where a type in javadoc.signatures uses a type in pages.
- The types involved
org.jetbrains.dokka.javadoc.signatures.JavadocSignatureProvider→org.jetbrains.dokka.pages.ContentNode
- Direction
- javadoc.signatures uses pages, so a change to pages can break javadoc.signatures, while a change to javadoc.signatures can't break pages.
- Position
- Below the diagonal: javadoc.signatures uses a module listed above it, which is the healthy direction.
36→18 javadoc.signatures uses base.transformers.pages.comments✕
- Connections
- 1 pair of types, where a type in javadoc.signatures uses a type in base.transformers.pages.comments.
- The types involved
org.jetbrains.dokka.javadoc.signatures.JavadocSignatureProvider→org.jetbrains.dokka.base.transformers.pages.comments.CommentsToContentConverter
- Direction
- javadoc.signatures uses base.transformers.pages.comments, so a change to base.transformers.pages.comments can break javadoc.signatures, while a change to javadoc.signatures can't break base.transformers.pages.comments.
- Position
- Below the diagonal: javadoc.signatures uses a module listed above it, which is the healthy direction.
36→31 javadoc.signatures uses base.signatures✕
- Connections
- 2 pairs of types, where a type in javadoc.signatures uses a type in base.signatures.
- The types involved
org.jetbrains.dokka.javadoc.signatures.JavadocSignatureProvider→org.jetbrains.dokka.base.signatures.JvmSignatureUtilsorg.jetbrains.dokka.javadoc.signatures.JavadocSignatureProvider→org.jetbrains.dokka.base.signatures.SignatureProvider
- Direction
- javadoc.signatures uses base.signatures, so a change to base.signatures can break javadoc.signatures, while a change to javadoc.signatures can't break base.signatures.
- Position
- Below the diagonal: javadoc.signatures uses a module listed above it, which is the healthy direction.
37→2 kotlinAsJava.signatures uses utilities✕
- Connections
- 1 pair of types, where a type in kotlinAsJava.signatures uses a type in utilities.
- The types involved
org.jetbrains.dokka.kotlinAsJava.signatures.JavaSignatureProvider→org.jetbrains.dokka.utilities.DokkaLogger
- Direction
- kotlinAsJava.signatures uses utilities, so a change to utilities can break kotlinAsJava.signatures, while a change to kotlinAsJava.signatures can't break utilities.
- Position
- Below the diagonal: kotlinAsJava.signatures uses a module listed above it, which is the healthy direction.
37→3 kotlinAsJava.signatures uses DokkaConfiguration✕
- Connections
- 1 pair of types, where a type in kotlinAsJava.signatures uses a type in DokkaConfiguration.
- The types involved
org.jetbrains.dokka.kotlinAsJava.signatures.JavaSignatureUtils→org.jetbrains.dokka.DokkaConfiguration.DokkaSourceSet
- Direction
- kotlinAsJava.signatures uses DokkaConfiguration, so a change to DokkaConfiguration can break kotlinAsJava.signatures, while a change to kotlinAsJava.signatures can't break DokkaConfiguration.
- Position
- Below the diagonal: kotlinAsJava.signatures uses a module listed above it, which is the healthy direction.
37→6 kotlinAsJava.signatures uses plugability✕
- Connections
- 1 pair of types, where a type in kotlinAsJava.signatures uses a type in plugability.
- The types involved
org.jetbrains.dokka.kotlinAsJava.signatures.JavaSignatureProvider→org.jetbrains.dokka.plugability.DokkaContext
- Direction
- kotlinAsJava.signatures uses plugability, so a change to plugability can break kotlinAsJava.signatures, while a change to kotlinAsJava.signatures can't break plugability.
- Position
- Below the diagonal: kotlinAsJava.signatures uses a module listed above it, which is the healthy direction.
37→10 kotlinAsJava.signatures uses model.Annotations✕
- Connections
- 1 pair of types, where a type in kotlinAsJava.signatures uses a type in model.Annotations.
- The types involved
org.jetbrains.dokka.kotlinAsJava.signatures.JavaSignatureUtils→org.jetbrains.dokka.model.Annotations.Annotation
- Direction
- kotlinAsJava.signatures uses model.Annotations, so a change to model.Annotations can break kotlinAsJava.signatures, while a change to kotlinAsJava.signatures can't break model.Annotations.
- Position
- Below the diagonal: kotlinAsJava.signatures uses a module listed above it, which is the healthy direction.
37→11 kotlinAsJava.signatures uses model✕
- Connections
- 9 pairs of types, where a type in kotlinAsJava.signatures uses a type in model.
- The types involved
org.jetbrains.dokka.kotlinAsJava.signatures.JavaSignatureProvider→org.jetbrains.dokka.model.DClasslikeorg.jetbrains.dokka.kotlinAsJava.signatures.JavaSignatureProvider→org.jetbrains.dokka.model.DEnumEntryorg.jetbrains.dokka.kotlinAsJava.signatures.JavaSignatureProvider→org.jetbrains.dokka.model.DFunctionorg.jetbrains.dokka.kotlinAsJava.signatures.JavaSignatureProvider→org.jetbrains.dokka.model.DPropertyorg.jetbrains.dokka.kotlinAsJava.signatures.JavaSignatureProvider→org.jetbrains.dokka.model.DTypeParameterorg.jetbrains.dokka.kotlinAsJava.signatures.JavaSignatureProvider→org.jetbrains.dokka.model.Documentableorg.jetbrains.dokka.kotlinAsJava.signatures.JavaSignatureProvider→org.jetbrains.dokka.model.Modifierorg.jetbrains.dokka.kotlinAsJava.signatures.JavaSignatureProvider→org.jetbrains.dokka.model.Projectionorg.jetbrains.dokka.kotlinAsJava.signatures.JavaSignatureUtils→org.jetbrains.dokka.model.AnnotationTarget
- Direction
- kotlinAsJava.signatures uses model, so a change to model can break kotlinAsJava.signatures, while a change to kotlinAsJava.signatures can't break model.
- Position
- Below the diagonal: kotlinAsJava.signatures uses a module listed above it, which is the healthy direction.
37→14 kotlinAsJava.signatures uses pages✕
- Connections
- 2 pairs of types, where a type in kotlinAsJava.signatures uses a type in pages.
- The types involved
org.jetbrains.dokka.kotlinAsJava.signatures.JavaSignatureProvider→org.jetbrains.dokka.pages.ContentGrouporg.jetbrains.dokka.kotlinAsJava.signatures.JavaSignatureProvider→org.jetbrains.dokka.pages.ContentNode
- Direction
- kotlinAsJava.signatures uses pages, so a change to pages can break kotlinAsJava.signatures, while a change to kotlinAsJava.signatures can't break pages.
- Position
- Below the diagonal: kotlinAsJava.signatures uses a module listed above it, which is the healthy direction.
37→18 kotlinAsJava.signatures uses base.transformers.pages.comments✕
- Connections
- 1 pair of types, where a type in kotlinAsJava.signatures uses a type in base.transformers.pages.comments.
- The types involved
org.jetbrains.dokka.kotlinAsJava.signatures.JavaSignatureProvider→org.jetbrains.dokka.base.transformers.pages.comments.CommentsToContentConverter
- Direction
- kotlinAsJava.signatures uses base.transformers.pages.comments, so a change to base.transformers.pages.comments can break kotlinAsJava.signatures, while a change to kotlinAsJava.signatures can't break base.transformers.pages.comments.
- Position
- Below the diagonal: kotlinAsJava.signatures uses a module listed above it, which is the healthy direction.
37→26 kotlinAsJava.signatures uses base.translators.documentables✕
- Connections
- 1 pair of types, where a type in kotlinAsJava.signatures uses a type in base.translators.documentables.
- The types involved
org.jetbrains.dokka.kotlinAsJava.signatures.JavaSignatureProvider→org.jetbrains.dokka.base.translators.documentables.PageContentBuilder
- Direction
- kotlinAsJava.signatures uses base.translators.documentables, so a change to base.translators.documentables can break kotlinAsJava.signatures, while a change to kotlinAsJava.signatures can't break base.translators.documentables.
- Position
- Below the diagonal: kotlinAsJava.signatures uses a module listed above it, which is the healthy direction.
37→31 kotlinAsJava.signatures uses base.signatures✕
- Connections
- 4 pairs of types, where a type in kotlinAsJava.signatures uses a type in base.signatures.
- The types involved
org.jetbrains.dokka.kotlinAsJava.signatures.JavaSignatureProvider→org.jetbrains.dokka.base.signatures.JvmSignatureUtilsorg.jetbrains.dokka.kotlinAsJava.signatures.JavaSignatureProvider→org.jetbrains.dokka.base.signatures.SignatureProviderorg.jetbrains.dokka.kotlinAsJava.signatures.JavaSignatureUtils→org.jetbrains.dokka.base.signatures.Allorg.jetbrains.dokka.kotlinAsJava.signatures.JavaSignatureUtils→org.jetbrains.dokka.base.signatures.JvmSignatureUtils
- Direction
- kotlinAsJava.signatures uses base.signatures, so a change to base.signatures can break kotlinAsJava.signatures, while a change to kotlinAsJava.signatures can't break base.signatures.
- Position
- Below the diagonal: kotlinAsJava.signatures uses a module listed above it, which is the healthy direction.
38→1 allModulesPage uses links✕
- Connections
- 3 pairs of types, where a type in allModulesPage uses a type in links.
- The types involved
org.jetbrains.dokka.allModulesPage.DefaultExternalModuleLinkResolver→org.jetbrains.dokka.links.DRIorg.jetbrains.dokka.allModulesPage.ExternalModuleLinkResolver→org.jetbrains.dokka.links.DRIorg.jetbrains.dokka.allModulesPage.MultimoduleLocationProvider→org.jetbrains.dokka.links.DRI
- Direction
- allModulesPage uses links, so a change to links can break allModulesPage, while a change to allModulesPage can't break links.
- Position
- Below the diagonal: allModulesPage uses a module listed above it, which is the healthy direction.
38→3 allModulesPage uses DokkaConfiguration✕
- Connections
- 2 pairs of types, where a type in allModulesPage uses a type in DokkaConfiguration.
- The types involved
org.jetbrains.dokka.allModulesPage.DefaultExternalModuleLinkResolver→org.jetbrains.dokka.DokkaConfiguration.DokkaModuleDescriptionorg.jetbrains.dokka.allModulesPage.MultimodulePageCreator→org.jetbrains.dokka.DokkaConfiguration.DokkaModuleDescription
- Direction
- allModulesPage uses DokkaConfiguration, so a change to DokkaConfiguration can break allModulesPage, while a change to allModulesPage can't break DokkaConfiguration.
- Position
- Below the diagonal: allModulesPage uses a module listed above it, which is the healthy direction.
38→4 allModulesPage uses model.doc✕
- Connections
- 2 pairs of types, where a type in allModulesPage uses a type in model.doc.
- The types involved
org.jetbrains.dokka.allModulesPage.MultimodulePageCreator→org.jetbrains.dokka.model.doc.DocumentationNodeorg.jetbrains.dokka.allModulesPage.MultimodulePageCreator→org.jetbrains.dokka.model.doc.P
- Direction
- allModulesPage uses model.doc, so a change to model.doc can break allModulesPage, while a change to allModulesPage can't break model.doc.
- Position
- Below the diagonal: allModulesPage uses a module listed above it, which is the healthy direction.
38→6 allModulesPage uses plugability✕
- Connections
- 9 pairs of types, where a type in allModulesPage uses a type in plugability.
- The types involved
org.jetbrains.dokka.allModulesPage.AllModulesPageGeneration→org.jetbrains.dokka.plugability.DokkaContextorg.jetbrains.dokka.allModulesPage.AllModulesPagePlugin→org.jetbrains.dokka.plugability.DokkaPluginorg.jetbrains.dokka.allModulesPage.AllModulesPagePlugin→org.jetbrains.dokka.plugability.Extensionorg.jetbrains.dokka.allModulesPage.AllModulesPagePlugin→org.jetbrains.dokka.plugability.ExtensionPointorg.jetbrains.dokka.allModulesPage.AllModulesPagePlugin→org.jetbrains.dokka.plugability.PluginApiPreviewAcknowledgementorg.jetbrains.dokka.allModulesPage.DefaultExternalModuleLinkResolver→org.jetbrains.dokka.plugability.DokkaContextorg.jetbrains.dokka.allModulesPage.MultimoduleLocationProvider→org.jetbrains.dokka.plugability.DokkaContextorg.jetbrains.dokka.allModulesPage.MultimodulePageCreator→org.jetbrains.dokka.plugability.DokkaContextorg.jetbrains.dokka.allModulesPage.ResolveLinkCommandHandler→org.jetbrains.dokka.plugability.DokkaContext
- Direction
- allModulesPage uses plugability, so a change to plugability can break allModulesPage, while a change to allModulesPage can't break plugability.
- Position
- Below the diagonal: allModulesPage uses a module listed above it, which is the healthy direction.
38→8 allModulesPage uses base.resolvers.external✕
- Connections
- 1 pair of types, where a type in allModulesPage uses a type in base.resolvers.external.
- The types involved
org.jetbrains.dokka.allModulesPage.DefaultExternalModuleLinkResolver→org.jetbrains.dokka.base.resolvers.external.ExternalLocationProviderFactory
- Direction
- allModulesPage uses base.resolvers.external, so a change to base.resolvers.external can break allModulesPage, while a change to allModulesPage can't break base.resolvers.external.
- Position
- Below the diagonal: allModulesPage uses a module listed above it, which is the healthy direction.
38→11 allModulesPage uses model✕
- Connections
- 1 pair of types, where a type in allModulesPage uses a type in model.
- The types involved
org.jetbrains.dokka.allModulesPage.MultimoduleLocationProvider→org.jetbrains.dokka.model.DisplaySourceSet
- Direction
- allModulesPage uses model, so a change to model can break allModulesPage, while a change to allModulesPage can't break model.
- Position
- Below the diagonal: allModulesPage uses a module listed above it, which is the healthy direction.
38→13 allModulesPage uses analysis.kotlin.internal✕
- Connections
- 1 pair of types, where a type in allModulesPage uses a type in analysis.kotlin.internal.
- The types involved
org.jetbrains.dokka.allModulesPage.MultimodulePageCreator→org.jetbrains.dokka.analysis.kotlin.internal.ModuleAndPackageDocumentationReader
- Direction
- allModulesPage uses analysis.kotlin.internal, so a change to analysis.kotlin.internal can break allModulesPage, while a change to allModulesPage can't break analysis.kotlin.internal.
- Position
- Below the diagonal: allModulesPage uses a module listed above it, which is the healthy direction.
38→14 allModulesPage uses pages✕
- Connections
- 4 pairs of types, where a type in allModulesPage uses a type in pages.
- The types involved
org.jetbrains.dokka.allModulesPage.AllModulesPageGeneration→org.jetbrains.dokka.pages.RootPageNodeorg.jetbrains.dokka.allModulesPage.MultimoduleLocationProvider→org.jetbrains.dokka.pages.PageNodeorg.jetbrains.dokka.allModulesPage.MultimoduleLocationProvider→org.jetbrains.dokka.pages.RootPageNodeorg.jetbrains.dokka.allModulesPage.MultimodulePageCreator→org.jetbrains.dokka.pages.RootPageNode
- Direction
- allModulesPage uses pages, so a change to pages can break allModulesPage, while a change to allModulesPage can't break pages.
- Position
- Below the diagonal: allModulesPage uses a module listed above it, which is the healthy direction.
38→16 allModulesPage uses base.resolvers.local✕
- Connections
- 3 pairs of types, where a type in allModulesPage uses a type in base.resolvers.local.
- The types involved
org.jetbrains.dokka.allModulesPage.AllModulesPagePlugin→org.jetbrains.dokka.base.resolvers.local.LocationProviderFactoryorg.jetbrains.dokka.allModulesPage.MultimoduleLocationProvider→org.jetbrains.dokka.base.resolvers.local.DokkaBaseLocationProviderorg.jetbrains.dokka.allModulesPage.MultimoduleLocationProvider→org.jetbrains.dokka.base.resolvers.local.LocationProvider
- Direction
- allModulesPage uses base.resolvers.local, so a change to base.resolvers.local can break allModulesPage, while a change to allModulesPage can't break base.resolvers.local.
- Position
- Below the diagonal: allModulesPage uses a module listed above it, which is the healthy direction.
38→17 allModulesPage uses base.templating✕
- Connections
- 1 pair of types, where a type in allModulesPage uses a type in base.templating.
- The types involved
org.jetbrains.dokka.allModulesPage.ResolveLinkCommandHandler→org.jetbrains.dokka.base.templating.Command
- Direction
- allModulesPage uses base.templating, so a change to base.templating can break allModulesPage, while a change to allModulesPage can't break base.templating.
- Position
- Below the diagonal: allModulesPage uses a module listed above it, which is the healthy direction.
38→18 allModulesPage uses base.transformers.pages.comments✕
- Connections
- 1 pair of types, where a type in allModulesPage uses a type in base.transformers.pages.comments.
- The types involved
org.jetbrains.dokka.allModulesPage.MultimodulePageCreator→org.jetbrains.dokka.base.transformers.pages.comments.CommentsToContentConverter
- Direction
- allModulesPage uses base.transformers.pages.comments, so a change to base.transformers.pages.comments can break allModulesPage, while a change to allModulesPage can't break base.transformers.pages.comments.
- Position
- Below the diagonal: allModulesPage uses a module listed above it, which is the healthy direction.
38→21 allModulesPage uses transformers.pages✕
- Connections
- 3 pairs of types, where a type in allModulesPage uses a type in transformers.pages.
- The types involved
org.jetbrains.dokka.allModulesPage.AllModulesPagePlugin→org.jetbrains.dokka.transformers.pages.PageCreatororg.jetbrains.dokka.allModulesPage.AllModulesPagePlugin→org.jetbrains.dokka.transformers.pages.PageTransformerorg.jetbrains.dokka.allModulesPage.MultimodulePageCreator→org.jetbrains.dokka.transformers.pages.PageCreator
- Direction
- allModulesPage uses transformers.pages, so a change to transformers.pages can break allModulesPage, while a change to allModulesPage can't break transformers.pages.
- Position
- Below the diagonal: allModulesPage uses a module listed above it, which is the healthy direction.
38→28 allModulesPage uses templates✕
- Connections
- 3 pairs of types, where a type in allModulesPage uses a type in templates.
- The types involved
org.jetbrains.dokka.allModulesPage.AllModulesPageGeneration→org.jetbrains.dokka.templates.TemplatingPluginorg.jetbrains.dokka.allModulesPage.AllModulesPagePlugin→org.jetbrains.dokka.templates.CommandHandlerorg.jetbrains.dokka.allModulesPage.ResolveLinkCommandHandler→org.jetbrains.dokka.templates.CommandHandler
- Direction
- allModulesPage uses templates, so a change to templates can break allModulesPage, while a change to allModulesPage can't break templates.
- Position
- Below the diagonal: allModulesPage uses a module listed above it, which is the healthy direction.
38→31 allModulesPage uses base.signatures✕
- Connections
- 1 pair of types, where a type in allModulesPage uses a type in base.signatures.
- The types involved
org.jetbrains.dokka.allModulesPage.MultimodulePageCreator→org.jetbrains.dokka.base.signatures.SignatureProvider
- Direction
- allModulesPage uses base.signatures, so a change to base.signatures can break allModulesPage, while a change to allModulesPage can't break base.signatures.
- Position
- Below the diagonal: allModulesPage uses a module listed above it, which is the healthy direction.
38→35 allModulesPage uses base✕
- Connections
- 1 pair of types, where a type in allModulesPage uses a type in base.
- The types involved
org.jetbrains.dokka.allModulesPage.AllModulesPagePlugin→org.jetbrains.dokka.base.DokkaBase
- Direction
- allModulesPage uses base, so a change to base can break allModulesPage, while a change to allModulesPage can't break base.
- Position
- Below the diagonal: allModulesPage uses a module listed above it, which is the healthy direction.
39→3 javadoc uses DokkaConfiguration✕
- Connections
- 1 pair of types, where a type in javadoc uses a type in DokkaConfiguration.
- The types involved
org.jetbrains.dokka.javadoc.JavadocPageCreator→org.jetbrains.dokka.DokkaConfiguration.DokkaSourceSet
- Direction
- javadoc uses DokkaConfiguration, so a change to DokkaConfiguration can break javadoc, while a change to javadoc can't break DokkaConfiguration.
- Position
- Below the diagonal: javadoc uses a module listed above it, which is the healthy direction.
39→6 javadoc uses plugability✕
- Connections
- 6 pairs of types, where a type in javadoc uses a type in plugability.
- The types involved
org.jetbrains.dokka.javadoc.JavadocDocumentableToPageTranslator→org.jetbrains.dokka.plugability.DokkaContextorg.jetbrains.dokka.javadoc.JavadocPageCreator→org.jetbrains.dokka.plugability.DokkaContextorg.jetbrains.dokka.javadoc.JavadocPlugin→org.jetbrains.dokka.plugability.DokkaPluginorg.jetbrains.dokka.javadoc.JavadocPlugin→org.jetbrains.dokka.plugability.Extensionorg.jetbrains.dokka.javadoc.JavadocPlugin→org.jetbrains.dokka.plugability.ExtensionPointorg.jetbrains.dokka.javadoc.JavadocPlugin→org.jetbrains.dokka.plugability.PluginApiPreviewAcknowledgement
- Direction
- javadoc uses plugability, so a change to plugability can break javadoc, while a change to javadoc can't break plugability.
- Position
- Below the diagonal: javadoc uses a module listed above it, which is the healthy direction.
39→11 javadoc uses model✕
- Connections
- 5 pairs of types, where a type in javadoc uses a type in model.
- The types involved
org.jetbrains.dokka.javadoc.JavadocDocumentableToPageTranslator→org.jetbrains.dokka.model.DModuleorg.jetbrains.dokka.javadoc.JavadocPageCreator→org.jetbrains.dokka.model.DClasslikeorg.jetbrains.dokka.javadoc.JavadocPageCreator→org.jetbrains.dokka.model.DModuleorg.jetbrains.dokka.javadoc.JavadocPageCreator→org.jetbrains.dokka.model.DPackageorg.jetbrains.dokka.javadoc.JavadocPageCreator→org.jetbrains.dokka.model.Documentable
- Direction
- javadoc uses model, so a change to model can break javadoc, while a change to javadoc can't break model.
- Position
- Below the diagonal: javadoc uses a module listed above it, which is the healthy direction.
39→14 javadoc uses pages✕
- Connections
- 2 pairs of types, where a type in javadoc uses a type in pages.
- The types involved
org.jetbrains.dokka.javadoc.JavadocDocumentableToPageTranslator→org.jetbrains.dokka.pages.RootPageNodeorg.jetbrains.dokka.javadoc.JavadocPageCreator→org.jetbrains.dokka.pages.ContentNode
- Direction
- javadoc uses pages, so a change to pages can break javadoc, while a change to javadoc can't break pages.
- Position
- Below the diagonal: javadoc uses a module listed above it, which is the healthy direction.
39→16 javadoc uses base.resolvers.local✕
- Connections
- 1 pair of types, where a type in javadoc uses a type in base.resolvers.local.
- The types involved
org.jetbrains.dokka.javadoc.JavadocPlugin→org.jetbrains.dokka.base.resolvers.local.LocationProviderFactory
- Direction
- javadoc uses base.resolvers.local, so a change to base.resolvers.local can break javadoc, while a change to javadoc can't break base.resolvers.local.
- Position
- Below the diagonal: javadoc uses a module listed above it, which is the healthy direction.
39→19 javadoc uses renderers✕
- Connections
- 2 pairs of types, where a type in javadoc uses a type in renderers.
- The types involved
org.jetbrains.dokka.javadoc.JavadocPlugin→org.jetbrains.dokka.renderers.PostActionorg.jetbrains.dokka.javadoc.JavadocPlugin→org.jetbrains.dokka.renderers.Renderer
- Direction
- javadoc uses renderers, so a change to renderers can break javadoc, while a change to javadoc can't break renderers.
- Position
- Below the diagonal: javadoc uses a module listed above it, which is the healthy direction.
39→20 javadoc uses transformers.documentation✕
- Connections
- 3 pairs of types, where a type in javadoc uses a type in transformers.documentation.
- The types involved
org.jetbrains.dokka.javadoc.JavadocDocumentableToPageTranslator→org.jetbrains.dokka.transformers.documentation.DocumentableToPageTranslatororg.jetbrains.dokka.javadoc.JavadocPlugin→org.jetbrains.dokka.transformers.documentation.DocumentableToPageTranslatororg.jetbrains.dokka.javadoc.JavadocPlugin→org.jetbrains.dokka.transformers.documentation.PreMergeDocumentableTransformer
- Direction
- javadoc uses transformers.documentation, so a change to transformers.documentation can break javadoc, while a change to javadoc can't break transformers.documentation.
- Position
- Below the diagonal: javadoc uses a module listed above it, which is the healthy direction.
39→21 javadoc uses transformers.pages✕
- Connections
- 1 pair of types, where a type in javadoc uses a type in transformers.pages.
- The types involved
org.jetbrains.dokka.javadoc.JavadocPlugin→org.jetbrains.dokka.transformers.pages.PageTransformer
- Direction
- javadoc uses transformers.pages, so a change to transformers.pages can break javadoc, while a change to javadoc can't break transformers.pages.
- Position
- Below the diagonal: javadoc uses a module listed above it, which is the healthy direction.
39→27 javadoc uses javadoc.pages✕
- Connections
- 7 pairs of types, where a type in javadoc uses a type in javadoc.pages.
- The types involved
org.jetbrains.dokka.javadoc.JavadocPageCreator→org.jetbrains.dokka.javadoc.pages.JavadocClasslikePageNodeorg.jetbrains.dokka.javadoc.JavadocPageCreator→org.jetbrains.dokka.javadoc.pages.JavadocContentNodeorg.jetbrains.dokka.javadoc.JavadocPageCreator→org.jetbrains.dokka.javadoc.pages.JavadocFunctionNodeorg.jetbrains.dokka.javadoc.JavadocPageCreator→org.jetbrains.dokka.javadoc.pages.JavadocIndexExtraorg.jetbrains.dokka.javadoc.JavadocPageCreator→org.jetbrains.dokka.javadoc.pages.JavadocModulePageNodeorg.jetbrains.dokka.javadoc.JavadocPageCreator→org.jetbrains.dokka.javadoc.pages.JavadocPackagePageNodeorg.jetbrains.dokka.javadoc.JavadocPageCreator→org.jetbrains.dokka.javadoc.pages.JavadocSignatureContentNode
- Direction
- javadoc uses javadoc.pages, so a change to javadoc.pages can break javadoc, while a change to javadoc can't break javadoc.pages.
- Position
- Below the diagonal: javadoc uses a module listed above it, which is the healthy direction.
39→31 javadoc uses base.signatures✕
- Connections
- 2 pairs of types, where a type in javadoc uses a type in base.signatures.
- The types involved
org.jetbrains.dokka.javadoc.JavadocPageCreator→org.jetbrains.dokka.base.signatures.SignatureProviderorg.jetbrains.dokka.javadoc.JavadocPlugin→org.jetbrains.dokka.base.signatures.SignatureProvider
- Direction
- javadoc uses base.signatures, so a change to base.signatures can break javadoc, while a change to javadoc can't break base.signatures.
- Position
- Below the diagonal: javadoc uses a module listed above it, which is the healthy direction.
39→35 javadoc uses base✕
- Connections
- 1 pair of types, where a type in javadoc uses a type in base.
- The types involved
org.jetbrains.dokka.javadoc.JavadocPlugin→org.jetbrains.dokka.base.DokkaBase
- Direction
- javadoc uses base, so a change to base can break javadoc, while a change to javadoc can't break base.
- Position
- Below the diagonal: javadoc uses a module listed above it, which is the healthy direction.
40→2 kotlinAsJava.translators uses utilities✕
- Connections
- 2 pairs of types, where a type in kotlinAsJava.translators uses a type in utilities.
- The types involved
org.jetbrains.dokka.kotlinAsJava.translators.KotlinAsJavaDocumentableToPageTranslator→org.jetbrains.dokka.utilities.DokkaLoggerorg.jetbrains.dokka.kotlinAsJava.translators.KotlinAsJavaPageCreator→org.jetbrains.dokka.utilities.DokkaLogger
- Direction
- kotlinAsJava.translators uses utilities, so a change to utilities can break kotlinAsJava.translators, while a change to kotlinAsJava.translators can't break utilities.
- Position
- Below the diagonal: kotlinAsJava.translators uses a module listed above it, which is the healthy direction.
40→6 kotlinAsJava.translators uses plugability✕
- Connections
- 1 pair of types, where a type in kotlinAsJava.translators uses a type in plugability.
- The types involved
org.jetbrains.dokka.kotlinAsJava.translators.KotlinAsJavaDocumentableToPageTranslator→org.jetbrains.dokka.plugability.DokkaContext
- Direction
- kotlinAsJava.translators uses plugability, so a change to plugability can break kotlinAsJava.translators, while a change to kotlinAsJava.translators can't break plugability.
- Position
- Below the diagonal: kotlinAsJava.translators uses a module listed above it, which is the healthy direction.
40→11 kotlinAsJava.translators uses model✕
- Connections
- 2 pairs of types, where a type in kotlinAsJava.translators uses a type in model.
- The types involved
org.jetbrains.dokka.kotlinAsJava.translators.KotlinAsJavaDocumentableToPageTranslator→org.jetbrains.dokka.model.DModuleorg.jetbrains.dokka.kotlinAsJava.translators.KotlinAsJavaPageCreator→org.jetbrains.dokka.model.DProperty
- Direction
- kotlinAsJava.translators uses model, so a change to model can break kotlinAsJava.translators, while a change to kotlinAsJava.translators can't break model.
- Position
- Below the diagonal: kotlinAsJava.translators uses a module listed above it, which is the healthy direction.
40→13 kotlinAsJava.translators uses analysis.kotlin.internal✕
- Connections
- 2 pairs of types, where a type in kotlinAsJava.translators uses a type in analysis.kotlin.internal.
- The types involved
org.jetbrains.dokka.kotlinAsJava.translators.KotlinAsJavaDocumentableToPageTranslator→org.jetbrains.dokka.analysis.kotlin.internal.DocumentableSourceLanguageParserorg.jetbrains.dokka.kotlinAsJava.translators.KotlinAsJavaPageCreator→org.jetbrains.dokka.analysis.kotlin.internal.DocumentableSourceLanguageParser
- Direction
- kotlinAsJava.translators uses analysis.kotlin.internal, so a change to analysis.kotlin.internal can break kotlinAsJava.translators, while a change to kotlinAsJava.translators can't break analysis.kotlin.internal.
- Position
- Below the diagonal: kotlinAsJava.translators uses a module listed above it, which is the healthy direction.
40→14 kotlinAsJava.translators uses pages✕
- Connections
- 2 pairs of types, where a type in kotlinAsJava.translators uses a type in pages.
- The types involved
org.jetbrains.dokka.kotlinAsJava.translators.KotlinAsJavaDocumentableToPageTranslator→org.jetbrains.dokka.pages.ModulePageNodeorg.jetbrains.dokka.kotlinAsJava.translators.KotlinAsJavaPageCreator→org.jetbrains.dokka.pages.MemberPageNode
- Direction
- kotlinAsJava.translators uses pages, so a change to pages can break kotlinAsJava.translators, while a change to kotlinAsJava.translators can't break pages.
- Position
- Below the diagonal: kotlinAsJava.translators uses a module listed above it, which is the healthy direction.
40→18 kotlinAsJava.translators uses base.transformers.pages.comments✕
- Connections
- 2 pairs of types, where a type in kotlinAsJava.translators uses a type in base.transformers.pages.comments.
- The types involved
org.jetbrains.dokka.kotlinAsJava.translators.KotlinAsJavaDocumentableToPageTranslator→org.jetbrains.dokka.base.transformers.pages.comments.CommentsToContentConverterorg.jetbrains.dokka.kotlinAsJava.translators.KotlinAsJavaPageCreator→org.jetbrains.dokka.base.transformers.pages.comments.CommentsToContentConverter
- Direction
- kotlinAsJava.translators uses base.transformers.pages.comments, so a change to base.transformers.pages.comments can break kotlinAsJava.translators, while a change to kotlinAsJava.translators can't break base.transformers.pages.comments.
- Position
- Below the diagonal: kotlinAsJava.translators uses a module listed above it, which is the healthy direction.
40→20 kotlinAsJava.translators uses transformers.documentation✕
- Connections
- 1 pair of types, where a type in kotlinAsJava.translators uses a type in transformers.documentation.
- The types involved
org.jetbrains.dokka.kotlinAsJava.translators.KotlinAsJavaDocumentableToPageTranslator→org.jetbrains.dokka.transformers.documentation.DocumentableToPageTranslator
- Direction
- kotlinAsJava.translators uses transformers.documentation, so a change to transformers.documentation can break kotlinAsJava.translators, while a change to kotlinAsJava.translators can't break transformers.documentation.
- Position
- Below the diagonal: kotlinAsJava.translators uses a module listed above it, which is the healthy direction.
40→26 kotlinAsJava.translators uses base.translators.documentables✕
- Connections
- 1 pair of types, where a type in kotlinAsJava.translators uses a type in base.translators.documentables.
- The types involved
org.jetbrains.dokka.kotlinAsJava.translators.KotlinAsJavaPageCreator→org.jetbrains.dokka.base.translators.documentables.DefaultPageCreator
- Direction
- kotlinAsJava.translators uses base.translators.documentables, so a change to base.translators.documentables can break kotlinAsJava.translators, while a change to kotlinAsJava.translators can't break base.translators.documentables.
- Position
- Below the diagonal: kotlinAsJava.translators uses a module listed above it, which is the healthy direction.
40→31 kotlinAsJava.translators uses base.signatures✕
- Connections
- 2 pairs of types, where a type in kotlinAsJava.translators uses a type in base.signatures.
- The types involved
org.jetbrains.dokka.kotlinAsJava.translators.KotlinAsJavaDocumentableToPageTranslator→org.jetbrains.dokka.base.signatures.SignatureProviderorg.jetbrains.dokka.kotlinAsJava.translators.KotlinAsJavaPageCreator→org.jetbrains.dokka.base.signatures.SignatureProvider
- Direction
- kotlinAsJava.translators uses base.signatures, so a change to base.signatures can break kotlinAsJava.translators, while a change to kotlinAsJava.translators can't break base.signatures.
- Position
- Below the diagonal: kotlinAsJava.translators uses a module listed above it, which is the healthy direction.
40→35 kotlinAsJava.translators uses base✕
- Connections
- 2 pairs of types, where a type in kotlinAsJava.translators uses a type in base.
- The types involved
org.jetbrains.dokka.kotlinAsJava.translators.KotlinAsJavaDocumentableToPageTranslator→org.jetbrains.dokka.base.DokkaBaseConfigurationorg.jetbrains.dokka.kotlinAsJava.translators.KotlinAsJavaPageCreator→org.jetbrains.dokka.base.DokkaBaseConfiguration
- Direction
- kotlinAsJava.translators uses base, so a change to base can break kotlinAsJava.translators, while a change to kotlinAsJava.translators can't break base.
- Position
- Below the diagonal: kotlinAsJava.translators uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Accessibility
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 87 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 67 | High / Critical |
Roadmap
Top priorities: Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href; Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label; Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href. | +5.7 pts | Medium | Keyboard semantics |
| Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label. | +3.9 pts | Medium | Forms & labels |
| Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video. | +3.5 pts | Medium | Text alternatives |
| Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh. | +3.3 pts | Medium | Page structure |
| Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1. | +2.5 pts | Medium | Visual & motion safety |
| Add tests that import the unreached modules (directly or through their public entry). | +1.6 pts | Medium | Test Coverage |
| Reconcile the README with reality: CONTRIBUTING.md links to `build-logic/src/main/kotlin/org/jetbrains/conventions/base-java.gradle.kts`, but `build-logic/src/main/kotlin/org/jetbrains/conventions/base-java.gradle.kts` does not exist; dokka-subprojects/plugin-gfm/README.md links to `dokka-migration.md`, but `dokka-subprojects/plugin-gfm/dokka-migration.md` does not exist; dokka-subprojects/plugin-gfm/README.md links to `dokka-gradle.md`, but `dokka-subprojects/plugin-gfm/dokka-gradle.md` does not exist; dokka-subprojects/plugin-gfm/README.md links to `dokka-plugins.md#apply-dokka-plugins`, but `dokka-subprojects/plugin-gfm/dokka-plugins.md` does not exist; dokka-subprojects/plugin-gfm/README.md links to `dokka-maven.md#other-output-formats`, but `dokka-subprojects/plugin-gfm/dokka-maven.md` does not exist. | +1.4 pts | Medium | Documentation accuracy |
| Resolve the 1 `createSmallHTML` spells `HTML` where 18 names in the project spell it… finding(s) in Naming Consistency — start with HtmlRenderer.kt. | +0.6 pts | Low | Naming Consistency |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 1.0 | Slop | Dependency Vulnerabilities: Critical vulnerability: REDACTED |
| REDACTED | 1.6 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.4 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.5 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.5 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.1 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| dokka-subprojects/analysis-java-psi/src/main/kotlin/org/jetbrains/dokka/analysis/java/parsers/doctag/HtmlToDocTagConverter.kt | 6.0 | Mixed | Explicit Debt: TodoComment |
| dokka-subprojects/analysis-java-psi/src/main/kotlin/org/jetbrains/dokka/analysis/java/parsers/doctag/PsiElementToHtmlConverter.kt | 6.0 | Mixed | Explicit Debt: TodoComment |
| dokka-subprojects/analysis-kotlin-symbols/src/main/kotlin/org/jetbrains/dokka/analysis/kotlin/symbols/translators/DefaultSymbolToDocumentableTranslator.kt | 6.0 | Mixed | Explicit Debt: TodoComment |
| dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/renderers/html/HtmlRenderer.kt | 6.0 | Mixed | Explicit Debt: TodoComment |
| dokka-subprojects/core/src/main/kotlin/org/jetbrains/dokka/model/Documentable.kt | 6.0 | Mixed | Explicit Debt: TodoComment |
| dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/translators/documentables/PageContentBuilder.kt | 6.0 | Mixed | Explicit Debt: TodoComment |
| dokka-subprojects/core/src/main/kotlin/org/jetbrains/dokka/transformers/documentation/DefaultDocumentableMerger.kt | 6.0 | Mixed | Explicit Debt: TodoComment |
| dokka-subprojects/plugin-kotlin-as-java/src/main/kotlin/org/jetbrains/dokka/kotlinAsJava/converters/KotlinToJavaConverter.kt | 6.0 | Mixed | Explicit Debt: TodoComment |
| dokka-subprojects/analysis-java-psi/src/main/kotlin/org/jetbrains/dokka/analysis/java/util/CoreCopyPaste.kt | 6.0 | Mixed | Explicit Debt: TodoComment |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 66 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 66 dimensions across the health lenses
- Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 746 of 766 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.kt) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.kt) and this repository declares a JVM test suite (repository root, Gradle), but it was not re-run: the analyzer environment could not run it. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D12 Dependency Hygiene — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Currency was graded against Maven Central, but whether an artifact is DEPRECATED is not: Maven Central publishes no deprecation marker, exactly as rubygems.org does not. Whether one is UNMAINTAINED is not graded either — no registry publishes a maintenance status, and release age does not stand in for one. Two of this dimension's four signals are therefore unread on a Maven tree, and its score reflects currency alone.
- D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares a Python pyproject.toml/requirements.txt (pip/uv/Poetry), but the licence verdict published here was taken over its JVM dependencies. Nothing was read about its Python dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
- D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (dokka-runners/dokka-gradle-plugin/build.gradle.kts), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict. For npm the surface is what a published REDACTED's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
- D24 Comment Value — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `dokka-runners/dokka-gradle-plugin/src/classicMain/kotlin/DokkaMultiModuleFileLayout.kt`, `dokka-runners/dokka-gradle-plugin/src/classicMain/kotlin/tasks/AbstractDokkaLeafTask.kt`, `dokka-runners/dokka-gradle-plugin/src/classicMain/kotlin/tasks/AbstractDokkaParentTask.kt`, `dokka-runners/dokka-gradle-plugin/src/classicMain/kotlin/tasks/DokkaCollectorTask.kt`, `dokka-runners/dokka-gradle-plugin/src/classicMain/kotlin/tasks/DokkaMultiModuleTask.kt`, … (+49 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- AC6 Visual & motion safety — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 14 further occurrence(s) are not listed individually; the score already reflects all 54.
- AX1 Captive dependencies — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository's container is an unrecognised JSR-330 (javax.inject / jakarta.inject) container, whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- AXB2 Runtime readiness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `npm run` found no REDACTED in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. (rule: no-root-manifest). The renderer reported: the dev server (`npm run start`) exited before it served a page. Likely cause (our sandbox): `npm run` found no REDACTED in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read REDACTED: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DevServer (start). the dev server (`npm run start`) exited before it served a page. Likely cause (our sandbox): `npm run` found no REDACTED in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read REDACTED: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and this repository's Java, Kotlin is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and this repository's Kotlin is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- R10 Code Duplication — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 1 further occurrence(s) are not listed individually; the score already reflects all 41.
- R2 Cyclomatic Complexity — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 35 further occurrence(s) are not listed individually; the score already reflects all 75.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
- D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned REDACTED, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
- AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
- AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
14 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was HtmlToDocTagConverter.createBlock at 44. A further 12 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being MarkdownParser.visitNode at 36 — they are counted neither in the figure above nor in this dimension's score. 12 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: dokka-subprojects/analysis-markdown-jb/src/main/kotlin/org/jetbrains/dokka/analysis/markdown/jb/MarkdownParser.kt (MarkdownParser.visitNode at 36), dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/renderers/html/HtmlRenderer.kt (HtmlRenderer.wrapGroup at 27), dokka-subprojects/analysis-kotlin-symbols/src/main/kotlin/org/jetbrains/dokka/analysis/kotlin/symbols/translators/DRIFactory.kt (DRIFactoryKt.getDRIFromSymbol at 25), dokka-subprojects/core/src/main/kotlin/org/jetbrains/dokka/model/extraModifiers.kt (ExtraModifiers.valueOf at 25), dokka-subprojects/analysis-kotlin-symbols/src/main/kotlin/org/jetbrains/dokka/analysis/kotlin/symbols/translators/AnnotationTranslator.kt (AnnotationTranslator.toDokkaAnnotationValue at 23), and 7 more not listed here. They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 14 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with HtmlToDocTagConverter.createBlock (cyclomatic 44), DocTagToContentConverter.buildContent (cyclomatic 42), DocTagsFromIElementFactory.getInstance (cyclomatic 38). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 14 together lifts Cyclomatic Complexity from 7.8 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
19 method(s) exceeded the cognitive complexity threshold of 15; the worst was DefaultSnippetToHtmlConverter.parseSnippet at 83.
What to do
- Bring the 1 body over 60 down to 60 or less in Cognitive Complexity — start with DefaultSnippetToHtmlConverter.parseSnippet (cognitive 83). — Refactoring it lifts Cognitive Complexity from 6.7 to about 7.0/10.
D3 · God Classes
21 god class(es) detected.
What to do
- Resolve the 6 ClassTooLong finding(s) in God Classes — start with DefaultSymbolToDocumentableTranslator.kt, HtmlRenderer.kt, DefaultPageCreator.kt. — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 6 TooManyMethods finding(s) in God Classes — start with HtmlRenderer.kt, DefaultPageCreator.kt, MarkdownParser.kt. — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 6 FileTooLong finding(s) in God Classes — start with DefaultSymbolToDocumentableTranslator.kt, Documentable.kt, HtmlRenderer.kt. — One of this dimension's main actionable groups (6 warning-level).
D4 · Code Duplication
36 duplicated block group(s) detected. 3.1 % of the production lines (1,389 of 44,953) are in a reported copy. A further 35 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 2 of the 71 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
What to do
- Resolve the 4 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with DefaultDocumentableMerger.kt (2), DokkaTask.kt, DocumentableReplacerTransformer.kt. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 4 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with DocumentableReplacerTransformer.kt (2), DefaultSymbolToDocumentableTranslator.kt, JavadocSignatureProvider.kt. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 3 Edited copy of a member (8 corresponding lines) finding(s) in Code Duplication — start with jvmOverloads.kt, EmptyPackagesFilterTransformer.kt, KotlinDocumentableSourceLanguageParser.kt. — One of this dimension's main actionable groups (3 warning-level).
D5 · Coupling
34 production modules (Gradle+Maven+npm), 0 dependency cycle(s), 1 unstable depended-on module(s). Read from the build's own module declarations; edges a convention plugin adds from buildSrc or build-logic are not visible there; 2 module(s) off the main sequence, with abstractness counted on 30 of the 34 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What to do
- Resolve the 2 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Unstable project dokka finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
D6 · Cohesion (LCOM4)
1 of 138 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with AbstractIntegrationTest.kt. — One of this dimension's main actionable groups (1 warning-level).
D12 · Dependency Hygiene
3 outdated artifact(s) of 3 resolved by the build, graded against Maven Central. The poms themselves state a version for only 77 of 99 declaration(s) — the rest are parent- or BOM-managed, which is why this is read from the resolved graph rather than from the manifests. Whether any of these is DEPRECATED is not graded — Maven Central publishes no deprecation marker, exactly as rubygems.org does not. Whether any is UNMAINTAINED is not graded either: no registry publishes a maintenance status, and release age does not stand in for one. Known CVEs in this graph are D30's question, read from the manifest there.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 42 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 126 Maven/Gradle manifest(s) declare with a version resolvable from the manifest itself — the same declaration-site closure this analysis reads for dependency currency. The JVM has no lockfile a checkout is guaranteed to carry, so this is deliberately NOT the transitive closure. 22 further coordinate(s) are declared with no version at the declaration site — inherited from a parent POM, a BOM or an unresolved Gradle version reference — and are NOT graded: this verdict covers what the checkout pins, not the full transitive graph. A further 24 coordinate(s) are not published to Maven Central — another repository (Google's Maven hosts androidx), a SNAPSHOT, or a private artifact — so their licences are not readable from here and they are outside this verdict. ★ COVERAGE OF THIS VERDICT: it grades this repository's JVM dependencies and nothing else. The repository also declares a Python pyproject.toml/requirements.txt (pip/uv/Poetry), and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D16 · Bus Factor
13 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is dokka-subprojects/analysis-markdown-jb/src/main/kotlin/org/jetbrains/dokka/analysis/markdown/jb/MarkdownParser.kt. Counted over 243 of the 604 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D17 · Explicit Debt
82 deducted task-comment markers across 44953 LoC (0.2/KLoC) → score 9.7. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 79 TodoComment finding(s) in Explicit Debt — start with StdlibUtil.kt (7), HtmlRenderer.kt (4), DefaultSymbolToDocumentableTranslator.kt (4). — One of this dimension's main actionable groups (79 warning-level).
- Resolve the 3 HackComment finding(s) in Explicit Debt — start with JvmMappedMethodsDocumentableFilterTransformer.kt, DokkaMojo.kt, HtmlAggregationWarningTest.kt. — One of this dimension's main actionable groups (3 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 21 document(s) read across 2 unit(s).
D21 · Naming Consistency
2 naming inconsistencies among 46 declarations measured against a convention their peers follow.
What to do
- Resolve the 1 `externalDri` spells `Dri` where 26 names in the project spell it `DRI` finding(s) in Naming Consistency — start with KdocMarkdownParser.kt. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 `createSmallHTML` spells `HTML` where 18 names in the project spell it… finding(s) in Naming Consistency — start with HtmlRenderer.kt. — One of this dimension's main actionable groups (1 recommendation-level).
D24 · Comment Value
0 of 37 judged comments only repeat the code they sit on (0.0 %).
D26 · Project Cohesion
3 of 24 build units (Gradle) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
87 finding(s): 0 critical, 82 high, 5 medium, 0 low. 65 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 3 file(s) — `dokka-subprojects/plugin-javadoc/src/main/resources/static_res/jquery/external/jquery/jquery.js`, `REDACTED`, `gradlew` (line 74, line 180) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 2 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 17 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4), REDACTED (4), REDACTED (3). — One of this dimension's main actionable groups (17 issue-level).
- Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3). — One of this dimension's main actionable groups (3 warning-level).
- No action in Static Analysis (SAST) — all 65 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (65 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
55 finding(s): 4 critical, 30 high, 17 medium, 4 low.
What to do
- Resolve the 29 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (27), REDACTED (2). — One of this dimension's main actionable groups (29 issue-level).
- Resolve the 3 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 1 Critical vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D34 · Knowledge Freshness
163 of 243 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/translators/documentables/PageContentBuilder.kt. Counted over 243 of the 604 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 160 Orphaned file finding(s) in Knowledge Freshness — start with index.ts (6), build.gradle.kts (5), htmlPreprocessors.kt (2). — One of this dimension's main actionable groups (160 recommendation-level).
- Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with PageContentBuilder.kt, SnippetToHtmlConverter.kt, DocumentableVisibilityFilterTransformer.kt. — One of this dimension's main actionable groups (3 recommendation-level).
- Resolve the 1 Concentrated knowledge decay finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
Strongest change-coupling: DocTagsFromIElementFactory.kt↔DocTagToContentConverter.kt 57%; HtmlRenderer.kt↔DocTagToContentConverter.kt 51%; TestedVersions.kt↔TestedVersionsSource.kt 50%
What to do
- Resolve the 3 Change coupling finding(s) in Change Coupling — start with DocTagsFromIElementFactory.kt, HtmlRenderer.kt, TestedVersions.kt. — One of this dimension's main actionable groups (3 warning-level).
D36 · Supply-chain Provenance & Signing
1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 8 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (8 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 9 platform declaration(s) and 121 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AC1 · Text alternatives
- An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative. (×2) — REDACTED:7549, REDACTED:7561
What to do
- Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
AC2 · Forms & labels
- A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label. (×4) — dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/renderers/html/HtmlRenderer.kt:813, dokka-subprojects/plugin-base/src/main/resources/dokka/templates/includes/footer.ftl:4, dokka-subprojects/plugin-javadoc/src/main/resources/static_res/jquery/external/jquery/jquery.js:1389, …
- This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×9) — dokka-subprojects/plugin-javadoc/src/main/resources/static_res/jquery/external/jquery/jquery.js:1333, dokka-subprojects/plugin-javadoc/src/main/resources/static_res/jquery/external/jquery/jquery.js:1390, dokka-subprojects/plugin-javadoc/src/main/resources/static_res/jquery/external/jquery/jquery.js:2949, …
- A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one). (×6) — REDACTED:6893, REDACTED:7557, REDACTED:9099, …
What to do
- Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
AC3 · Page structure
- An empty heading appears in the document outline announced with no text. Give the heading text, or remove it if it's decorative. (×6) — dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/renderers/html/HtmlRenderer.kt:707, dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/renderers/html/HtmlRenderer.kt:708, dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/renderers/html/HtmlRenderer.kt:709, …
- A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>. — dokka-subprojects/plugin-base/src/main/resources/dokka/templates/base.ftl:5
- The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). — dokka-subprojects/plugin-versioning/src/main/resources/dokka/not-found-version.html:2
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — dokka-subprojects/plugin-versioning/src/main/resources/dokka/not-found-version.html:2
What to do
- Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC4 · Keyboard semantics
- A positive tabindex forces a manual tab order that fights the DOM and is fragile. Use tabindex="0" (or restructure the DOM). — dokka-subprojects/plugin-base/src/main/resources/dokka/templates/includes/header.ftl:5
- An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action. (×9) — REDACTED:9028, REDACTED:9044, REDACTED:9063, …
What to do
- Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
AC5 · ARIA correctness
AC6 · Visual & motion safety
- `.platform-tag.jvm-like` sets color: white on background-color: #4DBB5F — 2.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — examples/gradle/dokka-versioning-multimodule-example/previousDocVersions/0.9/styles/style.css:821
- `.platform-tag.js-like` sets color: white on background-color: #FED236 — 1.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — examples/gradle/dokka-versioning-multimodule-example/previousDocVersions/0.9/styles/style.css:826
- `.platform-tag.native-like` sets color: white on background-color: #CD74F6 — 2.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — examples/gradle/dokka-versioning-multimodule-example/previousDocVersions/0.9/styles/style.css:831
- `.platform-tag.common-like` sets color: white on background-color: #A6AFBA — 2.2:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — examples/gradle/dokka-versioning-multimodule-example/previousDocVersions/0.9/styles/style.css:836
- `.ui-state-active, .ui-widget-content .ui-state-active, .ui-widget-header .ui-state-active, a.ui-button:active, .ui-button:active, .ui-button.ui-state-active:hover` sets color: #ffffff on background-color: #007fff — 3.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. (×3) — dokka-subprojects/plugin-javadoc/src/main/resources/static_res/jquery/jquery-ui.css:982, dokka-integration-tests/gradle/src/testExampleProjects/expectedData/exampleProjects/library-publishing-example/javadoc/jquery/jquery-ui.css:982, dokka-integration-tests/gradle/src/testExampleProjects/expectedData/exampleProjects/javadoc-example/javadoc/jquery/jquery-ui.css:982
- `.ui-state-highlight, .ui-widget-content .ui-state-highlight, .ui-widget-header .ui-state-highlight` sets color: #777620 on background-color: #fffa90 — 4.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. (×3) — dokka-subprojects/plugin-javadoc/src/main/resources/static_res/jquery/jquery-ui.css:1004, dokka-integration-tests/gradle/src/testExampleProjects/expectedData/exampleProjects/library-publishing-example/javadoc/jquery/jquery-ui.css:1004, dokka-integration-tests/gradle/src/testExampleProjects/expectedData/exampleProjects/javadoc-example/javadoc/jquery/jquery-ui.css:1004
- `.toc--skip-link` sets color: #fff on background-color: #458cff — 3.3:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — dokka-subprojects/plugin-base/src/main/resources/dokka/ui-kit/ui-kit.css:3253
- `.search button:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — examples/gradle/dokka-versioning-multimodule-example/previousDocVersions/0.9/styles/main.css:1
- `.section-tab` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. (×5) — examples/gradle/dokka-versioning-multimodule-example/previousDocVersions/0.9/styles/style.css:184, dokka-integration-tests/gradle/projects/ui-showcase/previousDocVersions/1.9/styles/style.css:530, dokka-integration-tests/gradle/projects/ui-showcase/previousDocVersions/1.8/styles/style.css:530, …
- `.platform-tag` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — examples/gradle/dokka-versioning-multimodule-example/previousDocVersions/0.9/styles/style.css:803
- `.ui-helper-reset` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. (×6) — dokka-subprojects/plugin-javadoc/src/main/resources/static_res/jquery/jquery-ui.css:26, dokka-subprojects/plugin-javadoc/src/main/resources/static_res/jquery/jquery-ui.structure.css:30, dokka-integration-tests/gradle/src/testExampleProjects/expectedData/exampleProjects/library-publishing-example/javadoc/jquery/jquery-ui.css:26, …
- `.ui-menu` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. (×6) — dokka-subprojects/plugin-javadoc/src/main/resources/static_res/jquery/jquery-ui.css:117, dokka-subprojects/plugin-javadoc/src/main/resources/static_res/jquery/jquery-ui.structure.css:121, dokka-integration-tests/gradle/src/testExampleProjects/expectedData/exampleProjects/library-publishing-example/javadoc/jquery/jquery-ui.css:117, …
- `.ui-dialog` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. (×6) — dokka-subprojects/plugin-javadoc/src/main/resources/static_res/jquery/jquery-ui.css:495, dokka-subprojects/plugin-javadoc/src/main/resources/static_res/jquery/jquery-ui.structure.css:499, dokka-integration-tests/gradle/src/testExampleProjects/expectedData/exampleProjects/library-publishing-example/javadoc/jquery/jquery-ui.css:495, …
- `.menu-toggle` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. (×4) — dokka-integration-tests/gradle/projects/ui-showcase/previousDocVersions/1.9/styles/style.css:297, dokka-integration-tests/gradle/projects/ui-showcase/previousDocVersions/1.8/styles/style.css:297, dokka-integration-tests/gradle/projects/ui-showcase/previousDocVersions/1.5/styles/style.css:297, …
What to do
- Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
M1 · Documentation (README)
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
- CONTRIBUTING.md links to `build-logic/src/main/kotlin/org/jetbrains/conventions/base-java.gradle.kts`, but `build-logic/src/main/kotlin/org/jetbrains/conventions/base-java.gradle.kts` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — CONTRIBUTING.md:161
- dokka-subprojects/plugin-gfm/README.md links to `dokka-migration.md`, but `dokka-subprojects/plugin-gfm/dokka-migration.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — dokka-subprojects/plugin-gfm/README.md:4
- dokka-subprojects/plugin-gfm/README.md links to `dokka-gradle.md`, but `dokka-subprojects/plugin-gfm/dokka-gradle.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — dokka-subprojects/plugin-gfm/README.md:14
- dokka-subprojects/plugin-gfm/README.md links to `dokka-plugins.md#apply-dokka-plugins`, but `dokka-subprojects/plugin-gfm/dokka-plugins.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — dokka-subprojects/plugin-gfm/README.md:74
- dokka-subprojects/plugin-gfm/README.md links to `dokka-maven.md#other-output-formats`, but `dokka-subprojects/plugin-gfm/dokka-maven.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — dokka-subprojects/plugin-gfm/README.md:97
- dokka-subprojects/plugin-gfm/README.md links to `dokka-cli.md#run-with-command-line-options`, but `dokka-subprojects/plugin-gfm/dokka-cli.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — dokka-subprojects/plugin-gfm/README.md:108
- dokka-subprojects/plugin-jekyll/README.md links to `dokka-migration.md`, but `dokka-subprojects/plugin-jekyll/dokka-migration.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — dokka-subprojects/plugin-jekyll/README.md:4
- dokka-subprojects/plugin-jekyll/README.md links to `dokka-gradle.md`, but `dokka-subprojects/plugin-jekyll/dokka-gradle.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — dokka-subprojects/plugin-jekyll/README.md:15
- dokka-subprojects/plugin-jekyll/README.md links to `dokka-plugins.md#apply-dokka-plugins`, but `dokka-subprojects/plugin-jekyll/dokka-plugins.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — dokka-subprojects/plugin-jekyll/README.md:52
- dokka-subprojects/plugin-jekyll/README.md links to `dokka-maven.md#other-output-formats`, but `dokka-subprojects/plugin-jekyll/dokka-maven.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — dokka-subprojects/plugin-jekyll/README.md:75
- dokka-subprojects/plugin-jekyll/README.md links to `dokka-cli.md#run-with-command-line-options`, but `dokka-subprojects/plugin-jekyll/dokka-cli.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — dokka-subprojects/plugin-jekyll/README.md:86
What to do
- Reconcile the README with reality: CONTRIBUTING.md links to `build-logic/src/main/kotlin/org/jetbrains/conventions/base-java.gradle.kts`, but `build-logic/src/main/kotlin/org/jetbrains/conventions/base-java.gradle.kts` does not exist; dokka-subprojects/plugin-gfm/README.md links to `dokka-migration.md`, but `dokka-subprojects/plugin-gfm/dokka-migration.md` does not exist; dokka-subprojects/plugin-gfm/README.md links to `dokka-gradle.md`, but `dokka-subprojects/plugin-gfm/dokka-gradle.md` does not exist; dokka-subprojects/plugin-gfm/README.md links to `dokka-plugins.md#apply-dokka-plugins`, but `dokka-subprojects/plugin-gfm/dokka-plugins.md` does not exist; dokka-subprojects/plugin-gfm/README.md links to `dokka-maven.md#other-output-formats`, but `dokka-subprojects/plugin-gfm/dokka-maven.md` does not exist.
P1 · CI/CD gates
P10 · Library API & versioning
- 15 public types in `org.jetbrains.dokka.gradle.internal` are marked as implementation by their own namespace, folder or name: `AbstractDokkaTaskExtensionsKt` (dokka-runners/dokka-gradle-plugin/src/classicMain/kotlin/internal/AbstractDokkaTaskExtensions.kt:1, `internal`), `HasFormatName` (dokka-runners/dokka-gradle-plugin/src/main/kotlin/internal/HasFormatName.kt:10, `internal`), `InternalDokkaGradlePluginApi` (dokka-runners/dokka-gradle-plugin/src/main/kotlin/internal/InternalDokkaGradlePluginApi.kt:38, `internal`), `PluginFeaturesServiceKt` (dokka-runners/dokka-gradle-plugin/src/main/kotlin/internal/PluginFeaturesService.kt:1, `internal`), `CollectionsUtilsKt` (dokka-runners/dokka-gradle-plugin/src/main/kotlin/internal/collectionsUtils.kt:1, `internal`), `DokkaBootstrapFactoryKt` (dokka-runners/dokka-gradle-plugin/src/main/kotlin/internal/dokkaBootstrapFactory.kt:1, `internal`), `FindExtensionLenientKt` (dokka-runners/dokka-gradle-plugin/src/main/kotlin/internal/findExtensionLenient.kt:1, `internal`), `GradleProviderUtilsKt` (dokka-runners/dokka-gradle-plugin/src/main/kotlin/internal/gradleProviderUtils.kt:1, `internal`), and 7 more. While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — dokka-runners/dokka-gradle-plugin/src/classicMain/kotlin/internal/AbstractDokkaTaskExtensions.kt:1
- 1 public type in `org.jetbrains.dokka.gradle.internal.GradlePropertiesFileSource` is marked as implementation by its own namespace, folder or name: `Params` (dokka-runners/dokka-gradle-plugin/src/main/kotlin/internal/GradlePropertiesFileSource.kt:21, `internal`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers. — dokka-runners/dokka-gradle-plugin/src/main/kotlin/internal/GradlePropertiesFileSource.kt:21
- 2 public types in `org.jetbrains.dokka.gradle.internal.PluginFeaturesService` are marked as implementation by their own namespace, folder or name: `Params` (dokka-runners/dokka-gradle-plugin/src/main/kotlin/internal/PluginFeaturesService.kt:39, `internal`), `Companion` (dokka-runners/dokka-gradle-plugin/src/main/kotlin/internal/PluginFeaturesService.kt:267, `internal`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — dokka-runners/dokka-gradle-plugin/src/main/kotlin/internal/PluginFeaturesService.kt:39
- 4 public types in `org.jetbrains.dokka.gradle.internal.PluginFeaturesService.PluginMode` are marked as implementation by their own namespace, folder or name: `V1Enabled` (dokka-runners/dokka-gradle-plugin/src/main/kotlin/internal/PluginFeaturesService.kt:217, `internal`), `V2EnabledWithHelpers` (dokka-runners/dokka-gradle-plugin/src/main/kotlin/internal/PluginFeaturesService.kt:218, `internal`), `V2Enabled` (dokka-runners/dokka-gradle-plugin/src/main/kotlin/internal/PluginFeaturesService.kt:219, `internal`), `Companion` (dokka-runners/dokka-gradle-plugin/src/main/kotlin/internal/PluginFeaturesService.kt:222, `internal`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — dokka-runners/dokka-gradle-plugin/src/main/kotlin/internal/PluginFeaturesService.kt:217
- 1 public type in `org.jetbrains.dokka.gradle.internal.Compat` is marked as implementation by its own namespace, folder or name: `locateOrRegisterMetadataDependencyTransformationTaskKt` (dokka-runners/dokka-gradle-plugin/src/main/kotlin/internal/compat.locateOrRegisterMetadataDependencyTransformationTask.kt:1, `internal`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers. — dokka-runners/dokka-gradle-plugin/src/main/kotlin/internal/compat.locateOrRegisterMetadataDependencyTransformationTask.kt:1
What to do
- Hide `org.jetbrains.dokka.gradle.internal` (`AbstractDokkaTaskExtensionsKt`, `HasFormatName`, `InternalDokkaGradlePluginApi`, `PluginFeaturesServiceKt`, `CollectionsUtilsKt`, `DokkaBootstrapFactoryKt`, `FindExtensionLenientKt`, `GradleProviderUtilsKt`, and 7 more) (Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `org.jetbrains.dokka.gradle.internal.GradlePropertiesFileSource` (`Params`) (Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `org.jetbrains.dokka.gradle.internal.PluginFeaturesService` (`Params`, `Companion`) (Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `org.jetbrains.dokka.gradle.internal.PluginFeaturesService.PluginMode` (`V1Enabled`, `V2EnabledWithHelpers`, `V2Enabled`, `Companion`) (Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `org.jetbrains.dokka.gradle.internal.Compat` (`locateOrRegisterMetadataDependencyTransformationTaskKt`) (Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
P3 · Security & performance tooling
- `REDACTED` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — REDACTED:38
What to do
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
PF3 · Async & latency hygiene
R1 · Type Safety
R10 · Code Duplication
- dokka-integration-tests/gradle/src/testExampleProjects/expectedData/exampleProjects/javadoc-example/javadoc/ and dokka-subprojects/plugin-javadoc/src/main/resources/static_res/ are near-verbatim copies of each other: 12 files are byte-identical under the same relative paths (~33268 lines; the trees hold 29 and 12 files). That is one structural fact, not 12 local ones: every edit made to one tree and not the other drifts silently, which is the failure whole-tree forks guarantee. Pick one tree as the single source and produce the other from it (generated, copied at build or release time, or re-exported) — or, if the copy is a stale snapshot nothing produces any more, delete it. Check first whether the copy is a deliberately published deliverable (a template consumers copy verbatim, a released sample frozen at a version); where it is, keep it produced from the source tree rather than edited in place. — REDACTED:1
- dokka-integration-tests/gradle/src/testExampleProjects/expectedData/exampleProjects/library-publishing-example/javadoc/ and dokka-subprojects/plugin-javadoc/src/main/resources/static_res/ are near-verbatim copies of each other: 12 files are byte-identical under the same relative paths (~33268 lines; the trees hold 29 and 12 files). That is one structural fact, not 12 local ones: every edit made to one tree and not the other drifts silently, which is the failure whole-tree forks guarantee. Pick one tree as the single source and produce the other from it (generated, copied at build or release time, or re-exported) — or, if the copy is a stale snapshot nothing produces any more, delete it. Check first whether the copy is a deliberately published deliverable (a template consumers copy verbatim, a released sample frozen at a version); where it is, keep it produced from the source tree rather than edited in place. — REDACTED:1
- REDACTED:225 · REDACTED:7197 — the two spans are one implementation copied and then locally edited — 233 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — REDACTED:225
- dokka-subprojects/plugin-base/src/main/resources/dokka/scripts/safe-local-storage_blocking.js:7 · dokka-subprojects/plugin-base/src/main/resources/dokka/scripts/safe-local-storage_blocking.js:49 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — dokka-subprojects/plugin-base/src/main/resources/dokka/scripts/safe-local-storage_blocking.js:7
- REDACTED:1175 · REDACTED:1211 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — REDACTED:1175
- REDACTED:1088 · REDACTED:1132 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — REDACTED:1088
- REDACTED:9029 · REDACTED:9064 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — REDACTED:9029
- REDACTED:10169 · REDACTED:16626 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:10169
- REDACTED:5569 · REDACTED:5600 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:5569
- REDACTED:5999 · REDACTED:14643 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:5999
- REDACTED:10754 · REDACTED:10995 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:10754
- REDACTED:10241 · REDACTED:16697 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:10241
- REDACTED:10901 · REDACTED:10934 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — REDACTED:10901
- REDACTED:15296 · REDACTED:17417 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:15296
- REDACTED:9896 · REDACTED:13020 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:9896
- REDACTED:12749 · REDACTED:12808 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — REDACTED:12749
- REDACTED:13266 · REDACTED:13283 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:13266
- REDACTED:2818 · REDACTED:2830 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:2818
- REDACTED:7720 · REDACTED:7754 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:7720
- REDACTED:4684 · REDACTED:18186 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — REDACTED:4684
- REDACTED:8709 · REDACTED:8775 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:8709
- REDACTED:10215 · REDACTED:16672 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:10215
- REDACTED:10883 · REDACTED:10960 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — REDACTED:10883
- REDACTED:13901 · REDACTED:14033 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — REDACTED:13901
- REDACTED:15387 · REDACTED:15397 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — REDACTED:15387
- REDACTED:5333 · REDACTED:14610 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:5333
- REDACTED:3379 · REDACTED:3739 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:3379
- REDACTED:4700 · REDACTED:18202 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — REDACTED:4700
- REDACTED:8536 · REDACTED:8772 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:8536
- REDACTED:9435 · REDACTED:9449 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — REDACTED:9435
- REDACTED:12191 · REDACTED:12200 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:12191
- REDACTED:15833 · REDACTED:15842 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — REDACTED:15833
- dokka-subprojects/plugin-base/src/main/resources/dokka/scripts/platform-content-handler.js:182 · dokka-subprojects/plugin-base/src/main/resources/dokka/scripts/platform-content-handler.js:192 — the two spans are one implementation copied and then locally edited — 50 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — dokka-subprojects/plugin-base/src/main/resources/dokka/scripts/platform-content-handler.js:182
- REDACTED:7740 · REDACTED:7774 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:7740
- REDACTED:16762 · REDACTED:16808 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — REDACTED:16762
- REDACTED:4782 · REDACTED:18242 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:4782
- REDACTED:4798 · REDACTED:4807 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — REDACTED:4798
- REDACTED:10319 · REDACTED:10325 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — REDACTED:10319
- REDACTED:11528 · REDACTED:11534 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — REDACTED:11528
- REDACTED:1816 · REDACTED:1853 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:1816
What to do
- Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
R2 · Cyclomatic Complexity
- _generateHTML has cyclomatic complexity 88 and cognitive complexity 220; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:8978
- _doKeyDown has cyclomatic complexity 45 and cognitive complexity 76; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:7919
- parseDate has cyclomatic complexity 42 and cognitive complexity 49; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:8457
- drag has cyclomatic complexity 33 and cognitive complexity 48; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:10865
- _respectSize has cyclomatic complexity 29 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:11619
- _generatePosition has cyclomatic complexity 27 and cognitive complexity 57; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:10377
- _contactContainers has cyclomatic complexity 27 and cognitive complexity 57; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:16472
- _generateMonthYearHeader has cyclomatic complexity 27 and cognitive complexity 46; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:9237
- formatDate has cyclomatic complexity 27 and cognitive complexity 42; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:8670
- _clear has cyclomatic complexity 27 and cognitive complexity 36; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:16938
- _generatePosition has cyclomatic complexity 26 and cognitive complexity 47; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:16803
- (anonymous) has cyclomatic complexity 26 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:13389
- (anonymous) has cyclomatic complexity 24 and cognitive complexity 32; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:13966
- resize has cyclomatic complexity 23 and cognitive complexity 33; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:11922
- _keydown has cyclomatic complexity 23 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:5174
- _mouseDrag has cyclomatic complexity 22 and cognitive complexity 36; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:15876
- drag has cyclomatic complexity 22 and cognitive complexity 33; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:10785
- _showDatepicker has cyclomatic complexity 22 and cognitive complexity 27; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:8059
- keydown has cyclomatic complexity 22 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:15411
- _mouseStart has cyclomatic complexity 20 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:15658
- resize has cyclomatic complexity 19 and cognitive complexity 24; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:12143
- _setOption has cyclomatic complexity 19 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:12900
- _setContainment has cyclomatic complexity 19 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:16713
- _setContainment has cyclomatic complexity 19 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:10259
- _refreshValue has cyclomatic complexity 18 and cognitive complexity 33; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:15330
- _optionDatepicker has cyclomatic complexity 18 and cognitive complexity 25; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:7829
- (anonymous) has cyclomatic complexity 18 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:3072
- _mouseMove has cyclomatic complexity 18 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:9644
- keydown has cyclomatic complexity 18 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:14521
- _hideDatepicker has cyclomatic complexity 17 and cognitive complexity 33; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:8237
- (anonymous) has cyclomatic complexity 17 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:13526
- _eventHandler has cyclomatic complexity 17 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:18215
- set has cyclomatic complexity 16 and cognitive complexity 24; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:1960
- (anonymous) has cyclomatic complexity 16 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:3515
- _setOption has cyclomatic complexity 16 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:15156
- _intersectsWith has cyclomatic complexity 15 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:16115
- (anonymous) has cyclomatic complexity 15 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. (×2) — REDACTED:18, REDACTED:723
- _checkOffset has cyclomatic complexity 14 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:8199
- _animate has cyclomatic complexity 14 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:4868
R3 · Large Files
- REDACTED has 15970 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
What to do
- Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
R4 · Test Coverage
- 0% of 40 production file(s) reachable from 0 test file(s) via the import graph — 'production' here is the RESIDUE: every source file left once tests, tooling, generated output, config, declarations and declaration-only modules, fixture corpora, type fixtures, behaviour-free data modules, re-export barrels, registration/constant data modules and service workers are set aside, so the percentage is taken over a smaller denominator than the workspace's file count
What to do
- Add tests that import the unreached modules (directly or through their public entry).
R5 · Dependency Freshness
R6 · Tooling
- test ✗ · lint ✓ · typecheck ✓ — read from this repository's REDACTED scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
What to do
- Add a test runner (vitest / jest / playwright) as REDACTED scripts and run them in CI.
R7 · Dead Code
- Unreachable from the 9 application, 9 tooling and 0 test entry point(s) detected in this repo. Gate removals on `npm run build` — an undetected custom entry would make these reachable.
- no import path from any entry point (9 application, 9 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (dokka-subprojects/plugin-base-frontend/src/main/components/app/index.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — dokka-subprojects/plugin-base-frontend/src/main/components/search/search.tsx
- no import path from any entry point (9 application, 9 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (dokka-subprojects/plugin-base-frontend/src/main/components/search/search.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×3) — dokka-subprojects/plugin-base-frontend/src/main/components/search/dokkaFuzzyFilter.tsx, dokka-subprojects/plugin-base-frontend/src/main/components/search/dokkaSearchAnchor.tsx, dokka-subprojects/plugin-base-frontend/src/main/components/utils/requests.tsx
- no import path from any entry point (9 application, 9 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (dokka-subprojects/plugin-base-frontend/src/main/components/search/dokkaSearchAnchor.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — dokka-subprojects/plugin-base-frontend/src/main/components/utils/hotkey.ts
- no import path from any entry point (9 application, 9 tooling, 0 test roots considered), but 5 in-repo import(s) from 5 other file(s) do name it (dokka-subprojects/plugin-base-frontend/src/main/components/search/dokkaFuzzyFilter.tsx, dokka-subprojects/plugin-base-frontend/src/main/components/search/dokkaSearchAnchor.tsx, dokka-subprojects/plugin-base-frontend/src/main/components/search/search.tsx and 2 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — dokka-subprojects/plugin-base-frontend/src/main/components/search/types.ts
- no import path from any entry point (9 application, 9 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (dokka-subprojects/plugin-base-frontend/src/main/components/search/dokkaFuzzyFilter.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — dokka-subprojects/plugin-base-frontend/src/main/components/search/searchResultRow.tsx
- no import path from any entry point (9 application, 9 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (dokka-subprojects/plugin-base-frontend/src/main/components/search/searchResultRow.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — dokka-subprojects/plugin-base-frontend/src/main/components/utils/arrayUtils.ts
- no import path from any entry point (9 application, 9 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make — dokka-subprojects/plugin-base-frontend/src/main/components/root.tsx
- no import path from any entry point (9 application, 9 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (dokka-subprojects/plugin-base-frontend/src/main/components/utils/hotkey.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — dokka-subprojects/plugin-base-frontend/src/main/components/utils/os.ts
- no import path from any entry point (9 application, 9 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (dokka-subprojects/plugin-base-frontend/src/main/components/root.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — dokka-subprojects/plugin-base-frontend/src/main/components/app/index.tsx
What to do
- Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
R8 · Dependency Hygiene
- Imported but not declared in any reachable REDACTED — installs work only by hoisting accident. — dokka-subprojects/plugin-base-frontend/webpack.config.js:55
- Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×2)
What to do
- Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports
X1 · Async correctness
X12 · Unreachable branch
X16 · Unfloored truncation loop
X18 · Disposal-pattern correctness
- `Files.walk(…)` opens something that has to be given back — a file descriptor, a socket, a directory handle — and its only use reads `.iterator` through it and drops it, so this expression both creates the value and is the last place that can release it, and does not. Every call leaks one more open handle until the collector happens to reach it: `Too many open files` under load, and on Windows a file that cannot be replaced or deleted while it is held. Open it with `Files.walk(…).use { r -> … }`, which releases it on every path including a throw, or hold it and call `.close()` in a `finally`. — dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/renderers/FileWriter.kt:79
What to do
- Each finding names the value and the span that decides who owns it — the `new` that created it, or the constructor parameter that handed it over. Confirm ownership from that span, then make the disposal match it: release what this type created, leave what it was injected with to whoever created THAT, and drop a finalizer whose type holds nothing unmanaged to release.
X21 · Side-effecting pattern guard
X23 · Unguarded diagnostic materialisation
- `debug` at line 96 is called with an argument built by `Thread.currentThread().stackTrace.drop(1).joinToString("…")` (line 98), whose cost grows with the collection it walks. Kotlin evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isDebugEnabled` test, no `BuildConfig.DEBUG` flag, no trailing lambda (`logger.debug { … }`) the logger calls only when the level is on. — dokka-subprojects/analysis-kotlin-symbols/src/main/kotlin/org/jetbrains/dokka/analysis/kotlin/symbols/translators/AnnotationTranslator.kt:96
- `debug` at line 247 is called with an argument built by `Thread.currentThread().stackTrace.drop(1).joinToString("…")` (line 247), whose cost grows with the collection it walks. Kotlin evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isDebugEnabled` test, no `BuildConfig.DEBUG` flag, no trailing lambda (`logger.debug { … }`) the logger calls only when the level is on. — dokka-subprojects/analysis-kotlin-symbols/src/main/kotlin/org/jetbrains/dokka/analysis/kotlin/symbols/translators/TypeTranslator.kt:247
What to do
- In Kotlin, hand the logger a lambda it calls only when the level is on (`logger.debug { "rows: ${rows.joinToString()}" }` — kotlin-logging and Log4j 2's Kotlin API take one), or put the line behind `if (log.isDebugEnabled)` (`if (BuildConfig.DEBUG)` for a line only a debug build needs). A string template is not the fix on SLF4J or Timber: their message is a `String`, so every `joinToString` or `toJson` inside the `${…}` runs before the call is entered.
X25 · Inert configuration knob
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
- An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×12) — REDACTED:1975, REDACTED:1988, REDACTED:8048, …
- `catch (_: Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×2) — dokka-runners/dokka-gradle-plugin/src/main/kotlin/adapters/AndroidAdapter.kt:108, dokka-runners/dokka-gradle-plugin/src/main/kotlin/adapters/AndroidAdapter.kt:112
What to do
- Swallowed exception (empty catch)
X30 · Support guard that admits what it rejects
X4 · Structured logging
- `info` at line 115 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — dokka-runners/dokka-gradle-plugin/src/main/kotlin/tasks/LogHtmlPublicationLinkTask.kt:115
- `info` at line 152 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — dokka-runners/dokka-gradle-plugin/src/main/kotlin/tasks/LogHtmlPublicationLinkTask.kt:152
- `info` at line 155 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — dokka-runners/dokka-gradle-plugin/src/main/kotlin/tasks/LogHtmlPublicationLinkTask.kt:155
- `info` at line 74 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — dokka-runners/dokka-gradle-plugin/src/main/kotlin/internal/LoggerAdapter.kt:74
- `debug` at line 76 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — dokka-runners/dokka-gradle-plugin/src/main/kotlin/internal/LoggerAdapter.kt:76
- `warn` at line 78 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — dokka-runners/dokka-gradle-plugin/src/main/kotlin/internal/LoggerAdapter.kt:78
- `error` at line 80 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — dokka-runners/dokka-gradle-plugin/src/main/kotlin/internal/LoggerAdapter.kt:80
What to do
- Interpolated log message defeats structured logging
X5 · Nullable reference types
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC1 · Text alternatives | 1.1.1, 1.2.2, 1.2.5 | Partial signal |
| AC2 · Forms & labels | 1.3.1, 3.3.2, 4.1.2 | Partial signal |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC4 · Keyboard semantics | 2.1.1, 2.4.3 | Partial signal |
| AC5 · ARIA correctness | 4.1.2 | Partial signal |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 49% | Weak — gated by R2, X4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 96% | Exemplary | Solid. |
| Maturity | 50% | Weak — gated by D34, M4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 47% | Weak — gated by R4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 57% | Adequate — gated by D29, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Accessibility | 28% | Weak — gated by AC1, AC2, AC3, AC4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 1 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 6 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 2 control(s) we could not find positive evidence for
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 60 check(s) not relevant to this codebase
- AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Java code is a Spring, JSR-330 or CDI singleton bean. No class in this Kotlin code is a Spring, JSR-330 or CDI singleton bean. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — AX6 reached only 6% of this repository's production lines — kotlin (43,292 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — the dev server (`npm run start`) exited before it served a page. Likely cause (our sandbox): `npm run` found no REDACTED in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read REDACTED: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered. This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no data at rest for these controls to protect.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named column (email, first_name, date_of_birth, phone_number, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~70040 lines of test source are present (.kt) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not included — the .kt suite was found but not re-run
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — symbol resolution incomplete — navigability not assessed
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — 54 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (265 value object(s))
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P2 Observability — This repository's JavaScript/TypeScript, JVM source (31 module(s), 567 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM, JavaScript/TypeScript source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a REDACTED, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — no C# was loaded; this repository's Java and Kotlin were read, and no request in it can be cancelled by a caller (Ktor, OkHttp's newCall or a URL stream, from a suspend function) — a Java request off Android takes no token: it is cancelled through the handle it returns (Future.cancel, Call.cancel, a Disposable), ambiently (io.grpc.Context) or by interrupting its thread, not through a parameter; a Kotlin request outside a suspend function has no caller's cancellation to honour
- X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — X24 reached only 6% of this repository's production lines — kotlin (43,292 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 140 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- <button> with no accessible text REDACTED:6893
- <button> with no accessible text REDACTED:7557
- <button> with no accessible text REDACTED:9099
- <button> with no accessible text REDACTED:9114
- <button> with no accessible text REDACTED:12621
- <button> with no accessible text REDACTED:12713
- Link with no accessible name dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/renderers/html/HtmlRenderer.kt:813
- Link with no accessible name dokka-subprojects/plugin-base/src/main/resources/dokka/templates/includes/footer.ftl:4
- Link with no accessible name dokka-subprojects/plugin-javadoc/src/main/resources/static_res/jquery/external/jquery/jquery.js:1389
- Link with no accessible name dokka-subprojects/plugin-javadoc/src/main/resources/static_res/jquery/external/jquery/jquery.js:2936
- <select> without a programmatic label dokka-subprojects/plugin-javadoc/src/main/resources/static_res/jquery/external/jquery/jquery.js:1333
- <select> without a programmatic label dokka-subprojects/plugin-javadoc/src/main/resources/static_res/jquery/external/jquery/jquery.js:1390
- <select> without a programmatic label dokka-subprojects/plugin-javadoc/src/main/resources/static_res/jquery/external/jquery/jquery.js:4961
- <select> without a programmatic label REDACTED:14110
- <input> without a programmatic label dokka-subprojects/plugin-javadoc/src/main/resources/static_res/jquery/external/jquery/jquery.js:2949
- <input> without a programmatic label REDACTED:5686
- <input> without a programmatic label REDACTED:7655
- <input> without a programmatic label REDACTED:17116
- REDACTED
- REDACTED
- REDACTED
- <img> without a text alternative REDACTED:7549
- <img> without a text alternative REDACTED:7561
- <textarea> without a programmatic label dokka-subprojects/plugin-javadoc/src/main/resources/static_res/jquery/external/jquery/jquery.js:4931
- Document without a <title> dokka-subprojects/plugin-base/src/main/resources/dokka/templates/base.ftl:5
- <html> without a lang dokka-subprojects/plugin-versioning/src/main/resources/dokka/not-found-version.html:2
- REDACTED
- REDACTED
- Unlisted import '@jetbrains/icons' dokka-subprojects/plugin-base-frontend/webpack.config.js:55
Serious — 413 finding(s)
- TodoComment dokka-subprojects/plugin-kotlin-as-java/src/test/kotlin/kotlinAsJavaPlugin/JvmNameTest.kt:102
- TodoComment dokka-subprojects/plugin-kotlin-as-java/src/main/kotlin/org/jetbrains/dokka/kotlinAsJava/CollectionExtensions.kt:7
- TodoComment dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/utils/CollectionExtensions.kt:7
- TodoComment dokka-subprojects/core/src/main/kotlin/org/jetbrains/dokka/transformers/documentation/DefaultDocumentableMerger.kt:318
- TodoComment dokka-subprojects/analysis-java-psi/src/main/kotlin/org/jetbrains/dokka/analysis/java/util/StdlibUtil.kt:11
- TodoComment dokka-subprojects/analysis-java-psi/src/main/kotlin/org/jetbrains/dokka/analysis/java/util/StdlibUtil.kt:22
- TodoComment dokka-subprojects/analysis-java-psi/src/main/kotlin/org/jetbrains/dokka/analysis/java/util/StdlibUtil.kt:25
- TodoComment dokka-subprojects/analysis-java-psi/src/main/kotlin/org/jetbrains/dokka/analysis/java/util/StdlibUtil.kt:28
- TodoComment dokka-subprojects/analysis-java-psi/src/main/kotlin/org/jetbrains/dokka/analysis/java/util/StdlibUtil.kt:31
- TodoComment dokka-subprojects/analysis-java-psi/src/main/kotlin/org/jetbrains/dokka/analysis/java/util/StdlibUtil.kt:34
- TodoComment dokka-subprojects/plugin-kotlin-as-java/src/main/kotlin/org/jetbrains/dokka/kotlinAsJava/converters/KotlinToJavaConverter.kt:115
- TodoComment dokka-subprojects/plugin-kotlin-as-java/src/main/kotlin/org/jetbrains/dokka/kotlinAsJava/converters/KotlinToJavaConverter.kt:446
- TodoComment dokka-subprojects/plugin-kotlin-as-java/src/main/kotlin/org/jetbrains/dokka/kotlinAsJava/converters/KotlinToJavaConverter.kt:455
- TodoComment dokka-subprojects/plugin-javadoc/src/test/kotlin/org/jetbrains/dokka/javadoc/Asserts.kt:10
- TodoComment dokka-subprojects/plugin-javadoc/src/main/kotlin/org/jetbrains/dokka/javadoc/renderer/JavadocContentToTemplateMapTranslator.kt:31
- TodoComment dokka-subprojects/plugin-javadoc/src/main/kotlin/org/jetbrains/dokka/javadoc/renderer/JavadocContentToTemplateMapTranslator.kt:218
- TodoComment dokka-subprojects/plugin-javadoc/src/main/kotlin/org/jetbrains/dokka/javadoc/renderer/JavadocContentToTemplateMapTranslator.kt:238
- TodoComment dokka-subprojects/plugin-javadoc/src/main/kotlin/org/jetbrains/dokka/javadoc/pages/JavadocPageNodes.kt:506
- TodoComment dokka-subprojects/plugin-base/src/test/kotlin/utils/TestUtils.kt:50
- TodoComment dokka-subprojects/plugin-base/src/test/kotlin/utils/TestUtils.kt:60
- TodoComment dokka-subprojects/analysis-kotlin-api/src/test/kotlin/org/jetbrains/dokka/test/EnumTemplatesTest.kt:95
- TodoComment dokka-subprojects/plugin-base/src/test/kotlin/utils/contentUtils.kt:12
- TodoComment dokka-subprojects/plugin-base/src/test/kotlin/utils/contentUtils.kt:145
- TodoComment dokka-subprojects/plugin-base/src/test/kotlin/utils/contentUtils.kt:294
- TodoComment dokka-subprojects/plugin-base/src/test/kotlin/translators/DefaultPsiToDocumentableTranslatorTest.kt:325
- Focus outline removed in CSS without a :focus replacement examples/gradle/dokka-versioning-multimodule-example/previousDocVersions/0.9/styles/main.css:1
- Focus outline removed in CSS without a :focus replacement examples/gradle/dokka-versioning-multimodule-example/previousDocVersions/0.9/styles/style.css:184
- Focus outline removed in CSS without a :focus replacement examples/gradle/dokka-versioning-multimodule-example/previousDocVersions/0.9/styles/style.css:803
- Focus outline removed in CSS without a :focus replacement dokka-subprojects/plugin-javadoc/src/main/resources/static_res/jquery/jquery-ui.css:26
- Focus outline removed in CSS without a :focus replacement dokka-subprojects/plugin-javadoc/src/main/resources/static_res/jquery/jquery-ui.css:117
- Focus outline removed in CSS without a :focus replacement dokka-subprojects/plugin-javadoc/src/main/resources/static_res/jquery/jquery-ui.css:495
- Focus outline removed in CSS without a :focus replacement dokka-subprojects/plugin-javadoc/src/main/resources/static_res/jquery/jquery-ui.structure.css:30
- Focus outline removed in CSS without a :focus replacement dokka-subprojects/plugin-javadoc/src/main/resources/static_res/jquery/jquery-ui.structure.css:121
- Focus outline removed in CSS without a :focus replacement dokka-subprojects/plugin-javadoc/src/main/resources/static_res/jquery/jquery-ui.structure.css:499
- Focus outline removed in CSS without a :focus replacement dokka-integration-tests/gradle/src/testExampleProjects/expectedData/exampleProjects/library-publishing-example/javadoc/jquery/jquery-ui.css:26
- Focus outline removed in CSS without a :focus replacement dokka-integration-tests/gradle/src/testExampleProjects/expectedData/exampleProjects/library-publishing-example/javadoc/jquery/jquery-ui.css:117
- Focus outline removed in CSS without a :focus replacement dokka-integration-tests/gradle/src/testExampleProjects/expectedData/exampleProjects/library-publishing-example/javadoc/jquery/jquery-ui.css:495
- Focus outline removed in CSS without a :focus replacement dokka-integration-tests/gradle/src/testExampleProjects/expectedData/exampleProjects/library-publishing-example/javadoc/jquery/jquery-ui.structure.css:30
- Focus outline removed in CSS without a :focus replacement dokka-integration-tests/gradle/src/testExampleProjects/expectedData/exampleProjects/library-publishing-example/javadoc/jquery/jquery-ui.structure.css:121
- Focus outline removed in CSS without a :focus replacement dokka-integration-tests/gradle/src/testExampleProjects/expectedData/exampleProjects/library-publishing-example/javadoc/jquery/jquery-ui.structure.css:499
- Focus outline removed in CSS without a :focus replacement dokka-integration-tests/gradle/src/testExampleProjects/expectedData/exampleProjects/javadoc-example/javadoc/jquery/jquery-ui.css:26
- Focus outline removed in CSS without a :focus replacement dokka-integration-tests/gradle/src/testExampleProjects/expectedData/exampleProjects/javadoc-example/javadoc/jquery/jquery-ui.css:117
- Focus outline removed in CSS without a :focus replacement dokka-integration-tests/gradle/src/testExampleProjects/expectedData/exampleProjects/javadoc-example/javadoc/jquery/jquery-ui.css:495
- Focus outline removed in CSS without a :focus replacement dokka-integration-tests/gradle/src/testExampleProjects/expectedData/exampleProjects/javadoc-example/javadoc/jquery/jquery-ui.structure.css:30
- Focus outline removed in CSS without a :focus replacement dokka-integration-tests/gradle/src/testExampleProjects/expectedData/exampleProjects/javadoc-example/javadoc/jquery/jquery-ui.structure.css:121
- Focus outline removed in CSS without a :focus replacement dokka-integration-tests/gradle/src/testExampleProjects/expectedData/exampleProjects/javadoc-example/javadoc/jquery/jquery-ui.structure.css:499
- Focus outline removed in CSS without a :focus replacement dokka-integration-tests/gradle/projects/ui-showcase/previousDocVersions/1.9/styles/style.css:297
- Focus outline removed in CSS without a :focus replacement dokka-integration-tests/gradle/projects/ui-showcase/previousDocVersions/1.9/styles/style.css:530
- Focus outline removed in CSS without a :focus replacement dokka-integration-tests/gradle/projects/ui-showcase/previousDocVersions/1.8/styles/style.css:297
- Focus outline removed in CSS without a :focus replacement dokka-integration-tests/gradle/projects/ui-showcase/previousDocVersions/1.8/styles/style.css:530
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Swallowed exception (empty catch) REDACTED:1975
- Swallowed exception (empty catch) REDACTED:1988
- Swallowed exception (empty catch) REDACTED:8048
- Swallowed exception (empty catch) REDACTED:8853
- Swallowed exception (empty catch) REDACTED:11099
- Swallowed exception (empty catch) REDACTED:17700
- Swallowed exception (empty catch) REDACTED:17703
- Swallowed exception (empty catch) dokka-subprojects/plugin-javadoc/src/main/resources/static_res/jquery/external/jquery/jquery.js:4442
- Swallowed exception (empty catch) dokka-subprojects/plugin-javadoc/src/main/resources/static_res/jquery/external/jquery/jquery.js:5122
- Swallowed exception (empty catch) dokka-subprojects/plugin-javadoc/src/main/resources/static_res/jquery/external/jquery/jquery.js:6340
- Swallowed exception (empty catch) dokka-subprojects/plugin-javadoc/src/main/resources/static_res/jquery/external/jquery/jquery.js:8872
- Swallowed exception (empty catch) dokka-subprojects/plugin-javadoc/src/main/resources/static_res/jquery/external/jquery/jquery.js:9970
- Anchor without href REDACTED:9028
- Anchor without href REDACTED:9044
- Anchor without href REDACTED:9063
- Anchor without href REDACTED:9079
- Anchor without href REDACTED:12623
- Anchor without href REDACTED:12922
- Anchor without href REDACTED:17304
- Anchor without href REDACTED:17637
- Anchor without href REDACTED:18578
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- ClassTooLong: DokkaSymbolVisitor dokka-subprojects/analysis-kotlin-symbols/src/main/kotlin/org/jetbrains/dokka/analysis/kotlin/symbols/translators/DefaultSymbolToDocumentableTranslator.kt:96
- ClassTooLong: HtmlRenderer dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/renderers/html/HtmlRenderer.kt:40
- ClassTooLong: DefaultPageCreator dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/translators/documentables/DefaultPageCreator.kt:37
- ClassTooLong: PageContentBuilder dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/translators/documentables/PageContentBuilder.kt:24
- ClassTooLong: JavaDocParser dokka-subprojects/analysis-java-psi/src/main/kotlin/com/intellij/java/syntax/parser/JavaDocParser.kt:30
- ClassTooLong: DokkaPsiParser dokka-subprojects/analysis-java-psi/src/main/kotlin/org/jetbrains/dokka/analysis/java/parsers/DokkaPsiParser.kt:33
- TooManyMethods: HtmlRenderer dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/renderers/html/HtmlRenderer.kt:40
- TooManyMethods: DefaultPageCreator dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/translators/documentables/DefaultPageCreator.kt:37
- TooManyMethods: MarkdownParser dokka-subprojects/analysis-markdown-jb/src/main/kotlin/org/jetbrains/dokka/analysis/markdown/jb/MarkdownParser.kt:28
- TooManyMethods: DokkaSymbolVisitor dokka-subprojects/analysis-kotlin-symbols/src/main/kotlin/org/jetbrains/dokka/analysis/kotlin/symbols/translators/DefaultSymbolToDocumentableTranslator.kt:96
- TooManyMethods: DocumentableContentBuilder dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/translators/documentables/PageContentBuilder.kt:66
- TooManyMethods: DefaultRenderer dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/renderers/DefaultRenderer.kt:22
- FileTooLong: translators/DefaultSymbolToDocumentableTranslator.kt dokka-subprojects/analysis-kotlin-symbols/src/main/kotlin/org/jetbrains/dokka/analysis/kotlin/symbols/translators/DefaultSymbolToDocumentableTranslator.kt
- FileTooLong: model/Documentable.kt dokka-subprojects/core/src/main/kotlin/org/jetbrains/dokka/model/Documentable.kt
- FileTooLong: html/HtmlRenderer.kt dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/renderers/html/HtmlRenderer.kt
- FileTooLong: documentables/DefaultPageCreator.kt dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/translators/documentables/DefaultPageCreator.kt
- FileTooLong: documentables/PageContentBuilder.kt dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/translators/documentables/PageContentBuilder.kt
- FileTooLong: parser/JavaDocParser.kt dokka-subprojects/analysis-java-psi/src/main/kotlin/com/intellij/java/syntax/parser/JavaDocParser.kt
- Duplicated block (10 lines × 2 locations) REDACTED:4684
- Duplicated block (10 lines × 2 locations) REDACTED:8709
- Duplicated block (10 lines × 2 locations) REDACTED:10215
- Duplicated block (10 lines × 2 locations) REDACTED:10883
- Duplicated block (10 lines × 2 locations) REDACTED:13901
- Duplicated block (10 lines × 2 locations) REDACTED:15387
- Duplicated block (8 lines × 2 locations) REDACTED:3379
- Duplicated block (8 lines × 2 locations) REDACTED:4700
- Duplicated block (8 lines × 2 locations) REDACTED:8536
- Duplicated block (8 lines × 2 locations) REDACTED:9435
- Duplicated block (8 lines × 2 locations) REDACTED:12191
- Duplicated block (8 lines × 2 locations) REDACTED:15833
- Duplicated block (7 lines × 2) dokka-runners/dokka-gradle-plugin/src/classicMain/kotlin/tasks/DokkaTask.kt:20
- Duplicated block (7 lines × 2) dokka-subprojects/core/src/main/kotlin/org/jetbrains/dokka/transformers/documentation/DefaultDocumentableMerger.kt:246
- Duplicated block (7 lines × 2) dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/transformers/documentables/DocumentableReplacerTransformer.kt:212
- Duplicated block (7 lines × 2) dokka-subprojects/core/src/main/kotlin/org/jetbrains/dokka/transformers/documentation/DefaultDocumentableMerger.kt:161
- Duplicated block (5 lines × 2) dokka-subprojects/analysis-kotlin-symbols/src/main/kotlin/org/jetbrains/dokka/analysis/kotlin/symbols/translators/DefaultSymbolToDocumentableTranslator.kt:858
- Duplicated block (5 lines × 2) dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/transformers/documentables/DocumentableReplacerTransformer.kt:47
- Duplicated block (5 lines × 2) dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/transformers/documentables/DocumentableReplacerTransformer.kt:118
- Duplicated block (5 lines × 2) dokka-subprojects/plugin-javadoc/src/main/kotlin/org/jetbrains/dokka/javadoc/signatures/JavadocSignatureProvider.kt:89
- Duplicated block (6 lines × 2 locations) REDACTED:4782
- Duplicated block (6 lines × 2 locations) REDACTED:4798
- Duplicated block (6 lines × 2 locations) REDACTED:10319
- Duplicated block (6 lines × 2 locations) REDACTED:11528
- Low contrast colour pair in CSS (3.8:1) dokka-subprojects/plugin-javadoc/src/main/resources/static_res/jquery/jquery-ui.css:982
- Low contrast colour pair in CSS (3.8:1) dokka-integration-tests/gradle/src/testExampleProjects/expectedData/exampleProjects/library-publishing-example/javadoc/jquery/jquery-ui.css:982
- Low contrast colour pair in CSS (3.8:1) dokka-integration-tests/gradle/src/testExampleProjects/expectedData/exampleProjects/javadoc-example/javadoc/jquery/jquery-ui.css:982
- Low contrast colour pair in CSS (4.4:1) dokka-subprojects/plugin-javadoc/src/main/resources/static_res/jquery/jquery-ui.css:1004
- Low contrast colour pair in CSS (4.4:1) dokka-integration-tests/gradle/src/testExampleProjects/expectedData/exampleProjects/library-publishing-example/javadoc/jquery/jquery-ui.css:1004
- Low contrast colour pair in CSS (4.4:1) dokka-integration-tests/gradle/src/testExampleProjects/expectedData/exampleProjects/javadoc-example/javadoc/jquery/jquery-ui.css:1004
- HackComment dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/transformers/documentables/JvmMappedMethodsDocumentableFilterTransformer.kt:61
- HackComment dokka-runners/runner-maven-plugin/src/main/kotlin/org/jetbrains/dokka/maven/DokkaMojo.kt:283
- HackComment dokka-runners/dokka-gradle-plugin/src/testFunctional/kotlin/HtmlAggregationWarningTest.kt:20
- REDACTED
- REDACTED
- REDACTED
- MethodTooLong: DocTagToContentConverter.buildContent dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/transformers/pages/comments/DocTagToContentConverter.kt:18
- MethodTooLong: SourceSetArgumentsParserKt.parseSourceSet dokka-runners/runner-cli/src/main/kotlin/org/jetbrains/dokka/SourceSetArgumentsParser.kt:12
- MethodTooLong: DocumentableVisibilityFilter.filterClasslikes dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/transformers/documentables/DocumentableVisibilityFilterTransformer.kt:261
- Change coupling: DocTagsFromIElementFactory.kt ↔ DocTagToContentConverter.kt dokka-subprojects/analysis-markdown-jb/src/main/kotlin/org/jetbrains/dokka/analysis/markdown/jb/factories/DocTagsFromIElementFactory.kt:1
- Change coupling: HtmlRenderer.kt ↔ DocTagToContentConverter.kt dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/renderers/html/HtmlRenderer.kt:1
- Change coupling: TestedVersions.kt ↔ TestedVersionsSource.kt dokka-integration-tests/gradle/src/main/kotlin/org/jetbrains/dokka/it/gradle/TestedVersions.kt:1
- Edited copy of a member (8 corresponding lines) dokka-subprojects/plugin-kotlin-as-java/src/main/kotlin/org/jetbrains/dokka/kotlinAsJava/jvmOverloads.kt:11
- Edited copy of a member (8 corresponding lines) dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/transformers/documentables/EmptyPackagesFilterTransformer.kt:19
- Edited copy of a member (8 corresponding lines) dokka-subprojects/analysis-kotlin-symbols/src/main/kotlin/org/jetbrains/dokka/analysis/kotlin/symbols/services/KotlinDocumentableSourceLanguageParser.kt:22
- Edited copy of a member (5 corresponding lines) dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/signatures/KotlinSignatureUtils.kt:46
- Edited copy of a member (5 corresponding lines) dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/transformers/documentables/DeprecatedDocumentableFilterTransformer.kt:45
- Edited copy of a member (5 corresponding lines) dokka-subprojects/core/src/main/kotlin/org/jetbrains/dokka/model/Documentable.kt:1004
- Duplicated block (15 lines × 2) dokka-subprojects/core/src/main/kotlin/org/jetbrains/dokka/model/Documentable.kt:236
- Duplicated block (15 lines × 2) dokka-subprojects/core/src/main/kotlin/org/jetbrains/dokka/model/Documentable.kt:342
- Duplicated block (15 lines × 2) dokka-subprojects/core/src/main/kotlin/org/jetbrains/dokka/model/Documentable.kt:456
- Duplicated block (11 lines × 2) dokka-runners/dokka-gradle-plugin/src/main/kotlin/tasks/DokkaGenerateTask.kt:370
- Duplicated block (11 lines × 2) dokka-subprojects/analysis-java-psi/src/main/kotlin/org/jetbrains/dokka/analysis/java/util/PsiUtil.kt:145
- Duplicated block (11 lines × 2) dokka-subprojects/plugin-all-modules-page/src/main/kotlin/org/jetbrains/dokka/allModulesPage/AllModulesPageGeneration.kt:67
- Duplicated block (5 lines × 4) dokka-subprojects/analysis-kotlin-symbols/src/main/kotlin/org/jetbrains/dokka/analysis/kotlin/symbols/translators/DefaultSymbolToDocumentableTranslator.kt:278
- Duplicated block (5 lines × 4) dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/transformers/documentables/DocumentableReplacerTransformer.kt:56
- Duplicated block (5 lines × 4) dokka-subprojects/plugin-kotlin-as-java/src/main/kotlin/org/jetbrains/dokka/kotlinAsJava/transformers/JvmNameDocumentableTransformer.kt:67
- Duplicated block (12 lines × 2 locations) REDACTED:9896
- Duplicated block (12 lines × 2 locations) REDACTED:12749
- Duplicated block (12 lines × 2 locations) REDACTED:13266
- Edited copy of a member (22 corresponding lines) dokka-subprojects/core/src/main/kotlin/org/jetbrains/dokka/pages/utils.kt:17
- Edited copy of a member (22 corresponding lines) dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/transformers/pages/DefaultSamplesTransformer.kt:28
- Edited copy of a member (15 corresponding lines) dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/transformers/documentables/DocumentableReplacerTransformer.kt:129
- Edited copy of a member (15 corresponding lines) dokka-subprojects/plugin-kotlin-as-java/src/main/kotlin/org/jetbrains/dokka/kotlinAsJava/converters/KotlinToJavaConverter.kt:368
- Edited copy of a member (13 corresponding lines) dokka-runners/dokka-gradle-plugin/src/classicMain/kotlin/tasks/DokkaTask.kt:17
- Edited copy of a member (13 corresponding lines) dokka-subprojects/analysis-kotlin-symbols/src/main/kotlin/org/jetbrains/dokka/analysis/kotlin/symbols/services/SymbolFullClassHierarchyBuilder.kt:50
- Edited copy of a member (6 corresponding lines) dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/transformers/documentables/DocumentableReplacerTransformer.kt:20
- Edited copy of a member (6 corresponding lines) dokka-subprojects/analysis-java-psi/src/main/kotlin/org/jetbrains/dokka/analysis/java/util/CoreCopyPaste.kt:12
- Edited copy of a member (10 corresponding lines) dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/signatures/KotlinSignatureProvider.kt:122
- Edited copy of a member (10 corresponding lines) dokka-subprojects/plugin-javadoc/src/main/kotlin/org/jetbrains/dokka/javadoc/signatures/JavadocSignatureProvider.kt:43
- Duplicated block (21 lines × 2) dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/renderers/DefaultRenderer.kt:193
- Duplicated block (21 lines × 2) dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/signatures/KotlinSignatureProvider.kt:279
- Duplicated block (16–17 lines × 2) dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/transformers/pages/DefaultSamplesTransformer.kt:29
- Duplicated block (16–17 lines × 2) dokka-subprojects/plugin-kotlin-as-java/src/main/kotlin/org/jetbrains/dokka/kotlinAsJava/converters/KotlinCompanion.kt:34
- Off the main sequence: dokka:dokka-subprojects:dokka-core
- Off the main sequence: dokka-integration-tests:utilities
- Forked directory tree (12 identical files, ~33268 lines × 2 trees) REDACTED:1
- Forked directory tree (12 identical files, ~33268 lines × 2 trees) REDACTED:1
- Duplicated block (19 lines × 2 locations) REDACTED:5569
- Duplicated block (19 lines × 2 locations) REDACTED:5999
- Duplicated block (15 lines × 2 locations) REDACTED:10901
- Duplicated block (15 lines × 2 locations) REDACTED:15296
- Duplicated block (11 lines × 2 locations) REDACTED:2818
- Duplicated block (11 lines × 2 locations) REDACTED:7720
- Duplicated block (7 lines × 2 locations) REDACTED:7740
- Duplicated block (7 lines × 2 locations) REDACTED:16762
- Complex function (anonymous) (cyclomatic 15, cognitive 14) REDACTED:18
- Complex function (anonymous) (cyclomatic 15, cognitive 14) REDACTED:723
- Swallowed exception (caught, then discarded) dokka-runners/dokka-gradle-plugin/src/main/kotlin/adapters/AndroidAdapter.kt:108
- Swallowed exception (caught, then discarded) dokka-runners/dokka-gradle-plugin/src/main/kotlin/adapters/AndroidAdapter.kt:112
- Empty <h1> heading dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/renderers/html/HtmlRenderer.kt:707
- Empty <h2> heading dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/renderers/html/HtmlRenderer.kt:708
- Empty <h3> heading dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/renderers/html/HtmlRenderer.kt:709
- Empty <h4> heading dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/renderers/html/HtmlRenderer.kt:710
- Empty <h5> heading dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/renderers/html/HtmlRenderer.kt:711
- Empty <h6> heading dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/renderers/html/HtmlRenderer.kt:712
- Page without a main landmark dokka-subprojects/plugin-versioning/src/main/resources/dokka/not-found-version.html:2
- Positive tabindex (1) dokka-subprojects/plugin-base/src/main/resources/dokka/templates/includes/header.ftl:5
- Low contrast colour pair in CSS (2.4:1) examples/gradle/dokka-versioning-multimodule-example/previousDocVersions/0.9/styles/style.css:821
- Low contrast colour pair in CSS (1.4:1) examples/gradle/dokka-versioning-multimodule-example/previousDocVersions/0.9/styles/style.css:826
- Low contrast colour pair in CSS (2.8:1) examples/gradle/dokka-versioning-multimodule-example/previousDocVersions/0.9/styles/style.css:831
- Low contrast colour pair in CSS (2.2:1) examples/gradle/dokka-versioning-multimodule-example/previousDocVersions/0.9/styles/style.css:836
- Low contrast colour pair in CSS (3.3:1) dokka-subprojects/plugin-base/src/main/resources/dokka/ui-kit/ui-kit.css:3253
- HtmlToDocTagConverter.createBlock (cyclomatic 44) dokka-subprojects/analysis-java-psi/src/main/kotlin/org/jetbrains/dokka/analysis/java/parsers/doctag/HtmlToDocTagConverter.kt:36
- DocTagToContentConverter.buildContent (cyclomatic 42) dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/transformers/pages/comments/DocTagToContentConverter.kt:18
- DocTagsFromIElementFactory.getInstance (cyclomatic 38) dokka-subprojects/analysis-markdown-jb/src/main/kotlin/org/jetbrains/dokka/analysis/markdown/jb/factories/DocTagsFromIElementFactory.kt:22
- JavaDocParser.parseDataItem (cyclomatic 33) dokka-subprojects/analysis-java-psi/src/main/kotlin/com/intellij/java/syntax/parser/JavaDocParser.kt:93
- DefaultSnippetToHtmlConverter.parseSnippet (cyclomatic 28) dokka-subprojects/analysis-java-psi/src/main/kotlin/org/jetbrains/dokka/analysis/java/parsers/doctag/SnippetToHtmlConverter.kt:169
- JavaDocParser.parseMarkdownReference (cyclomatic 20) dokka-subprojects/analysis-java-psi/src/main/kotlin/com/intellij/java/syntax/parser/JavaDocParser.kt:369
- DocumentableVisibilityFilter.filterClasslikes (cyclomatic 20) dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/transformers/documentables/DocumentableVisibilityFilterTransformer.kt:261
- index.initFilterSection (cyclomatic 20) dokka-subprojects/plugin-base-frontend/src/main/ui-kit/filter-section/index.ts:35
- NavigationDataProvider.chooseNavigationIcon (cyclomatic 19) dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/renderers/html/NavigationDataProvider.kt:51
- JavaDocParser.parseMarkdownReferenceChecked (cyclomatic 18) dokka-subprojects/analysis-java-psi/src/main/kotlin/com/intellij/java/syntax/parser/JavaDocParser.kt:268
- KdocMarkdownParserKt.parseFromKDocTag (cyclomatic 18) dokka-subprojects/analysis-kotlin-symbols/src/main/kotlin/org/jetbrains/dokka/analysis/kotlin/symbols/kdoc/KdocMarkdownParser.kt:19
- KotlinSignatureProvider.regularSignature (cyclomatic 18) dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/signatures/KotlinSignatureProvider.kt:166
- KotlinSignatureProvider.signatureForProjection (cyclomatic 18) dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/signatures/KotlinSignatureProvider.kt:477
- renderableFromLabel (cyclomatic 17) REDACTED:100
- DefaultSnippetToHtmlConverter.parseSnippet (cognitive 83) dokka-subprojects/analysis-java-psi/src/main/kotlin/org/jetbrains/dokka/analysis/java/parsers/doctag/SnippetToHtmlConverter.kt:169
- JavaDocParser.parseDataItem (cognitive 47) dokka-subprojects/analysis-java-psi/src/main/kotlin/com/intellij/java/syntax/parser/JavaDocParser.kt:93
- JavaDocParser.parseMarkdownReference (cognitive 37) dokka-subprojects/analysis-java-psi/src/main/kotlin/com/intellij/java/syntax/parser/JavaDocParser.kt:369
- NavigationDataProvider.chooseNavigationIcon (cognitive 35) dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/renderers/html/NavigationDataProvider.kt:51
- JavaDocParser.parseMarkdownReferenceChecked (cognitive 33) dokka-subprojects/analysis-java-psi/src/main/kotlin/com/intellij/java/syntax/parser/JavaDocParser.kt:268
- DocumentableVisibilityFilter.filterClasslikes (cognitive 25) dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/transformers/documentables/DocumentableVisibilityFilterTransformer.kt:261
- Parser.extractKDocSections (cognitive 24) dokka-subprojects/analysis-markdown-jb/src/main/kotlin/org/jetbrains/dokka/analysis/markdown/jb/Parser.kt:74
- PsiElementToHtmlConverterKt.stringifyElementAsText (cognitive 21) dokka-subprojects/analysis-java-psi/src/main/kotlin/org/jetbrains/dokka/analysis/java/parsers/doctag/PsiElementToHtmlConverter.kt:220
- platform-content-handler.handleAnchor (cognitive 21) dokka-subprojects/plugin-base/src/main/resources/dokka/scripts/platform-content-handler.js:84
- DokkaSymbolVisitor.getDokkaModality (cognitive 20) dokka-subprojects/analysis-kotlin-symbols/src/main/kotlin/org/jetbrains/dokka/analysis/kotlin/symbols/translators/DefaultSymbolToDocumentableTranslator.kt:1125
- KotlinSignatureProvider.regularSignature (cognitive 20) dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/signatures/KotlinSignatureProvider.kt:166
- FocusTrap.handleKeyDown (cognitive 20) dokka-subprojects/plugin-base-frontend/src/main/ui-kit/dropdown/focus-trap.ts:37
- HtmlToDocTagConverter.createBlock (cognitive 18) dokka-subprojects/analysis-java-psi/src/main/kotlin/org/jetbrains/dokka/analysis/java/parsers/doctag/HtmlToDocTagConverter.kt:36
- index.initFilterSection (cognitive 18) dokka-subprojects/plugin-base-frontend/src/main/ui-kit/filter-section/index.ts:35
- DefaultSnippetToHtmlConverter.convertSnippet (cognitive 17) dokka-subprojects/analysis-java-psi/src/main/kotlin/org/jetbrains/dokka/analysis/java/parsers/doctag/SnippetToHtmlConverter.kt:86
- DirectiveBasedHtmlTemplateProcessingStrategy.extractCommandsFromComments (cognitive 17) dokka-subprojects/plugin-templating/src/main/kotlin/org/jetbrains/dokka/templates/DirectiveBasedTemplateProcessing.kt:64
- renderableFromLabel (cognitive 17) REDACTED:100
- DefaultSnippetToHtmlConverter.lines (cognitive 16) dokka-subprojects/analysis-java-psi/src/main/kotlin/org/jetbrains/dokka/analysis/java/parsers/doctag/SnippetToHtmlConverter.kt:413
- DokkaSymbolVisitor.toDokkaVisibility (cognitive 16) dokka-subprojects/analysis-kotlin-symbols/src/main/kotlin/org/jetbrains/dokka/analysis/kotlin/symbols/translators/DefaultSymbolToDocumentableTranslator.kt:1226
- REDACTED
- REDACTED
- REDACTED
- Members sharing a duplicated core (7 members, 50+ identical tokens) dokka-subprojects/core/src/main/kotlin/org/jetbrains/dokka/transformers/documentation/DefaultDocumentableMerger.kt:149
- Edited copy of a member (66 corresponding lines) dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/transformers/documentables/DocumentableReplacerTransformer.kt:42
- Edited copy of a member (46 corresponding lines) dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/signatures/KotlinSignatureProvider.kt:279
- Edited copy of a member (32 corresponding lines) dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/renderers/DefaultRenderer.kt:182
- Edited copy of a member (24 corresponding lines) dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/translators/documentables/PageContentBuilder.kt:232
- Edited copies of one member (3 members, 14+ corresponding lines) dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/transformers/documentables/DocumentableReplacerTransformer.kt:27
- Edited copy of a member (12 corresponding lines) dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/transformers/documentables/DocumentableVisibilityFilterTransformer.kt:172
- Edited copy of a member (16 corresponding lines) dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/transformers/pages/DefaultSamplesTransformer.kt:95
- Edited copy of a member (18 corresponding lines) dokka-subprojects/core/src/main/kotlin/org/jetbrains/dokka/model/Documentable.kt:453
- Edited copies of one member (4 members, 16+ corresponding lines) dokka-subprojects/core/src/main/kotlin/org/jetbrains/dokka/model/Documentable.kt:235
- Edited copies of one member (3 members, 8+ corresponding lines) dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/transformers/documentables/DocumentableReplacerTransformer.kt:170
- Edited copy of a member (7 corresponding lines) dokka-subprojects/analysis-kotlin-symbols/src/main/kotlin/org/jetbrains/dokka/analysis/kotlin/symbols/translators/AnnotationTranslator.kt:173
- Edited copy of a member (9 corresponding lines) dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/renderers/DefaultRenderer.kt:241
- Edited copy of a member (2 corresponding lines) dokka-subprojects/core/src/main/kotlin/org/jetbrains/dokka/pages/PageNodes.kt:98
- Edited copy of a member (1 corresponding lines) dokka-subprojects/core/src/main/kotlin/org/jetbrains/dokka/pages/PageNodes.kt:200
- Edited copy of a member (3 corresponding lines) dokka-subprojects/analysis-java-psi/src/main/kotlin/org/jetbrains/dokka/analysis/java/parsers/DokkaPsiParser.kt:533
- Edited copies of one member (3 members, 10+ corresponding lines) dokka-subprojects/analysis-java-psi/src/main/kotlin/org/jetbrains/dokka/analysis/java/doccomment/JavaDocComment.kt:72
- Edited copy of a member (4 corresponding lines) dokka-subprojects/plugin-kotlin-playground-samples/src/main/kotlin/org/jetbrains/dokka/kotlinPlaygroundSamples/KotlinPlaygroundSamplesInstaller.kt:56
- Duplicated block (7–13 lines × 3) dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/transformers/documentables/DocumentableVisibilityFilterTransformer.kt:350
- Duplicated block (13 lines × 2) dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/transformers/pages/DefaultSamplesTransformer.kt:95
- Duplicated block (11–12 lines × 2) dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/transformers/documentables/SuppressedByConditionDocumentableFilterTransformer.kt:58
- Duplicated block (25 lines × 2) dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/transformers/pages/DefaultSamplesTransformer.kt:61
- Duplicated block (11 lines × 4) dokka-subprojects/analysis-kotlin-symbols/src/main/kotlin/org/jetbrains/dokka/analysis/kotlin/symbols/translators/DefaultSymbolToDocumentableTranslator.kt:267
- Duplicated block (10 lines × 2) dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/signatures/KotlinSignatureProvider.kt:306
- Duplicated block (8–9 lines × 3) dokka-subprojects/analysis-kotlin-symbols/src/main/kotlin/org/jetbrains/dokka/analysis/kotlin/symbols/translators/DefaultSymbolToDocumentableTranslator.kt:279
- Duplicated block (8–9 lines × 2) dokka-subprojects/plugin-javadoc/src/main/kotlin/org/jetbrains/dokka/javadoc/signatures/JavadocSignatureProvider.kt:215
- Duplicated block (7 lines × 3) dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/transformers/documentables/DocumentableReplacerTransformer.kt:59
- Duplicated block (6 lines × 3) dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/transformers/documentables/SuppressedByConditionDocumentableFilterTransformer.kt:63
- Duplicated block (5 lines × 3) dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/transformers/documentables/SuppressedByConditionDocumentableFilterTransformer.kt:61
- Duplicated block (2–5 lines × 7) dokka-subprojects/core/src/main/kotlin/org/jetbrains/dokka/transformers/documentation/DefaultDocumentableMerger.kt:150
- Duplicated block (9 lines × 4) dokka-subprojects/analysis-java-psi/src/main/kotlin/org/jetbrains/dokka/analysis/java/util/StdlibUtil.kt:12
- Duplicated block (8 lines × 2) dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/renderers/html/htmlPreprocessors.kt:93
- Duplicated block (6 lines × 4) dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/transformers/pages/annotations/SinceKotlinTransformer.kt:113
- Edited copy of a member (11 corresponding lines) dokka-subprojects/core-test-api/src/main/kotlin/org/jetbrains/dokka/testApi/configuration.kt:83
- Unstable project dokka:dokka-subprojects:plugin-gfm-template-processing
- Low cohesion: AbstractIntegrationTest (LCOM4 9) dokka-integration-tests/utilities/src/main/kotlin/org/jetbrains/dokka/it/AbstractIntegrationTest.kt:16
- Duplicated block with local edits (38 matched lines × 2 locations) REDACTED:225
- Duplicated block (37 lines × 2 locations) dokka-subprojects/plugin-base/src/main/resources/dokka/scripts/safe-local-storage_blocking.js:7
- Duplicated block (35 lines × 2 locations) REDACTED:1175
- Duplicated block (27 lines × 2 locations) REDACTED:1088
- Duplicated block (23 lines × 2 locations) REDACTED:9029
- Duplicated block (22 lines × 2 locations) REDACTED:10169
- Duplicated block (18 lines × 2 locations) REDACTED:10754
- Duplicated block (16 lines × 2 locations) REDACTED:10241
- Duplicated block (9 lines × 2 locations) REDACTED:5333
- Duplicated block with local edits (7 matched lines × 2 locations) dokka-subprojects/plugin-base/src/main/resources/dokka/scripts/platform-content-handler.js:182
- Duplicated block (5 lines × 2 locations) REDACTED:1816
- Complex function _generateHTML (cyclomatic 88, cognitive 220) REDACTED:8978
- Complex function _doKeyDown (cyclomatic 45, cognitive 76) REDACTED:7919
- Complex function parseDate (cyclomatic 42, cognitive 49) REDACTED:8457
- Complex function drag (cyclomatic 33, cognitive 48) REDACTED:10865
- Complex function _respectSize (cyclomatic 29, cognitive 20) REDACTED:11619
- Complex function _generatePosition (cyclomatic 27, cognitive 57) REDACTED:10377
- Complex function _contactContainers (cyclomatic 27, cognitive 57) REDACTED:16472
- Complex function _generateMonthYearHeader (cyclomatic 27, cognitive 46) REDACTED:9237
- Complex function formatDate (cyclomatic 27, cognitive 42) REDACTED:8670
- Complex function _clear (cyclomatic 27, cognitive 36) REDACTED:16938
- Complex function _generatePosition (cyclomatic 26, cognitive 47) REDACTED:16803
- Complex function (anonymous) (cyclomatic 26, cognitive 16) REDACTED:13389
- Complex function (anonymous) (cyclomatic 24, cognitive 32) REDACTED:13966
- Complex function resize (cyclomatic 23, cognitive 33) REDACTED:11922
- Complex function _keydown (cyclomatic 23, cognitive 20) REDACTED:5174
- Complex function _mouseDrag (cyclomatic 22, cognitive 36) REDACTED:15876
- Complex function drag (cyclomatic 22, cognitive 33) REDACTED:10785
- Complex function _showDatepicker (cyclomatic 22, cognitive 27) REDACTED:8059
- Complex function keydown (cyclomatic 22, cognitive 13) REDACTED:15411
- Complex function _mouseStart (cyclomatic 20, cognitive 22) REDACTED:15658
- Complex function resize (cyclomatic 19, cognitive 24) REDACTED:12143
- Complex function _setOption (cyclomatic 19, cognitive 23) REDACTED:12900
- Complex function _setContainment (cyclomatic 19, cognitive 22) REDACTED:16713
- Complex function _setContainment (cyclomatic 19, cognitive 18) REDACTED:10259
- Complex function _refreshValue (cyclomatic 18, cognitive 33) REDACTED:15330
- Complex function _optionDatepicker (cyclomatic 18, cognitive 25) REDACTED:7829
- Complex function (anonymous) (cyclomatic 18, cognitive 22) REDACTED:3072
- Complex function _mouseMove (cyclomatic 18, cognitive 20) REDACTED:9644
- Complex function keydown (cyclomatic 18, cognitive 13) REDACTED:14521
- Complex function _hideDatepicker (cyclomatic 17, cognitive 33) REDACTED:8237
- Complex function (anonymous) (cyclomatic 17, cognitive 17) REDACTED:13526
- Complex function _eventHandler (cyclomatic 17, cognitive 15) REDACTED:18215
- Complex function set (cyclomatic 16, cognitive 24) REDACTED:1960
- Complex function (anonymous) (cyclomatic 16, cognitive 18) REDACTED:3515
- Complex function _setOption (cyclomatic 16, cognitive 13) REDACTED:15156
- Complex function _intersectsWith (cyclomatic 15, cognitive 17) REDACTED:16115
- Complex function _checkOffset (cyclomatic 14, cognitive 13) REDACTED:8199
- Complex function _animate (cyclomatic 14, cognitive 11) REDACTED:4868
- REDACTED: 15970 lines of code REDACTED:1
- Test Coverage
- No test script
- Dead file (~228 LoC) dokka-subprojects/plugin-base-frontend/src/main/components/search/search.tsx
- Dead file (~91 LoC) dokka-subprojects/plugin-base-frontend/src/main/components/search/dokkaFuzzyFilter.tsx
- Dead file (~61 LoC) dokka-subprojects/plugin-base-frontend/src/main/components/utils/hotkey.ts
- Dead file (~55 LoC) dokka-subprojects/plugin-base-frontend/src/main/components/search/types.ts
- Dead file (~34 LoC) dokka-subprojects/plugin-base-frontend/src/main/components/search/searchResultRow.tsx
- Dead file (~33 LoC) dokka-subprojects/plugin-base-frontend/src/main/components/search/dokkaSearchAnchor.tsx
- Dead file (~30 LoC) dokka-subprojects/plugin-base-frontend/src/main/components/utils/arrayUtils.ts
- Dead file (~26 LoC) dokka-subprojects/plugin-base-frontend/src/main/components/root.tsx
- Dead file (~23 LoC) dokka-subprojects/plugin-base-frontend/src/main/components/utils/os.ts
- Dead file (~17 LoC) dokka-subprojects/plugin-base-frontend/src/main/components/app/index.tsx
- Dead file (~11 LoC) dokka-subprojects/plugin-base-frontend/src/main/components/utils/requests.tsx
- Unused dependency '@jetbrains/logos'
- Unused dependency 'lodash'
- Disposable created and abandoned in the function that made it dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/renderers/FileWriter.kt:79
Minor — 210 finding(s)
- Orphaned file dokka-subprojects/plugin-kotlin-as-java/src/main/kotlin/org/jetbrains/dokka/kotlinAsJava/converters/KotlinToJavaConverter.kt:1
- Orphaned file dokka-runners/dokka-gradle-plugin/src/main/kotlin/internal/PluginFeaturesService.kt:1
- Orphaned file dokka-runners/dokka-gradle-plugin/src/classicMain/kotlin/GradleDokkaSourceSetBuilder.kt:1
- Orphaned file dokka-subprojects/plugin-javadoc/src/main/kotlin/org/jetbrains/dokka/javadoc/pages/JavadocPageNodes.kt:1
- Orphaned file dokka-subprojects/core/src/main/kotlin/org/jetbrains/dokka/pages/ContentNodes.kt:1
- Orphaned file dokka-runners/dokka-gradle-plugin/src/main/kotlin/tasks/DokkaGenerateTask.kt:1
- Orphaned file dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/translators/documentables/DescriptionSections.kt:1
- Orphaned file dokka-subprojects/plugin-gfm/src/main/kotlin/org/jetbrains/dokka/gfm/renderer/CommonmarkRenderer.kt:1
- Orphaned file dokka-subprojects/plugin-javadoc/src/main/kotlin/org/jetbrains/dokka/javadoc/renderer/JavadocContentToTemplateMapTranslator.kt:1
- Orphaned file dokka-integration-tests/gradle/src/main/kotlin/org/jetbrains/dokka/it/gradle/junit/DokkaGradlePluginTestExtension.kt:1
- Orphaned file dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/DokkaBase.kt:1
- Orphaned file dokka-subprojects/analysis-java-psi/src/main/kotlin/org/jetbrains/dokka/analysis/java/parsers/JavaDocCommentParser.kt:1
- Orphaned file dokka-subprojects/plugin-javadoc/src/main/kotlin/org/jetbrains/dokka/javadoc/JavadocPageCreator.kt:1
- Orphaned file dokka-runners/dokka-gradle-plugin/src/classicMain/kotlin/tasks/AbstractDokkaTask.kt:1
- Orphaned file dokka-subprojects/core/src/main/kotlin/org/jetbrains/dokka/configuration.kt:1
- Orphaned file dokka-subprojects/plugin-javadoc/src/main/kotlin/org/jetbrains/dokka/javadoc/renderer/SearchScriptsCreator.kt:1
- Orphaned file dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/renderers/DefaultRenderer.kt:1
- Orphaned file dokka-runners/dokka-gradle-plugin/src/main/kotlin/adapters/AndroidAdapter.kt:1
- Orphaned file dokka-runners/dokka-gradle-plugin/src/main/kotlin/dependencies/FormatDependenciesManager.kt:1
- Orphaned file dokka-subprojects/core/src/main/kotlin/org/jetbrains/dokka/plugability/DokkaContext.kt:1
- Orphaned file dokka-runners/dokka-gradle-plugin/src/main/kotlin/formats/DokkaHtmlPlugin.kt:1
- Orphaned file dokka-subprojects/plugin-kotlin-as-java/src/main/kotlin/org/jetbrains/dokka/kotlinAsJava/signatures/JavaSignatureProvider.kt:1
- Orphaned file dokka-subprojects/plugin-javadoc/src/main/kotlin/org/jetbrains/dokka/javadoc/renderer/KorteJavadocRenderer.kt:1
- Orphaned file dokka-subprojects/core/src/main/kotlin/org/jetbrains/dokka/defaultConfiguration.kt:1
- Orphaned file dokka-subprojects/core-test-api/src/main/kotlin/org/jetbrains/dokka/testApi/testRunner/TestRunner.kt:1
- README/code drift CONTRIBUTING.md:161
- README/code drift dokka-subprojects/plugin-gfm/README.md:4
- README/code drift dokka-subprojects/plugin-gfm/README.md:14
- README/code drift dokka-subprojects/plugin-gfm/README.md:74
- README/code drift dokka-subprojects/plugin-gfm/README.md:97
- README/code drift dokka-subprojects/plugin-gfm/README.md:108
- README/code drift dokka-subprojects/plugin-jekyll/README.md:4
- README/code drift dokka-subprojects/plugin-jekyll/README.md:15
- README/code drift dokka-subprojects/plugin-jekyll/README.md:52
- README/code drift dokka-subprojects/plugin-jekyll/README.md:75
- README/code drift dokka-subprojects/plugin-jekyll/README.md:86
- Interpolated log message defeats structured logging dokka-runners/dokka-gradle-plugin/src/main/kotlin/tasks/LogHtmlPublicationLinkTask.kt:115
- Interpolated log message defeats structured logging dokka-runners/dokka-gradle-plugin/src/main/kotlin/tasks/LogHtmlPublicationLinkTask.kt:152
- Interpolated log message defeats structured logging dokka-runners/dokka-gradle-plugin/src/main/kotlin/tasks/LogHtmlPublicationLinkTask.kt:155
- Interpolated log message defeats structured logging dokka-runners/dokka-gradle-plugin/src/main/kotlin/internal/LoggerAdapter.kt:74
- Interpolated log message defeats structured logging dokka-runners/dokka-gradle-plugin/src/main/kotlin/internal/LoggerAdapter.kt:76
- Interpolated log message defeats structured logging dokka-runners/dokka-gradle-plugin/src/main/kotlin/internal/LoggerAdapter.kt:78
- Interpolated log message defeats structured logging dokka-runners/dokka-gradle-plugin/src/main/kotlin/internal/LoggerAdapter.kt:80
- Duplicated predicate build-settings-logic/settings.gradle.kts:61
- Duplicated predicate dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/renderers/html/HtmlRenderer.kt:85
- Duplicated predicate dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/renderers/html/HtmlRenderer.kt:153
- Duplicated predicate dokka-runners/dokka-gradle-plugin/src/classicMain/kotlin/kotlin/KotlinNativeDistributionAccessor.kt:54
- Duplicated predicate dokka-subprojects/analysis-java-psi/src/main/kotlin/org/jetbrains/dokka/analysis/java/util/CoreCopyPaste.kt:22
- Duplicated predicate dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/renderers/html/HtmlRenderer.kt:1059
- Implementation type on the public API dokka-runners/dokka-gradle-plugin/src/classicMain/kotlin/internal/AbstractDokkaTaskExtensions.kt:1
- Implementation type on the public API dokka-runners/dokka-gradle-plugin/src/main/kotlin/internal/GradlePropertiesFileSource.kt:21
- Implementation type on the public API dokka-runners/dokka-gradle-plugin/src/main/kotlin/internal/PluginFeaturesService.kt:39
- Implementation type on the public API dokka-runners/dokka-gradle-plugin/src/main/kotlin/internal/PluginFeaturesService.kt:217
- Implementation type on the public API dokka-runners/dokka-gradle-plugin/src/main/kotlin/internal/compat.locateOrRegisterMetadataDependencyTransformationTask.kt:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Most significant orphaned file dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/translators/documentables/PageContentBuilder.kt:1
- Most significant orphaned file dokka-subprojects/analysis-java-psi/src/main/kotlin/org/jetbrains/dokka/analysis/java/parsers/doctag/SnippetToHtmlConverter.kt:1
- Most significant orphaned file dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/transformers/documentables/DocumentableVisibilityFilterTransformer.kt:1
- Diagnostic log message is built whether or not it is wanted dokka-subprojects/analysis-kotlin-symbols/src/main/kotlin/org/jetbrains/dokka/analysis/kotlin/symbols/translators/AnnotationTranslator.kt:96
- Diagnostic log message is built whether or not it is wanted dokka-subprojects/analysis-kotlin-symbols/src/main/kotlin/org/jetbrains/dokka/analysis/kotlin/symbols/translators/TypeTranslator.kt:247
- Off-boarding risk: anonymized user #1
- Further sole-owners (lower concentration)
- `externalDri` spells `Dri` where 26 names in the project spell it `DRI` dokka-subprojects/analysis-kotlin-symbols/src/main/kotlin/org/jetbrains/dokka/analysis/kotlin/symbols/kdoc/KdocMarkdownParser.kt:19
- `createSmallHTML` spells `HTML` where 18 names in the project spell it `Html` dokka-subprojects/plugin-base/src/main/kotlin/org/jetbrains/dokka/base/renderers/html/HtmlRenderer.kt:958
- Projects may be oversized for their cohesion
- Concentrated knowledge decay
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No dependency-update automation REDACTED:38
- No changelog
Minor — 3 finding(s)
- Outdated (compile): org.jetbrains.kotlin:kotlin-stdlib
- Outdated (compile): org.jetbrains:annotations
- Outdated (compile): org.jetbrains.kotlin:kotlin-stdlib
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-b521d0bddda5460fb02da2ca3cde9fa0/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-b521d0bddda5460fb02da2ca3cde9fa0/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude docs --exclude docs-developer --exclude dokka-integration-tests/gradle/projects --exclude dokka-integration-tests/gradle/src/testExampleProjects/expectedData --exclude dokka-runners/dokka-gradle-plugin/src/testFunctional/resources --exclude examples . | 87 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 55 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 54 file(s) — `dokka-runners/dokka-gradle-plugin/src/classicMain/kotlin/DokkaMultiModuleFileLayout.kt`, `dokka-runners/dokka-gradle-plugin/src/classicMain/kotlin/tasks/AbstractDokkaLeafTask.kt`, `dokka-runners/dokka-gradle-plugin/src/classicMain/kotlin/tasks/AbstractDokkaParentTask.kt`, `dokka-runners/dokka-gradle-plugin/src/classicMain/kotlin/tasks/DokkaCollectorTask.kt`, `dokka-runners/dokka-gradle-plugin/src/classicMain/kotlin/tasks/DokkaMultiModuleTask.kt`, … (+49 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |