Executive summary
LawnchairLauncher/lawnicons falls short of our standard for production because two passwords or keys sit in the current code. It scores 57.3 out of 100 and is rated Adequate, and all 61 of its critical findings are security problems.
Production Readiness, at 50.6, is the weakest lens by a small margin, and the weakest lens counts most in the score. The best first step is recording design decisions, worth about 5.0 points. Replacing the two exposed passwords or keys and switching the old ones off would lift Production Readiness itself, worth about 4.8 points.
Forty-three pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Nine secrets can leak from the build pipeline, and three pipeline steps install packages that can change without warning. Pinning each tool to an exact version, limiting each secret to its own step and pinning what the pipeline installs would close these risks. Passing outside input through environment variables would fix the two pipeline steps that put outside input straight into a shell command, and the two passwords or keys in the code and the password or key in the code's history need replacing, with the old ones switched off.
The product code is 12,910 lines, about €17,000 to rebuild.
The weakest lenses score close to each other, so improving any of them moves the score.
Rebuild cost: about €17,000 · Estimate
| Cost to rebuild | €5,500 to €28,000, for 91 to 290 hours of work, about 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 57. 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: 12,910 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: which parts of the code depend on which
| uses → | 1 (global) | 2 .github.scripts.name_checker | 3 app.lawnchair.lawnicons.data.model.OssLibrary | 4 app.lawnchair.lawnicons.data.repository.BasePreferenceManager | 5 app.lawnchair.lawnicons.ui.destination.about | 6 app.lawnchair.lawnicons.ui.destination.iconrequest.IconRequestViewModel | 7 .github.scripts | 8 app.lawnchair.lawnicons.data.model | 9 app.lawnchair.lawnicons.ui.destination.about.ColumnTypes | 10 app.lawnchair.lawnicons.ui.destination.iconrequest.IconRequestViewModel.ZipCreationResult | 11 app.lawnchair.lawnicons.data.api | 12 app.lawnchair.lawnicons.data.model.AnnouncementLocation | 13 app.lawnchair.lawnicons.data.model.Component | 14 app.lawnchair.lawnicons.data.model.SearchMode | 15 app.lawnchair.lawnicons.data.repository.acknowledgements | 16 app.lawnchair.lawnicons.data.repository.iconrequest.IconRequestBundler | 17 app.lawnchair.lawnicons.ui | 18 app.lawnchair.lawnicons.ui.components | 19 app.lawnchair.lawnicons.ui.components.home.iconpreview | 20 app.lawnchair.lawnicons.ui.components.home.search | 21 app.lawnchair.lawnicons.data.repository | 22 app.lawnchair.lawnicons.ui.components.SystemNavigation | 23 app.lawnchair.lawnicons.ui.components.home | 24 app.lawnchair.lawnicons.ui.destination.acknowledgements | 25 app.lawnchair.lawnicons.data.repository.home | 26 app.lawnchair.lawnicons.data.repository.iconrequest | 27 app.lawnchair.lawnicons.di | 28 app.lawnchair.lawnicons.ui.destination.contributors | 29 app.lawnchair.lawnicons.ui.destination.newicons | 30 app.lawnchair.lawnicons | 31 app.lawnchair.lawnicons.data.repository.bugreport | 32 app.lawnchair.lawnicons.ui.destination.contributors.ContributorsUiState | 33 app.lawnchair.lawnicons.ui.destination.debugmenu | 34 app.lawnchair.lawnicons.ui.destination.home | 35 app.lawnchair.lawnicons.ui.destination.iconrequest | 36 app.lawnchair.lawnicons.LawniconsGraph | 37 app.lawnchair.lawnicons.data.repository.bugreport.BugReportReceiver | 38 app.lawnchair.lawnicons.data.repository.bugreport.KatbinService | 39 app.lawnchair.lawnicons.data.repository.bugreport.LawniconsBugReporter | 40 app.lawnchair.lawnicons.ui.destination.home.HomeUiState |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 (global) | ||||||||||||||||||||||||||||||||||||||||
| 2 .github.scripts.name_checker | ||||||||||||||||||||||||||||||||||||||||
| 3 app.lawnchair.lawnicons.data.model.OssLibrary | ||||||||||||||||||||||||||||||||||||||||
| 4 app.lawnchair.lawnicons.data.repository.BasePreferenceManager | ||||||||||||||||||||||||||||||||||||||||
| 5 app.lawnchair.lawnicons.ui.destination.about | ||||||||||||||||||||||||||||||||||||||||
| 6 app.lawnchair.lawnicons.ui.destination.iconrequest.IconRequestViewModel | ||||||||||||||||||||||||||||||||||||||||
| 7 .github.scripts | 2 | |||||||||||||||||||||||||||||||||||||||
| 8 app.lawnchair.lawnicons.data.model | 2 | |||||||||||||||||||||||||||||||||||||||
| 9 app.lawnchair.lawnicons.ui.destination.about.ColumnTypes | 4 | |||||||||||||||||||||||||||||||||||||||
| 10 app.lawnchair.lawnicons.ui.destination.iconrequest.IconRequestViewModel.ZipCreationResult | 2 | |||||||||||||||||||||||||||||||||||||||
| 11 app.lawnchair.lawnicons.data.api | 3 | |||||||||||||||||||||||||||||||||||||||
| 12 app.lawnchair.lawnicons.data.model.AnnouncementLocation | 2 | |||||||||||||||||||||||||||||||||||||||
| 13 app.lawnchair.lawnicons.data.model.Component | 1 | |||||||||||||||||||||||||||||||||||||||
| 14 app.lawnchair.lawnicons.data.model.SearchMode | 3 | |||||||||||||||||||||||||||||||||||||||
| 15 app.lawnchair.lawnicons.data.repository.acknowledgements | 4 | |||||||||||||||||||||||||||||||||||||||
| 16 app.lawnchair.lawnicons.data.repository.iconrequest.IconRequestBundler | 1 | |||||||||||||||||||||||||||||||||||||||
| 17 app.lawnchair.lawnicons.ui | 2 | |||||||||||||||||||||||||||||||||||||||
| 18 app.lawnchair.lawnicons.ui.components | 1 | |||||||||||||||||||||||||||||||||||||||
| 19 app.lawnchair.lawnicons.ui.components.home.iconpreview | 4 | |||||||||||||||||||||||||||||||||||||||
| 20 app.lawnchair.lawnicons.ui.components.home.search | 4 | |||||||||||||||||||||||||||||||||||||||
| 21 app.lawnchair.lawnicons.data.repository | 1 | 6 | 1 | |||||||||||||||||||||||||||||||||||||
| 22 app.lawnchair.lawnicons.ui.components.SystemNavigation | 3 | |||||||||||||||||||||||||||||||||||||||
| 23 app.lawnchair.lawnicons.ui.components.home | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 24 app.lawnchair.lawnicons.ui.destination.acknowledgements | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 25 app.lawnchair.lawnicons.data.repository.home | 7 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 26 app.lawnchair.lawnicons.data.repository.iconrequest | 13 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 27 app.lawnchair.lawnicons.di | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 28 app.lawnchair.lawnicons.ui.destination.contributors | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 29 app.lawnchair.lawnicons.ui.destination.newicons | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 30 app.lawnchair.lawnicons | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 31 app.lawnchair.lawnicons.data.repository.bugreport | 1 | |||||||||||||||||||||||||||||||||||||||
| 32 app.lawnchair.lawnicons.ui.destination.contributors.ContributorsUiState | 1 | 3 | ||||||||||||||||||||||||||||||||||||||
| 33 app.lawnchair.lawnicons.ui.destination.debugmenu | 1 | 4 | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 34 app.lawnchair.lawnicons.ui.destination.home | 8 | 2 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 35 app.lawnchair.lawnicons.ui.destination.iconrequest | 1 | 3 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 36 app.lawnchair.lawnicons.LawniconsGraph | 1 | |||||||||||||||||||||||||||||||||||||||
| 37 app.lawnchair.lawnicons.data.repository.bugreport.BugReportReceiver | 1 | |||||||||||||||||||||||||||||||||||||||
| 38 app.lawnchair.lawnicons.data.repository.bugreport.KatbinService | 1 | |||||||||||||||||||||||||||||||||||||||
| 39 app.lawnchair.lawnicons.data.repository.bugreport.LawniconsBugReporter | 1 | |||||||||||||||||||||||||||||||||||||||
| 40 app.lawnchair.lawnicons.ui.destination.home.HomeUiState | 2 | 2 |
7→2 .github.scripts uses .github.scripts.name_checker✕
- Connections
- 2 pairs of types, where a type in .github.scripts uses a type in .github.scripts.name_checker.
- The types involved
.github.scripts.name_checker→.github.scripts.name_checker.CheckContext.github.scripts.name_checker→.github.scripts.name_checker.RunReport
- Direction
- .github.scripts uses .github.scripts.name_checker, so a change to .github.scripts.name_checker can break .github.scripts, while a change to .github.scripts can't break .github.scripts.name_checker.
- Position
- Below the diagonal: .github.scripts uses a module listed above it, which is the healthy direction.
8→3 app.lawnchair.lawnicons.data.model uses app.lawnchair.lawnicons.data.model.OssLibrary✕
- Connections
- 2 pairs of types, where a type in app.lawnchair.lawnicons.data.model uses a type in app.lawnchair.lawnicons.data.model.OssLibrary.
- The types involved
app.lawnchair.lawnicons.data.model.OssLibrary→app.lawnchair.lawnicons.data.model.OssLibrary.Licenseapp.lawnchair.lawnicons.data.model.OssLibrary→app.lawnchair.lawnicons.data.model.OssLibrary.Scm
- Direction
- app.lawnchair.lawnicons.data.model uses app.lawnchair.lawnicons.data.model.OssLibrary, so a change to app.lawnchair.lawnicons.data.model.OssLibrary can break app.lawnchair.lawnicons.data.model, while a change to app.lawnchair.lawnicons.data.model can't break app.lawnchair.lawnicons.data.model.OssLibrary.
- Position
- Below the diagonal: app.lawnchair.lawnicons.data.model uses a module listed above it, which is the healthy direction.
9→5 app.lawnchair.lawnicons.ui.destination.about.ColumnTypes uses app.lawnchair.lawnicons.ui.destination.about✕
- Connections
- 4 pairs of types, where a type in app.lawnchair.lawnicons.ui.destination.about.ColumnTypes uses a type in app.lawnchair.lawnicons.ui.destination.about.
- The types involved
app.lawnchair.lawnicons.ui.destination.about.ColumnTypes.HEADER→app.lawnchair.lawnicons.ui.destination.about.ColumnTypesapp.lawnchair.lawnicons.ui.destination.about.ColumnTypes.LIST_ITEM→app.lawnchair.lawnicons.ui.destination.about.ColumnTypesapp.lawnchair.lawnicons.ui.destination.about.ColumnTypes.NAVIGATION_ITEM→app.lawnchair.lawnicons.ui.destination.about.ColumnTypesapp.lawnchair.lawnicons.ui.destination.about.ColumnTypes.SPACER→app.lawnchair.lawnicons.ui.destination.about.ColumnTypes
- Direction
- app.lawnchair.lawnicons.ui.destination.about.ColumnTypes uses app.lawnchair.lawnicons.ui.destination.about, so a change to app.lawnchair.lawnicons.ui.destination.about can break app.lawnchair.lawnicons.ui.destination.about.ColumnTypes, while a change to app.lawnchair.lawnicons.ui.destination.about.ColumnTypes can't break app.lawnchair.lawnicons.ui.destination.about.
- Position
- Below the diagonal: app.lawnchair.lawnicons.ui.destination.about.ColumnTypes uses a module listed above it, which is the healthy direction.
10→6 app.lawnchair.lawnicons.ui.destination.iconrequest.IconRequestViewModel.ZipCreationResult uses app.lawnchair.lawnicons.ui.destination.iconrequest.IconRequestViewModel✕
- Connections
- 2 pairs of types, where a type in app.lawnchair.lawnicons.ui.destination.iconrequest.IconRequestViewModel.ZipCreationResult uses a type in app.lawnchair.lawnicons.ui.destination.iconrequest.IconRequestViewModel.
- The types involved
app.lawnchair.lawnicons.ui.destination.iconrequest.IconRequestViewModel.ZipCreationResult.Error→app.lawnchair.lawnicons.ui.destination.iconrequest.IconRequestViewModel.ZipCreationResultapp.lawnchair.lawnicons.ui.destination.iconrequest.IconRequestViewModel.ZipCreationResult.Success→app.lawnchair.lawnicons.ui.destination.iconrequest.IconRequestViewModel.ZipCreationResult
- Direction
- app.lawnchair.lawnicons.ui.destination.iconrequest.IconRequestViewModel.ZipCreationResult uses app.lawnchair.lawnicons.ui.destination.iconrequest.IconRequestViewModel, so a change to app.lawnchair.lawnicons.ui.destination.iconrequest.IconRequestViewModel can break app.lawnchair.lawnicons.ui.destination.iconrequest.IconRequestViewModel.ZipCreationResult, while a change to app.lawnchair.lawnicons.ui.destination.iconrequest.IconRequestViewModel.ZipCreationResult can't break app.lawnchair.lawnicons.ui.destination.iconrequest.IconRequestViewModel.
- Position
- Below the diagonal: app.lawnchair.lawnicons.ui.destination.iconrequest.IconRequestViewModel.ZipCreationResult uses a module listed above it, which is the healthy direction.
11→8 app.lawnchair.lawnicons.data.api uses app.lawnchair.lawnicons.data.model✕
- Connections
- 3 pairs of types, where a type in app.lawnchair.lawnicons.data.api uses a type in app.lawnchair.lawnicons.data.model.
- The types involved
app.lawnchair.lawnicons.data.api.AnnouncementsAPI→app.lawnchair.lawnicons.data.model.Announcementsapp.lawnchair.lawnicons.data.api.GitHubContributorsAPI→app.lawnchair.lawnicons.data.model.GitHubContributorapp.lawnchair.lawnicons.data.api.IconRequestSettingsAPI→app.lawnchair.lawnicons.data.model.IconRequestSettings
- Direction
- app.lawnchair.lawnicons.data.api uses app.lawnchair.lawnicons.data.model, so a change to app.lawnchair.lawnicons.data.model can break app.lawnchair.lawnicons.data.api, while a change to app.lawnchair.lawnicons.data.api can't break app.lawnchair.lawnicons.data.model.
- Position
- Below the diagonal: app.lawnchair.lawnicons.data.api uses a module listed above it, which is the healthy direction.
12→8 app.lawnchair.lawnicons.data.model.AnnouncementLocation uses app.lawnchair.lawnicons.data.model✕
- Connections
- 2 pairs of types, where a type in app.lawnchair.lawnicons.data.model.AnnouncementLocation uses a type in app.lawnchair.lawnicons.data.model.
- The types involved
app.lawnchair.lawnicons.data.model.AnnouncementLocation.Home→app.lawnchair.lawnicons.data.model.AnnouncementLocationapp.lawnchair.lawnicons.data.model.AnnouncementLocation.IconRequest→app.lawnchair.lawnicons.data.model.AnnouncementLocation
- Direction
- app.lawnchair.lawnicons.data.model.AnnouncementLocation uses app.lawnchair.lawnicons.data.model, so a change to app.lawnchair.lawnicons.data.model can break app.lawnchair.lawnicons.data.model.AnnouncementLocation, while a change to app.lawnchair.lawnicons.data.model.AnnouncementLocation can't break app.lawnchair.lawnicons.data.model.
- Position
- Below the diagonal: app.lawnchair.lawnicons.data.model.AnnouncementLocation uses a module listed above it, which is the healthy direction.
13→8 app.lawnchair.lawnicons.data.model.Component uses app.lawnchair.lawnicons.data.model✕
- Connections
- 1 pair of types, where a type in app.lawnchair.lawnicons.data.model.Component uses a type in app.lawnchair.lawnicons.data.model.
- The types involved
app.lawnchair.lawnicons.data.model.Component.Companion→app.lawnchair.lawnicons.data.model.Component
- Direction
- app.lawnchair.lawnicons.data.model.Component uses app.lawnchair.lawnicons.data.model, so a change to app.lawnchair.lawnicons.data.model can break app.lawnchair.lawnicons.data.model.Component, while a change to app.lawnchair.lawnicons.data.model.Component can't break app.lawnchair.lawnicons.data.model.
- Position
- Below the diagonal: app.lawnchair.lawnicons.data.model.Component uses a module listed above it, which is the healthy direction.
14→8 app.lawnchair.lawnicons.data.model.SearchMode uses app.lawnchair.lawnicons.data.model✕
- Connections
- 3 pairs of types, where a type in app.lawnchair.lawnicons.data.model.SearchMode uses a type in app.lawnchair.lawnicons.data.model.
- The types involved
app.lawnchair.lawnicons.data.model.SearchMode.COMPONENT→app.lawnchair.lawnicons.data.model.SearchModeapp.lawnchair.lawnicons.data.model.SearchMode.DRAWABLE→app.lawnchair.lawnicons.data.model.SearchModeapp.lawnchair.lawnicons.data.model.SearchMode.LABEL→app.lawnchair.lawnicons.data.model.SearchMode
- Direction
- app.lawnchair.lawnicons.data.model.SearchMode uses app.lawnchair.lawnicons.data.model, so a change to app.lawnchair.lawnicons.data.model can break app.lawnchair.lawnicons.data.model.SearchMode, while a change to app.lawnchair.lawnicons.data.model.SearchMode can't break app.lawnchair.lawnicons.data.model.
- Position
- Below the diagonal: app.lawnchair.lawnicons.data.model.SearchMode uses a module listed above it, which is the healthy direction.
15→8 app.lawnchair.lawnicons.data.repository.acknowledgements uses app.lawnchair.lawnicons.data.model✕
- Connections
- 4 pairs of types, where a type in app.lawnchair.lawnicons.data.repository.acknowledgements uses a type in app.lawnchair.lawnicons.data.model.
- The types involved
app.lawnchair.lawnicons.data.repository.acknowledgements.AssetOssLibraryDataSource→app.lawnchair.lawnicons.data.model.OssLibraryapp.lawnchair.lawnicons.data.repository.acknowledgements.OssLibraryDataSource→app.lawnchair.lawnicons.data.model.OssLibraryapp.lawnchair.lawnicons.data.repository.acknowledgements.OssLibraryRepository→app.lawnchair.lawnicons.data.model.OssLibraryapp.lawnchair.lawnicons.data.repository.acknowledgements.OssLibraryRepositoryImpl→app.lawnchair.lawnicons.data.model.OssLibrary
- Direction
- app.lawnchair.lawnicons.data.repository.acknowledgements uses app.lawnchair.lawnicons.data.model, so a change to app.lawnchair.lawnicons.data.model can break app.lawnchair.lawnicons.data.repository.acknowledgements, while a change to app.lawnchair.lawnicons.data.repository.acknowledgements can't break app.lawnchair.lawnicons.data.model.
- Position
- Below the diagonal: app.lawnchair.lawnicons.data.repository.acknowledgements uses a module listed above it, which is the healthy direction.
16→8 app.lawnchair.lawnicons.data.repository.iconrequest.IconRequestBundler uses app.lawnchair.lawnicons.data.model✕
- Connections
- 1 pair of types, where a type in app.lawnchair.lawnicons.data.repository.iconrequest.IconRequestBundler uses a type in app.lawnchair.lawnicons.data.model.
- The types involved
app.lawnchair.lawnicons.data.repository.iconrequest.IconRequestBundler.UniqueIconInfo→app.lawnchair.lawnicons.data.model.SystemIconInfo
- Direction
- app.lawnchair.lawnicons.data.repository.iconrequest.IconRequestBundler uses app.lawnchair.lawnicons.data.model, so a change to app.lawnchair.lawnicons.data.model can break app.lawnchair.lawnicons.data.repository.iconrequest.IconRequestBundler, while a change to app.lawnchair.lawnicons.data.repository.iconrequest.IconRequestBundler can't break app.lawnchair.lawnicons.data.model.
- Position
- Below the diagonal: app.lawnchair.lawnicons.data.repository.iconrequest.IconRequestBundler uses a module listed above it, which is the healthy direction.
17→8 app.lawnchair.lawnicons.ui uses app.lawnchair.lawnicons.data.model✕
- Connections
- 2 pairs of types, where a type in app.lawnchair.lawnicons.ui uses a type in app.lawnchair.lawnicons.data.model.
- The types involved
app.lawnchair.lawnicons.ui.LawniconsActions→app.lawnchair.lawnicons.data.model.IconInfoapp.lawnchair.lawnicons.ui.LawniconsKt→app.lawnchair.lawnicons.data.model.IconInfo
- Direction
- app.lawnchair.lawnicons.ui uses app.lawnchair.lawnicons.data.model, so a change to app.lawnchair.lawnicons.data.model can break app.lawnchair.lawnicons.ui, while a change to app.lawnchair.lawnicons.ui can't break app.lawnchair.lawnicons.data.model.
- Position
- Below the diagonal: app.lawnchair.lawnicons.ui uses a module listed above it, which is the healthy direction.
18→8 app.lawnchair.lawnicons.ui.components uses app.lawnchair.lawnicons.data.model✕
- Connections
- 1 pair of types, where a type in app.lawnchair.lawnicons.ui.components uses a type in app.lawnchair.lawnicons.data.model.
- The types involved
app.lawnchair.lawnicons.ui.components.AnnouncementCardKt→app.lawnchair.lawnicons.data.model.Announcement
- Direction
- app.lawnchair.lawnicons.ui.components uses app.lawnchair.lawnicons.data.model, so a change to app.lawnchair.lawnicons.data.model can break app.lawnchair.lawnicons.ui.components, while a change to app.lawnchair.lawnicons.ui.components can't break app.lawnchair.lawnicons.data.model.
- Position
- Below the diagonal: app.lawnchair.lawnicons.ui.components uses a module listed above it, which is the healthy direction.
19→8 app.lawnchair.lawnicons.ui.components.home.iconpreview uses app.lawnchair.lawnicons.data.model✕
- Connections
- 4 pairs of types, where a type in app.lawnchair.lawnicons.ui.components.home.iconpreview uses a type in app.lawnchair.lawnicons.data.model.
- The types involved
app.lawnchair.lawnicons.ui.components.home.iconpreview.IconInfoSheetKt→app.lawnchair.lawnicons.data.model.Componentapp.lawnchair.lawnicons.ui.components.home.iconpreview.IconInfoSheetKt→app.lawnchair.lawnicons.data.model.IconInfoapp.lawnchair.lawnicons.ui.components.home.iconpreview.IconPreviewGridKt→app.lawnchair.lawnicons.data.model.IconInfoapp.lawnchair.lawnicons.ui.components.home.iconpreview.IconPreviewKt→app.lawnchair.lawnicons.data.model.IconInfo
- Direction
- app.lawnchair.lawnicons.ui.components.home.iconpreview uses app.lawnchair.lawnicons.data.model, so a change to app.lawnchair.lawnicons.data.model can break app.lawnchair.lawnicons.ui.components.home.iconpreview, while a change to app.lawnchair.lawnicons.ui.components.home.iconpreview can't break app.lawnchair.lawnicons.data.model.
- Position
- Below the diagonal: app.lawnchair.lawnicons.ui.components.home.iconpreview uses a module listed above it, which is the healthy direction.
20→8 app.lawnchair.lawnicons.ui.components.home.search uses app.lawnchair.lawnicons.data.model✕
- Connections
- 4 pairs of types, where a type in app.lawnchair.lawnicons.ui.components.home.search uses a type in app.lawnchair.lawnicons.data.model.
- The types involved
app.lawnchair.lawnicons.ui.components.home.search.SearchContentsKt→app.lawnchair.lawnicons.data.model.IconInfoapp.lawnchair.lawnicons.ui.components.home.search.SearchContentsKt→app.lawnchair.lawnicons.data.model.SearchModeapp.lawnchair.lawnicons.ui.components.home.search.SearchState→app.lawnchair.lawnicons.data.model.SearchModeapp.lawnchair.lawnicons.ui.components.home.search.SearchStateKt→app.lawnchair.lawnicons.data.model.SearchMode
- Direction
- app.lawnchair.lawnicons.ui.components.home.search uses app.lawnchair.lawnicons.data.model, so a change to app.lawnchair.lawnicons.data.model can break app.lawnchair.lawnicons.ui.components.home.search, while a change to app.lawnchair.lawnicons.ui.components.home.search can't break app.lawnchair.lawnicons.data.model.
- Position
- Below the diagonal: app.lawnchair.lawnicons.ui.components.home.search uses a module listed above it, which is the healthy direction.
21→4 app.lawnchair.lawnicons.data.repository uses app.lawnchair.lawnicons.data.repository.BasePreferenceManager✕
- Connections
- 1 pair of types, where a type in app.lawnchair.lawnicons.data.repository uses a type in app.lawnchair.lawnicons.data.repository.BasePreferenceManager.
- The types involved
app.lawnchair.lawnicons.data.repository.PreferenceManager→app.lawnchair.lawnicons.data.repository.BasePreferenceManager.BoolPref
- Direction
- app.lawnchair.lawnicons.data.repository uses app.lawnchair.lawnicons.data.repository.BasePreferenceManager, so a change to app.lawnchair.lawnicons.data.repository.BasePreferenceManager can break app.lawnchair.lawnicons.data.repository, while a change to app.lawnchair.lawnicons.data.repository can't break app.lawnchair.lawnicons.data.repository.BasePreferenceManager.
- Position
- Below the diagonal: app.lawnchair.lawnicons.data.repository uses a module listed above it, which is the healthy direction.
21→8 app.lawnchair.lawnicons.data.repository uses app.lawnchair.lawnicons.data.model✕
- Connections
- 6 pairs of types, where a type in app.lawnchair.lawnicons.data.repository uses a type in app.lawnchair.lawnicons.data.model.
- The types involved
app.lawnchair.lawnicons.data.repository.AppFilterDiffIconDataSource→app.lawnchair.lawnicons.data.model.IconInfoapp.lawnchair.lawnicons.data.repository.AppFilterIconDataSource→app.lawnchair.lawnicons.data.model.IconInfoapp.lawnchair.lawnicons.data.repository.GitHubContributorsRepository→app.lawnchair.lawnicons.data.model.GitHubContributorapp.lawnchair.lawnicons.data.repository.IconDataSource→app.lawnchair.lawnicons.data.model.IconInfoapp.lawnchair.lawnicons.data.repository.NewIconsRepository→app.lawnchair.lawnicons.data.model.IconInfoModelapp.lawnchair.lawnicons.data.repository.NewIconsRepositoryImpl→app.lawnchair.lawnicons.data.model.IconInfoModel
- Direction
- app.lawnchair.lawnicons.data.repository uses app.lawnchair.lawnicons.data.model, so a change to app.lawnchair.lawnicons.data.model can break app.lawnchair.lawnicons.data.repository, while a change to app.lawnchair.lawnicons.data.repository can't break app.lawnchair.lawnicons.data.model.
- Position
- Below the diagonal: app.lawnchair.lawnicons.data.repository uses a module listed above it, which is the healthy direction.
21→11 app.lawnchair.lawnicons.data.repository uses app.lawnchair.lawnicons.data.api✕
- Connections
- 1 pair of types, where a type in app.lawnchair.lawnicons.data.repository uses a type in app.lawnchair.lawnicons.data.api.
- The types involved
app.lawnchair.lawnicons.data.repository.GitHubContributorsRepository→app.lawnchair.lawnicons.data.api.GitHubContributorsAPI
- Direction
- app.lawnchair.lawnicons.data.repository uses app.lawnchair.lawnicons.data.api, so a change to app.lawnchair.lawnicons.data.api can break app.lawnchair.lawnicons.data.repository, while a change to app.lawnchair.lawnicons.data.repository can't break app.lawnchair.lawnicons.data.api.
- Position
- Below the diagonal: app.lawnchair.lawnicons.data.repository uses a module listed above it, which is the healthy direction.
22→18 app.lawnchair.lawnicons.ui.components.SystemNavigation uses app.lawnchair.lawnicons.ui.components✕
- Connections
- 3 pairs of types, where a type in app.lawnchair.lawnicons.ui.components.SystemNavigation uses a type in app.lawnchair.lawnicons.ui.components.
- The types involved
app.lawnchair.lawnicons.ui.components.SystemNavigation.GESTURE→app.lawnchair.lawnicons.ui.components.SystemNavigationapp.lawnchair.lawnicons.ui.components.SystemNavigation.THREE_BUTTON→app.lawnchair.lawnicons.ui.components.SystemNavigationapp.lawnchair.lawnicons.ui.components.SystemNavigation.TWO_BUTTON→app.lawnchair.lawnicons.ui.components.SystemNavigation
- Direction
- app.lawnchair.lawnicons.ui.components.SystemNavigation uses app.lawnchair.lawnicons.ui.components, so a change to app.lawnchair.lawnicons.ui.components can break app.lawnchair.lawnicons.ui.components.SystemNavigation, while a change to app.lawnchair.lawnicons.ui.components.SystemNavigation can't break app.lawnchair.lawnicons.ui.components.
- Position
- Below the diagonal: app.lawnchair.lawnicons.ui.components.SystemNavigation uses a module listed above it, which is the healthy direction.
23→8 app.lawnchair.lawnicons.ui.components.home uses app.lawnchair.lawnicons.data.model✕
- Connections
- 1 pair of types, where a type in app.lawnchair.lawnicons.ui.components.home uses a type in app.lawnchair.lawnicons.data.model.
- The types involved
app.lawnchair.lawnicons.ui.components.home.HomeTopBarKt→app.lawnchair.lawnicons.data.model.IconInfoModel
- Direction
- app.lawnchair.lawnicons.ui.components.home uses app.lawnchair.lawnicons.data.model, so a change to app.lawnchair.lawnicons.data.model can break app.lawnchair.lawnicons.ui.components.home, while a change to app.lawnchair.lawnicons.ui.components.home can't break app.lawnchair.lawnicons.data.model.
- Position
- Below the diagonal: app.lawnchair.lawnicons.ui.components.home uses a module listed above it, which is the healthy direction.
23→20 app.lawnchair.lawnicons.ui.components.home uses app.lawnchair.lawnicons.ui.components.home.search✕
- Connections
- 1 pair of types, where a type in app.lawnchair.lawnicons.ui.components.home uses a type in app.lawnchair.lawnicons.ui.components.home.search.
- The types involved
app.lawnchair.lawnicons.ui.components.home.HomeTopBarKt→app.lawnchair.lawnicons.ui.components.home.search.SearchState
- Direction
- app.lawnchair.lawnicons.ui.components.home uses app.lawnchair.lawnicons.ui.components.home.search, so a change to app.lawnchair.lawnicons.ui.components.home.search can break app.lawnchair.lawnicons.ui.components.home, while a change to app.lawnchair.lawnicons.ui.components.home can't break app.lawnchair.lawnicons.ui.components.home.search.
- Position
- Below the diagonal: app.lawnchair.lawnicons.ui.components.home uses a module listed above it, which is the healthy direction.
24→8 app.lawnchair.lawnicons.ui.destination.acknowledgements uses app.lawnchair.lawnicons.data.model✕
- Connections
- 2 pairs of types, where a type in app.lawnchair.lawnicons.ui.destination.acknowledgements uses a type in app.lawnchair.lawnicons.data.model.
- The types involved
app.lawnchair.lawnicons.ui.destination.acknowledgements.AcknowledgementsKt→app.lawnchair.lawnicons.data.model.OssLibraryapp.lawnchair.lawnicons.ui.destination.acknowledgements.AcknowledgementsViewModel→app.lawnchair.lawnicons.data.model.OssLibrary
- Direction
- app.lawnchair.lawnicons.ui.destination.acknowledgements uses app.lawnchair.lawnicons.data.model, so a change to app.lawnchair.lawnicons.data.model can break app.lawnchair.lawnicons.ui.destination.acknowledgements, while a change to app.lawnchair.lawnicons.ui.destination.acknowledgements can't break app.lawnchair.lawnicons.data.model.
- Position
- Below the diagonal: app.lawnchair.lawnicons.ui.destination.acknowledgements uses a module listed above it, which is the healthy direction.
24→15 app.lawnchair.lawnicons.ui.destination.acknowledgements uses app.lawnchair.lawnicons.data.repository.acknowledgements✕
- Connections
- 1 pair of types, where a type in app.lawnchair.lawnicons.ui.destination.acknowledgements uses a type in app.lawnchair.lawnicons.data.repository.acknowledgements.
- The types involved
app.lawnchair.lawnicons.ui.destination.acknowledgements.AcknowledgementsViewModel→app.lawnchair.lawnicons.data.repository.acknowledgements.OssLibraryRepository
- Direction
- app.lawnchair.lawnicons.ui.destination.acknowledgements uses app.lawnchair.lawnicons.data.repository.acknowledgements, so a change to app.lawnchair.lawnicons.data.repository.acknowledgements can break app.lawnchair.lawnicons.ui.destination.acknowledgements, while a change to app.lawnchair.lawnicons.ui.destination.acknowledgements can't break app.lawnchair.lawnicons.data.repository.acknowledgements.
- Position
- Below the diagonal: app.lawnchair.lawnicons.ui.destination.acknowledgements uses a module listed above it, which is the healthy direction.
25→8 app.lawnchair.lawnicons.data.repository.home uses app.lawnchair.lawnicons.data.model✕
- Connections
- 7 pairs of types, where a type in app.lawnchair.lawnicons.data.repository.home uses a type in app.lawnchair.lawnicons.data.model.
- The types involved
app.lawnchair.lawnicons.data.repository.home.AnnouncementsRepository→app.lawnchair.lawnicons.data.model.Announcementapp.lawnchair.lawnicons.data.repository.home.GetIconInfoKt→app.lawnchair.lawnicons.data.model.IconInfoapp.lawnchair.lawnicons.data.repository.home.IconInfoGroup→app.lawnchair.lawnicons.data.model.LabelAndComponentapp.lawnchair.lawnicons.data.repository.home.IconRepository→app.lawnchair.lawnicons.data.model.IconInfoModelapp.lawnchair.lawnicons.data.repository.home.IconRepository→app.lawnchair.lawnicons.data.model.SearchModeapp.lawnchair.lawnicons.data.repository.home.IconRepositoryImpl→app.lawnchair.lawnicons.data.model.IconInfoModelapp.lawnchair.lawnicons.data.repository.home.IconRepositoryImpl→app.lawnchair.lawnicons.data.model.SearchMode
- Direction
- app.lawnchair.lawnicons.data.repository.home uses app.lawnchair.lawnicons.data.model, so a change to app.lawnchair.lawnicons.data.model can break app.lawnchair.lawnicons.data.repository.home, while a change to app.lawnchair.lawnicons.data.repository.home can't break app.lawnchair.lawnicons.data.model.
- Position
- Below the diagonal: app.lawnchair.lawnicons.data.repository.home uses a module listed above it, which is the healthy direction.
25→11 app.lawnchair.lawnicons.data.repository.home uses app.lawnchair.lawnicons.data.api✕
- Connections
- 1 pair of types, where a type in app.lawnchair.lawnicons.data.repository.home uses a type in app.lawnchair.lawnicons.data.api.
- The types involved
app.lawnchair.lawnicons.data.repository.home.AnnouncementsRepository→app.lawnchair.lawnicons.data.api.AnnouncementsAPI
- Direction
- app.lawnchair.lawnicons.data.repository.home uses app.lawnchair.lawnicons.data.api, so a change to app.lawnchair.lawnicons.data.api can break app.lawnchair.lawnicons.data.repository.home, while a change to app.lawnchair.lawnicons.data.repository.home can't break app.lawnchair.lawnicons.data.api.
- Position
- Below the diagonal: app.lawnchair.lawnicons.data.repository.home uses a module listed above it, which is the healthy direction.
25→21 app.lawnchair.lawnicons.data.repository.home uses app.lawnchair.lawnicons.data.repository✕
- Connections
- 1 pair of types, where a type in app.lawnchair.lawnicons.data.repository.home uses a type in app.lawnchair.lawnicons.data.repository.
- The types involved
app.lawnchair.lawnicons.data.repository.home.IconRepositoryImpl→app.lawnchair.lawnicons.data.repository.IconDataSource
- Direction
- app.lawnchair.lawnicons.data.repository.home uses app.lawnchair.lawnicons.data.repository, so a change to app.lawnchair.lawnicons.data.repository can break app.lawnchair.lawnicons.data.repository.home, while a change to app.lawnchair.lawnicons.data.repository.home can't break app.lawnchair.lawnicons.data.repository.
- Position
- Below the diagonal: app.lawnchair.lawnicons.data.repository.home uses a module listed above it, which is the healthy direction.
26→8 app.lawnchair.lawnicons.data.repository.iconrequest uses app.lawnchair.lawnicons.data.model✕
- Connections
- 13 pairs of types, where a type in app.lawnchair.lawnicons.data.repository.iconrequest uses a type in app.lawnchair.lawnicons.data.model.
- The types involved
app.lawnchair.lawnicons.data.repository.iconrequest.ArcticonsDashboardHandler→app.lawnchair.lawnicons.data.model.IconRequestDataapp.lawnchair.lawnicons.data.repository.iconrequest.GetSystemPackageListKt→app.lawnchair.lawnicons.data.model.IconInfoapp.lawnchair.lawnicons.data.repository.iconrequest.GetSystemPackageListKt→app.lawnchair.lawnicons.data.model.SystemIconInfoapp.lawnchair.lawnicons.data.repository.iconrequest.IconRequestBundler→app.lawnchair.lawnicons.data.model.SystemIconInfoapp.lawnchair.lawnicons.data.repository.iconrequest.IconRequestBundlerKt→app.lawnchair.lawnicons.data.model.SystemIconInfoapp.lawnchair.lawnicons.data.repository.iconrequest.IconRequestHandler→app.lawnchair.lawnicons.data.model.IconRequestDataapp.lawnchair.lawnicons.data.repository.iconrequest.IconRequestRepository→app.lawnchair.lawnicons.data.model.IconRequestModelapp.lawnchair.lawnicons.data.repository.iconrequest.IconRequestRepository→app.lawnchair.lawnicons.data.model.SystemIconInfoapp.lawnchair.lawnicons.data.repository.iconrequest.IconRequestRepositoryImpl→app.lawnchair.lawnicons.data.model.IconInfoapp.lawnchair.lawnicons.data.repository.iconrequest.IconRequestRepositoryImpl→app.lawnchair.lawnicons.data.model.IconRequestModelapp.lawnchair.lawnicons.data.repository.iconrequest.IconRequestRepositoryImpl→app.lawnchair.lawnicons.data.model.SystemIconInfoapp.lawnchair.lawnicons.data.repository.iconrequest.IconRequestRepositoryKt→app.lawnchair.lawnicons.data.model.IconInfoapp.lawnchair.lawnicons.data.repository.iconrequest.IconRequestRepositoryKt→app.lawnchair.lawnicons.data.model.SystemIconInfo
- Direction
- app.lawnchair.lawnicons.data.repository.iconrequest uses app.lawnchair.lawnicons.data.model, so a change to app.lawnchair.lawnicons.data.model can break app.lawnchair.lawnicons.data.repository.iconrequest, while a change to app.lawnchair.lawnicons.data.repository.iconrequest can't break app.lawnchair.lawnicons.data.model.
- Position
- Below the diagonal: app.lawnchair.lawnicons.data.repository.iconrequest uses a module listed above it, which is the healthy direction.
26→11 app.lawnchair.lawnicons.data.repository.iconrequest uses app.lawnchair.lawnicons.data.api✕
- Connections
- 1 pair of types, where a type in app.lawnchair.lawnicons.data.repository.iconrequest uses a type in app.lawnchair.lawnicons.data.api.
- The types involved
app.lawnchair.lawnicons.data.repository.iconrequest.IconRequestRepositoryImpl→app.lawnchair.lawnicons.data.api.IconRequestSettingsAPI
- Direction
- app.lawnchair.lawnicons.data.repository.iconrequest uses app.lawnchair.lawnicons.data.api, so a change to app.lawnchair.lawnicons.data.api can break app.lawnchair.lawnicons.data.repository.iconrequest, while a change to app.lawnchair.lawnicons.data.repository.iconrequest can't break app.lawnchair.lawnicons.data.api.
- Position
- Below the diagonal: app.lawnchair.lawnicons.data.repository.iconrequest uses a module listed above it, which is the healthy direction.
26→16 app.lawnchair.lawnicons.data.repository.iconrequest uses app.lawnchair.lawnicons.data.repository.iconrequest.IconRequestBundler✕
- Connections
- 1 pair of types, where a type in app.lawnchair.lawnicons.data.repository.iconrequest uses a type in app.lawnchair.lawnicons.data.repository.iconrequest.IconRequestBundler.
- The types involved
app.lawnchair.lawnicons.data.repository.iconrequest.IconRequestBundler→app.lawnchair.lawnicons.data.repository.iconrequest.IconRequestBundler.UniqueIconInfo
- Direction
- app.lawnchair.lawnicons.data.repository.iconrequest uses app.lawnchair.lawnicons.data.repository.iconrequest.IconRequestBundler, so a change to app.lawnchair.lawnicons.data.repository.iconrequest.IconRequestBundler can break app.lawnchair.lawnicons.data.repository.iconrequest, while a change to app.lawnchair.lawnicons.data.repository.iconrequest can't break app.lawnchair.lawnicons.data.repository.iconrequest.IconRequestBundler.
- Position
- Below the diagonal: app.lawnchair.lawnicons.data.repository.iconrequest uses a module listed above it, which is the healthy direction.
26→21 app.lawnchair.lawnicons.data.repository.iconrequest uses app.lawnchair.lawnicons.data.repository✕
- Connections
- 2 pairs of types, where a type in app.lawnchair.lawnicons.data.repository.iconrequest uses a type in app.lawnchair.lawnicons.data.repository.
- The types involved
app.lawnchair.lawnicons.data.repository.iconrequest.IconRequestRepositoryImpl→app.lawnchair.lawnicons.data.repository.IconDataSourceapp.lawnchair.lawnicons.data.repository.iconrequest.IconRequestRepositoryImpl→app.lawnchair.lawnicons.data.repository.PreferenceManager
- Direction
- app.lawnchair.lawnicons.data.repository.iconrequest uses app.lawnchair.lawnicons.data.repository, so a change to app.lawnchair.lawnicons.data.repository can break app.lawnchair.lawnicons.data.repository.iconrequest, while a change to app.lawnchair.lawnicons.data.repository.iconrequest can't break app.lawnchair.lawnicons.data.repository.
- Position
- Below the diagonal: app.lawnchair.lawnicons.data.repository.iconrequest uses a module listed above it, which is the healthy direction.
27→11 app.lawnchair.lawnicons.di uses app.lawnchair.lawnicons.data.api✕
- Connections
- 3 pairs of types, where a type in app.lawnchair.lawnicons.di uses a type in app.lawnchair.lawnicons.data.api.
- The types involved
app.lawnchair.lawnicons.di.GithubApiModule→app.lawnchair.lawnicons.data.api.GitHubContributorsAPIapp.lawnchair.lawnicons.di.WebsiteApiModule→app.lawnchair.lawnicons.data.api.AnnouncementsAPIapp.lawnchair.lawnicons.di.WebsiteApiModule→app.lawnchair.lawnicons.data.api.IconRequestSettingsAPI
- Direction
- app.lawnchair.lawnicons.di uses app.lawnchair.lawnicons.data.api, so a change to app.lawnchair.lawnicons.data.api can break app.lawnchair.lawnicons.di, while a change to app.lawnchair.lawnicons.di can't break app.lawnchair.lawnicons.data.api.
- Position
- Below the diagonal: app.lawnchair.lawnicons.di uses a module listed above it, which is the healthy direction.
27→21 app.lawnchair.lawnicons.di uses app.lawnchair.lawnicons.data.repository✕
- Connections
- 1 pair of types, where a type in app.lawnchair.lawnicons.di uses a type in app.lawnchair.lawnicons.data.repository.
- The types involved
app.lawnchair.lawnicons.di.PreferencesModule→app.lawnchair.lawnicons.data.repository.PreferenceStore
- Direction
- app.lawnchair.lawnicons.di uses app.lawnchair.lawnicons.data.repository, so a change to app.lawnchair.lawnicons.data.repository can break app.lawnchair.lawnicons.di, while a change to app.lawnchair.lawnicons.di can't break app.lawnchair.lawnicons.data.repository.
- Position
- Below the diagonal: app.lawnchair.lawnicons.di uses a module listed above it, which is the healthy direction.
28→8 app.lawnchair.lawnicons.ui.destination.contributors uses app.lawnchair.lawnicons.data.model✕
- Connections
- 2 pairs of types, where a type in app.lawnchair.lawnicons.ui.destination.contributors uses a type in app.lawnchair.lawnicons.data.model.
- The types involved
app.lawnchair.lawnicons.ui.destination.contributors.ContributorsKt→app.lawnchair.lawnicons.data.model.GitHubContributorapp.lawnchair.lawnicons.ui.destination.contributors.ContributorsViewModelState→app.lawnchair.lawnicons.data.model.GitHubContributor
- Direction
- app.lawnchair.lawnicons.ui.destination.contributors uses app.lawnchair.lawnicons.data.model, so a change to app.lawnchair.lawnicons.data.model can break app.lawnchair.lawnicons.ui.destination.contributors, while a change to app.lawnchair.lawnicons.ui.destination.contributors can't break app.lawnchair.lawnicons.data.model.
- Position
- Below the diagonal: app.lawnchair.lawnicons.ui.destination.contributors uses a module listed above it, which is the healthy direction.
28→21 app.lawnchair.lawnicons.ui.destination.contributors uses app.lawnchair.lawnicons.data.repository✕
- Connections
- 1 pair of types, where a type in app.lawnchair.lawnicons.ui.destination.contributors uses a type in app.lawnchair.lawnicons.data.repository.
- The types involved
app.lawnchair.lawnicons.ui.destination.contributors.ContributorsViewModel→app.lawnchair.lawnicons.data.repository.GitHubContributorsRepository
- Direction
- app.lawnchair.lawnicons.ui.destination.contributors uses app.lawnchair.lawnicons.data.repository, so a change to app.lawnchair.lawnicons.data.repository can break app.lawnchair.lawnicons.ui.destination.contributors, while a change to app.lawnchair.lawnicons.ui.destination.contributors can't break app.lawnchair.lawnicons.data.repository.
- Position
- Below the diagonal: app.lawnchair.lawnicons.ui.destination.contributors uses a module listed above it, which is the healthy direction.
29→8 app.lawnchair.lawnicons.ui.destination.newicons uses app.lawnchair.lawnicons.data.model✕
- Connections
- 2 pairs of types, where a type in app.lawnchair.lawnicons.ui.destination.newicons uses a type in app.lawnchair.lawnicons.data.model.
- The types involved
app.lawnchair.lawnicons.ui.destination.newicons.NewIconsKt→app.lawnchair.lawnicons.data.model.IconInfoModelapp.lawnchair.lawnicons.ui.destination.newicons.NewIconsViewModel→app.lawnchair.lawnicons.data.model.IconInfoModel
- Direction
- app.lawnchair.lawnicons.ui.destination.newicons uses app.lawnchair.lawnicons.data.model, so a change to app.lawnchair.lawnicons.data.model can break app.lawnchair.lawnicons.ui.destination.newicons, while a change to app.lawnchair.lawnicons.ui.destination.newicons can't break app.lawnchair.lawnicons.data.model.
- Position
- Below the diagonal: app.lawnchair.lawnicons.ui.destination.newicons uses a module listed above it, which is the healthy direction.
29→21 app.lawnchair.lawnicons.ui.destination.newicons uses app.lawnchair.lawnicons.data.repository✕
- Connections
- 1 pair of types, where a type in app.lawnchair.lawnicons.ui.destination.newicons uses a type in app.lawnchair.lawnicons.data.repository.
- The types involved
app.lawnchair.lawnicons.ui.destination.newicons.NewIconsViewModel→app.lawnchair.lawnicons.data.repository.NewIconsRepository
- Direction
- app.lawnchair.lawnicons.ui.destination.newicons uses app.lawnchair.lawnicons.data.repository, so a change to app.lawnchair.lawnicons.data.repository can break app.lawnchair.lawnicons.ui.destination.newicons, while a change to app.lawnchair.lawnicons.ui.destination.newicons can't break app.lawnchair.lawnicons.data.repository.
- Position
- Below the diagonal: app.lawnchair.lawnicons.ui.destination.newicons uses a module listed above it, which is the healthy direction.
30→8 app.lawnchair.lawnicons uses app.lawnchair.lawnicons.data.model✕
- Connections
- 1 pair of types, where a type in app.lawnchair.lawnicons uses a type in app.lawnchair.lawnicons.data.model.
- The types involved
app.lawnchair.lawnicons.MainActivity→app.lawnchair.lawnicons.data.model.IconInfo
- Direction
- app.lawnchair.lawnicons uses app.lawnchair.lawnicons.data.model, so a change to app.lawnchair.lawnicons.data.model can break app.lawnchair.lawnicons, while a change to app.lawnchair.lawnicons can't break app.lawnchair.lawnicons.data.model.
- Position
- Below the diagonal: app.lawnchair.lawnicons uses a module listed above it, which is the healthy direction.
30→27 app.lawnchair.lawnicons uses app.lawnchair.lawnicons.di✕
- Connections
- 2 pairs of types, where a type in app.lawnchair.lawnicons uses a type in app.lawnchair.lawnicons.di.
- The types involved
app.lawnchair.lawnicons.LawniconsGraph→app.lawnchair.lawnicons.di.AppInitializerapp.lawnchair.lawnicons.LawniconsGraph→app.lawnchair.lawnicons.di.MetroViewModelFactoryImpl
- Direction
- app.lawnchair.lawnicons uses app.lawnchair.lawnicons.di, so a change to app.lawnchair.lawnicons.di can break app.lawnchair.lawnicons, while a change to app.lawnchair.lawnicons can't break app.lawnchair.lawnicons.di.
- Position
- Below the diagonal: app.lawnchair.lawnicons uses a module listed above it, which is the healthy direction.
31→27 app.lawnchair.lawnicons.data.repository.bugreport uses app.lawnchair.lawnicons.di✕
- Connections
- 1 pair of types, where a type in app.lawnchair.lawnicons.data.repository.bugreport uses a type in app.lawnchair.lawnicons.di.
- The types involved
app.lawnchair.lawnicons.data.repository.bugreport.LawniconsBugReporter→app.lawnchair.lawnicons.di.AppInitializer
- Direction
- app.lawnchair.lawnicons.data.repository.bugreport uses app.lawnchair.lawnicons.di, so a change to app.lawnchair.lawnicons.di can break app.lawnchair.lawnicons.data.repository.bugreport, while a change to app.lawnchair.lawnicons.data.repository.bugreport can't break app.lawnchair.lawnicons.di.
- Position
- Below the diagonal: app.lawnchair.lawnicons.data.repository.bugreport uses a module listed above it, which is the healthy direction.
32→8 app.lawnchair.lawnicons.ui.destination.contributors.ContributorsUiState uses app.lawnchair.lawnicons.data.model✕
- Connections
- 1 pair of types, where a type in app.lawnchair.lawnicons.ui.destination.contributors.ContributorsUiState uses a type in app.lawnchair.lawnicons.data.model.
- The types involved
app.lawnchair.lawnicons.ui.destination.contributors.ContributorsUiState.Success→app.lawnchair.lawnicons.data.model.GitHubContributor
- Direction
- app.lawnchair.lawnicons.ui.destination.contributors.ContributorsUiState uses app.lawnchair.lawnicons.data.model, so a change to app.lawnchair.lawnicons.data.model can break app.lawnchair.lawnicons.ui.destination.contributors.ContributorsUiState, while a change to app.lawnchair.lawnicons.ui.destination.contributors.ContributorsUiState can't break app.lawnchair.lawnicons.data.model.
- Position
- Below the diagonal: app.lawnchair.lawnicons.ui.destination.contributors.ContributorsUiState uses a module listed above it, which is the healthy direction.
32→28 app.lawnchair.lawnicons.ui.destination.contributors.ContributorsUiState uses app.lawnchair.lawnicons.ui.destination.contributors✕
- Connections
- 3 pairs of types, where a type in app.lawnchair.lawnicons.ui.destination.contributors.ContributorsUiState uses a type in app.lawnchair.lawnicons.ui.destination.contributors.
- The types involved
app.lawnchair.lawnicons.ui.destination.contributors.ContributorsUiState.Error→app.lawnchair.lawnicons.ui.destination.contributors.ContributorsUiStateapp.lawnchair.lawnicons.ui.destination.contributors.ContributorsUiState.Loading→app.lawnchair.lawnicons.ui.destination.contributors.ContributorsUiStateapp.lawnchair.lawnicons.ui.destination.contributors.ContributorsUiState.Success→app.lawnchair.lawnicons.ui.destination.contributors.ContributorsUiState
- Direction
- app.lawnchair.lawnicons.ui.destination.contributors.ContributorsUiState uses app.lawnchair.lawnicons.ui.destination.contributors, so a change to app.lawnchair.lawnicons.ui.destination.contributors can break app.lawnchair.lawnicons.ui.destination.contributors.ContributorsUiState, while a change to app.lawnchair.lawnicons.ui.destination.contributors.ContributorsUiState can't break app.lawnchair.lawnicons.ui.destination.contributors.
- Position
- Below the diagonal: app.lawnchair.lawnicons.ui.destination.contributors.ContributorsUiState uses a module listed above it, which is the healthy direction.
33→4 app.lawnchair.lawnicons.ui.destination.debugmenu uses app.lawnchair.lawnicons.data.repository.BasePreferenceManager✕
- Connections
- 1 pair of types, where a type in app.lawnchair.lawnicons.ui.destination.debugmenu uses a type in app.lawnchair.lawnicons.data.repository.BasePreferenceManager.
- The types involved
app.lawnchair.lawnicons.ui.destination.debugmenu.DebugMenuKt→app.lawnchair.lawnicons.data.repository.BasePreferenceManager.BoolPref
- Direction
- app.lawnchair.lawnicons.ui.destination.debugmenu uses app.lawnchair.lawnicons.data.repository.BasePreferenceManager, so a change to app.lawnchair.lawnicons.data.repository.BasePreferenceManager can break app.lawnchair.lawnicons.ui.destination.debugmenu, while a change to app.lawnchair.lawnicons.ui.destination.debugmenu can't break app.lawnchair.lawnicons.data.repository.BasePreferenceManager.
- Position
- Below the diagonal: app.lawnchair.lawnicons.ui.destination.debugmenu uses a module listed above it, which is the healthy direction.
33→8 app.lawnchair.lawnicons.ui.destination.debugmenu uses app.lawnchair.lawnicons.data.model✕
- Connections
- 4 pairs of types, where a type in app.lawnchair.lawnicons.ui.destination.debugmenu uses a type in app.lawnchair.lawnicons.data.model.
- The types involved
app.lawnchair.lawnicons.ui.destination.debugmenu.DebugMenuKt→app.lawnchair.lawnicons.data.model.IconInfoModelapp.lawnchair.lawnicons.ui.destination.debugmenu.DebugMenuKt→app.lawnchair.lawnicons.data.model.IconRequestModelapp.lawnchair.lawnicons.ui.destination.debugmenu.DebugMenuViewModel→app.lawnchair.lawnicons.data.model.IconInfoModelapp.lawnchair.lawnicons.ui.destination.debugmenu.DebugMenuViewModel→app.lawnchair.lawnicons.data.model.IconRequestModel
- Direction
- app.lawnchair.lawnicons.ui.destination.debugmenu uses app.lawnchair.lawnicons.data.model, so a change to app.lawnchair.lawnicons.data.model can break app.lawnchair.lawnicons.ui.destination.debugmenu, while a change to app.lawnchair.lawnicons.ui.destination.debugmenu can't break app.lawnchair.lawnicons.data.model.
- Position
- Below the diagonal: app.lawnchair.lawnicons.ui.destination.debugmenu uses a module listed above it, which is the healthy direction.
33→21 app.lawnchair.lawnicons.ui.destination.debugmenu uses app.lawnchair.lawnicons.data.repository✕
- Connections
- 2 pairs of types, where a type in app.lawnchair.lawnicons.ui.destination.debugmenu uses a type in app.lawnchair.lawnicons.data.repository.
- The types involved
app.lawnchair.lawnicons.ui.destination.debugmenu.DebugMenuViewModel→app.lawnchair.lawnicons.data.repository.NewIconsRepositoryapp.lawnchair.lawnicons.ui.destination.debugmenu.DebugMenuViewModel→app.lawnchair.lawnicons.data.repository.PreferenceManager
- Direction
- app.lawnchair.lawnicons.ui.destination.debugmenu uses app.lawnchair.lawnicons.data.repository, so a change to app.lawnchair.lawnicons.data.repository can break app.lawnchair.lawnicons.ui.destination.debugmenu, while a change to app.lawnchair.lawnicons.ui.destination.debugmenu can't break app.lawnchair.lawnicons.data.repository.
- Position
- Below the diagonal: app.lawnchair.lawnicons.ui.destination.debugmenu uses a module listed above it, which is the healthy direction.
33→25 app.lawnchair.lawnicons.ui.destination.debugmenu uses app.lawnchair.lawnicons.data.repository.home✕
- Connections
- 1 pair of types, where a type in app.lawnchair.lawnicons.ui.destination.debugmenu uses a type in app.lawnchair.lawnicons.data.repository.home.
- The types involved
app.lawnchair.lawnicons.ui.destination.debugmenu.DebugMenuViewModel→app.lawnchair.lawnicons.data.repository.home.IconRepository
- Direction
- app.lawnchair.lawnicons.ui.destination.debugmenu uses app.lawnchair.lawnicons.data.repository.home, so a change to app.lawnchair.lawnicons.data.repository.home can break app.lawnchair.lawnicons.ui.destination.debugmenu, while a change to app.lawnchair.lawnicons.ui.destination.debugmenu can't break app.lawnchair.lawnicons.data.repository.home.
- Position
- Below the diagonal: app.lawnchair.lawnicons.ui.destination.debugmenu uses a module listed above it, which is the healthy direction.
33→26 app.lawnchair.lawnicons.ui.destination.debugmenu uses app.lawnchair.lawnicons.data.repository.iconrequest✕
- Connections
- 1 pair of types, where a type in app.lawnchair.lawnicons.ui.destination.debugmenu uses a type in app.lawnchair.lawnicons.data.repository.iconrequest.
- The types involved
app.lawnchair.lawnicons.ui.destination.debugmenu.DebugMenuViewModel→app.lawnchair.lawnicons.data.repository.iconrequest.IconRequestRepository
- Direction
- app.lawnchair.lawnicons.ui.destination.debugmenu uses app.lawnchair.lawnicons.data.repository.iconrequest, so a change to app.lawnchair.lawnicons.data.repository.iconrequest can break app.lawnchair.lawnicons.ui.destination.debugmenu, while a change to app.lawnchair.lawnicons.ui.destination.debugmenu can't break app.lawnchair.lawnicons.data.repository.iconrequest.
- Position
- Below the diagonal: app.lawnchair.lawnicons.ui.destination.debugmenu uses a module listed above it, which is the healthy direction.
34→8 app.lawnchair.lawnicons.ui.destination.home uses app.lawnchair.lawnicons.data.model✕
- Connections
- 8 pairs of types, where a type in app.lawnchair.lawnicons.ui.destination.home uses a type in app.lawnchair.lawnicons.data.model.
- The types involved
app.lawnchair.lawnicons.ui.destination.home.HomeActions→app.lawnchair.lawnicons.data.model.SearchModeapp.lawnchair.lawnicons.ui.destination.home.HomeSearchUiState→app.lawnchair.lawnicons.data.model.IconInfoModelapp.lawnchair.lawnicons.ui.destination.home.HomeSearchUiState→app.lawnchair.lawnicons.data.model.SearchModeapp.lawnchair.lawnicons.ui.destination.home.HomeViewModel→app.lawnchair.lawnicons.data.model.IconInfoModelapp.lawnchair.lawnicons.ui.destination.home.HomeViewModel→app.lawnchair.lawnicons.data.model.SearchModeapp.lawnchair.lawnicons.ui.destination.home.HomeViewModelImpl→app.lawnchair.lawnicons.data.model.Announcementapp.lawnchair.lawnicons.ui.destination.home.HomeViewModelImpl→app.lawnchair.lawnicons.data.model.IconInfoModelapp.lawnchair.lawnicons.ui.destination.home.HomeViewModelImpl→app.lawnchair.lawnicons.data.model.SearchMode
- Direction
- app.lawnchair.lawnicons.ui.destination.home uses app.lawnchair.lawnicons.data.model, so a change to app.lawnchair.lawnicons.data.model can break app.lawnchair.lawnicons.ui.destination.home, while a change to app.lawnchair.lawnicons.ui.destination.home can't break app.lawnchair.lawnicons.data.model.
- Position
- Below the diagonal: app.lawnchair.lawnicons.ui.destination.home uses a module listed above it, which is the healthy direction.
34→21 app.lawnchair.lawnicons.ui.destination.home uses app.lawnchair.lawnicons.data.repository✕
- Connections
- 2 pairs of types, where a type in app.lawnchair.lawnicons.ui.destination.home uses a type in app.lawnchair.lawnicons.data.repository.
- The types involved
app.lawnchair.lawnicons.ui.destination.home.HomeViewModelImpl→app.lawnchair.lawnicons.data.repository.NewIconsRepositoryapp.lawnchair.lawnicons.ui.destination.home.HomeViewModelImpl→app.lawnchair.lawnicons.data.repository.PreferenceManager
- Direction
- app.lawnchair.lawnicons.ui.destination.home uses app.lawnchair.lawnicons.data.repository, so a change to app.lawnchair.lawnicons.data.repository can break app.lawnchair.lawnicons.ui.destination.home, while a change to app.lawnchair.lawnicons.ui.destination.home can't break app.lawnchair.lawnicons.data.repository.
- Position
- Below the diagonal: app.lawnchair.lawnicons.ui.destination.home uses a module listed above it, which is the healthy direction.
34→25 app.lawnchair.lawnicons.ui.destination.home uses app.lawnchair.lawnicons.data.repository.home✕
- Connections
- 2 pairs of types, where a type in app.lawnchair.lawnicons.ui.destination.home uses a type in app.lawnchair.lawnicons.data.repository.home.
- The types involved
app.lawnchair.lawnicons.ui.destination.home.HomeViewModelImpl→app.lawnchair.lawnicons.data.repository.home.AnnouncementsRepositoryapp.lawnchair.lawnicons.ui.destination.home.HomeViewModelImpl→app.lawnchair.lawnicons.data.repository.home.IconRepository
- Direction
- app.lawnchair.lawnicons.ui.destination.home uses app.lawnchair.lawnicons.data.repository.home, so a change to app.lawnchair.lawnicons.data.repository.home can break app.lawnchair.lawnicons.ui.destination.home, while a change to app.lawnchair.lawnicons.ui.destination.home can't break app.lawnchair.lawnicons.data.repository.home.
- Position
- Below the diagonal: app.lawnchair.lawnicons.ui.destination.home uses a module listed above it, which is the healthy direction.
34→26 app.lawnchair.lawnicons.ui.destination.home uses app.lawnchair.lawnicons.data.repository.iconrequest✕
- Connections
- 1 pair of types, where a type in app.lawnchair.lawnicons.ui.destination.home uses a type in app.lawnchair.lawnicons.data.repository.iconrequest.
- The types involved
app.lawnchair.lawnicons.ui.destination.home.HomeViewModelImpl→app.lawnchair.lawnicons.data.repository.iconrequest.IconRequestRepository
- Direction
- app.lawnchair.lawnicons.ui.destination.home uses app.lawnchair.lawnicons.data.repository.iconrequest, so a change to app.lawnchair.lawnicons.data.repository.iconrequest can break app.lawnchair.lawnicons.ui.destination.home, while a change to app.lawnchair.lawnicons.ui.destination.home can't break app.lawnchair.lawnicons.data.repository.iconrequest.
- Position
- Below the diagonal: app.lawnchair.lawnicons.ui.destination.home uses a module listed above it, which is the healthy direction.
35→6 app.lawnchair.lawnicons.ui.destination.iconrequest uses app.lawnchair.lawnicons.ui.destination.iconrequest.IconRequestViewModel✕
- Connections
- 1 pair of types, where a type in app.lawnchair.lawnicons.ui.destination.iconrequest uses a type in app.lawnchair.lawnicons.ui.destination.iconrequest.IconRequestViewModel.
- The types involved
app.lawnchair.lawnicons.ui.destination.iconrequest.IconRequestViewModel→app.lawnchair.lawnicons.ui.destination.iconrequest.IconRequestViewModel.ZipCreationResult
- Direction
- app.lawnchair.lawnicons.ui.destination.iconrequest uses app.lawnchair.lawnicons.ui.destination.iconrequest.IconRequestViewModel, so a change to app.lawnchair.lawnicons.ui.destination.iconrequest.IconRequestViewModel can break app.lawnchair.lawnicons.ui.destination.iconrequest, while a change to app.lawnchair.lawnicons.ui.destination.iconrequest can't break app.lawnchair.lawnicons.ui.destination.iconrequest.IconRequestViewModel.
- Position
- Below the diagonal: app.lawnchair.lawnicons.ui.destination.iconrequest uses a module listed above it, which is the healthy direction.
35→8 app.lawnchair.lawnicons.ui.destination.iconrequest uses app.lawnchair.lawnicons.data.model✕
- Connections
- 3 pairs of types, where a type in app.lawnchair.lawnicons.ui.destination.iconrequest uses a type in app.lawnchair.lawnicons.data.model.
- The types involved
app.lawnchair.lawnicons.ui.destination.iconrequest.IconRequestKt→app.lawnchair.lawnicons.data.model.SystemIconInfoapp.lawnchair.lawnicons.ui.destination.iconrequest.IconRequestViewModel→app.lawnchair.lawnicons.data.model.Announcementapp.lawnchair.lawnicons.ui.destination.iconrequest.IconRequestViewModel→app.lawnchair.lawnicons.data.model.SystemIconInfo
- Direction
- app.lawnchair.lawnicons.ui.destination.iconrequest uses app.lawnchair.lawnicons.data.model, so a change to app.lawnchair.lawnicons.data.model can break app.lawnchair.lawnicons.ui.destination.iconrequest, while a change to app.lawnchair.lawnicons.ui.destination.iconrequest can't break app.lawnchair.lawnicons.data.model.
- Position
- Below the diagonal: app.lawnchair.lawnicons.ui.destination.iconrequest uses a module listed above it, which is the healthy direction.
35→25 app.lawnchair.lawnicons.ui.destination.iconrequest uses app.lawnchair.lawnicons.data.repository.home✕
- Connections
- 1 pair of types, where a type in app.lawnchair.lawnicons.ui.destination.iconrequest uses a type in app.lawnchair.lawnicons.data.repository.home.
- The types involved
app.lawnchair.lawnicons.ui.destination.iconrequest.IconRequestViewModel→app.lawnchair.lawnicons.data.repository.home.AnnouncementsRepository
- Direction
- app.lawnchair.lawnicons.ui.destination.iconrequest uses app.lawnchair.lawnicons.data.repository.home, so a change to app.lawnchair.lawnicons.data.repository.home can break app.lawnchair.lawnicons.ui.destination.iconrequest, while a change to app.lawnchair.lawnicons.ui.destination.iconrequest can't break app.lawnchair.lawnicons.data.repository.home.
- Position
- Below the diagonal: app.lawnchair.lawnicons.ui.destination.iconrequest uses a module listed above it, which is the healthy direction.
35→26 app.lawnchair.lawnicons.ui.destination.iconrequest uses app.lawnchair.lawnicons.data.repository.iconrequest✕
- Connections
- 2 pairs of types, where a type in app.lawnchair.lawnicons.ui.destination.iconrequest uses a type in app.lawnchair.lawnicons.data.repository.iconrequest.
- The types involved
app.lawnchair.lawnicons.ui.destination.iconrequest.IconRequestViewModel→app.lawnchair.lawnicons.data.repository.iconrequest.IconRequestHandlerapp.lawnchair.lawnicons.ui.destination.iconrequest.IconRequestViewModel→app.lawnchair.lawnicons.data.repository.iconrequest.IconRequestRepository
- Direction
- app.lawnchair.lawnicons.ui.destination.iconrequest uses app.lawnchair.lawnicons.data.repository.iconrequest, so a change to app.lawnchair.lawnicons.data.repository.iconrequest can break app.lawnchair.lawnicons.ui.destination.iconrequest, while a change to app.lawnchair.lawnicons.ui.destination.iconrequest can't break app.lawnchair.lawnicons.data.repository.iconrequest.
- Position
- Below the diagonal: app.lawnchair.lawnicons.ui.destination.iconrequest uses a module listed above it, which is the healthy direction.
36→30 app.lawnchair.lawnicons.LawniconsGraph uses app.lawnchair.lawnicons✕
- Connections
- 1 pair of types, where a type in app.lawnchair.lawnicons.LawniconsGraph uses a type in app.lawnchair.lawnicons.
- The types involved
app.lawnchair.lawnicons.LawniconsGraph.Factory→app.lawnchair.lawnicons.LawniconsGraph
- Direction
- app.lawnchair.lawnicons.LawniconsGraph uses app.lawnchair.lawnicons, so a change to app.lawnchair.lawnicons can break app.lawnchair.lawnicons.LawniconsGraph, while a change to app.lawnchair.lawnicons.LawniconsGraph can't break app.lawnchair.lawnicons.
- Position
- Below the diagonal: app.lawnchair.lawnicons.LawniconsGraph uses a module listed above it, which is the healthy direction.
37→31 app.lawnchair.lawnicons.data.repository.bugreport.BugReportReceiver uses app.lawnchair.lawnicons.data.repository.bugreport✕
- Connections
- 1 pair of types, where a type in app.lawnchair.lawnicons.data.repository.bugreport.BugReportReceiver uses a type in app.lawnchair.lawnicons.data.repository.bugreport.
- The types involved
app.lawnchair.lawnicons.data.repository.bugreport.BugReportReceiver.Companion→app.lawnchair.lawnicons.data.repository.bugreport.BugReport
- Direction
- app.lawnchair.lawnicons.data.repository.bugreport.BugReportReceiver uses app.lawnchair.lawnicons.data.repository.bugreport, so a change to app.lawnchair.lawnicons.data.repository.bugreport can break app.lawnchair.lawnicons.data.repository.bugreport.BugReportReceiver, while a change to app.lawnchair.lawnicons.data.repository.bugreport.BugReportReceiver can't break app.lawnchair.lawnicons.data.repository.bugreport.
- Position
- Below the diagonal: app.lawnchair.lawnicons.data.repository.bugreport.BugReportReceiver uses a module listed above it, which is the healthy direction.
38→31 app.lawnchair.lawnicons.data.repository.bugreport.KatbinService uses app.lawnchair.lawnicons.data.repository.bugreport✕
- Connections
- 1 pair of types, where a type in app.lawnchair.lawnicons.data.repository.bugreport.KatbinService uses a type in app.lawnchair.lawnicons.data.repository.bugreport.
- The types involved
app.lawnchair.lawnicons.data.repository.bugreport.KatbinService.Companion→app.lawnchair.lawnicons.data.repository.bugreport.KatbinService
- Direction
- app.lawnchair.lawnicons.data.repository.bugreport.KatbinService uses app.lawnchair.lawnicons.data.repository.bugreport, so a change to app.lawnchair.lawnicons.data.repository.bugreport can break app.lawnchair.lawnicons.data.repository.bugreport.KatbinService, while a change to app.lawnchair.lawnicons.data.repository.bugreport.KatbinService can't break app.lawnchair.lawnicons.data.repository.bugreport.
- Position
- Below the diagonal: app.lawnchair.lawnicons.data.repository.bugreport.KatbinService uses a module listed above it, which is the healthy direction.
39→31 app.lawnchair.lawnicons.data.repository.bugreport.LawniconsBugReporter uses app.lawnchair.lawnicons.data.repository.bugreport✕
- Connections
- 1 pair of types, where a type in app.lawnchair.lawnicons.data.repository.bugreport.LawniconsBugReporter uses a type in app.lawnchair.lawnicons.data.repository.bugreport.
- The types involved
app.lawnchair.lawnicons.data.repository.bugreport.LawniconsBugReporter.Report→app.lawnchair.lawnicons.data.repository.bugreport.BugReport
- Direction
- app.lawnchair.lawnicons.data.repository.bugreport.LawniconsBugReporter uses app.lawnchair.lawnicons.data.repository.bugreport, so a change to app.lawnchair.lawnicons.data.repository.bugreport can break app.lawnchair.lawnicons.data.repository.bugreport.LawniconsBugReporter, while a change to app.lawnchair.lawnicons.data.repository.bugreport.LawniconsBugReporter can't break app.lawnchair.lawnicons.data.repository.bugreport.
- Position
- Below the diagonal: app.lawnchair.lawnicons.data.repository.bugreport.LawniconsBugReporter uses a module listed above it, which is the healthy direction.
40→8 app.lawnchair.lawnicons.ui.destination.home.HomeUiState uses app.lawnchair.lawnicons.data.model✕
- Connections
- 2 pairs of types, where a type in app.lawnchair.lawnicons.ui.destination.home.HomeUiState uses a type in app.lawnchair.lawnicons.data.model.
- The types involved
app.lawnchair.lawnicons.ui.destination.home.HomeUiState.Success→app.lawnchair.lawnicons.data.model.Announcementapp.lawnchair.lawnicons.ui.destination.home.HomeUiState.Success→app.lawnchair.lawnicons.data.model.IconInfoModel
- Direction
- app.lawnchair.lawnicons.ui.destination.home.HomeUiState uses app.lawnchair.lawnicons.data.model, so a change to app.lawnchair.lawnicons.data.model can break app.lawnchair.lawnicons.ui.destination.home.HomeUiState, while a change to app.lawnchair.lawnicons.ui.destination.home.HomeUiState can't break app.lawnchair.lawnicons.data.model.
- Position
- Below the diagonal: app.lawnchair.lawnicons.ui.destination.home.HomeUiState uses a module listed above it, which is the healthy direction.
40→34 app.lawnchair.lawnicons.ui.destination.home.HomeUiState uses app.lawnchair.lawnicons.ui.destination.home✕
- Connections
- 2 pairs of types, where a type in app.lawnchair.lawnicons.ui.destination.home.HomeUiState uses a type in app.lawnchair.lawnicons.ui.destination.home.
- The types involved
app.lawnchair.lawnicons.ui.destination.home.HomeUiState.Loading→app.lawnchair.lawnicons.ui.destination.home.HomeUiStateapp.lawnchair.lawnicons.ui.destination.home.HomeUiState.Success→app.lawnchair.lawnicons.ui.destination.home.HomeUiState
- Direction
- app.lawnchair.lawnicons.ui.destination.home.HomeUiState uses app.lawnchair.lawnicons.ui.destination.home, so a change to app.lawnchair.lawnicons.ui.destination.home can break app.lawnchair.lawnicons.ui.destination.home.HomeUiState, while a change to app.lawnchair.lawnicons.ui.destination.home.HomeUiState can't break app.lawnchair.lawnicons.ui.destination.home.
- Position
- Below the diagonal: app.lawnchair.lawnicons.ui.destination.home.HomeUiState 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 — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 61 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 7 | Medium |
| A07:2025 — Authentication Failures | 4 | High / Critical |
Roadmap
Top priorities: Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.gradle.kts; Resolve the 2 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2); 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.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.gradle.kts. | +5.0 pts | Low | ADR Quality |
| Resolve the 2 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2). | +4.8 pts | Low | REDACTED Scanning |
| 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. | +4.0 pts | Medium | Architecture documentation |
| 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. | +3.0 pts | Medium | Security & performance tooling |
| Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it. | +2.1 pts | Medium | Deployment & Rollback |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +2.1 pts | Medium | Release Hygiene |
| Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. | +1.0 pts | Low | Bus Factor |
| Resolve the 1 Off-boarding risk finding(s) in Bus Factor. | +1.0 pts | Low | Bus Factor |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 1.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.5 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.6 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.6 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 6.4 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| app/src/main/kotlin/app/lawnchair/lawnicons/ui/destination/about/About.kt | 7.0 | Mixed | Code Duplication: Duplicated block (11 lines × 2) |
| .github/scripts/bot_orchestrator.py | 7.2 | Mixed | Cyclomatic Complexity: bot_orchestrator.collect_final_report (cyclomatic 16) |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| .github/scripts/nightly_notes.py | 7.4 | Mixed | Cyclomatic Complexity: nightly_notes.generate_notes (cyclomatic 19) |
| send_notifications.py | 8.2 | Near-clean | Explicit Debt: TodoComment |
| app/src/main/kotlin/app/lawnchair/lawnicons/data/repository/iconrequest/IconRequestBundler.kt | 8.2 | Near-clean | Explicit Debt: TodoComment |
| svg-processor/src/main/kotlin/app/lawnchair/lawnicons/helper/SvgFilesProcessor.kt | 8.5 | Near-clean | Code Duplication: Edited copy of a member (13 corresponding lines) |
| app/src/main/kotlin/app/lawnchair/lawnicons/ui/components/core/TopAppBar.kt | 8.5 | Near-clean | Code Duplication: Edited copy of a member (18 corresponding lines) |
| .github/scripts/name_checker.py | 8.5 | Near-clean | Code Duplication: Edited copy of a member (5 corresponding lines) |
| app/src/main/kotlin/app/lawnchair/lawnicons/data/repository/bugreport/KatbinService.kt | 8.5 | Near-clean | Code Duplication: Edited copies of one member (3 members, 5+ corresponding lines) |
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 46 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 46 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, 123 of 134 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.kt) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.kt) and this repository declares a JVM test suite (repository root, Gradle), but it was not re-run: the analyzer environment could not run it. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D12 Dependency Hygiene — 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 292 artifact(s) across its subprojects (87 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.
- 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. `app/src/main/kotlin/app/lawnchair/lawnicons/LawniconsGraph.kt`, `app/src/main/kotlin/app/lawnchair/lawnicons/data/repository/PreferenceManager.kt`, `app/src/main/kotlin/app/lawnchair/lawnicons/di/AppInitializer.kt`, `app/src/main/kotlin/app/lawnchair/lawnicons/ui/components/core/placeholder/Placeholder.kt` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- AX1 Captive dependencies — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository's container is Metro, 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.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Boot via AndroidApp (app). the Android app did not build — `./gradlew :app:assembleDebug` exited 1: olumnScrollbar:lazycolumnscrollbar:3.0.0. > Could not get resource 'https://jitpack.io/com/github/nanihadesuka/LazyColumnScrollbar/lazycolumnscrollbar/3.0.0/lazycolumnscrollbar-3.0.0.pom'.…; runtime evidence skipped (launch chosen because app/build.gradle.kts applies the Android application plugin and gradlew builds it).
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Java was found, and this repository's Kotlin, Python 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 no C#, JavaScript/TypeScript, Java, Dart, Ruby, Scala or Rust was found, and this repository's Kotlin, Python 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.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- 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.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
7 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was lint_icons.rule_square_size at 34.
What to do
- Bring the 7 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with lint_icons.rule_square_size (cyclomatic 34), lint_icons.rule_effects (cyclomatic 24), lint_icons.rule_fill_color (cyclomatic 20). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 7 together lifts Cyclomatic Complexity from 8.6 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
12 method(s) exceeded the cognitive complexity threshold of 15; the worst was lint_icons.rule_square_size at 63.
What to do
- Bring the 12 bodies over 15 down to 15 or less in Cognitive Complexity — start with lint_icons.rule_square_size (cognitive 63), lint_icons.rule_effects (cognitive 61), bot_orchestrator.collect_final_report (cognitive 43). — 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 12 together lifts Cognitive Complexity from 7.0 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
1 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 1 FileTooLong finding(s) in God Classes — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
5 duplicated block group(s) detected. 1.5 % of the production lines (189 of 12,910) are in a reported copy. A further 5 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 1 Edited copy of a member (20 corresponding lines) finding(s) in Code Duplication — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Edited copy of a member (13 corresponding lines) finding(s) in Code Duplication — start with SvgFilesProcessor.kt. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Edited copy of a member (18 corresponding lines) finding(s) in Code Duplication — start with TopAppBar.kt. — One of this dimension's main actionable groups (1 warning-level).
D5 · Coupling
3 production modules (Gradle), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; edges a convention plugin adds from buildSrc or build-logic are not visible there; 0 module(s) off the main sequence.
D6 · Cohesion (LCOM4)
0 of 12 classes have LCOM4 above 3.
D13 · REDACTED Scanning
1 secret(s) detected. 2 detection(s) were excluded as holding no minted credential in material that runs: a name, reference or comparison rather than a value, a readable phrase or pattern, a value that declares itself fake, or development, test, example, mock or demo material.
What to do
- Resolve the 2 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
D14 · License Compliance
0 of 3 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 4 Maven/Gradle manifest(s) declare with a version resolvable from the manifest itself — the same declaration-site closure this analysis reads for dependency currency. The JVM has no lockfile a checkout is guaranteed to carry, so this is deliberately NOT the transitive closure. 6 further coordinate(s) are declared with no version at the declaration site — inherited from a parent POM, a BOM or an unresolved Gradle version reference — and are NOT graded: this verdict covers what the checkout pins, not the full transitive graph. A further 4 coordinate(s) are not published to Maven Central — another repository (Google's Maven hosts androidx), a SNAPSHOT, or a private artifact — so their licences are not readable from here and they are outside this verdict.
D15 · Churn × Complexity Hotspots
Top hotspots: REDACTED (7×34=238); .github/scripts/bot_orchestrator.py (9×16=144)
What to do
- Resolve the 2 Hotspot finding(s) in Churn × Complexity Hotspots — start with REDACTED, bot_orchestrator.py. — One of this dimension's main actionable groups (2 warning-level).
D16 · Bus Factor
25 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is app/src/main/kotlin/app/lawnchair/lawnicons/ui/destination/iconrequest/IconRequest.kt. Counted over 67 of the 123 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
D17 · Explicit Debt
2 deducted task-comment markers across 12910 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.
What to do
- Resolve the 2 TodoComment finding(s) in Explicit Debt — start with send_notifications.py, IconRequestBundler.kt. — One of this dimension's main actionable groups (2 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 5 document(s) read across 3 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.gradle.kts. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
1 of 3 build units (Gradle) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with build.gradle.kts. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
1 finding(s): 0 critical, 1 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 1 REDACTED finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
61 finding(s): 0 critical, 58 high, 3 medium, 0 low. 43 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 1 file(s) — `gradlew` (line 74, line 178) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 3 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 6 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED (3). — One of this dimension's main actionable groups (6 issue-level).
- Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 issue-level).
- No action in Static Analysis (SAST) — all 43 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 (43 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
No known-vulnerable dependencies in any ecosystem this repository declares.
D34 · Knowledge Freshness
9 of 67 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is app/src/main/kotlin/app/lawnchair/lawnicons/ui/theme/icon/NewReleases.kt. Counted over 67 of the 123 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 9 Orphaned file finding(s) in Knowledge Freshness — start with NewReleases.kt, ConfigProcessor.kt, Share.kt. — One of this dimension's main actionable groups (9 recommendation-level).
- Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
Strongest change-coupling: HomeTopBar.kt↔Home.kt 71%; SearchBarInputField.kt↔Home.kt 68%; HomeBottomBar.kt↔Home.kt 60%
What to do
- Resolve the 1 Change-coupling hub finding(s) in Change Coupling — start with Home.kt. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Change coupling clique finding(s) in Change Coupling — start with GetIconInfo.kt. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Change coupling finding(s) in Change Coupling — start with About.kt. — One of this dimension's main actionable groups (1 warning-level).
D36 · Supply-chain Provenance & Signing
1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 3 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 2 platform declaration(s) and 7 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
M1 · Documentation (README)
What to do
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
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.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
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.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P2 · Observability
- Only 1/2 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `svg-processor`.
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 9 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. — REDACTED:8
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.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release. — REDACTED:173
What to do
- Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
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
X16 · Unfloored truncation loop
X18 · Disposal-pattern correctness
X21 · Side-effecting pattern guard
X25 · Inert configuration knob
X27 · Collection changed while being enumerated
X3 · Exception handling
- An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. — REDACTED:919
- `except` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×2) — send_notifications.py:61, send_notifications.py:99
- `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. — app/src/main/kotlin/app/lawnchair/lawnicons/data/repository/iconrequest/IconRequestRepository.kt:76
What to do
- Swallowed exception (empty catch)
X30 · Support guard that admits what it rejects
X5 · Nullable reference types
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 81.3 | Strong | Solid. |
| Architecture | 88.6 | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 54.1 | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 50.6 | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 55.4 | Adequate — gated by D29, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100.0 | Exemplary | Strongest area. |
Unscored — 1 check(s) recorded observations but carry no score
- X7 Silent fallback defaults — 1 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 — 68 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 Java code is a Spring, JSR-330 or CDI singleton bean. No class in this Kotlin code is a Spring, JSR-330 or CDI singleton bean. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads.
- 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
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — the Android app did not build — `./gradlew :app:assembleDebug` exited 1: olumnScrollbar:lazycolumnscrollbar:3.0.0. > Could not get resource 'https://jitpack.io/com/github/nanihadesuka/LazyColumnScrollbar/lazycolumnscrollbar/3.0.0/lazycolumnscrollbar-3.0.0.pom'.…; runtime evidence skipped (launch chosen because app/build.gradle.kts applies the Android application plugin and gradlew builds it) This is a statement about this run, not a statement about your application: nothing here says the app is inaccessible, only that it was never run.
- 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 — ~3105 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 292 artifact(s) across its subprojects (87 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.
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (1854 declarations, no unit with a dominant convention).
- 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, .py, 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
- 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) — 4 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (37 value object(s))
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby, 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, Python source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a pom.xml, Gradle or sbt build, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- 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.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — no C# was loaded; this repository's Python and Kotlin were read, and no request in it can be cancelled by a caller (Ktor, OkHttp's newCall or a URL stream, from a suspend function) — a Python request takes no token: asyncio cancels the task and trio or anyio the scope that made it, from outside the call, and requests, httpx, aiohttp and gRPC take a timeout, not a cancellation; a Kotlin request outside a suspend function has no caller's cancellation to honour
- X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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 — X24 reached only 9% of this repository's production lines — kotlin (11,723 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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.
- X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Kotlin was read, and it logs through none that an assembled message defeats: Android's `Log` and Timber, java.util.logging and log4j-api-kotlin take one finished message (as log4net does in C#), or it makes no call through a named logger at all. Calls made through SLF4J, log4j 2 or kotlin-logging (`LoggerFactory.getLogger`, `KotlinLogging.logger {}`) would be judged.
- X6 Hand-rolled structured-format parsing — 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 — 61 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 49 finding(s)
- REDACTED
- REDACTED
- REDACTED
- Swallowed exception (caught, then discarded) send_notifications.py:61
- Swallowed exception (caught, then discarded) send_notifications.py:99
- Swallowed exception (caught, then discarded) app/src/main/kotlin/app/lawnchair/lawnicons/data/repository/iconrequest/IconRequestRepository.kt:76
- Hotspot: REDACTED REDACTED:274
- Hotspot: .github/scripts/bot_orchestrator.py .github/scripts/bot_orchestrator.py:297
- TodoComment send_notifications.py:7
- TodoComment app/src/main/kotlin/app/lawnchair/lawnicons/data/repository/iconrequest/IconRequestBundler.kt:156
- REDACTED
- REDACTED
- lint_icons.rule_square_size (cyclomatic 34) REDACTED:274
- lint_icons.rule_effects (cyclomatic 24) REDACTED:368
- lint_icons.rule_fill_color (cyclomatic 20) REDACTED:520
- nightly_notes.generate_notes (cyclomatic 19) .github/scripts/nightly_notes.py:93
- lint_icons.rule_adjacent_stroke_weight (cyclomatic 17) REDACTED:705
- bot_orchestrator.collect_final_report (cyclomatic 16) .github/scripts/bot_orchestrator.py:226
- bot_orchestrator.build_comment_body (cyclomatic 16) .github/scripts/bot_orchestrator.py:297
- lint_icons.rule_square_size (cognitive 63) REDACTED:274
- lint_icons.rule_effects (cognitive 61) REDACTED:368
- bot_orchestrator.collect_final_report (cognitive 43) .github/scripts/bot_orchestrator.py:226
- nightly_notes.generate_notes (cognitive 36) .github/scripts/nightly_notes.py:93
- lint_icons.rule_fill_color (cognitive 32) REDACTED:520
- lint_icons.rule_adjacent_stroke_weight (cognitive 28) REDACTED:705
- bot_orchestrator.build_comment_body (cognitive 26) .github/scripts/bot_orchestrator.py:297
- lint_icons.analyze_file (cognitive 22) REDACTED:892
- icontool.add_or_link_component (cognitive 18) REDACTED:70
- nightly_notes.get_merged_prs (cognitive 16) .github/scripts/nightly_notes.py:17
- lint_icons._path_subpaths (cognitive 16) REDACTED:156
- lint_icons.main (cognitive 16) REDACTED:970
- REDACTED
- FileTooLong: ./REDACTED REDACTED
- Change-coupling hub: Home.kt → HomeBottomBar.kt, HomeTopBar.kt, SearchBarInputField.kt, SearchContents.kt, DebugMenu.kt, IconRequest.kt app/src/main/kotlin/app/lawnchair/lawnicons/ui/destination/home/Home.kt
- Change coupling clique: GetIconInfo.kt, IconRepository.kt, GetSystemPackageList.kt app/src/main/kotlin/app/lawnchair/lawnicons/data/repository/home/GetIconInfo.kt
- Change coupling: About.kt ↔ Contributors.kt app/src/main/kotlin/app/lawnchair/lawnicons/ui/destination/about/About.kt:1
- REDACTED
- REDACTED
- Edited copy of a member (20 corresponding lines) REDACTED:595
- Edited copy of a member (13 corresponding lines) svg-processor/src/main/kotlin/app/lawnchair/lawnicons/helper/SvgFilesProcessor.kt:137
- Edited copy of a member (18 corresponding lines) app/src/main/kotlin/app/lawnchair/lawnicons/ui/components/core/TopAppBar.kt:60
- Edited copy of a member (5 corresponding lines) .github/scripts/name_checker.py:108
- Edited copies of one member (3 members, 5+ corresponding lines) app/src/main/kotlin/app/lawnchair/lawnicons/data/repository/bugreport/KatbinService.kt:18
- Duplicated block (11 lines × 2) app/src/main/kotlin/app/lawnchair/lawnicons/ui/destination/about/About.kt:97
- Duplicated block (8 lines × 2) app/src/main/kotlin/app/lawnchair/lawnicons/ui/components/home/iconpreview/IconInfoSheet.kt:216
- Duplicated block (13 lines × 2) REDACTED:401
- Duplicated block (9–10 lines × 2) REDACTED:595
- Duplicated block (7 lines × 2) REDACTED:334
- Swallowed exception (empty catch) REDACTED:919
Minor — 24 finding(s)
- Orphaned file app/src/main/kotlin/app/lawnchair/lawnicons/ui/theme/icon/NewReleases.kt:1
- Orphaned file svg-processor/src/main/kotlin/app/lawnchair/lawnicons/helper/ConfigProcessor.kt:1
- Orphaned file app/src/main/kotlin/app/lawnchair/lawnicons/ui/theme/icon/Share.kt:1
- Orphaned file app/src/main/kotlin/app/lawnchair/lawnicons/ui/theme/icon/About.kt:1
- Orphaned file app/src/main/kotlin/app/lawnchair/lawnicons/ui/theme/icon/Save.kt:1
- Orphaned file app/src/main/kotlin/app/lawnchair/lawnicons/ui/theme/icon/Copy.kt:1
- Orphaned file app/src/main/kotlin/app/lawnchair/lawnicons/ui/theme/icon/Discord.kt:1
- Orphaned file app/src/main/kotlin/app/lawnchair/lawnicons/ui/theme/icon/Mail.kt:1
- Orphaned file app/src/main/kotlin/app/lawnchair/lawnicons/ui/theme/icon/IconRequest.kt:1
- Off-boarding risk: anonymized user #1
- Further sole-owners (lower concentration)
- No ADRs found svg-processor/build.gradle.kts:3
- Projects may be oversized for their cohesion app/build.gradle.kts:1
- REDACTED
- Orphaned files with no living knowledge
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- Logging is not universal
- No SAST REDACTED:8
- No release approval gate REDACTED:173
- No changelog
- Silent fallback default in catch app/src/main/kotlin/app/lawnchair/lawnicons/data/repository/iconrequest/GetSystemPackageList.kt:37
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-6655a4a1feaf4e35b0772357d9855cbc/history.json --exit-code 0 --source . | 0 | 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=800" --report-format json --report-path /tmp/watchdog-gitleaks-6655a4a1feaf4e35b0772357d9855cbc/history-1.json --exit-code 0 --source . | 2 | artifacts/raw/gitleaks-history-1.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=1000 --max-count=3044" --report-format json --report-path /tmp/watchdog-gitleaks-6655a4a1feaf4e35b0772357d9855cbc/history-2.json --exit-code 0 --source . | 2 | artifacts/raw/gitleaks-history-2.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-6655a4a1feaf4e35b0772357d9855cbc/tree.json --exit-code 0 --source . | 4 | 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 . | 61 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 4 file(s) — `app/src/main/kotlin/app/lawnchair/lawnicons/LawniconsGraph.kt`, `app/src/main/kotlin/app/lawnchair/lawnicons/data/repository/PreferenceManager.kt`, `app/src/main/kotlin/app/lawnchair/lawnicons/di/AppInitializer.kt`, `app/src/main/kotlin/app/lawnchair/lawnicons/ui/components/core/placeholder/Placeholder.kt` — 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 | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |