Executive summary
LazyIonEs/AndroidToolKit falls short of our standard for production, in part because it has passwords or keys in the code's history. It scores 55.4 out of 100 and is rated Adequate, and 35 of its 36 critical findings are security problems.
Security and Compliance, at 45.0, is the weakest lens and counts most in the score. The best first step is replacing the 27 passwords or keys found in the code's history, worth about 6.1 points. Adding automated security scanning comes next, worth about 5.6 points. Raising Security and Compliance to 70 would lift the score to about 61.7.
Twenty-seven passwords or keys are open to anyone who can read the repository. Seven pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and one secret can leak from the build pipeline. Replacing each exposed password or key, pinning each tool to an exact version and limiting the secret to its own step would close these risks. The package under a licence on your banned list needs replacing, or clearing with your legal team.
The product code is 19,712 lines, about €35,000 to rebuild.
If Security and Compliance rose from 45.0 to 70, the lowest score rated Strong, the score would rise from 55.4 to about 61.7.
Rebuild cost: about €35,000 · Estimate
| Cost to rebuild | €12,000 to €59,000, for 195 to 619 hours of work, about 0.2 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.8 at a score of 55. 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: 19,712 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 core.coroutine | 2 core.process | 3 data.generator.JunkCodeComposer | 4 data.source.ArscBlamer | 5 domain.cleaner | 6 domain.icon | 7 domain.junk | 8 domain.keystore | 9 domain.signature | 10 domain.signing | 11 model | 12 data.generator.MultiAarGenerator | 13 data.process | 14 domain.apk | 15 domain.junk.JunkConfiguration | 16 domain.preferences | 17 data.generator | 18 data.repository.DefaultPreferencesRepository | 19 data.source.PreferencesDataSource | 20 domain.apk.BuildApkOutcome | 21 domain.preferences.PreferenceChange | 22 domain.repository | 23 feature.app | 24 app | 25 core.validation | 26 data.generator.JunkLayoutComposer | 27 data.source | 28 domain.usecase | 29 feature.app.UiMessage | 30 data.repository | 31 feature.cleaner | 32 feature.iconfactory | 33 feature.junk | 34 feature.keystore | 35 feature.signature | 36 feature.update | 37 org.tool.kit | 38 feature.apk | 39 feature.setting | 40 platform |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 core.coroutine | ||||||||||||||||||||||||||||||||||||||||
| 2 core.process | ||||||||||||||||||||||||||||||||||||||||
| 3 data.generator.JunkCodeComposer | ||||||||||||||||||||||||||||||||||||||||
| 4 data.source.ArscBlamer | ||||||||||||||||||||||||||||||||||||||||
| 5 domain.cleaner | ||||||||||||||||||||||||||||||||||||||||
| 6 domain.icon | ||||||||||||||||||||||||||||||||||||||||
| 7 domain.junk | ||||||||||||||||||||||||||||||||||||||||
| 8 domain.keystore | ||||||||||||||||||||||||||||||||||||||||
| 9 domain.signature | ||||||||||||||||||||||||||||||||||||||||
| 10 domain.signing | ||||||||||||||||||||||||||||||||||||||||
| 11 model | ||||||||||||||||||||||||||||||||||||||||
| 12 data.generator.MultiAarGenerator | 1 | |||||||||||||||||||||||||||||||||||||||
| 13 data.process | 3 | |||||||||||||||||||||||||||||||||||||||
| 14 domain.apk | 1 | |||||||||||||||||||||||||||||||||||||||
| 15 domain.junk.JunkConfiguration | 2 | |||||||||||||||||||||||||||||||||||||||
| 16 domain.preferences | 2 | |||||||||||||||||||||||||||||||||||||||
| 17 data.generator | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 18 data.repository.DefaultPreferencesRepository | 1 | |||||||||||||||||||||||||||||||||||||||
| 19 data.source.PreferencesDataSource | 2 | 3 | ||||||||||||||||||||||||||||||||||||||
| 20 domain.apk.BuildApkOutcome | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 21 domain.preferences.PreferenceChange | 3 | 18 | ||||||||||||||||||||||||||||||||||||||
| 22 domain.repository | 5 | 2 | 3 | 2 | 1 | 2 | 8 | |||||||||||||||||||||||||||||||||
| 23 feature.app | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 24 app | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 25 core.validation | 1 | |||||||||||||||||||||||||||||||||||||||
| 26 data.generator.JunkLayoutComposer | 3 | |||||||||||||||||||||||||||||||||||||||
| 27 data.source | 1 | 1 | 3 | 1 | 2 | 2 | 2 | 2 | 8 | 1 | 4 | 2 | 9 | |||||||||||||||||||||||||||
| 28 domain.usecase | 4 | 2 | 4 | 2 | 1 | 2 | 3 | 12 | ||||||||||||||||||||||||||||||||
| 29 feature.app.UiMessage | 2 | |||||||||||||||||||||||||||||||||||||||
| 30 data.repository | 2 | 1 | 2 | 1 | 4 | 3 | 1 | 13 | 4 | |||||||||||||||||||||||||||||||
| 31 feature.cleaner | 19 | 3 | 5 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||
| 32 feature.iconfactory | 3 | 2 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 33 feature.junk | 1 | 2 | 2 | 3 | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||
| 34 feature.keystore | 2 | 1 | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 35 feature.signature | 3 | 4 | 3 | 5 | 5 | 4 | 2 | |||||||||||||||||||||||||||||||||
| 36 feature.update | 1 | 1 | 6 | 3 | 1 | |||||||||||||||||||||||||||||||||||
| 37 org.tool.kit | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 38 feature.apk | 1 | 10 | 2 | 2 | 4 | 2 | 2 | 4 | ||||||||||||||||||||||||||||||||
| 39 feature.setting | 2 | 1 | 3 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 40 platform | 1 | 1 | 1 | 2 | 1 |
12→17 data.generator.MultiAarGenerator uses data.generator part of a loop✕
- Connections
- 1 pair of types, where a type in data.generator.MultiAarGenerator uses a type in data.generator.
- The types involved
org.tool.kit.data.generator.MultiAarGenerator.AarConfig→org.tool.kit.data.generator.JunkGenerationPolicy
- Direction
- data.generator.MultiAarGenerator uses data.generator, so a change to data.generator can break data.generator.MultiAarGenerator, while a change to data.generator.MultiAarGenerator can't break data.generator.
- 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→2 data.process uses core.process✕
- Connections
- 3 pairs of types, where a type in data.process uses a type in core.process.
- The types involved
org.tool.kit.data.process.JvmProcessRunner→org.tool.kit.core.process.ProcessRequestorg.tool.kit.data.process.JvmProcessRunner→org.tool.kit.core.process.ProcessResultorg.tool.kit.data.process.JvmProcessRunner→org.tool.kit.core.process.ProcessRunner
- Direction
- data.process uses core.process, so a change to core.process can break data.process, while a change to data.process can't break core.process.
- Position
- Below the diagonal: data.process uses a module listed above it, which is the healthy direction.
14→10 domain.apk uses domain.signing✕
- Connections
- 1 pair of types, where a type in domain.apk uses a type in domain.signing.
- The types involved
org.tool.kit.domain.apk.BuildApkRequest→org.tool.kit.domain.signing.SignApkRequest
- Direction
- domain.apk uses domain.signing, so a change to domain.signing can break domain.apk, while a change to domain.apk can't break domain.signing.
- Position
- Below the diagonal: domain.apk uses a module listed above it, which is the healthy direction.
15→7 domain.junk.JunkConfiguration uses domain.junk✕
- Connections
- 2 pairs of types, where a type in domain.junk.JunkConfiguration uses a type in domain.junk.
- The types involved
org.tool.kit.domain.junk.JunkConfiguration.Multi→org.tool.kit.domain.junk.JunkConfigurationorg.tool.kit.domain.junk.JunkConfiguration.Single→org.tool.kit.domain.junk.JunkConfiguration
- Direction
- domain.junk.JunkConfiguration uses domain.junk, so a change to domain.junk can break domain.junk.JunkConfiguration, while a change to domain.junk.JunkConfiguration can't break domain.junk.
- Position
- Below the diagonal: domain.junk.JunkConfiguration uses a module listed above it, which is the healthy direction.
16→11 domain.preferences uses model✕
- Connections
- 2 pairs of types, where a type in domain.preferences uses a type in model.
- The types involved
org.tool.kit.domain.preferences.PreferencesSnapshot→org.tool.kit.model.IconFactoryDataorg.tool.kit.domain.preferences.PreferencesSnapshot→org.tool.kit.model.UserData
- Direction
- domain.preferences uses model, so a change to model can break domain.preferences, while a change to domain.preferences can't break model.
- Position
- Below the diagonal: domain.preferences uses a module listed above it, which is the healthy direction.
17→3 data.generator uses data.generator.JunkCodeComposer✕
- Connections
- 1 pair of types, where a type in data.generator uses a type in data.generator.JunkCodeComposer.
- The types involved
org.tool.kit.data.generator.JunkCodeComposer→org.tool.kit.data.generator.JunkCodeComposer.Node
- Direction
- data.generator uses data.generator.JunkCodeComposer, so a change to data.generator.JunkCodeComposer can break data.generator, while a change to data.generator can't break data.generator.JunkCodeComposer.
- Position
- Below the diagonal: data.generator uses a module listed above it, which is the healthy direction.
17→12 data.generator uses data.generator.MultiAarGenerator✕
- Connections
- 1 pair of types, where a type in data.generator uses a type in data.generator.MultiAarGenerator.
- The types involved
org.tool.kit.data.generator.MultiAarGenerator→org.tool.kit.data.generator.MultiAarGenerator.AarConfig
- Direction
- data.generator uses data.generator.MultiAarGenerator, so a change to data.generator.MultiAarGenerator can break data.generator, while a change to data.generator can't break data.generator.MultiAarGenerator.
- Position
- Below the diagonal: data.generator uses a module listed above it, which is the healthy direction.
18→16 data.repository.DefaultPreferencesRepository uses domain.preferences✕
- Connections
- 1 pair of types, where a type in data.repository.DefaultPreferencesRepository uses a type in domain.preferences.
- The types involved
org.tool.kit.data.repository.DefaultPreferencesRepository.Write→org.tool.kit.domain.preferences.PreferenceChange
- Direction
- data.repository.DefaultPreferencesRepository uses domain.preferences, so a change to domain.preferences can break data.repository.DefaultPreferencesRepository, while a change to data.repository.DefaultPreferencesRepository can't break domain.preferences.
- Position
- Below the diagonal: data.repository.DefaultPreferencesRepository uses a module listed above it, which is the healthy direction.
19→11 data.source.PreferencesDataSource uses model✕
- Connections
- 2 pairs of types, where a type in data.source.PreferencesDataSource uses a type in model.
- The types involved
org.tool.kit.data.source.PreferencesDataSource.Companion→org.tool.kit.model.IconFactoryDataorg.tool.kit.data.source.PreferencesDataSource.Companion→org.tool.kit.model.UserData
- Direction
- data.source.PreferencesDataSource uses model, so a change to model can break data.source.PreferencesDataSource, while a change to data.source.PreferencesDataSource can't break model.
- Position
- Below the diagonal: data.source.PreferencesDataSource uses a module listed above it, which is the healthy direction.
19→16 data.source.PreferencesDataSource uses domain.preferences✕
- Connections
- 3 pairs of types, where a type in data.source.PreferencesDataSource uses a type in domain.preferences.
- The types involved
org.tool.kit.data.source.PreferencesDataSource.Companion→org.tool.kit.domain.preferences.CopyPreferenceorg.tool.kit.data.source.PreferencesDataSource.Companion→org.tool.kit.domain.preferences.JunkPreferenceorg.tool.kit.data.source.PreferencesDataSource.Companion→org.tool.kit.domain.preferences.ThemePreference
- Direction
- data.source.PreferencesDataSource uses domain.preferences, so a change to domain.preferences can break data.source.PreferencesDataSource, while a change to data.source.PreferencesDataSource can't break domain.preferences.
- Position
- Below the diagonal: data.source.PreferencesDataSource uses a module listed above it, which is the healthy direction.
20→10 domain.apk.BuildApkOutcome uses domain.signing✕
- Connections
- 1 pair of types, where a type in domain.apk.BuildApkOutcome uses a type in domain.signing.
- The types involved
org.tool.kit.domain.apk.BuildApkOutcome.Success→org.tool.kit.domain.signing.SignApkOutcome
- Direction
- domain.apk.BuildApkOutcome uses domain.signing, so a change to domain.signing can break domain.apk.BuildApkOutcome, while a change to domain.apk.BuildApkOutcome can't break domain.signing.
- Position
- Below the diagonal: domain.apk.BuildApkOutcome uses a module listed above it, which is the healthy direction.
20→14 domain.apk.BuildApkOutcome uses domain.apk✕
- Connections
- 2 pairs of types, where a type in domain.apk.BuildApkOutcome uses a type in domain.apk.
- The types involved
org.tool.kit.domain.apk.BuildApkOutcome.Failure→org.tool.kit.domain.apk.BuildApkOutcomeorg.tool.kit.domain.apk.BuildApkOutcome.Success→org.tool.kit.domain.apk.BuildApkOutcome
- Direction
- domain.apk.BuildApkOutcome uses domain.apk, so a change to domain.apk can break domain.apk.BuildApkOutcome, while a change to domain.apk.BuildApkOutcome can't break domain.apk.
- Position
- Below the diagonal: domain.apk.BuildApkOutcome uses a module listed above it, which is the healthy direction.
21→11 domain.preferences.PreferenceChange uses model✕
- Connections
- 3 pairs of types, where a type in domain.preferences.PreferenceChange uses a type in model.
- The types involved
org.tool.kit.domain.preferences.PreferenceChange.IconSettings→org.tool.kit.model.IconFactoryDataorg.tool.kit.domain.preferences.PreferenceChange.StoreSize→org.tool.kit.model.DestStoreSizeorg.tool.kit.domain.preferences.PreferenceChange.StoreType→org.tool.kit.model.DestStoreType
- Direction
- domain.preferences.PreferenceChange uses model, so a change to model can break domain.preferences.PreferenceChange, while a change to domain.preferences.PreferenceChange can't break model.
- Position
- Below the diagonal: domain.preferences.PreferenceChange uses a module listed above it, which is the healthy direction.
21→16 domain.preferences.PreferenceChange uses domain.preferences✕
- Connections
- 18 pairs of types, where a type in domain.preferences.PreferenceChange uses a type in domain.preferences.
- The types involved
org.tool.kit.domain.preferences.PreferenceChange.AlignFileSize→org.tool.kit.domain.preferences.PreferenceChangeorg.tool.kit.domain.preferences.PreferenceChange.AlwaysShowLabel→org.tool.kit.domain.preferences.PreferenceChangeorg.tool.kit.domain.preferences.PreferenceChange.CopyModeChanged→org.tool.kit.domain.preferences.CopyPreferenceorg.tool.kit.domain.preferences.PreferenceChange.CopyModeChanged→org.tool.kit.domain.preferences.PreferenceChangeorg.tool.kit.domain.preferences.PreferenceChange.DeveloperMode→org.tool.kit.domain.preferences.PreferenceChangeorg.tool.kit.domain.preferences.PreferenceChange.DuplicateRemoval→org.tool.kit.domain.preferences.PreferenceChangeorg.tool.kit.domain.preferences.PreferenceChange.HuaweiAlignment→org.tool.kit.domain.preferences.PreferenceChangeorg.tool.kit.domain.preferences.PreferenceChange.IconSettings→org.tool.kit.domain.preferences.PreferenceChangeorg.tool.kit.domain.preferences.PreferenceChange.JunkModeChanged→org.tool.kit.domain.preferences.JunkPreferenceorg.tool.kit.domain.preferences.PreferenceChange.JunkModeChanged→org.tool.kit.domain.preferences.PreferenceChangeorg.tool.kit.domain.preferences.PreferenceChange.OutputPath→org.tool.kit.domain.preferences.PreferenceChangeorg.tool.kit.domain.preferences.PreferenceChange.ShowJunkCode→org.tool.kit.domain.preferences.PreferenceChangeorg.tool.kit.domain.preferences.PreferenceChange.SignerSuffix→org.tool.kit.domain.preferences.PreferenceChangeorg.tool.kit.domain.preferences.PreferenceChange.StartCheckUpdate→org.tool.kit.domain.preferences.PreferenceChangeorg.tool.kit.domain.preferences.PreferenceChange.StoreSize→org.tool.kit.domain.preferences.PreferenceChangeorg.tool.kit.domain.preferences.PreferenceChange.StoreType→org.tool.kit.domain.preferences.PreferenceChangeorg.tool.kit.domain.preferences.PreferenceChange.Theme→org.tool.kit.domain.preferences.PreferenceChangeorg.tool.kit.domain.preferences.PreferenceChange.Theme→org.tool.kit.domain.preferences.ThemePreference
- Direction
- domain.preferences.PreferenceChange uses domain.preferences, so a change to domain.preferences can break domain.preferences.PreferenceChange, while a change to domain.preferences.PreferenceChange can't break domain.preferences.
- Position
- Below the diagonal: domain.preferences.PreferenceChange uses a module listed above it, which is the healthy direction.
22→5 domain.repository uses domain.cleaner✕
- Connections
- 5 pairs of types, where a type in domain.repository uses a type in domain.cleaner.
- The types involved
org.tool.kit.domain.repository.BuildCachesRepository→org.tool.kit.domain.cleaner.BuildDirectoryorg.tool.kit.domain.repository.BuildCachesRepository→org.tool.kit.domain.cleaner.CleanerScanRequestorg.tool.kit.domain.repository.BuildCachesRepository→org.tool.kit.domain.cleaner.DeleteBuildCacheResultorg.tool.kit.domain.repository.CleanerRuleConfigSnapshot→org.tool.kit.domain.cleaner.CleanerRuleConfigorg.tool.kit.domain.repository.CleanerRulesRepository→org.tool.kit.domain.cleaner.CleanerRuleConfig
- Direction
- domain.repository uses domain.cleaner, so a change to domain.cleaner can break domain.repository, while a change to domain.repository can't break domain.cleaner.
- Position
- Below the diagonal: domain.repository uses a module listed above it, which is the healthy direction.
22→6 domain.repository uses domain.icon✕
- Connections
- 2 pairs of types, where a type in domain.repository uses a type in domain.icon.
- The types involved
org.tool.kit.domain.repository.IconOutputSession→org.tool.kit.domain.icon.IconOutputFilesorg.tool.kit.domain.repository.IconOutputs→org.tool.kit.domain.icon.GenerateIconsRequest
- Direction
- domain.repository uses domain.icon, so a change to domain.icon can break domain.repository, while a change to domain.repository can't break domain.icon.
- Position
- Below the diagonal: domain.repository uses a module listed above it, which is the healthy direction.
22→7 domain.repository uses domain.junk✕
- Connections
- 3 pairs of types, where a type in domain.repository uses a type in domain.junk.
- The types involved
org.tool.kit.domain.repository.JunkCodeRepository→org.tool.kit.domain.junk.GenerateJunkCodeRequestorg.tool.kit.domain.repository.JunkCodeRepository→org.tool.kit.domain.junk.GeneratedJunkCodeorg.tool.kit.domain.repository.JunkSizeEstimator→org.tool.kit.domain.junk.JunkSizeEstimate
- Direction
- domain.repository uses domain.junk, so a change to domain.junk can break domain.repository, while a change to domain.repository can't break domain.junk.
- Position
- Below the diagonal: domain.repository uses a module listed above it, which is the healthy direction.
22→8 domain.repository uses domain.keystore✕
- Connections
- 2 pairs of types, where a type in domain.repository uses a type in domain.keystore.
- The types involved
org.tool.kit.domain.repository.KeyStoreRepository→org.tool.kit.domain.keystore.GenerateKeyStoreOutcomeorg.tool.kit.domain.repository.KeyStoreRepository→org.tool.kit.domain.keystore.GenerateKeyStoreRequest
- Direction
- domain.repository uses domain.keystore, so a change to domain.keystore can break domain.repository, while a change to domain.repository can't break domain.keystore.
- Position
- Below the diagonal: domain.repository uses a module listed above it, which is the healthy direction.
22→9 domain.repository uses domain.signature✕
- Connections
- 1 pair of types, where a type in domain.repository uses a type in domain.signature.
- The types involved
org.tool.kit.domain.repository.SignatureRepository→org.tool.kit.domain.signature.SignatureVerification
- Direction
- domain.repository uses domain.signature, so a change to domain.signature can break domain.repository, while a change to domain.repository can't break domain.signature.
- Position
- Below the diagonal: domain.repository uses a module listed above it, which is the healthy direction.
22→10 domain.repository uses domain.signing✕
- Connections
- 2 pairs of types, where a type in domain.repository uses a type in domain.signing.
- The types involved
org.tool.kit.domain.repository.ApkSigningRepository→org.tool.kit.domain.signing.SignApkOutcomeorg.tool.kit.domain.repository.ApkSigningRepository→org.tool.kit.domain.signing.SignApkRequest
- Direction
- domain.repository uses domain.signing, so a change to domain.signing can break domain.repository, while a change to domain.repository can't break domain.signing.
- Position
- Below the diagonal: domain.repository uses a module listed above it, which is the healthy direction.
22→14 domain.repository uses domain.apk✕
- Connections
- 8 pairs of types, where a type in domain.repository uses a type in domain.apk.
- The types involved
org.tool.kit.domain.repository.ApkBuildWorkspaces→org.tool.kit.domain.apk.ApkBuildWorkspaceorg.tool.kit.domain.repository.ApkBuildWorkspaces→org.tool.kit.domain.apk.BuildApkRequestorg.tool.kit.domain.repository.ApkInformationRepository→org.tool.kit.domain.apk.ApkArchiveInformationorg.tool.kit.domain.repository.ApkInformationRepository→org.tool.kit.domain.apk.ApkComponentorg.tool.kit.domain.repository.ApkInformationRepository→org.tool.kit.domain.apk.ApkFileMetadataorg.tool.kit.domain.repository.ApkInformationRepository→org.tool.kit.domain.apk.ApkIconSourceorg.tool.kit.domain.repository.ApkToolRepository→org.tool.kit.domain.apk.ApkBuildWorkspaceorg.tool.kit.domain.repository.ApkToolRepository→org.tool.kit.domain.apk.BuildApkRequest
- Direction
- domain.repository uses domain.apk, so a change to domain.apk can break domain.repository, while a change to domain.repository can't break domain.apk.
- Position
- Below the diagonal: domain.repository uses a module listed above it, which is the healthy direction.
23→11 feature.app uses model✕
- Connections
- 1 pair of types, where a type in feature.app uses a type in model.
- The types involved
org.tool.kit.feature.app.AppUiState→org.tool.kit.model.DarkThemeConfig
- Direction
- feature.app uses model, so a change to model can break feature.app, while a change to feature.app can't break model.
- Position
- Below the diagonal: feature.app uses a module listed above it, which is the healthy direction.
23→16 feature.app uses domain.preferences✕
- Connections
- 1 pair of types, where a type in feature.app uses a type in domain.preferences.
- The types involved
org.tool.kit.feature.app.AppViewModel→org.tool.kit.domain.preferences.PreferencesRepository
- Direction
- feature.app uses domain.preferences, so a change to domain.preferences can break feature.app, while a change to feature.app can't break domain.preferences.
- Position
- Below the diagonal: feature.app uses a module listed above it, which is the healthy direction.
24→16 app uses domain.preferences✕
- Connections
- 1 pair of types, where a type in app uses a type in domain.preferences.
- The types involved
org.tool.kit.app.AppBootstrap→org.tool.kit.domain.preferences.PreferencesRepository
- Direction
- app uses domain.preferences, so a change to domain.preferences can break app, while a change to app can't break domain.preferences.
- Position
- Below the diagonal: app uses a module listed above it, which is the healthy direction.
24→22 app uses domain.repository✕
- Connections
- 2 pairs of types, where a type in app uses a type in domain.repository.
- The types involved
org.tool.kit.app.AppBootstrap→org.tool.kit.domain.repository.StorageCapacityorg.tool.kit.app.AppBootstrap→org.tool.kit.domain.repository.StorageRepository
- Direction
- app uses domain.repository, so a change to domain.repository can break app, while a change to app can't break domain.repository.
- Position
- Below the diagonal: app uses a module listed above it, which is the healthy direction.
25→22 core.validation uses domain.repository✕
- Connections
- 1 pair of types, where a type in core.validation uses a type in domain.repository.
- The types involved
org.tool.kit.core.validation.KeyAliasesValidation→org.tool.kit.domain.repository.KeyStoreRepository
- Direction
- core.validation uses domain.repository, so a change to domain.repository can break core.validation, while a change to core.validation can't break domain.repository.
- Position
- Below the diagonal: core.validation uses a module listed above it, which is the healthy direction.
26→17 data.generator.JunkLayoutComposer uses data.generator✕
- Connections
- 3 pairs of types, where a type in data.generator.JunkLayoutComposer uses a type in data.generator.
- The types involved
org.tool.kit.data.generator.JunkLayoutComposer.Composition→org.tool.kit.data.generator.JunkGenerationPolicyorg.tool.kit.data.generator.JunkLayoutComposer.Composition→org.tool.kit.data.generator.JunkLayoutResultorg.tool.kit.data.generator.JunkLayoutComposer.Composition→org.tool.kit.data.generator.JunkResourcePool
- Direction
- data.generator.JunkLayoutComposer uses data.generator, so a change to data.generator can break data.generator.JunkLayoutComposer, while a change to data.generator.JunkLayoutComposer can't break data.generator.
- Position
- Below the diagonal: data.generator.JunkLayoutComposer uses a module listed above it, which is the healthy direction.
27→2 data.source uses core.process✕
- Connections
- 1 pair of types, where a type in data.source uses a type in core.process.
- The types involved
org.tool.kit.data.source.Aapt2DataSource→org.tool.kit.core.process.ProcessRunner
- Direction
- data.source uses core.process, so a change to core.process can break data.source, while a change to data.source can't break core.process.
- Position
- Below the diagonal: data.source uses a module listed above it, which is the healthy direction.
27→4 data.source uses data.source.ArscBlamer✕
- Connections
- 1 pair of types, where a type in data.source uses a type in data.source.ArscBlamer.
- The types involved
org.tool.kit.data.source.ArscBlamer→org.tool.kit.data.source.ArscBlamer.ResourceEntry
- Direction
- data.source uses data.source.ArscBlamer, so a change to data.source.ArscBlamer can break data.source, while a change to data.source can't break data.source.ArscBlamer.
- Position
- Below the diagonal: data.source uses a module listed above it, which is the healthy direction.
27→5 data.source uses domain.cleaner✕
- Connections
- 3 pairs of types, where a type in data.source uses a type in domain.cleaner.
- The types involved
org.tool.kit.data.source.JvmBuildCachesDataSource→org.tool.kit.domain.cleaner.BuildDirectoryorg.tool.kit.data.source.JvmBuildCachesDataSource→org.tool.kit.domain.cleaner.CleanerScanRequestorg.tool.kit.data.source.JvmBuildCachesDataSource→org.tool.kit.domain.cleaner.DeleteBuildCacheResult
- Direction
- data.source uses domain.cleaner, so a change to domain.cleaner can break data.source, while a change to data.source can't break domain.cleaner.
- Position
- Below the diagonal: data.source uses a module listed above it, which is the healthy direction.
27→6 data.source uses domain.icon✕
- Connections
- 1 pair of types, where a type in data.source uses a type in domain.icon.
- The types involved
org.tool.kit.data.source.JvmIconOutputs→org.tool.kit.domain.icon.GenerateIconsRequest
- Direction
- data.source uses domain.icon, so a change to domain.icon can break data.source, while a change to data.source can't break domain.icon.
- Position
- Below the diagonal: data.source uses a module listed above it, which is the healthy direction.
27→7 data.source uses domain.junk✕
- Connections
- 2 pairs of types, where a type in data.source uses a type in domain.junk.
- The types involved
org.tool.kit.data.source.JvmJunkCodeDataSource→org.tool.kit.domain.junk.GenerateJunkCodeRequestorg.tool.kit.data.source.JvmJunkCodeDataSource→org.tool.kit.domain.junk.GeneratedJunkCode
- Direction
- data.source uses domain.junk, so a change to domain.junk can break data.source, while a change to data.source can't break domain.junk.
- Position
- Below the diagonal: data.source uses a module listed above it, which is the healthy direction.
27→8 data.source uses domain.keystore✕
- Connections
- 2 pairs of types, where a type in data.source uses a type in domain.keystore.
- The types involved
org.tool.kit.data.source.JvmKeyStoreDataSource→org.tool.kit.domain.keystore.GenerateKeyStoreOutcomeorg.tool.kit.data.source.JvmKeyStoreDataSource→org.tool.kit.domain.keystore.GenerateKeyStoreRequest
- Direction
- data.source uses domain.keystore, so a change to domain.keystore can break data.source, while a change to data.source can't break domain.keystore.
- Position
- Below the diagonal: data.source uses a module listed above it, which is the healthy direction.
27→9 data.source uses domain.signature✕
- Connections
- 2 pairs of types, where a type in data.source uses a type in domain.signature.
- The types involved
org.tool.kit.data.source.ApkVerificationMappingKt→org.tool.kit.domain.signature.SignatureVerificationorg.tool.kit.data.source.CertificateMappingKt→org.tool.kit.domain.signature.CertificateInformation
- Direction
- data.source uses domain.signature, so a change to domain.signature can break data.source, while a change to data.source can't break domain.signature.
- Position
- Below the diagonal: data.source uses a module listed above it, which is the healthy direction.
27→10 data.source uses domain.signing✕
- Connections
- 2 pairs of types, where a type in data.source uses a type in domain.signing.
- The types involved
org.tool.kit.data.source.JvmApkSignerDataSource→org.tool.kit.domain.signing.SignApkOutcomeorg.tool.kit.data.source.JvmApkSignerDataSource→org.tool.kit.domain.signing.SignApkRequest
- Direction
- data.source uses domain.signing, so a change to domain.signing can break data.source, while a change to data.source can't break domain.signing.
- Position
- Below the diagonal: data.source uses a module listed above it, which is the healthy direction.
27→14 data.source uses domain.apk✕
- Connections
- 8 pairs of types, where a type in data.source uses a type in domain.apk.
- The types involved
org.tool.kit.data.source.ApkArchiveInspectorKt→org.tool.kit.domain.apk.ApkAlignmentorg.tool.kit.data.source.ApkArchiveInspectorKt→org.tool.kit.domain.apk.ApkArchiveInformationorg.tool.kit.data.source.ApkComponentInspectorKt→org.tool.kit.domain.apk.ApkComponentorg.tool.kit.data.source.ApkIconDataSource→org.tool.kit.domain.apk.ApkIconSourceorg.tool.kit.data.source.JvmApkBuildWorkspaces→org.tool.kit.domain.apk.ApkBuildWorkspaceorg.tool.kit.data.source.JvmApkBuildWorkspaces→org.tool.kit.domain.apk.BuildApkRequestorg.tool.kit.data.source.JvmApkToolDataSource→org.tool.kit.domain.apk.ApkBuildWorkspaceorg.tool.kit.data.source.JvmApkToolDataSource→org.tool.kit.domain.apk.BuildApkRequest
- Direction
- data.source uses domain.apk, so a change to domain.apk can break data.source, while a change to data.source can't break domain.apk.
- Position
- Below the diagonal: data.source uses a module listed above it, which is the healthy direction.
27→15 data.source uses domain.junk.JunkConfiguration✕
- Connections
- 1 pair of types, where a type in data.source uses a type in domain.junk.JunkConfiguration.
- The types involved
org.tool.kit.data.source.JvmJunkCodeDataSource→org.tool.kit.domain.junk.JunkConfiguration.Single
- Direction
- data.source uses domain.junk.JunkConfiguration, so a change to domain.junk.JunkConfiguration can break data.source, while a change to data.source can't break domain.junk.JunkConfiguration.
- Position
- Below the diagonal: data.source uses a module listed above it, which is the healthy direction.
27→16 data.source uses domain.preferences✕
- Connections
- 4 pairs of types, where a type in data.source uses a type in domain.preferences.
- The types involved
org.tool.kit.data.source.PreferencesDataSource→org.tool.kit.domain.preferences.PreferenceChangeorg.tool.kit.data.source.PreferencesDataSource→org.tool.kit.domain.preferences.PreferencesSnapshotorg.tool.kit.data.source.PreferencesStorage→org.tool.kit.domain.preferences.PreferenceChangeorg.tool.kit.data.source.PreferencesStorage→org.tool.kit.domain.preferences.PreferencesSnapshot
- Direction
- data.source uses domain.preferences, so a change to domain.preferences can break data.source, while a change to data.source can't break domain.preferences.
- Position
- Below the diagonal: data.source uses a module listed above it, which is the healthy direction.
27→17 data.source uses data.generator✕
- Connections
- 2 pairs of types, where a type in data.source uses a type in data.generator.
- The types involved
org.tool.kit.data.source.JvmJunkCodeDataSource→org.tool.kit.data.generator.JunkGenerationPolicyorg.tool.kit.data.source.JvmJunkCodeDataSource→org.tool.kit.data.generator.JunkGenerationProgress
- Direction
- data.source uses data.generator, so a change to data.generator can break data.source, while a change to data.source can't break data.generator.
- Position
- Below the diagonal: data.source uses a module listed above it, which is the healthy direction.
27→22 data.source uses domain.repository✕
- Connections
- 9 pairs of types, where a type in data.source uses a type in domain.repository.
- The types involved
org.tool.kit.data.source.JvmApkBuildWorkspaces→org.tool.kit.domain.repository.ApkBuildWorkspacesorg.tool.kit.data.source.JvmApkSignerDataSource→org.tool.kit.domain.repository.ApkSigningRepositoryorg.tool.kit.data.source.JvmApkToolDataSource→org.tool.kit.domain.repository.ApkBuildSessionorg.tool.kit.data.source.JvmApkToolDataSource→org.tool.kit.domain.repository.ApkToolRepositoryorg.tool.kit.data.source.JvmBuildCachesDataSource→org.tool.kit.domain.repository.BuildCachesRepositoryorg.tool.kit.data.source.JvmIconOutputs→org.tool.kit.domain.repository.IconOutputSessionorg.tool.kit.data.source.JvmIconOutputs→org.tool.kit.domain.repository.IconOutputsorg.tool.kit.data.source.JvmImageProcessor→org.tool.kit.domain.repository.ImageProcessororg.tool.kit.data.source.JvmJunkCodeDataSource→org.tool.kit.domain.repository.JunkCodeRepository
- Direction
- data.source uses domain.repository, so a change to domain.repository can break data.source, while a change to data.source can't break domain.repository.
- Position
- Below the diagonal: data.source uses a module listed above it, which is the healthy direction.
28→5 domain.usecase uses domain.cleaner✕
- Connections
- 4 pairs of types, where a type in domain.usecase uses a type in domain.cleaner.
- The types involved
org.tool.kit.domain.usecase.DeleteBuildCachesUseCase→org.tool.kit.domain.cleaner.BuildDirectoryorg.tool.kit.domain.usecase.DeleteBuildCachesUseCase→org.tool.kit.domain.cleaner.DeleteBuildCacheResultorg.tool.kit.domain.usecase.ScanBuildCachesUseCase→org.tool.kit.domain.cleaner.BuildDirectoryorg.tool.kit.domain.usecase.ScanBuildCachesUseCase→org.tool.kit.domain.cleaner.CleanerScanRequest
- Direction
- domain.usecase uses domain.cleaner, so a change to domain.cleaner can break domain.usecase, while a change to domain.usecase can't break domain.cleaner.
- Position
- Below the diagonal: domain.usecase uses a module listed above it, which is the healthy direction.
28→6 domain.usecase uses domain.icon✕
- Connections
- 2 pairs of types, where a type in domain.usecase uses a type in domain.icon.
- The types involved
org.tool.kit.domain.usecase.GenerateIconsUseCase→org.tool.kit.domain.icon.GenerateIconsOutcomeorg.tool.kit.domain.usecase.GenerateIconsUseCase→org.tool.kit.domain.icon.GenerateIconsRequest
- Direction
- domain.usecase uses domain.icon, so a change to domain.icon can break domain.usecase, while a change to domain.usecase can't break domain.icon.
- Position
- Below the diagonal: domain.usecase uses a module listed above it, which is the healthy direction.
28→7 domain.usecase uses domain.junk✕
- Connections
- 4 pairs of types, where a type in domain.usecase uses a type in domain.junk.
- The types involved
org.tool.kit.domain.usecase.EstimateJunkSizeUseCase→org.tool.kit.domain.junk.JunkConfigurationorg.tool.kit.domain.usecase.EstimateJunkSizeUseCase→org.tool.kit.domain.junk.JunkSizeEstimateorg.tool.kit.domain.usecase.GenerateJunkCodeUseCase→org.tool.kit.domain.junk.GenerateJunkCodeOutcomeorg.tool.kit.domain.usecase.GenerateJunkCodeUseCase→org.tool.kit.domain.junk.GenerateJunkCodeRequest
- Direction
- domain.usecase uses domain.junk, so a change to domain.junk can break domain.usecase, while a change to domain.usecase can't break domain.junk.
- Position
- Below the diagonal: domain.usecase uses a module listed above it, which is the healthy direction.
28→8 domain.usecase uses domain.keystore✕
- Connections
- 2 pairs of types, where a type in domain.usecase uses a type in domain.keystore.
- The types involved
org.tool.kit.domain.usecase.GenerateKeyStoreUseCase→org.tool.kit.domain.keystore.GenerateKeyStoreOutcomeorg.tool.kit.domain.usecase.GenerateKeyStoreUseCase→org.tool.kit.domain.keystore.GenerateKeyStoreRequest
- Direction
- domain.usecase uses domain.keystore, so a change to domain.keystore can break domain.usecase, while a change to domain.usecase can't break domain.keystore.
- Position
- Below the diagonal: domain.usecase uses a module listed above it, which is the healthy direction.
28→9 domain.usecase uses domain.signature✕
- Connections
- 1 pair of types, where a type in domain.usecase uses a type in domain.signature.
- The types involved
org.tool.kit.domain.usecase.VerifySignatureUseCase→org.tool.kit.domain.signature.SignatureVerification
- Direction
- domain.usecase uses domain.signature, so a change to domain.signature can break domain.usecase, while a change to domain.usecase can't break domain.signature.
- Position
- Below the diagonal: domain.usecase uses a module listed above it, which is the healthy direction.
28→10 domain.usecase uses domain.signing✕
- Connections
- 2 pairs of types, where a type in domain.usecase uses a type in domain.signing.
- The types involved
org.tool.kit.domain.usecase.SignApkUseCase→org.tool.kit.domain.signing.SignApkOutcomeorg.tool.kit.domain.usecase.SignApkUseCase→org.tool.kit.domain.signing.SignApkRequest
- Direction
- domain.usecase uses domain.signing, so a change to domain.signing can break domain.usecase, while a change to domain.usecase can't break domain.signing.
- Position
- Below the diagonal: domain.usecase uses a module listed above it, which is the healthy direction.
28→14 domain.usecase uses domain.apk✕
- Connections
- 3 pairs of types, where a type in domain.usecase uses a type in domain.apk.
- The types involved
org.tool.kit.domain.usecase.BuildApkUseCase→org.tool.kit.domain.apk.BuildApkOutcomeorg.tool.kit.domain.usecase.BuildApkUseCase→org.tool.kit.domain.apk.BuildApkRequestorg.tool.kit.domain.usecase.ReadApkInformationUseCase→org.tool.kit.domain.apk.ApkInformationData
- Direction
- domain.usecase uses domain.apk, so a change to domain.apk can break domain.usecase, while a change to domain.usecase can't break domain.apk.
- Position
- Below the diagonal: domain.usecase uses a module listed above it, which is the healthy direction.
28→22 domain.usecase uses domain.repository✕
- Connections
- 12 pairs of types, where a type in domain.usecase uses a type in domain.repository.
- The types involved
org.tool.kit.domain.usecase.BuildApkUseCase→org.tool.kit.domain.repository.ApkBuildWorkspacesorg.tool.kit.domain.usecase.BuildApkUseCase→org.tool.kit.domain.repository.ApkToolRepositoryorg.tool.kit.domain.usecase.DeleteBuildCachesUseCase→org.tool.kit.domain.repository.BuildCachesRepositoryorg.tool.kit.domain.usecase.EstimateJunkSizeUseCase→org.tool.kit.domain.repository.JunkSizeEstimatororg.tool.kit.domain.usecase.GenerateIconsUseCase→org.tool.kit.domain.repository.IconOutputsorg.tool.kit.domain.usecase.GenerateIconsUseCase→org.tool.kit.domain.repository.ImageProcessororg.tool.kit.domain.usecase.GenerateJunkCodeUseCase→org.tool.kit.domain.repository.JunkCodeRepositoryorg.tool.kit.domain.usecase.GenerateKeyStoreUseCase→org.tool.kit.domain.repository.KeyStoreRepositoryorg.tool.kit.domain.usecase.ReadApkInformationUseCase→org.tool.kit.domain.repository.ApkInformationRepositoryorg.tool.kit.domain.usecase.ScanBuildCachesUseCase→org.tool.kit.domain.repository.BuildCachesRepositoryorg.tool.kit.domain.usecase.SignApkUseCase→org.tool.kit.domain.repository.ApkSigningRepositoryorg.tool.kit.domain.usecase.VerifySignatureUseCase→org.tool.kit.domain.repository.SignatureRepository
- Direction
- domain.usecase uses domain.repository, so a change to domain.repository can break domain.usecase, while a change to domain.usecase can't break domain.repository.
- Position
- Below the diagonal: domain.usecase uses a module listed above it, which is the healthy direction.
29→23 feature.app.UiMessage uses feature.app✕
- Connections
- 2 pairs of types, where a type in feature.app.UiMessage uses a type in feature.app.
- The types involved
org.tool.kit.feature.app.UiMessage.Resource→org.tool.kit.feature.app.UiMessageorg.tool.kit.feature.app.UiMessage.Text→org.tool.kit.feature.app.UiMessage
- Direction
- feature.app.UiMessage uses feature.app, so a change to feature.app can break feature.app.UiMessage, while a change to feature.app.UiMessage can't break feature.app.
- Position
- Below the diagonal: feature.app.UiMessage uses a module listed above it, which is the healthy direction.
30→1 data.repository uses core.coroutine✕
- Connections
- 2 pairs of types, where a type in data.repository uses a type in core.coroutine.
- The types involved
org.tool.kit.data.repository.DefaultPreferencesRepository→org.tool.kit.core.coroutine.AppDispatchersorg.tool.kit.data.repository.JvmUpdateRepository→org.tool.kit.core.coroutine.AppDispatchers
- Direction
- data.repository uses core.coroutine, so a change to core.coroutine can break data.repository, while a change to data.repository can't break core.coroutine.
- Position
- Below the diagonal: data.repository uses a module listed above it, which is the healthy direction.
30→5 data.repository uses domain.cleaner✕
- Connections
- 1 pair of types, where a type in data.repository uses a type in domain.cleaner.
- The types involved
org.tool.kit.data.repository.DefaultCleanerRulesRepository→org.tool.kit.domain.cleaner.CleanerRuleConfig
- Direction
- data.repository uses domain.cleaner, so a change to domain.cleaner can break data.repository, while a change to data.repository can't break domain.cleaner.
- Position
- Below the diagonal: data.repository uses a module listed above it, which is the healthy direction.
30→8 data.repository uses domain.keystore✕
- Connections
- 2 pairs of types, where a type in data.repository uses a type in domain.keystore.
- The types involved
org.tool.kit.data.repository.JvmKeyStoreRepository→org.tool.kit.domain.keystore.GenerateKeyStoreOutcomeorg.tool.kit.data.repository.JvmKeyStoreRepository→org.tool.kit.domain.keystore.GenerateKeyStoreRequest
- Direction
- data.repository uses domain.keystore, so a change to domain.keystore can break data.repository, while a change to data.repository can't break domain.keystore.
- Position
- Below the diagonal: data.repository uses a module listed above it, which is the healthy direction.
30→9 data.repository uses domain.signature✕
- Connections
- 1 pair of types, where a type in data.repository uses a type in domain.signature.
- The types involved
org.tool.kit.data.repository.JvmSignatureRepository→org.tool.kit.domain.signature.SignatureVerification
- Direction
- data.repository uses domain.signature, so a change to domain.signature can break data.repository, while a change to data.repository can't break domain.signature.
- Position
- Below the diagonal: data.repository uses a module listed above it, which is the healthy direction.
30→14 data.repository uses domain.apk✕
- Connections
- 4 pairs of types, where a type in data.repository uses a type in domain.apk.
- The types involved
org.tool.kit.data.repository.JvmApkInformationRepository→org.tool.kit.domain.apk.ApkArchiveInformationorg.tool.kit.data.repository.JvmApkInformationRepository→org.tool.kit.domain.apk.ApkComponentorg.tool.kit.data.repository.JvmApkInformationRepository→org.tool.kit.domain.apk.ApkFileMetadataorg.tool.kit.data.repository.JvmApkInformationRepository→org.tool.kit.domain.apk.ApkIconSource
- Direction
- data.repository uses domain.apk, so a change to domain.apk can break data.repository, while a change to data.repository can't break domain.apk.
- Position
- Below the diagonal: data.repository uses a module listed above it, which is the healthy direction.
30→16 data.repository uses domain.preferences✕
- Connections
- 3 pairs of types, where a type in data.repository uses a type in domain.preferences.
- The types involved
org.tool.kit.data.repository.DefaultPreferencesRepository→org.tool.kit.domain.preferences.PreferenceChangeorg.tool.kit.data.repository.DefaultPreferencesRepository→org.tool.kit.domain.preferences.PreferencesRepositoryorg.tool.kit.data.repository.DefaultPreferencesRepository→org.tool.kit.domain.preferences.PreferencesSnapshot
- Direction
- data.repository uses domain.preferences, so a change to domain.preferences can break data.repository, while a change to data.repository can't break domain.preferences.
- Position
- Below the diagonal: data.repository uses a module listed above it, which is the healthy direction.
30→18 data.repository uses data.repository.DefaultPreferencesRepository✕
- Connections
- 1 pair of types, where a type in data.repository uses a type in data.repository.DefaultPreferencesRepository.
- The types involved
org.tool.kit.data.repository.DefaultPreferencesRepository→org.tool.kit.data.repository.DefaultPreferencesRepository.Write
- Direction
- data.repository uses data.repository.DefaultPreferencesRepository, so a change to data.repository.DefaultPreferencesRepository can break data.repository, while a change to data.repository can't break data.repository.DefaultPreferencesRepository.
- Position
- Below the diagonal: data.repository uses a module listed above it, which is the healthy direction.
30→22 data.repository uses domain.repository✕
- Connections
- 13 pairs of types, where a type in data.repository uses a type in domain.repository.
- The types involved
org.tool.kit.data.repository.DefaultCleanerRulesRepository→org.tool.kit.domain.repository.CleanerRuleConfigSnapshotorg.tool.kit.data.repository.DefaultCleanerRulesRepository→org.tool.kit.domain.repository.CleanerRulesRepositoryorg.tool.kit.data.repository.JvmApkInformationRepository→org.tool.kit.domain.repository.ApkInformationRepositoryorg.tool.kit.data.repository.JvmKeyStoreRepository→org.tool.kit.domain.repository.KeyStoreRepositoryorg.tool.kit.data.repository.JvmSignatureRepository→org.tool.kit.domain.repository.SignatureRepositoryorg.tool.kit.data.repository.JvmStorageRepository→org.tool.kit.domain.repository.PathMetadataorg.tool.kit.data.repository.JvmStorageRepository→org.tool.kit.domain.repository.StorageCapacityorg.tool.kit.data.repository.JvmStorageRepository→org.tool.kit.domain.repository.StorageRepositoryorg.tool.kit.data.repository.JvmUpdateRepository→org.tool.kit.domain.repository.UpdateAssetorg.tool.kit.data.repository.JvmUpdateRepository→org.tool.kit.domain.repository.UpdateCheckResultorg.tool.kit.data.repository.JvmUpdateRepository→org.tool.kit.domain.repository.UpdateDownloadResultorg.tool.kit.data.repository.JvmUpdateRepository→org.tool.kit.domain.repository.UpdateErrororg.tool.kit.data.repository.JvmUpdateRepository→org.tool.kit.domain.repository.UpdateRepository
- Direction
- data.repository uses domain.repository, so a change to domain.repository can break data.repository, while a change to data.repository can't break domain.repository.
- Position
- Below the diagonal: data.repository uses a module listed above it, which is the healthy direction.
30→27 data.repository uses data.source✕
- Connections
- 4 pairs of types, where a type in data.repository uses a type in data.source.
- The types involved
org.tool.kit.data.repository.DefaultPreferencesRepository→org.tool.kit.data.source.PreferencesStorageorg.tool.kit.data.repository.JvmApkInformationRepository→org.tool.kit.data.source.Aapt2DataSourceorg.tool.kit.data.repository.JvmApkInformationRepository→org.tool.kit.data.source.ApkIconDataSourceorg.tool.kit.data.repository.JvmKeyStoreRepository→org.tool.kit.data.source.JvmKeyStoreDataSource
- Direction
- data.repository uses data.source, so a change to data.source can break data.repository, while a change to data.repository can't break data.source.
- Position
- Below the diagonal: data.repository uses a module listed above it, which is the healthy direction.
31→5 feature.cleaner uses domain.cleaner✕
- Connections
- 19 pairs of types, where a type in feature.cleaner uses a type in domain.cleaner.
- The types involved
org.tool.kit.feature.cleaner.CleanerConditionRow→org.tool.kit.domain.cleaner.CleanerConditionorg.tool.kit.feature.cleaner.CleanerItemUi→org.tool.kit.domain.cleaner.BuildDirectoryorg.tool.kit.feature.cleaner.CleanerRuleConditionEditorKt→org.tool.kit.domain.cleaner.CleanerConditionorg.tool.kit.feature.cleaner.CleanerRuleConditionEditorKt→org.tool.kit.domain.cleaner.CleanerRuleIssueorg.tool.kit.feature.cleaner.CleanerRuleConditionEditorKt→org.tool.kit.domain.cleaner.CleanerTargetorg.tool.kit.feature.cleaner.CleanerRuleLabelsKt→org.tool.kit.domain.cleaner.CleanerConditionorg.tool.kit.feature.cleaner.CleanerRuleLabelsKt→org.tool.kit.domain.cleaner.CleanerRuleGrouporg.tool.kit.feature.cleaner.CleanerRuleLabelsKt→org.tool.kit.domain.cleaner.CleanerRuleIssueorg.tool.kit.feature.cleaner.CleanerRuleLabelsKt→org.tool.kit.domain.cleaner.CleanerTargetorg.tool.kit.feature.cleaner.CleanerRuleLabelsKt→org.tool.kit.domain.cleaner.TextOperatororg.tool.kit.feature.cleaner.CleanerRulesScreenKt→org.tool.kit.domain.cleaner.CleanerRuleGrouporg.tool.kit.feature.cleaner.CleanerRulesUiState→org.tool.kit.domain.cleaner.CleanerRuleConfigorg.tool.kit.feature.cleaner.CleanerRulesUiState→org.tool.kit.domain.cleaner.CleanerRuleValidationorg.tool.kit.feature.cleaner.CleanerRulesViewModel→org.tool.kit.domain.cleaner.CleanerConditionorg.tool.kit.feature.cleaner.CleanerRulesViewModel→org.tool.kit.domain.cleaner.CleanerRuleConfigorg.tool.kit.feature.cleaner.CleanerRulesViewModel→org.tool.kit.domain.cleaner.CleanerRuleGrouporg.tool.kit.feature.cleaner.CleanerRulesViewModelKt→org.tool.kit.domain.cleaner.CleanerRuleConfigorg.tool.kit.feature.cleaner.CleanerStateKt→org.tool.kit.domain.cleaner.BuildDirectoryorg.tool.kit.feature.cleaner.CleanerUiState→org.tool.kit.domain.cleaner.CleanerRuleConfig
- Direction
- feature.cleaner uses domain.cleaner, so a change to domain.cleaner can break feature.cleaner, while a change to feature.cleaner can't break domain.cleaner.
- Position
- Below the diagonal: feature.cleaner uses a module listed above it, which is the healthy direction.
31→11 feature.cleaner uses model✕
- Connections
- 3 pairs of types, where a type in feature.cleaner uses a type in model.
- The types involved
org.tool.kit.feature.cleaner.CleanerScreenKt→org.tool.kit.model.Sequenceorg.tool.kit.feature.cleaner.CleanerStateKt→org.tool.kit.model.Sequenceorg.tool.kit.feature.cleaner.CleanerUiState→org.tool.kit.model.Sequence
- Direction
- feature.cleaner uses model, so a change to model can break feature.cleaner, while a change to feature.cleaner can't break model.
- Position
- Below the diagonal: feature.cleaner uses a module listed above it, which is the healthy direction.
31→22 feature.cleaner uses domain.repository✕
- Connections
- 5 pairs of types, where a type in feature.cleaner uses a type in domain.repository.
- The types involved
org.tool.kit.feature.cleaner.CleanerRulesViewModel→org.tool.kit.domain.repository.CleanerRulesRepositoryorg.tool.kit.feature.cleaner.CleanerUiState→org.tool.kit.domain.repository.StorageCapacityorg.tool.kit.feature.cleaner.CleanerViewModel→org.tool.kit.domain.repository.CleanerRulesRepositoryorg.tool.kit.feature.cleaner.CleanerViewModel→org.tool.kit.domain.repository.StorageCapacityorg.tool.kit.feature.cleaner.CleanerViewModel→org.tool.kit.domain.repository.StorageRepository
- Direction
- feature.cleaner uses domain.repository, so a change to domain.repository can break feature.cleaner, while a change to feature.cleaner can't break domain.repository.
- Position
- Below the diagonal: feature.cleaner uses a module listed above it, which is the healthy direction.
31→23 feature.cleaner uses feature.app✕
- Connections
- 1 pair of types, where a type in feature.cleaner uses a type in feature.app.
- The types involved
org.tool.kit.feature.cleaner.CleanerViewModel→org.tool.kit.feature.app.AppEffectSink
- Direction
- feature.cleaner uses feature.app, so a change to feature.app can break feature.cleaner, while a change to feature.cleaner can't break feature.app.
- Position
- Below the diagonal: feature.cleaner uses a module listed above it, which is the healthy direction.
31→25 feature.cleaner uses core.validation✕
- Connections
- 1 pair of types, where a type in feature.cleaner uses a type in core.validation.
- The types involved
org.tool.kit.feature.cleaner.CleanerViewModel→org.tool.kit.core.validation.LatestRequest
- Direction
- feature.cleaner uses core.validation, so a change to core.validation can break feature.cleaner, while a change to feature.cleaner can't break core.validation.
- Position
- Below the diagonal: feature.cleaner uses a module listed above it, which is the healthy direction.
31→28 feature.cleaner uses domain.usecase✕
- Connections
- 2 pairs of types, where a type in feature.cleaner uses a type in domain.usecase.
- The types involved
org.tool.kit.feature.cleaner.CleanerViewModel→org.tool.kit.domain.usecase.DeleteBuildCachesUseCaseorg.tool.kit.feature.cleaner.CleanerViewModel→org.tool.kit.domain.usecase.ScanBuildCachesUseCase
- Direction
- feature.cleaner uses domain.usecase, so a change to domain.usecase can break feature.cleaner, while a change to feature.cleaner can't break domain.usecase.
- Position
- Below the diagonal: feature.cleaner uses a module listed above it, which is the healthy direction.
32→11 feature.iconfactory uses model✕
- Connections
- 3 pairs of types, where a type in feature.iconfactory uses a type in model.
- The types involved
org.tool.kit.feature.iconfactory.IconFactoryScreenKt→org.tool.kit.model.IconFactoryDataorg.tool.kit.feature.iconfactory.IconFactoryUiState→org.tool.kit.model.IconFactoryDataorg.tool.kit.feature.iconfactory.IconSettingsReducer→org.tool.kit.model.IconFactoryData
- Direction
- feature.iconfactory uses model, so a change to model can break feature.iconfactory, while a change to feature.iconfactory can't break model.
- Position
- Below the diagonal: feature.iconfactory uses a module listed above it, which is the healthy direction.
32→16 feature.iconfactory uses domain.preferences✕
- Connections
- 2 pairs of types, where a type in feature.iconfactory uses a type in domain.preferences.
- The types involved
org.tool.kit.feature.iconfactory.IconFactoryViewModel→org.tool.kit.domain.preferences.PreferencesRepositoryorg.tool.kit.feature.iconfactory.IconFactoryViewModel→org.tool.kit.domain.preferences.PreferencesSnapshot
- Direction
- feature.iconfactory uses domain.preferences, so a change to domain.preferences can break feature.iconfactory, while a change to feature.iconfactory can't break domain.preferences.
- Position
- Below the diagonal: feature.iconfactory uses a module listed above it, which is the healthy direction.
32→22 feature.iconfactory uses domain.repository✕
- Connections
- 1 pair of types, where a type in feature.iconfactory uses a type in domain.repository.
- The types involved
org.tool.kit.feature.iconfactory.IconFactoryViewModel→org.tool.kit.domain.repository.StorageRepository
- Direction
- feature.iconfactory uses domain.repository, so a change to domain.repository can break feature.iconfactory, while a change to feature.iconfactory can't break domain.repository.
- Position
- Below the diagonal: feature.iconfactory uses a module listed above it, which is the healthy direction.
32→23 feature.iconfactory uses feature.app✕
- Connections
- 1 pair of types, where a type in feature.iconfactory uses a type in feature.app.
- The types involved
org.tool.kit.feature.iconfactory.IconFactoryViewModel→org.tool.kit.feature.app.AppEffectSink
- Direction
- feature.iconfactory uses feature.app, so a change to feature.app can break feature.iconfactory, while a change to feature.iconfactory can't break feature.app.
- Position
- Below the diagonal: feature.iconfactory uses a module listed above it, which is the healthy direction.
32→25 feature.iconfactory uses core.validation✕
- Connections
- 1 pair of types, where a type in feature.iconfactory uses a type in core.validation.
- The types involved
org.tool.kit.feature.iconfactory.IconFactoryViewModel→org.tool.kit.core.validation.LatestRequest
- Direction
- feature.iconfactory uses core.validation, so a change to core.validation can break feature.iconfactory, while a change to feature.iconfactory can't break core.validation.
- Position
- Below the diagonal: feature.iconfactory uses a module listed above it, which is the healthy direction.
32→28 feature.iconfactory uses domain.usecase✕
- Connections
- 1 pair of types, where a type in feature.iconfactory uses a type in domain.usecase.
- The types involved
org.tool.kit.feature.iconfactory.IconFactoryViewModel→org.tool.kit.domain.usecase.GenerateIconsUseCase
- Direction
- feature.iconfactory uses domain.usecase, so a change to domain.usecase can break feature.iconfactory, while a change to feature.iconfactory can't break domain.usecase.
- Position
- Below the diagonal: feature.iconfactory uses a module listed above it, which is the healthy direction.
33→7 feature.junk uses domain.junk✕
- Connections
- 1 pair of types, where a type in feature.junk uses a type in domain.junk.
- The types involved
org.tool.kit.feature.junk.JunkCodeStateKt→org.tool.kit.domain.junk.JunkConfiguration
- Direction
- feature.junk uses domain.junk, so a change to domain.junk can break feature.junk, while a change to feature.junk can't break domain.junk.
- Position
- Below the diagonal: feature.junk uses a module listed above it, which is the healthy direction.
33→11 feature.junk uses model✕
- Connections
- 2 pairs of types, where a type in feature.junk uses a type in model.
- The types involved
org.tool.kit.feature.junk.JunkCodeScreenKt→org.tool.kit.model.JunkModeorg.tool.kit.feature.junk.JunkCodeUiState→org.tool.kit.model.JunkMode
- Direction
- feature.junk uses model, so a change to model can break feature.junk, while a change to feature.junk can't break model.
- Position
- Below the diagonal: feature.junk uses a module listed above it, which is the healthy direction.
33→16 feature.junk uses domain.preferences✕
- Connections
- 2 pairs of types, where a type in feature.junk uses a type in domain.preferences.
- The types involved
org.tool.kit.feature.junk.JunkCodeViewModel→org.tool.kit.domain.preferences.PreferencesRepositoryorg.tool.kit.feature.junk.JunkCodeViewModel→org.tool.kit.domain.preferences.PreferencesSnapshot
- Direction
- feature.junk uses domain.preferences, so a change to domain.preferences can break feature.junk, while a change to feature.junk can't break domain.preferences.
- Position
- Below the diagonal: feature.junk uses a module listed above it, which is the healthy direction.
33→22 feature.junk uses domain.repository✕
- Connections
- 3 pairs of types, where a type in feature.junk uses a type in domain.repository.
- The types involved
org.tool.kit.feature.junk.JunkCodeViewModel→org.tool.kit.domain.repository.JunkTokenGeneratororg.tool.kit.feature.junk.JunkCodeViewModel→org.tool.kit.domain.repository.StorageRepositoryorg.tool.kit.feature.junk.JunkOutputValidation→org.tool.kit.domain.repository.StorageRepository
- Direction
- feature.junk uses domain.repository, so a change to domain.repository can break feature.junk, while a change to feature.junk can't break domain.repository.
- Position
- Below the diagonal: feature.junk uses a module listed above it, which is the healthy direction.
33→23 feature.junk uses feature.app✕
- Connections
- 1 pair of types, where a type in feature.junk uses a type in feature.app.
- The types involved
org.tool.kit.feature.junk.JunkCodeViewModel→org.tool.kit.feature.app.AppEffectSink
- Direction
- feature.junk uses feature.app, so a change to feature.app can break feature.junk, while a change to feature.junk can't break feature.app.
- Position
- Below the diagonal: feature.junk uses a module listed above it, which is the healthy direction.
33→25 feature.junk uses core.validation✕
- Connections
- 1 pair of types, where a type in feature.junk uses a type in core.validation.
- The types involved
org.tool.kit.feature.junk.JunkOutputValidation→org.tool.kit.core.validation.LatestRequest
- Direction
- feature.junk uses core.validation, so a change to core.validation can break feature.junk, while a change to feature.junk can't break core.validation.
- Position
- Below the diagonal: feature.junk uses a module listed above it, which is the healthy direction.
33→28 feature.junk uses domain.usecase✕
- Connections
- 2 pairs of types, where a type in feature.junk uses a type in domain.usecase.
- The types involved
org.tool.kit.feature.junk.JunkCodeViewModel→org.tool.kit.domain.usecase.EstimateJunkSizeUseCaseorg.tool.kit.feature.junk.JunkCodeViewModel→org.tool.kit.domain.usecase.GenerateJunkCodeUseCase
- Direction
- feature.junk uses domain.usecase, so a change to domain.usecase can break feature.junk, while a change to feature.junk can't break domain.usecase.
- Position
- Below the diagonal: feature.junk uses a module listed above it, which is the healthy direction.
34→16 feature.keystore uses domain.preferences✕
- Connections
- 2 pairs of types, where a type in feature.keystore uses a type in domain.preferences.
- The types involved
org.tool.kit.feature.keystore.KeyStoreGenerationViewModel→org.tool.kit.domain.preferences.PreferencesRepositoryorg.tool.kit.feature.keystore.KeyStoreGenerationViewModel→org.tool.kit.domain.preferences.PreferencesSnapshot
- Direction
- feature.keystore uses domain.preferences, so a change to domain.preferences can break feature.keystore, while a change to feature.keystore can't break domain.preferences.
- Position
- Below the diagonal: feature.keystore uses a module listed above it, which is the healthy direction.
34→22 feature.keystore uses domain.repository✕
- Connections
- 1 pair of types, where a type in feature.keystore uses a type in domain.repository.
- The types involved
org.tool.kit.feature.keystore.KeyStoreGenerationViewModel→org.tool.kit.domain.repository.StorageRepository
- Direction
- feature.keystore uses domain.repository, so a change to domain.repository can break feature.keystore, while a change to feature.keystore can't break domain.repository.
- Position
- Below the diagonal: feature.keystore uses a module listed above it, which is the healthy direction.
34→23 feature.keystore uses feature.app✕
- Connections
- 2 pairs of types, where a type in feature.keystore uses a type in feature.app.
- The types involved
org.tool.kit.feature.keystore.KeyStoreGenerationViewModel→org.tool.kit.feature.app.AppEffectSinkorg.tool.kit.feature.keystore.KeyStoreGenerationViewModel→org.tool.kit.feature.app.UiMessage
- Direction
- feature.keystore uses feature.app, so a change to feature.app can break feature.keystore, while a change to feature.keystore can't break feature.app.
- Position
- Below the diagonal: feature.keystore uses a module listed above it, which is the healthy direction.
34→25 feature.keystore uses core.validation✕
- Connections
- 1 pair of types, where a type in feature.keystore uses a type in core.validation.
- The types involved
org.tool.kit.feature.keystore.KeyStoreGenerationViewModel→org.tool.kit.core.validation.LatestRequest
- Direction
- feature.keystore uses core.validation, so a change to core.validation can break feature.keystore, while a change to feature.keystore can't break core.validation.
- Position
- Below the diagonal: feature.keystore uses a module listed above it, which is the healthy direction.
34→28 feature.keystore uses domain.usecase✕
- Connections
- 1 pair of types, where a type in feature.keystore uses a type in domain.usecase.
- The types involved
org.tool.kit.feature.keystore.KeyStoreGenerationViewModel→org.tool.kit.domain.usecase.GenerateKeyStoreUseCase
- Direction
- feature.keystore uses domain.usecase, so a change to domain.usecase can break feature.keystore, while a change to feature.keystore can't break domain.usecase.
- Position
- Below the diagonal: feature.keystore uses a module listed above it, which is the healthy direction.
35→9 feature.signature uses domain.signature✕
- Connections
- 3 pairs of types, where a type in feature.signature uses a type in domain.signature.
- The types involved
org.tool.kit.feature.signature.SignatureInformationScreenKt→org.tool.kit.domain.signature.CertificateInformationorg.tool.kit.feature.signature.SignatureInformationViewModel→org.tool.kit.domain.signature.SignatureVerificationorg.tool.kit.feature.signature.VerifierResultUi→org.tool.kit.domain.signature.CertificateInformation
- Direction
- feature.signature uses domain.signature, so a change to domain.signature can break feature.signature, while a change to feature.signature can't break domain.signature.
- Position
- Below the diagonal: feature.signature uses a module listed above it, which is the healthy direction.
35→11 feature.signature uses model✕
- Connections
- 4 pairs of types, where a type in feature.signature uses a type in model.
- The types involved
org.tool.kit.feature.signature.ApkSignatureForm→org.tool.kit.model.SignaturePolicyorg.tool.kit.feature.signature.ApkSigningScreenKt→org.tool.kit.model.SignaturePolicyorg.tool.kit.feature.signature.SignatureInformationScreenKt→org.tool.kit.model.CopyModeorg.tool.kit.feature.signature.SignatureInformationUiState→org.tool.kit.model.CopyMode
- Direction
- feature.signature uses model, so a change to model can break feature.signature, while a change to feature.signature can't break model.
- Position
- Below the diagonal: feature.signature uses a module listed above it, which is the healthy direction.
35→16 feature.signature uses domain.preferences✕
- Connections
- 3 pairs of types, where a type in feature.signature uses a type in domain.preferences.
- The types involved
org.tool.kit.feature.signature.ApkSigningViewModel→org.tool.kit.domain.preferences.PreferencesRepositoryorg.tool.kit.feature.signature.ApkSigningViewModel→org.tool.kit.domain.preferences.PreferencesSnapshotorg.tool.kit.feature.signature.SignatureInformationViewModel→org.tool.kit.domain.preferences.PreferencesRepository
- Direction
- feature.signature uses domain.preferences, so a change to domain.preferences can break feature.signature, while a change to feature.signature can't break domain.preferences.
- Position
- Below the diagonal: feature.signature uses a module listed above it, which is the healthy direction.
35→22 feature.signature uses domain.repository✕
- Connections
- 5 pairs of types, where a type in feature.signature uses a type in domain.repository.
- The types involved
org.tool.kit.feature.signature.ApkSigningViewModel→org.tool.kit.domain.repository.KeyStoreRepositoryorg.tool.kit.feature.signature.ApkSigningViewModel→org.tool.kit.domain.repository.StorageRepositoryorg.tool.kit.feature.signature.SignatureInformationViewModel→org.tool.kit.domain.repository.KeyStoreRepositoryorg.tool.kit.feature.signature.SigningCredentialsValidation→org.tool.kit.domain.repository.KeyStoreRepositoryorg.tool.kit.feature.signature.SigningCredentialsValidation→org.tool.kit.domain.repository.StorageRepository
- Direction
- feature.signature uses domain.repository, so a change to domain.repository can break feature.signature, while a change to feature.signature can't break domain.repository.
- Position
- Below the diagonal: feature.signature uses a module listed above it, which is the healthy direction.
35→23 feature.signature uses feature.app✕
- Connections
- 5 pairs of types, where a type in feature.signature uses a type in feature.app.
- The types involved
org.tool.kit.feature.signature.ApkSigningViewModel→org.tool.kit.feature.app.AppEffectSinkorg.tool.kit.feature.signature.ApkSigningViewModel→org.tool.kit.feature.app.UiMessageorg.tool.kit.feature.signature.SignatureInformationViewModel→org.tool.kit.feature.app.AppEffectSinkorg.tool.kit.feature.signature.SignatureInformationViewModel→org.tool.kit.feature.app.ClipboardWriterorg.tool.kit.feature.signature.SignatureInformationViewModel→org.tool.kit.feature.app.UiMessage
- Direction
- feature.signature uses feature.app, so a change to feature.app can break feature.signature, while a change to feature.signature can't break feature.app.
- Position
- Below the diagonal: feature.signature uses a module listed above it, which is the healthy direction.
35→25 feature.signature uses core.validation✕
- Connections
- 4 pairs of types, where a type in feature.signature uses a type in core.validation.
- The types involved
org.tool.kit.feature.signature.ApkSigningViewModel→org.tool.kit.core.validation.LatestRequestorg.tool.kit.feature.signature.SignatureInformationViewModel→org.tool.kit.core.validation.KeyAliasesValidationorg.tool.kit.feature.signature.SignatureInformationViewModel→org.tool.kit.core.validation.LatestRequestorg.tool.kit.feature.signature.SigningCredentialsValidation→org.tool.kit.core.validation.LatestRequest
- Direction
- feature.signature uses core.validation, so a change to core.validation can break feature.signature, while a change to feature.signature can't break core.validation.
- Position
- Below the diagonal: feature.signature uses a module listed above it, which is the healthy direction.
35→28 feature.signature uses domain.usecase✕
- Connections
- 2 pairs of types, where a type in feature.signature uses a type in domain.usecase.
- The types involved
org.tool.kit.feature.signature.ApkSigningViewModel→org.tool.kit.domain.usecase.SignApkUseCaseorg.tool.kit.feature.signature.SignatureInformationViewModel→org.tool.kit.domain.usecase.VerifySignatureUseCase
- Direction
- feature.signature uses domain.usecase, so a change to domain.usecase can break feature.signature, while a change to feature.signature can't break domain.usecase.
- Position
- Below the diagonal: feature.signature uses a module listed above it, which is the healthy direction.
36→1 feature.update uses core.coroutine✕
- Connections
- 1 pair of types, where a type in feature.update uses a type in core.coroutine.
- The types involved
org.tool.kit.feature.update.UpdateViewModel→org.tool.kit.core.coroutine.AppDispatchers
- Direction
- feature.update uses core.coroutine, so a change to core.coroutine can break feature.update, while a change to feature.update can't break core.coroutine.
- Position
- Below the diagonal: feature.update uses a module listed above it, which is the healthy direction.
36→16 feature.update uses domain.preferences✕
- Connections
- 1 pair of types, where a type in feature.update uses a type in domain.preferences.
- The types involved
org.tool.kit.feature.update.UpdateViewModel→org.tool.kit.domain.preferences.PreferencesRepository
- Direction
- feature.update uses domain.preferences, so a change to domain.preferences can break feature.update, while a change to feature.update can't break domain.preferences.
- Position
- Below the diagonal: feature.update uses a module listed above it, which is the healthy direction.
36→22 feature.update uses domain.repository✕
- Connections
- 6 pairs of types, where a type in feature.update uses a type in domain.repository.
- The types involved
org.tool.kit.feature.update.UpdateDialogKt→org.tool.kit.domain.repository.UpdateAssetorg.tool.kit.feature.update.UpdateDialogKt→org.tool.kit.domain.repository.UpdateReleaseorg.tool.kit.feature.update.UpdateUiState→org.tool.kit.domain.repository.UpdateAssetorg.tool.kit.feature.update.UpdateUiState→org.tool.kit.domain.repository.UpdateReleaseorg.tool.kit.feature.update.UpdateViewModel→org.tool.kit.domain.repository.UpdateErrororg.tool.kit.feature.update.UpdateViewModel→org.tool.kit.domain.repository.UpdateRepository
- Direction
- feature.update uses domain.repository, so a change to domain.repository can break feature.update, while a change to feature.update can't break domain.repository.
- Position
- Below the diagonal: feature.update uses a module listed above it, which is the healthy direction.
36→23 feature.update uses feature.app✕
- Connections
- 3 pairs of types, where a type in feature.update uses a type in feature.app.
- The types involved
org.tool.kit.feature.update.UpdateRouteKt→org.tool.kit.feature.app.DesktopActionHandlerorg.tool.kit.feature.update.UpdateViewModel→org.tool.kit.feature.app.AppEffectSinkorg.tool.kit.feature.update.UpdateViewModel→org.tool.kit.feature.app.UiMessage
- Direction
- feature.update uses feature.app, so a change to feature.app can break feature.update, while a change to feature.update can't break feature.app.
- Position
- Below the diagonal: feature.update uses a module listed above it, which is the healthy direction.
36→29 feature.update uses feature.app.UiMessage✕
- Connections
- 1 pair of types, where a type in feature.update uses a type in feature.app.UiMessage.
- The types involved
org.tool.kit.feature.update.UpdateViewModel→org.tool.kit.feature.app.UiMessage.Resource
- Direction
- feature.update uses feature.app.UiMessage, so a change to feature.app.UiMessage can break feature.update, while a change to feature.update can't break feature.app.UiMessage.
- Position
- Below the diagonal: feature.update uses a module listed above it, which is the healthy direction.
37→23 org.tool.kit uses feature.app✕
- Connections
- 3 pairs of types, where a type in org.tool.kit uses a type in feature.app.
- The types involved
org.tool.kit.AppKt→org.tool.kit.feature.app.AppEffectSinkorg.tool.kit.AppKt→org.tool.kit.feature.app.AppUiStateorg.tool.kit.AppKt→org.tool.kit.feature.app.DesktopActionHandler
- Direction
- org.tool.kit uses feature.app, so a change to feature.app can break org.tool.kit, while a change to org.tool.kit can't break feature.app.
- Position
- Below the diagonal: org.tool.kit uses a module listed above it, which is the healthy direction.
37→36 org.tool.kit uses feature.update✕
- Connections
- 1 pair of types, where a type in org.tool.kit uses a type in feature.update.
- The types involved
org.tool.kit.AppKt→org.tool.kit.feature.update.UpdateViewModel
- Direction
- org.tool.kit uses feature.update, so a change to feature.update can break org.tool.kit, while a change to org.tool.kit can't break feature.update.
- Position
- Below the diagonal: org.tool.kit uses a module listed above it, which is the healthy direction.
38→11 feature.apk uses model✕
- Connections
- 1 pair of types, where a type in feature.apk uses a type in model.
- The types involved
org.tool.kit.feature.apk.ApkToolForm→org.tool.kit.model.SignaturePolicy
- Direction
- feature.apk uses model, so a change to model can break feature.apk, while a change to feature.apk can't break model.
- Position
- Below the diagonal: feature.apk uses a module listed above it, which is the healthy direction.
38→14 feature.apk uses domain.apk✕
- Connections
- 10 pairs of types, where a type in feature.apk uses a type in domain.apk.
- The types involved
org.tool.kit.feature.apk.ApkComponentPageKt→org.tool.kit.domain.apk.ApkComponentorg.tool.kit.feature.apk.ApkContentsPageKt→org.tool.kit.domain.apk.ApkAlignmentorg.tool.kit.feature.apk.ApkContentsPageKt→org.tool.kit.domain.apk.ApkExportedDeclarationorg.tool.kit.feature.apk.ApkContentsPageKt→org.tool.kit.domain.apk.ApkFileCategoryorg.tool.kit.feature.apk.ApkIconDecoder→org.tool.kit.domain.apk.ApkIconSourceorg.tool.kit.feature.apk.ApkInformationResultUi→org.tool.kit.domain.apk.ApkArchiveInformationorg.tool.kit.feature.apk.ApkInformationResultUi→org.tool.kit.domain.apk.ApkComponentorg.tool.kit.feature.apk.ApkLibraryPageKt→org.tool.kit.domain.apk.ApkAlignmentorg.tool.kit.feature.apk.ApkLibraryPageKt→org.tool.kit.domain.apk.ApkNativeLibraryorg.tool.kit.feature.apk.ApkPackagePageKt→org.tool.kit.domain.apk.ApkArchiveInformation
- Direction
- feature.apk uses domain.apk, so a change to domain.apk can break feature.apk, while a change to feature.apk can't break domain.apk.
- Position
- Below the diagonal: feature.apk uses a module listed above it, which is the healthy direction.
38→16 feature.apk uses domain.preferences✕
- Connections
- 2 pairs of types, where a type in feature.apk uses a type in domain.preferences.
- The types involved
org.tool.kit.feature.apk.ApkToolViewModel→org.tool.kit.domain.preferences.PreferencesRepositoryorg.tool.kit.feature.apk.ApkToolViewModel→org.tool.kit.domain.preferences.PreferencesSnapshot
- Direction
- feature.apk uses domain.preferences, so a change to domain.preferences can break feature.apk, while a change to feature.apk can't break domain.preferences.
- Position
- Below the diagonal: feature.apk uses a module listed above it, which is the healthy direction.
38→22 feature.apk uses domain.repository✕
- Connections
- 2 pairs of types, where a type in feature.apk uses a type in domain.repository.
- The types involved
org.tool.kit.feature.apk.ApkToolViewModel→org.tool.kit.domain.repository.KeyStoreRepositoryorg.tool.kit.feature.apk.ApkToolViewModel→org.tool.kit.domain.repository.StorageRepository
- Direction
- feature.apk uses domain.repository, so a change to domain.repository can break feature.apk, while a change to feature.apk can't break domain.repository.
- Position
- Below the diagonal: feature.apk uses a module listed above it, which is the healthy direction.
38→23 feature.apk uses feature.app✕
- Connections
- 4 pairs of types, where a type in feature.apk uses a type in feature.app.
- The types involved
org.tool.kit.feature.apk.ApkInformationViewModel→org.tool.kit.feature.app.AppEffectSinkorg.tool.kit.feature.apk.ApkInformationViewModel→org.tool.kit.feature.app.ClipboardWriterorg.tool.kit.feature.apk.ApkToolViewModel→org.tool.kit.feature.app.AppEffectSinkorg.tool.kit.feature.apk.ApkToolViewModel→org.tool.kit.feature.app.UiMessage
- Direction
- feature.apk uses feature.app, so a change to feature.app can break feature.apk, while a change to feature.apk can't break feature.app.
- Position
- Below the diagonal: feature.apk uses a module listed above it, which is the healthy direction.
38→25 feature.apk uses core.validation✕
- Connections
- 2 pairs of types, where a type in feature.apk uses a type in core.validation.
- The types involved
org.tool.kit.feature.apk.ApkInformationViewModel→org.tool.kit.core.validation.LatestRequestorg.tool.kit.feature.apk.ApkToolViewModel→org.tool.kit.core.validation.LatestRequest
- Direction
- feature.apk uses core.validation, so a change to core.validation can break feature.apk, while a change to feature.apk can't break core.validation.
- Position
- Below the diagonal: feature.apk uses a module listed above it, which is the healthy direction.
38→28 feature.apk uses domain.usecase✕
- Connections
- 2 pairs of types, where a type in feature.apk uses a type in domain.usecase.
- The types involved
org.tool.kit.feature.apk.ApkInformationViewModel→org.tool.kit.domain.usecase.ReadApkInformationUseCaseorg.tool.kit.feature.apk.ApkToolViewModel→org.tool.kit.domain.usecase.BuildApkUseCase
- Direction
- feature.apk uses domain.usecase, so a change to domain.usecase can break feature.apk, while a change to feature.apk can't break domain.usecase.
- Position
- Below the diagonal: feature.apk uses a module listed above it, which is the healthy direction.
38→35 feature.apk uses feature.signature✕
- Connections
- 4 pairs of types, where a type in feature.apk uses a type in feature.signature.
- The types involved
org.tool.kit.feature.apk.ApkToolForm→org.tool.kit.feature.signature.SigningCredentialsUiorg.tool.kit.feature.apk.ApkToolFormReducer→org.tool.kit.feature.signature.SigningCredentialsUiorg.tool.kit.feature.apk.ApkToolValidation→org.tool.kit.feature.signature.SignValidationStateorg.tool.kit.feature.apk.ApkToolViewModel→org.tool.kit.feature.signature.SigningCredentialsValidation
- Direction
- feature.apk uses feature.signature, so a change to feature.signature can break feature.apk, while a change to feature.apk can't break feature.signature.
- Position
- Below the diagonal: feature.apk uses a module listed above it, which is the healthy direction.
39→16 feature.setting uses domain.preferences✕
- Connections
- 2 pairs of types, where a type in feature.setting uses a type in domain.preferences.
- The types involved
org.tool.kit.feature.setting.SettingsUiState→org.tool.kit.domain.preferences.PreferencesSnapshotorg.tool.kit.feature.setting.SettingsViewModel→org.tool.kit.domain.preferences.PreferencesRepository
- Direction
- feature.setting uses domain.preferences, so a change to domain.preferences can break feature.setting, while a change to feature.setting can't break domain.preferences.
- Position
- Below the diagonal: feature.setting uses a module listed above it, which is the healthy direction.
39→22 feature.setting uses domain.repository✕
- Connections
- 1 pair of types, where a type in feature.setting uses a type in domain.repository.
- The types involved
org.tool.kit.feature.setting.SettingsViewModel→org.tool.kit.domain.repository.StorageRepository
- Direction
- feature.setting uses domain.repository, so a change to domain.repository can break feature.setting, while a change to feature.setting can't break domain.repository.
- Position
- Below the diagonal: feature.setting uses a module listed above it, which is the healthy direction.
39→23 feature.setting uses feature.app✕
- Connections
- 3 pairs of types, where a type in feature.setting uses a type in feature.app.
- The types involved
org.tool.kit.feature.setting.SettingsRouteKt→org.tool.kit.feature.app.DesktopActionHandlerorg.tool.kit.feature.setting.SettingsViewModel→org.tool.kit.feature.app.AppEffectSinkorg.tool.kit.feature.setting.SettingsViewModel→org.tool.kit.feature.app.DesktopActionHandler
- Direction
- feature.setting uses feature.app, so a change to feature.app can break feature.setting, while a change to feature.setting can't break feature.app.
- Position
- Below the diagonal: feature.setting uses a module listed above it, which is the healthy direction.
39→25 feature.setting uses core.validation✕
- Connections
- 1 pair of types, where a type in feature.setting uses a type in core.validation.
- The types involved
org.tool.kit.feature.setting.SettingsViewModel→org.tool.kit.core.validation.LatestRequest
- Direction
- feature.setting uses core.validation, so a change to core.validation can break feature.setting, while a change to feature.setting can't break core.validation.
- Position
- Below the diagonal: feature.setting uses a module listed above it, which is the healthy direction.
39→36 feature.setting uses feature.update✕
- Connections
- 1 pair of types, where a type in feature.setting uses a type in feature.update.
- The types involved
org.tool.kit.feature.setting.SettingsRouteKt→org.tool.kit.feature.update.UpdateViewModel
- Direction
- feature.setting uses feature.update, so a change to feature.update can break feature.setting, while a change to feature.setting can't break feature.update.
- Position
- Below the diagonal: feature.setting uses a module listed above it, which is the healthy direction.
40→1 platform uses core.coroutine✕
- Connections
- 1 pair of types, where a type in platform uses a type in core.coroutine.
- The types involved
org.tool.kit.platform.JvmDesktopActionHandler→org.tool.kit.core.coroutine.AppDispatchers
- Direction
- platform uses core.coroutine, so a change to core.coroutine can break platform, while a change to platform can't break core.coroutine.
- Position
- Below the diagonal: platform uses a module listed above it, which is the healthy direction.
40→11 platform uses model✕
- Connections
- 1 pair of types, where a type in platform uses a type in model.
- The types involved
org.tool.kit.platform.DesktopFileSelection→org.tool.kit.model.FileSelectorType
- Direction
- platform uses model, so a change to model can break platform, while a change to platform can't break model.
- Position
- Below the diagonal: platform uses a module listed above it, which is the healthy direction.
40→14 platform uses domain.apk✕
- Connections
- 1 pair of types, where a type in platform uses a type in domain.apk.
- The types involved
org.tool.kit.platform.JvmApkIconDecoder→org.tool.kit.domain.apk.ApkIconSource
- Direction
- platform uses domain.apk, so a change to domain.apk can break platform, while a change to platform can't break domain.apk.
- Position
- Below the diagonal: platform uses a module listed above it, which is the healthy direction.
40→23 platform uses feature.app✕
- Connections
- 2 pairs of types, where a type in platform uses a type in feature.app.
- The types involved
org.tool.kit.platform.JvmClipboardWriter→org.tool.kit.feature.app.ClipboardWriterorg.tool.kit.platform.JvmDesktopActionHandler→org.tool.kit.feature.app.DesktopActionHandler
- Direction
- platform uses feature.app, so a change to feature.app can break platform, while a change to platform can't break feature.app.
- Position
- Below the diagonal: platform uses a module listed above it, which is the healthy direction.
40→38 platform uses feature.apk✕
- Connections
- 1 pair of types, where a type in platform uses a type in feature.apk.
- The types involved
org.tool.kit.platform.JvmApkIconDecoder→org.tool.kit.feature.apk.ApkIconDecoder
- Direction
- platform uses feature.apk, so a change to feature.apk can break platform, while a change to platform can't break feature.apk.
- Position
- Below the diagonal: platform 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 — Domain Modelling
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A07:2025 — Authentication Failures | 28 | High / Critical |
| A05:2025 — Injection | 9 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 7 | Medium |
Roadmap
Top priorities: Resolve the 27 REDACTED finding(s) in Secrets (history) — start with REDACTED (24), REDACTED (3); Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing; Resolve the 1 Banned license finding(s) in License Compliance.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 27 REDACTED finding(s) in Secrets (history) — start with REDACTED (24), REDACTED (3). | +6.1 pts | Medium | Secrets (history) |
| Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing. | +5.6 pts | Medium | Security & performance tooling |
| Resolve the 1 Banned license finding(s) in License Compliance. | +2.5 pts | Low | License Compliance |
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.gradle.kts. | +2.3 pts | Low | ADR Quality |
| Resolve the 1 `DownloadStartUI` spells `UI` where 23 names in the project spell it… finding(s) in Naming Consistency — start with UpdateDialog.kt. | +1.7 pts | Low | Naming Consistency |
| Resolve the 1 `DownloadUI` spells `UI` where 23 names in the project spell it `Ui` finding(s) in Naming Consistency — start with UpdateDialog.kt. | +1.7 pts | Low | Naming Consistency |
| Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. | +1.3 pts | Low | Static Analysis (SAST) |
| 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 |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 4.4 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 4.6 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 5.1 | Mixed | Secrets (history): REDACTED: REDACTED |
| shared/src/commonMain/kotlin/org/tool/kit/feature/setting/SettingsScreen.kt | 5.9 | Mixed | God Classes: FileTooLong: setting/SettingsScreen.kt |
| shared/src/commonMain/kotlin/org/tool/kit/feature/signature/SignatureInformationScreen.kt | 6.3 | Mixed | Code Duplication: Edited copies of one member (3 members, 67+ corresponding lines) |
| shared/src/commonMain/kotlin/org/tool/kit/feature/keystore/KeyStoreGenerationScreen.kt | 7.0 | Mixed | God Classes: MethodTooLong: KeyStoreGenerationScreenKt.GenerationBox |
| shared/src/commonMain/kotlin/org/tool/kit/feature/ui/UI.kt | 7.0 | Mixed | Code Duplication: Edited copy of a member (17 corresponding lines) |
| shared/src/commonMain/kotlin/org/tool/kit/feature/signature/ApkSigningScreen.kt | 7.0 | Mixed | Code Duplication: Duplicated block (18–19 lines × 2) |
| shared/src/commonMain/kotlin/org/tool/kit/feature/cleaner/CleanerRulesScreen.kt | 7.0 | Mixed | Cyclomatic Complexity: CleanerRulesScreenKt.CleanerRulesScreen (cyclomatic 20) |
| shared/src/jvmMain/kotlin/org/tool/kit/data/generator/JunkCodeComposer.kt | 7.0 | Mixed | Cyclomatic Complexity: JunkCodeComposer.booleanMethod (cyclomatic 16) |
| shared/src/commonMain/kotlin/org/tool/kit/feature/apk/ApkToolScreen.kt | 7.0 | Mixed | Code Duplication: Edited copy of a member (48 corresponding lines) |
| shared/src/commonMain/kotlin/org/tool/kit/feature/apk/ApkToolViewModel.kt | 7.1 | Mixed | Cyclomatic Complexity: ApkToolViewModel.submit (cyclomatic 16) |
| shared/src/jvmMain/kotlin/org/tool/kit/data/source/JvmBuildCachesDataSource.kt | 7.2 | Mixed | Cyclomatic Complexity: JvmBuildCachesDataSource.scan (cyclomatic 26) |
| shared/src/jvmMain/kotlin/org/tool/kit/data/source/ApkVerificationMapping.kt | 7.2 | Mixed | Cyclomatic Complexity: ApkVerificationMappingKt.mapApkVerification (cyclomatic 18) |
| shared/src/commonMain/kotlin/org/tool/kit/feature/junk/JunkCodeScreen.kt | 7.2 | Mixed | Code Duplication: Duplicated block (24 lines × 2) |
| shared/src/jvmMain/kotlin/org/tool/kit/data/generator/JunkLayoutComposer.kt | 7.4 | Mixed | Cyclomatic Complexity: Composition.widget (cyclomatic 34) |
| shared/src/jvmMain/kotlin/org/tool/kit/data/generator/AndroidJunkGenerator.kt | 7.4 | Mixed | Cyclomatic Complexity: AndroidJunkGenerator.startGenerate (cyclomatic 25) |
| rust/src/lib.rs | 7.4 | Mixed | Cyclomatic Complexity: toolkit_rs::resize_fir (cyclomatic 22) |
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.8, 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, 151 of 164 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.kt) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.kt) and this repository declares a JVM test suite (repository root, Gradle), but it was not re-run: no test result was produced. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D12 Dependency Hygiene — 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. Not scored — a Gradle build resolved 390 artifact(s) across its subprojects (228 behind a shipped release, reported), but the currency signal was not established over the whole graph, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
- D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares a Gradle build (build.gradle/build.gradle.kts), but the licence verdict published here was taken over its crate dependencies. Nothing was read about its Gradle dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- 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 (3 contributor(s) across 418 commit(s) sampled, automation and bot accounts excluded). One of them holds 100% of the history; the other 2 hold 0% 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 — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: 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.
- 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. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- 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. `shared/src/commonMain/kotlin/org/tool/kit/core/process/ProcessRunner.kt`, `shared/src/commonMain/kotlin/org/tool/kit/data/repository/DefaultCleanerRulesRepository.kt`, `shared/src/commonMain/kotlin/org/tool/kit/domain/repository/ApkSigningRepository.kt`, `shared/src/commonMain/kotlin/org/tool/kit/domain/repository/JunkCodeRepository.kt`, `shared/src/commonMain/kotlin/org/tool/kit/domain/usecase/BuildApkUseCase.kt`, … (+17 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- D34 Knowledge Freshness — 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. File-level freshness contradicts repo activity: 67 commits in the last 90 days, yet 61 of 94 significant files carry no living knowledge. Those two readings cannot both be true, so the per-file recency signal is treated as unreliable here and freshness is not scored for this run.
- 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 Koin, 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.
- 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.
- DM8 Value-object opportunities — 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 finds primitive parameters that travel together through several signatures of the domain (a missing value object). Its deterministic rule has not yet shown 95 % precision on adjudicated rows, so the clumps it finds are counted here and not published as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
- DM9 Scattered domain decisions — 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. Not measured — scattered-decision detection needs expression-level symbol resolution: a comparison operand bound to the member it judges (arm one) and a construction bound to the type it produces (arm two). A Roslyn compilation carries both; arm two alone also runs on any frontend that declares whether a construction is produced or passed, and this target loaded neither.
- 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, Scala, Rust and Java source only, and this repository's Kotlin is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- 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, Scala and Rust source only, and this repository's Kotlin is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P1 CI/CD gates — 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. A CI pipeline exists and the word "test" appears, but no explicit test-runner invocation (your stack's test command, or a test job) was matched — so either the gate runs tests through a step this pass could not recognise, or "test" is incidental here (a path, "latest", a reporter). Which of the two it is cannot be settled from this dimension's evidence; the coverage dimensions report whether a suite exists at all. You can widen what we reach: name the test runner explicitly in the pipeline step (your stack's test command, or a job named for the suite) so the gate is unambiguous to a reader and to this pass.
- 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 reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, 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.
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.
- 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.
- D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
- 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").
- 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.
- 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.
- 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.
- DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
- 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
17 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was Composition.widget at 34. A further 6 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being IconFactoryViewModel.onIntent at 25 — they are counted neither in the figure above nor in this dimension's score. 5 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: shared/src/commonMain/kotlin/org/tool/kit/feature/keystore/KeyStoreGenerationViewModel.kt (KeyStoreGenerationViewModel.onIntent at 24), shared/src/jvmMain/kotlin/org/tool/kit/data/generator/JunkGenerationReport.kt (JunkGenerationReportKt.codeLengths at 20), shared/src/commonMain/kotlin/org/tool/kit/feature/setting/SettingsViewModel.kt (SettingsViewModel.onIntent at 18), shared/src/commonMain/kotlin/org/tool/kit/domain/preferences/PreferencesRepository.kt (PreferencesRepositoryKt.changed at 16), shared/src/jvmMain/kotlin/org/tool/kit/data/source/PreferencesDataSource.kt (PreferencesDataSource.write at 16). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 1 body over 30 down to 30 or less in Cyclomatic Complexity — start with Composition.widget (cyclomatic 34). — Refactoring it lifts Cyclomatic Complexity from 7.6 to about 7.7/10.
D2 · Cognitive Complexity
19 method(s) exceeded the cognitive complexity threshold of 15; the worst was JvmBuildCachesDataSource.scan at 45.
What to do
- Bring the 19 bodies over 15 down to 15 or less in Cognitive Complexity — start with JvmBuildCachesDataSource.scan (cognitive 45), Composition.widget (cognitive 39), ApkVerificationMappingKt.mapApkVerification (cognitive 33). — 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 19 together lifts Cognitive Complexity from 6.9 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
10 god class(es) detected.
What to do
- Resolve the 5 MethodTooLong finding(s) in God Classes — start with CleanerRulesScreen.kt (3), AndroidJunkGenerator.kt, KeyStoreGenerationScreen.kt. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 4 FileTooLong finding(s) in God Classes — start with JunkCodeComposer.kt, CleanerRulesScreen.kt, CleanerScreen.kt. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 1 ClassTooLong finding(s) in God Classes — start with JunkCodeComposer.kt. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
27 duplicated block group(s) detected. 6.4 % of the production lines (1,257 of 19,712) are in a reported copy. A further 15 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
What to do
- Resolve the 6 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with ApkComponentPage.kt, ApkToolScreen.kt, CleanerRulesViewModel.kt. — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 3 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with JunkCodeScreen.kt, ApkToolScreen.kt, lib.rs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 3 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with ApkToolViewModel.kt (2), ApkComponentPage.kt. — One of this dimension's main actionable groups (3 warning-level).
D5 · Coupling
4 production modules (Gradle+Cargo), 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 3 of the 4 (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).
D6 · Cohesion (LCOM4)
0 of 37 classes have LCOM4 above 3.
D13 · REDACTED Scanning
REDACTED scan ran and found no leaked secrets.
D14 · License Compliance
1 of 188 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository commits no Cargo.lock, so its graph was resolved here: its manifests' `[dependencies]` and `[build-dependencies]` closed over the crates.io index, each crate at the newest release its requirement admits (what a fresh `cargo generate-lockfile` picks, not a graph the repository has pinned). Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository. ★ COVERAGE OF THIS VERDICT: it grades this repository's crate dependencies and nothing else. The repository also declares a Gradle build (build.gradle/build.gradle.kts), and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
What to do
- Resolve the 1 Banned license finding(s) in License Compliance. — One of this dimension's main actionable groups (1 issue-level).
D15 · Churn × Complexity Hotspots
Top hotspots: shared/src/commonMain/kotlin/org/tool/kit/feature/cleaner/CleanerViewModel.kt (2×19=38); shared/src/commonMain/kotlin/org/tool/kit/feature/apk/ApkToolViewModel.kt (2×16=32)
What to do
- Resolve the 2 Hotspot finding(s) in Churn × Complexity Hotspots — start with CleanerViewModel.kt, ApkToolViewModel.kt. — One of this dimension's main actionable groups (2 warning-level).
D17 · Explicit Debt
0 deducted task-comment markers across 19712 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. 2 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).
D21 · Naming Consistency
2 naming inconsistencies among 25 declarations measured against a convention their peers follow.
What to do
- Resolve the 1 `DownloadStartUI` spells `UI` where 23 names in the project spell it… finding(s) in Naming Consistency — start with UpdateDialog.kt. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 `DownloadUI` spells `UI` where 23 names in the project spell it `Ui` finding(s) in Naming Consistency — start with UpdateDialog.kt. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
1 of 3 build units (Cargo, Gradle) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with build.gradle.kts. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
27 finding(s): 0 critical, 27 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 27 REDACTED finding(s) in Secrets (history) — start with REDACTED (24), REDACTED (3). — One of this dimension's main actionable groups (27 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)
9 finding(s): 0 critical, 8 high, 1 medium, 0 low. 7 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 3 file(s) — `gradlew` (line 72, line 177), `shared/src/jvmMain/kotlin/org/tool/kit/data/generator/JunkGenerationReport.kt`, `shared/src/jvmMain/kotlin/org/tool/kit/data/generator/JunkLayoutComposer.kt` (line 121) — 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 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 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).
- No action in Static Analysis (SAST) — all 7 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (7 issue-level, 0 of them charged here).
D35 · Change Coupling
Strongest change-coupling: KeyStoreGenerationScreen.kt↔SignatureInformationScreen.kt 85%; ApkInformationScreen.kt↔KeyStoreGenerationScreen.kt 85%; KeyStoreGenerationScreen.kt↔ApkSigningScreen.kt 85%
What to do
- Resolve the 4 Change coupling finding(s) in Change Coupling — start with ApkInformationScreen.kt, SettingsScreen.kt, KeyStoreGenerationScreen.kt. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 3 Change-coupling hub finding(s) in Change Coupling — start with SignatureInformationScreen.kt, ApkSigningScreen.kt, App.kt. — One of this dimension's main actionable groups (3 warning-level).
D36 · Supply-chain Provenance & Signing
0/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 — start with REDACTED. — 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).
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 2 platform declaration(s) and 63 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
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
DM10 · One transaction, one aggregate
DM12 · Ambient inputs in the domain
DM6 · Domain ↔ infrastructure boundary
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
What to do
- Run the test suite in CI via an explicit runner step (`./gradlew test` for the toolchain this pipeline already uses) and gate merges on it.
P2 · Observability
- Only 2/3 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `rust`.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add spotbugs with find-sec-bugs (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 1 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
- `rust/Cargo.toml` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — rust/Cargo.toml:10
What to do
- Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
PF3 · Async & latency hygiene
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X16 · Unfloored truncation loop
X18 · Disposal-pattern correctness
X2 · Cancellation propagation
X21 · Side-effecting pattern guard
X25 · Inert configuration knob
X27 · Collection changed while being enumerated
X3 · Exception handling
- `catch (_: Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×9) — shared/src/jvmMain/kotlin/org/tool/kit/data/source/ApkArchiveInspector.kt:46, shared/src/jvmMain/kotlin/org/tool/kit/data/source/ApkArchiveInspector.kt:60, shared/src/jvmMain/kotlin/org/tool/kit/data/source/ApkArchiveInspector.kt:107, …
What to do
- Swallowed exception (caught, then discarded)
X30 · Support guard that admits what it rejects
X4 · Structured logging
X5 · Nullable reference types
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 82.7 | Strong | Solid. |
| Architecture | 86.5 | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 72.1 | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 45.3 | Weak — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 45.0 | Weak — gated by D28, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 100.0 | Exemplary | Strongest area. |
| Performance | 100.0 | Exemplary | Solid. |
Unscored — 1 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 3 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 — 75 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- 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. Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written.
- 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
- 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 — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- 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 — ~10851 lines of test source are present (.kt) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not included — the .kt suite was found but not re-run
- D12 Dependency Hygiene — Not scored — a Gradle build resolved 390 artifact(s) across its subprojects (228 behind a shipped release, reported), but the currency signal was not established over the whole graph, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
- 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.
- 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 — this repository's production source is .kt, .rs, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — symbol resolution incomplete — navigability not assessed
- D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts), a Cargo manifest and a Gradle version catalogue — not scanned yet).
- 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) — 22 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D34 Knowledge Freshness — knowledge concentrated in recent work — freshness signal contradicted by repo activity
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts), a Cargo manifest and a Gradle version catalogue — not scanned yet).
- 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 Aggregate boundaries — no aggregates detected — aggregate-boundary check not applicable
- DM11 Constructible invalid state — no entities detected — construction-time invariants not assessable
- DM2 Strongly-typed ids — no id-bearing domain types detected — strongly-typed-id adoption not assessable
- DM3 Integration-event coupling — no integration events detected — coupling check not applicable
- DM4 Rich vs anemic model — no data-bearing entities detected — rich-vs-anemic model not assessable
- DM5 Encapsulated state — no domain entities found — DM5 grades how entities protect their state, and this repository declares none
- DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
- DM8 Value-object opportunities — not scored — the deterministic rule found 0 candidate clump(s); its rows are withheld until it has a measured precision of 95 % (a sample of fewer than 10 rows cannot show one)
- DM9 Scattered domain decisions — not measured — scattered-decision detection needs expression-level symbol resolution: a comparison operand bound to the member it judges (arm one) and a construction bound to the type it produces (arm two). A Roslyn compilation carries both; arm two alone also runs on any frontend that declares whether a construction is produced or passed, and this target loaded neither
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner 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, Scala, Rust and Java, 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'.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM, Rust 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.
- 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.
- 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
- 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
- X23 Unguarded diagnostic materialisation — 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 — 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
- 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 — 36 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Banned license: imagequant
- REDACTED
Serious — 109 finding(s)
- Swallowed exception (caught, then discarded) shared/src/jvmMain/kotlin/org/tool/kit/data/source/ApkArchiveInspector.kt:46
- Swallowed exception (caught, then discarded) shared/src/jvmMain/kotlin/org/tool/kit/data/source/ApkArchiveInspector.kt:60
- Swallowed exception (caught, then discarded) shared/src/jvmMain/kotlin/org/tool/kit/data/source/ApkArchiveInspector.kt:107
- Swallowed exception (caught, then discarded) shared/src/jvmMain/kotlin/org/tool/kit/data/source/ApkComponentInspector.kt:31
- Swallowed exception (caught, then discarded) shared/src/jvmMain/kotlin/org/tool/kit/data/source/JvmBuildCachesDataSource.kt:130
- Swallowed exception (caught, then discarded) shared/src/commonMain/kotlin/org/tool/kit/feature/junk/JunkOutputValidation.kt:29
- Swallowed exception (caught, then discarded) shared/src/commonMain/kotlin/org/tool/kit/feature/iconfactory/IconFactoryViewModel.kt:99
- Swallowed exception (caught, then discarded) shared/src/commonMain/kotlin/org/tool/kit/feature/cleaner/CleanerViewModel.kt:136
- Swallowed exception (caught, then discarded) shared/src/commonMain/kotlin/org/tool/kit/feature/cleaner/CleanerViewModel.kt:197
- Duplicated block (8 lines × 2) shared/src/commonMain/kotlin/org/tool/kit/feature/apk/ApkComponentPage.kt:82
- Duplicated block (8 lines × 2) shared/src/commonMain/kotlin/org/tool/kit/feature/apk/ApkToolScreen.kt:290
- Duplicated block (8 lines × 2) shared/src/commonMain/kotlin/org/tool/kit/feature/cleaner/CleanerRulesViewModel.kt:120
- Duplicated block (8 lines × 2) shared/src/commonMain/kotlin/org/tool/kit/feature/setting/SettingsScreen.kt:242
- Duplicated block (8 lines × 2) shared/src/commonMain/kotlin/org/tool/kit/feature/signature/SignatureInformationScreen.kt:411
- Duplicated block (8 lines × 2) shared/src/jvmMain/kotlin/org/tool/kit/data/generator/JunkCodeComposer.kt:480
- MethodTooLong: CleanerRulesScreenKt.CleanerRulesScreen shared/src/commonMain/kotlin/org/tool/kit/feature/cleaner/CleanerRulesScreen.kt:57
- MethodTooLong: CleanerRulesScreenKt.RuleCard shared/src/commonMain/kotlin/org/tool/kit/feature/cleaner/CleanerRulesScreen.kt:397
- MethodTooLong: AndroidJunkGenerator.startGenerate shared/src/jvmMain/kotlin/org/tool/kit/data/generator/AndroidJunkGenerator.kt:26
- MethodTooLong: KeyStoreGenerationScreenKt.GenerationBox shared/src/commonMain/kotlin/org/tool/kit/feature/keystore/KeyStoreGenerationScreen.kt:61
- MethodTooLong: CleanerRulesScreenKt.ScanSettings shared/src/commonMain/kotlin/org/tool/kit/feature/cleaner/CleanerRulesScreen.kt:762
- FileTooLong: generator/JunkCodeComposer.kt shared/src/jvmMain/kotlin/org/tool/kit/data/generator/JunkCodeComposer.kt
- FileTooLong: cleaner/CleanerRulesScreen.kt shared/src/commonMain/kotlin/org/tool/kit/feature/cleaner/CleanerRulesScreen.kt
- FileTooLong: cleaner/CleanerScreen.kt shared/src/commonMain/kotlin/org/tool/kit/feature/cleaner/CleanerScreen.kt
- FileTooLong: setting/SettingsScreen.kt shared/src/commonMain/kotlin/org/tool/kit/feature/setting/SettingsScreen.kt
- Change coupling: ApkInformationScreen.kt ↔ KeyStoreGenerationScreen.kt shared/src/commonMain/kotlin/org/tool/kit/feature/apk/ApkInformationScreen.kt:1
- Change coupling: SettingsScreen.kt ↔ PreferencesDataSource.kt shared/src/commonMain/kotlin/org/tool/kit/feature/setting/SettingsScreen.kt:1
- Change coupling: KeyStoreGenerationScreen.kt ↔ SettingsScreen.kt shared/src/commonMain/kotlin/org/tool/kit/feature/keystore/KeyStoreGenerationScreen.kt:1
- Change coupling: UI.kt ↔ FileTypes.kt shared/src/commonMain/kotlin/org/tool/kit/feature/ui/UI.kt:1
- Change-coupling hub: SignatureInformationScreen.kt → ApkInformationScreen.kt, IconFactoryScreen.kt, KeyStoreGenerationScreen.kt, SettingsScreen.kt, UI.kt shared/src/commonMain/kotlin/org/tool/kit/feature/signature/SignatureInformationScreen.kt
- Change-coupling hub: ApkSigningScreen.kt → ApkInformationScreen.kt, IconFactoryScreen.kt, KeyStoreGenerationScreen.kt, SettingsScreen.kt, SignatureInformationScreen.kt, UI.kt, FileTypes.kt shared/src/commonMain/kotlin/org/tool/kit/feature/signature/ApkSigningScreen.kt
- Change-coupling hub: App.kt → ApkInformationScreen.kt, CleanerScreen.kt, JunkCodeScreen.kt, KeyStoreGenerationScreen.kt, SettingsScreen.kt, ApkSigningScreen.kt, SignatureInformationScreen.kt, PreferencesDataSource.kt shared/src/commonMain/kotlin/org/tool/kit/App.kt
- Duplicated block (9 lines × 2) shared/src/commonMain/kotlin/org/tool/kit/feature/junk/JunkCodeScreen.kt:64
- Duplicated block (9 lines × 2) shared/src/commonMain/kotlin/org/tool/kit/feature/apk/ApkToolScreen.kt:377
- Duplicated block (9 lines × 2) rust/src/lib.rs:321
- Duplicated block (7 lines × 2) shared/src/commonMain/kotlin/org/tool/kit/feature/apk/ApkComponentPage.kt:43
- Duplicated block (7 lines × 2) shared/src/commonMain/kotlin/org/tool/kit/feature/apk/ApkToolViewModel.kt:146
- Duplicated block (7 lines × 2) shared/src/commonMain/kotlin/org/tool/kit/feature/apk/ApkToolViewModel.kt:166
- Hotspot: shared/src/commonMain/kotlin/org/tool/kit/feature/cleaner/CleanerViewModel.kt shared/src/commonMain/kotlin/org/tool/kit/feature/cleaner/CleanerViewModel.kt:221
- Hotspot: shared/src/commonMain/kotlin/org/tool/kit/feature/apk/ApkToolViewModel.kt shared/src/commonMain/kotlin/org/tool/kit/feature/apk/ApkToolViewModel.kt:175
- Edited copy of a member (17 corresponding lines) shared/src/commonMain/kotlin/org/tool/kit/feature/apk/ApkInformationRoute.kt:14
- Edited copy of a member (17 corresponding lines) shared/src/commonMain/kotlin/org/tool/kit/feature/ui/UI.kt:92
- Duplicated block (18 lines × 2) shared/src/commonMain/kotlin/org/tool/kit/feature/junk/JunkCodeScreen.kt:310
- Duplicated block (18 lines × 2) shared/src/jvmMain/kotlin/org/tool/kit/data/generator/JunkCodeComposer.kt:760
- Duplicated block (10 lines × 2) shared/src/commonMain/kotlin/org/tool/kit/feature/setting/SettingsScreen.kt:273
- Duplicated block (10 lines × 2) shared/src/commonMain/kotlin/org/tool/kit/feature/apk/ApkComponentPage.kt:111
- Duplicated block (6 lines × 2) shared/src/commonMain/kotlin/org/tool/kit/feature/apk/ApkPackagePage.kt:291
- Duplicated block (6 lines × 2) shared/src/commonMain/kotlin/org/tool/kit/feature/apk/ApkInformationViewModel.kt:117
- Composition.widget (cyclomatic 34) shared/src/jvmMain/kotlin/org/tool/kit/data/generator/JunkLayoutComposer.kt:178
- JvmBuildCachesDataSource.scan (cyclomatic 26) shared/src/jvmMain/kotlin/org/tool/kit/data/source/JvmBuildCachesDataSource.kt:16
- AndroidJunkGenerator.startGenerate (cyclomatic 25) shared/src/jvmMain/kotlin/org/tool/kit/data/generator/AndroidJunkGenerator.kt:26
- toolkit_rs::resize_fir (cyclomatic 22) rust/src/lib.rs:25
- CleanerRulesScreenKt.CleanerRulesScreen (cyclomatic 20) shared/src/commonMain/kotlin/org/tool/kit/feature/cleaner/CleanerRulesScreen.kt:57
- CleanerRulesScreenKt.RuleCard (cyclomatic 20) shared/src/commonMain/kotlin/org/tool/kit/feature/cleaner/CleanerRulesScreen.kt:397
- CleanerViewModel.confirmDelete (cyclomatic 19) shared/src/commonMain/kotlin/org/tool/kit/feature/cleaner/CleanerViewModel.kt:221
- IconFactoryViewModel.submit (cyclomatic 19) shared/src/commonMain/kotlin/org/tool/kit/feature/iconfactory/IconFactoryViewModel.kt:110
- ApkArchiveInspectorKt.inspectElfAlignment (cyclomatic 19) shared/src/jvmMain/kotlin/org/tool/kit/data/source/ApkArchiveInspector.kt:63
- ApkToolFormReducer.field (cyclomatic 18) shared/src/commonMain/kotlin/org/tool/kit/feature/apk/ApkToolState.kt:74
- SigningFormReducer.field (cyclomatic 18) shared/src/commonMain/kotlin/org/tool/kit/feature/signature/ApkSigningState.kt:55
- ApkVerificationMappingKt.mapApkVerification (cyclomatic 18) shared/src/jvmMain/kotlin/org/tool/kit/data/source/ApkVerificationMapping.kt:9
- ApkSigningViewModel.submit (cyclomatic 17) shared/src/commonMain/kotlin/org/tool/kit/feature/signature/ApkSigningViewModel.kt:141
- ApkToolViewModel.submit (cyclomatic 16) shared/src/commonMain/kotlin/org/tool/kit/feature/apk/ApkToolViewModel.kt:175
- CleanerViewModel.onIntent (cyclomatic 16) shared/src/commonMain/kotlin/org/tool/kit/feature/cleaner/CleanerViewModel.kt:69
- JunkCodeComposer.booleanMethod (cyclomatic 16) shared/src/jvmMain/kotlin/org/tool/kit/data/generator/JunkCodeComposer.kt:579
- JvmBuildCachesDataSource.delete (cyclomatic 16) shared/src/jvmMain/kotlin/org/tool/kit/data/source/JvmBuildCachesDataSource.kt:89
- JvmBuildCachesDataSource.scan (cognitive 45) shared/src/jvmMain/kotlin/org/tool/kit/data/source/JvmBuildCachesDataSource.kt:16
- Composition.widget (cognitive 39) shared/src/jvmMain/kotlin/org/tool/kit/data/generator/JunkLayoutComposer.kt:178
- ApkVerificationMappingKt.mapApkVerification (cognitive 33) shared/src/jvmMain/kotlin/org/tool/kit/data/source/ApkVerificationMapping.kt:9
- CleanerRulesScreenKt.RuleCard (cognitive 32) shared/src/commonMain/kotlin/org/tool/kit/feature/cleaner/CleanerRulesScreen.kt:397
- CleanerViewModel.confirmDelete (cognitive 27) shared/src/commonMain/kotlin/org/tool/kit/feature/cleaner/CleanerViewModel.kt:221
- AndroidJunkGenerator.startGenerate (cognitive 27) shared/src/jvmMain/kotlin/org/tool/kit/data/generator/AndroidJunkGenerator.kt:26
- CleanerRuleEvaluatorKt.validateRule (cognitive 24) shared/src/commonMain/kotlin/org/tool/kit/domain/cleaner/CleanerRuleEvaluator.kt:15
- SigningFormReducer.field (cognitive 24) shared/src/commonMain/kotlin/org/tool/kit/feature/signature/ApkSigningState.kt:55
- CleanerRulesScreenKt.CleanerRulesScreen (cognitive 22) shared/src/commonMain/kotlin/org/tool/kit/feature/cleaner/CleanerRulesScreen.kt:57
- DesktopFormattingKt.formatFileSize (cognitive 22) shared/src/jvmMain/kotlin/org/tool/kit/utils/DesktopFormatting.kt:18
- UpdateDialogKt.UpdateDialog (cognitive 21) shared/src/commonMain/kotlin/org/tool/kit/feature/update/UpdateDialog.kt:67
- JunkCodeComposer.booleanMethod (cognitive 20) shared/src/jvmMain/kotlin/org/tool/kit/data/generator/JunkCodeComposer.kt:579
- Composition.fill (cognitive 20) shared/src/jvmMain/kotlin/org/tool/kit/data/generator/JunkLayoutComposer.kt:91
- ApkArchiveInspectorKt.inspectElfAlignment (cognitive 19) shared/src/jvmMain/kotlin/org/tool/kit/data/source/ApkArchiveInspector.kt:63
- JvmBuildCachesDataSource.delete (cognitive 19) shared/src/jvmMain/kotlin/org/tool/kit/data/source/JvmBuildCachesDataSource.kt:89
- CleanerScreenKt.CleanerResultRow (cognitive 18) shared/src/commonMain/kotlin/org/tool/kit/feature/cleaner/CleanerScreen.kt:414
- ApkSigningViewModel.submit (cognitive 18) shared/src/commonMain/kotlin/org/tool/kit/feature/signature/ApkSigningViewModel.kt:141
- GenerateIconsUseCase.invoke (cognitive 16) shared/src/commonMain/kotlin/org/tool/kit/domain/usecase/GenerateIconsUseCase.kt:15
- ApkToolViewModel.submit (cognitive 16) shared/src/commonMain/kotlin/org/tool/kit/feature/apk/ApkToolViewModel.kt:175
- REDACTED
- ClassTooLong: JunkComposedUnit shared/src/jvmMain/kotlin/org/tool/kit/data/generator/JunkCodeComposer.kt:18
- REDACTED
- REDACTED
- Edited copy of a member (61 corresponding lines) rust/src/lib.rs:272
- Edited copies of one member (3 members, 67+ corresponding lines) shared/src/commonMain/kotlin/org/tool/kit/feature/signature/SignatureInformationScreen.kt:410
- Edited copy of a member (46 corresponding lines) shared/src/jvmMain/kotlin/org/tool/kit/data/generator/JunkCodeComposer.kt:753
- Edited copy of a member (48 corresponding lines) shared/src/commonMain/kotlin/org/tool/kit/feature/apk/ApkToolScreen.kt:327
- Edited copies of one member (4 members, 35+ corresponding lines) shared/src/commonMain/kotlin/org/tool/kit/feature/apk/ApkToolScreen.kt:153
- Edited copy of a member (14 corresponding lines) shared/src/commonMain/kotlin/org/tool/kit/feature/apk/ApkToolRoute.kt:19
- Edited copy of a member (24 corresponding lines) shared/src/commonMain/kotlin/org/tool/kit/feature/apk/ApkContentsPage.kt:167
- Edited copy of a member (25 corresponding lines) shared/src/jvmMain/kotlin/org/tool/kit/utils/DesktopFormatting.kt:22
- Edited copy of a member (12 corresponding lines) shared/src/commonMain/kotlin/org/tool/kit/feature/cleaner/CleanerRulesViewModel.kt:114
- Edited copy of a member (8 corresponding lines) shared/src/commonMain/kotlin/org/tool/kit/feature/apk/ApkToolViewModel.kt:145
- Edited copies of one member (4 members, 8+ corresponding lines) shared/src/commonMain/kotlin/org/tool/kit/feature/apk/ApkToolViewModel.kt:155
- Edited copy of a member (10 corresponding lines) shared/src/jvmMain/kotlin/org/tool/kit/data/repository/JvmKeyStoreRepository.kt:17
- Edited copy of a member (7 corresponding lines) shared/src/commonMain/kotlin/org/tool/kit/feature/iconfactory/IconFactoryWorkspace.kt:301
- Duplicated block (24 lines × 2) shared/src/commonMain/kotlin/org/tool/kit/feature/junk/JunkCodeScreen.kt:218
- Duplicated block (18–19 lines × 2) shared/src/commonMain/kotlin/org/tool/kit/feature/signature/ApkSigningScreen.kt:318
- Duplicated block (17–18 lines × 2) shared/src/commonMain/kotlin/org/tool/kit/feature/apk/ApkToolScreen.kt:332
- Duplicated block (17 lines × 3) shared/src/commonMain/kotlin/org/tool/kit/feature/junk/JunkCodeScreen.kt:221
- Duplicated block (16 lines × 2) shared/src/commonMain/kotlin/org/tool/kit/feature/apk/ApkToolScreen.kt:350
- Duplicated block (15 lines × 3) shared/src/commonMain/kotlin/org/tool/kit/feature/apk/ApkToolScreen.kt:350
- Duplicated block (11–12 lines × 2) shared/src/commonMain/kotlin/org/tool/kit/feature/apk/ApkContentsPage.kt:170
- Duplicated block (9 lines × 4) shared/src/jvmMain/kotlin/org/tool/kit/data/source/ApkVerificationMapping.kt:24
- Duplicated block (9 lines × 5) shared/src/jvmMain/kotlin/org/tool/kit/data/source/ApkVerificationMapping.kt:24
Minor — 18 finding(s)
- Duplicated predicate shared/src/commonMain/kotlin/org/tool/kit/feature/apk/ApkToolState.kt:39
- Duplicated predicate shared/src/commonMain/kotlin/org/tool/kit/feature/apk/ApkToolState.kt:38
- Duplicated predicate shared/src/commonMain/kotlin/org/tool/kit/domain/apk/ApkInformationData.kt:30
- No ADRs found shared/build.gradle.kts:311
- `DownloadStartUI` spells `UI` where 23 names in the project spell it `Ui` shared/src/commonMain/kotlin/org/tool/kit/feature/update/UpdateDialog.kt:141
- `DownloadUI` spells `UI` where 23 names in the project spell it `Ui` shared/src/commonMain/kotlin/org/tool/kit/feature/update/UpdateDialog.kt:234
- Projects may be oversized for their cohesion shared/build.gradle.kts:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- Logging is not universal
- No SAST
- No dependency-update automation rust/Cargo.toml:10
- No changelog
Minor — 1 finding(s)
- Off the main sequence: :shared
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 --log-opts "--full-history --all --skip=0 --max-count=200" --report-format json --report-path /tmp/watchdog-gitleaks-36e94175dcb345bd9314584566d04814/history.json --exit-code 0 --source . | 33 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=200 --max-count=218" --report-format json --report-path /tmp/watchdog-gitleaks-36e94175dcb345bd9314584566d04814/history-1.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history-1.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-36e94175dcb345bd9314584566d04814/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 9 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts), a Cargo manifest and a Gradle version catalogue — not scanned yet). | 0 | — |
| 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 22 file(s) — `shared/src/commonMain/kotlin/org/tool/kit/core/process/ProcessRunner.kt`, `shared/src/commonMain/kotlin/org/tool/kit/data/repository/DefaultCleanerRulesRepository.kt`, `shared/src/commonMain/kotlin/org/tool/kit/domain/repository/ApkSigningRepository.kt`, `shared/src/commonMain/kotlin/org/tool/kit/domain/repository/JunkCodeRepository.kt`, `shared/src/commonMain/kotlin/org/tool/kit/domain/usecase/BuildApkUseCase.kt`, … (+17 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts), a Cargo manifest and a Gradle version catalogue — not scanned yet). | 0 | — |