Executive summary
mikepenz/AboutLibraries is rated At risk because critical security findings are open, most of them in the packages it uses. Its score is held back in part because it has form fields without a label. It scores 52 out of 100, which the At risk rating leaves unchanged.
Accessibility, at 31, is the weakest lens and counts most in the score. The best first step is labelling the form fields and buttons, worth about 10 points. Fixing focus, motion and contrast comes next, worth about 9 points. Raising Accessibility to 70 would lift the score to about 69.
Twelve form fields can't be read by a screen reader. Ten known security holes in the packages the code depends on can be used by attackers, and two secrets can leak from the build pipeline. Labelling the form fields, updating the vulnerable packages and limiting each secret to its own step would close these risks. The password or key in the code's history needs replacing, with the old one switched off.
The product code is 13,752 lines, about €17,000 to rebuild.
If Accessibility rose from 31 to 70, the lowest score rated Strong, the score would rise from 52 to about 69.
New since the last survey: 50 findings
- Code Duplication · Edited copy of a member (34 corresponding lines) aboutlibraries-compose-m2/src/commonMain/kotlin/com/mikepenz/aboutlibraries/ui/compose/SharedLibraries.kt
- Code Duplication · Edited copy of a member (84 corresponding lines) aboutlibraries-compose/src/commonMain/kotlin/com/mikepenz/aboutlibraries/ui/compose/variant/refined/RefinedHeader.kt
- Code Duplication · Edited copy of a member (58 corresponding lines) aboutlibraries-core/src/androidMain/kotlin/com/mikepenz/aboutlibraries/util/AndroidParser.kt
- Code Duplication · Edited copy of a member (57 corresponding lines) aboutlibraries-compose-m2/src/commonMain/kotlin/com/mikepenz/aboutlibraries/ui/compose/style/M2LibrariesStyle.kt
- Code Duplication · Edited copy of a member (42 corresponding lines) aboutlibraries-compose-m2/src/commonMain/kotlin/com/mikepenz/aboutlibraries/ui/compose/SharedLibraries.kt
- Code Duplication · Edited copy of a member (30 corresponding lines) aboutlibraries-compose-m2/src/commonMain/kotlin/com/mikepenz/aboutlibraries/ui/compose/SharedLibraries.kt
- Code Duplication · Edited copy of a member (30 corresponding lines) aboutlibraries-compose-m2/src/commonMain/kotlin/com/mikepenz/aboutlibraries/ui/compose/component/LibrariesChip.kt
- Code Duplication · Edited copy of a member (11 corresponding lines) plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/util/parser/LibraryReader.kt
- Code Duplication · Edited copy of a member (11 corresponding lines) aboutlibraries-core/src/androidMain/kotlin/com/mikepenz/aboutlibraries/util/AndroidExtensions.kt
- Code Duplication · Edited copy of a member (8 corresponding lines) aboutlibraries-core/src/androidMain/kotlin/com/mikepenz/aboutlibraries/util/AndroidExtensions.kt
- Code Duplication · Duplicated block (34–35 lines × 2) aboutlibraries-compose-m2/src/commonMain/kotlin/com/mikepenz/aboutlibraries/ui/compose/SharedLibraries.kt
- Code Duplication · Duplicated block (22–24 lines × 2) aboutlibraries-compose-m2/src/commonMain/kotlin/com/mikepenz/aboutlibraries/ui/compose/SharedLibraries.kt
- Code Duplication · Duplicated block (20 lines × 3) aboutlibraries-compose/src/commonMain/kotlin/com/mikepenz/aboutlibraries/ui/compose/variant/refined/RefinedHeader.kt
- Code Duplication · Duplicated block (19 lines × 2) aboutlibraries-compose-m2/src/commonMain/kotlin/com/mikepenz/aboutlibraries/ui/compose/style/M2VariantTokens.kt
- Code Duplication · Duplicated block (18 lines × 2) aboutlibraries-compose-m2/src/commonMain/kotlin/com/mikepenz/aboutlibraries/ui/compose/component/LibrariesChip.kt
- Code Duplication · Duplicated block (14–16 lines × 3) aboutlibraries-compose-m2/src/commonMain/kotlin/com/mikepenz/aboutlibraries/ui/compose/style/M2VariantTokens.kt
- Code Duplication · Duplicated block (16 lines × 2) aboutlibraries-compose-m2/src/commonMain/kotlin/com/mikepenz/aboutlibraries/ui/compose/SharedLibraries.kt
- Code Duplication · Duplicated block (16 lines × 2) aboutlibraries-compose/src/commonMain/kotlin/com/mikepenz/aboutlibraries/ui/compose/variant/refined/RefinedRow.kt
- Code Duplication · Duplicated block (15 lines × 2) aboutlibraries-compose-m2/src/commonMain/kotlin/com/mikepenz/aboutlibraries/ui/compose/style/M2VariantTokens.kt
- Code Duplication · Duplicated block (14 lines × 2) plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/AboutLibrariesExportComplianceTask.kt
- Code Duplication · Duplicated block (14 lines × 2) plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/AboutLibrariesExportComplianceTask.kt
- Code Duplication · Duplicated block (10 lines × 3) plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/AboutLibrariesPluginAndroidExtension.kt
- Code Duplication · Duplicated block (10 lines × 2) aboutlibraries-compose-m3/src/commonMain/kotlin/com/mikepenz/aboutlibraries/ui/compose/m3/SharedLibraries.kt
- Code Duplication · Duplicated block (9 lines × 2) aboutlibraries-core/src/androidMain/kotlin/com/mikepenz/aboutlibraries/util/AndroidParser.kt
- Code Duplication · Duplicated block (9 lines × 2) app/src/main/kotlin/com/mikepenz/aboutlibraries/sample/ComposeActivity.kt
- Code Duplication · Duplicated block (10 lines × 2) aboutlibraries-compose/src/commonMain/kotlin/com/mikepenz/aboutlibraries/ui/compose/variant/refined/RefinedHeader.kt
- Code Duplication · Duplicated block (12 lines × 3) aboutlibraries-compose-m2/src/androidMain/kotlin/com/mikepenz/aboutlibraries/ui/compose/SharedLibraries.android.kt
- Code Duplication · Duplicated block (10 lines × 2) aboutlibraries-compose-m2/src/commonMain/kotlin/com/mikepenz/aboutlibraries/ui/compose/SharedLibraries.kt
- Code Duplication · Duplicated block (10 lines × 3) aboutlibraries-compose-m2/src/commonMain/kotlin/com/mikepenz/aboutlibraries/ui/compose/SharedLibraries.kt
- Code Duplication · Duplicated block (6 lines × 2) aboutlibraries-compose/src/commonMain/kotlin/com/mikepenz/aboutlibraries/ui/compose/variant/refined/RefinedRow.kt
- Code Duplication · Edited copy of a member (20 corresponding lines) sample/android/src/debug/kotlin/com/mikepenz/aboutlibraries/screenshot/VariantPreviews.kt
- Code Duplication · Edited copy of a member (23 corresponding lines) sample/android/src/debug/kotlin/com/mikepenz/aboutlibraries/screenshot/SampleAppPreviews.kt
- Code Duplication · Edited copies of one member (6 members, 10+ corresponding lines) sample/android/src/debug/kotlin/com/mikepenz/aboutlibraries/screenshot/VariantPreviews.kt
- Code Duplication · Edited copy of a member (16 corresponding lines) sample/android/src/debug/kotlin/com/mikepenz/aboutlibraries/screenshot/SampleAppPreviews.kt
- Code Duplication · Edited copy of a member (15 corresponding lines) sample/android/src/debug/kotlin/com/mikepenz/aboutlibraries/screenshot/SampleAppPreviews.kt
- Code Duplication · Edited copy of a member (10 corresponding lines) sample/android/src/debug/kotlin/com/mikepenz/aboutlibraries/screenshot/SampleAppPreviews.kt
- Code Duplication · Edited copy of a member (7 corresponding lines) sample/android/src/debug/kotlin/com/mikepenz/aboutlibraries/screenshot/VariantPreviews.kt
- Code Duplication · Edited copy of a member (14 corresponding lines) sample/android/src/debug/kotlin/com/mikepenz/aboutlibraries/screenshot/VariantPreviews.kt
- Code Duplication · Edited copies of one member (3 members, 7+ corresponding lines) sample/android/src/debug/kotlin/com/mikepenz/aboutlibraries/screenshot/VariantPreviews.kt
- Code Duplication · Edited copy of a member (12 corresponding lines) sample/android/src/debug/kotlin/com/mikepenz/aboutlibraries/screenshot/SampleAppPreviews.kt
- Code Duplication · Edited copy of a member (12 corresponding lines) sample/android/src/debug/kotlin/com/mikepenz/aboutlibraries/screenshot/SampleAppPreviews.kt
- Code Duplication · Duplicated block (18 lines × 2) sample/shared/src/commonMain/kotlin/com/mikepenz/aboutlibraries/sample/App.kt
- Code Duplication · Duplicated block (12 lines × 2) sample/shared/src/commonMain/kotlin/com/mikepenz/aboutlibraries/sample/App.kt
- Code Duplication · Duplicated block (9 lines × 2) sample/android/src/debug/kotlin/com/mikepenz/aboutlibraries/screenshot/VariantPreviews.kt
- Code Duplication · Duplicated block (8 lines × 2) sample/shared/src/commonMain/kotlin/com/mikepenz/aboutlibraries/sample/App.kt
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Visual & motion safety · Low contrast colour pair in CSS (3.2:1) DEV/definition-file-builder/css/component.css
Fixed since the last survey: 27 findings
- Code Duplication · Duplicated block (22–24 lines × 2) aboutlibraries-compose-m2/src/commonMain/kotlin/com/mikepenz/aboutlibraries/ui/compose/SharedLibraries.kt
- Code Duplication · Duplicated block (23 lines × 2) aboutlibraries-compose-m2/src/commonMain/kotlin/com/mikepenz/aboutlibraries/ui/compose/SharedLibraries.kt
- Code Duplication · Duplicated block (20 lines × 3) aboutlibraries-compose/src/commonMain/kotlin/com/mikepenz/aboutlibraries/ui/compose/variant/refined/RefinedHeader.kt
- Code Duplication · Duplicated block (20 lines × 2) aboutlibraries-compose-m2/src/commonMain/kotlin/com/mikepenz/aboutlibraries/ui/compose/SharedLibraries.kt
- Code Duplication · Duplicated block (19 lines × 2) aboutlibraries-compose-m2/src/commonMain/kotlin/com/mikepenz/aboutlibraries/ui/compose/style/M2VariantTokens.kt
- Code Duplication · Duplicated block (16 lines × 2) aboutlibraries-compose/src/commonMain/kotlin/com/mikepenz/aboutlibraries/ui/compose/variant/refined/RefinedRow.kt
- Code Duplication · Duplicated block (15 lines × 2) aboutlibraries-compose-m2/src/commonMain/kotlin/com/mikepenz/aboutlibraries/ui/compose/style/M2VariantTokens.kt
- Code Duplication · Duplicated block (14 lines × 2) aboutlibraries-compose-m2/src/commonMain/kotlin/com/mikepenz/aboutlibraries/ui/compose/component/LibrariesChip.kt
- Code Duplication · Duplicated block (14 lines × 2) plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/AboutLibrariesExportComplianceTask.kt
- Code Duplication · Duplicated block (14 lines × 2) plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/AboutLibrariesExportComplianceTask.kt
- Code Duplication · Duplicated block (10 lines × 3) plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/AboutLibrariesPluginAndroidExtension.kt
- Code Duplication · Duplicated block (9 lines × 2) aboutlibraries-core/src/androidMain/kotlin/com/mikepenz/aboutlibraries/util/AndroidParser.kt
- Code Duplication · Duplicated block (9 lines × 2) app/src/main/kotlin/com/mikepenz/aboutlibraries/sample/ComposeActivity.kt
- Code Duplication · Duplicated block (6 lines × 2) aboutlibraries-compose/src/commonMain/kotlin/com/mikepenz/aboutlibraries/ui/compose/variant/refined/RefinedHeader.kt
- Code Duplication · Duplicated block (12 lines × 3) aboutlibraries-compose-m2/src/androidMain/kotlin/com/mikepenz/aboutlibraries/ui/compose/SharedLibraries.android.kt
- Code Duplication · Duplicated block (10 lines × 2) aboutlibraries-compose-m2/src/commonMain/kotlin/com/mikepenz/aboutlibraries/ui/compose/SharedLibraries.kt
- Code Duplication · Duplicated block (10 lines × 3) aboutlibraries-compose-m2/src/commonMain/kotlin/com/mikepenz/aboutlibraries/ui/compose/SharedLibraries.kt
- Code Duplication · Duplicated block (6 lines × 2) aboutlibraries-compose/src/commonMain/kotlin/com/mikepenz/aboutlibraries/ui/compose/variant/refined/RefinedRow.kt
- Code Duplication · Duplicated block (18 lines × 2) sample/shared/src/commonMain/kotlin/com/mikepenz/aboutlibraries/sample/App.kt
- Code Duplication · Duplicated block (12 lines × 2) sample/shared/src/commonMain/kotlin/com/mikepenz/aboutlibraries/sample/App.kt
- Code Duplication · Duplicated block (9 lines × 2) sample/android/src/debug/kotlin/com/mikepenz/aboutlibraries/screenshot/VariantPreviews.kt
- Code Duplication · Duplicated block (8 lines × 2) sample/shared/src/commonMain/kotlin/com/mikepenz/aboutlibraries/sample/App.kt
- Churn × Complexity Hotspots · Hotspot: plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/util/LibraryPostProcessor.kt plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/util/LibraryPostProcessor.kt
- Churn × Complexity Hotspots · Hotspot: plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/BaseAboutLibrariesTask.kt plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/BaseAboutLibrariesTask.kt
- Churn × Complexity Hotspots · Hotspot: sample/shared/src/commonMain/kotlin/com/mikepenz/aboutlibraries/sample/m3/Theme.kt sample/shared/src/commonMain/kotlin/com/mikepenz/aboutlibraries/sample/m3/Theme.kt
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- A11y enforcement · Accessibility enforcement below the top rung
Rebuild cost: about €17,000 · Estimate
| Cost to rebuild | €5,700 to €29,000, for 96 to 304 hours of work, about 0.1 person-years for one engineer |
|---|---|
| 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 52. 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 | Small: 13,752 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 entity | 2 plugin.mapping | 3 com.mikepenz.aboutlibraries | 4 plugin.api | 5 plugin.api.GitHubApi | 6 plugin.mapping.SpdxLicense | 7 plugin.model | 8 plugin.util.parser | 9 ui.compose.variant | 10 Libs | 11 plugin.api.Api | 12 plugin.util | 13 ui.compose.android.Extensions | 14 ui.compose.style | 15 ui.compose.variant.LibrariesDensity | 16 ui.compose.variant.LibrariesVariant | 17 ui.compose.variant.LibraryActionKind | 18 ui.compose.variant.LibraryActionMode | 19 ui.compose.variant.LibraryDetailMode | 20 ui.compose.wear.preview | 21 plugin | 22 plugin.util.DependencyCollector | 23 ui.compose | 24 ui.compose.m3.sheet | 25 ui.compose.m3.style | 26 ui.compose.style.ContrastLevel | 27 ui.compose.style.LicenseHueResolver | 28 ui.compose.variant.refined | 29 ui.compose.variant.traditional | 30 util | 31 plugin.DuplicateMode | 32 plugin.DuplicateRule | 33 plugin.StrictMode | 34 ui.compose.SharedLibraries | 35 ui.compose.component | 36 ui.compose.m3 | 37 ui.compose.m3.SharedLibraries | 38 ui.compose.m3.component | 39 ui.compose.wear | 40 ui.compose.wear.component |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 entity | ||||||||||||||||||||||||||||||||||||||||
| 2 plugin.mapping | ||||||||||||||||||||||||||||||||||||||||
| 3 com.mikepenz.aboutlibraries | 2 | |||||||||||||||||||||||||||||||||||||||
| 4 plugin.api | 9 | |||||||||||||||||||||||||||||||||||||||
| 5 plugin.api.GitHubApi | 1 | |||||||||||||||||||||||||||||||||||||||
| 6 plugin.mapping.SpdxLicense | 380 | |||||||||||||||||||||||||||||||||||||||
| 7 plugin.model | 2 | |||||||||||||||||||||||||||||||||||||||
| 8 plugin.util.parser | 3 | |||||||||||||||||||||||||||||||||||||||
| 9 ui.compose.variant | 5 | 7 | ||||||||||||||||||||||||||||||||||||||
| 10 Libs | 1 | |||||||||||||||||||||||||||||||||||||||
| 11 plugin.api.Api | 2 | |||||||||||||||||||||||||||||||||||||||
| 12 plugin.util | 10 | 1 | 1 | 4 | ||||||||||||||||||||||||||||||||||||
| 13 ui.compose.android.Extensions | 1 | |||||||||||||||||||||||||||||||||||||||
| 14 ui.compose.style | 1 | |||||||||||||||||||||||||||||||||||||||
| 15 ui.compose.variant.LibrariesDensity | 2 | |||||||||||||||||||||||||||||||||||||||
| 16 ui.compose.variant.LibrariesVariant | 2 | |||||||||||||||||||||||||||||||||||||||
| 17 ui.compose.variant.LibraryActionKind | 4 | |||||||||||||||||||||||||||||||||||||||
| 18 ui.compose.variant.LibraryActionMode | 3 | |||||||||||||||||||||||||||||||||||||||
| 19 ui.compose.variant.LibraryDetailMode | 4 | |||||||||||||||||||||||||||||||||||||||
| 20 ui.compose.wear.preview | 1 | |||||||||||||||||||||||||||||||||||||||
| 21 plugin | 2 | |||||||||||||||||||||||||||||||||||||||
| 22 plugin.util.DependencyCollector | 1 | |||||||||||||||||||||||||||||||||||||||
| 23 ui.compose | 1 | 2 | 6 | 4 | ||||||||||||||||||||||||||||||||||||
| 24 ui.compose.m3.sheet | 1 | 2 | 2 | |||||||||||||||||||||||||||||||||||||
| 25 ui.compose.m3.style | 5 | |||||||||||||||||||||||||||||||||||||||
| 26 ui.compose.style.ContrastLevel | 2 | |||||||||||||||||||||||||||||||||||||||
| 27 ui.compose.style.LicenseHueResolver | 1 | |||||||||||||||||||||||||||||||||||||||
| 28 ui.compose.variant.refined | 1 | 2 | 4 | |||||||||||||||||||||||||||||||||||||
| 29 ui.compose.variant.traditional | 1 | 2 | 6 | |||||||||||||||||||||||||||||||||||||
| 30 util | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 31 plugin.DuplicateMode | 3 | |||||||||||||||||||||||||||||||||||||||
| 32 plugin.DuplicateRule | 3 | |||||||||||||||||||||||||||||||||||||||
| 33 plugin.StrictMode | 3 | |||||||||||||||||||||||||||||||||||||||
| 34 ui.compose.SharedLibraries | 5 | 5 | ||||||||||||||||||||||||||||||||||||||
| 35 ui.compose.component | 2 | 5 | ||||||||||||||||||||||||||||||||||||||
| 36 ui.compose.m3 | 1 | 1 | 6 | 4 | 2 | |||||||||||||||||||||||||||||||||||
| 37 ui.compose.m3.SharedLibraries | 5 | 5 | ||||||||||||||||||||||||||||||||||||||
| 38 ui.compose.m3.component | 2 | 5 | ||||||||||||||||||||||||||||||||||||||
| 39 ui.compose.wear | 2 | 1 | 6 | |||||||||||||||||||||||||||||||||||||
| 40 ui.compose.wear.component | 3 | 7 |
3→1 com.mikepenz.aboutlibraries uses entity✕
- Connections
- 2 pairs of types, where a type in com.mikepenz.aboutlibraries uses a type in entity.
- The types involved
com.mikepenz.aboutlibraries.Libs→com.mikepenz.aboutlibraries.entity.Librarycom.mikepenz.aboutlibraries.Libs→com.mikepenz.aboutlibraries.entity.License
- Direction
- com.mikepenz.aboutlibraries uses entity, so a change to entity can break com.mikepenz.aboutlibraries, while a change to com.mikepenz.aboutlibraries can't break entity.
- Position
- Below the diagonal: com.mikepenz.aboutlibraries uses a module listed above it, which is the healthy direction.
4→2 plugin.api uses plugin.mapping✕
- Connections
- 9 pairs of types, where a type in plugin.api uses a type in plugin.mapping.
- The types involved
com.mikepenz.aboutlibraries.plugin.api.Api→com.mikepenz.aboutlibraries.plugin.mapping.Fundingcom.mikepenz.aboutlibraries.plugin.api.Api→com.mikepenz.aboutlibraries.plugin.mapping.Licensecom.mikepenz.aboutlibraries.plugin.api.Api→com.mikepenz.aboutlibraries.plugin.mapping.Scmcom.mikepenz.aboutlibraries.plugin.api.GitHubApi→com.mikepenz.aboutlibraries.plugin.mapping.Fundingcom.mikepenz.aboutlibraries.plugin.api.GitHubApi→com.mikepenz.aboutlibraries.plugin.mapping.Licensecom.mikepenz.aboutlibraries.plugin.api.GitHubApi→com.mikepenz.aboutlibraries.plugin.mapping.Scmcom.mikepenz.aboutlibraries.plugin.api.IApi→com.mikepenz.aboutlibraries.plugin.mapping.Fundingcom.mikepenz.aboutlibraries.plugin.api.IApi→com.mikepenz.aboutlibraries.plugin.mapping.Licensecom.mikepenz.aboutlibraries.plugin.api.IApi→com.mikepenz.aboutlibraries.plugin.mapping.Scm
- Direction
- plugin.api uses plugin.mapping, so a change to plugin.mapping can break plugin.api, while a change to plugin.api can't break plugin.mapping.
- Position
- Below the diagonal: plugin.api uses a module listed above it, which is the healthy direction.
5→2 plugin.api.GitHubApi uses plugin.mapping✕
- Connections
- 1 pair of types, where a type in plugin.api.GitHubApi uses a type in plugin.mapping.
- The types involved
com.mikepenz.aboutlibraries.plugin.api.GitHubApi.Companion→com.mikepenz.aboutlibraries.plugin.mapping.Funding
- Direction
- plugin.api.GitHubApi uses plugin.mapping, so a change to plugin.mapping can break plugin.api.GitHubApi, while a change to plugin.api.GitHubApi can't break plugin.mapping.
- Position
- Below the diagonal: plugin.api.GitHubApi uses a module listed above it, which is the healthy direction.
6→2 plugin.mapping.SpdxLicense uses plugin.mapping✕
- Connections
- 380 pairs of types, where a type in plugin.mapping.SpdxLicense uses a type in plugin.mapping. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.mikepenz.aboutlibraries.plugin.mapping.SpdxLicense.AAL→com.mikepenz.aboutlibraries.plugin.mapping.SpdxLicensecom.mikepenz.aboutlibraries.plugin.mapping.SpdxLicense.ADSL→com.mikepenz.aboutlibraries.plugin.mapping.SpdxLicensecom.mikepenz.aboutlibraries.plugin.mapping.SpdxLicense.AFL_1_1→com.mikepenz.aboutlibraries.plugin.mapping.SpdxLicensecom.mikepenz.aboutlibraries.plugin.mapping.SpdxLicense.AFL_1_2→com.mikepenz.aboutlibraries.plugin.mapping.SpdxLicensecom.mikepenz.aboutlibraries.plugin.mapping.SpdxLicense.AFL_2_0→com.mikepenz.aboutlibraries.plugin.mapping.SpdxLicensecom.mikepenz.aboutlibraries.plugin.mapping.SpdxLicense.AFL_2_1→com.mikepenz.aboutlibraries.plugin.mapping.SpdxLicensecom.mikepenz.aboutlibraries.plugin.mapping.SpdxLicense.AFL_3_0→com.mikepenz.aboutlibraries.plugin.mapping.SpdxLicensecom.mikepenz.aboutlibraries.plugin.mapping.SpdxLicense.AGPL_1_0_only→com.mikepenz.aboutlibraries.plugin.mapping.SpdxLicensecom.mikepenz.aboutlibraries.plugin.mapping.SpdxLicense.AGPL_1_0_or_later→com.mikepenz.aboutlibraries.plugin.mapping.SpdxLicensecom.mikepenz.aboutlibraries.plugin.mapping.SpdxLicense.AGPL_3_0_only→com.mikepenz.aboutlibraries.plugin.mapping.SpdxLicensecom.mikepenz.aboutlibraries.plugin.mapping.SpdxLicense.AGPL_3_0_or_later→com.mikepenz.aboutlibraries.plugin.mapping.SpdxLicensecom.mikepenz.aboutlibraries.plugin.mapping.SpdxLicense.AMDPLPA→com.mikepenz.aboutlibraries.plugin.mapping.SpdxLicensecom.mikepenz.aboutlibraries.plugin.mapping.SpdxLicense.AML→com.mikepenz.aboutlibraries.plugin.mapping.SpdxLicensecom.mikepenz.aboutlibraries.plugin.mapping.SpdxLicense.AMPAS→com.mikepenz.aboutlibraries.plugin.mapping.SpdxLicensecom.mikepenz.aboutlibraries.plugin.mapping.SpdxLicense.ANTLR_PD→com.mikepenz.aboutlibraries.plugin.mapping.SpdxLicensecom.mikepenz.aboutlibraries.plugin.mapping.SpdxLicense.APAFML→com.mikepenz.aboutlibraries.plugin.mapping.SpdxLicensecom.mikepenz.aboutlibraries.plugin.mapping.SpdxLicense.APL_1_0→com.mikepenz.aboutlibraries.plugin.mapping.SpdxLicensecom.mikepenz.aboutlibraries.plugin.mapping.SpdxLicense.APSL_1_0→com.mikepenz.aboutlibraries.plugin.mapping.SpdxLicensecom.mikepenz.aboutlibraries.plugin.mapping.SpdxLicense.APSL_1_1→com.mikepenz.aboutlibraries.plugin.mapping.SpdxLicensecom.mikepenz.aboutlibraries.plugin.mapping.SpdxLicense.APSL_1_2→com.mikepenz.aboutlibraries.plugin.mapping.SpdxLicensecom.mikepenz.aboutlibraries.plugin.mapping.SpdxLicense.APSL_2_0→com.mikepenz.aboutlibraries.plugin.mapping.SpdxLicensecom.mikepenz.aboutlibraries.plugin.mapping.SpdxLicense.ASDKL→com.mikepenz.aboutlibraries.plugin.mapping.SpdxLicensecom.mikepenz.aboutlibraries.plugin.mapping.SpdxLicense.Abstyles→com.mikepenz.aboutlibraries.plugin.mapping.SpdxLicensecom.mikepenz.aboutlibraries.plugin.mapping.SpdxLicense.Adobe_2006→com.mikepenz.aboutlibraries.plugin.mapping.SpdxLicensecom.mikepenz.aboutlibraries.plugin.mapping.SpdxLicense.Adobe_Glyph→com.mikepenz.aboutlibraries.plugin.mapping.SpdxLicense
- Direction
- plugin.mapping.SpdxLicense uses plugin.mapping, so a change to plugin.mapping can break plugin.mapping.SpdxLicense, while a change to plugin.mapping.SpdxLicense can't break plugin.mapping.
- Position
- Below the diagonal: plugin.mapping.SpdxLicense uses a module listed above it, which is the healthy direction.
7→2 plugin.model uses plugin.mapping✕
- Connections
- 2 pairs of types, where a type in plugin.model uses a type in plugin.mapping.
- The types involved
com.mikepenz.aboutlibraries.plugin.model.ResultContainer→com.mikepenz.aboutlibraries.plugin.mapping.Librarycom.mikepenz.aboutlibraries.plugin.model.ResultContainer→com.mikepenz.aboutlibraries.plugin.mapping.License
- Direction
- plugin.model uses plugin.mapping, so a change to plugin.mapping can break plugin.model, while a change to plugin.model can't break plugin.mapping.
- Position
- Below the diagonal: plugin.model uses a module listed above it, which is the healthy direction.
8→2 plugin.util.parser uses plugin.mapping✕
- Connections
- 3 pairs of types, where a type in plugin.util.parser uses a type in plugin.mapping.
- The types involved
com.mikepenz.aboutlibraries.plugin.util.parser.FundingReader→com.mikepenz.aboutlibraries.plugin.mapping.Fundingcom.mikepenz.aboutlibraries.plugin.util.parser.LibraryReader→com.mikepenz.aboutlibraries.plugin.mapping.Librarycom.mikepenz.aboutlibraries.plugin.util.parser.LicenseReader→com.mikepenz.aboutlibraries.plugin.mapping.License
- Direction
- plugin.util.parser uses plugin.mapping, so a change to plugin.mapping can break plugin.util.parser, while a change to plugin.util.parser can't break plugin.mapping.
- Position
- Below the diagonal: plugin.util.parser uses a module listed above it, which is the healthy direction.
9→1 ui.compose.variant uses entity✕
- Connections
- 5 pairs of types, where a type in ui.compose.variant uses a type in entity.
- The types involved
com.mikepenz.aboutlibraries.ui.compose.variant.LibrariesKt→com.mikepenz.aboutlibraries.entity.Librarycom.mikepenz.aboutlibraries.ui.compose.variant.LibraryActionsKt→com.mikepenz.aboutlibraries.entity.Librarycom.mikepenz.aboutlibraries.ui.compose.variant.LibraryDetailBodyKt→com.mikepenz.aboutlibraries.entity.Librarycom.mikepenz.aboutlibraries.ui.compose.variant.LibraryListScaffoldKt→com.mikepenz.aboutlibraries.entity.Librarycom.mikepenz.aboutlibraries.ui.compose.variant.LibraryRowKt→com.mikepenz.aboutlibraries.entity.Library
- Direction
- ui.compose.variant uses entity, so a change to entity can break ui.compose.variant, while a change to ui.compose.variant can't break entity.
- Position
- Below the diagonal: ui.compose.variant uses a module listed above it, which is the healthy direction.
9→14 ui.compose.variant uses ui.compose.style part of a loop✕
- Connections
- 7 pairs of types, where a type in ui.compose.variant uses a type in ui.compose.style.
- The types involved
com.mikepenz.aboutlibraries.ui.compose.variant.LibrariesKt→com.mikepenz.aboutlibraries.ui.compose.style.LibrariesStylecom.mikepenz.aboutlibraries.ui.compose.variant.LibrariesKt→com.mikepenz.aboutlibraries.ui.compose.style.LibraryActionBadgescom.mikepenz.aboutlibraries.ui.compose.variant.LibraryActionsKt→com.mikepenz.aboutlibraries.ui.compose.style.LibrariesStylecom.mikepenz.aboutlibraries.ui.compose.variant.LibraryActionsKt→com.mikepenz.aboutlibraries.ui.compose.style.LibraryActionBadgescom.mikepenz.aboutlibraries.ui.compose.variant.LibraryDetailBodyKt→com.mikepenz.aboutlibraries.ui.compose.style.LibrariesStylecom.mikepenz.aboutlibraries.ui.compose.variant.LibraryDetailBodyKt→com.mikepenz.aboutlibraries.ui.compose.style.LibraryActionBadgescom.mikepenz.aboutlibraries.ui.compose.variant.LibraryRowKt→com.mikepenz.aboutlibraries.ui.compose.style.LibrariesStyle
- Direction
- ui.compose.variant uses ui.compose.style, so a change to ui.compose.style can break ui.compose.variant, while a change to ui.compose.variant can't break ui.compose.style.
- 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.
10→3 Libs uses com.mikepenz.aboutlibraries✕
- Connections
- 1 pair of types, where a type in Libs uses a type in com.mikepenz.aboutlibraries.
- The types involved
com.mikepenz.aboutlibraries.Libs.Builder→com.mikepenz.aboutlibraries.Libs
- Direction
- Libs uses com.mikepenz.aboutlibraries, so a change to com.mikepenz.aboutlibraries can break Libs, while a change to Libs can't break com.mikepenz.aboutlibraries.
- Position
- Below the diagonal: Libs uses a module listed above it, which is the healthy direction.
11→4 plugin.api.Api uses plugin.api✕
- Connections
- 2 pairs of types, where a type in plugin.api.Api uses a type in plugin.api.
- The types involved
com.mikepenz.aboutlibraries.plugin.api.Api.Companion→com.mikepenz.aboutlibraries.plugin.api.IApicom.mikepenz.aboutlibraries.plugin.api.Api.NoOpApi→com.mikepenz.aboutlibraries.plugin.api.IApi
- Direction
- plugin.api.Api uses plugin.api, so a change to plugin.api can break plugin.api.Api, while a change to plugin.api.Api can't break plugin.api.
- Position
- Below the diagonal: plugin.api.Api uses a module listed above it, which is the healthy direction.
12→2 plugin.util uses plugin.mapping✕
- Connections
- 10 pairs of types, where a type in plugin.util uses a type in plugin.mapping.
- The types involved
com.mikepenz.aboutlibraries.plugin.util.DependencyData→com.mikepenz.aboutlibraries.plugin.mapping.Developercom.mikepenz.aboutlibraries.plugin.util.DependencyData→com.mikepenz.aboutlibraries.plugin.mapping.Fundingcom.mikepenz.aboutlibraries.plugin.util.DependencyData→com.mikepenz.aboutlibraries.plugin.mapping.Licensecom.mikepenz.aboutlibraries.plugin.util.DependencyData→com.mikepenz.aboutlibraries.plugin.mapping.Organizationcom.mikepenz.aboutlibraries.plugin.util.DependencyData→com.mikepenz.aboutlibraries.plugin.mapping.Scmcom.mikepenz.aboutlibraries.plugin.util.ExtensionsKt→com.mikepenz.aboutlibraries.plugin.mapping.Librarycom.mikepenz.aboutlibraries.plugin.util.ExtensionsKt→com.mikepenz.aboutlibraries.plugin.mapping.Licensecom.mikepenz.aboutlibraries.plugin.util.LibraryUtilKt→com.mikepenz.aboutlibraries.plugin.mapping.Librarycom.mikepenz.aboutlibraries.plugin.util.LicenseUtil→com.mikepenz.aboutlibraries.plugin.mapping.Licensecom.mikepenz.aboutlibraries.plugin.util.LicenseUtilKt→com.mikepenz.aboutlibraries.plugin.mapping.License
- Direction
- plugin.util uses plugin.mapping, so a change to plugin.mapping can break plugin.util, while a change to plugin.util can't break plugin.mapping.
- Position
- Below the diagonal: plugin.util uses a module listed above it, which is the healthy direction.
12→4 plugin.util uses plugin.api✕
- Connections
- 1 pair of types, where a type in plugin.util uses a type in plugin.api.
- The types involved
com.mikepenz.aboutlibraries.plugin.util.LibraryPostProcessor→com.mikepenz.aboutlibraries.plugin.api.IApi
- Direction
- plugin.util uses plugin.api, so a change to plugin.api can break plugin.util, while a change to plugin.util can't break plugin.api.
- Position
- Below the diagonal: plugin.util uses a module listed above it, which is the healthy direction.
12→7 plugin.util uses plugin.model✕
- Connections
- 1 pair of types, where a type in plugin.util uses a type in plugin.model.
- The types involved
com.mikepenz.aboutlibraries.plugin.util.LibraryPostProcessor→com.mikepenz.aboutlibraries.plugin.model.ResultContainer
- Direction
- plugin.util uses plugin.model, so a change to plugin.model can break plugin.util, while a change to plugin.util can't break plugin.model.
- Position
- Below the diagonal: plugin.util uses a module listed above it, which is the healthy direction.
12→21 plugin.util uses plugin part of a loop✕
- Connections
- 4 pairs of types, where a type in plugin.util uses a type in plugin.
- The types involved
com.mikepenz.aboutlibraries.plugin.util.LibraryPostProcessor→com.mikepenz.aboutlibraries.plugin.DuplicateModecom.mikepenz.aboutlibraries.plugin.util.LibraryPostProcessor→com.mikepenz.aboutlibraries.plugin.DuplicateRulecom.mikepenz.aboutlibraries.plugin.util.LibraryUtilKt→com.mikepenz.aboutlibraries.plugin.DuplicateModecom.mikepenz.aboutlibraries.plugin.util.LibraryUtilKt→com.mikepenz.aboutlibraries.plugin.DuplicateRule
- Direction
- plugin.util uses plugin, so a change to plugin can break plugin.util, while a change to plugin.util can't break plugin.
- 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→3 ui.compose.android.Extensions uses com.mikepenz.aboutlibraries✕
- Connections
- 1 pair of types, where a type in ui.compose.android.Extensions uses a type in com.mikepenz.aboutlibraries.
- The types involved
com.mikepenz.aboutlibraries.ui.compose.android.Extensions.androidKt→com.mikepenz.aboutlibraries.Libs
- Direction
- ui.compose.android.Extensions uses com.mikepenz.aboutlibraries, so a change to com.mikepenz.aboutlibraries can break ui.compose.android.Extensions, while a change to ui.compose.android.Extensions can't break com.mikepenz.aboutlibraries.
- Position
- Below the diagonal: ui.compose.android.Extensions uses a module listed above it, which is the healthy direction.
14→9 ui.compose.style uses ui.compose.variant✕
- Connections
- 1 pair of types, where a type in ui.compose.style uses a type in ui.compose.variant.
- The types involved
com.mikepenz.aboutlibraries.ui.compose.style.VariantPadding→com.mikepenz.aboutlibraries.ui.compose.variant.LibrariesDensity
- Direction
- ui.compose.style uses ui.compose.variant, so a change to ui.compose.variant can break ui.compose.style, while a change to ui.compose.style can't break ui.compose.variant.
- Position
- Below the diagonal: ui.compose.style uses a module listed above it, which is the healthy direction.
15→9 ui.compose.variant.LibrariesDensity uses ui.compose.variant✕
- Connections
- 2 pairs of types, where a type in ui.compose.variant.LibrariesDensity uses a type in ui.compose.variant.
- The types involved
com.mikepenz.aboutlibraries.ui.compose.variant.LibrariesDensity.Compact→com.mikepenz.aboutlibraries.ui.compose.variant.LibrariesDensitycom.mikepenz.aboutlibraries.ui.compose.variant.LibrariesDensity.Cozy→com.mikepenz.aboutlibraries.ui.compose.variant.LibrariesDensity
- Direction
- ui.compose.variant.LibrariesDensity uses ui.compose.variant, so a change to ui.compose.variant can break ui.compose.variant.LibrariesDensity, while a change to ui.compose.variant.LibrariesDensity can't break ui.compose.variant.
- Position
- Below the diagonal: ui.compose.variant.LibrariesDensity uses a module listed above it, which is the healthy direction.
16→9 ui.compose.variant.LibrariesVariant uses ui.compose.variant✕
- Connections
- 2 pairs of types, where a type in ui.compose.variant.LibrariesVariant uses a type in ui.compose.variant.
- The types involved
com.mikepenz.aboutlibraries.ui.compose.variant.LibrariesVariant.Refined→com.mikepenz.aboutlibraries.ui.compose.variant.LibrariesVariantcom.mikepenz.aboutlibraries.ui.compose.variant.LibrariesVariant.Traditional→com.mikepenz.aboutlibraries.ui.compose.variant.LibrariesVariant
- Direction
- ui.compose.variant.LibrariesVariant uses ui.compose.variant, so a change to ui.compose.variant can break ui.compose.variant.LibrariesVariant, while a change to ui.compose.variant.LibrariesVariant can't break ui.compose.variant.
- Position
- Below the diagonal: ui.compose.variant.LibrariesVariant uses a module listed above it, which is the healthy direction.
17→9 ui.compose.variant.LibraryActionKind uses ui.compose.variant✕
- Connections
- 4 pairs of types, where a type in ui.compose.variant.LibraryActionKind uses a type in ui.compose.variant.
- The types involved
com.mikepenz.aboutlibraries.ui.compose.variant.LibraryActionKind.License→com.mikepenz.aboutlibraries.ui.compose.variant.LibraryActionKindcom.mikepenz.aboutlibraries.ui.compose.variant.LibraryActionKind.Source→com.mikepenz.aboutlibraries.ui.compose.variant.LibraryActionKindcom.mikepenz.aboutlibraries.ui.compose.variant.LibraryActionKind.Sponsor→com.mikepenz.aboutlibraries.ui.compose.variant.LibraryActionKindcom.mikepenz.aboutlibraries.ui.compose.variant.LibraryActionKind.Website→com.mikepenz.aboutlibraries.ui.compose.variant.LibraryActionKind
- Direction
- ui.compose.variant.LibraryActionKind uses ui.compose.variant, so a change to ui.compose.variant can break ui.compose.variant.LibraryActionKind, while a change to ui.compose.variant.LibraryActionKind can't break ui.compose.variant.
- Position
- Below the diagonal: ui.compose.variant.LibraryActionKind uses a module listed above it, which is the healthy direction.
18→9 ui.compose.variant.LibraryActionMode uses ui.compose.variant✕
- Connections
- 3 pairs of types, where a type in ui.compose.variant.LibraryActionMode uses a type in ui.compose.variant.
- The types involved
com.mikepenz.aboutlibraries.ui.compose.variant.LibraryActionMode.Chips→com.mikepenz.aboutlibraries.ui.compose.variant.LibraryActionModecom.mikepenz.aboutlibraries.ui.compose.variant.LibraryActionMode.Icons→com.mikepenz.aboutlibraries.ui.compose.variant.LibraryActionModecom.mikepenz.aboutlibraries.ui.compose.variant.LibraryActionMode.Links→com.mikepenz.aboutlibraries.ui.compose.variant.LibraryActionMode
- Direction
- ui.compose.variant.LibraryActionMode uses ui.compose.variant, so a change to ui.compose.variant can break ui.compose.variant.LibraryActionMode, while a change to ui.compose.variant.LibraryActionMode can't break ui.compose.variant.
- Position
- Below the diagonal: ui.compose.variant.LibraryActionMode uses a module listed above it, which is the healthy direction.
19→9 ui.compose.variant.LibraryDetailMode uses ui.compose.variant✕
- Connections
- 4 pairs of types, where a type in ui.compose.variant.LibraryDetailMode uses a type in ui.compose.variant.
- The types involved
com.mikepenz.aboutlibraries.ui.compose.variant.LibraryDetailMode.Dialog→com.mikepenz.aboutlibraries.ui.compose.variant.LibraryDetailModecom.mikepenz.aboutlibraries.ui.compose.variant.LibraryDetailMode.Inline→com.mikepenz.aboutlibraries.ui.compose.variant.LibraryDetailModecom.mikepenz.aboutlibraries.ui.compose.variant.LibraryDetailMode.None→com.mikepenz.aboutlibraries.ui.compose.variant.LibraryDetailModecom.mikepenz.aboutlibraries.ui.compose.variant.LibraryDetailMode.Sheet→com.mikepenz.aboutlibraries.ui.compose.variant.LibraryDetailMode
- Direction
- ui.compose.variant.LibraryDetailMode uses ui.compose.variant, so a change to ui.compose.variant can break ui.compose.variant.LibraryDetailMode, while a change to ui.compose.variant.LibraryDetailMode can't break ui.compose.variant.
- Position
- Below the diagonal: ui.compose.variant.LibraryDetailMode uses a module listed above it, which is the healthy direction.
20→3 ui.compose.wear.preview uses com.mikepenz.aboutlibraries✕
- Connections
- 1 pair of types, where a type in ui.compose.wear.preview uses a type in com.mikepenz.aboutlibraries.
- The types involved
com.mikepenz.aboutlibraries.ui.compose.wear.preview.FakeDataKt→com.mikepenz.aboutlibraries.Libs
- Direction
- ui.compose.wear.preview uses com.mikepenz.aboutlibraries, so a change to com.mikepenz.aboutlibraries can break ui.compose.wear.preview, while a change to ui.compose.wear.preview can't break com.mikepenz.aboutlibraries.
- Position
- Below the diagonal: ui.compose.wear.preview uses a module listed above it, which is the healthy direction.
21→12 plugin uses plugin.util✕
- Connections
- 2 pairs of types, where a type in plugin uses a type in plugin.util.
- The types involved
com.mikepenz.aboutlibraries.plugin.BaseAboutLibrariesTask→com.mikepenz.aboutlibraries.plugin.util.DependencyCoordinatescom.mikepenz.aboutlibraries.plugin.BaseAboutLibrariesTask→com.mikepenz.aboutlibraries.plugin.util.LibraryPostProcessor
- Direction
- plugin uses plugin.util, so a change to plugin.util can break plugin, while a change to plugin can't break plugin.util.
- Position
- Below the diagonal: plugin uses a module listed above it, which is the healthy direction.
22→12 plugin.util.DependencyCollector uses plugin.util✕
- Connections
- 1 pair of types, where a type in plugin.util.DependencyCollector uses a type in plugin.util.
- The types involved
com.mikepenz.aboutlibraries.plugin.util.DependencyCollector.Companion→com.mikepenz.aboutlibraries.plugin.util.DependencyCoordinates
- Direction
- plugin.util.DependencyCollector uses plugin.util, so a change to plugin.util can break plugin.util.DependencyCollector, while a change to plugin.util.DependencyCollector can't break plugin.util.
- Position
- Below the diagonal: plugin.util.DependencyCollector uses a module listed above it, which is the healthy direction.
23→1 ui.compose uses entity✕
- Connections
- 1 pair of types, where a type in ui.compose uses a type in entity.
- The types involved
com.mikepenz.aboutlibraries.ui.compose.SharedLibrariesKt→com.mikepenz.aboutlibraries.entity.Library
- Direction
- ui.compose uses entity, so a change to entity can break ui.compose, while a change to ui.compose can't break entity.
- Position
- Below the diagonal: ui.compose uses a module listed above it, which is the healthy direction.
23→3 ui.compose uses com.mikepenz.aboutlibraries✕
- Connections
- 2 pairs of types, where a type in ui.compose uses a type in com.mikepenz.aboutlibraries.
- The types involved
com.mikepenz.aboutlibraries.ui.compose.ExtensionsKt→com.mikepenz.aboutlibraries.Libscom.mikepenz.aboutlibraries.ui.compose.SharedLibrariesKt→com.mikepenz.aboutlibraries.Libs
- Direction
- ui.compose uses com.mikepenz.aboutlibraries, so a change to com.mikepenz.aboutlibraries can break ui.compose, while a change to ui.compose can't break com.mikepenz.aboutlibraries.
- Position
- Below the diagonal: ui.compose uses a module listed above it, which is the healthy direction.
23→9 ui.compose uses ui.compose.variant✕
- Connections
- 6 pairs of types, where a type in ui.compose uses a type in ui.compose.variant.
- The types involved
com.mikepenz.aboutlibraries.ui.compose.SharedLibrariesKt→com.mikepenz.aboutlibraries.ui.compose.variant.LibrariesDensitycom.mikepenz.aboutlibraries.ui.compose.SharedLibrariesKt→com.mikepenz.aboutlibraries.ui.compose.variant.LibrariesVariantcom.mikepenz.aboutlibraries.ui.compose.SharedLibrariesKt→com.mikepenz.aboutlibraries.ui.compose.variant.LibraryActionKindcom.mikepenz.aboutlibraries.ui.compose.SharedLibrariesKt→com.mikepenz.aboutlibraries.ui.compose.variant.LibraryActionModecom.mikepenz.aboutlibraries.ui.compose.SharedLibrariesKt→com.mikepenz.aboutlibraries.ui.compose.variant.LibraryBadgescom.mikepenz.aboutlibraries.ui.compose.SharedLibrariesKt→com.mikepenz.aboutlibraries.ui.compose.variant.LibraryDetailMode
- Direction
- ui.compose uses ui.compose.variant, so a change to ui.compose.variant can break ui.compose, while a change to ui.compose can't break ui.compose.variant.
- Position
- Below the diagonal: ui.compose uses a module listed above it, which is the healthy direction.
23→14 ui.compose uses ui.compose.style✕
- Connections
- 4 pairs of types, where a type in ui.compose uses a type in ui.compose.style.
- The types involved
com.mikepenz.aboutlibraries.ui.compose.SharedLibrariesKt→com.mikepenz.aboutlibraries.ui.compose.style.LibrariesStylecom.mikepenz.aboutlibraries.ui.compose.SharedLibrariesKt→com.mikepenz.aboutlibraries.ui.compose.style.LibraryActionBadgescom.mikepenz.aboutlibraries.ui.compose.SharedLibrariesKt→com.mikepenz.aboutlibraries.ui.compose.style.VariantColorscom.mikepenz.aboutlibraries.ui.compose.SharedLibrariesKt→com.mikepenz.aboutlibraries.ui.compose.style.VariantTextStyles
- Direction
- ui.compose uses ui.compose.style, so a change to ui.compose.style can break ui.compose, while a change to ui.compose can't break ui.compose.style.
- Position
- Below the diagonal: ui.compose uses a module listed above it, which is the healthy direction.
24→1 ui.compose.m3.sheet uses entity✕
- Connections
- 1 pair of types, where a type in ui.compose.m3.sheet uses a type in entity.
- The types involved
com.mikepenz.aboutlibraries.ui.compose.m3.sheet.LibraryDetailSheetKt→com.mikepenz.aboutlibraries.entity.Library
- Direction
- ui.compose.m3.sheet uses entity, so a change to entity can break ui.compose.m3.sheet, while a change to ui.compose.m3.sheet can't break entity.
- Position
- Below the diagonal: ui.compose.m3.sheet uses a module listed above it, which is the healthy direction.
24→9 ui.compose.m3.sheet uses ui.compose.variant✕
- Connections
- 2 pairs of types, where a type in ui.compose.m3.sheet uses a type in ui.compose.variant.
- The types involved
com.mikepenz.aboutlibraries.ui.compose.m3.sheet.LibraryDetailSheetKt→com.mikepenz.aboutlibraries.ui.compose.variant.LibraryActionKindcom.mikepenz.aboutlibraries.ui.compose.m3.sheet.LibraryDetailSheetKt→com.mikepenz.aboutlibraries.ui.compose.variant.LibraryActionMode
- Direction
- ui.compose.m3.sheet uses ui.compose.variant, so a change to ui.compose.variant can break ui.compose.m3.sheet, while a change to ui.compose.m3.sheet can't break ui.compose.variant.
- Position
- Below the diagonal: ui.compose.m3.sheet uses a module listed above it, which is the healthy direction.
24→14 ui.compose.m3.sheet uses ui.compose.style✕
- Connections
- 2 pairs of types, where a type in ui.compose.m3.sheet uses a type in ui.compose.style.
- The types involved
com.mikepenz.aboutlibraries.ui.compose.m3.sheet.LibraryDetailSheetKt→com.mikepenz.aboutlibraries.ui.compose.style.LibrariesStylecom.mikepenz.aboutlibraries.ui.compose.m3.sheet.LibraryDetailSheetKt→com.mikepenz.aboutlibraries.ui.compose.style.LibraryActionBadges
- Direction
- ui.compose.m3.sheet uses ui.compose.style, so a change to ui.compose.style can break ui.compose.m3.sheet, while a change to ui.compose.m3.sheet can't break ui.compose.style.
- Position
- Below the diagonal: ui.compose.m3.sheet uses a module listed above it, which is the healthy direction.
25→14 ui.compose.m3.style uses ui.compose.style✕
- Connections
- 5 pairs of types, where a type in ui.compose.m3.style uses a type in ui.compose.style.
- The types involved
com.mikepenz.aboutlibraries.ui.compose.m3.style.M3LibrariesStyleKt→com.mikepenz.aboutlibraries.ui.compose.style.LibrariesStylecom.mikepenz.aboutlibraries.ui.compose.m3.style.M3VariantTokensKt→com.mikepenz.aboutlibraries.ui.compose.style.ContrastLevelcom.mikepenz.aboutlibraries.ui.compose.m3.style.M3VariantTokensKt→com.mikepenz.aboutlibraries.ui.compose.style.LicenseHueResolvercom.mikepenz.aboutlibraries.ui.compose.m3.style.M3VariantTokensKt→com.mikepenz.aboutlibraries.ui.compose.style.VariantColorscom.mikepenz.aboutlibraries.ui.compose.m3.style.M3VariantTokensKt→com.mikepenz.aboutlibraries.ui.compose.style.VariantTextStyles
- Direction
- ui.compose.m3.style uses ui.compose.style, so a change to ui.compose.style can break ui.compose.m3.style, while a change to ui.compose.m3.style can't break ui.compose.style.
- Position
- Below the diagonal: ui.compose.m3.style uses a module listed above it, which is the healthy direction.
26→14 ui.compose.style.ContrastLevel uses ui.compose.style✕
- Connections
- 2 pairs of types, where a type in ui.compose.style.ContrastLevel uses a type in ui.compose.style.
- The types involved
com.mikepenz.aboutlibraries.ui.compose.style.ContrastLevel.High→com.mikepenz.aboutlibraries.ui.compose.style.ContrastLevelcom.mikepenz.aboutlibraries.ui.compose.style.ContrastLevel.Normal→com.mikepenz.aboutlibraries.ui.compose.style.ContrastLevel
- Direction
- ui.compose.style.ContrastLevel uses ui.compose.style, so a change to ui.compose.style can break ui.compose.style.ContrastLevel, while a change to ui.compose.style.ContrastLevel can't break ui.compose.style.
- Position
- Below the diagonal: ui.compose.style.ContrastLevel uses a module listed above it, which is the healthy direction.
27→14 ui.compose.style.LicenseHueResolver uses ui.compose.style✕
- Connections
- 1 pair of types, where a type in ui.compose.style.LicenseHueResolver uses a type in ui.compose.style.
- The types involved
com.mikepenz.aboutlibraries.ui.compose.style.LicenseHueResolver.Companion→com.mikepenz.aboutlibraries.ui.compose.style.LicenseHueResolver
- Direction
- ui.compose.style.LicenseHueResolver uses ui.compose.style, so a change to ui.compose.style can break ui.compose.style.LicenseHueResolver, while a change to ui.compose.style.LicenseHueResolver can't break ui.compose.style.
- Position
- Below the diagonal: ui.compose.style.LicenseHueResolver uses a module listed above it, which is the healthy direction.
28→1 ui.compose.variant.refined uses entity✕
- Connections
- 1 pair of types, where a type in ui.compose.variant.refined uses a type in entity.
- The types involved
com.mikepenz.aboutlibraries.ui.compose.variant.refined.RefinedRowKt→com.mikepenz.aboutlibraries.entity.Library
- Direction
- ui.compose.variant.refined uses entity, so a change to entity can break ui.compose.variant.refined, while a change to ui.compose.variant.refined can't break entity.
- Position
- Below the diagonal: ui.compose.variant.refined uses a module listed above it, which is the healthy direction.
28→9 ui.compose.variant.refined uses ui.compose.variant✕
- Connections
- 2 pairs of types, where a type in ui.compose.variant.refined uses a type in ui.compose.variant.
- The types involved
com.mikepenz.aboutlibraries.ui.compose.variant.refined.RefinedRowKt→com.mikepenz.aboutlibraries.ui.compose.variant.LibrariesDensitycom.mikepenz.aboutlibraries.ui.compose.variant.refined.RefinedRowKt→com.mikepenz.aboutlibraries.ui.compose.variant.LibraryBadges
- Direction
- ui.compose.variant.refined uses ui.compose.variant, so a change to ui.compose.variant can break ui.compose.variant.refined, while a change to ui.compose.variant.refined can't break ui.compose.variant.
- Position
- Below the diagonal: ui.compose.variant.refined uses a module listed above it, which is the healthy direction.
28→14 ui.compose.variant.refined uses ui.compose.style✕
- Connections
- 4 pairs of types, where a type in ui.compose.variant.refined uses a type in ui.compose.style.
- The types involved
com.mikepenz.aboutlibraries.ui.compose.variant.refined.RefinedHeaderKt→com.mikepenz.aboutlibraries.ui.compose.style.LibrariesStylecom.mikepenz.aboutlibraries.ui.compose.variant.refined.RefinedHeaderKt→com.mikepenz.aboutlibraries.ui.compose.style.LibraryStringscom.mikepenz.aboutlibraries.ui.compose.variant.refined.RefinedRowKt→com.mikepenz.aboutlibraries.ui.compose.style.LibrariesStylecom.mikepenz.aboutlibraries.ui.compose.variant.refined.RefinedRowKt→com.mikepenz.aboutlibraries.ui.compose.style.VariantDimensions
- Direction
- ui.compose.variant.refined uses ui.compose.style, so a change to ui.compose.style can break ui.compose.variant.refined, while a change to ui.compose.variant.refined can't break ui.compose.style.
- Position
- Below the diagonal: ui.compose.variant.refined uses a module listed above it, which is the healthy direction.
29→1 ui.compose.variant.traditional uses entity✕
- Connections
- 1 pair of types, where a type in ui.compose.variant.traditional uses a type in entity.
- The types involved
com.mikepenz.aboutlibraries.ui.compose.variant.traditional.TraditionalRowKt→com.mikepenz.aboutlibraries.entity.Library
- Direction
- ui.compose.variant.traditional uses entity, so a change to entity can break ui.compose.variant.traditional, while a change to ui.compose.variant.traditional can't break entity.
- Position
- Below the diagonal: ui.compose.variant.traditional uses a module listed above it, which is the healthy direction.
29→9 ui.compose.variant.traditional uses ui.compose.variant✕
- Connections
- 2 pairs of types, where a type in ui.compose.variant.traditional uses a type in ui.compose.variant.
- The types involved
com.mikepenz.aboutlibraries.ui.compose.variant.traditional.TraditionalRowKt→com.mikepenz.aboutlibraries.ui.compose.variant.LibrariesDensitycom.mikepenz.aboutlibraries.ui.compose.variant.traditional.TraditionalRowKt→com.mikepenz.aboutlibraries.ui.compose.variant.LibraryBadges
- Direction
- ui.compose.variant.traditional uses ui.compose.variant, so a change to ui.compose.variant can break ui.compose.variant.traditional, while a change to ui.compose.variant.traditional can't break ui.compose.variant.
- Position
- Below the diagonal: ui.compose.variant.traditional uses a module listed above it, which is the healthy direction.
29→14 ui.compose.variant.traditional uses ui.compose.style✕
- Connections
- 6 pairs of types, where a type in ui.compose.variant.traditional uses a type in ui.compose.style.
- The types involved
com.mikepenz.aboutlibraries.ui.compose.variant.traditional.TraditionalHeaderKt→com.mikepenz.aboutlibraries.ui.compose.style.LibrariesStylecom.mikepenz.aboutlibraries.ui.compose.variant.traditional.TraditionalHeaderKt→com.mikepenz.aboutlibraries.ui.compose.style.LibraryStringscom.mikepenz.aboutlibraries.ui.compose.variant.traditional.TraditionalRowKt→com.mikepenz.aboutlibraries.ui.compose.style.LibrariesStylecom.mikepenz.aboutlibraries.ui.compose.variant.traditional.TraditionalRowKt→com.mikepenz.aboutlibraries.ui.compose.style.VariantColorscom.mikepenz.aboutlibraries.ui.compose.variant.traditional.TraditionalRowKt→com.mikepenz.aboutlibraries.ui.compose.style.VariantShapescom.mikepenz.aboutlibraries.ui.compose.variant.traditional.TraditionalRowKt→com.mikepenz.aboutlibraries.ui.compose.style.VariantTextStyles
- Direction
- ui.compose.variant.traditional uses ui.compose.style, so a change to ui.compose.style can break ui.compose.variant.traditional, while a change to ui.compose.variant.traditional can't break ui.compose.style.
- Position
- Below the diagonal: ui.compose.variant.traditional uses a module listed above it, which is the healthy direction.
30→1 util uses entity✕
- Connections
- 2 pairs of types, where a type in util uses a type in entity.
- The types involved
com.mikepenz.aboutlibraries.util.Result→com.mikepenz.aboutlibraries.entity.Librarycom.mikepenz.aboutlibraries.util.Result→com.mikepenz.aboutlibraries.entity.License
- Direction
- util uses entity, so a change to entity can break util, while a change to util can't break entity.
- Position
- Below the diagonal: util uses a module listed above it, which is the healthy direction.
30→10 util uses Libs✕
- Connections
- 2 pairs of types, where a type in util uses a type in Libs.
- The types involved
com.mikepenz.aboutlibraries.util.AndroidExtensionsKt→com.mikepenz.aboutlibraries.Libs.Buildercom.mikepenz.aboutlibraries.util.JvmExtensionsKt→com.mikepenz.aboutlibraries.Libs.Builder
- Direction
- util uses Libs, so a change to Libs can break util, while a change to util can't break Libs.
- Position
- Below the diagonal: util uses a module listed above it, which is the healthy direction.
31→21 plugin.DuplicateMode uses plugin✕
- Connections
- 3 pairs of types, where a type in plugin.DuplicateMode uses a type in plugin.
- The types involved
com.mikepenz.aboutlibraries.plugin.DuplicateMode.KEEP→com.mikepenz.aboutlibraries.plugin.DuplicateModecom.mikepenz.aboutlibraries.plugin.DuplicateMode.LINK→com.mikepenz.aboutlibraries.plugin.DuplicateModecom.mikepenz.aboutlibraries.plugin.DuplicateMode.MERGE→com.mikepenz.aboutlibraries.plugin.DuplicateMode
- Direction
- plugin.DuplicateMode uses plugin, so a change to plugin can break plugin.DuplicateMode, while a change to plugin.DuplicateMode can't break plugin.
- Position
- Below the diagonal: plugin.DuplicateMode uses a module listed above it, which is the healthy direction.
32→21 plugin.DuplicateRule uses plugin✕
- Connections
- 3 pairs of types, where a type in plugin.DuplicateRule uses a type in plugin.
- The types involved
com.mikepenz.aboutlibraries.plugin.DuplicateRule.EXACT→com.mikepenz.aboutlibraries.plugin.DuplicateRulecom.mikepenz.aboutlibraries.plugin.DuplicateRule.GROUP→com.mikepenz.aboutlibraries.plugin.DuplicateRulecom.mikepenz.aboutlibraries.plugin.DuplicateRule.SIMPLE→com.mikepenz.aboutlibraries.plugin.DuplicateRule
- Direction
- plugin.DuplicateRule uses plugin, so a change to plugin can break plugin.DuplicateRule, while a change to plugin.DuplicateRule can't break plugin.
- Position
- Below the diagonal: plugin.DuplicateRule uses a module listed above it, which is the healthy direction.
33→21 plugin.StrictMode uses plugin✕
- Connections
- 3 pairs of types, where a type in plugin.StrictMode uses a type in plugin.
- The types involved
com.mikepenz.aboutlibraries.plugin.StrictMode.FAIL→com.mikepenz.aboutlibraries.plugin.StrictModecom.mikepenz.aboutlibraries.plugin.StrictMode.IGNORE→com.mikepenz.aboutlibraries.plugin.StrictModecom.mikepenz.aboutlibraries.plugin.StrictMode.WARN→com.mikepenz.aboutlibraries.plugin.StrictMode
- Direction
- plugin.StrictMode uses plugin, so a change to plugin can break plugin.StrictMode, while a change to plugin.StrictMode can't break plugin.
- Position
- Below the diagonal: plugin.StrictMode uses a module listed above it, which is the healthy direction.
34→1 ui.compose.SharedLibraries uses entity✕
- Connections
- 5 pairs of types, where a type in ui.compose.SharedLibraries uses a type in entity.
- The types involved
com.mikepenz.aboutlibraries.ui.compose.SharedLibraries.androidKt→com.mikepenz.aboutlibraries.entity.Librarycom.mikepenz.aboutlibraries.ui.compose.SharedLibraries.jsKt→com.mikepenz.aboutlibraries.entity.Librarycom.mikepenz.aboutlibraries.ui.compose.SharedLibraries.jvmKt→com.mikepenz.aboutlibraries.entity.Librarycom.mikepenz.aboutlibraries.ui.compose.SharedLibraries.nativeKt→com.mikepenz.aboutlibraries.entity.Librarycom.mikepenz.aboutlibraries.ui.compose.SharedLibraries.wasmJsKt→com.mikepenz.aboutlibraries.entity.Library
- Direction
- ui.compose.SharedLibraries uses entity, so a change to entity can break ui.compose.SharedLibraries, while a change to ui.compose.SharedLibraries can't break entity.
- Position
- Below the diagonal: ui.compose.SharedLibraries uses a module listed above it, which is the healthy direction.
34→23 ui.compose.SharedLibraries uses ui.compose✕
- Connections
- 5 pairs of types, where a type in ui.compose.SharedLibraries uses a type in ui.compose.
- The types involved
com.mikepenz.aboutlibraries.ui.compose.SharedLibraries.androidKt→com.mikepenz.aboutlibraries.ui.compose.LibraryColorscom.mikepenz.aboutlibraries.ui.compose.SharedLibraries.jsKt→com.mikepenz.aboutlibraries.ui.compose.LibraryColorscom.mikepenz.aboutlibraries.ui.compose.SharedLibraries.jvmKt→com.mikepenz.aboutlibraries.ui.compose.LibraryColorscom.mikepenz.aboutlibraries.ui.compose.SharedLibraries.nativeKt→com.mikepenz.aboutlibraries.ui.compose.LibraryColorscom.mikepenz.aboutlibraries.ui.compose.SharedLibraries.wasmJsKt→com.mikepenz.aboutlibraries.ui.compose.LibraryColors
- Direction
- ui.compose.SharedLibraries uses ui.compose, so a change to ui.compose can break ui.compose.SharedLibraries, while a change to ui.compose.SharedLibraries can't break ui.compose.
- Position
- Below the diagonal: ui.compose.SharedLibraries uses a module listed above it, which is the healthy direction.
35→1 ui.compose.component uses entity✕
- Connections
- 2 pairs of types, where a type in ui.compose.component uses a type in entity.
- The types involved
com.mikepenz.aboutlibraries.ui.compose.component.LibraryDefaultComponentsKt→com.mikepenz.aboutlibraries.entity.Fundingcom.mikepenz.aboutlibraries.ui.compose.component.LibraryDefaultComponentsKt→com.mikepenz.aboutlibraries.entity.License
- Direction
- ui.compose.component uses entity, so a change to entity can break ui.compose.component, while a change to ui.compose.component can't break entity.
- Position
- Below the diagonal: ui.compose.component uses a module listed above it, which is the healthy direction.
35→23 ui.compose.component uses ui.compose✕
- Connections
- 5 pairs of types, where a type in ui.compose.component uses a type in ui.compose.
- The types involved
com.mikepenz.aboutlibraries.ui.compose.component.LibraryDefaultComponentsKt→com.mikepenz.aboutlibraries.ui.compose.LibraryColorscom.mikepenz.aboutlibraries.ui.compose.component.LibraryDefaultComponentsKt→com.mikepenz.aboutlibraries.ui.compose.LibraryDimensionscom.mikepenz.aboutlibraries.ui.compose.component.LibraryDefaultComponentsKt→com.mikepenz.aboutlibraries.ui.compose.LibraryPaddingcom.mikepenz.aboutlibraries.ui.compose.component.LibraryDefaultComponentsKt→com.mikepenz.aboutlibraries.ui.compose.LibraryShapescom.mikepenz.aboutlibraries.ui.compose.component.LibraryDefaultComponentsKt→com.mikepenz.aboutlibraries.ui.compose.LibraryTextStyles
- Direction
- ui.compose.component uses ui.compose, so a change to ui.compose can break ui.compose.component, while a change to ui.compose.component can't break ui.compose.
- Position
- Below the diagonal: ui.compose.component uses a module listed above it, which is the healthy direction.
36→1 ui.compose.m3 uses entity✕
- Connections
- 1 pair of types, where a type in ui.compose.m3 uses a type in entity.
- The types involved
com.mikepenz.aboutlibraries.ui.compose.m3.SharedLibrariesKt→com.mikepenz.aboutlibraries.entity.Library
- Direction
- ui.compose.m3 uses entity, so a change to entity can break ui.compose.m3, while a change to ui.compose.m3 can't break entity.
- Position
- Below the diagonal: ui.compose.m3 uses a module listed above it, which is the healthy direction.
36→3 ui.compose.m3 uses com.mikepenz.aboutlibraries✕
- Connections
- 1 pair of types, where a type in ui.compose.m3 uses a type in com.mikepenz.aboutlibraries.
- The types involved
com.mikepenz.aboutlibraries.ui.compose.m3.SharedLibrariesKt→com.mikepenz.aboutlibraries.Libs
- Direction
- ui.compose.m3 uses com.mikepenz.aboutlibraries, so a change to com.mikepenz.aboutlibraries can break ui.compose.m3, while a change to ui.compose.m3 can't break com.mikepenz.aboutlibraries.
- Position
- Below the diagonal: ui.compose.m3 uses a module listed above it, which is the healthy direction.
36→9 ui.compose.m3 uses ui.compose.variant✕
- Connections
- 6 pairs of types, where a type in ui.compose.m3 uses a type in ui.compose.variant.
- The types involved
com.mikepenz.aboutlibraries.ui.compose.m3.SharedLibrariesKt→com.mikepenz.aboutlibraries.ui.compose.variant.LibrariesDensitycom.mikepenz.aboutlibraries.ui.compose.m3.SharedLibrariesKt→com.mikepenz.aboutlibraries.ui.compose.variant.LibrariesVariantcom.mikepenz.aboutlibraries.ui.compose.m3.SharedLibrariesKt→com.mikepenz.aboutlibraries.ui.compose.variant.LibraryActionKindcom.mikepenz.aboutlibraries.ui.compose.m3.SharedLibrariesKt→com.mikepenz.aboutlibraries.ui.compose.variant.LibraryActionModecom.mikepenz.aboutlibraries.ui.compose.m3.SharedLibrariesKt→com.mikepenz.aboutlibraries.ui.compose.variant.LibraryBadgescom.mikepenz.aboutlibraries.ui.compose.m3.SharedLibrariesKt→com.mikepenz.aboutlibraries.ui.compose.variant.LibraryDetailMode
- Direction
- ui.compose.m3 uses ui.compose.variant, so a change to ui.compose.variant can break ui.compose.m3, while a change to ui.compose.m3 can't break ui.compose.variant.
- Position
- Below the diagonal: ui.compose.m3 uses a module listed above it, which is the healthy direction.
36→14 ui.compose.m3 uses ui.compose.style✕
- Connections
- 4 pairs of types, where a type in ui.compose.m3 uses a type in ui.compose.style.
- The types involved
com.mikepenz.aboutlibraries.ui.compose.m3.SharedLibrariesKt→com.mikepenz.aboutlibraries.ui.compose.style.LibrariesStylecom.mikepenz.aboutlibraries.ui.compose.m3.SharedLibrariesKt→com.mikepenz.aboutlibraries.ui.compose.style.LibraryActionBadgescom.mikepenz.aboutlibraries.ui.compose.m3.SharedLibrariesKt→com.mikepenz.aboutlibraries.ui.compose.style.VariantColorscom.mikepenz.aboutlibraries.ui.compose.m3.SharedLibrariesKt→com.mikepenz.aboutlibraries.ui.compose.style.VariantTextStyles
- Direction
- ui.compose.m3 uses ui.compose.style, so a change to ui.compose.style can break ui.compose.m3, while a change to ui.compose.m3 can't break ui.compose.style.
- Position
- Below the diagonal: ui.compose.m3 uses a module listed above it, which is the healthy direction.
36→23 ui.compose.m3 uses ui.compose✕
- Connections
- 2 pairs of types, where a type in ui.compose.m3 uses a type in ui.compose.
- The types involved
com.mikepenz.aboutlibraries.ui.compose.m3.SharedLibrariesKt→com.mikepenz.aboutlibraries.ui.compose.ChipColorscom.mikepenz.aboutlibraries.ui.compose.m3.SharedLibrariesKt→com.mikepenz.aboutlibraries.ui.compose.LibraryColors
- Direction
- ui.compose.m3 uses ui.compose, so a change to ui.compose can break ui.compose.m3, while a change to ui.compose.m3 can't break ui.compose.
- Position
- Below the diagonal: ui.compose.m3 uses a module listed above it, which is the healthy direction.
37→1 ui.compose.m3.SharedLibraries uses entity✕
- Connections
- 5 pairs of types, where a type in ui.compose.m3.SharedLibraries uses a type in entity.
- The types involved
com.mikepenz.aboutlibraries.ui.compose.m3.SharedLibraries.androidKt→com.mikepenz.aboutlibraries.entity.Librarycom.mikepenz.aboutlibraries.ui.compose.m3.SharedLibraries.jsKt→com.mikepenz.aboutlibraries.entity.Librarycom.mikepenz.aboutlibraries.ui.compose.m3.SharedLibraries.jvmKt→com.mikepenz.aboutlibraries.entity.Librarycom.mikepenz.aboutlibraries.ui.compose.m3.SharedLibraries.nativeKt→com.mikepenz.aboutlibraries.entity.Librarycom.mikepenz.aboutlibraries.ui.compose.m3.SharedLibraries.wasmJsKt→com.mikepenz.aboutlibraries.entity.Library
- Direction
- ui.compose.m3.SharedLibraries uses entity, so a change to entity can break ui.compose.m3.SharedLibraries, while a change to ui.compose.m3.SharedLibraries can't break entity.
- Position
- Below the diagonal: ui.compose.m3.SharedLibraries uses a module listed above it, which is the healthy direction.
37→23 ui.compose.m3.SharedLibraries uses ui.compose✕
- Connections
- 5 pairs of types, where a type in ui.compose.m3.SharedLibraries uses a type in ui.compose.
- The types involved
com.mikepenz.aboutlibraries.ui.compose.m3.SharedLibraries.androidKt→com.mikepenz.aboutlibraries.ui.compose.LibraryColorscom.mikepenz.aboutlibraries.ui.compose.m3.SharedLibraries.jsKt→com.mikepenz.aboutlibraries.ui.compose.LibraryColorscom.mikepenz.aboutlibraries.ui.compose.m3.SharedLibraries.jvmKt→com.mikepenz.aboutlibraries.ui.compose.LibraryColorscom.mikepenz.aboutlibraries.ui.compose.m3.SharedLibraries.nativeKt→com.mikepenz.aboutlibraries.ui.compose.LibraryColorscom.mikepenz.aboutlibraries.ui.compose.m3.SharedLibraries.wasmJsKt→com.mikepenz.aboutlibraries.ui.compose.LibraryColors
- Direction
- ui.compose.m3.SharedLibraries uses ui.compose, so a change to ui.compose can break ui.compose.m3.SharedLibraries, while a change to ui.compose.m3.SharedLibraries can't break ui.compose.
- Position
- Below the diagonal: ui.compose.m3.SharedLibraries uses a module listed above it, which is the healthy direction.
38→1 ui.compose.m3.component uses entity✕
- Connections
- 2 pairs of types, where a type in ui.compose.m3.component uses a type in entity.
- The types involved
com.mikepenz.aboutlibraries.ui.compose.m3.component.LibraryDefaultComponentsKt→com.mikepenz.aboutlibraries.entity.Fundingcom.mikepenz.aboutlibraries.ui.compose.m3.component.LibraryDefaultComponentsKt→com.mikepenz.aboutlibraries.entity.License
- Direction
- ui.compose.m3.component uses entity, so a change to entity can break ui.compose.m3.component, while a change to ui.compose.m3.component can't break entity.
- Position
- Below the diagonal: ui.compose.m3.component uses a module listed above it, which is the healthy direction.
38→23 ui.compose.m3.component uses ui.compose✕
- Connections
- 5 pairs of types, where a type in ui.compose.m3.component uses a type in ui.compose.
- The types involved
com.mikepenz.aboutlibraries.ui.compose.m3.component.LibraryDefaultComponentsKt→com.mikepenz.aboutlibraries.ui.compose.LibraryColorscom.mikepenz.aboutlibraries.ui.compose.m3.component.LibraryDefaultComponentsKt→com.mikepenz.aboutlibraries.ui.compose.LibraryDimensionscom.mikepenz.aboutlibraries.ui.compose.m3.component.LibraryDefaultComponentsKt→com.mikepenz.aboutlibraries.ui.compose.LibraryPaddingcom.mikepenz.aboutlibraries.ui.compose.m3.component.LibraryDefaultComponentsKt→com.mikepenz.aboutlibraries.ui.compose.LibraryShapescom.mikepenz.aboutlibraries.ui.compose.m3.component.LibraryDefaultComponentsKt→com.mikepenz.aboutlibraries.ui.compose.LibraryTextStyles
- Direction
- ui.compose.m3.component uses ui.compose, so a change to ui.compose can break ui.compose.m3.component, while a change to ui.compose.m3.component can't break ui.compose.
- Position
- Below the diagonal: ui.compose.m3.component uses a module listed above it, which is the healthy direction.
39→1 ui.compose.wear uses entity✕
- Connections
- 2 pairs of types, where a type in ui.compose.wear uses a type in entity.
- The types involved
com.mikepenz.aboutlibraries.ui.compose.wear.SharedLibrariesKt→com.mikepenz.aboutlibraries.entity.Librarycom.mikepenz.aboutlibraries.ui.compose.wear.SharedLibrariesKt→com.mikepenz.aboutlibraries.entity.License
- Direction
- ui.compose.wear uses entity, so a change to entity can break ui.compose.wear, while a change to ui.compose.wear can't break entity.
- Position
- Below the diagonal: ui.compose.wear uses a module listed above it, which is the healthy direction.
39→3 ui.compose.wear uses com.mikepenz.aboutlibraries✕
- Connections
- 1 pair of types, where a type in ui.compose.wear uses a type in com.mikepenz.aboutlibraries.
- The types involved
com.mikepenz.aboutlibraries.ui.compose.wear.SharedLibrariesKt→com.mikepenz.aboutlibraries.Libs
- Direction
- ui.compose.wear uses com.mikepenz.aboutlibraries, so a change to com.mikepenz.aboutlibraries can break ui.compose.wear, while a change to ui.compose.wear can't break com.mikepenz.aboutlibraries.
- Position
- Below the diagonal: ui.compose.wear uses a module listed above it, which is the healthy direction.
39→23 ui.compose.wear uses ui.compose✕
- Connections
- 6 pairs of types, where a type in ui.compose.wear uses a type in ui.compose.
- The types involved
com.mikepenz.aboutlibraries.ui.compose.wear.SharedLibrariesKt→com.mikepenz.aboutlibraries.ui.compose.ChipColorscom.mikepenz.aboutlibraries.ui.compose.wear.SharedLibrariesKt→com.mikepenz.aboutlibraries.ui.compose.LibraryColorscom.mikepenz.aboutlibraries.ui.compose.wear.SharedLibrariesKt→com.mikepenz.aboutlibraries.ui.compose.LibraryDimensionscom.mikepenz.aboutlibraries.ui.compose.wear.SharedLibrariesKt→com.mikepenz.aboutlibraries.ui.compose.LibraryPaddingcom.mikepenz.aboutlibraries.ui.compose.wear.SharedLibrariesKt→com.mikepenz.aboutlibraries.ui.compose.LibraryShapescom.mikepenz.aboutlibraries.ui.compose.wear.SharedLibrariesKt→com.mikepenz.aboutlibraries.ui.compose.LibraryTextStyles
- Direction
- ui.compose.wear uses ui.compose, so a change to ui.compose can break ui.compose.wear, while a change to ui.compose.wear can't break ui.compose.
- Position
- Below the diagonal: ui.compose.wear uses a module listed above it, which is the healthy direction.
40→1 ui.compose.wear.component uses entity✕
- Connections
- 3 pairs of types, where a type in ui.compose.wear.component uses a type in entity.
- The types involved
com.mikepenz.aboutlibraries.ui.compose.wear.component.LibrariesScaffoldKt→com.mikepenz.aboutlibraries.entity.Librarycom.mikepenz.aboutlibraries.ui.compose.wear.component.LibrariesScaffoldKt→com.mikepenz.aboutlibraries.entity.Licensecom.mikepenz.aboutlibraries.ui.compose.wear.component.LibraryDefaultComponentsKt→com.mikepenz.aboutlibraries.entity.License
- Direction
- ui.compose.wear.component uses entity, so a change to entity can break ui.compose.wear.component, while a change to ui.compose.wear.component can't break entity.
- Position
- Below the diagonal: ui.compose.wear.component uses a module listed above it, which is the healthy direction.
40→23 ui.compose.wear.component uses ui.compose✕
- Connections
- 7 pairs of types, where a type in ui.compose.wear.component uses a type in ui.compose.
- The types involved
com.mikepenz.aboutlibraries.ui.compose.wear.component.LibrariesScaffoldKt→com.mikepenz.aboutlibraries.ui.compose.LibraryDimensionscom.mikepenz.aboutlibraries.ui.compose.wear.component.LibrariesScaffoldKt→com.mikepenz.aboutlibraries.ui.compose.LibraryPaddingcom.mikepenz.aboutlibraries.ui.compose.wear.component.LibraryDefaultComponentsKt→com.mikepenz.aboutlibraries.ui.compose.LibraryColorscom.mikepenz.aboutlibraries.ui.compose.wear.component.LibraryDefaultComponentsKt→com.mikepenz.aboutlibraries.ui.compose.LibraryDimensionscom.mikepenz.aboutlibraries.ui.compose.wear.component.LibraryDefaultComponentsKt→com.mikepenz.aboutlibraries.ui.compose.LibraryPaddingcom.mikepenz.aboutlibraries.ui.compose.wear.component.LibraryDefaultComponentsKt→com.mikepenz.aboutlibraries.ui.compose.LibraryShapescom.mikepenz.aboutlibraries.ui.compose.wear.component.LibraryDefaultComponentsKt→com.mikepenz.aboutlibraries.ui.compose.LibraryTextStyles
- Direction
- ui.compose.wear.component uses ui.compose, so a change to ui.compose can break ui.compose.wear.component, while a change to ui.compose.wear.component can't break ui.compose.
- Position
- Below the diagonal: ui.compose.wear.component 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
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 17 | High / Critical |
| A05:2025 — Injection | 4 | High / Critical |
| A07:2025 — Authentication Failures | 2 | High / Critical |
Roadmap
Top priorities: Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label; 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; Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label. | +10.0 pts | Medium | Forms & labels |
| 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. | +9.1 pts | Medium | Visual & motion safety |
| Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh. | +5.6 pts | Medium | Page structure |
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.gradle.kts. | +2.2 pts | Low | ADR Quality |
| Interpolated log message defeats structured logging | +2.8 pts | Medium | Structured logging |
| 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. | +2.0 pts | Medium | Architecture documentation |
| Swallowed exception (caught, then discarded) | +1.7 pts | Medium | Exception handling |
| Bring the 7 bodies over 15 down to 15 or less in Cognitive Complexity — start with LibraryPostProcessor.process (cognitive 69), AboutLibrariesTask.action (cognitive 41), AboutLibrariesExportComplianceTask.action (cognitive 36). | +1.5 pts | High | Cognitive Complexity |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| sample/android/src/debug/kotlin/com/mikepenz/aboutlibraries/screenshot/VariantPreviews.kt | 7.0 | Mixed | Code Duplication: Edited copy of a member (20 corresponding lines) |
| aboutlibraries-compose-m2/src/commonMain/kotlin/com/mikepenz/aboutlibraries/ui/compose/SharedLibraries.kt | 7.0 | Mixed | Code Duplication: Edited copy of a member (34 corresponding lines) |
| sample/android/src/debug/kotlin/com/mikepenz/aboutlibraries/screenshot/SampleAppPreviews.kt | 7.0 | Mixed | Code Duplication: Edited copy of a member (23 corresponding lines) |
| plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/AboutLibrariesExportComplianceTask.kt | 7.2 | Mixed | Cyclomatic Complexity: AboutLibrariesExportComplianceTask.action (cyclomatic 18) |
| REDACTED | 7.2 | Mixed | Secrets (history): REDACTED: REDACTED |
| plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/util/LibraryPostProcessor.kt | 7.4 | Mixed | Cyclomatic Complexity: LibraryPostProcessor.process (cyclomatic 33) |
| aboutlibraries-compose/src/commonMain/kotlin/com/mikepenz/aboutlibraries/ui/compose/variant/refined/RefinedRow.kt | 7.4 | Mixed | Cognitive Complexity: RefinedRowKt.RefinedRow (cognitive 18) |
| aboutlibraries-compose/src/commonMain/kotlin/com/mikepenz/aboutlibraries/ui/compose/variant/refined/RefinedHeader.kt | 7.4 | Mixed | Code Duplication: Edited copy of a member (84 corresponding lines) |
| aboutlibraries-compose-m2/src/commonMain/kotlin/com/mikepenz/aboutlibraries/ui/compose/style/M2LibrariesStyle.kt | 7.4 | Mixed | Code Duplication: Edited copy of a member (57 corresponding lines) |
| aboutlibraries-compose-m2/src/commonMain/kotlin/com/mikepenz/aboutlibraries/ui/compose/style/M2VariantTokens.kt | 7.4 | Mixed | Code Duplication: Duplicated block (19 lines × 2) |
| sample/shared/src/commonMain/kotlin/com/mikepenz/aboutlibraries/sample/App.kt | 7.4 | Mixed | Code Duplication: Duplicated block (18 lines × 2) |
| plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/AboutLibrariesTask.kt | 7.8 | Mixed | Cyclomatic Complexity: AboutLibrariesTask.action (cyclomatic 19) |
| aboutlibraries-compose/src/commonMain/kotlin/com/mikepenz/aboutlibraries/ui/compose/variant/LibraryActions.kt | 7.8 | Mixed | Cyclomatic Complexity: LibraryActionsKt.LibraryActions (cyclomatic 17) |
| aboutlibraries-core/src/androidMain/kotlin/com/mikepenz/aboutlibraries/util/AndroidParser.kt | 7.8 | Mixed | Code Duplication: Edited copy of a member (58 corresponding lines) |
| aboutlibraries-compose-m2/src/commonMain/kotlin/com/mikepenz/aboutlibraries/ui/compose/component/LibrariesChip.kt | 7.8 | Mixed | Code Duplication: Edited copy of a member (30 corresponding lines) |
| aboutlibraries-core/src/androidMain/kotlin/com/mikepenz/aboutlibraries/util/AndroidExtensions.kt | 7.8 | Mixed | Code Duplication: Edited copy of a member (11 corresponding lines) |
| REDACTED | 7.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/BaseAboutLibrariesTask.kt | 8.5 | Near-clean | Cognitive Complexity: BaseAboutLibrariesTask.configure (cognitive 26) |
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 49 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 — 49 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, 143 of 392 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.
- 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 Gradle tree, and its score reflects currency alone.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (153 contributor(s) across 3261 commit(s) sampled, automation and bot accounts excluded). One of them holds 86% of the history; the other 152 hold 0.1% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- 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 — 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. 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.
- 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 (plugin-build/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 package.json'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 — 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. 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. `aboutlibraries-compose/src/commonMain/kotlin/com/mikepenz/aboutlibraries/ui/compose/style/LicenseHueResolver.kt`, `aboutlibraries-compose/src/commonMain/kotlin/com/mikepenz/aboutlibraries/ui/compose/variant/LibraryActions.kt`, `plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/BaseAboutLibrariesTask.kt` 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.
- 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 is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing 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.
- AXB1 Runtime evidence locked — no reproducible boot — 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. Subject: 2 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates. The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. We then boot it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
- 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 Kotlin, Python 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, Python 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.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- 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.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- 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 REDACTED Scanning: REDACTED 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.
- 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.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- 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 requirements.txt, 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.
- 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.
- 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.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- 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
4 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was LibraryPostProcessor.process at 33.
What to do
- Bring the 4 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with LibraryPostProcessor.process (cyclomatic 33), AboutLibrariesTask.action (cyclomatic 19), AboutLibrariesExportComplianceTask.action (cyclomatic 18). — 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 4 together lifts Cyclomatic Complexity from 8.9 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
7 method(s) exceeded the cognitive complexity threshold of 15; the worst was LibraryPostProcessor.process at 69.
What to do
- Bring the 7 bodies over 15 down to 15 or less in Cognitive Complexity — start with LibraryPostProcessor.process (cognitive 69), AboutLibrariesTask.action (cognitive 41), AboutLibrariesExportComplianceTask.action (cognitive 36). — 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 7 together lifts Cognitive Complexity from 7.5 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
1 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 1 MethodTooLong finding(s) in God Classes — start with LibraryPostProcessor.kt. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
34 duplicated block group(s) detected. 11.6 % of the production lines (1,598 of 13,752) are in a reported copy. A further 21 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 22 of the 55 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 (10 lines × 2) finding(s) in Code Duplication — start with SharedLibraries.kt (2), RefinedHeader.kt, SampleAppPreviews.kt. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 4 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with VariantPreviews.kt (2), AndroidParser.kt, ComposeActivity.kt. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 2 Edited copy of a member (30 corresponding lines) finding(s) in Code Duplication — start with SharedLibraries.kt, LibrariesChip.kt. — One of this dimension's main actionable groups (2 warning-level).
D5 · Coupling
9 production modules (Gradle), 0 dependency cycle(s), 0 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; 1 module(s) off the main sequence, with abstractness counted on 8 of the 9 (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 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
D6 · Cohesion (LCOM4)
0 of 12 classes have LCOM4 above 3.
D11 · Test Reliability
0 flaky across 1 measured tier(s). Java/Kotlin (repository root, Gradle): measured (0 flaky).
D12 · Dependency Hygiene
This repository's Gradle dependency graph was RESOLVED BY A BUILD, across every subproject rather than the root alone: 756 artifact(s) resolved, 497 of them gradable against Maven Central, and 244 behind a shipped release. Where a version was requested and a different one won conflict resolution, the RESOLVED version is what is graded — grading the request would recommend an upgrade already applied. Known CVEs in the same graph are a separate question again, reported under D30.
D13 · REDACTED Scanning
REDACTED scan ran and found no leaked secrets.
D14 · License Compliance
0 of 12 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 16 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. 1 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 11 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.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window. Repeated repair below the complexity floor: plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/util/LibraryUtil.kt (3 of 4 changes were fixes)
What to do
- Resolve the 1 Repeated repair finding(s) in Churn × Complexity Hotspots — start with LibraryUtil.kt. — One of this dimension's main actionable groups (1 warning-level).
D17 · Explicit Debt
0 deducted task-comment markers across 13752 LoC (0.0/KLoC) → score 10.0. 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.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 4 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.gradle.kts. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
0 of 8 build units (Gradle) flagged as possibly oversized/incoherent.
D28 · Secrets (history)
1 finding(s): 0 critical, 1 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 1 REDACTED finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
4 finding(s): 0 critical, 2 high, 1 medium, 1 low. semgrep hit a parse error in 2 file(s) — `gradlew` (line 74, line 178), `plugin-build/gradlew` (line 74, line 178) — 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 1 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 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D30 · Dependency Vulnerabilities
15 finding(s): 2 critical, 8 high, 4 medium, 1 low.
What to do
- Resolve the 8 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (8). — One of this dimension's main actionable groups (8 issue-level).
- Resolve the 4 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (4). — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 2 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 53 of the 104 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
3/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- 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).
D37 · Vulnerability-disclosure Policy
A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.
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 1 platform declaration(s) and 25 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
AC2 · Forms & labels
- This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×3) — REDACTED:33, REDACTED:50, REDACTED:57
- This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label. (×9) — REDACTED:38, REDACTED:40, REDACTED:44, …
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
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — REDACTED: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.
AC6 · Visual & motion safety
- `.nl-form .nl-submit` sets color: #fff on background-color: #3396E5 — 3.2:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — DEV/definition-file-builder/css/component.css:220
- `.nl-form input: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. — DEV/definition-file-builder/css/component.css:45
- `.nl-field ul` moves (`transition: visibility 0s 0.3s, opacity 0.3s, transform 0.3s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — DEV/definition-file-builder/css/component.css:83
- `.nl-field.nl-field-open ul` moves (`transition: visibility 0s 0s, opacity 0.3s, transform 0.3s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — DEV/definition-file-builder/css/component.css:94
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
P1 · CI/CD gates
P10 · Library API & versioning
P3 · Security & performance tooling
What to do
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
P6 · Release Hygiene
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 `.forEach` 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`. — plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/AboutLibrariesExportComplianceTask.kt:129
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
X27 · Collection changed while being enumerated
X3 · Exception handling
- `catch (t: Throwable)` 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. — plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/util/LicenseUtil.kt:26
What to do
- Swallowed exception (caught, then discarded)
X30 · Support guard that admits what it rejects
X4 · Structured logging
- `error` at line 138 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. — plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/AboutLibrariesExportComplianceTask.kt:138
- `info` at line 244 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. — plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/BaseAboutLibrariesTask.kt:244
- `info` at line 247 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. — plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/BaseAboutLibrariesTask.kt:247
- `info` at line 254 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. — plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/BaseAboutLibrariesTask.kt:254
- `info` at line 257 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. — plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/BaseAboutLibrariesTask.kt:257
- `info` at line 263 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. — plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/BaseAboutLibrariesTask.kt:263
- `info` at line 266 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. — plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/BaseAboutLibrariesTask.kt:266
- `debug` at line 270 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. — plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/BaseAboutLibrariesTask.kt:270
- `warn` at line 435 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. — plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/BaseAboutLibrariesTask.kt:435
- `debug` at line 447 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. — plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/BaseAboutLibrariesTask.kt:447
- `warn` at line 464 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. — plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/BaseAboutLibrariesTask.kt:464
- `error` at line 126 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. — plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/util/DependencyCollector.kt:126
- `info` at line 260 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. — plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/util/DependencyCollector.kt:260
- `info` at line 265 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. — plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/util/DependencyCollector.kt:265
- `info` at line 269 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. — plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/util/DependencyCollector.kt:269
- `info` at line 102 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. — plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/util/LibraryPostProcessor.kt:102
- `debug` at line 138 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. — plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/util/LibraryPostProcessor.kt:138
- `debug` at line 167 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. — plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/util/LibraryPostProcessor.kt:167
- `warn` at line 171 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. — plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/util/LibraryPostProcessor.kt:171
- `debug` at line 230 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. — plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/util/LibraryPostProcessor.kt:230
- `warn` at line 255 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. — plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/util/LibraryPostProcessor.kt:255
- `info` at line 338 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. — plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/util/LibraryPostProcessor.kt:338
- `info` at line 339 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. — plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/util/LibraryPostProcessor.kt:339
- `info` at line 47 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. — plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/util/LicenseUtil.kt:47
- `error` at line 70 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. — plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/util/parser/LibraryReader.kt:70
- `error` at line 37 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. — plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/util/parser/LicenseReader.kt:37
- `error` at line 39 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. — plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/api/GitHubApi.kt:39
- `debug` at line 51 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. — plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/api/GitHubApi.kt:51
- `info` at line 61 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. — plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/api/GitHubApi.kt:61
- `warn` at line 113 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. — plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/api/GitHubApi.kt:113
- `warn` at line 174 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. — plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/api/GitHubApi.kt:174
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 |
|---|---|---|
| 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 |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 64% | Adequate — gated by X4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 98% | Exemplary | Strongest area. |
| Maturity | 70% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 76% | Strong | Solid. |
| Security | 86% | Strong | Solid. |
| Accessibility | 31% | Weak — gated by AC2, AC6 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
Unscored — 1 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 4 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 66 check(s) not relevant to this codebase
- AC1 Text alternatives — No image/media element found in the parsed markup — AC1 not applicable here.
- AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
- AC5 ARIA correctness — No ARIA usage found in the parsed markup — AC5 not applicable here.
- 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 Kotlin code is a Spring, JSR-330 or CDI singleton bean. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. No Swift request handler (a Vapor, Hummingbird, Kitura, Swifter or Perfect route handler, as a method or a registered closure) is declared, so no state is shared between request threads. 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 — not assessed — interface segregation is computed over a type surface 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
- 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
- AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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 — ~4308 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.
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- 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.
- D21 Naming Consistency — Naming consistency does not read html yet; not measured.
- 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"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .kt, .py, .swift source were not judged.
- 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) — 3 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- 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 (15 value object(s))
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and this analysis resolves a call's owner only where the receiver's type is written down in the source. Reported as guidance rather than measured
- 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 (8 module(s), 99 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, Python 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 `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a pom.xml, Gradle or sbt build, 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.
- PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
- 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.
- X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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 Python 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 Python request takes no token: asyncio cancels the task and trio or anyio the scope that made it, from outside the call, and requests, httpx, aiohttp and gRPC take a timeout, not a cancellation; 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 3% of this repository's production lines — kotlin (12,770 lines), swift (23 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — 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 — 25 finding(s)
- <input> without a programmatic label REDACTED:38
- <input> without a programmatic label REDACTED:40
- <input> without a programmatic label REDACTED:44
- <input> without a programmatic label REDACTED:46
- <input> without a programmatic label REDACTED:55
- <input> without a programmatic label REDACTED:66
- <input> without a programmatic label REDACTED:69
- <input> without a programmatic label REDACTED:74
- <input> without a programmatic label REDACTED:79
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- <select> without a programmatic label REDACTED:33
- <select> without a programmatic label REDACTED:50
- <select> without a programmatic label REDACTED:57
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 82 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (10 lines × 2) aboutlibraries-compose-m3/src/commonMain/kotlin/com/mikepenz/aboutlibraries/ui/compose/m3/SharedLibraries.kt:280
- Duplicated block (10 lines × 2) aboutlibraries-compose/src/commonMain/kotlin/com/mikepenz/aboutlibraries/ui/compose/variant/refined/RefinedHeader.kt:87
- Duplicated block (10 lines × 2) aboutlibraries-compose-m2/src/commonMain/kotlin/com/mikepenz/aboutlibraries/ui/compose/SharedLibraries.kt:250
- Duplicated block (10 lines × 2) sample/android/src/debug/kotlin/com/mikepenz/aboutlibraries/screenshot/SampleAppPreviews.kt:216
- Duplicated block (9 lines × 2) aboutlibraries-core/src/androidMain/kotlin/com/mikepenz/aboutlibraries/util/AndroidParser.kt:23
- Duplicated block (9 lines × 2) app/src/main/kotlin/com/mikepenz/aboutlibraries/sample/ComposeActivity.kt:232
- Duplicated block (9 lines × 2) sample/android/src/debug/kotlin/com/mikepenz/aboutlibraries/screenshot/VariantPreviews.kt:393
- Duplicated block (9 lines × 2) sample/android/src/debug/kotlin/com/mikepenz/aboutlibraries/screenshot/VariantPreviews.kt:236
- Animation without a prefers-reduced-motion guard DEV/definition-file-builder/css/component.css:83
- Animation without a prefers-reduced-motion guard DEV/definition-file-builder/css/component.css:94
- Edited copy of a member (30 corresponding lines) aboutlibraries-compose-m2/src/commonMain/kotlin/com/mikepenz/aboutlibraries/ui/compose/SharedLibraries.kt:89
- Edited copy of a member (30 corresponding lines) aboutlibraries-compose-m2/src/commonMain/kotlin/com/mikepenz/aboutlibraries/ui/compose/component/LibrariesChip.kt:43
- Edited copy of a member (11 corresponding lines) plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/util/parser/LibraryReader.kt:15
- Edited copy of a member (11 corresponding lines) aboutlibraries-core/src/androidMain/kotlin/com/mikepenz/aboutlibraries/util/AndroidExtensions.kt:62
- Duplicated block (19 lines × 2) aboutlibraries-compose-m2/src/commonMain/kotlin/com/mikepenz/aboutlibraries/ui/compose/style/M2LibrariesStyle.kt:59
- Duplicated block (19 lines × 2) aboutlibraries-compose-m2/src/commonMain/kotlin/com/mikepenz/aboutlibraries/ui/compose/style/M2VariantTokens.kt:49
- Duplicated block (18 lines × 2) aboutlibraries-compose-m2/src/commonMain/kotlin/com/mikepenz/aboutlibraries/ui/compose/component/LibrariesChip.kt:44
- Duplicated block (18 lines × 2) sample/shared/src/commonMain/kotlin/com/mikepenz/aboutlibraries/sample/App.kt:207
- Duplicated block (16 lines × 2) aboutlibraries-compose-m2/src/commonMain/kotlin/com/mikepenz/aboutlibraries/ui/compose/SharedLibraries.kt:103
- Duplicated block (16 lines × 2) aboutlibraries-compose/src/commonMain/kotlin/com/mikepenz/aboutlibraries/ui/compose/variant/refined/RefinedRow.kt:107
- Duplicated block (14 lines × 2) plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/AboutLibrariesExportComplianceTask.kt:54
- Duplicated block (14 lines × 2) plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/AboutLibrariesExportComplianceTask.kt:100
- Duplicated block (10 lines × 3) plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/AboutLibrariesPluginAndroidExtension.kt:16
- Duplicated block (10 lines × 3) aboutlibraries-compose-m2/src/commonMain/kotlin/com/mikepenz/aboutlibraries/ui/compose/SharedLibraries.kt:286
- Edited copy of a member (12 corresponding lines) sample/android/src/debug/kotlin/com/mikepenz/aboutlibraries/screenshot/SampleAppPreviews.kt:186
- Edited copy of a member (12 corresponding lines) sample/android/src/debug/kotlin/com/mikepenz/aboutlibraries/screenshot/SampleAppPreviews.kt:216
- Duplicated block (11 lines × 2) sample/android/src/debug/kotlin/com/mikepenz/aboutlibraries/screenshot/SampleAppPreviews.kt:302
- Duplicated block (11 lines × 2) sample/android/src/debug/kotlin/com/mikepenz/aboutlibraries/screenshot/VariantPreviews.kt:464
- Page without a main landmark REDACTED:2
- Low contrast colour pair in CSS (3.2:1) DEV/definition-file-builder/css/component.css:220
- Focus outline removed in CSS without a :focus replacement DEV/definition-file-builder/css/component.css:45
- LibraryPostProcessor.process (cyclomatic 33) plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/util/LibraryPostProcessor.kt:42
- AboutLibrariesTask.action (cyclomatic 19) plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/AboutLibrariesTask.kt:70
- AboutLibrariesExportComplianceTask.action (cyclomatic 18) plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/AboutLibrariesExportComplianceTask.kt:53
- LibraryActionsKt.LibraryActions (cyclomatic 17) aboutlibraries-compose/src/commonMain/kotlin/com/mikepenz/aboutlibraries/ui/compose/variant/LibraryActions.kt:42
- Repeated repair: plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/util/LibraryUtil.kt plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/util/LibraryUtil.kt:9
- LibraryPostProcessor.process (cognitive 69) plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/util/LibraryPostProcessor.kt:42
- AboutLibrariesTask.action (cognitive 41) plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/AboutLibrariesTask.kt:70
- AboutLibrariesExportComplianceTask.action (cognitive 36) plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/AboutLibrariesExportComplianceTask.kt:53
- LibraryActionsKt.LibraryActions (cognitive 26) aboutlibraries-compose/src/commonMain/kotlin/com/mikepenz/aboutlibraries/ui/compose/variant/LibraryActions.kt:42
- BaseAboutLibrariesTask.configure (cognitive 26) plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/BaseAboutLibrariesTask.kt:205
- DependencyCollector.loadDependencyCoordinates (cognitive 22) plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/util/DependencyCollector.kt:83
- RefinedRowKt.RefinedRow (cognitive 18) aboutlibraries-compose/src/commonMain/kotlin/com/mikepenz/aboutlibraries/ui/compose/variant/refined/RefinedRow.kt:54
- REDACTED
- MethodTooLong: LibraryPostProcessor.process plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/util/LibraryPostProcessor.kt:42
- REDACTED
- Edited copy of a member (34 corresponding lines) aboutlibraries-compose-m2/src/commonMain/kotlin/com/mikepenz/aboutlibraries/ui/compose/SharedLibraries.kt:151
- Edited copy of a member (84 corresponding lines) aboutlibraries-compose/src/commonMain/kotlin/com/mikepenz/aboutlibraries/ui/compose/variant/refined/RefinedHeader.kt:69
- Edited copy of a member (58 corresponding lines) aboutlibraries-core/src/androidMain/kotlin/com/mikepenz/aboutlibraries/util/AndroidParser.kt:12
- Edited copy of a member (57 corresponding lines) aboutlibraries-compose-m2/src/commonMain/kotlin/com/mikepenz/aboutlibraries/ui/compose/style/M2LibrariesStyle.kt:21
- Edited copy of a member (42 corresponding lines) aboutlibraries-compose-m2/src/commonMain/kotlin/com/mikepenz/aboutlibraries/ui/compose/SharedLibraries.kt:203
- Edited copy of a member (8 corresponding lines) aboutlibraries-core/src/androidMain/kotlin/com/mikepenz/aboutlibraries/util/AndroidExtensions.kt:74
- Duplicated block (34–35 lines × 2) aboutlibraries-compose-m2/src/commonMain/kotlin/com/mikepenz/aboutlibraries/ui/compose/SharedLibraries.kt:159
- Duplicated block (22–24 lines × 2) aboutlibraries-compose-m2/src/commonMain/kotlin/com/mikepenz/aboutlibraries/ui/compose/SharedLibraries.kt:204
- Duplicated block (20 lines × 3) aboutlibraries-compose/src/commonMain/kotlin/com/mikepenz/aboutlibraries/ui/compose/variant/refined/RefinedHeader.kt:103
- Duplicated block (20 lines × 2) aboutlibraries-compose-m2/src/commonMain/kotlin/com/mikepenz/aboutlibraries/ui/compose/style/M2LibrariesStyle.kt:34
- Duplicated block (17–19 lines × 2) aboutlibraries-compose-m2/src/commonMain/kotlin/com/mikepenz/aboutlibraries/ui/compose/SharedLibraries.kt:228
- Duplicated block (14–16 lines × 3) aboutlibraries-compose-m2/src/commonMain/kotlin/com/mikepenz/aboutlibraries/ui/compose/style/M2VariantTokens.kt:51
- Duplicated block (15 lines × 2) aboutlibraries-compose-m2/src/commonMain/kotlin/com/mikepenz/aboutlibraries/ui/compose/style/M2VariantTokens.kt:122
- Duplicated block (12 lines × 3) aboutlibraries-compose-m2/src/androidMain/kotlin/com/mikepenz/aboutlibraries/ui/compose/SharedLibraries.android.kt:17
- Duplicated block (6 lines × 2) aboutlibraries-compose/src/commonMain/kotlin/com/mikepenz/aboutlibraries/ui/compose/variant/refined/RefinedRow.kt:64
- Edited copy of a member (20 corresponding lines) sample/android/src/debug/kotlin/com/mikepenz/aboutlibraries/screenshot/VariantPreviews.kt:393
- Edited copy of a member (23 corresponding lines) sample/android/src/debug/kotlin/com/mikepenz/aboutlibraries/screenshot/SampleAppPreviews.kt:91
- Edited copies of one member (6 members, 10+ corresponding lines) sample/android/src/debug/kotlin/com/mikepenz/aboutlibraries/screenshot/VariantPreviews.kt:127
- Edited copy of a member (16 corresponding lines) sample/android/src/debug/kotlin/com/mikepenz/aboutlibraries/screenshot/SampleAppPreviews.kt:53
- Edited copy of a member (15 corresponding lines) sample/android/src/debug/kotlin/com/mikepenz/aboutlibraries/screenshot/SampleAppPreviews.kt:150
- Edited copy of a member (10 corresponding lines) sample/android/src/debug/kotlin/com/mikepenz/aboutlibraries/screenshot/SampleAppPreviews.kt:345
- Edited copy of a member (7 corresponding lines) sample/android/src/debug/kotlin/com/mikepenz/aboutlibraries/screenshot/VariantPreviews.kt:174
- Edited copy of a member (14 corresponding lines) sample/android/src/debug/kotlin/com/mikepenz/aboutlibraries/screenshot/VariantPreviews.kt:523
- Edited copies of one member (3 members, 7+ corresponding lines) sample/android/src/debug/kotlin/com/mikepenz/aboutlibraries/screenshot/VariantPreviews.kt:97
- Duplicated block (13 lines × 2) sample/android/src/debug/kotlin/com/mikepenz/aboutlibraries/screenshot/SampleAppPreviews.kt:268
- Duplicated block (12 lines × 2) sample/shared/src/commonMain/kotlin/com/mikepenz/aboutlibraries/sample/App.kt:226
- Duplicated block (8 lines × 2) sample/shared/src/commonMain/kotlin/com/mikepenz/aboutlibraries/sample/App.kt:322
- Duplicated block (6 lines × 3) sample/android/src/debug/kotlin/com/mikepenz/aboutlibraries/screenshot/VariantPreviews.kt:127
- Duplicated block (5 lines × 3) sample/android/src/debug/kotlin/com/mikepenz/aboutlibraries/screenshot/VariantPreviews.kt:194
- Off the main sequence: AboutLibraries:aboutlibraries-core
- Disposable created and abandoned in the function that made it plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/AboutLibrariesExportComplianceTask.kt:129
- Swallowed exception (caught, then discarded) plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/util/LicenseUtil.kt:26
Minor — 41 finding(s)
- Interpolated log message defeats structured logging plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/AboutLibrariesExportComplianceTask.kt:138
- Interpolated log message defeats structured logging plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/BaseAboutLibrariesTask.kt:244
- Interpolated log message defeats structured logging plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/BaseAboutLibrariesTask.kt:247
- Interpolated log message defeats structured logging plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/BaseAboutLibrariesTask.kt:254
- Interpolated log message defeats structured logging plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/BaseAboutLibrariesTask.kt:257
- Interpolated log message defeats structured logging plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/BaseAboutLibrariesTask.kt:263
- Interpolated log message defeats structured logging plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/BaseAboutLibrariesTask.kt:266
- Interpolated log message defeats structured logging plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/BaseAboutLibrariesTask.kt:270
- Interpolated log message defeats structured logging plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/BaseAboutLibrariesTask.kt:435
- Interpolated log message defeats structured logging plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/BaseAboutLibrariesTask.kt:447
- Interpolated log message defeats structured logging plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/BaseAboutLibrariesTask.kt:464
- Interpolated log message defeats structured logging plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/util/DependencyCollector.kt:126
- Interpolated log message defeats structured logging plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/util/DependencyCollector.kt:260
- Interpolated log message defeats structured logging plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/util/DependencyCollector.kt:265
- Interpolated log message defeats structured logging plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/util/DependencyCollector.kt:269
- Interpolated log message defeats structured logging plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/util/LibraryPostProcessor.kt:102
- Interpolated log message defeats structured logging plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/util/LibraryPostProcessor.kt:138
- Interpolated log message defeats structured logging plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/util/LibraryPostProcessor.kt:167
- Interpolated log message defeats structured logging plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/util/LibraryPostProcessor.kt:171
- Interpolated log message defeats structured logging plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/util/LibraryPostProcessor.kt:230
- Interpolated log message defeats structured logging plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/util/LibraryPostProcessor.kt:255
- Interpolated log message defeats structured logging plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/util/LibraryPostProcessor.kt:338
- Interpolated log message defeats structured logging plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/util/LibraryPostProcessor.kt:339
- Interpolated log message defeats structured logging plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/util/LicenseUtil.kt:47
- Interpolated log message defeats structured logging plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/util/parser/LibraryReader.kt:70
- Duplicated predicate aboutlibraries-compose/src/commonMain/kotlin/com/mikepenz/aboutlibraries/ui/compose/variant/refined/RefinedRow.kt:115
- Duplicated predicate aboutlibraries-compose-m2/src/commonMain/kotlin/com/mikepenz/aboutlibraries/ui/compose/SharedLibraries.kt:183
- Duplicated predicate aboutlibraries-compose-wear-m3/src/main/kotlin/com/mikepenz/aboutlibraries/ui/compose/wear/component/LibrariesScaffold.kt:141
- Duplicated predicate aboutlibraries-compose-m3/src/commonMain/kotlin/com/mikepenz/aboutlibraries/ui/compose/m3/style/M3VariantTokens.kt:136
- No ADRs found app/build.gradle.kts:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
Minor — 244 finding(s)
- Outdated (compile): org.jetbrains.kotlinx:kotlinx-serialization-json
- Outdated (compile): org.jetbrains.kotlinx:kotlinx-serialization-core
- Outdated (compile): org.jetbrains.kotlinx:atomicfu
- Outdated (compile): org.jetbrains.androidx.lifecycle:lifecycle-common
- Outdated (compile): org.jetbrains.androidx.lifecycle:lifecycle-runtime
- Outdated (compile): org.jetbrains.androidx.lifecycle:lifecycle-runtime-compose
- Outdated (compile): org.jetbrains.androidx.savedstate:savedstate
- Outdated (compile): org.jetbrains.androidx.lifecycle:lifecycle-viewmodel
- Outdated (compile): org.jetbrains.androidx.lifecycle:lifecycle-viewmodel-savedstate
- Outdated (compile): org.jetbrains.compose.annotation-internal:annotation
- Outdated (compile): org.jetbrains.compose.collection-internal:collection
- Outdated (compile): org.jetbrains.androidx.savedstate:savedstate-compose
- Outdated (compile): org.jetbrains.skiko:skiko
- Outdated (compile): org.jetbrains:annotations
- Outdated (compile): org.jetbrains.kotlinx:kotlinx-coroutines-android
- Outdated (compile): org.jetbrains.kotlinx:kotlinx-coroutines-core-jvm
- Outdated (compile): org.jetbrains.kotlinx:kotlinx-coroutines-bom
- Outdated (compile): org.jetbrains.kotlinx:kotlinx-serialization-core-jvm
- Outdated (compile): org.jetbrains.kotlinx:kotlinx-serialization-bom
- Outdated (compile): org.jspecify:jspecify
- Outdated (compile): com.google.guava:guava
- Outdated (compile): com.google.guava:failureaccess
- Outdated (compile): org.checkerframework:checker-qual
- Outdated (compile): com.google.errorprone:error_prone_annotations
- Outdated (compile): com.google.j2objc:j2objc-annotations
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-db2d97c2814c43d3bd6bd8eda08a5105/history.json --exit-code 0 --source . | 1 | 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-db2d97c2814c43d3bd6bd8eda08a5105/tree.json --exit-code 0 --source . | 1 | 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 kotlin-js-store . | 4 | 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/** . | 15 | 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 3 file(s) — `aboutlibraries-compose/src/commonMain/kotlin/com/mikepenz/aboutlibraries/ui/compose/style/LicenseHueResolver.kt`, `aboutlibraries-compose/src/commonMain/kotlin/com/mikepenz/aboutlibraries/ui/compose/variant/LibraryActions.kt`, `plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/BaseAboutLibrariesTask.kt` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 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 |