Executive summary
igorescodro/alkaa falls short of our standard for production, held back most by its Accessibility lens, the interface's usability with a keyboard or assistive technology. It scores 52 out of 100 and is rated Adequate, and 40 of its 60 critical findings are security problems.
Accessibility, at 35, is the weakest lens and counts most in the score. The best first step for the work it takes is replacing the four exposed passwords or keys and switching the old ones off, worth about 6 points. Making the controls keyboard-usable would lift Accessibility itself, worth about 8 points. Raising Accessibility to 70 would lift the score to about 64.
Thirty pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Four passwords or keys in the code and two in the code's history are open to anyone who can read the repository, and ten buttons or links have no name a screen reader can say. Pinning each tool to an exact version, replacing each exposed password or key and naming the buttons and links would close these risks. Limiting each secret to its own step would fix the three secrets exposed to more of the pipeline than needed, and passing outside input through environment variables would deal with the pipeline step that puts outside input straight into a shell command. The nine form fields without a label need a label.
The product code is 15,722 lines, about €22,000 to rebuild.
If Accessibility rose from 35 to 70, the lowest score rated Strong, the score would rise from 52 to about 64.
New since the last survey: 3 findings
- Visual & motion safety · Low contrast colour pair in CSS (2.1:1) assets/designsystem/alkaa-ds.html
- Visual & motion safety · Low contrast colour pair in CSS (1.7:1) assets/designsystem/alkaa-ds.html
- Visual & motion safety · Low contrast colour pair in CSS (2.2:1) assets/designsystem/alkaa-ds.html
Rebuild cost: about €22,000 · Estimate
| Cost to rebuild | €7,400 to €37,000, for 124 to 393 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.7 at a score of 52. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 15,722 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 categoryapi.model | 2 categoryapi.presentation | 3 coroutines | 4 domain.model | 5 glance.model | 6 local.model | 7 navigationapi.marker | 8 repository.model | 9 category.mapper | 10 domain.interactor | 11 domain.repository | 12 domain.usecase.category | 13 local.mapper | 14 navigationapi.destination | 15 preference.presentation | 16 search.presentation | 17 task.model | 18 category.presentation.bottomsheet | 19 category.presentation.list | 20 domain.usecase.task | 21 domain.usecase.taskwithcategory | 22 local.dao.impl | 23 local.datasource | 24 navigationapi.event | 25 repository | 26 task.mapper | 27 alarm.notification | 28 domain.usecase.alarm | 29 glance.data | 30 navigationapi.controller | 31 alarm.interactor | 32 domain.usecase.alarm.implementation | 33 domain.usecase.task.implementation | 34 navigation.compose | 35 navigation.controller | 36 navigationapi.provider | 37 task.presentation.detail.alarm | 38 task.presentation.detail.main | 39 task.presentation.add | 40 task.presentation.list |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 categoryapi.model | ||||||||||||||||||||||||||||||||||||||||
| 2 categoryapi.presentation | ||||||||||||||||||||||||||||||||||||||||
| 3 coroutines | ||||||||||||||||||||||||||||||||||||||||
| 4 domain.model | ||||||||||||||||||||||||||||||||||||||||
| 5 glance.model | ||||||||||||||||||||||||||||||||||||||||
| 6 local.model | ||||||||||||||||||||||||||||||||||||||||
| 7 navigationapi.marker | ||||||||||||||||||||||||||||||||||||||||
| 8 repository.model | ||||||||||||||||||||||||||||||||||||||||
| 9 category.mapper | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 10 domain.interactor | 2 | |||||||||||||||||||||||||||||||||||||||
| 11 domain.repository | 4 | |||||||||||||||||||||||||||||||||||||||
| 12 domain.usecase.category | 5 | |||||||||||||||||||||||||||||||||||||||
| 13 local.mapper | 3 | 4 | ||||||||||||||||||||||||||||||||||||||
| 14 navigationapi.destination | 2 | |||||||||||||||||||||||||||||||||||||||
| 15 preference.presentation | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 search.presentation | 1 | |||||||||||||||||||||||||||||||||||||||
| 17 task.model | 1 | |||||||||||||||||||||||||||||||||||||||
| 18 category.presentation.bottomsheet | 3 | 2 | 2 | 4 | ||||||||||||||||||||||||||||||||||||
| 19 category.presentation.list | 1 | 4 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 20 domain.usecase.task | 6 | 3 | 3 | |||||||||||||||||||||||||||||||||||||
| 21 domain.usecase.taskwithcategory | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 22 local.dao.impl | 3 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 23 local.datasource | 4 | 4 | ||||||||||||||||||||||||||||||||||||||
| 24 navigationapi.event | 1 | |||||||||||||||||||||||||||||||||||||||
| 25 repository | 5 | 4 | ||||||||||||||||||||||||||||||||||||||
| 26 task.mapper | 1 | 4 | 3 | |||||||||||||||||||||||||||||||||||||
| 27 alarm.notification | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 28 domain.usecase.alarm | 5 | 5 | 3 | 1 | ||||||||||||||||||||||||||||||||||||
| 29 glance.data | 3 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 30 navigationapi.controller | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 31 alarm.interactor | 2 | 2 | 2 | |||||||||||||||||||||||||||||||||||||
| 32 domain.usecase.alarm.implementation | 2 | 2 | 3 | 7 | ||||||||||||||||||||||||||||||||||||
| 33 domain.usecase.task.implementation | 3 | 5 | 4 | 15 | 1 | |||||||||||||||||||||||||||||||||||
| 34 navigation.compose | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 35 navigation.controller | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 36 navigationapi.provider | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 37 task.presentation.detail.alarm | 1 | 5 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 38 task.presentation.detail.main | 2 | 2 | 1 | 4 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 39 task.presentation.add | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 40 task.presentation.list | 3 | 1 | 4 | 1 | 1 | 1 | 2 |
9→1 category.mapper uses categoryapi.model✕
- Connections
- 1 pair of types, where a type in category.mapper uses a type in categoryapi.model.
- The types involved
com.escodro.category.mapper.CategoryMapper→com.escodro.categoryapi.model.Category
- Direction
- category.mapper uses categoryapi.model, so a change to categoryapi.model can break category.mapper, while a change to category.mapper can't break categoryapi.model.
- Position
- Below the diagonal: category.mapper uses a module listed above it, which is the healthy direction.
9→4 category.mapper uses domain.model✕
- Connections
- 1 pair of types, where a type in category.mapper uses a type in domain.model.
- The types involved
com.escodro.category.mapper.CategoryMapper→com.escodro.domain.model.Category
- Direction
- category.mapper uses domain.model, so a change to domain.model can break category.mapper, while a change to category.mapper can't break domain.model.
- Position
- Below the diagonal: category.mapper uses a module listed above it, which is the healthy direction.
10→4 domain.interactor uses domain.model✕
- Connections
- 2 pairs of types, where a type in domain.interactor uses a type in domain.model.
- The types involved
com.escodro.domain.interactor.AlarmInteractor→com.escodro.domain.model.Taskcom.escodro.domain.interactor.NotificationInteractor→com.escodro.domain.model.Task
- Direction
- domain.interactor uses domain.model, so a change to domain.model can break domain.interactor, while a change to domain.interactor can't break domain.model.
- Position
- Below the diagonal: domain.interactor uses a module listed above it, which is the healthy direction.
11→4 domain.repository uses domain.model✕
- Connections
- 4 pairs of types, where a type in domain.repository uses a type in domain.model.
- The types involved
com.escodro.domain.repository.CategoryRepository→com.escodro.domain.model.Categorycom.escodro.domain.repository.SearchRepository→com.escodro.domain.model.TaskWithCategorycom.escodro.domain.repository.TaskRepository→com.escodro.domain.model.Taskcom.escodro.domain.repository.TaskWithCategoryRepository→com.escodro.domain.model.TaskWithCategory
- Direction
- domain.repository uses domain.model, so a change to domain.model can break domain.repository, while a change to domain.repository can't break domain.model.
- Position
- Below the diagonal: domain.repository uses a module listed above it, which is the healthy direction.
12→4 domain.usecase.category uses domain.model✕
- Connections
- 5 pairs of types, where a type in domain.usecase.category uses a type in domain.model.
- The types involved
com.escodro.domain.usecase.category.AddCategory→com.escodro.domain.model.Categorycom.escodro.domain.usecase.category.DeleteCategory→com.escodro.domain.model.Categorycom.escodro.domain.usecase.category.LoadAllCategories→com.escodro.domain.model.Categorycom.escodro.domain.usecase.category.LoadCategory→com.escodro.domain.model.Categorycom.escodro.domain.usecase.category.UpdateCategory→com.escodro.domain.model.Category
- Direction
- domain.usecase.category uses domain.model, so a change to domain.model can break domain.usecase.category, while a change to domain.usecase.category can't break domain.model.
- Position
- Below the diagonal: domain.usecase.category uses a module listed above it, which is the healthy direction.
13→6 local.mapper uses local.model✕
- Connections
- 3 pairs of types, where a type in local.mapper uses a type in local.model.
- The types involved
com.escodro.local.mapper.AlarmIntervalMapper→com.escodro.local.model.AlarmIntervalcom.escodro.local.mapper.SelectMapper→com.escodro.local.model.TaskWithCategorycom.escodro.local.mapper.TaskWithCategoryMapper→com.escodro.local.model.TaskWithCategory
- Direction
- local.mapper uses local.model, so a change to local.model can break local.mapper, while a change to local.mapper can't break local.model.
- Position
- Below the diagonal: local.mapper uses a module listed above it, which is the healthy direction.
13→8 local.mapper uses repository.model✕
- Connections
- 4 pairs of types, where a type in local.mapper uses a type in repository.model.
- The types involved
com.escodro.local.mapper.AlarmIntervalMapper→com.escodro.repository.model.AlarmIntervalcom.escodro.local.mapper.CategoryMapper→com.escodro.repository.model.Categorycom.escodro.local.mapper.TaskMapper→com.escodro.repository.model.Taskcom.escodro.local.mapper.TaskWithCategoryMapper→com.escodro.repository.model.TaskWithCategory
- Direction
- local.mapper uses repository.model, so a change to repository.model can break local.mapper, while a change to local.mapper can't break repository.model.
- Position
- Below the diagonal: local.mapper uses a module listed above it, which is the healthy direction.
14→7 navigationapi.destination uses navigationapi.marker✕
- Connections
- 2 pairs of types, where a type in navigationapi.destination uses a type in navigationapi.marker.
- The types involved
com.escodro.navigationapi.destination.DestinationKt→com.escodro.navigationapi.marker.TopAppBarVisiblecom.escodro.navigationapi.destination.DestinationKt→com.escodro.navigationapi.marker.TopLevel
- Direction
- navigationapi.destination uses navigationapi.marker, so a change to navigationapi.marker can break navigationapi.destination, while a change to navigationapi.destination can't break navigationapi.marker.
- Position
- Below the diagonal: navigationapi.destination uses a module listed above it, which is the healthy direction.
15→3 preference.presentation uses coroutines✕
- Connections
- 1 pair of types, where a type in preference.presentation uses a type in coroutines.
- The types involved
com.escodro.preference.presentation.PreferenceViewModel→com.escodro.coroutines.AppCoroutineScope
- Direction
- preference.presentation uses coroutines, so a change to coroutines can break preference.presentation, while a change to preference.presentation can't break coroutines.
- Position
- Below the diagonal: preference.presentation uses a module listed above it, which is the healthy direction.
16→4 search.presentation uses domain.model✕
- Connections
- 1 pair of types, where a type in search.presentation uses a type in domain.model.
- The types involved
com.escodro.search.presentation.SearchViewModel→com.escodro.domain.model.TaskWithCategory
- Direction
- search.presentation uses domain.model, so a change to domain.model can break search.presentation, while a change to search.presentation can't break domain.model.
- Position
- Below the diagonal: search.presentation uses a module listed above it, which is the healthy direction.
17→1 task.model uses categoryapi.model✕
- Connections
- 1 pair of types, where a type in task.model uses a type in categoryapi.model.
- The types involved
com.escodro.task.model.TaskWithCategory→com.escodro.categoryapi.model.Category
- Direction
- task.model uses categoryapi.model, so a change to categoryapi.model can break task.model, while a change to task.model can't break categoryapi.model.
- Position
- Below the diagonal: task.model uses a module listed above it, which is the healthy direction.
18→1 category.presentation.bottomsheet uses categoryapi.model✕
- Connections
- 3 pairs of types, where a type in category.presentation.bottomsheet uses a type in categoryapi.model.
- The types involved
com.escodro.category.presentation.bottomsheet.CategoryAddViewModel→com.escodro.categoryapi.model.Categorycom.escodro.category.presentation.bottomsheet.CategoryBottomSheetKt→com.escodro.categoryapi.model.Categorycom.escodro.category.presentation.bottomsheet.CategoryEditViewModel→com.escodro.categoryapi.model.Category
- Direction
- category.presentation.bottomsheet uses categoryapi.model, so a change to categoryapi.model can break category.presentation.bottomsheet, while a change to category.presentation.bottomsheet can't break categoryapi.model.
- Position
- Below the diagonal: category.presentation.bottomsheet uses a module listed above it, which is the healthy direction.
18→3 category.presentation.bottomsheet uses coroutines✕
- Connections
- 2 pairs of types, where a type in category.presentation.bottomsheet uses a type in coroutines.
- The types involved
com.escodro.category.presentation.bottomsheet.CategoryAddViewModel→com.escodro.coroutines.AppCoroutineScopecom.escodro.category.presentation.bottomsheet.CategoryEditViewModel→com.escodro.coroutines.AppCoroutineScope
- Direction
- category.presentation.bottomsheet uses coroutines, so a change to coroutines can break category.presentation.bottomsheet, while a change to category.presentation.bottomsheet can't break coroutines.
- Position
- Below the diagonal: category.presentation.bottomsheet uses a module listed above it, which is the healthy direction.
18→9 category.presentation.bottomsheet uses category.mapper✕
- Connections
- 2 pairs of types, where a type in category.presentation.bottomsheet uses a type in category.mapper.
- The types involved
com.escodro.category.presentation.bottomsheet.CategoryAddViewModel→com.escodro.category.mapper.CategoryMappercom.escodro.category.presentation.bottomsheet.CategoryEditViewModel→com.escodro.category.mapper.CategoryMapper
- Direction
- category.presentation.bottomsheet uses category.mapper, so a change to category.mapper can break category.presentation.bottomsheet, while a change to category.presentation.bottomsheet can't break category.mapper.
- Position
- Below the diagonal: category.presentation.bottomsheet uses a module listed above it, which is the healthy direction.
18→12 category.presentation.bottomsheet uses domain.usecase.category✕
- Connections
- 4 pairs of types, where a type in category.presentation.bottomsheet uses a type in domain.usecase.category.
- The types involved
com.escodro.category.presentation.bottomsheet.CategoryAddViewModel→com.escodro.domain.usecase.category.AddCategorycom.escodro.category.presentation.bottomsheet.CategoryEditViewModel→com.escodro.domain.usecase.category.DeleteCategorycom.escodro.category.presentation.bottomsheet.CategoryEditViewModel→com.escodro.domain.usecase.category.LoadCategorycom.escodro.category.presentation.bottomsheet.CategoryEditViewModel→com.escodro.domain.usecase.category.UpdateCategory
- Direction
- category.presentation.bottomsheet uses domain.usecase.category, so a change to domain.usecase.category can break category.presentation.bottomsheet, while a change to category.presentation.bottomsheet can't break domain.usecase.category.
- Position
- Below the diagonal: category.presentation.bottomsheet uses a module listed above it, which is the healthy direction.
19→1 category.presentation.list uses categoryapi.model✕
- Connections
- 1 pair of types, where a type in category.presentation.list uses a type in categoryapi.model.
- The types involved
com.escodro.category.presentation.list.CategoryListKt→com.escodro.categoryapi.model.Category
- Direction
- category.presentation.list uses categoryapi.model, so a change to categoryapi.model can break category.presentation.list, while a change to category.presentation.list can't break categoryapi.model.
- Position
- Below the diagonal: category.presentation.list uses a module listed above it, which is the healthy direction.
19→2 category.presentation.list uses categoryapi.presentation✕
- Connections
- 4 pairs of types, where a type in category.presentation.list uses a type in categoryapi.presentation.
- The types involved
com.escodro.category.presentation.list.CategoryListKt→com.escodro.categoryapi.presentation.CategoryListViewModelcom.escodro.category.presentation.list.CategoryListKt→com.escodro.categoryapi.presentation.CategoryStatecom.escodro.category.presentation.list.CategoryListViewModelImpl→com.escodro.categoryapi.presentation.CategoryListViewModelcom.escodro.category.presentation.list.CategoryListViewModelImpl→com.escodro.categoryapi.presentation.CategoryState
- Direction
- category.presentation.list uses categoryapi.presentation, so a change to categoryapi.presentation can break category.presentation.list, while a change to category.presentation.list can't break categoryapi.presentation.
- Position
- Below the diagonal: category.presentation.list uses a module listed above it, which is the healthy direction.
19→9 category.presentation.list uses category.mapper✕
- Connections
- 1 pair of types, where a type in category.presentation.list uses a type in category.mapper.
- The types involved
com.escodro.category.presentation.list.CategoryListViewModelImpl→com.escodro.category.mapper.CategoryMapper
- Direction
- category.presentation.list uses category.mapper, so a change to category.mapper can break category.presentation.list, while a change to category.presentation.list can't break category.mapper.
- Position
- Below the diagonal: category.presentation.list uses a module listed above it, which is the healthy direction.
19→12 category.presentation.list uses domain.usecase.category✕
- Connections
- 1 pair of types, where a type in category.presentation.list uses a type in domain.usecase.category.
- The types involved
com.escodro.category.presentation.list.CategoryListViewModelImpl→com.escodro.domain.usecase.category.LoadAllCategories
- Direction
- category.presentation.list uses domain.usecase.category, so a change to domain.usecase.category can break category.presentation.list, while a change to category.presentation.list can't break domain.usecase.category.
- Position
- Below the diagonal: category.presentation.list uses a module listed above it, which is the healthy direction.
20→4 domain.usecase.task uses domain.model✕
- Connections
- 6 pairs of types, where a type in domain.usecase.task uses a type in domain.model.
- The types involved
com.escodro.domain.usecase.task.AddTask→com.escodro.domain.model.Taskcom.escodro.domain.usecase.task.CompleteTask→com.escodro.domain.model.Taskcom.escodro.domain.usecase.task.DeleteTask→com.escodro.domain.model.Taskcom.escodro.domain.usecase.task.LoadTask→com.escodro.domain.model.Taskcom.escodro.domain.usecase.task.UncompleteTask→com.escodro.domain.model.Taskcom.escodro.domain.usecase.task.UpdateTask→com.escodro.domain.model.Task
- Direction
- domain.usecase.task uses domain.model, so a change to domain.model can break domain.usecase.task, while a change to domain.usecase.task can't break domain.model.
- Position
- Below the diagonal: domain.usecase.task uses a module listed above it, which is the healthy direction.
20→10 domain.usecase.task uses domain.interactor✕
- Connections
- 3 pairs of types, where a type in domain.usecase.task uses a type in domain.interactor.
- The types involved
com.escodro.domain.usecase.task.CompleteTask→com.escodro.domain.interactor.AlarmInteractorcom.escodro.domain.usecase.task.CompleteTask→com.escodro.domain.interactor.NotificationInteractorcom.escodro.domain.usecase.task.DeleteTask→com.escodro.domain.interactor.AlarmInteractor
- Direction
- domain.usecase.task uses domain.interactor, so a change to domain.interactor can break domain.usecase.task, while a change to domain.usecase.task can't break domain.interactor.
- Position
- Below the diagonal: domain.usecase.task uses a module listed above it, which is the healthy direction.
20→11 domain.usecase.task uses domain.repository✕
- Connections
- 3 pairs of types, where a type in domain.usecase.task uses a type in domain.repository.
- The types involved
com.escodro.domain.usecase.task.CompleteTask→com.escodro.domain.repository.TaskRepositorycom.escodro.domain.usecase.task.DeleteTask→com.escodro.domain.repository.TaskRepositorycom.escodro.domain.usecase.task.UncompleteTask→com.escodro.domain.repository.TaskRepository
- Direction
- domain.usecase.task uses domain.repository, so a change to domain.repository can break domain.usecase.task, while a change to domain.usecase.task can't break domain.repository.
- Position
- Below the diagonal: domain.usecase.task uses a module listed above it, which is the healthy direction.
21→4 domain.usecase.taskwithcategory uses domain.model✕
- Connections
- 2 pairs of types, where a type in domain.usecase.taskwithcategory uses a type in domain.model.
- The types involved
com.escodro.domain.usecase.taskwithcategory.LoadCompletedTasks→com.escodro.domain.model.TaskWithCategorycom.escodro.domain.usecase.taskwithcategory.LoadUncompletedTasks→com.escodro.domain.model.TaskWithCategory
- Direction
- domain.usecase.taskwithcategory uses domain.model, so a change to domain.model can break domain.usecase.taskwithcategory, while a change to domain.usecase.taskwithcategory can't break domain.model.
- Position
- Below the diagonal: domain.usecase.taskwithcategory uses a module listed above it, which is the healthy direction.
21→11 domain.usecase.taskwithcategory uses domain.repository✕
- Connections
- 1 pair of types, where a type in domain.usecase.taskwithcategory uses a type in domain.repository.
- The types involved
com.escodro.domain.usecase.taskwithcategory.LoadCompletedTasks→com.escodro.domain.repository.TaskWithCategoryRepository
- Direction
- domain.usecase.taskwithcategory uses domain.repository, so a change to domain.repository can break domain.usecase.taskwithcategory, while a change to domain.usecase.taskwithcategory can't break domain.repository.
- Position
- Below the diagonal: domain.usecase.taskwithcategory uses a module listed above it, which is the healthy direction.
22→3 local.dao.impl uses coroutines✕
- Connections
- 3 pairs of types, where a type in local.dao.impl uses a type in coroutines.
- The types involved
com.escodro.local.dao.impl.CategoryDaoImpl→com.escodro.coroutines.CoroutineDispatcherProvidercom.escodro.local.dao.impl.TaskDaoImpl→com.escodro.coroutines.CoroutineDispatcherProvidercom.escodro.local.dao.impl.TaskWithCategoryDaoImpl→com.escodro.coroutines.CoroutineDispatcherProvider
- Direction
- local.dao.impl uses coroutines, so a change to coroutines can break local.dao.impl, while a change to local.dao.impl can't break coroutines.
- Position
- Below the diagonal: local.dao.impl uses a module listed above it, which is the healthy direction.
22→6 local.dao.impl uses local.model✕
- Connections
- 1 pair of types, where a type in local.dao.impl uses a type in local.model.
- The types involved
com.escodro.local.dao.impl.TaskWithCategoryDaoImpl→com.escodro.local.model.TaskWithCategory
- Direction
- local.dao.impl uses local.model, so a change to local.model can break local.dao.impl, while a change to local.dao.impl can't break local.model.
- Position
- Below the diagonal: local.dao.impl uses a module listed above it, which is the healthy direction.
22→13 local.dao.impl uses local.mapper✕
- Connections
- 1 pair of types, where a type in local.dao.impl uses a type in local.mapper.
- The types involved
com.escodro.local.dao.impl.TaskWithCategoryDaoImpl→com.escodro.local.mapper.SelectMapper
- Direction
- local.dao.impl uses local.mapper, so a change to local.mapper can break local.dao.impl, while a change to local.dao.impl can't break local.mapper.
- Position
- Below the diagonal: local.dao.impl uses a module listed above it, which is the healthy direction.
23→8 local.datasource uses repository.model✕
- Connections
- 4 pairs of types, where a type in local.datasource uses a type in repository.model.
- The types involved
com.escodro.local.datasource.CategoryLocalDataSource→com.escodro.repository.model.Categorycom.escodro.local.datasource.SearchLocalDataSource→com.escodro.repository.model.TaskWithCategorycom.escodro.local.datasource.TaskLocalDataSource→com.escodro.repository.model.Taskcom.escodro.local.datasource.TaskWithCategoryLocalDataSource→com.escodro.repository.model.TaskWithCategory
- Direction
- local.datasource uses repository.model, so a change to repository.model can break local.datasource, while a change to local.datasource can't break repository.model.
- Position
- Below the diagonal: local.datasource uses a module listed above it, which is the healthy direction.
23→13 local.datasource uses local.mapper✕
- Connections
- 4 pairs of types, where a type in local.datasource uses a type in local.mapper.
- The types involved
com.escodro.local.datasource.CategoryLocalDataSource→com.escodro.local.mapper.CategoryMappercom.escodro.local.datasource.SearchLocalDataSource→com.escodro.local.mapper.TaskWithCategoryMappercom.escodro.local.datasource.TaskLocalDataSource→com.escodro.local.mapper.TaskMappercom.escodro.local.datasource.TaskWithCategoryLocalDataSource→com.escodro.local.mapper.TaskWithCategoryMapper
- Direction
- local.datasource uses local.mapper, so a change to local.mapper can break local.datasource, while a change to local.datasource can't break local.mapper.
- Position
- Below the diagonal: local.datasource uses a module listed above it, which is the healthy direction.
24→14 navigationapi.event uses navigationapi.destination✕
- Connections
- 1 pair of types, where a type in navigationapi.event uses a type in navigationapi.destination.
- The types involved
com.escodro.navigationapi.event.Event→com.escodro.navigationapi.destination.Destination
- Direction
- navigationapi.event uses navigationapi.destination, so a change to navigationapi.destination can break navigationapi.event, while a change to navigationapi.event can't break navigationapi.destination.
- Position
- Below the diagonal: navigationapi.event uses a module listed above it, which is the healthy direction.
25→4 repository uses domain.model✕
- Connections
- 5 pairs of types, where a type in repository uses a type in domain.model.
- The types involved
com.escodro.repository.CategoryRepositoryImpl→com.escodro.domain.model.Categorycom.escodro.repository.PreferencesRepositoryImpl→com.escodro.domain.model.AppThemeOptionscom.escodro.repository.SearchRepositoryImpl→com.escodro.domain.model.TaskWithCategorycom.escodro.repository.TaskRepositoryImpl→com.escodro.domain.model.Taskcom.escodro.repository.TaskWithCategoryRepositoryImpl→com.escodro.domain.model.TaskWithCategory
- Direction
- repository uses domain.model, so a change to domain.model can break repository, while a change to repository can't break domain.model.
- Position
- Below the diagonal: repository uses a module listed above it, which is the healthy direction.
25→11 repository uses domain.repository✕
- Connections
- 4 pairs of types, where a type in repository uses a type in domain.repository.
- The types involved
com.escodro.repository.CategoryRepositoryImpl→com.escodro.domain.repository.CategoryRepositorycom.escodro.repository.SearchRepositoryImpl→com.escodro.domain.repository.SearchRepositorycom.escodro.repository.TaskRepositoryImpl→com.escodro.domain.repository.TaskRepositorycom.escodro.repository.TaskWithCategoryRepositoryImpl→com.escodro.domain.repository.TaskWithCategoryRepository
- Direction
- repository uses domain.repository, so a change to domain.repository can break repository, while a change to repository can't break domain.repository.
- Position
- Below the diagonal: repository uses a module listed above it, which is the healthy direction.
26→1 task.mapper uses categoryapi.model✕
- Connections
- 1 pair of types, where a type in task.mapper uses a type in categoryapi.model.
- The types involved
com.escodro.task.mapper.CategoryMapper→com.escodro.categoryapi.model.Category
- Direction
- task.mapper uses categoryapi.model, so a change to categoryapi.model can break task.mapper, while a change to task.mapper can't break categoryapi.model.
- Position
- Below the diagonal: task.mapper uses a module listed above it, which is the healthy direction.
26→4 task.mapper uses domain.model✕
- Connections
- 4 pairs of types, where a type in task.mapper uses a type in domain.model.
- The types involved
com.escodro.task.mapper.AlarmIntervalMapper→com.escodro.domain.model.AlarmIntervalcom.escodro.task.mapper.CategoryMapper→com.escodro.domain.model.Categorycom.escodro.task.mapper.TaskMapper→com.escodro.domain.model.Taskcom.escodro.task.mapper.TaskWithCategoryMapper→com.escodro.domain.model.TaskWithCategory
- Direction
- task.mapper uses domain.model, so a change to domain.model can break task.mapper, while a change to task.mapper can't break domain.model.
- Position
- Below the diagonal: task.mapper uses a module listed above it, which is the healthy direction.
26→17 task.mapper uses task.model✕
- Connections
- 3 pairs of types, where a type in task.mapper uses a type in task.model.
- The types involved
com.escodro.task.mapper.AlarmIntervalMapper→com.escodro.task.model.AlarmIntervalcom.escodro.task.mapper.TaskMapper→com.escodro.task.model.Taskcom.escodro.task.mapper.TaskWithCategoryMapper→com.escodro.task.model.TaskWithCategory
- Direction
- task.mapper uses task.model, so a change to task.model can break task.mapper, while a change to task.mapper can't break task.model.
- Position
- Below the diagonal: task.mapper uses a module listed above it, which is the healthy direction.
27→3 alarm.notification uses coroutines✕
- Connections
- 3 pairs of types, where a type in alarm.notification uses a type in coroutines.
- The types involved
com.escodro.alarm.notification.AndroidTaskNotification→com.escodro.coroutines.AppCoroutineScopecom.escodro.alarm.notification.NotificationActionDelegate→com.escodro.coroutines.AppCoroutineScopecom.escodro.alarm.notification.TaskNotificationChannel→com.escodro.coroutines.AppCoroutineScope
- Direction
- alarm.notification uses coroutines, so a change to coroutines can break alarm.notification, while a change to alarm.notification can't break coroutines.
- Position
- Below the diagonal: alarm.notification uses a module listed above it, which is the healthy direction.
27→20 alarm.notification uses domain.usecase.task✕
- Connections
- 1 pair of types, where a type in alarm.notification uses a type in domain.usecase.task.
- The types involved
com.escodro.alarm.notification.NotificationActionDelegate→com.escodro.domain.usecase.task.CompleteTask
- Direction
- alarm.notification uses domain.usecase.task, so a change to domain.usecase.task can break alarm.notification, while a change to alarm.notification can't break domain.usecase.task.
- Position
- Below the diagonal: alarm.notification uses a module listed above it, which is the healthy direction.
28→4 domain.usecase.alarm uses domain.model✕
- Connections
- 5 pairs of types, where a type in domain.usecase.alarm uses a type in domain.model.
- The types involved
com.escodro.domain.usecase.alarm.RescheduleFutureAlarms→com.escodro.domain.model.Taskcom.escodro.domain.usecase.alarm.ScheduleNextAlarm→com.escodro.domain.model.AlarmIntervalcom.escodro.domain.usecase.alarm.ScheduleNextAlarm→com.escodro.domain.model.Taskcom.escodro.domain.usecase.alarm.UpdateAlarm→com.escodro.domain.model.Taskcom.escodro.domain.usecase.alarm.UpdateTaskAsRepeating→com.escodro.domain.model.AlarmInterval
- Direction
- domain.usecase.alarm uses domain.model, so a change to domain.model can break domain.usecase.alarm, while a change to domain.usecase.alarm can't break domain.model.
- Position
- Below the diagonal: domain.usecase.alarm uses a module listed above it, which is the healthy direction.
28→10 domain.usecase.alarm uses domain.interactor✕
- Connections
- 5 pairs of types, where a type in domain.usecase.alarm uses a type in domain.interactor.
- The types involved
com.escodro.domain.usecase.alarm.RescheduleFutureAlarms→com.escodro.domain.interactor.AlarmInteractorcom.escodro.domain.usecase.alarm.ScheduleNextAlarm→com.escodro.domain.interactor.AlarmInteractorcom.escodro.domain.usecase.alarm.ShowAlarm→com.escodro.domain.interactor.NotificationInteractorcom.escodro.domain.usecase.alarm.SnoozeAlarm→com.escodro.domain.interactor.AlarmInteractorcom.escodro.domain.usecase.alarm.SnoozeAlarm→com.escodro.domain.interactor.NotificationInteractor
- Direction
- domain.usecase.alarm uses domain.interactor, so a change to domain.interactor can break domain.usecase.alarm, while a change to domain.usecase.alarm can't break domain.interactor.
- Position
- Below the diagonal: domain.usecase.alarm uses a module listed above it, which is the healthy direction.
28→11 domain.usecase.alarm uses domain.repository✕
- Connections
- 3 pairs of types, where a type in domain.usecase.alarm uses a type in domain.repository.
- The types involved
com.escodro.domain.usecase.alarm.RescheduleFutureAlarms→com.escodro.domain.repository.TaskRepositorycom.escodro.domain.usecase.alarm.ScheduleNextAlarm→com.escodro.domain.repository.TaskRepositorycom.escodro.domain.usecase.alarm.ShowAlarm→com.escodro.domain.repository.TaskRepository
- Direction
- domain.usecase.alarm uses domain.repository, so a change to domain.repository can break domain.usecase.alarm, while a change to domain.usecase.alarm can't break domain.repository.
- Position
- Below the diagonal: domain.usecase.alarm uses a module listed above it, which is the healthy direction.
28→20 domain.usecase.alarm uses domain.usecase.task✕
- Connections
- 1 pair of types, where a type in domain.usecase.alarm uses a type in domain.usecase.task.
- The types involved
com.escodro.domain.usecase.alarm.SnoozeAlarm→com.escodro.domain.usecase.task.LoadTask
- Direction
- domain.usecase.alarm uses domain.usecase.task, so a change to domain.usecase.task can break domain.usecase.alarm, while a change to domain.usecase.alarm can't break domain.usecase.task.
- Position
- Below the diagonal: domain.usecase.alarm uses a module listed above it, which is the healthy direction.
29→5 glance.data uses glance.model✕
- Connections
- 3 pairs of types, where a type in glance.data uses a type in glance.model.
- The types involved
com.escodro.glance.data.TaskListGlanceUpdater→com.escodro.glance.model.Taskcom.escodro.glance.data.TaskListStateDefinition→com.escodro.glance.model.Taskcom.escodro.glance.data.TaskListUpdaterWorker→com.escodro.glance.model.Task
- Direction
- glance.data uses glance.model, so a change to glance.model can break glance.data, while a change to glance.data can't break glance.model.
- Position
- Below the diagonal: glance.data uses a module listed above it, which is the healthy direction.
29→20 glance.data uses domain.usecase.task✕
- Connections
- 1 pair of types, where a type in glance.data uses a type in domain.usecase.task.
- The types involved
com.escodro.glance.data.TaskListGlanceUpdater→com.escodro.domain.usecase.task.UpdateTaskStatus
- Direction
- glance.data uses domain.usecase.task, so a change to domain.usecase.task can break glance.data, while a change to glance.data can't break domain.usecase.task.
- Position
- Below the diagonal: glance.data uses a module listed above it, which is the healthy direction.
29→21 glance.data uses domain.usecase.taskwithcategory✕
- Connections
- 1 pair of types, where a type in glance.data uses a type in domain.usecase.taskwithcategory.
- The types involved
com.escodro.glance.data.TaskListGlanceUpdater→com.escodro.domain.usecase.taskwithcategory.LoadUncompletedTasks
- Direction
- glance.data uses domain.usecase.taskwithcategory, so a change to domain.usecase.taskwithcategory can break glance.data, while a change to glance.data can't break domain.usecase.taskwithcategory.
- Position
- Below the diagonal: glance.data uses a module listed above it, which is the healthy direction.
30→14 navigationapi.controller uses navigationapi.destination✕
- Connections
- 1 pair of types, where a type in navigationapi.controller uses a type in navigationapi.destination.
- The types involved
com.escodro.navigationapi.controller.NavEventController→com.escodro.navigationapi.destination.Destination
- Direction
- navigationapi.controller uses navigationapi.destination, so a change to navigationapi.destination can break navigationapi.controller, while a change to navigationapi.controller can't break navigationapi.destination.
- Position
- Below the diagonal: navigationapi.controller uses a module listed above it, which is the healthy direction.
30→24 navigationapi.controller uses navigationapi.event✕
- Connections
- 1 pair of types, where a type in navigationapi.controller uses a type in navigationapi.event.
- The types involved
com.escodro.navigationapi.controller.NavEventController→com.escodro.navigationapi.event.Event
- Direction
- navigationapi.controller uses navigationapi.event, so a change to navigationapi.event can break navigationapi.controller, while a change to navigationapi.controller can't break navigationapi.event.
- Position
- Below the diagonal: navigationapi.controller uses a module listed above it, which is the healthy direction.
31→4 alarm.interactor uses domain.model✕
- Connections
- 2 pairs of types, where a type in alarm.interactor uses a type in domain.model.
- The types involved
com.escodro.alarm.interactor.AlarmInteractorImpl→com.escodro.domain.model.Taskcom.escodro.alarm.interactor.NotificationInteractorImpl→com.escodro.domain.model.Task
- Direction
- alarm.interactor uses domain.model, so a change to domain.model can break alarm.interactor, while a change to alarm.interactor can't break domain.model.
- Position
- Below the diagonal: alarm.interactor uses a module listed above it, which is the healthy direction.
31→10 alarm.interactor uses domain.interactor✕
- Connections
- 2 pairs of types, where a type in alarm.interactor uses a type in domain.interactor.
- The types involved
com.escodro.alarm.interactor.AlarmInteractorImpl→com.escodro.domain.interactor.AlarmInteractorcom.escodro.alarm.interactor.NotificationInteractorImpl→com.escodro.domain.interactor.NotificationInteractor
- Direction
- alarm.interactor uses domain.interactor, so a change to domain.interactor can break alarm.interactor, while a change to alarm.interactor can't break domain.interactor.
- Position
- Below the diagonal: alarm.interactor uses a module listed above it, which is the healthy direction.
31→27 alarm.interactor uses alarm.notification✕
- Connections
- 2 pairs of types, where a type in alarm.interactor uses a type in alarm.notification.
- The types involved
com.escodro.alarm.interactor.AlarmInteractorImpl→com.escodro.alarm.notification.NotificationSchedulercom.escodro.alarm.interactor.NotificationInteractorImpl→com.escodro.alarm.notification.TaskNotification
- Direction
- alarm.interactor uses alarm.notification, so a change to alarm.notification can break alarm.interactor, while a change to alarm.interactor can't break alarm.notification.
- Position
- Below the diagonal: alarm.interactor uses a module listed above it, which is the healthy direction.
32→4 domain.usecase.alarm.implementation uses domain.model✕
- Connections
- 2 pairs of types, where a type in domain.usecase.alarm.implementation uses a type in domain.model.
- The types involved
com.escodro.domain.usecase.alarm.implementation.UpdateAlarmImpl→com.escodro.domain.model.Taskcom.escodro.domain.usecase.alarm.implementation.UpdateTaskAsRepeatingImpl→com.escodro.domain.model.AlarmInterval
- Direction
- domain.usecase.alarm.implementation uses domain.model, so a change to domain.model can break domain.usecase.alarm.implementation, while a change to domain.usecase.alarm.implementation can't break domain.model.
- Position
- Below the diagonal: domain.usecase.alarm.implementation uses a module listed above it, which is the healthy direction.
32→10 domain.usecase.alarm.implementation uses domain.interactor✕
- Connections
- 2 pairs of types, where a type in domain.usecase.alarm.implementation uses a type in domain.interactor.
- The types involved
com.escodro.domain.usecase.alarm.implementation.CancelAlarmImpl→com.escodro.domain.interactor.AlarmInteractorcom.escodro.domain.usecase.alarm.implementation.ScheduleAlarmImpl→com.escodro.domain.interactor.AlarmInteractor
- Direction
- domain.usecase.alarm.implementation uses domain.interactor, so a change to domain.interactor can break domain.usecase.alarm.implementation, while a change to domain.usecase.alarm.implementation can't break domain.interactor.
- Position
- Below the diagonal: domain.usecase.alarm.implementation uses a module listed above it, which is the healthy direction.
32→11 domain.usecase.alarm.implementation uses domain.repository✕
- Connections
- 3 pairs of types, where a type in domain.usecase.alarm.implementation uses a type in domain.repository.
- The types involved
com.escodro.domain.usecase.alarm.implementation.CancelAlarmImpl→com.escodro.domain.repository.TaskRepositorycom.escodro.domain.usecase.alarm.implementation.ScheduleAlarmImpl→com.escodro.domain.repository.TaskRepositorycom.escodro.domain.usecase.alarm.implementation.UpdateTaskAsRepeatingImpl→com.escodro.domain.repository.TaskRepository
- Direction
- domain.usecase.alarm.implementation uses domain.repository, so a change to domain.repository can break domain.usecase.alarm.implementation, while a change to domain.usecase.alarm.implementation can't break domain.repository.
- Position
- Below the diagonal: domain.usecase.alarm.implementation uses a module listed above it, which is the healthy direction.
32→28 domain.usecase.alarm.implementation uses domain.usecase.alarm✕
- Connections
- 7 pairs of types, where a type in domain.usecase.alarm.implementation uses a type in domain.usecase.alarm.
- The types involved
com.escodro.domain.usecase.alarm.implementation.CancelAlarmImpl→com.escodro.domain.usecase.alarm.CancelAlarmcom.escodro.domain.usecase.alarm.implementation.ScheduleAlarmImpl→com.escodro.domain.usecase.alarm.ScheduleAlarmcom.escodro.domain.usecase.alarm.implementation.UpdateAlarmImpl→com.escodro.domain.usecase.alarm.CancelAlarmcom.escodro.domain.usecase.alarm.implementation.UpdateAlarmImpl→com.escodro.domain.usecase.alarm.ScheduleAlarmcom.escodro.domain.usecase.alarm.implementation.UpdateAlarmImpl→com.escodro.domain.usecase.alarm.UpdateAlarmcom.escodro.domain.usecase.alarm.implementation.UpdateAlarmImpl→com.escodro.domain.usecase.alarm.UpdateTaskAsRepeatingcom.escodro.domain.usecase.alarm.implementation.UpdateTaskAsRepeatingImpl→com.escodro.domain.usecase.alarm.UpdateTaskAsRepeating
- Direction
- domain.usecase.alarm.implementation uses domain.usecase.alarm, so a change to domain.usecase.alarm can break domain.usecase.alarm.implementation, while a change to domain.usecase.alarm.implementation can't break domain.usecase.alarm.
- Position
- Below the diagonal: domain.usecase.alarm.implementation uses a module listed above it, which is the healthy direction.
33→4 domain.usecase.task.implementation uses domain.model✕
- Connections
- 3 pairs of types, where a type in domain.usecase.task.implementation uses a type in domain.model.
- The types involved
com.escodro.domain.usecase.task.implementation.AddTaskImpl→com.escodro.domain.model.Taskcom.escodro.domain.usecase.task.implementation.LoadTaskImpl→com.escodro.domain.model.Taskcom.escodro.domain.usecase.task.implementation.UpdateTaskImpl→com.escodro.domain.model.Task
- Direction
- domain.usecase.task.implementation uses domain.model, so a change to domain.model can break domain.usecase.task.implementation, while a change to domain.usecase.task.implementation can't break domain.model.
- Position
- Below the diagonal: domain.usecase.task.implementation uses a module listed above it, which is the healthy direction.
33→10 domain.usecase.task.implementation uses domain.interactor✕
- Connections
- 5 pairs of types, where a type in domain.usecase.task.implementation uses a type in domain.interactor.
- The types involved
com.escodro.domain.usecase.task.implementation.AddTaskImpl→com.escodro.domain.interactor.GlanceInteractorcom.escodro.domain.usecase.task.implementation.UpdateTaskImpl→com.escodro.domain.interactor.GlanceInteractorcom.escodro.domain.usecase.task.implementation.UpdateTaskStatusImpl→com.escodro.domain.interactor.GlanceInteractorcom.escodro.domain.usecase.task.implementation.UpdateTaskTitleImpl→com.escodro.domain.interactor.AlarmInteractorcom.escodro.domain.usecase.task.implementation.UpdateTaskTitleImpl→com.escodro.domain.interactor.GlanceInteractor
- Direction
- domain.usecase.task.implementation uses domain.interactor, so a change to domain.interactor can break domain.usecase.task.implementation, while a change to domain.usecase.task.implementation can't break domain.interactor.
- Position
- Below the diagonal: domain.usecase.task.implementation uses a module listed above it, which is the healthy direction.
33→11 domain.usecase.task.implementation uses domain.repository✕
- Connections
- 4 pairs of types, where a type in domain.usecase.task.implementation uses a type in domain.repository.
- The types involved
com.escodro.domain.usecase.task.implementation.AddTaskImpl→com.escodro.domain.repository.TaskRepositorycom.escodro.domain.usecase.task.implementation.LoadTaskImpl→com.escodro.domain.repository.TaskRepositorycom.escodro.domain.usecase.task.implementation.UpdateTaskImpl→com.escodro.domain.repository.TaskRepositorycom.escodro.domain.usecase.task.implementation.UpdateTaskStatusImpl→com.escodro.domain.repository.TaskRepository
- Direction
- domain.usecase.task.implementation uses domain.repository, so a change to domain.repository can break domain.usecase.task.implementation, while a change to domain.usecase.task.implementation can't break domain.repository.
- Position
- Below the diagonal: domain.usecase.task.implementation uses a module listed above it, which is the healthy direction.
33→20 domain.usecase.task.implementation uses domain.usecase.task✕
- Connections
- 15 pairs of types, where a type in domain.usecase.task.implementation uses a type in domain.usecase.task.
- The types involved
com.escodro.domain.usecase.task.implementation.AddTaskImpl→com.escodro.domain.usecase.task.AddTaskcom.escodro.domain.usecase.task.implementation.LoadTaskImpl→com.escodro.domain.usecase.task.LoadTaskcom.escodro.domain.usecase.task.implementation.UpdateTaskCategoryImpl→com.escodro.domain.usecase.task.LoadTaskcom.escodro.domain.usecase.task.implementation.UpdateTaskCategoryImpl→com.escodro.domain.usecase.task.UpdateTaskcom.escodro.domain.usecase.task.implementation.UpdateTaskCategoryImpl→com.escodro.domain.usecase.task.UpdateTaskCategorycom.escodro.domain.usecase.task.implementation.UpdateTaskDescriptionImpl→com.escodro.domain.usecase.task.LoadTaskcom.escodro.domain.usecase.task.implementation.UpdateTaskDescriptionImpl→com.escodro.domain.usecase.task.UpdateTaskcom.escodro.domain.usecase.task.implementation.UpdateTaskDescriptionImpl→com.escodro.domain.usecase.task.UpdateTaskDescriptioncom.escodro.domain.usecase.task.implementation.UpdateTaskImpl→com.escodro.domain.usecase.task.UpdateTaskcom.escodro.domain.usecase.task.implementation.UpdateTaskStatusImpl→com.escodro.domain.usecase.task.CompleteTaskcom.escodro.domain.usecase.task.implementation.UpdateTaskStatusImpl→com.escodro.domain.usecase.task.UncompleteTaskcom.escodro.domain.usecase.task.implementation.UpdateTaskStatusImpl→com.escodro.domain.usecase.task.UpdateTaskStatuscom.escodro.domain.usecase.task.implementation.UpdateTaskTitleImpl→com.escodro.domain.usecase.task.LoadTaskcom.escodro.domain.usecase.task.implementation.UpdateTaskTitleImpl→com.escodro.domain.usecase.task.UpdateTaskcom.escodro.domain.usecase.task.implementation.UpdateTaskTitleImpl→com.escodro.domain.usecase.task.UpdateTaskTitle
- Direction
- domain.usecase.task.implementation uses domain.usecase.task, so a change to domain.usecase.task can break domain.usecase.task.implementation, while a change to domain.usecase.task.implementation can't break domain.usecase.task.
- Position
- Below the diagonal: domain.usecase.task.implementation uses a module listed above it, which is the healthy direction.
33→28 domain.usecase.task.implementation uses domain.usecase.alarm✕
- Connections
- 1 pair of types, where a type in domain.usecase.task.implementation uses a type in domain.usecase.alarm.
- The types involved
com.escodro.domain.usecase.task.implementation.AddTaskImpl→com.escodro.domain.usecase.alarm.UpdateAlarm
- Direction
- domain.usecase.task.implementation uses domain.usecase.alarm, so a change to domain.usecase.alarm can break domain.usecase.task.implementation, while a change to domain.usecase.task.implementation can't break domain.usecase.alarm.
- Position
- Below the diagonal: domain.usecase.task.implementation uses a module listed above it, which is the healthy direction.
34→14 navigation.compose uses navigationapi.destination✕
- Connections
- 1 pair of types, where a type in navigation.compose uses a type in navigationapi.destination.
- The types involved
com.escodro.navigation.compose.NavigationKt→com.escodro.navigationapi.destination.Destination
- Direction
- navigation.compose uses navigationapi.destination, so a change to navigationapi.destination can break navigation.compose, while a change to navigation.compose can't break navigationapi.destination.
- Position
- Below the diagonal: navigation.compose uses a module listed above it, which is the healthy direction.
34→30 navigation.compose uses navigationapi.controller✕
- Connections
- 2 pairs of types, where a type in navigation.compose uses a type in navigationapi.controller.
- The types involved
com.escodro.navigation.compose.NavigationKt→com.escodro.navigationapi.controller.NavBackStackcom.escodro.navigation.compose.NavigationKt→com.escodro.navigationapi.controller.NavEventController
- Direction
- navigation.compose uses navigationapi.controller, so a change to navigationapi.controller can break navigation.compose, while a change to navigation.compose can't break navigationapi.controller.
- Position
- Below the diagonal: navigation.compose uses a module listed above it, which is the healthy direction.
35→3 navigation.controller uses coroutines✕
- Connections
- 1 pair of types, where a type in navigation.controller uses a type in coroutines.
- The types involved
com.escodro.navigation.controller.NavEventControllerImpl→com.escodro.coroutines.AppCoroutineScope
- Direction
- navigation.controller uses coroutines, so a change to coroutines can break navigation.controller, while a change to navigation.controller can't break coroutines.
- Position
- Below the diagonal: navigation.controller uses a module listed above it, which is the healthy direction.
35→14 navigation.controller uses navigationapi.destination✕
- Connections
- 1 pair of types, where a type in navigation.controller uses a type in navigationapi.destination.
- The types involved
com.escodro.navigation.controller.NavEventControllerImpl→com.escodro.navigationapi.destination.Destination
- Direction
- navigation.controller uses navigationapi.destination, so a change to navigationapi.destination can break navigation.controller, while a change to navigation.controller can't break navigationapi.destination.
- Position
- Below the diagonal: navigation.controller uses a module listed above it, which is the healthy direction.
35→24 navigation.controller uses navigationapi.event✕
- Connections
- 1 pair of types, where a type in navigation.controller uses a type in navigationapi.event.
- The types involved
com.escodro.navigation.controller.NavEventControllerImpl→com.escodro.navigationapi.event.Event
- Direction
- navigation.controller uses navigationapi.event, so a change to navigationapi.event can break navigation.controller, while a change to navigation.controller can't break navigationapi.event.
- Position
- Below the diagonal: navigation.controller uses a module listed above it, which is the healthy direction.
35→30 navigation.controller uses navigationapi.controller✕
- Connections
- 1 pair of types, where a type in navigation.controller uses a type in navigationapi.controller.
- The types involved
com.escodro.navigation.controller.NavEventControllerImpl→com.escodro.navigationapi.controller.NavEventController
- Direction
- navigation.controller uses navigationapi.controller, so a change to navigationapi.controller can break navigation.controller, while a change to navigation.controller can't break navigationapi.controller.
- Position
- Below the diagonal: navigation.controller uses a module listed above it, which is the healthy direction.
36→14 navigationapi.provider uses navigationapi.destination✕
- Connections
- 1 pair of types, where a type in navigationapi.provider uses a type in navigationapi.destination.
- The types involved
com.escodro.navigationapi.provider.NavGraph→com.escodro.navigationapi.destination.Destination
- Direction
- navigationapi.provider uses navigationapi.destination, so a change to navigationapi.destination can break navigationapi.provider, while a change to navigationapi.provider can't break navigationapi.destination.
- Position
- Below the diagonal: navigationapi.provider uses a module listed above it, which is the healthy direction.
36→30 navigationapi.provider uses navigationapi.controller✕
- Connections
- 1 pair of types, where a type in navigationapi.provider uses a type in navigationapi.controller.
- The types involved
com.escodro.navigationapi.provider.NavGraph→com.escodro.navigationapi.controller.NavEventController
- Direction
- navigationapi.provider uses navigationapi.controller, so a change to navigationapi.controller can break navigationapi.provider, while a change to navigationapi.provider can't break navigationapi.controller.
- Position
- Below the diagonal: navigationapi.provider uses a module listed above it, which is the healthy direction.
37→3 task.presentation.detail.alarm uses coroutines✕
- Connections
- 1 pair of types, where a type in task.presentation.detail.alarm uses a type in coroutines.
- The types involved
com.escodro.task.presentation.detail.alarm.TaskAlarmViewModel→com.escodro.coroutines.AppCoroutineScope
- Direction
- task.presentation.detail.alarm uses coroutines, so a change to coroutines can break task.presentation.detail.alarm, while a change to task.presentation.detail.alarm can't break coroutines.
- Position
- Below the diagonal: task.presentation.detail.alarm uses a module listed above it, which is the healthy direction.
37→17 task.presentation.detail.alarm uses task.model✕
- Connections
- 5 pairs of types, where a type in task.presentation.detail.alarm uses a type in task.model.
- The types involved
com.escodro.task.presentation.detail.alarm.AlarmSelectionComponentsKt→com.escodro.task.model.AlarmIntervalcom.escodro.task.presentation.detail.alarm.AlarmSelectionKt→com.escodro.task.model.AlarmIntervalcom.escodro.task.presentation.detail.alarm.AlarmSelectionState→com.escodro.task.model.AlarmIntervalcom.escodro.task.presentation.detail.alarm.AlarmSelectionStateKt→com.escodro.task.model.AlarmIntervalcom.escodro.task.presentation.detail.alarm.TaskAlarmViewModel→com.escodro.task.model.AlarmInterval
- Direction
- task.presentation.detail.alarm uses task.model, so a change to task.model can break task.presentation.detail.alarm, while a change to task.presentation.detail.alarm can't break task.model.
- Position
- Below the diagonal: task.presentation.detail.alarm uses a module listed above it, which is the healthy direction.
37→20 task.presentation.detail.alarm uses domain.usecase.task✕
- Connections
- 1 pair of types, where a type in task.presentation.detail.alarm uses a type in domain.usecase.task.
- The types involved
com.escodro.task.presentation.detail.alarm.TaskAlarmViewModel→com.escodro.domain.usecase.task.LoadTask
- Direction
- task.presentation.detail.alarm uses domain.usecase.task, so a change to domain.usecase.task can break task.presentation.detail.alarm, while a change to task.presentation.detail.alarm can't break domain.usecase.task.
- Position
- Below the diagonal: task.presentation.detail.alarm uses a module listed above it, which is the healthy direction.
37→26 task.presentation.detail.alarm uses task.mapper✕
- Connections
- 1 pair of types, where a type in task.presentation.detail.alarm uses a type in task.mapper.
- The types involved
com.escodro.task.presentation.detail.alarm.TaskAlarmViewModel→com.escodro.task.mapper.AlarmIntervalMapper
- Direction
- task.presentation.detail.alarm uses task.mapper, so a change to task.mapper can break task.presentation.detail.alarm, while a change to task.presentation.detail.alarm can't break task.mapper.
- Position
- Below the diagonal: task.presentation.detail.alarm uses a module listed above it, which is the healthy direction.
37→28 task.presentation.detail.alarm uses domain.usecase.alarm✕
- Connections
- 1 pair of types, where a type in task.presentation.detail.alarm uses a type in domain.usecase.alarm.
- The types involved
com.escodro.task.presentation.detail.alarm.TaskAlarmViewModel→com.escodro.domain.usecase.alarm.UpdateAlarm
- Direction
- task.presentation.detail.alarm uses domain.usecase.alarm, so a change to domain.usecase.alarm can break task.presentation.detail.alarm, while a change to task.presentation.detail.alarm can't break domain.usecase.alarm.
- Position
- Below the diagonal: task.presentation.detail.alarm uses a module listed above it, which is the healthy direction.
37→38 task.presentation.detail.alarm uses task.presentation.detail.main part of a loop✕
- Connections
- 1 pair of types, where a type in task.presentation.detail.alarm uses a type in task.presentation.detail.main.
- The types involved
com.escodro.task.presentation.detail.alarm.TaskAlarmViewModel→com.escodro.task.presentation.detail.main.TaskId
- Direction
- task.presentation.detail.alarm uses task.presentation.detail.main, so a change to task.presentation.detail.main can break task.presentation.detail.alarm, while a change to task.presentation.detail.alarm can't break task.presentation.detail.main.
- 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.
38→2 task.presentation.detail.main uses categoryapi.presentation✕
- Connections
- 2 pairs of types, where a type in task.presentation.detail.main uses a type in categoryapi.presentation.
- The types involved
com.escodro.task.presentation.detail.main.TaskDetailKt→com.escodro.categoryapi.presentation.CategoryListViewModelcom.escodro.task.presentation.detail.main.TaskDetailKt→com.escodro.categoryapi.presentation.CategoryState
- Direction
- task.presentation.detail.main uses categoryapi.presentation, so a change to categoryapi.presentation can break task.presentation.detail.main, while a change to task.presentation.detail.main can't break categoryapi.presentation.
- Position
- Below the diagonal: task.presentation.detail.main uses a module listed above it, which is the healthy direction.
38→3 task.presentation.detail.main uses coroutines✕
- Connections
- 2 pairs of types, where a type in task.presentation.detail.main uses a type in coroutines.
- The types involved
com.escodro.task.presentation.detail.main.TaskDetailViewModel→com.escodro.coroutines.AppCoroutineScopecom.escodro.task.presentation.detail.main.TaskDetailViewModel→com.escodro.coroutines.CoroutineDebouncer
- Direction
- task.presentation.detail.main uses coroutines, so a change to coroutines can break task.presentation.detail.main, while a change to task.presentation.detail.main can't break coroutines.
- Position
- Below the diagonal: task.presentation.detail.main uses a module listed above it, which is the healthy direction.
38→17 task.presentation.detail.main uses task.model✕
- Connections
- 1 pair of types, where a type in task.presentation.detail.main uses a type in task.model.
- The types involved
com.escodro.task.presentation.detail.main.TaskDetailKt→com.escodro.task.model.Task
- Direction
- task.presentation.detail.main uses task.model, so a change to task.model can break task.presentation.detail.main, while a change to task.presentation.detail.main can't break task.model.
- Position
- Below the diagonal: task.presentation.detail.main uses a module listed above it, which is the healthy direction.
38→20 task.presentation.detail.main uses domain.usecase.task✕
- Connections
- 4 pairs of types, where a type in task.presentation.detail.main uses a type in domain.usecase.task.
- The types involved
com.escodro.task.presentation.detail.main.TaskDetailViewModel→com.escodro.domain.usecase.task.LoadTaskcom.escodro.task.presentation.detail.main.TaskDetailViewModel→com.escodro.domain.usecase.task.UpdateTaskCategorycom.escodro.task.presentation.detail.main.TaskDetailViewModel→com.escodro.domain.usecase.task.UpdateTaskDescriptioncom.escodro.task.presentation.detail.main.TaskDetailViewModel→com.escodro.domain.usecase.task.UpdateTaskTitle
- Direction
- task.presentation.detail.main uses domain.usecase.task, so a change to domain.usecase.task can break task.presentation.detail.main, while a change to task.presentation.detail.main can't break domain.usecase.task.
- Position
- Below the diagonal: task.presentation.detail.main uses a module listed above it, which is the healthy direction.
38→26 task.presentation.detail.main uses task.mapper✕
- Connections
- 1 pair of types, where a type in task.presentation.detail.main uses a type in task.mapper.
- The types involved
com.escodro.task.presentation.detail.main.TaskDetailViewModel→com.escodro.task.mapper.TaskMapper
- Direction
- task.presentation.detail.main uses task.mapper, so a change to task.mapper can break task.presentation.detail.main, while a change to task.presentation.detail.main can't break task.mapper.
- Position
- Below the diagonal: task.presentation.detail.main uses a module listed above it, which is the healthy direction.
38→37 task.presentation.detail.main uses task.presentation.detail.alarm✕
- Connections
- 1 pair of types, where a type in task.presentation.detail.main uses a type in task.presentation.detail.alarm.
- The types involved
com.escodro.task.presentation.detail.main.TaskDetailKt→com.escodro.task.presentation.detail.alarm.TaskAlarmViewModel
- Direction
- task.presentation.detail.main uses task.presentation.detail.alarm, so a change to task.presentation.detail.alarm can break task.presentation.detail.main, while a change to task.presentation.detail.main can't break task.presentation.detail.alarm.
- Position
- Below the diagonal: task.presentation.detail.main uses a module listed above it, which is the healthy direction.
39→2 task.presentation.add uses categoryapi.presentation✕
- Connections
- 1 pair of types, where a type in task.presentation.add uses a type in categoryapi.presentation.
- The types involved
com.escodro.task.presentation.add.TaskBottomSheetKt→com.escodro.categoryapi.presentation.CategoryListViewModel
- Direction
- task.presentation.add uses categoryapi.presentation, so a change to categoryapi.presentation can break task.presentation.add, while a change to task.presentation.add can't break categoryapi.presentation.
- Position
- Below the diagonal: task.presentation.add uses a module listed above it, which is the healthy direction.
39→3 task.presentation.add uses coroutines✕
- Connections
- 1 pair of types, where a type in task.presentation.add uses a type in coroutines.
- The types involved
com.escodro.task.presentation.add.AddTaskViewModel→com.escodro.coroutines.AppCoroutineScope
- Direction
- task.presentation.add uses coroutines, so a change to coroutines can break task.presentation.add, while a change to task.presentation.add can't break coroutines.
- Position
- Below the diagonal: task.presentation.add uses a module listed above it, which is the healthy direction.
39→17 task.presentation.add uses task.model✕
- Connections
- 1 pair of types, where a type in task.presentation.add uses a type in task.model.
- The types involved
com.escodro.task.presentation.add.AddTaskViewModel→com.escodro.task.model.AlarmInterval
- Direction
- task.presentation.add uses task.model, so a change to task.model can break task.presentation.add, while a change to task.presentation.add can't break task.model.
- Position
- Below the diagonal: task.presentation.add uses a module listed above it, which is the healthy direction.
39→20 task.presentation.add uses domain.usecase.task✕
- Connections
- 1 pair of types, where a type in task.presentation.add uses a type in domain.usecase.task.
- The types involved
com.escodro.task.presentation.add.AddTaskViewModel→com.escodro.domain.usecase.task.AddTask
- Direction
- task.presentation.add uses domain.usecase.task, so a change to domain.usecase.task can break task.presentation.add, while a change to task.presentation.add can't break domain.usecase.task.
- Position
- Below the diagonal: task.presentation.add uses a module listed above it, which is the healthy direction.
39→26 task.presentation.add uses task.mapper✕
- Connections
- 1 pair of types, where a type in task.presentation.add uses a type in task.mapper.
- The types involved
com.escodro.task.presentation.add.AddTaskViewModel→com.escodro.task.mapper.AlarmIntervalMapper
- Direction
- task.presentation.add uses task.mapper, so a change to task.mapper can break task.presentation.add, while a change to task.presentation.add can't break task.mapper.
- Position
- Below the diagonal: task.presentation.add uses a module listed above it, which is the healthy direction.
39→38 task.presentation.add uses task.presentation.detail.main✕
- Connections
- 1 pair of types, where a type in task.presentation.add uses a type in task.presentation.detail.main.
- The types involved
com.escodro.task.presentation.add.AddTaskViewModel→com.escodro.task.presentation.detail.main.CategoryId
- Direction
- task.presentation.add uses task.presentation.detail.main, so a change to task.presentation.detail.main can break task.presentation.add, while a change to task.presentation.add can't break task.presentation.detail.main.
- Position
- Below the diagonal: task.presentation.add uses a module listed above it, which is the healthy direction.
40→2 task.presentation.list uses categoryapi.presentation✕
- Connections
- 3 pairs of types, where a type in task.presentation.list uses a type in categoryapi.presentation.
- The types involved
com.escodro.task.presentation.list.CategoryStateHandler→com.escodro.categoryapi.presentation.CategoryStatecom.escodro.task.presentation.list.TaskListKt→com.escodro.categoryapi.presentation.CategoryListViewModelcom.escodro.task.presentation.list.TaskListKt→com.escodro.categoryapi.presentation.CategoryState
- Direction
- task.presentation.list uses categoryapi.presentation, so a change to categoryapi.presentation can break task.presentation.list, while a change to task.presentation.list can't break categoryapi.presentation.
- Position
- Below the diagonal: task.presentation.list uses a module listed above it, which is the healthy direction.
40→3 task.presentation.list uses coroutines✕
- Connections
- 1 pair of types, where a type in task.presentation.list uses a type in coroutines.
- The types involved
com.escodro.task.presentation.list.TaskListViewModel→com.escodro.coroutines.AppCoroutineScope
- Direction
- task.presentation.list uses coroutines, so a change to coroutines can break task.presentation.list, while a change to task.presentation.list can't break coroutines.
- Position
- Below the diagonal: task.presentation.list uses a module listed above it, which is the healthy direction.
40→17 task.presentation.list uses task.model✕
- Connections
- 4 pairs of types, where a type in task.presentation.list uses a type in task.model.
- The types involved
com.escodro.task.presentation.list.TaskListComponentsKt→com.escodro.task.model.TaskWithCategorycom.escodro.task.presentation.list.TaskListKt→com.escodro.task.model.TaskWithCategorycom.escodro.task.presentation.list.TaskListViewModel→com.escodro.task.model.TaskWithCategorycom.escodro.task.presentation.list.TaskStateHandler→com.escodro.task.model.TaskWithCategory
- Direction
- task.presentation.list uses task.model, so a change to task.model can break task.presentation.list, while a change to task.presentation.list can't break task.model.
- Position
- Below the diagonal: task.presentation.list uses a module listed above it, which is the healthy direction.
40→20 task.presentation.list uses domain.usecase.task✕
- Connections
- 1 pair of types, where a type in task.presentation.list uses a type in domain.usecase.task.
- The types involved
com.escodro.task.presentation.list.TaskListViewModel→com.escodro.domain.usecase.task.UpdateTaskStatus
- Direction
- task.presentation.list uses domain.usecase.task, so a change to domain.usecase.task can break task.presentation.list, while a change to task.presentation.list can't break domain.usecase.task.
- Position
- Below the diagonal: task.presentation.list uses a module listed above it, which is the healthy direction.
40→21 task.presentation.list uses domain.usecase.taskwithcategory✕
- Connections
- 1 pair of types, where a type in task.presentation.list uses a type in domain.usecase.taskwithcategory.
- The types involved
com.escodro.task.presentation.list.TaskListViewModel→com.escodro.domain.usecase.taskwithcategory.LoadUncompletedTasks
- Direction
- task.presentation.list uses domain.usecase.taskwithcategory, so a change to domain.usecase.taskwithcategory can break task.presentation.list, while a change to task.presentation.list can't break domain.usecase.taskwithcategory.
- Position
- Below the diagonal: task.presentation.list uses a module listed above it, which is the healthy direction.
40→26 task.presentation.list uses task.mapper✕
- Connections
- 1 pair of types, where a type in task.presentation.list uses a type in task.mapper.
- The types involved
com.escodro.task.presentation.list.TaskListViewModel→com.escodro.task.mapper.TaskWithCategoryMapper
- Direction
- task.presentation.list uses task.mapper, so a change to task.mapper can break task.presentation.list, while a change to task.presentation.list can't break task.mapper.
- Position
- Below the diagonal: task.presentation.list uses a module listed above it, which is the healthy direction.
40→38 task.presentation.list uses task.presentation.detail.main✕
- Connections
- 2 pairs of types, where a type in task.presentation.list uses a type in task.presentation.detail.main.
- The types involved
com.escodro.task.presentation.list.CategoryStateHandler→com.escodro.task.presentation.detail.main.CategoryIdcom.escodro.task.presentation.list.TaskListKt→com.escodro.task.presentation.detail.main.CategoryId
- Direction
- task.presentation.list uses task.presentation.detail.main, so a change to task.presentation.detail.main can break task.presentation.list, while a change to task.presentation.list can't break task.presentation.detail.main.
- Position
- Below the diagonal: task.presentation.list uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Domain Modelling
At a glance — Accessibility
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 34 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 8 | Medium |
| A07:2025 — Authentication Failures | 6 | High / Critical |
Roadmap
Top priorities: Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href; Resolve the 4 Leaked secret finding(s) in Secret Scanning — start with REDACTED (2), REDACTED, REDACTED; Enforce accessibility in the toolchain your project already uses: assert accessibility in your UI test suite with your toolkit's own matcher (Flutter `meetsGuideline`, Espresso `AccessibilityChecks`, XCTest `performAccessibilityAudit`), then gate that test in CI so a regression blocks the merge.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 4 Leaked secret finding(s) in Secret Scanning — start with REDACTED (2), REDACTED, REDACTED. | +6.1 pts | Low | Secret Scanning |
| Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href. | +8.1 pts | Medium | Keyboard semantics |
| Enforce accessibility in the toolchain your project already uses: assert accessibility in your UI test suite with your toolkit's own matcher (Flutter `meetsGuideline`, Espresso `AccessibilityChecks`, XCTest `performAccessibilityAudit`), then gate that test in CI so a regression blocks the merge. | +3.6 pts | Medium | A11y enforcement |
| Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label. | +2.9 pts | Medium | Forms & labels |
| Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh. | +2.8 pts | Medium | Page structure |
| 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. | +2.7 pts | Medium | Security & performance tooling |
| Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED. | +1.3 pts | Low | Static Analysis (SAST) |
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +1.2 pts | Low | ADR Quality |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | Secret Scanning: Leaked secret: REDACTED |
| REDACTED | 4.4 | Mixed | Secret Scanning: Leaked secret: REDACTED |
| REDACTED | 4.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Secret Scanning: Leaked secret: REDACTED |
| features/alarm/src/desktopMain/kotlin/com/escodro/alarm/permission/DesktopAlarmPermission.kt | 6.9 | Mixed | Explicit Debt: TodoComment |
| features/alarm/src/desktopMain/kotlin/com/escodro/alarm/notification/DesktopNotificationScheduler.kt | 6.9 | Mixed | Explicit Debt: TodoComment |
| features/alarm/src/desktopMain/kotlin/com/escodro/alarm/notification/DesktopTaskNotification.kt | 6.9 | Mixed | Explicit Debt: TodoComment |
| libraries/designsystem/src/commonMain/kotlin/com/escodro/designsystem/components/kuvio/dialog/KuvioDialog.kt | 7.1 | Mixed | Code Duplication: Members sharing a duplicated core (4 members, 50+ identical tokens) |
| libraries/designsystem/src/commonMain/kotlin/com/escodro/designsystem/components/kuvio/item/KuvioTaskItem.kt | 7.2 | Mixed | Code Duplication: Duplicated block (16 lines × 2) |
| libraries/permission/src/desktopMain/kotlin/com/escodro/permission/api/DesktopPermissionController.kt | 7.3 | Mixed | Explicit Debt: TodoComment |
| features/navigation-api/src/androidMain/kotlin/com/escodro/navigationapi/deeplink/AndroidDeepLink.kt | 8.2 | Near-clean | Explicit Debt: TodoComment |
| domain/src/commonMain/kotlin/com/escodro/domain/usecase/task/DeleteTask.kt | 8.2 | Near-clean | Explicit Debt: TodoComment |
| libraries/designsystem/src/commonMain/kotlin/com/escodro/designsystem/theme/Type.kt | 8.5 | Near-clean | God Classes: MethodTooLong: TypeKt.alkaaTypography |
| libraries/designsystem/src/commonMain/kotlin/com/escodro/designsystem/components/kuvio/item/KuvioTaskListItem.kt | 8.5 | Near-clean | Code Duplication: Duplicated block (14 lines × 2) |
| libraries/designsystem/src/commonMain/kotlin/com/escodro/designsystem/components/kuvio/chip/KuvioTaskChip.kt | 8.5 | Near-clean | Code Duplication: Duplicated block (13 lines × 2) |
| libraries/permission/src/androidMain/kotlin/com/escodro/permission/api/AndroidPermissionController.kt | 8.5 | Near-clean | Code Duplication: Duplicated block (13 lines × 2) |
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 63 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 — 63 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, 119 of 564 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. To have real coverage read, produce a coverage report in a standard format (JaCoCo XML — the Gradle `jacocoTestReport` task) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (JaCoCo XML — the Gradle `jacocoTestReport` task) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.kt) and this repository declares a JVM test suite (repository root, Gradle), but it was not re-run: no test result was produced. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D12 Dependency Hygiene — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Currency was graded against Maven Central, but whether an artifact is DEPRECATED is not: Maven Central publishes no deprecation marker, exactly as rubygems.org does not. Whether one is UNMAINTAINED is not graded either — no registry publishes a maintenance status, and release age does not stand in for one. Two of this dimension's four signals are therefore unread on a Gradle tree, and its score reflects currency alone.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (7 contributor(s) across 3106 commit(s) sampled, automation and bot accounts excluded). One of them holds 99% of the history; the other 6 hold 0.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.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (shared/build.gradle.kts), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `features/task/src/commonMain/kotlin/com/escodro/task/presentation/detail/main/TaskDetail.kt` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- AX1 Captive dependencies — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository's container is Koin, whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- DM8 Value-object opportunities — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check finds primitive parameters that travel together through several signatures of the domain (a missing value object). Its deterministic rule has not yet shown 95 % precision on adjudicated rows, so the clumps it finds are counted here and not published as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
- DM9 Scattered domain decisions — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Arm two tells a construction that PRODUCES a measurement from one that merely passes it along, and this repository's frontend does not compute that fact. A measurement built independently in two places would not appear above.
- DM9 Scattered domain decisions — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Some of this repository's production types come from a frontend that does not bind comparison operands to the members they read, which arm one needs, and those types were not walked for this dimension. The counts above speak for the languages that declare it.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Kotlin, Swift is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's Kotlin, Swift 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.
- X2 Cancellation propagation — 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, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch, got, undici, node:http; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, 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.
- 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.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- 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.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
- AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
- AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
0 method(s) exceeded the cyclomatic complexity threshold of 15.
D2 · Cognitive Complexity
0 method(s) exceeded the cognitive complexity threshold of 15.
D3 · God Classes
1 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 1 MethodTooLong finding(s) in God Classes — start with Type.kt. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
14 duplicated block group(s) detected. One further row reports members as variants of one another; it aggregates block groups already counted above and is not itself counted.
What to do
- Resolve the 3 Duplicated block (13 lines × 2) finding(s) in Code Duplication — start with KuvioTaskChip.kt, KuvioTaskItem.kt, AndroidPermissionController.kt. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 Duplicated block (16 lines × 2) finding(s) in Code Duplication — start with KuvioTaskItem.kt (2). — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Members sharing a duplicated core (4 members, 50+ identical tokens) finding(s) in Code Duplication — start with KuvioDialog.kt. — One of this dimension's main actionable groups (1 warning-level).
D5 · Coupling
28 production modules (Gradle), 0 dependency cycle(s), 4 unstable depended-on module(s). Read from the build's own module declarations; edges a convention plugin adds from buildSrc or build-logic are not visible there; 2 module(s) off the main sequence, with abstractness counted on 26 of the 28 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What to do
- Resolve the 4 Unstable project finding(s) in Coupling. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 2 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (2 warning-level).
D6 · Cohesion (LCOM4)
0 of 30 classes have LCOM4 above 3.
D12 · Dependency Hygiene
This repository's Gradle dependency graph was RESOLVED BY A BUILD, across every subproject rather than the root alone: 950 artifact(s) resolved, 611 of them gradable against Maven Central, and 430 behind a shipped release. Where a version was requested and a different one won conflict resolution, the RESOLVED version is what is graded — grading the request would recommend an upgrade already applied. Known CVEs in the same graph are a separate question again, reported under D30.
D13 · Secret Scanning
3 secret(s) detected.
What to do
- Resolve the 4 Leaked secret finding(s) in Secret Scanning — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (4 issue-level).
D14 · License Compliance
0 of 38 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 30 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 15 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
13 deducted task-comment markers across 15722 LoC (0.1/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 13 TodoComment finding(s) in Explicit Debt — start with DesktopAlarmPermission.kt (3), DesktopNotificationScheduler.kt (3), DesktopTaskNotification.kt (3). — One of this dimension's main actionable groups (13 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 33 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
0 of 28 build units (Gradle, Xcode) flagged as possibly oversized/incoherent.
D28 · Secrets (history)
2 finding(s): 0 critical, 2 high, 0 medium, 0 low.
What to do
- Resolve the 2 High secret finding(s) in Secrets (history) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
D29 · Static Analysis (SAST)
34 finding(s): 0 critical, 34 high, 0 medium, 0 low. 30 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 1 file(s) — `gradlew` (line 74, line 178) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 2 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 30 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 (30 issue-level, 0 of them charged here).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 53 of the 431 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
Strongest change-coupling: Color.kt↔Theme.kt 73%; Theme.kt↔Type.kt 69%; Color.kt↔Type.kt 55%
What to do
- Resolve the 1 Change coupling clique finding(s) in Change Coupling — start with Color.kt. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Change coupling finding(s) in Change Coupling — start with AndroidNotificationScheduler.kt. — One of this dimension's main actionable groups (1 warning-level).
D36 · Supply-chain Provenance & Signing
1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 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 — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 2 platform declaration(s) and 53 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AC2 · Forms & labels
- A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one). (×10) — assets/designsystem/alkaa-ds.html:4029, assets/designsystem/alkaa-ds.html:4032, assets/designsystem/alkaa-ds.html:4035, …
- This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×8) — assets/designsystem/alkaa-ds.html:4440, assets/designsystem/alkaa-ds.html:4449, assets/designsystem/alkaa-ds.html:4461, …
- This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label. — assets/designsystem/alkaa-ds.html:5772
What to do
- Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
AC3 · Page structure
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — assets/designsystem/alkaa-ds.html:2
What to do
- Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC4 · Keyboard semantics
- A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler. — assets/designsystem/alkaa-ds.html:2452
What to do
- Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
AC6 · Visual & motion safety
- `.toggle-thumb` moves (`transition: transform .25s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — assets/designsystem/alkaa-ds.html:86
- `.section` moves (`animation: fadeUp .4s ease both`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — assets/designsystem/alkaa-ds.html:90
- `.ssc-card` moves (`transition: transform .15s, box-shadow .15s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — assets/designsystem/alkaa-ds.html:214
- `.fab` moves (`transition: box-shadow .2s, transform .1s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — assets/designsystem/alkaa-ds.html:362
- `.tabbar-indicator` moves (`transition: width .25s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — assets/designsystem/alkaa-ds.html:397
- `.ssc` moves (`transition: transform .15s, box-shadow .15s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — assets/designsystem/alkaa-ds.html:506
- `.fab` moves (`transition: box-shadow .2s, transform .15s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — assets/designsystem/alkaa-ds.html:650
- `.card` moves (`transition: box-shadow .2s,transform .15s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — assets/designsystem/alkaa-ds.html:733
- `.rb-dot` moves (`transition: transform .15s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — assets/designsystem/alkaa-ds.html:796
- `[data-theme="dark"] .ms-screens .phone` moves (`animation: phoneFadeUp 0.6s ease both`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — assets/designsystem/alkaa-ds.html:1670
- `.ms-screens .screen-block:nth-child(1) .phone` moves (`animation: phoneFadeUp 0.55s ease both`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — assets/designsystem/alkaa-ds.html:2361
- `.ms-screens .screen-block:nth-child(2) .phone` moves (`animation: phoneFadeUp 0.55s 0.1s ease both`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — assets/designsystem/alkaa-ds.html:2362
- `.ms-screens .screen-block:nth-child(3) .phone` moves (`animation: phoneFadeUp 0.55s 0.2s ease both`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — assets/designsystem/alkaa-ds.html:2363
- `.ms-screens .screen-block:nth-child(4) .phone` moves (`animation: phoneFadeUp 0.55s 0.3s ease both`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — assets/designsystem/alkaa-ds.html:2364
- `.sb-input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — assets/designsystem/alkaa-ds.html:426
- `.search-bar-input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — assets/designsystem/alkaa-ds.html:714
- `.tf-input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — assets/designsystem/alkaa-ds.html:778
- `[data-theme="dark"] .ms-screens .edit-title-input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — assets/designsystem/alkaa-ds.html:1381
- `[data-theme="dark"] .ms-screens .search-input-wrap .s-input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — assets/designsystem/alkaa-ds.html:1489
- `.ms-screens .s-input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — assets/designsystem/alkaa-ds.html:2266
- `.badge.green` sets color: #fff on background-color: #34C98C — 2.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — assets/designsystem/alkaa-ds.html:293
- `.tab-p-badge` sets color: #fff on background-color: #FFB4AB — 1.7:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — assets/designsystem/alkaa-ds.html:831
- `.ms-screens .task-chip` sets color: #4d6a8a on background-color: #1e3451 — 2.2:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — assets/designsystem/alkaa-ds.html:2089
What to do
- Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
AC7 · A11y enforcement
- No accessibility enforcement found — no accessibility linting at author time and no automated accessibility check in tests or CI. Add your UI toolkit's own accessibility assertion to the test suite (Flutter `meetsGuideline`, Espresso `AccessibilityChecks`, XCTest `performAccessibilityAudit`), then gate that test in the pipeline. What was searched, so you can tell an absence from a miss: the 1 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
What to do
- Enforce accessibility in the toolchain your project already uses: assert accessibility in your UI test suite with your toolkit's own matcher (Flutter `meetsGuideline`, Espresso `AccessibilityChecks`, XCTest `performAccessibilityAudit`), then gate that test in CI so a regression blocks the merge.
AX10 · Code composition
What to do
- The domain core is a small share of production code — check that business logic isn't leaking into the application/infrastructure layers (a thin domain is the anemic-domain smell).
AX3 · Project dependency cycles
AX4 · Dependency direction
DM12 · Ambient inputs in the domain
DM6 · Domain ↔ infrastructure boundary
DM9 · Scattered domain decisions
M1 · Documentation (README)
What to do
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P2 · Observability
- Only 3/5 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `desktop-app`, `ios-app`.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add spotbugs with find-sec-bugs (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 5 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:9
What to do
- Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
P6 · Release Hygiene
PF3 · Async & latency hygiene
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X20 · Mistyped argument guard
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
X30 · Support guard that admits what it rejects
X4 · Structured logging
X5 · Nullable reference types
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC2 · Forms & labels | 1.3.1, 3.3.2, 4.1.2 | Partial signal |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC4 · Keyboard semantics | 2.1.1, 2.4.3 | Partial signal |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
| AC7 · A11y enforcement | enforcement — no page criterion | Enforcement posture (process) |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 99% | Exemplary | Solid. |
| Architecture | 93% | Exemplary | Solid. |
| Maturity | 80% | Strong | Solid. |
| Readiness | 53% | Adequate — gated by D13, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 64% | Adequate — gated by D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 100% | Exemplary | Strongest area. |
| Accessibility | 35% | Weak — gated by AC4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Solid. |
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 66 check(s) not relevant to this codebase
- AC1 Text alternatives — No image/media element found in the parsed markup — AC1 not applicable here.
- AC5 ARIA correctness — No ARIA usage found in the parsed markup — AC5 not applicable here.
- AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Kotlin code is a Spring, JSR-330 or CDI singleton bean. No Swift request handler (a Vapor, Hummingbird, Kitura, Swifter or Perfect route handler, as a method or a registered closure) is declared, so no state is shared between request threads.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility (rendered) — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no data at rest for these controls to protect.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named column (email, first_name, date_of_birth, phone_number, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~4480 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
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; Kotlin, Swift, html not measured.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .kt, .swift, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — symbol resolution incomplete — navigability not assessed
- D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) 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.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- 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
- D9 Test Distribution — Test source is 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 its unit/integration/BDD/E2E split couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- DM1 Aggregate boundaries — no aggregates detected — aggregate-boundary check not applicable
- DM10 One transaction, one aggregate — no repository writes detected — no operation to judge against the one-aggregate rule
- DM11 Constructible invalid state — no entities detected — construction-time invariants not assessable
- DM2 Strongly-typed ids — no id-bearing domain types detected — strongly-typed-id adoption not assessable
- DM3 Integration-event coupling — no integration events detected — coupling check not applicable
- DM4 Rich vs anemic model — no data-bearing entities detected — rich-vs-anemic model not assessable
- DM5 Encapsulated state — no domain entities found — DM5 grades how entities protect their state, and this repository declares none
- DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
- DM8 Value-object opportunities — not scored — the deterministic rule found 0 candidate clump(s); its rows are withheld until it has a measured precision of 95 % (a sample of fewer than 10 rows cannot show one)
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and this analysis resolves a call's owner only where the receiver's type is written down in the source. Reported as guidance rather than measured
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM, Swift 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 — no coverage report found on disk — produce a coverage report in a standard format (JaCoCo XML — the Gradle `jacocoTestReport` task) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a pom.xml, Gradle or sbt build, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X2 Cancellation propagation — 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
- 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
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 60 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- <button> with no accessible text assets/designsystem/alkaa-ds.html:4029
- <button> with no accessible text assets/designsystem/alkaa-ds.html:4032
- <button> with no accessible text assets/designsystem/alkaa-ds.html:4035
- <button> with no accessible text assets/designsystem/alkaa-ds.html:4067
- <button> with no accessible text assets/designsystem/alkaa-ds.html:4073
- <button> with no accessible text assets/designsystem/alkaa-ds.html:4079
- <button> with no accessible text assets/designsystem/alkaa-ds.html:4100
- <button> with no accessible text assets/designsystem/alkaa-ds.html:4106
- <button> with no accessible text assets/designsystem/alkaa-ds.html:4112
- <button> with no accessible text assets/designsystem/alkaa-ds.html:4118
- <input> without a programmatic label assets/designsystem/alkaa-ds.html:4440
- <input> without a programmatic label assets/designsystem/alkaa-ds.html:4449
- <input> without a programmatic label assets/designsystem/alkaa-ds.html:4461
- <input> without a programmatic label assets/designsystem/alkaa-ds.html:4476
- <input> without a programmatic label assets/designsystem/alkaa-ds.html:4492
- <input> without a programmatic label assets/designsystem/alkaa-ds.html:4500
- <input> without a programmatic label assets/designsystem/alkaa-ds.html:4512
- <input> without a programmatic label assets/designsystem/alkaa-ds.html:4521
- <input> without a programmatic label assets/designsystem/alkaa-ds.html:5772
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Click handler on a non-interactive <div> assets/designsystem/alkaa-ds.html:2452
- REDACTED
Serious — 68 finding(s)
- Animation without a prefers-reduced-motion guard assets/designsystem/alkaa-ds.html:86
- Animation without a prefers-reduced-motion guard assets/designsystem/alkaa-ds.html:90
- Animation without a prefers-reduced-motion guard assets/designsystem/alkaa-ds.html:214
- Animation without a prefers-reduced-motion guard assets/designsystem/alkaa-ds.html:362
- Animation without a prefers-reduced-motion guard assets/designsystem/alkaa-ds.html:397
- Animation without a prefers-reduced-motion guard assets/designsystem/alkaa-ds.html:506
- Animation without a prefers-reduced-motion guard assets/designsystem/alkaa-ds.html:650
- Animation without a prefers-reduced-motion guard assets/designsystem/alkaa-ds.html:733
- Animation without a prefers-reduced-motion guard assets/designsystem/alkaa-ds.html:796
- Animation without a prefers-reduced-motion guard assets/designsystem/alkaa-ds.html:1670
- Animation without a prefers-reduced-motion guard assets/designsystem/alkaa-ds.html:2361
- Animation without a prefers-reduced-motion guard assets/designsystem/alkaa-ds.html:2362
- Animation without a prefers-reduced-motion guard assets/designsystem/alkaa-ds.html:2363
- Animation without a prefers-reduced-motion guard assets/designsystem/alkaa-ds.html:2364
- TodoComment libraries/permission/src/desktopMain/kotlin/com/escodro/permission/api/DesktopPermissionController.kt:9
- TodoComment libraries/permission/src/desktopMain/kotlin/com/escodro/permission/api/DesktopPermissionController.kt:14
- TodoComment features/navigation-api/src/androidMain/kotlin/com/escodro/navigationapi/deeplink/AndroidDeepLink.kt:22
- TodoComment features/alarm/src/desktopMain/kotlin/com/escodro/alarm/permission/DesktopAlarmPermission.kt:10
- TodoComment features/alarm/src/desktopMain/kotlin/com/escodro/alarm/permission/DesktopAlarmPermission.kt:15
- TodoComment features/alarm/src/desktopMain/kotlin/com/escodro/alarm/permission/DesktopAlarmPermission.kt:19
- TodoComment features/alarm/src/desktopMain/kotlin/com/escodro/alarm/notification/DesktopNotificationScheduler.kt:9
- TodoComment features/alarm/src/desktopMain/kotlin/com/escodro/alarm/notification/DesktopNotificationScheduler.kt:13
- TodoComment features/alarm/src/desktopMain/kotlin/com/escodro/alarm/notification/DesktopNotificationScheduler.kt:17
- TodoComment features/alarm/src/desktopMain/kotlin/com/escodro/alarm/notification/DesktopTaskNotification.kt:9
- TodoComment features/alarm/src/desktopMain/kotlin/com/escodro/alarm/notification/DesktopTaskNotification.kt:13
- TodoComment features/alarm/src/desktopMain/kotlin/com/escodro/alarm/notification/DesktopTaskNotification.kt:17
- TodoComment domain/src/commonMain/kotlin/com/escodro/domain/usecase/task/DeleteTask.kt:13
- Focus outline removed in CSS without a :focus replacement assets/designsystem/alkaa-ds.html:426
- Focus outline removed in CSS without a :focus replacement assets/designsystem/alkaa-ds.html:714
- Focus outline removed in CSS without a :focus replacement assets/designsystem/alkaa-ds.html:778
- Focus outline removed in CSS without a :focus replacement assets/designsystem/alkaa-ds.html:1381
- Focus outline removed in CSS without a :focus replacement assets/designsystem/alkaa-ds.html:1489
- Focus outline removed in CSS without a :focus replacement assets/designsystem/alkaa-ds.html:2266
- Unstable project :features:alarm
- Unstable project :features:home
- Unstable project :features:task
- Unstable project :shared
- Duplicated block (13 lines × 2) libraries/designsystem/src/commonMain/kotlin/com/escodro/designsystem/components/kuvio/chip/KuvioTaskChip.kt:139
- Duplicated block (13 lines × 2) libraries/designsystem/src/commonMain/kotlin/com/escodro/designsystem/components/kuvio/item/KuvioTaskItem.kt:277
- Duplicated block (13 lines × 2) libraries/permission/src/androidMain/kotlin/com/escodro/permission/api/AndroidPermissionController.kt:14
- Duplicated block (16 lines × 2) libraries/designsystem/src/commonMain/kotlin/com/escodro/designsystem/components/kuvio/item/KuvioTaskItem.kt:256
- Duplicated block (16 lines × 2) libraries/designsystem/src/commonMain/kotlin/com/escodro/designsystem/components/kuvio/item/KuvioTaskItem.kt:312
- Off the main sequence: :libraries:permission
- Off the main sequence: :libraries:designsystem
- Page without a main landmark assets/designsystem/alkaa-ds.html:2
- Low contrast colour pair in CSS (2.1:1) assets/designsystem/alkaa-ds.html:293
- Low contrast colour pair in CSS (1.7:1) assets/designsystem/alkaa-ds.html:831
- Low contrast colour pair in CSS (2.2:1) assets/designsystem/alkaa-ds.html:2089
- Accessibility enforcement below the top rung
- MethodTooLong: TypeKt.alkaaTypography libraries/designsystem/src/commonMain/kotlin/com/escodro/designsystem/theme/Type.kt:46
- Change coupling clique: Color.kt, Theme.kt, Type.kt libraries/designsystem/src/commonMain/kotlin/com/escodro/designsystem/theme/Color.kt
- Change coupling: AndroidNotificationScheduler.kt ↔ AndroidTaskNotification.kt features/alarm/src/androidMain/kotlin/com/escodro/alarm/notification/AndroidNotificationScheduler.kt:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Members sharing a duplicated core (4 members, 50+ identical tokens) libraries/designsystem/src/commonMain/kotlin/com/escodro/designsystem/components/kuvio/dialog/KuvioDialog.kt:449
- Duplicated block (39 lines × 2) libraries/designsystem/src/commonMain/kotlin/com/escodro/designsystem/components/kuvio/dialog/KuvioDialog.kt:363
- Duplicated block (31 lines × 2) libraries/designsystem/src/commonMain/kotlin/com/escodro/designsystem/components/kuvio/dialog/KuvioDialog.kt:255
- Duplicated block (25 lines × 2) libraries/designsystem/src/commonMain/kotlin/com/escodro/designsystem/components/kuvio/dialog/KuvioDialog.kt:195
- Duplicated block (23 lines × 2) libraries/designsystem/src/commonMain/kotlin/com/escodro/designsystem/components/kuvio/dialog/KuvioDialog.kt:465
- Duplicated block (16 lines × 4) libraries/designsystem/src/commonMain/kotlin/com/escodro/designsystem/components/kuvio/dialog/KuvioDialog.kt:454
- Duplicated block (15 lines × 2) libraries/designsystem/src/commonMain/kotlin/com/escodro/designsystem/components/kuvio/item/KuvioTaskItem.kt:236
- Duplicated block (14 lines × 2) libraries/designsystem/src/commonMain/kotlin/com/escodro/designsystem/components/kuvio/item/KuvioTaskListItem.kt:140
- Duplicated block (5 lines × 2) features/preference/src/commonMain/kotlin/com/escodro/preference/mapper/AppThemeOptionsMapper.kt:19
- Duplicated block (11 lines × 2) features/task/src/androidMain/kotlin/com/escodro/task/extension/LocalDateTimeExtensions.kt:12
Minor — 6 finding(s)
- No ADRs found
- REDACTED
- REDACTED
- No ADRs
- Logging is not universal
- No SAST REDACTED:9
Minor — 430 finding(s)
- Outdated (compile): app.cash.sqldelight:sqlite-3-18-dialect
- Outdated (compile): app.cash.sqldelight:dialect-api
- Outdated (compile): com.squareup:kotlinpoet
- Outdated (compile): com.squareup:kotlinpoet-jvm
- Outdated (compile): app.cash.sqldelight:compiler-env
- Outdated (compile): org.jetbrains.kotlin:kotlin-stdlib
- Outdated (compile): org.jetbrains:annotations
- Outdated (compile): app.cash.sqldelight:migration-env
- Outdated (compile): org.jetbrains.kotlin:kotlin-stdlib-common
- Outdated (compile): io.insert-koin:koin-core
- Outdated (compile): app.cash.sqldelight:runtime
- Outdated (compile): com.google.guava:guava
- Outdated (compile): com.google.guava:failureaccess
- Outdated (compile): org.checkerframework:checker-qual
- Outdated (compile): com.google.errorprone:error_prone_annotations
- Outdated (compile): com.google.j2objc:j2objc-annotations
- Outdated (compile): net.java.dev.jna:jna-platform
- Outdated (compile): net.java.dev.jna:jna
- Outdated (compile): org.jetbrains.kotlin:kotlin-stdlib-jdk8
- Outdated (compile): org.jetbrains.kotlin:kotlin-stdlib-jdk7
- Outdated (compile): org.jetbrains.kotlinx:atomicfu
- Outdated (compile): com.google.protobuf:protobuf-java
- Outdated (compile): com.google.code.gson:gson
- Outdated (compile): com.google.jimfs:jimfs
- Outdated (compile): org.apache.commons:commons-compress
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-562b3c4af587402f959c8d69c6486c53/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-562b3c4af587402f959c8d69c6486c53/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 . | 34 | 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) — `features/task/src/commonMain/kotlin/com/escodro/task/presentation/detail/main/TaskDetail.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 | — |