Executive summary
wisnukurniawan/Compose-ToDo meets our standard for a template or a sample. It scores 64.6 out of 100 and is rated Strong, and all seven of its critical findings are security problems.
Every lens scores high enough to be rated Strong, so no single lens holds the score back. The best first step is replacing the two exposed passwords or keys and switching the old ones off, worth about 7.5 points. Having someone learn and document the 64 files no active contributor knows comes next, worth about 5.9 points.
Five pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Two passwords or keys are open to anyone who can read the repository. Pinning each tool to an exact version and replacing each exposed password or key would close both risks.
The product code is 14,092 lines, about €23,000 to rebuild.
Every lens already scores high enough to be rated Strong, so no single lens holds the score back.
Rebuild cost: about €23,000 · Estimate
| Cost to rebuild | €7,700 to €39,000, for 128 to 407 hours of work, about 0.2 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.9 at a score of 65. 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: 14,092 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 foundation.window | 2 foundation.wrapper | 3 model | 4 features.todo.all.ui.ItemAllState | 5 features.todo.detail.ui.ListDetailAction | 6 features.todo.main.ui.ItemMainState | 7 features.todo.scheduled.ui.ItemScheduledState | 8 features.todo.step.ui.StepAction | 9 foundation.datasource.local.dao | 10 foundation.datasource.preference.provider | 11 runtime.navigation | 12 features.host.data | 13 features.localized.setting.data | 14 features.login.data | 15 features.logout.data | 16 features.splash.data | 17 features.theme.data | 18 features.todo.step.ui.StepAction.StepItemAction | 19 foundation.datasource.local.provider | 20 features.localized.setting.ui | 21 features.login.ui | 22 features.logout.ui | 23 features.todo.all.data | 24 features.todo.detail.data | 25 features.todo.group.data | 26 features.todo.grouplist.data | 27 features.todo.groupmenu.data | 28 features.todo.main.data | 29 features.todo.scheduled.data | 30 features.todo.search.data | 31 features.todo.step.data | 32 features.todo.taskreminder.data | 33 features.dashboard.data | 34 features.todo.all.ui | 35 features.todo.main.ui | 36 features.todo.scheduled.ui | 37 features.todo.step.ui | 38 features.todo.detail.ui | 39 features.todo.search.ui | 40 features.dashboard.ui |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 foundation.window | ||||||||||||||||||||||||||||||||||||||||
| 2 foundation.wrapper | ||||||||||||||||||||||||||||||||||||||||
| 3 model | ||||||||||||||||||||||||||||||||||||||||
| 4 features.todo.all.ui.ItemAllState | 3 | 2 | ||||||||||||||||||||||||||||||||||||||
| 5 features.todo.detail.ui.ListDetailAction | 2 | |||||||||||||||||||||||||||||||||||||||
| 6 features.todo.main.ui.ItemMainState | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 7 features.todo.scheduled.ui.ItemScheduledState | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 8 features.todo.step.ui.StepAction | 3 | |||||||||||||||||||||||||||||||||||||||
| 9 foundation.datasource.local.dao | 6 | |||||||||||||||||||||||||||||||||||||||
| 10 foundation.datasource.preference.provider | 4 | |||||||||||||||||||||||||||||||||||||||
| 11 runtime.navigation | 1 | |||||||||||||||||||||||||||||||||||||||
| 12 features.host.data | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 13 features.localized.setting.data | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 14 features.login.data | 2 | |||||||||||||||||||||||||||||||||||||||
| 15 features.logout.data | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 16 features.splash.data | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 17 features.theme.data | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 18 features.todo.step.ui.StepAction.StepItemAction | 2 | |||||||||||||||||||||||||||||||||||||||
| 19 foundation.datasource.local.provider | 10 | 8 | ||||||||||||||||||||||||||||||||||||||
| 20 features.localized.setting.ui | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 21 features.login.ui | 1 | |||||||||||||||||||||||||||||||||||||||
| 22 features.logout.ui | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 23 features.todo.all.data | 2 | 4 | 2 | |||||||||||||||||||||||||||||||||||||
| 24 features.todo.detail.data | 4 | 4 | 2 | |||||||||||||||||||||||||||||||||||||
| 25 features.todo.group.data | 4 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 26 features.todo.grouplist.data | 2 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 27 features.todo.groupmenu.data | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 28 features.todo.main.data | 2 | 6 | 3 | |||||||||||||||||||||||||||||||||||||
| 29 features.todo.scheduled.data | 4 | 4 | 1 | |||||||||||||||||||||||||||||||||||||
| 30 features.todo.search.data | 1 | 4 | 1 | |||||||||||||||||||||||||||||||||||||
| 31 features.todo.step.data | 4 | 8 | 3 | |||||||||||||||||||||||||||||||||||||
| 32 features.todo.taskreminder.data | 1 | 7 | 1 | |||||||||||||||||||||||||||||||||||||
| 33 features.dashboard.data | 1 | 4 | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||
| 34 features.todo.all.ui | 3 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 35 features.todo.main.ui | 1 | 3 | 1 | |||||||||||||||||||||||||||||||||||||
| 36 features.todo.scheduled.ui | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 37 features.todo.step.ui | 5 | 3 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 38 features.todo.detail.ui | 6 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 39 features.todo.search.ui | 2 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 40 features.dashboard.ui | 2 | 1 | 2 | 1 | 1 | 2 | 1 |
4→3 features.todo.all.ui.ItemAllState uses model✕
- Connections
- 3 pairs of types, where a type in features.todo.all.ui.ItemAllState uses a type in model.
- The types involved
com.wisnu.kurniawan.composetodolist.features.todo.all.ui.ItemAllState.List→com.wisnu.kurniawan.composetodolist.model.ToDoListcom.wisnu.kurniawan.composetodolist.features.todo.all.ui.ItemAllState.Task→com.wisnu.kurniawan.composetodolist.model.ToDoListcom.wisnu.kurniawan.composetodolist.features.todo.all.ui.ItemAllState.Task→com.wisnu.kurniawan.composetodolist.model.ToDoTask
- Direction
- features.todo.all.ui.ItemAllState uses model, so a change to model can break features.todo.all.ui.ItemAllState, while a change to features.todo.all.ui.ItemAllState can't break model.
- Position
- Below the diagonal: features.todo.all.ui.ItemAllState uses a module listed above it, which is the healthy direction.
4→34 features.todo.all.ui.ItemAllState uses features.todo.all.ui part of a loop✕
- Connections
- 2 pairs of types, where a type in features.todo.all.ui.ItemAllState uses a type in features.todo.all.ui.
- The types involved
com.wisnu.kurniawan.composetodolist.features.todo.all.ui.ItemAllState.List→com.wisnu.kurniawan.composetodolist.features.todo.all.ui.ItemAllStatecom.wisnu.kurniawan.composetodolist.features.todo.all.ui.ItemAllState.Task→com.wisnu.kurniawan.composetodolist.features.todo.all.ui.ItemAllState
- Direction
- features.todo.all.ui.ItemAllState uses features.todo.all.ui, so a change to features.todo.all.ui can break features.todo.all.ui.ItemAllState, while a change to features.todo.all.ui.ItemAllState can't break features.todo.all.ui.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
5→38 features.todo.detail.ui.ListDetailAction uses features.todo.detail.ui part of a loop✕
- Connections
- 2 pairs of types, where a type in features.todo.detail.ui.ListDetailAction uses a type in features.todo.detail.ui.
- The types involved
com.wisnu.kurniawan.composetodolist.features.todo.detail.ui.ListDetailAction.ListAction→com.wisnu.kurniawan.composetodolist.features.todo.detail.ui.ListDetailActioncom.wisnu.kurniawan.composetodolist.features.todo.detail.ui.ListDetailAction.TaskAction→com.wisnu.kurniawan.composetodolist.features.todo.detail.ui.ListDetailAction
- Direction
- features.todo.detail.ui.ListDetailAction uses features.todo.detail.ui, so a change to features.todo.detail.ui can break features.todo.detail.ui.ListDetailAction, while a change to features.todo.detail.ui.ListDetailAction can't break features.todo.detail.ui.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→3 features.todo.main.ui.ItemMainState uses model✕
- Connections
- 2 pairs of types, where a type in features.todo.main.ui.ItemMainState uses a type in model.
- The types involved
com.wisnu.kurniawan.composetodolist.features.todo.main.ui.ItemMainState.ItemGroup→com.wisnu.kurniawan.composetodolist.model.ToDoGroupcom.wisnu.kurniawan.composetodolist.features.todo.main.ui.ItemMainState.ItemListType→com.wisnu.kurniawan.composetodolist.model.ToDoList
- Direction
- features.todo.main.ui.ItemMainState uses model, so a change to model can break features.todo.main.ui.ItemMainState, while a change to features.todo.main.ui.ItemMainState can't break model.
- Position
- Below the diagonal: features.todo.main.ui.ItemMainState uses a module listed above it, which is the healthy direction.
6→35 features.todo.main.ui.ItemMainState uses features.todo.main.ui part of a loop✕
- Connections
- 2 pairs of types, where a type in features.todo.main.ui.ItemMainState uses a type in features.todo.main.ui.
- The types involved
com.wisnu.kurniawan.composetodolist.features.todo.main.ui.ItemMainState.ItemGroup→com.wisnu.kurniawan.composetodolist.features.todo.main.ui.ItemMainStatecom.wisnu.kurniawan.composetodolist.features.todo.main.ui.ItemMainState.ItemListType→com.wisnu.kurniawan.composetodolist.features.todo.main.ui.ItemMainState
- Direction
- features.todo.main.ui.ItemMainState uses features.todo.main.ui, so a change to features.todo.main.ui can break features.todo.main.ui.ItemMainState, while a change to features.todo.main.ui.ItemMainState can't break features.todo.main.ui.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→3 features.todo.scheduled.ui.ItemScheduledState uses model✕
- Connections
- 2 pairs of types, where a type in features.todo.scheduled.ui.ItemScheduledState uses a type in model.
- The types involved
com.wisnu.kurniawan.composetodolist.features.todo.scheduled.ui.ItemScheduledState.Task→com.wisnu.kurniawan.composetodolist.model.ToDoListcom.wisnu.kurniawan.composetodolist.features.todo.scheduled.ui.ItemScheduledState.Task→com.wisnu.kurniawan.composetodolist.model.ToDoTask
- Direction
- features.todo.scheduled.ui.ItemScheduledState uses model, so a change to model can break features.todo.scheduled.ui.ItemScheduledState, while a change to features.todo.scheduled.ui.ItemScheduledState can't break model.
- Position
- Below the diagonal: features.todo.scheduled.ui.ItemScheduledState uses a module listed above it, which is the healthy direction.
7→36 features.todo.scheduled.ui.ItemScheduledState uses features.todo.scheduled.ui part of a loop✕
- Connections
- 2 pairs of types, where a type in features.todo.scheduled.ui.ItemScheduledState uses a type in features.todo.scheduled.ui.
- The types involved
com.wisnu.kurniawan.composetodolist.features.todo.scheduled.ui.ItemScheduledState.Header→com.wisnu.kurniawan.composetodolist.features.todo.scheduled.ui.ItemScheduledStatecom.wisnu.kurniawan.composetodolist.features.todo.scheduled.ui.ItemScheduledState.Task→com.wisnu.kurniawan.composetodolist.features.todo.scheduled.ui.ItemScheduledState
- Direction
- features.todo.scheduled.ui.ItemScheduledState uses features.todo.scheduled.ui, so a change to features.todo.scheduled.ui can break features.todo.scheduled.ui.ItemScheduledState, while a change to features.todo.scheduled.ui.ItemScheduledState can't break features.todo.scheduled.ui.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→37 features.todo.step.ui.StepAction uses features.todo.step.ui part of a loop✕
- Connections
- 3 pairs of types, where a type in features.todo.step.ui.StepAction uses a type in features.todo.step.ui.
- The types involved
com.wisnu.kurniawan.composetodolist.features.todo.step.ui.StepAction.NoteAction→com.wisnu.kurniawan.composetodolist.features.todo.step.ui.StepActioncom.wisnu.kurniawan.composetodolist.features.todo.step.ui.StepAction.StepItemAction→com.wisnu.kurniawan.composetodolist.features.todo.step.ui.StepActioncom.wisnu.kurniawan.composetodolist.features.todo.step.ui.StepAction.TaskAction→com.wisnu.kurniawan.composetodolist.features.todo.step.ui.StepAction
- Direction
- features.todo.step.ui.StepAction uses features.todo.step.ui, so a change to features.todo.step.ui can break features.todo.step.ui.StepAction, while a change to features.todo.step.ui.StepAction can't break features.todo.step.ui.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→3 foundation.datasource.local.dao uses model✕
- Connections
- 6 pairs of types, where a type in foundation.datasource.local.dao uses a type in model.
- The types involved
com.wisnu.kurniawan.composetodolist.foundation.datasource.local.dao.ToDoListWriteDao→com.wisnu.kurniawan.composetodolist.model.ToDoColorcom.wisnu.kurniawan.composetodolist.foundation.datasource.local.dao.ToDoStepWriteDao→com.wisnu.kurniawan.composetodolist.model.ToDoStatuscom.wisnu.kurniawan.composetodolist.foundation.datasource.local.dao.ToDoTaskReadDao→com.wisnu.kurniawan.composetodolist.model.ToDoStatuscom.wisnu.kurniawan.composetodolist.foundation.datasource.local.dao.ToDoTaskReadDao→com.wisnu.kurniawan.composetodolist.model.ToDoTaskOverallCountcom.wisnu.kurniawan.composetodolist.foundation.datasource.local.dao.ToDoTaskWriteDao→com.wisnu.kurniawan.composetodolist.model.ToDoRepeatcom.wisnu.kurniawan.composetodolist.foundation.datasource.local.dao.ToDoTaskWriteDao→com.wisnu.kurniawan.composetodolist.model.ToDoStatus
- Direction
- foundation.datasource.local.dao uses model, so a change to model can break foundation.datasource.local.dao, while a change to foundation.datasource.local.dao can't break model.
- Position
- Below the diagonal: foundation.datasource.local.dao uses a module listed above it, which is the healthy direction.
10→3 foundation.datasource.preference.provider uses model✕
- Connections
- 4 pairs of types, where a type in foundation.datasource.preference.provider uses a type in model.
- The types involved
com.wisnu.kurniawan.composetodolist.foundation.datasource.preference.provider.CredentialProvider→com.wisnu.kurniawan.composetodolist.model.Credentialcom.wisnu.kurniawan.composetodolist.foundation.datasource.preference.provider.LanguageProvider→com.wisnu.kurniawan.composetodolist.model.Languagecom.wisnu.kurniawan.composetodolist.foundation.datasource.preference.provider.ThemeProvider→com.wisnu.kurniawan.composetodolist.model.Themecom.wisnu.kurniawan.composetodolist.foundation.datasource.preference.provider.UserProvider→com.wisnu.kurniawan.composetodolist.model.User
- Direction
- foundation.datasource.preference.provider uses model, so a change to model can break foundation.datasource.preference.provider, while a change to foundation.datasource.preference.provider can't break model.
- Position
- Below the diagonal: foundation.datasource.preference.provider uses a module listed above it, which is the healthy direction.
11→1 runtime.navigation uses foundation.window✕
- Connections
- 1 pair of types, where a type in runtime.navigation uses a type in foundation.window.
- The types involved
com.wisnu.kurniawan.composetodolist.runtime.navigation.MainNavHostKt→com.wisnu.kurniawan.composetodolist.foundation.window.WindowState
- Direction
- runtime.navigation uses foundation.window, so a change to foundation.window can break runtime.navigation, while a change to runtime.navigation can't break foundation.window.
- Position
- Below the diagonal: runtime.navigation uses a module listed above it, which is the healthy direction.
12→3 features.host.data uses model✕
- Connections
- 2 pairs of types, where a type in features.host.data uses a type in model.
- The types involved
com.wisnu.kurniawan.composetodolist.features.host.data.HostEnvironment→com.wisnu.kurniawan.composetodolist.model.Themecom.wisnu.kurniawan.composetodolist.features.host.data.IHostEnvironment→com.wisnu.kurniawan.composetodolist.model.Theme
- Direction
- features.host.data uses model, so a change to model can break features.host.data, while a change to features.host.data can't break model.
- Position
- Below the diagonal: features.host.data uses a module listed above it, which is the healthy direction.
12→10 features.host.data uses foundation.datasource.preference.provider✕
- Connections
- 1 pair of types, where a type in features.host.data uses a type in foundation.datasource.preference.provider.
- The types involved
com.wisnu.kurniawan.composetodolist.features.host.data.HostEnvironment→com.wisnu.kurniawan.composetodolist.foundation.datasource.preference.provider.ThemeProvider
- Direction
- features.host.data uses foundation.datasource.preference.provider, so a change to foundation.datasource.preference.provider can break features.host.data, while a change to features.host.data can't break foundation.datasource.preference.provider.
- Position
- Below the diagonal: features.host.data uses a module listed above it, which is the healthy direction.
13→3 features.localized.setting.data uses model✕
- Connections
- 2 pairs of types, where a type in features.localized.setting.data uses a type in model.
- The types involved
com.wisnu.kurniawan.composetodolist.features.localized.setting.data.ILocalizedSettingEnvironment→com.wisnu.kurniawan.composetodolist.model.Languagecom.wisnu.kurniawan.composetodolist.features.localized.setting.data.LocalizedSettingEnvironment→com.wisnu.kurniawan.composetodolist.model.Language
- Direction
- features.localized.setting.data uses model, so a change to model can break features.localized.setting.data, while a change to features.localized.setting.data can't break model.
- Position
- Below the diagonal: features.localized.setting.data uses a module listed above it, which is the healthy direction.
13→10 features.localized.setting.data uses foundation.datasource.preference.provider✕
- Connections
- 1 pair of types, where a type in features.localized.setting.data uses a type in foundation.datasource.preference.provider.
- The types involved
com.wisnu.kurniawan.composetodolist.features.localized.setting.data.LocalizedSettingEnvironment→com.wisnu.kurniawan.composetodolist.foundation.datasource.preference.provider.LanguageProvider
- Direction
- features.localized.setting.data uses foundation.datasource.preference.provider, so a change to foundation.datasource.preference.provider can break features.localized.setting.data, while a change to features.localized.setting.data can't break foundation.datasource.preference.provider.
- Position
- Below the diagonal: features.localized.setting.data uses a module listed above it, which is the healthy direction.
14→10 features.login.data uses foundation.datasource.preference.provider✕
- Connections
- 2 pairs of types, where a type in features.login.data uses a type in foundation.datasource.preference.provider.
- The types involved
com.wisnu.kurniawan.composetodolist.features.login.data.LoginEnvironment→com.wisnu.kurniawan.composetodolist.foundation.datasource.preference.provider.CredentialProvidercom.wisnu.kurniawan.composetodolist.features.login.data.LoginEnvironment→com.wisnu.kurniawan.composetodolist.foundation.datasource.preference.provider.UserProvider
- Direction
- features.login.data uses foundation.datasource.preference.provider, so a change to foundation.datasource.preference.provider can break features.login.data, while a change to features.login.data can't break foundation.datasource.preference.provider.
- Position
- Below the diagonal: features.login.data uses a module listed above it, which is the healthy direction.
15→3 features.logout.data uses model✕
- Connections
- 2 pairs of types, where a type in features.logout.data uses a type in model.
- The types involved
com.wisnu.kurniawan.composetodolist.features.logout.data.ILogoutEnvironment→com.wisnu.kurniawan.composetodolist.model.Usercom.wisnu.kurniawan.composetodolist.features.logout.data.LogoutEnvironment→com.wisnu.kurniawan.composetodolist.model.User
- Direction
- features.logout.data uses model, so a change to model can break features.logout.data, while a change to features.logout.data can't break model.
- Position
- Below the diagonal: features.logout.data uses a module listed above it, which is the healthy direction.
15→10 features.logout.data uses foundation.datasource.preference.provider✕
- Connections
- 2 pairs of types, where a type in features.logout.data uses a type in foundation.datasource.preference.provider.
- The types involved
com.wisnu.kurniawan.composetodolist.features.logout.data.LogoutEnvironment→com.wisnu.kurniawan.composetodolist.foundation.datasource.preference.provider.CredentialProvidercom.wisnu.kurniawan.composetodolist.features.logout.data.LogoutEnvironment→com.wisnu.kurniawan.composetodolist.foundation.datasource.preference.provider.UserProvider
- Direction
- features.logout.data uses foundation.datasource.preference.provider, so a change to foundation.datasource.preference.provider can break features.logout.data, while a change to features.logout.data can't break foundation.datasource.preference.provider.
- Position
- Below the diagonal: features.logout.data uses a module listed above it, which is the healthy direction.
16→3 features.splash.data uses model✕
- Connections
- 2 pairs of types, where a type in features.splash.data uses a type in model.
- The types involved
com.wisnu.kurniawan.composetodolist.features.splash.data.ISplashEnvironment→com.wisnu.kurniawan.composetodolist.model.Credentialcom.wisnu.kurniawan.composetodolist.features.splash.data.SplashEnvironment→com.wisnu.kurniawan.composetodolist.model.Credential
- Direction
- features.splash.data uses model, so a change to model can break features.splash.data, while a change to features.splash.data can't break model.
- Position
- Below the diagonal: features.splash.data uses a module listed above it, which is the healthy direction.
16→10 features.splash.data uses foundation.datasource.preference.provider✕
- Connections
- 1 pair of types, where a type in features.splash.data uses a type in foundation.datasource.preference.provider.
- The types involved
com.wisnu.kurniawan.composetodolist.features.splash.data.SplashEnvironment→com.wisnu.kurniawan.composetodolist.foundation.datasource.preference.provider.CredentialProvider
- Direction
- features.splash.data uses foundation.datasource.preference.provider, so a change to foundation.datasource.preference.provider can break features.splash.data, while a change to features.splash.data can't break foundation.datasource.preference.provider.
- Position
- Below the diagonal: features.splash.data uses a module listed above it, which is the healthy direction.
17→3 features.theme.data uses model✕
- Connections
- 2 pairs of types, where a type in features.theme.data uses a type in model.
- The types involved
com.wisnu.kurniawan.composetodolist.features.theme.data.IThemeEnvironment→com.wisnu.kurniawan.composetodolist.model.Themecom.wisnu.kurniawan.composetodolist.features.theme.data.ThemeEnvironment→com.wisnu.kurniawan.composetodolist.model.Theme
- Direction
- features.theme.data uses model, so a change to model can break features.theme.data, while a change to features.theme.data can't break model.
- Position
- Below the diagonal: features.theme.data uses a module listed above it, which is the healthy direction.
17→10 features.theme.data uses foundation.datasource.preference.provider✕
- Connections
- 1 pair of types, where a type in features.theme.data uses a type in foundation.datasource.preference.provider.
- The types involved
com.wisnu.kurniawan.composetodolist.features.theme.data.ThemeEnvironment→com.wisnu.kurniawan.composetodolist.foundation.datasource.preference.provider.ThemeProvider
- Direction
- features.theme.data uses foundation.datasource.preference.provider, so a change to foundation.datasource.preference.provider can break features.theme.data, while a change to features.theme.data can't break foundation.datasource.preference.provider.
- Position
- Below the diagonal: features.theme.data uses a module listed above it, which is the healthy direction.
18→8 features.todo.step.ui.StepAction.StepItemAction uses features.todo.step.ui.StepAction✕
- Connections
- 2 pairs of types, where a type in features.todo.step.ui.StepAction.StepItemAction uses a type in features.todo.step.ui.StepAction.
- The types involved
com.wisnu.kurniawan.composetodolist.features.todo.step.ui.StepAction.StepItemAction.Create→com.wisnu.kurniawan.composetodolist.features.todo.step.ui.StepAction.StepItemActioncom.wisnu.kurniawan.composetodolist.features.todo.step.ui.StepAction.StepItemAction.Edit→com.wisnu.kurniawan.composetodolist.features.todo.step.ui.StepAction.StepItemAction
- Direction
- features.todo.step.ui.StepAction.StepItemAction uses features.todo.step.ui.StepAction, so a change to features.todo.step.ui.StepAction can break features.todo.step.ui.StepAction.StepItemAction, while a change to features.todo.step.ui.StepAction.StepItemAction can't break features.todo.step.ui.StepAction.
- Position
- Below the diagonal: features.todo.step.ui.StepAction.StepItemAction uses a module listed above it, which is the healthy direction.
19→3 foundation.datasource.local.provider uses model✕
- Connections
- 10 pairs of types, where a type in foundation.datasource.local.provider uses a type in model.
- The types involved
com.wisnu.kurniawan.composetodolist.foundation.datasource.local.provider.ToDoGroupProvider→com.wisnu.kurniawan.composetodolist.model.ToDoGroupcom.wisnu.kurniawan.composetodolist.foundation.datasource.local.provider.ToDoListProvider→com.wisnu.kurniawan.composetodolist.model.GroupIdWithListcom.wisnu.kurniawan.composetodolist.foundation.datasource.local.provider.ToDoListProvider→com.wisnu.kurniawan.composetodolist.model.ToDoListcom.wisnu.kurniawan.composetodolist.foundation.datasource.local.provider.ToDoStepProvider→com.wisnu.kurniawan.composetodolist.model.ToDoStatuscom.wisnu.kurniawan.composetodolist.foundation.datasource.local.provider.ToDoStepProvider→com.wisnu.kurniawan.composetodolist.model.ToDoStepcom.wisnu.kurniawan.composetodolist.foundation.datasource.local.provider.ToDoTaskProvider→com.wisnu.kurniawan.composetodolist.model.TaskWithListcom.wisnu.kurniawan.composetodolist.foundation.datasource.local.provider.ToDoTaskProvider→com.wisnu.kurniawan.composetodolist.model.ToDoRepeatcom.wisnu.kurniawan.composetodolist.foundation.datasource.local.provider.ToDoTaskProvider→com.wisnu.kurniawan.composetodolist.model.ToDoStatuscom.wisnu.kurniawan.composetodolist.foundation.datasource.local.provider.ToDoTaskProvider→com.wisnu.kurniawan.composetodolist.model.ToDoTaskcom.wisnu.kurniawan.composetodolist.foundation.datasource.local.provider.ToDoTaskProvider→com.wisnu.kurniawan.composetodolist.model.ToDoTaskOverallCount
- Direction
- foundation.datasource.local.provider uses model, so a change to model can break foundation.datasource.local.provider, while a change to foundation.datasource.local.provider can't break model.
- Position
- Below the diagonal: foundation.datasource.local.provider uses a module listed above it, which is the healthy direction.
19→9 foundation.datasource.local.provider uses foundation.datasource.local.dao✕
- Connections
- 8 pairs of types, where a type in foundation.datasource.local.provider uses a type in foundation.datasource.local.dao.
- The types involved
com.wisnu.kurniawan.composetodolist.foundation.datasource.local.provider.ToDoGroupProvider→com.wisnu.kurniawan.composetodolist.foundation.datasource.local.dao.ToDoGroupReadDaocom.wisnu.kurniawan.composetodolist.foundation.datasource.local.provider.ToDoGroupProvider→com.wisnu.kurniawan.composetodolist.foundation.datasource.local.dao.ToDoGroupWriteDaocom.wisnu.kurniawan.composetodolist.foundation.datasource.local.provider.ToDoGroupProvider→com.wisnu.kurniawan.composetodolist.foundation.datasource.local.dao.ToDoListWriteDaocom.wisnu.kurniawan.composetodolist.foundation.datasource.local.provider.ToDoListProvider→com.wisnu.kurniawan.composetodolist.foundation.datasource.local.dao.ToDoListReadDaocom.wisnu.kurniawan.composetodolist.foundation.datasource.local.provider.ToDoListProvider→com.wisnu.kurniawan.composetodolist.foundation.datasource.local.dao.ToDoListWriteDaocom.wisnu.kurniawan.composetodolist.foundation.datasource.local.provider.ToDoStepProvider→com.wisnu.kurniawan.composetodolist.foundation.datasource.local.dao.ToDoStepWriteDaocom.wisnu.kurniawan.composetodolist.foundation.datasource.local.provider.ToDoTaskProvider→com.wisnu.kurniawan.composetodolist.foundation.datasource.local.dao.ToDoTaskReadDaocom.wisnu.kurniawan.composetodolist.foundation.datasource.local.provider.ToDoTaskProvider→com.wisnu.kurniawan.composetodolist.foundation.datasource.local.dao.ToDoTaskWriteDao
- Direction
- foundation.datasource.local.provider uses foundation.datasource.local.dao, so a change to foundation.datasource.local.dao can break foundation.datasource.local.provider, while a change to foundation.datasource.local.provider can't break foundation.datasource.local.dao.
- Position
- Below the diagonal: foundation.datasource.local.provider uses a module listed above it, which is the healthy direction.
20→3 features.localized.setting.ui uses model✕
- Connections
- 2 pairs of types, where a type in features.localized.setting.ui uses a type in model.
- The types involved
com.wisnu.kurniawan.composetodolist.features.localized.setting.ui.LanguageItem→com.wisnu.kurniawan.composetodolist.model.Languagecom.wisnu.kurniawan.composetodolist.features.localized.setting.ui.LocalizedSettingViewModelKt→com.wisnu.kurniawan.composetodolist.model.Language
- Direction
- features.localized.setting.ui uses model, so a change to model can break features.localized.setting.ui, while a change to features.localized.setting.ui can't break model.
- Position
- Below the diagonal: features.localized.setting.ui uses a module listed above it, which is the healthy direction.
20→13 features.localized.setting.ui uses features.localized.setting.data✕
- Connections
- 1 pair of types, where a type in features.localized.setting.ui uses a type in features.localized.setting.data.
- The types involved
com.wisnu.kurniawan.composetodolist.features.localized.setting.ui.LocalizedSettingViewModel→com.wisnu.kurniawan.composetodolist.features.localized.setting.data.ILocalizedSettingEnvironment
- Direction
- features.localized.setting.ui uses features.localized.setting.data, so a change to features.localized.setting.data can break features.localized.setting.ui, while a change to features.localized.setting.ui can't break features.localized.setting.data.
- Position
- Below the diagonal: features.localized.setting.ui uses a module listed above it, which is the healthy direction.
21→14 features.login.ui uses features.login.data✕
- Connections
- 1 pair of types, where a type in features.login.ui uses a type in features.login.data.
- The types involved
com.wisnu.kurniawan.composetodolist.features.login.ui.LoginViewModel→com.wisnu.kurniawan.composetodolist.features.login.data.ILoginEnvironment
- Direction
- features.login.ui uses features.login.data, so a change to features.login.data can break features.login.ui, while a change to features.login.ui can't break features.login.data.
- Position
- Below the diagonal: features.login.ui uses a module listed above it, which is the healthy direction.
22→3 features.logout.ui uses model✕
- Connections
- 1 pair of types, where a type in features.logout.ui uses a type in model.
- The types involved
com.wisnu.kurniawan.composetodolist.features.logout.ui.LogoutState→com.wisnu.kurniawan.composetodolist.model.User
- Direction
- features.logout.ui uses model, so a change to model can break features.logout.ui, while a change to features.logout.ui can't break model.
- Position
- Below the diagonal: features.logout.ui uses a module listed above it, which is the healthy direction.
22→15 features.logout.ui uses features.logout.data✕
- Connections
- 1 pair of types, where a type in features.logout.ui uses a type in features.logout.data.
- The types involved
com.wisnu.kurniawan.composetodolist.features.logout.ui.LogoutViewModel→com.wisnu.kurniawan.composetodolist.features.logout.data.ILogoutEnvironment
- Direction
- features.logout.ui uses features.logout.data, so a change to features.logout.data can break features.logout.ui, while a change to features.logout.ui can't break features.logout.data.
- Position
- Below the diagonal: features.logout.ui uses a module listed above it, which is the healthy direction.
23→2 features.todo.all.data uses foundation.wrapper✕
- Connections
- 2 pairs of types, where a type in features.todo.all.data uses a type in foundation.wrapper.
- The types involved
com.wisnu.kurniawan.composetodolist.features.todo.all.data.AllEnvironment→com.wisnu.kurniawan.composetodolist.foundation.wrapper.DateTimeProvidercom.wisnu.kurniawan.composetodolist.features.todo.all.data.IAllEnvironment→com.wisnu.kurniawan.composetodolist.foundation.wrapper.DateTimeProvider
- Direction
- features.todo.all.data uses foundation.wrapper, so a change to foundation.wrapper can break features.todo.all.data, while a change to features.todo.all.data can't break foundation.wrapper.
- Position
- Below the diagonal: features.todo.all.data uses a module listed above it, which is the healthy direction.
23→3 features.todo.all.data uses model✕
- Connections
- 4 pairs of types, where a type in features.todo.all.data uses a type in model.
- The types involved
com.wisnu.kurniawan.composetodolist.features.todo.all.data.AllEnvironment→com.wisnu.kurniawan.composetodolist.model.ToDoListcom.wisnu.kurniawan.composetodolist.features.todo.all.data.AllEnvironment→com.wisnu.kurniawan.composetodolist.model.ToDoTaskcom.wisnu.kurniawan.composetodolist.features.todo.all.data.IAllEnvironment→com.wisnu.kurniawan.composetodolist.model.ToDoListcom.wisnu.kurniawan.composetodolist.features.todo.all.data.IAllEnvironment→com.wisnu.kurniawan.composetodolist.model.ToDoTask
- Direction
- features.todo.all.data uses model, so a change to model can break features.todo.all.data, while a change to features.todo.all.data can't break model.
- Position
- Below the diagonal: features.todo.all.data uses a module listed above it, which is the healthy direction.
23→19 features.todo.all.data uses foundation.datasource.local.provider✕
- Connections
- 2 pairs of types, where a type in features.todo.all.data uses a type in foundation.datasource.local.provider.
- The types involved
com.wisnu.kurniawan.composetodolist.features.todo.all.data.AllEnvironment→com.wisnu.kurniawan.composetodolist.foundation.datasource.local.provider.ToDoListProvidercom.wisnu.kurniawan.composetodolist.features.todo.all.data.AllEnvironment→com.wisnu.kurniawan.composetodolist.foundation.datasource.local.provider.ToDoTaskProvider
- Direction
- features.todo.all.data uses foundation.datasource.local.provider, so a change to foundation.datasource.local.provider can break features.todo.all.data, while a change to features.todo.all.data can't break foundation.datasource.local.provider.
- Position
- Below the diagonal: features.todo.all.data uses a module listed above it, which is the healthy direction.
24→2 features.todo.detail.data uses foundation.wrapper✕
- Connections
- 4 pairs of types, where a type in features.todo.detail.data uses a type in foundation.wrapper.
- The types involved
com.wisnu.kurniawan.composetodolist.features.todo.detail.data.IListDetailEnvironment→com.wisnu.kurniawan.composetodolist.foundation.wrapper.DateTimeProvidercom.wisnu.kurniawan.composetodolist.features.todo.detail.data.IListDetailEnvironment→com.wisnu.kurniawan.composetodolist.foundation.wrapper.IdProvidercom.wisnu.kurniawan.composetodolist.features.todo.detail.data.ListDetailEnvironment→com.wisnu.kurniawan.composetodolist.foundation.wrapper.DateTimeProvidercom.wisnu.kurniawan.composetodolist.features.todo.detail.data.ListDetailEnvironment→com.wisnu.kurniawan.composetodolist.foundation.wrapper.IdProvider
- Direction
- features.todo.detail.data uses foundation.wrapper, so a change to foundation.wrapper can break features.todo.detail.data, while a change to features.todo.detail.data can't break foundation.wrapper.
- Position
- Below the diagonal: features.todo.detail.data uses a module listed above it, which is the healthy direction.
24→3 features.todo.detail.data uses model✕
- Connections
- 4 pairs of types, where a type in features.todo.detail.data uses a type in model.
- The types involved
com.wisnu.kurniawan.composetodolist.features.todo.detail.data.IListDetailEnvironment→com.wisnu.kurniawan.composetodolist.model.ToDoListcom.wisnu.kurniawan.composetodolist.features.todo.detail.data.IListDetailEnvironment→com.wisnu.kurniawan.composetodolist.model.ToDoTaskcom.wisnu.kurniawan.composetodolist.features.todo.detail.data.ListDetailEnvironment→com.wisnu.kurniawan.composetodolist.model.ToDoListcom.wisnu.kurniawan.composetodolist.features.todo.detail.data.ListDetailEnvironment→com.wisnu.kurniawan.composetodolist.model.ToDoTask
- Direction
- features.todo.detail.data uses model, so a change to model can break features.todo.detail.data, while a change to features.todo.detail.data can't break model.
- Position
- Below the diagonal: features.todo.detail.data uses a module listed above it, which is the healthy direction.
24→19 features.todo.detail.data uses foundation.datasource.local.provider✕
- Connections
- 2 pairs of types, where a type in features.todo.detail.data uses a type in foundation.datasource.local.provider.
- The types involved
com.wisnu.kurniawan.composetodolist.features.todo.detail.data.ListDetailEnvironment→com.wisnu.kurniawan.composetodolist.foundation.datasource.local.provider.ToDoListProvidercom.wisnu.kurniawan.composetodolist.features.todo.detail.data.ListDetailEnvironment→com.wisnu.kurniawan.composetodolist.foundation.datasource.local.provider.ToDoTaskProvider
- Direction
- features.todo.detail.data uses foundation.datasource.local.provider, so a change to foundation.datasource.local.provider can break features.todo.detail.data, while a change to features.todo.detail.data can't break foundation.datasource.local.provider.
- Position
- Below the diagonal: features.todo.detail.data uses a module listed above it, which is the healthy direction.
25→2 features.todo.group.data uses foundation.wrapper✕
- Connections
- 4 pairs of types, where a type in features.todo.group.data uses a type in foundation.wrapper.
- The types involved
com.wisnu.kurniawan.composetodolist.features.todo.group.data.CreateGroupEnvironment→com.wisnu.kurniawan.composetodolist.foundation.wrapper.DateTimeProvidercom.wisnu.kurniawan.composetodolist.features.todo.group.data.CreateGroupEnvironment→com.wisnu.kurniawan.composetodolist.foundation.wrapper.IdProvidercom.wisnu.kurniawan.composetodolist.features.todo.group.data.ICreateGroupEnvironment→com.wisnu.kurniawan.composetodolist.foundation.wrapper.DateTimeProvidercom.wisnu.kurniawan.composetodolist.features.todo.group.data.ICreateGroupEnvironment→com.wisnu.kurniawan.composetodolist.foundation.wrapper.IdProvider
- Direction
- features.todo.group.data uses foundation.wrapper, so a change to foundation.wrapper can break features.todo.group.data, while a change to features.todo.group.data can't break foundation.wrapper.
- Position
- Below the diagonal: features.todo.group.data uses a module listed above it, which is the healthy direction.
25→3 features.todo.group.data uses model✕
- Connections
- 2 pairs of types, where a type in features.todo.group.data uses a type in model.
- The types involved
com.wisnu.kurniawan.composetodolist.features.todo.group.data.CreateGroupEnvironment→com.wisnu.kurniawan.composetodolist.model.ToDoGroupcom.wisnu.kurniawan.composetodolist.features.todo.group.data.ICreateGroupEnvironment→com.wisnu.kurniawan.composetodolist.model.ToDoGroup
- Direction
- features.todo.group.data uses model, so a change to model can break features.todo.group.data, while a change to features.todo.group.data can't break model.
- Position
- Below the diagonal: features.todo.group.data uses a module listed above it, which is the healthy direction.
25→19 features.todo.group.data uses foundation.datasource.local.provider✕
- Connections
- 1 pair of types, where a type in features.todo.group.data uses a type in foundation.datasource.local.provider.
- The types involved
com.wisnu.kurniawan.composetodolist.features.todo.group.data.CreateGroupEnvironment→com.wisnu.kurniawan.composetodolist.foundation.datasource.local.provider.ToDoGroupProvider
- Direction
- features.todo.group.data uses foundation.datasource.local.provider, so a change to foundation.datasource.local.provider can break features.todo.group.data, while a change to features.todo.group.data can't break foundation.datasource.local.provider.
- Position
- Below the diagonal: features.todo.group.data uses a module listed above it, which is the healthy direction.
26→2 features.todo.grouplist.data uses foundation.wrapper✕
- Connections
- 2 pairs of types, where a type in features.todo.grouplist.data uses a type in foundation.wrapper.
- The types involved
com.wisnu.kurniawan.composetodolist.features.todo.grouplist.data.IUpdateGroupListEnvironment→com.wisnu.kurniawan.composetodolist.foundation.wrapper.DateTimeProvidercom.wisnu.kurniawan.composetodolist.features.todo.grouplist.data.UpdateGroupListEnvironment→com.wisnu.kurniawan.composetodolist.foundation.wrapper.DateTimeProvider
- Direction
- features.todo.grouplist.data uses foundation.wrapper, so a change to foundation.wrapper can break features.todo.grouplist.data, while a change to features.todo.grouplist.data can't break foundation.wrapper.
- Position
- Below the diagonal: features.todo.grouplist.data uses a module listed above it, which is the healthy direction.
26→3 features.todo.grouplist.data uses model✕
- Connections
- 2 pairs of types, where a type in features.todo.grouplist.data uses a type in model.
- The types involved
com.wisnu.kurniawan.composetodolist.features.todo.grouplist.data.IUpdateGroupListEnvironment→com.wisnu.kurniawan.composetodolist.model.GroupIdWithListcom.wisnu.kurniawan.composetodolist.features.todo.grouplist.data.UpdateGroupListEnvironment→com.wisnu.kurniawan.composetodolist.model.GroupIdWithList
- Direction
- features.todo.grouplist.data uses model, so a change to model can break features.todo.grouplist.data, while a change to features.todo.grouplist.data can't break model.
- Position
- Below the diagonal: features.todo.grouplist.data uses a module listed above it, which is the healthy direction.
26→19 features.todo.grouplist.data uses foundation.datasource.local.provider✕
- Connections
- 1 pair of types, where a type in features.todo.grouplist.data uses a type in foundation.datasource.local.provider.
- The types involved
com.wisnu.kurniawan.composetodolist.features.todo.grouplist.data.UpdateGroupListEnvironment→com.wisnu.kurniawan.composetodolist.foundation.datasource.local.provider.ToDoListProvider
- Direction
- features.todo.grouplist.data uses foundation.datasource.local.provider, so a change to foundation.datasource.local.provider can break features.todo.grouplist.data, while a change to features.todo.grouplist.data can't break foundation.datasource.local.provider.
- Position
- Below the diagonal: features.todo.grouplist.data uses a module listed above it, which is the healthy direction.
27→2 features.todo.groupmenu.data uses foundation.wrapper✕
- Connections
- 2 pairs of types, where a type in features.todo.groupmenu.data uses a type in foundation.wrapper.
- The types involved
com.wisnu.kurniawan.composetodolist.features.todo.groupmenu.data.GroupMenuEnvironment→com.wisnu.kurniawan.composetodolist.foundation.wrapper.DateTimeProvidercom.wisnu.kurniawan.composetodolist.features.todo.groupmenu.data.IGroupMenuEnvironment→com.wisnu.kurniawan.composetodolist.foundation.wrapper.DateTimeProvider
- Direction
- features.todo.groupmenu.data uses foundation.wrapper, so a change to foundation.wrapper can break features.todo.groupmenu.data, while a change to features.todo.groupmenu.data can't break foundation.wrapper.
- Position
- Below the diagonal: features.todo.groupmenu.data uses a module listed above it, which is the healthy direction.
27→19 features.todo.groupmenu.data uses foundation.datasource.local.provider✕
- Connections
- 2 pairs of types, where a type in features.todo.groupmenu.data uses a type in foundation.datasource.local.provider.
- The types involved
com.wisnu.kurniawan.composetodolist.features.todo.groupmenu.data.GroupMenuEnvironment→com.wisnu.kurniawan.composetodolist.foundation.datasource.local.provider.ToDoGroupProvidercom.wisnu.kurniawan.composetodolist.features.todo.groupmenu.data.GroupMenuEnvironment→com.wisnu.kurniawan.composetodolist.foundation.datasource.local.provider.ToDoListProvider
- Direction
- features.todo.groupmenu.data uses foundation.datasource.local.provider, so a change to foundation.datasource.local.provider can break features.todo.groupmenu.data, while a change to features.todo.groupmenu.data can't break foundation.datasource.local.provider.
- Position
- Below the diagonal: features.todo.groupmenu.data uses a module listed above it, which is the healthy direction.
28→2 features.todo.main.data uses foundation.wrapper✕
- Connections
- 2 pairs of types, where a type in features.todo.main.data uses a type in foundation.wrapper.
- The types involved
com.wisnu.kurniawan.composetodolist.features.todo.main.data.IToDoMainEnvironment→com.wisnu.kurniawan.composetodolist.foundation.wrapper.DateTimeProvidercom.wisnu.kurniawan.composetodolist.features.todo.main.data.ToDoMainEnvironment→com.wisnu.kurniawan.composetodolist.foundation.wrapper.DateTimeProvider
- Direction
- features.todo.main.data uses foundation.wrapper, so a change to foundation.wrapper can break features.todo.main.data, while a change to features.todo.main.data can't break foundation.wrapper.
- Position
- Below the diagonal: features.todo.main.data uses a module listed above it, which is the healthy direction.
28→3 features.todo.main.data uses model✕
- Connections
- 6 pairs of types, where a type in features.todo.main.data uses a type in model.
- The types involved
com.wisnu.kurniawan.composetodolist.features.todo.main.data.IToDoMainEnvironment→com.wisnu.kurniawan.composetodolist.model.ToDoGroupcom.wisnu.kurniawan.composetodolist.features.todo.main.data.IToDoMainEnvironment→com.wisnu.kurniawan.composetodolist.model.ToDoListcom.wisnu.kurniawan.composetodolist.features.todo.main.data.IToDoMainEnvironment→com.wisnu.kurniawan.composetodolist.model.ToDoTaskOverallCountcom.wisnu.kurniawan.composetodolist.features.todo.main.data.ToDoMainEnvironment→com.wisnu.kurniawan.composetodolist.model.ToDoGroupcom.wisnu.kurniawan.composetodolist.features.todo.main.data.ToDoMainEnvironment→com.wisnu.kurniawan.composetodolist.model.ToDoListcom.wisnu.kurniawan.composetodolist.features.todo.main.data.ToDoMainEnvironment→com.wisnu.kurniawan.composetodolist.model.ToDoTaskOverallCount
- Direction
- features.todo.main.data uses model, so a change to model can break features.todo.main.data, while a change to features.todo.main.data can't break model.
- Position
- Below the diagonal: features.todo.main.data uses a module listed above it, which is the healthy direction.
28→19 features.todo.main.data uses foundation.datasource.local.provider✕
- Connections
- 3 pairs of types, where a type in features.todo.main.data uses a type in foundation.datasource.local.provider.
- The types involved
com.wisnu.kurniawan.composetodolist.features.todo.main.data.ToDoMainEnvironment→com.wisnu.kurniawan.composetodolist.foundation.datasource.local.provider.ToDoGroupProvidercom.wisnu.kurniawan.composetodolist.features.todo.main.data.ToDoMainEnvironment→com.wisnu.kurniawan.composetodolist.foundation.datasource.local.provider.ToDoListProvidercom.wisnu.kurniawan.composetodolist.features.todo.main.data.ToDoMainEnvironment→com.wisnu.kurniawan.composetodolist.foundation.datasource.local.provider.ToDoTaskProvider
- Direction
- features.todo.main.data uses foundation.datasource.local.provider, so a change to foundation.datasource.local.provider can break features.todo.main.data, while a change to features.todo.main.data can't break foundation.datasource.local.provider.
- Position
- Below the diagonal: features.todo.main.data uses a module listed above it, which is the healthy direction.
29→2 features.todo.scheduled.data uses foundation.wrapper✕
- Connections
- 4 pairs of types, where a type in features.todo.scheduled.data uses a type in foundation.wrapper.
- The types involved
com.wisnu.kurniawan.composetodolist.features.todo.scheduled.data.IScheduledEnvironment→com.wisnu.kurniawan.composetodolist.foundation.wrapper.DateTimeProvidercom.wisnu.kurniawan.composetodolist.features.todo.scheduled.data.IScheduledEnvironment→com.wisnu.kurniawan.composetodolist.foundation.wrapper.IdProvidercom.wisnu.kurniawan.composetodolist.features.todo.scheduled.data.ScheduledEnvironment→com.wisnu.kurniawan.composetodolist.foundation.wrapper.DateTimeProvidercom.wisnu.kurniawan.composetodolist.features.todo.scheduled.data.ScheduledEnvironment→com.wisnu.kurniawan.composetodolist.foundation.wrapper.IdProvider
- Direction
- features.todo.scheduled.data uses foundation.wrapper, so a change to foundation.wrapper can break features.todo.scheduled.data, while a change to features.todo.scheduled.data can't break foundation.wrapper.
- Position
- Below the diagonal: features.todo.scheduled.data uses a module listed above it, which is the healthy direction.
29→3 features.todo.scheduled.data uses model✕
- Connections
- 4 pairs of types, where a type in features.todo.scheduled.data uses a type in model.
- The types involved
com.wisnu.kurniawan.composetodolist.features.todo.scheduled.data.IScheduledEnvironment→com.wisnu.kurniawan.composetodolist.model.TaskWithListcom.wisnu.kurniawan.composetodolist.features.todo.scheduled.data.IScheduledEnvironment→com.wisnu.kurniawan.composetodolist.model.ToDoTaskcom.wisnu.kurniawan.composetodolist.features.todo.scheduled.data.ScheduledEnvironment→com.wisnu.kurniawan.composetodolist.model.TaskWithListcom.wisnu.kurniawan.composetodolist.features.todo.scheduled.data.ScheduledEnvironment→com.wisnu.kurniawan.composetodolist.model.ToDoTask
- Direction
- features.todo.scheduled.data uses model, so a change to model can break features.todo.scheduled.data, while a change to features.todo.scheduled.data can't break model.
- Position
- Below the diagonal: features.todo.scheduled.data uses a module listed above it, which is the healthy direction.
29→19 features.todo.scheduled.data uses foundation.datasource.local.provider✕
- Connections
- 1 pair of types, where a type in features.todo.scheduled.data uses a type in foundation.datasource.local.provider.
- The types involved
com.wisnu.kurniawan.composetodolist.features.todo.scheduled.data.ScheduledEnvironment→com.wisnu.kurniawan.composetodolist.foundation.datasource.local.provider.ToDoTaskProvider
- Direction
- features.todo.scheduled.data uses foundation.datasource.local.provider, so a change to foundation.datasource.local.provider can break features.todo.scheduled.data, while a change to features.todo.scheduled.data can't break foundation.datasource.local.provider.
- Position
- Below the diagonal: features.todo.scheduled.data uses a module listed above it, which is the healthy direction.
30→2 features.todo.search.data uses foundation.wrapper✕
- Connections
- 1 pair of types, where a type in features.todo.search.data uses a type in foundation.wrapper.
- The types involved
com.wisnu.kurniawan.composetodolist.features.todo.search.data.SearchEnvironment→com.wisnu.kurniawan.composetodolist.foundation.wrapper.DateTimeProvider
- Direction
- features.todo.search.data uses foundation.wrapper, so a change to foundation.wrapper can break features.todo.search.data, while a change to features.todo.search.data can't break foundation.wrapper.
- Position
- Below the diagonal: features.todo.search.data uses a module listed above it, which is the healthy direction.
30→3 features.todo.search.data uses model✕
- Connections
- 4 pairs of types, where a type in features.todo.search.data uses a type in model.
- The types involved
com.wisnu.kurniawan.composetodolist.features.todo.search.data.ISearchEnvironment→com.wisnu.kurniawan.composetodolist.model.ToDoListcom.wisnu.kurniawan.composetodolist.features.todo.search.data.ISearchEnvironment→com.wisnu.kurniawan.composetodolist.model.ToDoTaskcom.wisnu.kurniawan.composetodolist.features.todo.search.data.SearchEnvironment→com.wisnu.kurniawan.composetodolist.model.ToDoListcom.wisnu.kurniawan.composetodolist.features.todo.search.data.SearchEnvironment→com.wisnu.kurniawan.composetodolist.model.ToDoTask
- Direction
- features.todo.search.data uses model, so a change to model can break features.todo.search.data, while a change to features.todo.search.data can't break model.
- Position
- Below the diagonal: features.todo.search.data uses a module listed above it, which is the healthy direction.
30→19 features.todo.search.data uses foundation.datasource.local.provider✕
- Connections
- 1 pair of types, where a type in features.todo.search.data uses a type in foundation.datasource.local.provider.
- The types involved
com.wisnu.kurniawan.composetodolist.features.todo.search.data.SearchEnvironment→com.wisnu.kurniawan.composetodolist.foundation.datasource.local.provider.ToDoTaskProvider
- Direction
- features.todo.search.data uses foundation.datasource.local.provider, so a change to foundation.datasource.local.provider can break features.todo.search.data, while a change to features.todo.search.data can't break foundation.datasource.local.provider.
- Position
- Below the diagonal: features.todo.search.data uses a module listed above it, which is the healthy direction.
31→2 features.todo.step.data uses foundation.wrapper✕
- Connections
- 4 pairs of types, where a type in features.todo.step.data uses a type in foundation.wrapper.
- The types involved
com.wisnu.kurniawan.composetodolist.features.todo.step.data.IStepEnvironment→com.wisnu.kurniawan.composetodolist.foundation.wrapper.DateTimeProvidercom.wisnu.kurniawan.composetodolist.features.todo.step.data.IStepEnvironment→com.wisnu.kurniawan.composetodolist.foundation.wrapper.IdProvidercom.wisnu.kurniawan.composetodolist.features.todo.step.data.StepEnvironment→com.wisnu.kurniawan.composetodolist.foundation.wrapper.DateTimeProvidercom.wisnu.kurniawan.composetodolist.features.todo.step.data.StepEnvironment→com.wisnu.kurniawan.composetodolist.foundation.wrapper.IdProvider
- Direction
- features.todo.step.data uses foundation.wrapper, so a change to foundation.wrapper can break features.todo.step.data, while a change to features.todo.step.data can't break foundation.wrapper.
- Position
- Below the diagonal: features.todo.step.data uses a module listed above it, which is the healthy direction.
31→3 features.todo.step.data uses model✕
- Connections
- 8 pairs of types, where a type in features.todo.step.data uses a type in model.
- The types involved
com.wisnu.kurniawan.composetodolist.features.todo.step.data.IStepEnvironment→com.wisnu.kurniawan.composetodolist.model.ToDoColorcom.wisnu.kurniawan.composetodolist.features.todo.step.data.IStepEnvironment→com.wisnu.kurniawan.composetodolist.model.ToDoRepeatcom.wisnu.kurniawan.composetodolist.features.todo.step.data.IStepEnvironment→com.wisnu.kurniawan.composetodolist.model.ToDoStepcom.wisnu.kurniawan.composetodolist.features.todo.step.data.IStepEnvironment→com.wisnu.kurniawan.composetodolist.model.ToDoTaskcom.wisnu.kurniawan.composetodolist.features.todo.step.data.StepEnvironment→com.wisnu.kurniawan.composetodolist.model.ToDoColorcom.wisnu.kurniawan.composetodolist.features.todo.step.data.StepEnvironment→com.wisnu.kurniawan.composetodolist.model.ToDoRepeatcom.wisnu.kurniawan.composetodolist.features.todo.step.data.StepEnvironment→com.wisnu.kurniawan.composetodolist.model.ToDoStepcom.wisnu.kurniawan.composetodolist.features.todo.step.data.StepEnvironment→com.wisnu.kurniawan.composetodolist.model.ToDoTask
- Direction
- features.todo.step.data uses model, so a change to model can break features.todo.step.data, while a change to features.todo.step.data can't break model.
- Position
- Below the diagonal: features.todo.step.data uses a module listed above it, which is the healthy direction.
31→19 features.todo.step.data uses foundation.datasource.local.provider✕
- Connections
- 3 pairs of types, where a type in features.todo.step.data uses a type in foundation.datasource.local.provider.
- The types involved
com.wisnu.kurniawan.composetodolist.features.todo.step.data.StepEnvironment→com.wisnu.kurniawan.composetodolist.foundation.datasource.local.provider.ToDoListProvidercom.wisnu.kurniawan.composetodolist.features.todo.step.data.StepEnvironment→com.wisnu.kurniawan.composetodolist.foundation.datasource.local.provider.ToDoStepProvidercom.wisnu.kurniawan.composetodolist.features.todo.step.data.StepEnvironment→com.wisnu.kurniawan.composetodolist.foundation.datasource.local.provider.ToDoTaskProvider
- Direction
- features.todo.step.data uses foundation.datasource.local.provider, so a change to foundation.datasource.local.provider can break features.todo.step.data, while a change to features.todo.step.data can't break foundation.datasource.local.provider.
- Position
- Below the diagonal: features.todo.step.data uses a module listed above it, which is the healthy direction.
32→2 features.todo.taskreminder.data uses foundation.wrapper✕
- Connections
- 1 pair of types, where a type in features.todo.taskreminder.data uses a type in foundation.wrapper.
- The types involved
com.wisnu.kurniawan.composetodolist.features.todo.taskreminder.data.TaskReminderEnvironment→com.wisnu.kurniawan.composetodolist.foundation.wrapper.DateTimeProvider
- Direction
- features.todo.taskreminder.data uses foundation.wrapper, so a change to foundation.wrapper can break features.todo.taskreminder.data, while a change to features.todo.taskreminder.data can't break foundation.wrapper.
- Position
- Below the diagonal: features.todo.taskreminder.data uses a module listed above it, which is the healthy direction.
32→3 features.todo.taskreminder.data uses model✕
- Connections
- 7 pairs of types, where a type in features.todo.taskreminder.data uses a type in model.
- The types involved
com.wisnu.kurniawan.composetodolist.features.todo.taskreminder.data.ITaskReminderEnvironment→com.wisnu.kurniawan.composetodolist.model.TaskWithListcom.wisnu.kurniawan.composetodolist.features.todo.taskreminder.data.ITaskReminderEnvironment→com.wisnu.kurniawan.composetodolist.model.ToDoTaskcom.wisnu.kurniawan.composetodolist.features.todo.taskreminder.data.TaskAlarmManager→com.wisnu.kurniawan.composetodolist.model.ToDoTaskcom.wisnu.kurniawan.composetodolist.features.todo.taskreminder.data.TaskNotificationManager→com.wisnu.kurniawan.composetodolist.model.ToDoListcom.wisnu.kurniawan.composetodolist.features.todo.taskreminder.data.TaskNotificationManager→com.wisnu.kurniawan.composetodolist.model.ToDoTaskcom.wisnu.kurniawan.composetodolist.features.todo.taskreminder.data.TaskReminderEnvironment→com.wisnu.kurniawan.composetodolist.model.TaskWithListcom.wisnu.kurniawan.composetodolist.features.todo.taskreminder.data.TaskReminderEnvironment→com.wisnu.kurniawan.composetodolist.model.ToDoTask
- Direction
- features.todo.taskreminder.data uses model, so a change to model can break features.todo.taskreminder.data, while a change to features.todo.taskreminder.data can't break model.
- Position
- Below the diagonal: features.todo.taskreminder.data uses a module listed above it, which is the healthy direction.
32→19 features.todo.taskreminder.data uses foundation.datasource.local.provider✕
- Connections
- 1 pair of types, where a type in features.todo.taskreminder.data uses a type in foundation.datasource.local.provider.
- The types involved
com.wisnu.kurniawan.composetodolist.features.todo.taskreminder.data.TaskReminderEnvironment→com.wisnu.kurniawan.composetodolist.foundation.datasource.local.provider.ToDoTaskProvider
- Direction
- features.todo.taskreminder.data uses foundation.datasource.local.provider, so a change to foundation.datasource.local.provider can break features.todo.taskreminder.data, while a change to features.todo.taskreminder.data can't break foundation.datasource.local.provider.
- Position
- Below the diagonal: features.todo.taskreminder.data uses a module listed above it, which is the healthy direction.
33→2 features.dashboard.data uses foundation.wrapper✕
- Connections
- 1 pair of types, where a type in features.dashboard.data uses a type in foundation.wrapper.
- The types involved
com.wisnu.kurniawan.composetodolist.features.dashboard.data.DashboardEnvironment→com.wisnu.kurniawan.composetodolist.foundation.wrapper.DateTimeProvider
- Direction
- features.dashboard.data uses foundation.wrapper, so a change to foundation.wrapper can break features.dashboard.data, while a change to features.dashboard.data can't break foundation.wrapper.
- Position
- Below the diagonal: features.dashboard.data uses a module listed above it, which is the healthy direction.
33→3 features.dashboard.data uses model✕
- Connections
- 4 pairs of types, where a type in features.dashboard.data uses a type in model.
- The types involved
com.wisnu.kurniawan.composetodolist.features.dashboard.data.DashboardEnvironment→com.wisnu.kurniawan.composetodolist.model.ToDoTaskDiffcom.wisnu.kurniawan.composetodolist.features.dashboard.data.DashboardEnvironment→com.wisnu.kurniawan.composetodolist.model.Usercom.wisnu.kurniawan.composetodolist.features.dashboard.data.IDashboardEnvironment→com.wisnu.kurniawan.composetodolist.model.ToDoTaskDiffcom.wisnu.kurniawan.composetodolist.features.dashboard.data.IDashboardEnvironment→com.wisnu.kurniawan.composetodolist.model.User
- Direction
- features.dashboard.data uses model, so a change to model can break features.dashboard.data, while a change to features.dashboard.data can't break model.
- Position
- Below the diagonal: features.dashboard.data uses a module listed above it, which is the healthy direction.
33→10 features.dashboard.data uses foundation.datasource.preference.provider✕
- Connections
- 1 pair of types, where a type in features.dashboard.data uses a type in foundation.datasource.preference.provider.
- The types involved
com.wisnu.kurniawan.composetodolist.features.dashboard.data.DashboardEnvironment→com.wisnu.kurniawan.composetodolist.foundation.datasource.preference.provider.UserProvider
- Direction
- features.dashboard.data uses foundation.datasource.preference.provider, so a change to foundation.datasource.preference.provider can break features.dashboard.data, while a change to features.dashboard.data can't break foundation.datasource.preference.provider.
- Position
- Below the diagonal: features.dashboard.data uses a module listed above it, which is the healthy direction.
33→19 features.dashboard.data uses foundation.datasource.local.provider✕
- Connections
- 1 pair of types, where a type in features.dashboard.data uses a type in foundation.datasource.local.provider.
- The types involved
com.wisnu.kurniawan.composetodolist.features.dashboard.data.DashboardEnvironment→com.wisnu.kurniawan.composetodolist.foundation.datasource.local.provider.ToDoTaskProvider
- Direction
- features.dashboard.data uses foundation.datasource.local.provider, so a change to foundation.datasource.local.provider can break features.dashboard.data, while a change to features.dashboard.data can't break foundation.datasource.local.provider.
- Position
- Below the diagonal: features.dashboard.data uses a module listed above it, which is the healthy direction.
33→32 features.dashboard.data uses features.todo.taskreminder.data✕
- Connections
- 2 pairs of types, where a type in features.dashboard.data uses a type in features.todo.taskreminder.data.
- The types involved
com.wisnu.kurniawan.composetodolist.features.dashboard.data.DashboardEnvironment→com.wisnu.kurniawan.composetodolist.features.todo.taskreminder.data.TaskAlarmManagercom.wisnu.kurniawan.composetodolist.features.dashboard.data.DashboardEnvironment→com.wisnu.kurniawan.composetodolist.features.todo.taskreminder.data.TaskNotificationManager
- Direction
- features.dashboard.data uses features.todo.taskreminder.data, so a change to features.todo.taskreminder.data can break features.dashboard.data, while a change to features.dashboard.data can't break features.todo.taskreminder.data.
- Position
- Below the diagonal: features.dashboard.data uses a module listed above it, which is the healthy direction.
34→3 features.todo.all.ui uses model✕
- Connections
- 3 pairs of types, where a type in features.todo.all.ui uses a type in model.
- The types involved
com.wisnu.kurniawan.composetodolist.features.todo.all.ui.AllScreenKt→com.wisnu.kurniawan.composetodolist.model.ToDoTaskcom.wisnu.kurniawan.composetodolist.features.todo.all.ui.AllState→com.wisnu.kurniawan.composetodolist.model.ToDoListcom.wisnu.kurniawan.composetodolist.features.todo.all.ui.AllViewModelKt→com.wisnu.kurniawan.composetodolist.model.ToDoList
- Direction
- features.todo.all.ui uses model, so a change to model can break features.todo.all.ui, while a change to features.todo.all.ui can't break model.
- Position
- Below the diagonal: features.todo.all.ui uses a module listed above it, which is the healthy direction.
34→4 features.todo.all.ui uses features.todo.all.ui.ItemAllState✕
- Connections
- 1 pair of types, where a type in features.todo.all.ui uses a type in features.todo.all.ui.ItemAllState.
- The types involved
com.wisnu.kurniawan.composetodolist.features.todo.all.ui.AllScreenKt→com.wisnu.kurniawan.composetodolist.features.todo.all.ui.ItemAllState.Task
- Direction
- features.todo.all.ui uses features.todo.all.ui.ItemAllState, so a change to features.todo.all.ui.ItemAllState can break features.todo.all.ui, while a change to features.todo.all.ui can't break features.todo.all.ui.ItemAllState.
- Position
- Below the diagonal: features.todo.all.ui uses a module listed above it, which is the healthy direction.
34→23 features.todo.all.ui uses features.todo.all.data✕
- Connections
- 1 pair of types, where a type in features.todo.all.ui uses a type in features.todo.all.data.
- The types involved
com.wisnu.kurniawan.composetodolist.features.todo.all.ui.AllViewModel→com.wisnu.kurniawan.composetodolist.features.todo.all.data.IAllEnvironment
- Direction
- features.todo.all.ui uses features.todo.all.data, so a change to features.todo.all.data can break features.todo.all.ui, while a change to features.todo.all.ui can't break features.todo.all.data.
- Position
- Below the diagonal: features.todo.all.ui uses a module listed above it, which is the healthy direction.
35→3 features.todo.main.ui uses model✕
- Connections
- 1 pair of types, where a type in features.todo.main.ui uses a type in model.
- The types involved
com.wisnu.kurniawan.composetodolist.features.todo.main.ui.ToDoMainState→com.wisnu.kurniawan.composetodolist.model.ToDoGroup
- Direction
- features.todo.main.ui uses model, so a change to model can break features.todo.main.ui, while a change to features.todo.main.ui can't break model.
- Position
- Below the diagonal: features.todo.main.ui uses a module listed above it, which is the healthy direction.
35→6 features.todo.main.ui uses features.todo.main.ui.ItemMainState✕
- Connections
- 3 pairs of types, where a type in features.todo.main.ui uses a type in features.todo.main.ui.ItemMainState.
- The types involved
com.wisnu.kurniawan.composetodolist.features.todo.main.ui.ToDoMainScreenKt→com.wisnu.kurniawan.composetodolist.features.todo.main.ui.ItemMainState.ItemGroupcom.wisnu.kurniawan.composetodolist.features.todo.main.ui.ToDoMainScreenKt→com.wisnu.kurniawan.composetodolist.features.todo.main.ui.ItemMainState.ItemListTypecom.wisnu.kurniawan.composetodolist.features.todo.main.ui.ToDoMainViewModelKt→com.wisnu.kurniawan.composetodolist.features.todo.main.ui.ItemMainState.ItemListType
- Direction
- features.todo.main.ui uses features.todo.main.ui.ItemMainState, so a change to features.todo.main.ui.ItemMainState can break features.todo.main.ui, while a change to features.todo.main.ui can't break features.todo.main.ui.ItemMainState.
- Position
- Below the diagonal: features.todo.main.ui uses a module listed above it, which is the healthy direction.
35→28 features.todo.main.ui uses features.todo.main.data✕
- Connections
- 1 pair of types, where a type in features.todo.main.ui uses a type in features.todo.main.data.
- The types involved
com.wisnu.kurniawan.composetodolist.features.todo.main.ui.ToDoMainViewModel→com.wisnu.kurniawan.composetodolist.features.todo.main.data.IToDoMainEnvironment
- Direction
- features.todo.main.ui uses features.todo.main.data, so a change to features.todo.main.data can break features.todo.main.ui, while a change to features.todo.main.ui can't break features.todo.main.data.
- Position
- Below the diagonal: features.todo.main.ui uses a module listed above it, which is the healthy direction.
36→3 features.todo.scheduled.ui uses model✕
- Connections
- 2 pairs of types, where a type in features.todo.scheduled.ui uses a type in model.
- The types involved
com.wisnu.kurniawan.composetodolist.features.todo.scheduled.ui.ScheduledScreenKt→com.wisnu.kurniawan.composetodolist.model.ToDoTaskcom.wisnu.kurniawan.composetodolist.features.todo.scheduled.ui.ScheduledState→com.wisnu.kurniawan.composetodolist.model.TaskWithList
- Direction
- features.todo.scheduled.ui uses model, so a change to model can break features.todo.scheduled.ui, while a change to features.todo.scheduled.ui can't break model.
- Position
- Below the diagonal: features.todo.scheduled.ui uses a module listed above it, which is the healthy direction.
36→7 features.todo.scheduled.ui uses features.todo.scheduled.ui.ItemScheduledState✕
- Connections
- 1 pair of types, where a type in features.todo.scheduled.ui uses a type in features.todo.scheduled.ui.ItemScheduledState.
- The types involved
com.wisnu.kurniawan.composetodolist.features.todo.scheduled.ui.ScheduledScreenKt→com.wisnu.kurniawan.composetodolist.features.todo.scheduled.ui.ItemScheduledState.Task
- Direction
- features.todo.scheduled.ui uses features.todo.scheduled.ui.ItemScheduledState, so a change to features.todo.scheduled.ui.ItemScheduledState can break features.todo.scheduled.ui, while a change to features.todo.scheduled.ui can't break features.todo.scheduled.ui.ItemScheduledState.
- Position
- Below the diagonal: features.todo.scheduled.ui uses a module listed above it, which is the healthy direction.
36→29 features.todo.scheduled.ui uses features.todo.scheduled.data✕
- Connections
- 1 pair of types, where a type in features.todo.scheduled.ui uses a type in features.todo.scheduled.data.
- The types involved
com.wisnu.kurniawan.composetodolist.features.todo.scheduled.ui.ScheduledViewModel→com.wisnu.kurniawan.composetodolist.features.todo.scheduled.data.IScheduledEnvironment
- Direction
- features.todo.scheduled.ui uses features.todo.scheduled.data, so a change to features.todo.scheduled.data can break features.todo.scheduled.ui, while a change to features.todo.scheduled.ui can't break features.todo.scheduled.data.
- Position
- Below the diagonal: features.todo.scheduled.ui uses a module listed above it, which is the healthy direction.
37→3 features.todo.step.ui uses model✕
- Connections
- 5 pairs of types, where a type in features.todo.step.ui uses a type in model.
- The types involved
com.wisnu.kurniawan.composetodolist.features.todo.step.ui.StepScreenKt→com.wisnu.kurniawan.composetodolist.model.ToDoStepcom.wisnu.kurniawan.composetodolist.features.todo.step.ui.StepScreenKt→com.wisnu.kurniawan.composetodolist.model.ToDoTaskcom.wisnu.kurniawan.composetodolist.features.todo.step.ui.StepState→com.wisnu.kurniawan.composetodolist.model.ToDoColorcom.wisnu.kurniawan.composetodolist.features.todo.step.ui.StepState→com.wisnu.kurniawan.composetodolist.model.ToDoTaskcom.wisnu.kurniawan.composetodolist.features.todo.step.ui.ToDoRepeatItem→com.wisnu.kurniawan.composetodolist.model.ToDoRepeat
- Direction
- features.todo.step.ui uses model, so a change to model can break features.todo.step.ui, while a change to features.todo.step.ui can't break model.
- Position
- Below the diagonal: features.todo.step.ui uses a module listed above it, which is the healthy direction.
37→8 features.todo.step.ui uses features.todo.step.ui.StepAction✕
- Connections
- 3 pairs of types, where a type in features.todo.step.ui uses a type in features.todo.step.ui.StepAction.
- The types involved
com.wisnu.kurniawan.composetodolist.features.todo.step.ui.StepViewModel→com.wisnu.kurniawan.composetodolist.features.todo.step.ui.StepAction.NoteActioncom.wisnu.kurniawan.composetodolist.features.todo.step.ui.StepViewModel→com.wisnu.kurniawan.composetodolist.features.todo.step.ui.StepAction.StepItemActioncom.wisnu.kurniawan.composetodolist.features.todo.step.ui.StepViewModel→com.wisnu.kurniawan.composetodolist.features.todo.step.ui.StepAction.TaskAction
- Direction
- features.todo.step.ui uses features.todo.step.ui.StepAction, so a change to features.todo.step.ui.StepAction can break features.todo.step.ui, while a change to features.todo.step.ui can't break features.todo.step.ui.StepAction.
- Position
- Below the diagonal: features.todo.step.ui uses a module listed above it, which is the healthy direction.
37→18 features.todo.step.ui uses features.todo.step.ui.StepAction.StepItemAction✕
- Connections
- 2 pairs of types, where a type in features.todo.step.ui uses a type in features.todo.step.ui.StepAction.StepItemAction.
- The types involved
com.wisnu.kurniawan.composetodolist.features.todo.step.ui.StepViewModel→com.wisnu.kurniawan.composetodolist.features.todo.step.ui.StepAction.StepItemAction.Createcom.wisnu.kurniawan.composetodolist.features.todo.step.ui.StepViewModel→com.wisnu.kurniawan.composetodolist.features.todo.step.ui.StepAction.StepItemAction.Edit
- Direction
- features.todo.step.ui uses features.todo.step.ui.StepAction.StepItemAction, so a change to features.todo.step.ui.StepAction.StepItemAction can break features.todo.step.ui, while a change to features.todo.step.ui can't break features.todo.step.ui.StepAction.StepItemAction.
- Position
- Below the diagonal: features.todo.step.ui uses a module listed above it, which is the healthy direction.
37→31 features.todo.step.ui uses features.todo.step.data✕
- Connections
- 1 pair of types, where a type in features.todo.step.ui uses a type in features.todo.step.data.
- The types involved
com.wisnu.kurniawan.composetodolist.features.todo.step.ui.StepViewModel→com.wisnu.kurniawan.composetodolist.features.todo.step.data.IStepEnvironment
- Direction
- features.todo.step.ui uses features.todo.step.data, so a change to features.todo.step.data can break features.todo.step.ui, while a change to features.todo.step.ui can't break features.todo.step.data.
- Position
- Below the diagonal: features.todo.step.ui uses a module listed above it, which is the healthy direction.
38→3 features.todo.detail.ui uses model✕
- Connections
- 6 pairs of types, where a type in features.todo.detail.ui uses a type in model.
- The types involved
com.wisnu.kurniawan.composetodolist.features.todo.detail.ui.ListDetailScreenKt→com.wisnu.kurniawan.composetodolist.model.ToDoTaskcom.wisnu.kurniawan.composetodolist.features.todo.detail.ui.ListDetailState→com.wisnu.kurniawan.composetodolist.model.ToDoListcom.wisnu.kurniawan.composetodolist.features.todo.detail.ui.ListDetailViewModel→com.wisnu.kurniawan.composetodolist.model.ToDoListcom.wisnu.kurniawan.composetodolist.features.todo.detail.ui.ListDetailViewModelKt→com.wisnu.kurniawan.composetodolist.model.ToDoRepeatcom.wisnu.kurniawan.composetodolist.features.todo.detail.ui.TaskScreenKt→com.wisnu.kurniawan.composetodolist.model.ToDoTaskcom.wisnu.kurniawan.composetodolist.features.todo.detail.ui.ToDoListState→com.wisnu.kurniawan.composetodolist.model.ToDoColor
- Direction
- features.todo.detail.ui uses model, so a change to model can break features.todo.detail.ui, while a change to features.todo.detail.ui can't break model.
- Position
- Below the diagonal: features.todo.detail.ui uses a module listed above it, which is the healthy direction.
38→5 features.todo.detail.ui uses features.todo.detail.ui.ListDetailAction✕
- Connections
- 2 pairs of types, where a type in features.todo.detail.ui uses a type in features.todo.detail.ui.ListDetailAction.
- The types involved
com.wisnu.kurniawan.composetodolist.features.todo.detail.ui.ListDetailViewModel→com.wisnu.kurniawan.composetodolist.features.todo.detail.ui.ListDetailAction.ListActioncom.wisnu.kurniawan.composetodolist.features.todo.detail.ui.ListDetailViewModel→com.wisnu.kurniawan.composetodolist.features.todo.detail.ui.ListDetailAction.TaskAction
- Direction
- features.todo.detail.ui uses features.todo.detail.ui.ListDetailAction, so a change to features.todo.detail.ui.ListDetailAction can break features.todo.detail.ui, while a change to features.todo.detail.ui can't break features.todo.detail.ui.ListDetailAction.
- Position
- Below the diagonal: features.todo.detail.ui uses a module listed above it, which is the healthy direction.
38→24 features.todo.detail.ui uses features.todo.detail.data✕
- Connections
- 1 pair of types, where a type in features.todo.detail.ui uses a type in features.todo.detail.data.
- The types involved
com.wisnu.kurniawan.composetodolist.features.todo.detail.ui.ListDetailViewModel→com.wisnu.kurniawan.composetodolist.features.todo.detail.data.IListDetailEnvironment
- Direction
- features.todo.detail.ui uses features.todo.detail.data, so a change to features.todo.detail.data can break features.todo.detail.ui, while a change to features.todo.detail.ui can't break features.todo.detail.data.
- Position
- Below the diagonal: features.todo.detail.ui uses a module listed above it, which is the healthy direction.
38→37 features.todo.detail.ui uses features.todo.step.ui✕
- Connections
- 1 pair of types, where a type in features.todo.detail.ui uses a type in features.todo.step.ui.
- The types involved
com.wisnu.kurniawan.composetodolist.features.todo.detail.ui.ListDetailViewModelKt→com.wisnu.kurniawan.composetodolist.features.todo.step.ui.ToDoRepeatItem
- Direction
- features.todo.detail.ui uses features.todo.step.ui, so a change to features.todo.step.ui can break features.todo.detail.ui, while a change to features.todo.detail.ui can't break features.todo.step.ui.
- Position
- Below the diagonal: features.todo.detail.ui uses a module listed above it, which is the healthy direction.
39→3 features.todo.search.ui uses model✕
- Connections
- 2 pairs of types, where a type in features.todo.search.ui uses a type in model.
- The types involved
com.wisnu.kurniawan.composetodolist.features.todo.search.ui.SearchScreenKt→com.wisnu.kurniawan.composetodolist.model.ToDoTaskcom.wisnu.kurniawan.composetodolist.features.todo.search.ui.SearchState→com.wisnu.kurniawan.composetodolist.model.ToDoList
- Direction
- features.todo.search.ui uses model, so a change to model can break features.todo.search.ui, while a change to features.todo.search.ui can't break model.
- Position
- Below the diagonal: features.todo.search.ui uses a module listed above it, which is the healthy direction.
39→4 features.todo.search.ui uses features.todo.all.ui.ItemAllState✕
- Connections
- 1 pair of types, where a type in features.todo.search.ui uses a type in features.todo.all.ui.ItemAllState.
- The types involved
com.wisnu.kurniawan.composetodolist.features.todo.search.ui.SearchScreenKt→com.wisnu.kurniawan.composetodolist.features.todo.all.ui.ItemAllState.Task
- Direction
- features.todo.search.ui uses features.todo.all.ui.ItemAllState, so a change to features.todo.all.ui.ItemAllState can break features.todo.search.ui, while a change to features.todo.search.ui can't break features.todo.all.ui.ItemAllState.
- Position
- Below the diagonal: features.todo.search.ui uses a module listed above it, which is the healthy direction.
39→30 features.todo.search.ui uses features.todo.search.data✕
- Connections
- 1 pair of types, where a type in features.todo.search.ui uses a type in features.todo.search.data.
- The types involved
com.wisnu.kurniawan.composetodolist.features.todo.search.ui.SearchViewModel→com.wisnu.kurniawan.composetodolist.features.todo.search.data.ISearchEnvironment
- Direction
- features.todo.search.ui uses features.todo.search.data, so a change to features.todo.search.data can break features.todo.search.ui, while a change to features.todo.search.ui can't break features.todo.search.data.
- Position
- Below the diagonal: features.todo.search.ui uses a module listed above it, which is the healthy direction.
39→34 features.todo.search.ui uses features.todo.all.ui✕
- Connections
- 2 pairs of types, where a type in features.todo.search.ui uses a type in features.todo.all.ui.
- The types involved
com.wisnu.kurniawan.composetodolist.features.todo.search.ui.SearchScreenKt→com.wisnu.kurniawan.composetodolist.features.todo.all.ui.ItemAllStatecom.wisnu.kurniawan.composetodolist.features.todo.search.ui.SearchState→com.wisnu.kurniawan.composetodolist.features.todo.all.ui.ItemAllState
- Direction
- features.todo.search.ui uses features.todo.all.ui, so a change to features.todo.all.ui can break features.todo.search.ui, while a change to features.todo.search.ui can't break features.todo.all.ui.
- Position
- Below the diagonal: features.todo.search.ui uses a module listed above it, which is the healthy direction.
40→3 features.dashboard.ui uses model✕
- Connections
- 2 pairs of types, where a type in features.dashboard.ui uses a type in model.
- The types involved
com.wisnu.kurniawan.composetodolist.features.dashboard.ui.DashboardScreenKt→com.wisnu.kurniawan.composetodolist.model.ToDoTaskcom.wisnu.kurniawan.composetodolist.features.dashboard.ui.DashboardState→com.wisnu.kurniawan.composetodolist.model.User
- Direction
- features.dashboard.ui uses model, so a change to model can break features.dashboard.ui, while a change to features.dashboard.ui can't break model.
- Position
- Below the diagonal: features.dashboard.ui uses a module listed above it, which is the healthy direction.
40→4 features.dashboard.ui uses features.todo.all.ui.ItemAllState✕
- Connections
- 1 pair of types, where a type in features.dashboard.ui uses a type in features.todo.all.ui.ItemAllState.
- The types involved
com.wisnu.kurniawan.composetodolist.features.dashboard.ui.DashboardScreenKt→com.wisnu.kurniawan.composetodolist.features.todo.all.ui.ItemAllState.Task
- Direction
- features.dashboard.ui uses features.todo.all.ui.ItemAllState, so a change to features.todo.all.ui.ItemAllState can break features.dashboard.ui, while a change to features.dashboard.ui can't break features.todo.all.ui.ItemAllState.
- Position
- Below the diagonal: features.dashboard.ui uses a module listed above it, which is the healthy direction.
40→6 features.dashboard.ui uses features.todo.main.ui.ItemMainState✕
- Connections
- 2 pairs of types, where a type in features.dashboard.ui uses a type in features.todo.main.ui.ItemMainState.
- The types involved
com.wisnu.kurniawan.composetodolist.features.dashboard.ui.DashboardScreenKt→com.wisnu.kurniawan.composetodolist.features.todo.main.ui.ItemMainState.ItemGroupcom.wisnu.kurniawan.composetodolist.features.dashboard.ui.DashboardScreenKt→com.wisnu.kurniawan.composetodolist.features.todo.main.ui.ItemMainState.ItemListType
- Direction
- features.dashboard.ui uses features.todo.main.ui.ItemMainState, so a change to features.todo.main.ui.ItemMainState can break features.dashboard.ui, while a change to features.dashboard.ui can't break features.todo.main.ui.ItemMainState.
- Position
- Below the diagonal: features.dashboard.ui uses a module listed above it, which is the healthy direction.
40→33 features.dashboard.ui uses features.dashboard.data✕
- Connections
- 1 pair of types, where a type in features.dashboard.ui uses a type in features.dashboard.data.
- The types involved
com.wisnu.kurniawan.composetodolist.features.dashboard.ui.DashboardViewModel→com.wisnu.kurniawan.composetodolist.features.dashboard.data.IDashboardEnvironment
- Direction
- features.dashboard.ui uses features.dashboard.data, so a change to features.dashboard.data can break features.dashboard.ui, while a change to features.dashboard.ui can't break features.dashboard.data.
- Position
- Below the diagonal: features.dashboard.ui uses a module listed above it, which is the healthy direction.
40→34 features.dashboard.ui uses features.todo.all.ui✕
- Connections
- 1 pair of types, where a type in features.dashboard.ui uses a type in features.todo.all.ui.
- The types involved
com.wisnu.kurniawan.composetodolist.features.dashboard.ui.DashboardScreenKt→com.wisnu.kurniawan.composetodolist.features.todo.all.ui.ItemAllState
- Direction
- features.dashboard.ui uses features.todo.all.ui, so a change to features.todo.all.ui can break features.dashboard.ui, while a change to features.dashboard.ui can't break features.todo.all.ui.
- Position
- Below the diagonal: features.dashboard.ui uses a module listed above it, which is the healthy direction.
40→35 features.dashboard.ui uses features.todo.main.ui✕
- Connections
- 2 pairs of types, where a type in features.dashboard.ui uses a type in features.todo.main.ui.
- The types involved
com.wisnu.kurniawan.composetodolist.features.dashboard.ui.DashboardScreenKt→com.wisnu.kurniawan.composetodolist.features.todo.main.ui.ItemMainStatecom.wisnu.kurniawan.composetodolist.features.dashboard.ui.DashboardScreenKt→com.wisnu.kurniawan.composetodolist.features.todo.main.ui.ToDoMainViewModel
- Direction
- features.dashboard.ui uses features.todo.main.ui, so a change to features.todo.main.ui can break features.dashboard.ui, while a change to features.dashboard.ui can't break features.todo.main.ui.
- Position
- Below the diagonal: features.dashboard.ui uses a module listed above it, which is the healthy direction.
40→39 features.dashboard.ui uses features.todo.search.ui✕
- Connections
- 1 pair of types, where a type in features.dashboard.ui uses a type in features.todo.search.ui.
- The types involved
com.wisnu.kurniawan.composetodolist.features.dashboard.ui.DashboardScreenKt→com.wisnu.kurniawan.composetodolist.features.todo.search.ui.SearchViewModel
- Direction
- features.dashboard.ui uses features.todo.search.ui, so a change to features.todo.search.ui can break features.dashboard.ui, while a change to features.dashboard.ui can't break features.todo.search.ui.
- Position
- Below the diagonal: features.dashboard.ui 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 | 5 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 4 | Medium |
| A07:2025 — Authentication Failures | 2 | High / Critical |
Roadmap
Top priorities: Resolve the 2 Leaked secret finding(s) in Secret Scanning — start with REDACTED (2); Resolve the 64 Orphaned file finding(s) in Knowledge Freshness — start with ToDoMainScreen.kt, DashboardScreen.kt, StepScreenExp.kt; Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 2 Leaked secret finding(s) in Secret Scanning — start with REDACTED (2). | +7.5 pts | Low | Secret Scanning |
| Resolve the 64 Orphaned file finding(s) in Knowledge Freshness — start with ToDoMainScreen.kt, DashboardScreen.kt, StepScreenExp.kt. | +5.9 pts | Medium | Knowledge Freshness |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +4.2 pts | Medium | Release Hygiene |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +2.9 pts | Medium | Architecture documentation |
| 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. | +1.7 pts | Medium | Documentation (README) |
| Swallowed exception (caught, then discarded) | +0.7 pts | Medium | Exception handling |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +0.3 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +0.3 pts | Low | Supply-chain Provenance & Signing |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.5 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Secret Scanning: Leaked secret: REDACTED |
| app/src/main/java/com/wisnu/kurniawan/composetodolist/features/todo/all/ui/AllScreen.kt | 7.1 | Near-clean | Code Duplication: Edited copies of one member (3 members, 85+ corresponding lines) |
| app/src/main/java/com/wisnu/kurniawan/composetodolist/features/todo/step/ui/StepScreen.kt | 7.4 | Near-clean | God Classes: MethodTooLong: StepScreenKt.StepContent |
| app/src/main/java/com/wisnu/kurniawan/composetodolist/features/todo/group/ui/CreateGroupScreen.kt | 7.4 | Near-clean | Code Duplication: Edited copy of a member (33 corresponding lines) |
| app/src/main/java/com/wisnu/kurniawan/composetodolist/features/todo/detail/ui/ListDetailScreen.kt | 7.4 | Near-clean | Code Duplication: Edited copy of a member (30 corresponding lines) |
| app/src/main/java/com/wisnu/kurniawan/composetodolist/foundation/theme/Theme.kt | 7.8 | Near-clean | Cyclomatic Complexity: ThemeKt.Theme (cyclomatic 18) |
| app/src/main/java/com/wisnu/kurniawan/composetodolist/features/todo/all/data/AllEnvironment.kt | 7.8 | Near-clean | Code Duplication: Members sharing a duplicated core (5 members, 50+ identical tokens) |
| app/src/main/java/com/wisnu/kurniawan/composetodolist/features/localized/setting/ui/LocalizedSettingScreen.kt | 7.8 | Near-clean | Code Duplication: Edited copy of a member (22 corresponding lines) |
| app/src/main/java/com/wisnu/kurniawan/composetodolist/features/todo/grouplist/ui/UpdateGroupListScreen.kt | 7.8 | Near-clean | Code Duplication: Edited copy of a member (18 corresponding lines) |
| app/src/main/java/com/wisnu/kurniawan/composetodolist/foundation/preview/NavPlayground.kt | 7.8 | Near-clean | Code Duplication: Edited copy of a member (23 corresponding lines) |
| app/src/main/java/com/wisnu/kurniawan/composetodolist/runtime/navigation/MainNavHost.kt | 7.8 | Near-clean | Code Duplication: Duplicated block (13–14 lines × 2) |
| app/src/test/java/com/wisnu/kurniawan/composetodolist/features/todo/groupmenu/ui/GroupMenuViewModelTest.kt | 8.2 | Near-clean | Explicit Debt: TodoComment |
| app/src/test/java/com/wisnu/kurniawan/composetodolist/features/todo/group/ui/CreateGroupViewModelTest.kt | 8.2 | Near-clean | Explicit Debt: TodoComment |
| app/src/test/java/com/wisnu/kurniawan/composetodolist/features/todo/group/data/CreateGroupEnvironmentTest.kt | 8.2 | Near-clean | Explicit Debt: TodoComment |
| app/src/test/java/com/wisnu/kurniawan/composetodolist/features/todo/detail/ui/CreateListDetailViewModelTest.kt | 8.2 | Near-clean | Explicit Debt: TodoComment |
| app/src/test/java/com/wisnu/kurniawan/composetodolist/features/todo/detail/data/ListDetailEnvironmentTest.kt | 8.2 | Near-clean | Explicit Debt: TodoComment |
| app/src/test/java/com/wisnu/kurniawan/composetodolist/features/logout/ui/LogoutViewModelTest.kt | 8.2 | Near-clean | Explicit Debt: TodoComment |
| app/src/main/java/com/wisnu/kurniawan/composetodolist/features/todo/taskreminder/ui/TaskReminderViewModel.kt | 8.2 | Near-clean | Explicit Debt: TodoComment |
| app/src/main/java/com/wisnu/kurniawan/composetodolist/features/dashboard/data/DashboardEnvironment.kt | 8.2 | Near-clean | Explicit Debt: TodoComment |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 38 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 38 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, 121 of 128 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 445 artifact(s) across its subprojects (137 behind a shipped release, reported), but the currency signal was not established over the whole graph, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (3 contributor(s) across 738 commit(s) sampled, automation and bot accounts excluded). One of them holds 96% of the history; the other 2 hold 2% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D26 Project Cohesion — 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` (14019 LoC, 501 module-visible types across 76 directories) is over its size bounds, and whether one unit is a coherent whole or a grab-bag is read from its type references: the parts of it that reach the rest only through its shared core. Those are read over the C#/VB code model, which this unit's source did not supply. Its size alone is no verdict on its cohesion, so none is published.
- 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/java/com/wisnu/kurniawan/composetodolist/features/todo/step/ui/StepScreenExp.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.
- 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: > Could not get resource 'https://jitpack.io/com/github/wisnukurniawan/foundation/lib-analytics-manager/0.1.3/lib-analytics-manager-0.1.3.pom'. > Could not GET 'https://jitpack.io/co…; runtime evidence skipped (launch chosen because app/build.gradle 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 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 is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- 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.
- 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").
- 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.
- 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.
- 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
2 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was StepViewModel.handleTaskAction at 20.
What to do
- Bring the 2 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with StepViewModel.handleTaskAction (cyclomatic 20), ThemeKt.Theme (cyclomatic 18). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cyclomatic Complexity from 9.5 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
1 method(s) exceeded the cognitive complexity threshold of 15; the worst was ThemeKt.Theme at 17.
What to do
- Bring the 1 body over 15 down to 15 or less in Cognitive Complexity — start with ThemeKt.Theme (cognitive 17). — Refactoring it lifts Cognitive Complexity from 9.8 to about 10.0/10.
D3 · God Classes
2 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 1 MethodTooLong finding(s) in God Classes — start with StepScreen.kt. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 FileTooLong finding(s) in God Classes — start with StepScreen.kt. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
14 duplicated block group(s) detected. 9.3 % of the production lines (1,312 of 14,092) are in a reported copy. A further 18 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 2 Edited copy of a member (27 corresponding lines) finding(s) in Code Duplication — start with HomeNavHost.kt, TextField.kt. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Edited copy of a member (22 corresponding lines) finding(s) in Code Duplication — start with StepScreen.kt, LocalizedSettingScreen.kt. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Edited copy of a member (23 corresponding lines) finding(s) in Code Duplication — start with ThemeScreen.kt, NavPlayground.kt. — One of this dimension's main actionable groups (2 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, with abstractness counted on 2 of the 3 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
D6 · Cohesion (LCOM4)
0 of 29 classes have LCOM4 above 3.
D13 · Secret Scanning
1 secret(s) detected.
What to do
- Resolve the 2 Leaked secret finding(s) in Secret Scanning — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
D14 · License Compliance
0 of 21 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. A further 49 coordinate(s) are not published to Maven Central — another repository (Google's Maven hosts androidx), a SNAPSHOT, or a private artifact — so their licences are not readable from here and they are outside this verdict.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
8 deducted task-comment markers across 14092 LoC (0.0/KLoC) → score 9.9. 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 8 TodoComment finding(s) in Explicit Debt — start with GroupMenuViewModelTest.kt, CreateGroupViewModelTest.kt, CreateGroupEnvironmentTest.kt. — One of this dimension's main actionable groups (8 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 16 document(s) read across 3 unit(s).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
5 finding(s): 0 critical, 5 high, 0 medium, 0 low. 5 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` (lines 144–145, line 146, line 147, …) — 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.
What to do
- No action in Static Analysis (SAST) — all 5 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 (5 issue-level, 0 of them charged here).
D34 · Knowledge Freshness
65 of 65 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/java/com/wisnu/kurniawan/composetodolist/features/todo/step/ui/StepScreen.kt. Counted over 65 of the 269 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 64 Orphaned file finding(s) in Knowledge Freshness — start with ToDoMainScreen.kt, DashboardScreen.kt, StepScreenExp.kt. — One of this dimension's main actionable groups (64 recommendation-level).
- Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 Most significant orphaned file finding(s) in Knowledge Freshness — start with StepScreen.kt. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 3 platform declaration(s) and 70 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
AX2 · Stateful singletons
AX3 · Project dependency cycles
AX5 · Architecture & structure
AX6 · Interface segregation
AX7 · Slice cohesion
- `DashboardEnvironment` (slice 'dashboard') depends on `TaskAlarmManager` from slice 'todo'. — app/src/main/java/com/wisnu/kurniawan/composetodolist/features/dashboard/data/DashboardEnvironment.kt:24
What to do
- Keep slices independent: share cross-slice needs via an explicit contract/shared-kernel, not direct references between slices.
M1 · Documentation (README)
What to do
- 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.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
P1 · CI/CD gates
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add spotbugs with find-sec-bugs (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 1 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:7
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.
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.
PF1 · Benchmark discipline
PF3 · Async & latency hygiene
X1 · Async correctness
X12 · Unreachable branch
X19 · Unrestored process-global state
X21 · Side-effecting pattern guard
X23 · Unguarded diagnostic materialisation
X3 · Exception handling
- `catch (exception: 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/java/com/wisnu/kurniawan/composetodolist/foundation/localization/LocalizationUtil.kt:23
What to do
- Swallowed exception (caught, then discarded)
X5 · Nullable reference types
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 81.0 | Strong | Solid. |
| Architecture | 84.4 | Exemplary | Solid. |
| Maturity | 61.2 | Adequate — gated by D34 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 55.5 | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 81.2 | Adequate — gated by D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 94.3 | Exemplary | Strongest area. |
Unscored — 1 check(s) recorded observations but carry no score
- P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
Not evidenced — 2 control(s) we could not find positive evidence for
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 75 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: Dagger rejects, at compile time, a component that holds a binding with a narrower scope than its own.
- AX4 Dependency direction — not applicable to a vertical-slice architecture (the inward-dependency rule is for layered/clean styles)
- 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: > Could not get resource 'https://jitpack.io/com/github/wisnukurniawan/foundation/lib-analytics-manager/0.1.3/lib-analytics-manager-0.1.3.pom'. > Could not GET 'https://jitpack.io/co…; runtime evidence skipped (launch chosen because app/build.gradle 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 — ~3963 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 445 artifact(s) across its subprojects (137 behind a shipped release, reported), but the currency signal was not established over the whole graph, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D20 ADR Quality — N/A — this repo declares itself a template / kata / sample / demo; a formal ADR log is deferred to a real application built from it.
- D21 Naming Consistency — D21 withholds its case and prefix conventions rows: 6 candidate(s) found and not reported.
- 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, 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
- D26 Project Cohesion — D26 could not read how the parts of this repository's one build unit reference each other, so its cohesion was not measured. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D27 Navigability — symbol resolution incomplete — navigability not assessed
- D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) and a Gradle version catalogue — not scanned yet).
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — 1 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.
- D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) and a Gradle version catalogue — not scanned yet).
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 25 value object(s); 2 domain event(s); its domain events are published by services or handlers — no domain entity raises one
- 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
- M4 Documentation accuracy — Not applicable: the 15 current-state document(s) make no claim of a kind M4 checks.
- P2 Observability — This repository's JVM source (1 module(s), 261 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM 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
- 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
- X16 Unfloored truncation loop — 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
- X18 Disposal-pattern correctness — 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 Kotlin was 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 Kotlin request outside a suspend function has no caller's cancellation to honour
- X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — 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
- X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X27 Collection changed while being enumerated — 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
- X30 Support guard that admits what it rejects — 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.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 7 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 50 finding(s)
- TodoComment app/src/test/java/com/wisnu/kurniawan/composetodolist/features/todo/groupmenu/ui/GroupMenuViewModelTest.kt:3
- TodoComment app/src/test/java/com/wisnu/kurniawan/composetodolist/features/todo/group/ui/CreateGroupViewModelTest.kt:3
- TodoComment app/src/test/java/com/wisnu/kurniawan/composetodolist/features/todo/group/data/CreateGroupEnvironmentTest.kt:3
- TodoComment app/src/test/java/com/wisnu/kurniawan/composetodolist/features/todo/detail/ui/CreateListDetailViewModelTest.kt:187
- TodoComment app/src/test/java/com/wisnu/kurniawan/composetodolist/features/todo/detail/data/ListDetailEnvironmentTest.kt:3
- TodoComment app/src/test/java/com/wisnu/kurniawan/composetodolist/features/logout/ui/LogoutViewModelTest.kt:8
- TodoComment app/src/main/java/com/wisnu/kurniawan/composetodolist/features/todo/taskreminder/ui/TaskReminderViewModel.kt:17
- TodoComment app/src/main/java/com/wisnu/kurniawan/composetodolist/features/dashboard/data/DashboardEnvironment.kt:32
- Edited copy of a member (27 corresponding lines) app/src/main/java/com/wisnu/kurniawan/composetodolist/runtime/navigation/HomeNavHost.kt:29
- Edited copy of a member (27 corresponding lines) app/src/main/java/com/wisnu/kurniawan/composetodolist/foundation/uicomponent/TextField.kt:65
- Edited copy of a member (22 corresponding lines) app/src/main/java/com/wisnu/kurniawan/composetodolist/features/todo/step/ui/StepScreen.kt:668
- Edited copy of a member (22 corresponding lines) app/src/main/java/com/wisnu/kurniawan/composetodolist/features/localized/setting/ui/LocalizedSettingScreen.kt:80
- Edited copy of a member (23 corresponding lines) app/src/main/java/com/wisnu/kurniawan/composetodolist/features/theme/ui/ThemeScreen.kt:34
- Edited copy of a member (23 corresponding lines) app/src/main/java/com/wisnu/kurniawan/composetodolist/foundation/preview/NavPlayground.kt:88
- Cross-slice coupling: dashboard → todo app/src/main/java/com/wisnu/kurniawan/composetodolist/features/dashboard/data/DashboardEnvironment.kt:24
- StepViewModel.handleTaskAction (cyclomatic 20) app/src/main/java/com/wisnu/kurniawan/composetodolist/features/todo/step/ui/StepViewModel.kt:58
- ThemeKt.Theme (cyclomatic 18) app/src/main/java/com/wisnu/kurniawan/composetodolist/foundation/theme/Theme.kt:116
- ThemeKt.Theme (cognitive 17) app/src/main/java/com/wisnu/kurniawan/composetodolist/foundation/theme/Theme.kt:116
- MethodTooLong: StepScreenKt.StepContent app/src/main/java/com/wisnu/kurniawan/composetodolist/features/todo/step/ui/StepScreen.kt:391
- FileTooLong: ui/StepScreen.kt app/src/main/java/com/wisnu/kurniawan/composetodolist/features/todo/step/ui/StepScreen.kt
- REDACTED
- REDACTED
- Members sharing a duplicated core (5 members, 50+ identical tokens) app/src/main/java/com/wisnu/kurniawan/composetodolist/features/todo/all/data/AllEnvironment.kt:22
- Edited copies of one member (3 members, 85+ corresponding lines) app/src/main/java/com/wisnu/kurniawan/composetodolist/features/todo/all/ui/AllScreen.kt:191
- Edited copy of a member (33 corresponding lines) app/src/main/java/com/wisnu/kurniawan/composetodolist/features/todo/group/ui/CreateGroupScreen.kt:45
- Edited copy of a member (53 corresponding lines) app/src/main/java/com/wisnu/kurniawan/composetodolist/features/todo/all/ui/AllScreen.kt:96
- Edited copy of a member (40 corresponding lines) app/src/main/java/com/wisnu/kurniawan/composetodolist/features/todo/group/ui/CreateGroupScreen.kt:134
- Edited copy of a member (30 corresponding lines) app/src/main/java/com/wisnu/kurniawan/composetodolist/features/todo/detail/ui/ListDetailScreen.kt:188
- Edited copy of a member (24 corresponding lines) app/src/main/java/com/wisnu/kurniawan/composetodolist/features/todo/step/ui/RenameStepScreen.kt:21
- Edited copies of one member (3 members, 20+ corresponding lines) app/src/main/java/com/wisnu/kurniawan/composetodolist/features/todo/all/ui/AllScreen.kt:65
- Edited copy of a member (20 corresponding lines) app/src/main/java/com/wisnu/kurniawan/composetodolist/features/todo/all/ui/AllViewModel.kt:27
- Edited copies of one member (4 members, 14+ corresponding lines) app/src/main/java/com/wisnu/kurniawan/composetodolist/runtime/navigation/AllNavHost.kt:15
- Edited copy of a member (18 corresponding lines) app/src/main/java/com/wisnu/kurniawan/composetodolist/features/todo/grouplist/ui/UpdateGroupListScreen.kt:50
- Edited copy of a member (11 corresponding lines) app/src/main/java/com/wisnu/kurniawan/composetodolist/features/todo/detail/data/ListDetailEnvironment.kt:36
- Duplicated block (35–36 lines × 2) app/src/main/java/com/wisnu/kurniawan/composetodolist/features/todo/all/ui/AllScreen.kt:284
- Duplicated block (26 lines × 2) app/src/main/java/com/wisnu/kurniawan/composetodolist/features/todo/all/ui/AllScreen.kt:238
- Duplicated block (19 lines × 2) app/src/main/java/com/wisnu/kurniawan/composetodolist/features/todo/detail/ui/ListDetailScreen.kt:323
- Duplicated block (18 lines × 2) app/src/main/java/com/wisnu/kurniawan/composetodolist/features/localized/setting/ui/LocalizedSettingScreen.kt:84
- Duplicated block (14–15 lines × 2) app/src/main/java/com/wisnu/kurniawan/composetodolist/features/todo/grouplist/ui/UpdateGroupListScreen.kt:167
- Duplicated block (13–14 lines × 2) app/src/main/java/com/wisnu/kurniawan/composetodolist/runtime/navigation/MainNavHost.kt:67
- Duplicated block (12 lines × 2) app/src/main/java/com/wisnu/kurniawan/composetodolist/runtime/navigation/MainNavHost.kt:141
- Duplicated block (11 lines × 5) app/src/main/java/com/wisnu/kurniawan/composetodolist/features/todo/all/data/AllEnvironment.kt:23
- Duplicated block (9–11 lines × 2) app/src/main/java/com/wisnu/kurniawan/composetodolist/features/dashboard/ui/DashboardScreen.kt:92
- Duplicated block (10–11 lines × 2) app/src/main/java/com/wisnu/kurniawan/composetodolist/features/todo/scheduled/ui/ScheduledViewModel.kt:74
- Duplicated block (10 lines × 2) app/src/main/java/com/wisnu/kurniawan/composetodolist/features/todo/all/ui/AllScreen.kt:224
- Duplicated block (9 lines × 2) app/src/main/java/com/wisnu/kurniawan/composetodolist/features/todo/detail/ui/ListDetailScreen.kt:208
- Duplicated block (8 lines × 2) app/src/main/java/com/wisnu/kurniawan/composetodolist/features/todo/group/ui/CreateGroupScreen.kt:73
- Duplicated block (20 lines × 2) app/src/main/java/com/wisnu/kurniawan/composetodolist/foundation/preview/NavPlayground.kt:91
- Coverage collected but not gated
- Swallowed exception (caught, then discarded) app/src/main/java/com/wisnu/kurniawan/composetodolist/foundation/localization/LocalizationUtil.kt:23
Minor — 71 finding(s)
- Orphaned file app/src/main/java/com/wisnu/kurniawan/composetodolist/features/todo/main/ui/ToDoMainScreen.kt:1
- Orphaned file app/src/main/java/com/wisnu/kurniawan/composetodolist/features/dashboard/ui/DashboardScreen.kt:1
- Orphaned file app/src/main/java/com/wisnu/kurniawan/composetodolist/features/todo/step/ui/StepScreenExp.kt:1
- Orphaned file app/src/main/java/com/wisnu/kurniawan/composetodolist/foundation/window/WindowState.kt:1
- Orphaned file app/src/main/java/com/wisnu/kurniawan/composetodolist/features/todo/scheduled/ui/ScheduledScreen.kt:1
- Orphaned file app/src/main/java/com/wisnu/kurniawan/composetodolist/foundation/uicomponent/TextField.kt:1
- Orphaned file app/src/main/java/com/wisnu/kurniawan/composetodolist/features/todo/all/ui/AllScreen.kt:1
- Orphaned file app/src/main/java/com/wisnu/kurniawan/composetodolist/features/todo/detail/ui/ListDetailScreen.kt:1
- Orphaned file app/src/main/java/com/wisnu/kurniawan/composetodolist/foundation/uicomponent/SwipeSearch.kt:1
- Orphaned file app/src/main/java/com/wisnu/kurniawan/composetodolist/features/todo/step/ui/StepViewModel.kt:1
- Orphaned file app/src/main/java/com/wisnu/kurniawan/composetodolist/foundation/uicomponent/SwipeDismiss.kt:1
- Orphaned file app/src/main/java/com/wisnu/kurniawan/composetodolist/features/todo/detail/ui/TaskScreen.kt:1
- Orphaned file app/src/main/java/com/wisnu/kurniawan/composetodolist/runtime/navigation/HomeNavHost.kt:1
- Orphaned file app/build.gradle:1
- Orphaned file app/src/main/java/com/wisnu/kurniawan/composetodolist/runtime/navigation/MainNavHost.kt:1
- Orphaned file app/src/main/java/com/wisnu/kurniawan/composetodolist/foundation/uicomponent/ToDoTaskDisplayable.kt:1
- Orphaned file app/src/main/java/com/wisnu/kurniawan/composetodolist/features/todo/detail/ui/ListDetailViewModel.kt:1
- Orphaned file app/src/main/java/com/wisnu/kurniawan/composetodolist/features/dashboard/ui/DashboardTabletScreen.kt:1
- Orphaned file app/src/main/java/com/wisnu/kurniawan/composetodolist/runtime/navigation/MainFlow.kt:1
- Orphaned file app/src/main/java/com/wisnu/kurniawan/composetodolist/features/todo/grouplist/ui/UpdateGroupListScreen.kt:1
- Orphaned file app/src/main/java/com/wisnu/kurniawan/composetodolist/features/login/ui/LoginScreen.kt:1
- Orphaned file app/src/main/java/com/wisnu/kurniawan/composetodolist/features/todo/group/ui/CreateGroupScreen.kt:1
- Orphaned file app/src/main/java/com/wisnu/kurniawan/composetodolist/features/todo/main/ui/ToDoMainViewModel.kt:1
- Orphaned file app/src/main/java/com/wisnu/kurniawan/composetodolist/features/todo/taskreminder/data/TaskNotificationManager.kt:1
- Orphaned file app/src/main/java/com/wisnu/kurniawan/composetodolist/foundation/uicomponent/Cell.kt:1
- Dormant codebase
- Most significant orphaned file app/src/main/java/com/wisnu/kurniawan/composetodolist/features/todo/step/ui/StepScreen.kt:1
- REDACTED
- REDACTED
- No ADRs
- No SAST REDACTED:7
- No changelog
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-6ee0a003b65b40fc8c17d01e290e3a54/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=538" --report-format json --report-path /tmp/watchdog-gitleaks-6ee0a003b65b40fc8c17d01e290e3a54/history-1.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history-1.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-6ee0a003b65b40fc8c17d01e290e3a54/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 5 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) and a Gradle version catalogue — not scanned yet). | 0 | — |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 1 file(s) — `app/src/main/java/com/wisnu/kurniawan/composetodolist/features/todo/step/ui/StepScreenExp.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 | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) and a Gradle version catalogue — not scanned yet). | 0 | — |