Executive summary
T8RIN/CookHelper falls short of our standard for a preview release because the project has no automated tests and we found no working pipeline that builds or tests changes to the code. It scores 36 out of 100 and is rated Weak, and one of its two critical findings is a leaked password or key.
Production Readiness, at 19, is the weakest lens and counts most in the score. The best first step for the work it takes is recording design decisions, worth about 6 points. Adding automated tests would lift Production Readiness itself, worth about 15 points. Raising Production Readiness to 62 would lift the score to about 48.
One password or key is open to anyone who can read the repository. The project has no automated tests, so a change can break it without warning. Adding automated tests and replacing the exposed password or key would close both risks.
The product code is 22,790 lines, about €22,000 to rebuild.
If Production Readiness rose from 19 to 62, the lowest score rated Strong, the score would rise from 36 to about 48.
Fixed since the last survey: 2 findings
- Change Coupling · Change coupling: CategorySelectionDialog.kt ↔ PickProductsWithMeasuresDialog.kt app/src/main/java/ru/tech/cookhelper/presentation/recipe_post_creation/components/CategorySelectionDialog.kt
- Change Coupling · Change coupling: PostItem.kt ↔ Screen.kt app/src/main/java/ru/tech/cookhelper/presentation/profile/components/PostItem.kt
Rebuild cost: about €22,000 · Estimate
| Cost to rebuild | €7,400 to €37,000, for 124 to 392 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 36. 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 | Medium: 22,790 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 core | 2 data.remote.utils | 3 data.utils | 4 domain.model | 5 presentation.settings.components | 6 presentation.ui.utils.event | 7 data.local.database | 8 data.remote.dto | 9 data.remote.web_socket | 10 domain.repository | 11 presentation.restore_password.viewModel | 12 presentation.ui.utils.compose | 13 data.remote.api.auth | 14 data.remote.api.chat | 15 data.remote.api.ingredients | 16 data.remote.web_socket.feed | 17 data.remote.web_socket.message | 18 data.remote.web_socket.user | 19 domain.use_case.cache_user | 20 domain.use_case.get_user | 21 presentation.ui.utils.navigation.Screen | 22 presentation.ui.widgets | 23 core.di | 24 data.repository | 25 presentation.app.viewModel | 26 presentation.chat.viewModel | 27 presentation.chat_list.viewModel | 28 presentation.confirm_email.viewModel | 29 presentation.login_screen.viewModel | 30 presentation.post_creation.viewModel | 31 presentation.registration_screen.viewModel | 32 presentation.topic_creation.viewModel | 33 presentation.ui.utils.navigation | 34 presentation.app.components | 35 presentation.edit_profile.viewModel | 36 presentation.feed_screen.viewModel | 37 presentation.fridge_screen.viewModel | 38 presentation.matched_recipes.viewModel | 39 presentation.pick_products.viewModel | 40 presentation.profile.viewModel |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 core | ||||||||||||||||||||||||||||||||||||||||
| 2 data.remote.utils | ||||||||||||||||||||||||||||||||||||||||
| 3 data.utils | ||||||||||||||||||||||||||||||||||||||||
| 4 domain.model | ||||||||||||||||||||||||||||||||||||||||
| 5 presentation.settings.components | ||||||||||||||||||||||||||||||||||||||||
| 6 presentation.ui.utils.event | ||||||||||||||||||||||||||||||||||||||||
| 7 data.local.database | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 8 data.remote.dto | 8 | 23 | ||||||||||||||||||||||||||||||||||||||
| 9 data.remote.web_socket | 1 | |||||||||||||||||||||||||||||||||||||||
| 10 domain.repository | 3 | 11 | ||||||||||||||||||||||||||||||||||||||
| 11 presentation.restore_password.viewModel | 1 | |||||||||||||||||||||||||||||||||||||||
| 12 presentation.ui.utils.compose | 1 | |||||||||||||||||||||||||||||||||||||||
| 13 data.remote.api.auth | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 14 data.remote.api.chat | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 15 data.remote.api.ingredients | 1 | 3 | ||||||||||||||||||||||||||||||||||||||
| 16 data.remote.web_socket.feed | 1 | 2 | 4 | |||||||||||||||||||||||||||||||||||||
| 17 data.remote.web_socket.message | 1 | 2 | 4 | |||||||||||||||||||||||||||||||||||||
| 18 data.remote.web_socket.user | 2 | 1 | 2 | 4 | ||||||||||||||||||||||||||||||||||||
| 19 domain.use_case.cache_user | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 20 domain.use_case.get_user | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 21 presentation.ui.utils.navigation.Screen | 4 | 1 | 20 | |||||||||||||||||||||||||||||||||||||
| 22 presentation.ui.widgets | 1 | |||||||||||||||||||||||||||||||||||||||
| 23 core.di | 3 | 3 | 4 | 2 | 2 | 2 | 2 | 2 | 2 | |||||||||||||||||||||||||||||||
| 24 data.repository | 3 | 1 | 11 | 4 | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||
| 25 presentation.app.viewModel | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 26 presentation.chat.viewModel | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 27 presentation.chat_list.viewModel | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 28 presentation.confirm_email.viewModel | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 29 presentation.login_screen.viewModel | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 30 presentation.post_creation.viewModel | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 31 presentation.registration_screen.viewModel | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 32 presentation.topic_creation.viewModel | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 33 presentation.ui.utils.navigation | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 34 presentation.app.components | 1 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 35 presentation.edit_profile.viewModel | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 36 presentation.feed_screen.viewModel | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 37 presentation.fridge_screen.viewModel | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 38 presentation.matched_recipes.viewModel | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 39 presentation.pick_products.viewModel | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 40 presentation.profile.viewModel | 1 | 1 |
7→3 data.local.database uses data.utils✕
- Connections
- 1 pair of types, where a type in data.local.database uses a type in data.utils.
- The types involved
ru.tech.cookhelper.data.local.database.TypeConverters→ru.tech.cookhelper.data.utils.JsonParser
- Direction
- data.local.database uses data.utils, so a change to data.utils can break data.local.database, while a change to data.local.database can't break data.utils.
- Position
- Below the diagonal: data.local.database uses a module listed above it, which is the healthy direction.
7→4 data.local.database uses domain.model✕
- Connections
- 2 pairs of types, where a type in data.local.database uses a type in domain.model.
- The types involved
ru.tech.cookhelper.data.local.database.TypeConverters→ru.tech.cookhelper.domain.model.FileDataru.tech.cookhelper.data.local.database.TypeConverters→ru.tech.cookhelper.domain.model.Product
- Direction
- data.local.database uses domain.model, so a change to domain.model can break data.local.database, while a change to data.local.database can't break domain.model.
- Position
- Below the diagonal: data.local.database uses a module listed above it, which is the healthy direction.
8→2 data.remote.dto uses data.remote.utils✕
- Connections
- 8 pairs of types, where a type in data.remote.dto uses a type in data.remote.utils.
- The types involved
ru.tech.cookhelper.data.remote.dto.ChatDto→ru.tech.cookhelper.data.remote.utils.Dtoru.tech.cookhelper.data.remote.dto.MatchedRecipeDto→ru.tech.cookhelper.data.remote.utils.Dtoru.tech.cookhelper.data.remote.dto.MessageDto→ru.tech.cookhelper.data.remote.utils.Dtoru.tech.cookhelper.data.remote.dto.PostDto→ru.tech.cookhelper.data.remote.utils.Dtoru.tech.cookhelper.data.remote.dto.ProductDto→ru.tech.cookhelper.data.remote.utils.Dtoru.tech.cookhelper.data.remote.dto.RecipeDto→ru.tech.cookhelper.data.remote.utils.Dtoru.tech.cookhelper.data.remote.dto.TopicDto→ru.tech.cookhelper.data.remote.utils.Dtoru.tech.cookhelper.data.remote.dto.UserDto→ru.tech.cookhelper.data.remote.utils.Dto
- Direction
- data.remote.dto uses data.remote.utils, so a change to data.remote.utils can break data.remote.dto, while a change to data.remote.dto can't break data.remote.utils.
- Position
- Below the diagonal: data.remote.dto uses a module listed above it, which is the healthy direction.
8→4 data.remote.dto uses domain.model✕
- Connections
- 23 pairs of types, where a type in data.remote.dto uses a type in domain.model.
- The types involved
ru.tech.cookhelper.data.remote.dto.ChatDto→ru.tech.cookhelper.domain.model.Chatru.tech.cookhelper.data.remote.dto.ChatDto→ru.tech.cookhelper.domain.model.FileDataru.tech.cookhelper.data.remote.dto.ChatDto→ru.tech.cookhelper.domain.model.Messageru.tech.cookhelper.data.remote.dto.MatchedRecipeDto→ru.tech.cookhelper.domain.model.MatchedReciperu.tech.cookhelper.data.remote.dto.MatchedRecipeDto→ru.tech.cookhelper.domain.model.Reciperu.tech.cookhelper.data.remote.dto.MessageDto→ru.tech.cookhelper.domain.model.FileDataru.tech.cookhelper.data.remote.dto.MessageDto→ru.tech.cookhelper.domain.model.Messageru.tech.cookhelper.data.remote.dto.MessageDto→ru.tech.cookhelper.domain.model.Userru.tech.cookhelper.data.remote.dto.PostDto→ru.tech.cookhelper.domain.model.FileDataru.tech.cookhelper.data.remote.dto.PostDto→ru.tech.cookhelper.domain.model.Postru.tech.cookhelper.data.remote.dto.PostDto→ru.tech.cookhelper.domain.model.Userru.tech.cookhelper.data.remote.dto.ProductDto→ru.tech.cookhelper.domain.model.Productru.tech.cookhelper.data.remote.dto.RecipeDto→ru.tech.cookhelper.domain.model.FileDataru.tech.cookhelper.data.remote.dto.RecipeDto→ru.tech.cookhelper.domain.model.Productru.tech.cookhelper.data.remote.dto.RecipeDto→ru.tech.cookhelper.domain.model.Reciperu.tech.cookhelper.data.remote.dto.RecipeDto→ru.tech.cookhelper.domain.model.Userru.tech.cookhelper.data.remote.dto.TopicDto→ru.tech.cookhelper.domain.model.FileDataru.tech.cookhelper.data.remote.dto.TopicDto→ru.tech.cookhelper.domain.model.Replyru.tech.cookhelper.data.remote.dto.TopicDto→ru.tech.cookhelper.domain.model.Topicru.tech.cookhelper.data.remote.dto.TopicDto→ru.tech.cookhelper.domain.model.Userru.tech.cookhelper.data.remote.dto.UserDto→ru.tech.cookhelper.domain.model.FileDataru.tech.cookhelper.data.remote.dto.UserDto→ru.tech.cookhelper.domain.model.Productru.tech.cookhelper.data.remote.dto.UserDto→ru.tech.cookhelper.domain.model.User
- Direction
- data.remote.dto uses domain.model, so a change to domain.model can break data.remote.dto, while a change to data.remote.dto can't break domain.model.
- Position
- Below the diagonal: data.remote.dto uses a module listed above it, which is the healthy direction.
9→3 data.remote.web_socket uses data.utils✕
- Connections
- 1 pair of types, where a type in data.remote.web_socket uses a type in data.utils.
- The types involved
ru.tech.cookhelper.data.remote.web_socket.WebSocketClient→ru.tech.cookhelper.data.utils.JsonParser
- Direction
- data.remote.web_socket uses data.utils, so a change to data.utils can break data.remote.web_socket, while a change to data.remote.web_socket can't break data.utils.
- Position
- Below the diagonal: data.remote.web_socket uses a module listed above it, which is the healthy direction.
10→1 domain.repository uses core✕
- Connections
- 3 pairs of types, where a type in domain.repository uses a type in core.
- The types involved
ru.tech.cookhelper.domain.repository.FridgeRepository→ru.tech.cookhelper.core.Actionru.tech.cookhelper.domain.repository.MessageRepository→ru.tech.cookhelper.core.Actionru.tech.cookhelper.domain.repository.UserRepository→ru.tech.cookhelper.core.Action
- Direction
- domain.repository uses core, so a change to core can break domain.repository, while a change to domain.repository can't break core.
- Position
- Below the diagonal: domain.repository uses a module listed above it, which is the healthy direction.
10→4 domain.repository uses domain.model✕
- Connections
- 11 pairs of types, where a type in domain.repository uses a type in domain.model.
- The types involved
ru.tech.cookhelper.domain.repository.FridgeRepository→ru.tech.cookhelper.domain.model.MatchedReciperu.tech.cookhelper.domain.repository.FridgeRepository→ru.tech.cookhelper.domain.model.Productru.tech.cookhelper.domain.repository.FridgeRepository→ru.tech.cookhelper.domain.model.Userru.tech.cookhelper.domain.repository.MessageRepository→ru.tech.cookhelper.domain.model.Chatru.tech.cookhelper.domain.repository.MessageRepository→ru.tech.cookhelper.domain.model.FormMessageru.tech.cookhelper.domain.repository.MessageRepository→ru.tech.cookhelper.domain.model.Messageru.tech.cookhelper.domain.repository.SettingsRepository→ru.tech.cookhelper.domain.model.Settingru.tech.cookhelper.domain.repository.UserRepository→ru.tech.cookhelper.domain.model.Postru.tech.cookhelper.domain.repository.UserRepository→ru.tech.cookhelper.domain.model.Reciperu.tech.cookhelper.domain.repository.UserRepository→ru.tech.cookhelper.domain.model.Topicru.tech.cookhelper.domain.repository.UserRepository→ru.tech.cookhelper.domain.model.User
- 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.
11→6 presentation.restore_password.viewModel uses presentation.ui.utils.event✕
- Connections
- 1 pair of types, where a type in presentation.restore_password.viewModel uses a type in presentation.ui.utils.event.
- The types involved
ru.tech.cookhelper.presentation.restore_password.viewModel.RestorePasswordViewModel→ru.tech.cookhelper.presentation.ui.utils.event.ViewModelEvents
- Direction
- presentation.restore_password.viewModel uses presentation.ui.utils.event, so a change to presentation.ui.utils.event can break presentation.restore_password.viewModel, while a change to presentation.restore_password.viewModel can't break presentation.ui.utils.event.
- Position
- Below the diagonal: presentation.restore_password.viewModel uses a module listed above it, which is the healthy direction.
12→34 presentation.ui.utils.compose uses presentation.app.components part of a loop✕
- Connections
- 1 pair of types, where a type in presentation.ui.utils.compose uses a type in presentation.app.components.
- The types involved
ru.tech.cookhelper.presentation.ui.utils.compose.ToastUtilsKt→ru.tech.cookhelper.presentation.app.components.ToastDuration
- Direction
- presentation.ui.utils.compose uses presentation.app.components, so a change to presentation.app.components can break presentation.ui.utils.compose, while a change to presentation.ui.utils.compose can't break presentation.app.components.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→2 data.remote.api.auth uses data.remote.utils✕
- Connections
- 1 pair of types, where a type in data.remote.api.auth uses a type in data.remote.utils.
- The types involved
ru.tech.cookhelper.data.remote.api.auth.AuthService→ru.tech.cookhelper.data.remote.utils.Response
- Direction
- data.remote.api.auth uses data.remote.utils, so a change to data.remote.utils can break data.remote.api.auth, while a change to data.remote.api.auth can't break data.remote.utils.
- Position
- Below the diagonal: data.remote.api.auth uses a module listed above it, which is the healthy direction.
13→8 data.remote.api.auth uses data.remote.dto✕
- Connections
- 1 pair of types, where a type in data.remote.api.auth uses a type in data.remote.dto.
- The types involved
ru.tech.cookhelper.data.remote.api.auth.AuthService→ru.tech.cookhelper.data.remote.dto.UserDto
- Direction
- data.remote.api.auth uses data.remote.dto, so a change to data.remote.dto can break data.remote.api.auth, while a change to data.remote.api.auth can't break data.remote.dto.
- Position
- Below the diagonal: data.remote.api.auth uses a module listed above it, which is the healthy direction.
14→2 data.remote.api.chat uses data.remote.utils✕
- Connections
- 1 pair of types, where a type in data.remote.api.chat uses a type in data.remote.utils.
- The types involved
ru.tech.cookhelper.data.remote.api.chat.ChatApi→ru.tech.cookhelper.data.remote.utils.Response
- Direction
- data.remote.api.chat uses data.remote.utils, so a change to data.remote.utils can break data.remote.api.chat, while a change to data.remote.api.chat can't break data.remote.utils.
- Position
- Below the diagonal: data.remote.api.chat uses a module listed above it, which is the healthy direction.
14→8 data.remote.api.chat uses data.remote.dto✕
- Connections
- 1 pair of types, where a type in data.remote.api.chat uses a type in data.remote.dto.
- The types involved
ru.tech.cookhelper.data.remote.api.chat.ChatApi→ru.tech.cookhelper.data.remote.dto.ChatDto
- Direction
- data.remote.api.chat uses data.remote.dto, so a change to data.remote.dto can break data.remote.api.chat, while a change to data.remote.api.chat can't break data.remote.dto.
- Position
- Below the diagonal: data.remote.api.chat uses a module listed above it, which is the healthy direction.
15→2 data.remote.api.ingredients uses data.remote.utils✕
- Connections
- 1 pair of types, where a type in data.remote.api.ingredients uses a type in data.remote.utils.
- The types involved
ru.tech.cookhelper.data.remote.api.ingredients.FridgeApi→ru.tech.cookhelper.data.remote.utils.Response
- Direction
- data.remote.api.ingredients uses data.remote.utils, so a change to data.remote.utils can break data.remote.api.ingredients, while a change to data.remote.api.ingredients can't break data.remote.utils.
- Position
- Below the diagonal: data.remote.api.ingredients uses a module listed above it, which is the healthy direction.
15→8 data.remote.api.ingredients uses data.remote.dto✕
- Connections
- 3 pairs of types, where a type in data.remote.api.ingredients uses a type in data.remote.dto.
- The types involved
ru.tech.cookhelper.data.remote.api.ingredients.FridgeApi→ru.tech.cookhelper.data.remote.dto.MatchedRecipeDtoru.tech.cookhelper.data.remote.api.ingredients.FridgeApi→ru.tech.cookhelper.data.remote.dto.ProductDtoru.tech.cookhelper.data.remote.api.ingredients.FridgeApi→ru.tech.cookhelper.data.remote.dto.UserDto
- Direction
- data.remote.api.ingredients uses data.remote.dto, so a change to data.remote.dto can break data.remote.api.ingredients, while a change to data.remote.api.ingredients can't break data.remote.dto.
- Position
- Below the diagonal: data.remote.api.ingredients uses a module listed above it, which is the healthy direction.
16→3 data.remote.web_socket.feed uses data.utils✕
- Connections
- 1 pair of types, where a type in data.remote.web_socket.feed uses a type in data.utils.
- The types involved
ru.tech.cookhelper.data.remote.web_socket.feed.FeedServiceImpl→ru.tech.cookhelper.data.utils.JsonParser
- Direction
- data.remote.web_socket.feed uses data.utils, so a change to data.utils can break data.remote.web_socket.feed, while a change to data.remote.web_socket.feed can't break data.utils.
- Position
- Below the diagonal: data.remote.web_socket.feed uses a module listed above it, which is the healthy direction.
16→8 data.remote.web_socket.feed uses data.remote.dto✕
- Connections
- 2 pairs of types, where a type in data.remote.web_socket.feed uses a type in data.remote.dto.
- The types involved
ru.tech.cookhelper.data.remote.web_socket.feed.FeedService→ru.tech.cookhelper.data.remote.dto.RecipeDtoru.tech.cookhelper.data.remote.web_socket.feed.FeedServiceImpl→ru.tech.cookhelper.data.remote.dto.RecipeDto
- Direction
- data.remote.web_socket.feed uses data.remote.dto, so a change to data.remote.dto can break data.remote.web_socket.feed, while a change to data.remote.web_socket.feed can't break data.remote.dto.
- Position
- Below the diagonal: data.remote.web_socket.feed uses a module listed above it, which is the healthy direction.
16→9 data.remote.web_socket.feed uses data.remote.web_socket✕
- Connections
- 4 pairs of types, where a type in data.remote.web_socket.feed uses a type in data.remote.web_socket.
- The types involved
ru.tech.cookhelper.data.remote.web_socket.feed.FeedService→ru.tech.cookhelper.data.remote.web_socket.Serviceru.tech.cookhelper.data.remote.web_socket.feed.FeedService→ru.tech.cookhelper.data.remote.web_socket.WebSocketStateru.tech.cookhelper.data.remote.web_socket.feed.FeedServiceImpl→ru.tech.cookhelper.data.remote.web_socket.WebSocketClientru.tech.cookhelper.data.remote.web_socket.feed.FeedServiceImpl→ru.tech.cookhelper.data.remote.web_socket.WebSocketState
- Direction
- data.remote.web_socket.feed uses data.remote.web_socket, so a change to data.remote.web_socket can break data.remote.web_socket.feed, while a change to data.remote.web_socket.feed can't break data.remote.web_socket.
- Position
- Below the diagonal: data.remote.web_socket.feed uses a module listed above it, which is the healthy direction.
17→3 data.remote.web_socket.message uses data.utils✕
- Connections
- 1 pair of types, where a type in data.remote.web_socket.message uses a type in data.utils.
- The types involved
ru.tech.cookhelper.data.remote.web_socket.message.MessageServiceImpl→ru.tech.cookhelper.data.utils.JsonParser
- Direction
- data.remote.web_socket.message uses data.utils, so a change to data.utils can break data.remote.web_socket.message, while a change to data.remote.web_socket.message can't break data.utils.
- Position
- Below the diagonal: data.remote.web_socket.message uses a module listed above it, which is the healthy direction.
17→8 data.remote.web_socket.message uses data.remote.dto✕
- Connections
- 2 pairs of types, where a type in data.remote.web_socket.message uses a type in data.remote.dto.
- The types involved
ru.tech.cookhelper.data.remote.web_socket.message.MessageService→ru.tech.cookhelper.data.remote.dto.MessageDtoru.tech.cookhelper.data.remote.web_socket.message.MessageServiceImpl→ru.tech.cookhelper.data.remote.dto.MessageDto
- Direction
- data.remote.web_socket.message uses data.remote.dto, so a change to data.remote.dto can break data.remote.web_socket.message, while a change to data.remote.web_socket.message can't break data.remote.dto.
- Position
- Below the diagonal: data.remote.web_socket.message uses a module listed above it, which is the healthy direction.
17→9 data.remote.web_socket.message uses data.remote.web_socket✕
- Connections
- 4 pairs of types, where a type in data.remote.web_socket.message uses a type in data.remote.web_socket.
- The types involved
ru.tech.cookhelper.data.remote.web_socket.message.MessageService→ru.tech.cookhelper.data.remote.web_socket.Serviceru.tech.cookhelper.data.remote.web_socket.message.MessageService→ru.tech.cookhelper.data.remote.web_socket.WebSocketStateru.tech.cookhelper.data.remote.web_socket.message.MessageServiceImpl→ru.tech.cookhelper.data.remote.web_socket.WebSocketClientru.tech.cookhelper.data.remote.web_socket.message.MessageServiceImpl→ru.tech.cookhelper.data.remote.web_socket.WebSocketState
- Direction
- data.remote.web_socket.message uses data.remote.web_socket, so a change to data.remote.web_socket can break data.remote.web_socket.message, while a change to data.remote.web_socket.message can't break data.remote.web_socket.
- Position
- Below the diagonal: data.remote.web_socket.message uses a module listed above it, which is the healthy direction.
18→2 data.remote.web_socket.user uses data.remote.utils✕
- Connections
- 2 pairs of types, where a type in data.remote.web_socket.user uses a type in data.remote.utils.
- The types involved
ru.tech.cookhelper.data.remote.web_socket.user.UserService→ru.tech.cookhelper.data.remote.utils.Responseru.tech.cookhelper.data.remote.web_socket.user.UserServiceImpl→ru.tech.cookhelper.data.remote.utils.Response
- Direction
- data.remote.web_socket.user uses data.remote.utils, so a change to data.remote.utils can break data.remote.web_socket.user, while a change to data.remote.web_socket.user can't break data.remote.utils.
- Position
- Below the diagonal: data.remote.web_socket.user uses a module listed above it, which is the healthy direction.
18→3 data.remote.web_socket.user uses data.utils✕
- Connections
- 1 pair of types, where a type in data.remote.web_socket.user uses a type in data.utils.
- The types involved
ru.tech.cookhelper.data.remote.web_socket.user.UserServiceImpl→ru.tech.cookhelper.data.utils.JsonParser
- Direction
- data.remote.web_socket.user uses data.utils, so a change to data.utils can break data.remote.web_socket.user, while a change to data.remote.web_socket.user can't break data.utils.
- Position
- Below the diagonal: data.remote.web_socket.user uses a module listed above it, which is the healthy direction.
18→8 data.remote.web_socket.user uses data.remote.dto✕
- Connections
- 2 pairs of types, where a type in data.remote.web_socket.user uses a type in data.remote.dto.
- The types involved
ru.tech.cookhelper.data.remote.web_socket.user.UserService→ru.tech.cookhelper.data.remote.dto.UserDtoru.tech.cookhelper.data.remote.web_socket.user.UserServiceImpl→ru.tech.cookhelper.data.remote.dto.UserDto
- Direction
- data.remote.web_socket.user uses data.remote.dto, so a change to data.remote.dto can break data.remote.web_socket.user, while a change to data.remote.web_socket.user can't break data.remote.dto.
- Position
- Below the diagonal: data.remote.web_socket.user uses a module listed above it, which is the healthy direction.
18→9 data.remote.web_socket.user uses data.remote.web_socket✕
- Connections
- 4 pairs of types, where a type in data.remote.web_socket.user uses a type in data.remote.web_socket.
- The types involved
ru.tech.cookhelper.data.remote.web_socket.user.UserService→ru.tech.cookhelper.data.remote.web_socket.Serviceru.tech.cookhelper.data.remote.web_socket.user.UserService→ru.tech.cookhelper.data.remote.web_socket.WebSocketStateru.tech.cookhelper.data.remote.web_socket.user.UserServiceImpl→ru.tech.cookhelper.data.remote.web_socket.WebSocketClientru.tech.cookhelper.data.remote.web_socket.user.UserServiceImpl→ru.tech.cookhelper.data.remote.web_socket.WebSocketState
- Direction
- data.remote.web_socket.user uses data.remote.web_socket, so a change to data.remote.web_socket can break data.remote.web_socket.user, while a change to data.remote.web_socket.user can't break data.remote.web_socket.
- Position
- Below the diagonal: data.remote.web_socket.user uses a module listed above it, which is the healthy direction.
19→4 domain.use_case.cache_user uses domain.model✕
- Connections
- 1 pair of types, where a type in domain.use_case.cache_user uses a type in domain.model.
- The types involved
ru.tech.cookhelper.domain.use_case.cache_user.CacheUserUseCase→ru.tech.cookhelper.domain.model.User
- Direction
- domain.use_case.cache_user uses domain.model, so a change to domain.model can break domain.use_case.cache_user, while a change to domain.use_case.cache_user can't break domain.model.
- Position
- Below the diagonal: domain.use_case.cache_user uses a module listed above it, which is the healthy direction.
19→10 domain.use_case.cache_user uses domain.repository✕
- Connections
- 1 pair of types, where a type in domain.use_case.cache_user uses a type in domain.repository.
- The types involved
ru.tech.cookhelper.domain.use_case.cache_user.CacheUserUseCase→ru.tech.cookhelper.domain.repository.UserRepository
- Direction
- domain.use_case.cache_user uses domain.repository, so a change to domain.repository can break domain.use_case.cache_user, while a change to domain.use_case.cache_user can't break domain.repository.
- Position
- Below the diagonal: domain.use_case.cache_user uses a module listed above it, which is the healthy direction.
20→4 domain.use_case.get_user uses domain.model✕
- Connections
- 1 pair of types, where a type in domain.use_case.get_user uses a type in domain.model.
- The types involved
ru.tech.cookhelper.domain.use_case.get_user.GetUserUseCase→ru.tech.cookhelper.domain.model.User
- Direction
- domain.use_case.get_user uses domain.model, so a change to domain.model can break domain.use_case.get_user, while a change to domain.use_case.get_user can't break domain.model.
- Position
- Below the diagonal: domain.use_case.get_user uses a module listed above it, which is the healthy direction.
20→10 domain.use_case.get_user uses domain.repository✕
- Connections
- 1 pair of types, where a type in domain.use_case.get_user uses a type in domain.repository.
- The types involved
ru.tech.cookhelper.domain.use_case.get_user.GetUserUseCase→ru.tech.cookhelper.domain.repository.UserRepository
- Direction
- domain.use_case.get_user uses domain.repository, so a change to domain.repository can break domain.use_case.get_user, while a change to domain.use_case.get_user can't break domain.repository.
- Position
- Below the diagonal: domain.use_case.get_user uses a module listed above it, which is the healthy direction.
21→4 presentation.ui.utils.navigation.Screen uses domain.model✕
- Connections
- 4 pairs of types, where a type in presentation.ui.utils.navigation.Screen uses a type in domain.model.
- The types involved
ru.tech.cookhelper.presentation.ui.utils.navigation.Screen.AllImages→ru.tech.cookhelper.domain.model.FileDataru.tech.cookhelper.presentation.ui.utils.navigation.Screen.FullscreenImagePager→ru.tech.cookhelper.domain.model.FileDataru.tech.cookhelper.presentation.ui.utils.navigation.Screen.PostCreation→ru.tech.cookhelper.domain.model.Postru.tech.cookhelper.presentation.ui.utils.navigation.Screen.RecipeDetails→ru.tech.cookhelper.domain.model.Recipe
- Direction
- presentation.ui.utils.navigation.Screen uses domain.model, so a change to domain.model can break presentation.ui.utils.navigation.Screen, while a change to presentation.ui.utils.navigation.Screen can't break domain.model.
- Position
- Below the diagonal: presentation.ui.utils.navigation.Screen uses a module listed above it, which is the healthy direction.
21→12 presentation.ui.utils.navigation.Screen uses presentation.ui.utils.compose✕
- Connections
- 1 pair of types, where a type in presentation.ui.utils.navigation.Screen uses a type in presentation.ui.utils.compose.
- The types involved
ru.tech.cookhelper.presentation.ui.utils.navigation.Screen.Home→ru.tech.cookhelper.presentation.ui.utils.compose.UIText
- Direction
- presentation.ui.utils.navigation.Screen uses presentation.ui.utils.compose, so a change to presentation.ui.utils.compose can break presentation.ui.utils.navigation.Screen, while a change to presentation.ui.utils.navigation.Screen can't break presentation.ui.utils.compose.
- Position
- Below the diagonal: presentation.ui.utils.navigation.Screen uses a module listed above it, which is the healthy direction.
21→33 presentation.ui.utils.navigation.Screen uses presentation.ui.utils.navigation part of a loop✕
- Connections
- 20 pairs of types, where a type in presentation.ui.utils.navigation.Screen uses a type in presentation.ui.utils.navigation.
- The types involved
ru.tech.cookhelper.presentation.ui.utils.navigation.Screen.AllImages→ru.tech.cookhelper.presentation.ui.utils.navigation.Screenru.tech.cookhelper.presentation.ui.utils.navigation.Screen.Authentication→ru.tech.cookhelper.presentation.ui.utils.navigation.Screenru.tech.cookhelper.presentation.ui.utils.navigation.Screen.BlockList→ru.tech.cookhelper.presentation.ui.utils.navigation.Screenru.tech.cookhelper.presentation.ui.utils.navigation.Screen.Buttons→ru.tech.cookhelper.presentation.ui.utils.navigation.Screenru.tech.cookhelper.presentation.ui.utils.navigation.Screen.Cart→ru.tech.cookhelper.presentation.ui.utils.navigation.Screenru.tech.cookhelper.presentation.ui.utils.navigation.Screen.Chat→ru.tech.cookhelper.presentation.ui.utils.navigation.Screenru.tech.cookhelper.presentation.ui.utils.navigation.Screen.ChatList→ru.tech.cookhelper.presentation.ui.utils.navigation.Screenru.tech.cookhelper.presentation.ui.utils.navigation.Screen.EditProfile→ru.tech.cookhelper.presentation.ui.utils.navigation.Screenru.tech.cookhelper.presentation.ui.utils.navigation.Screen.Favourites→ru.tech.cookhelper.presentation.ui.utils.navigation.Screenru.tech.cookhelper.presentation.ui.utils.navigation.Screen.ForumDiscussion→ru.tech.cookhelper.presentation.ui.utils.navigation.Screenru.tech.cookhelper.presentation.ui.utils.navigation.Screen.FullscreenImagePager→ru.tech.cookhelper.presentation.ui.utils.navigation.Screenru.tech.cookhelper.presentation.ui.utils.navigation.Screen.Home→ru.tech.cookhelper.presentation.ui.utils.navigation.Screenru.tech.cookhelper.presentation.ui.utils.navigation.Screen.MatchedRecipes→ru.tech.cookhelper.presentation.ui.utils.navigation.Screenru.tech.cookhelper.presentation.ui.utils.navigation.Screen.PostCreation→ru.tech.cookhelper.presentation.ui.utils.navigation.Screenru.tech.cookhelper.presentation.ui.utils.navigation.Screen.Profile→ru.tech.cookhelper.presentation.ui.utils.navigation.Screenru.tech.cookhelper.presentation.ui.utils.navigation.Screen.RecipeDetails→ru.tech.cookhelper.presentation.ui.utils.navigation.Screenru.tech.cookhelper.presentation.ui.utils.navigation.Screen.RecipePostCreation→ru.tech.cookhelper.presentation.ui.utils.navigation.Screenru.tech.cookhelper.presentation.ui.utils.navigation.Screen.Recipes→ru.tech.cookhelper.presentation.ui.utils.navigation.Screenru.tech.cookhelper.presentation.ui.utils.navigation.Screen.Settings→ru.tech.cookhelper.presentation.ui.utils.navigation.Screenru.tech.cookhelper.presentation.ui.utils.navigation.Screen.TopicCreation→ru.tech.cookhelper.presentation.ui.utils.navigation.Screen
- Direction
- presentation.ui.utils.navigation.Screen uses presentation.ui.utils.navigation, so a change to presentation.ui.utils.navigation can break presentation.ui.utils.navigation.Screen, while a change to presentation.ui.utils.navigation.Screen can't break presentation.ui.utils.navigation.
- 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.
22→12 presentation.ui.widgets uses presentation.ui.utils.compose✕
- Connections
- 1 pair of types, where a type in presentation.ui.widgets uses a type in presentation.ui.utils.compose.
- The types involved
ru.tech.cookhelper.presentation.ui.widgets.FabOption→ru.tech.cookhelper.presentation.ui.utils.compose.UIText
- Direction
- presentation.ui.widgets uses presentation.ui.utils.compose, so a change to presentation.ui.utils.compose can break presentation.ui.widgets, while a change to presentation.ui.widgets can't break presentation.ui.utils.compose.
- Position
- Below the diagonal: presentation.ui.widgets uses a module listed above it, which is the healthy direction.
23→3 core.di uses data.utils✕
- Connections
- 3 pairs of types, where a type in core.di uses a type in data.utils.
- The types involved
ru.tech.cookhelper.core.di.NetworkModule→ru.tech.cookhelper.data.utils.JsonParserru.tech.cookhelper.core.di.RepositoryModule→ru.tech.cookhelper.data.utils.JsonParserru.tech.cookhelper.core.di.RoomModule→ru.tech.cookhelper.data.utils.JsonParser
- Direction
- core.di uses data.utils, so a change to data.utils can break core.di, while a change to core.di can't break data.utils.
- Position
- Below the diagonal: core.di uses a module listed above it, which is the healthy direction.
23→7 core.di uses data.local.database✕
- Connections
- 3 pairs of types, where a type in core.di uses a type in data.local.database.
- The types involved
ru.tech.cookhelper.core.di.RepositoryModule→ru.tech.cookhelper.data.local.database.Databaseru.tech.cookhelper.core.di.RoomModule→ru.tech.cookhelper.data.local.database.Databaseru.tech.cookhelper.core.di.RoomModule→ru.tech.cookhelper.data.local.database.TypeConverters
- Direction
- core.di uses data.local.database, so a change to data.local.database can break core.di, while a change to core.di can't break data.local.database.
- Position
- Below the diagonal: core.di uses a module listed above it, which is the healthy direction.
23→10 core.di uses domain.repository✕
- Connections
- 4 pairs of types, where a type in core.di uses a type in domain.repository.
- The types involved
ru.tech.cookhelper.core.di.RepositoryModule→ru.tech.cookhelper.domain.repository.FridgeRepositoryru.tech.cookhelper.core.di.RepositoryModule→ru.tech.cookhelper.domain.repository.MessageRepositoryru.tech.cookhelper.core.di.RepositoryModule→ru.tech.cookhelper.domain.repository.SettingsRepositoryru.tech.cookhelper.core.di.RepositoryModule→ru.tech.cookhelper.domain.repository.UserRepository
- Direction
- core.di uses domain.repository, so a change to domain.repository can break core.di, while a change to core.di can't break domain.repository.
- Position
- Below the diagonal: core.di uses a module listed above it, which is the healthy direction.
23→13 core.di uses data.remote.api.auth✕
- Connections
- 2 pairs of types, where a type in core.di uses a type in data.remote.api.auth.
- The types involved
ru.tech.cookhelper.core.di.NetworkModule→ru.tech.cookhelper.data.remote.api.auth.AuthServiceru.tech.cookhelper.core.di.RepositoryModule→ru.tech.cookhelper.data.remote.api.auth.AuthService
- Direction
- core.di uses data.remote.api.auth, so a change to data.remote.api.auth can break core.di, while a change to core.di can't break data.remote.api.auth.
- Position
- Below the diagonal: core.di uses a module listed above it, which is the healthy direction.
23→14 core.di uses data.remote.api.chat✕
- Connections
- 2 pairs of types, where a type in core.di uses a type in data.remote.api.chat.
- The types involved
ru.tech.cookhelper.core.di.NetworkModule→ru.tech.cookhelper.data.remote.api.chat.ChatApiru.tech.cookhelper.core.di.RepositoryModule→ru.tech.cookhelper.data.remote.api.chat.ChatApi
- Direction
- core.di uses data.remote.api.chat, so a change to data.remote.api.chat can break core.di, while a change to core.di can't break data.remote.api.chat.
- Position
- Below the diagonal: core.di uses a module listed above it, which is the healthy direction.
23→15 core.di uses data.remote.api.ingredients✕
- Connections
- 2 pairs of types, where a type in core.di uses a type in data.remote.api.ingredients.
- The types involved
ru.tech.cookhelper.core.di.NetworkModule→ru.tech.cookhelper.data.remote.api.ingredients.FridgeApiru.tech.cookhelper.core.di.RepositoryModule→ru.tech.cookhelper.data.remote.api.ingredients.FridgeApi
- Direction
- core.di uses data.remote.api.ingredients, so a change to data.remote.api.ingredients can break core.di, while a change to core.di can't break data.remote.api.ingredients.
- Position
- Below the diagonal: core.di uses a module listed above it, which is the healthy direction.
23→16 core.di uses data.remote.web_socket.feed✕
- Connections
- 2 pairs of types, where a type in core.di uses a type in data.remote.web_socket.feed.
- The types involved
ru.tech.cookhelper.core.di.NetworkModule→ru.tech.cookhelper.data.remote.web_socket.feed.FeedServiceru.tech.cookhelper.core.di.RepositoryModule→ru.tech.cookhelper.data.remote.web_socket.feed.FeedService
- Direction
- core.di uses data.remote.web_socket.feed, so a change to data.remote.web_socket.feed can break core.di, while a change to core.di can't break data.remote.web_socket.feed.
- Position
- Below the diagonal: core.di uses a module listed above it, which is the healthy direction.
23→17 core.di uses data.remote.web_socket.message✕
- Connections
- 2 pairs of types, where a type in core.di uses a type in data.remote.web_socket.message.
- The types involved
ru.tech.cookhelper.core.di.NetworkModule→ru.tech.cookhelper.data.remote.web_socket.message.MessageServiceru.tech.cookhelper.core.di.RepositoryModule→ru.tech.cookhelper.data.remote.web_socket.message.MessageService
- Direction
- core.di uses data.remote.web_socket.message, so a change to data.remote.web_socket.message can break core.di, while a change to core.di can't break data.remote.web_socket.message.
- Position
- Below the diagonal: core.di uses a module listed above it, which is the healthy direction.
23→18 core.di uses data.remote.web_socket.user✕
- Connections
- 2 pairs of types, where a type in core.di uses a type in data.remote.web_socket.user.
- The types involved
ru.tech.cookhelper.core.di.NetworkModule→ru.tech.cookhelper.data.remote.web_socket.user.UserServiceru.tech.cookhelper.core.di.RepositoryModule→ru.tech.cookhelper.data.remote.web_socket.user.UserService
- Direction
- core.di uses data.remote.web_socket.user, so a change to data.remote.web_socket.user can break core.di, while a change to core.di can't break data.remote.web_socket.user.
- Position
- Below the diagonal: core.di uses a module listed above it, which is the healthy direction.
24→1 data.repository uses core✕
- Connections
- 3 pairs of types, where a type in data.repository uses a type in core.
- The types involved
ru.tech.cookhelper.data.repository.FridgeRepositoryImpl→ru.tech.cookhelper.core.Actionru.tech.cookhelper.data.repository.MessageRepositoryImpl→ru.tech.cookhelper.core.Actionru.tech.cookhelper.data.repository.UserRepositoryImpl→ru.tech.cookhelper.core.Action
- Direction
- data.repository uses core, so a change to core can break data.repository, while a change to data.repository can't break core.
- Position
- Below the diagonal: data.repository uses a module listed above it, which is the healthy direction.
24→3 data.repository uses data.utils✕
- Connections
- 1 pair of types, where a type in data.repository uses a type in data.utils.
- The types involved
ru.tech.cookhelper.data.repository.MessageRepositoryImpl→ru.tech.cookhelper.data.utils.JsonParser
- Direction
- data.repository uses data.utils, so a change to data.utils can break data.repository, while a change to data.repository can't break data.utils.
- Position
- Below the diagonal: data.repository uses a module listed above it, which is the healthy direction.
24→4 data.repository uses domain.model✕
- Connections
- 11 pairs of types, where a type in data.repository uses a type in domain.model.
- The types involved
ru.tech.cookhelper.data.repository.FridgeRepositoryImpl→ru.tech.cookhelper.domain.model.MatchedReciperu.tech.cookhelper.data.repository.FridgeRepositoryImpl→ru.tech.cookhelper.domain.model.Productru.tech.cookhelper.data.repository.FridgeRepositoryImpl→ru.tech.cookhelper.domain.model.Userru.tech.cookhelper.data.repository.MessageRepositoryImpl→ru.tech.cookhelper.domain.model.Chatru.tech.cookhelper.data.repository.MessageRepositoryImpl→ru.tech.cookhelper.domain.model.FormMessageru.tech.cookhelper.data.repository.MessageRepositoryImpl→ru.tech.cookhelper.domain.model.Messageru.tech.cookhelper.data.repository.SettingsRepositoryImpl→ru.tech.cookhelper.domain.model.Settingru.tech.cookhelper.data.repository.UserRepositoryImpl→ru.tech.cookhelper.domain.model.Postru.tech.cookhelper.data.repository.UserRepositoryImpl→ru.tech.cookhelper.domain.model.Reciperu.tech.cookhelper.data.repository.UserRepositoryImpl→ru.tech.cookhelper.domain.model.Topicru.tech.cookhelper.data.repository.UserRepositoryImpl→ru.tech.cookhelper.domain.model.User
- Direction
- data.repository uses domain.model, so a change to domain.model can break data.repository, while a change to data.repository can't break domain.model.
- Position
- Below the diagonal: data.repository uses a module listed above it, which is the healthy direction.
24→10 data.repository uses domain.repository✕
- Connections
- 4 pairs of types, where a type in data.repository uses a type in domain.repository.
- The types involved
ru.tech.cookhelper.data.repository.FridgeRepositoryImpl→ru.tech.cookhelper.domain.repository.FridgeRepositoryru.tech.cookhelper.data.repository.MessageRepositoryImpl→ru.tech.cookhelper.domain.repository.MessageRepositoryru.tech.cookhelper.data.repository.SettingsRepositoryImpl→ru.tech.cookhelper.domain.repository.SettingsRepositoryru.tech.cookhelper.data.repository.UserRepositoryImpl→ru.tech.cookhelper.domain.repository.UserRepository
- Direction
- data.repository uses domain.repository, so a change to domain.repository can break data.repository, while a change to data.repository can't break domain.repository.
- Position
- Below the diagonal: data.repository uses a module listed above it, which is the healthy direction.
24→13 data.repository uses data.remote.api.auth✕
- Connections
- 1 pair of types, where a type in data.repository uses a type in data.remote.api.auth.
- The types involved
ru.tech.cookhelper.data.repository.UserRepositoryImpl→ru.tech.cookhelper.data.remote.api.auth.AuthService
- Direction
- data.repository uses data.remote.api.auth, so a change to data.remote.api.auth can break data.repository, while a change to data.repository can't break data.remote.api.auth.
- Position
- Below the diagonal: data.repository uses a module listed above it, which is the healthy direction.
24→14 data.repository uses data.remote.api.chat✕
- Connections
- 1 pair of types, where a type in data.repository uses a type in data.remote.api.chat.
- The types involved
ru.tech.cookhelper.data.repository.MessageRepositoryImpl→ru.tech.cookhelper.data.remote.api.chat.ChatApi
- Direction
- data.repository uses data.remote.api.chat, so a change to data.remote.api.chat can break data.repository, while a change to data.repository can't break data.remote.api.chat.
- Position
- Below the diagonal: data.repository uses a module listed above it, which is the healthy direction.
24→15 data.repository uses data.remote.api.ingredients✕
- Connections
- 1 pair of types, where a type in data.repository uses a type in data.remote.api.ingredients.
- The types involved
ru.tech.cookhelper.data.repository.FridgeRepositoryImpl→ru.tech.cookhelper.data.remote.api.ingredients.FridgeApi
- Direction
- data.repository uses data.remote.api.ingredients, so a change to data.remote.api.ingredients can break data.repository, while a change to data.repository can't break data.remote.api.ingredients.
- Position
- Below the diagonal: data.repository uses a module listed above it, which is the healthy direction.
24→16 data.repository uses data.remote.web_socket.feed✕
- Connections
- 1 pair of types, where a type in data.repository uses a type in data.remote.web_socket.feed.
- The types involved
ru.tech.cookhelper.data.repository.UserRepositoryImpl→ru.tech.cookhelper.data.remote.web_socket.feed.FeedService
- Direction
- data.repository uses data.remote.web_socket.feed, so a change to data.remote.web_socket.feed can break data.repository, while a change to data.repository can't break data.remote.web_socket.feed.
- Position
- Below the diagonal: data.repository uses a module listed above it, which is the healthy direction.
24→17 data.repository uses data.remote.web_socket.message✕
- Connections
- 1 pair of types, where a type in data.repository uses a type in data.remote.web_socket.message.
- The types involved
ru.tech.cookhelper.data.repository.MessageRepositoryImpl→ru.tech.cookhelper.data.remote.web_socket.message.MessageService
- Direction
- data.repository uses data.remote.web_socket.message, so a change to data.remote.web_socket.message can break data.repository, while a change to data.repository can't break data.remote.web_socket.message.
- Position
- Below the diagonal: data.repository uses a module listed above it, which is the healthy direction.
24→18 data.repository uses data.remote.web_socket.user✕
- Connections
- 1 pair of types, where a type in data.repository uses a type in data.remote.web_socket.user.
- The types involved
ru.tech.cookhelper.data.repository.UserRepositoryImpl→ru.tech.cookhelper.data.remote.web_socket.user.UserService
- Direction
- data.repository uses data.remote.web_socket.user, so a change to data.remote.web_socket.user can break data.repository, while a change to data.repository can't break data.remote.web_socket.user.
- Position
- Below the diagonal: data.repository uses a module listed above it, which is the healthy direction.
25→5 presentation.app.viewModel uses presentation.settings.components✕
- Connections
- 1 pair of types, where a type in presentation.app.viewModel uses a type in presentation.settings.components.
- The types involved
ru.tech.cookhelper.presentation.app.viewModel.MainViewModel→ru.tech.cookhelper.presentation.settings.components.SettingsState
- Direction
- presentation.app.viewModel uses presentation.settings.components, so a change to presentation.settings.components can break presentation.app.viewModel, while a change to presentation.app.viewModel can't break presentation.settings.components.
- Position
- Below the diagonal: presentation.app.viewModel uses a module listed above it, which is the healthy direction.
25→6 presentation.app.viewModel uses presentation.ui.utils.event✕
- Connections
- 1 pair of types, where a type in presentation.app.viewModel uses a type in presentation.ui.utils.event.
- The types involved
ru.tech.cookhelper.presentation.app.viewModel.MainViewModel→ru.tech.cookhelper.presentation.ui.utils.event.ViewModelEvents
- Direction
- presentation.app.viewModel uses presentation.ui.utils.event, so a change to presentation.ui.utils.event can break presentation.app.viewModel, while a change to presentation.app.viewModel can't break presentation.ui.utils.event.
- Position
- Below the diagonal: presentation.app.viewModel uses a module listed above it, which is the healthy direction.
25→12 presentation.app.viewModel uses presentation.ui.utils.compose✕
- Connections
- 1 pair of types, where a type in presentation.app.viewModel uses a type in presentation.ui.utils.compose.
- The types involved
ru.tech.cookhelper.presentation.app.viewModel.MainViewModel→ru.tech.cookhelper.presentation.ui.utils.compose.UIText
- Direction
- presentation.app.viewModel uses presentation.ui.utils.compose, so a change to presentation.ui.utils.compose can break presentation.app.viewModel, while a change to presentation.app.viewModel can't break presentation.ui.utils.compose.
- Position
- Below the diagonal: presentation.app.viewModel uses a module listed above it, which is the healthy direction.
25→19 presentation.app.viewModel uses domain.use_case.cache_user✕
- Connections
- 1 pair of types, where a type in presentation.app.viewModel uses a type in domain.use_case.cache_user.
- The types involved
ru.tech.cookhelper.presentation.app.viewModel.MainViewModel→ru.tech.cookhelper.domain.use_case.cache_user.CacheUserUseCase
- Direction
- presentation.app.viewModel uses domain.use_case.cache_user, so a change to domain.use_case.cache_user can break presentation.app.viewModel, while a change to presentation.app.viewModel can't break domain.use_case.cache_user.
- Position
- Below the diagonal: presentation.app.viewModel uses a module listed above it, which is the healthy direction.
25→20 presentation.app.viewModel uses domain.use_case.get_user✕
- Connections
- 1 pair of types, where a type in presentation.app.viewModel uses a type in domain.use_case.get_user.
- The types involved
ru.tech.cookhelper.presentation.app.viewModel.MainViewModel→ru.tech.cookhelper.domain.use_case.get_user.GetUserUseCase
- Direction
- presentation.app.viewModel uses domain.use_case.get_user, so a change to domain.use_case.get_user can break presentation.app.viewModel, while a change to presentation.app.viewModel can't break domain.use_case.get_user.
- Position
- Below the diagonal: presentation.app.viewModel uses a module listed above it, which is the healthy direction.
25→34 presentation.app.viewModel uses presentation.app.components part of a loop✕
- Connections
- 1 pair of types, where a type in presentation.app.viewModel uses a type in presentation.app.components.
- The types involved
ru.tech.cookhelper.presentation.app.viewModel.MainViewModel→ru.tech.cookhelper.presentation.app.components.UserState
- Direction
- presentation.app.viewModel uses presentation.app.components, so a change to presentation.app.components can break presentation.app.viewModel, while a change to presentation.app.viewModel can't break presentation.app.components.
- 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.
26→4 presentation.chat.viewModel uses domain.model✕
- Connections
- 1 pair of types, where a type in presentation.chat.viewModel uses a type in domain.model.
- The types involved
ru.tech.cookhelper.presentation.chat.viewModel.ChatViewModel→ru.tech.cookhelper.domain.model.User
- Direction
- presentation.chat.viewModel uses domain.model, so a change to domain.model can break presentation.chat.viewModel, while a change to presentation.chat.viewModel can't break domain.model.
- Position
- Below the diagonal: presentation.chat.viewModel uses a module listed above it, which is the healthy direction.
26→6 presentation.chat.viewModel uses presentation.ui.utils.event✕
- Connections
- 1 pair of types, where a type in presentation.chat.viewModel uses a type in presentation.ui.utils.event.
- The types involved
ru.tech.cookhelper.presentation.chat.viewModel.ChatViewModel→ru.tech.cookhelper.presentation.ui.utils.event.ViewModelEvents
- Direction
- presentation.chat.viewModel uses presentation.ui.utils.event, so a change to presentation.ui.utils.event can break presentation.chat.viewModel, while a change to presentation.chat.viewModel can't break presentation.ui.utils.event.
- Position
- Below the diagonal: presentation.chat.viewModel uses a module listed above it, which is the healthy direction.
26→20 presentation.chat.viewModel uses domain.use_case.get_user✕
- Connections
- 1 pair of types, where a type in presentation.chat.viewModel uses a type in domain.use_case.get_user.
- The types involved
ru.tech.cookhelper.presentation.chat.viewModel.ChatViewModel→ru.tech.cookhelper.domain.use_case.get_user.GetUserUseCase
- Direction
- presentation.chat.viewModel uses domain.use_case.get_user, so a change to domain.use_case.get_user can break presentation.chat.viewModel, while a change to presentation.chat.viewModel can't break domain.use_case.get_user.
- Position
- Below the diagonal: presentation.chat.viewModel uses a module listed above it, which is the healthy direction.
27→4 presentation.chat_list.viewModel uses domain.model✕
- Connections
- 1 pair of types, where a type in presentation.chat_list.viewModel uses a type in domain.model.
- The types involved
ru.tech.cookhelper.presentation.chat_list.viewModel.ChatListViewModel→ru.tech.cookhelper.domain.model.User
- Direction
- presentation.chat_list.viewModel uses domain.model, so a change to domain.model can break presentation.chat_list.viewModel, while a change to presentation.chat_list.viewModel can't break domain.model.
- Position
- Below the diagonal: presentation.chat_list.viewModel uses a module listed above it, which is the healthy direction.
27→6 presentation.chat_list.viewModel uses presentation.ui.utils.event✕
- Connections
- 1 pair of types, where a type in presentation.chat_list.viewModel uses a type in presentation.ui.utils.event.
- The types involved
ru.tech.cookhelper.presentation.chat_list.viewModel.ChatListViewModel→ru.tech.cookhelper.presentation.ui.utils.event.ViewModelEvents
- Direction
- presentation.chat_list.viewModel uses presentation.ui.utils.event, so a change to presentation.ui.utils.event can break presentation.chat_list.viewModel, while a change to presentation.chat_list.viewModel can't break presentation.ui.utils.event.
- Position
- Below the diagonal: presentation.chat_list.viewModel uses a module listed above it, which is the healthy direction.
27→20 presentation.chat_list.viewModel uses domain.use_case.get_user✕
- Connections
- 1 pair of types, where a type in presentation.chat_list.viewModel uses a type in domain.use_case.get_user.
- The types involved
ru.tech.cookhelper.presentation.chat_list.viewModel.ChatListViewModel→ru.tech.cookhelper.domain.use_case.get_user.GetUserUseCase
- Direction
- presentation.chat_list.viewModel uses domain.use_case.get_user, so a change to domain.use_case.get_user can break presentation.chat_list.viewModel, while a change to presentation.chat_list.viewModel can't break domain.use_case.get_user.
- Position
- Below the diagonal: presentation.chat_list.viewModel uses a module listed above it, which is the healthy direction.
28→6 presentation.confirm_email.viewModel uses presentation.ui.utils.event✕
- Connections
- 1 pair of types, where a type in presentation.confirm_email.viewModel uses a type in presentation.ui.utils.event.
- The types involved
ru.tech.cookhelper.presentation.confirm_email.viewModel.ConfirmEmailViewModel→ru.tech.cookhelper.presentation.ui.utils.event.ViewModelEvents
- Direction
- presentation.confirm_email.viewModel uses presentation.ui.utils.event, so a change to presentation.ui.utils.event can break presentation.confirm_email.viewModel, while a change to presentation.confirm_email.viewModel can't break presentation.ui.utils.event.
- Position
- Below the diagonal: presentation.confirm_email.viewModel uses a module listed above it, which is the healthy direction.
28→19 presentation.confirm_email.viewModel uses domain.use_case.cache_user✕
- Connections
- 1 pair of types, where a type in presentation.confirm_email.viewModel uses a type in domain.use_case.cache_user.
- The types involved
ru.tech.cookhelper.presentation.confirm_email.viewModel.ConfirmEmailViewModel→ru.tech.cookhelper.domain.use_case.cache_user.CacheUserUseCase
- Direction
- presentation.confirm_email.viewModel uses domain.use_case.cache_user, so a change to domain.use_case.cache_user can break presentation.confirm_email.viewModel, while a change to presentation.confirm_email.viewModel can't break domain.use_case.cache_user.
- Position
- Below the diagonal: presentation.confirm_email.viewModel uses a module listed above it, which is the healthy direction.
29→6 presentation.login_screen.viewModel uses presentation.ui.utils.event✕
- Connections
- 1 pair of types, where a type in presentation.login_screen.viewModel uses a type in presentation.ui.utils.event.
- The types involved
ru.tech.cookhelper.presentation.login_screen.viewModel.LoginViewModel→ru.tech.cookhelper.presentation.ui.utils.event.ViewModelEvents
- Direction
- presentation.login_screen.viewModel uses presentation.ui.utils.event, so a change to presentation.ui.utils.event can break presentation.login_screen.viewModel, while a change to presentation.login_screen.viewModel can't break presentation.ui.utils.event.
- Position
- Below the diagonal: presentation.login_screen.viewModel uses a module listed above it, which is the healthy direction.
29→19 presentation.login_screen.viewModel uses domain.use_case.cache_user✕
- Connections
- 1 pair of types, where a type in presentation.login_screen.viewModel uses a type in domain.use_case.cache_user.
- The types involved
ru.tech.cookhelper.presentation.login_screen.viewModel.LoginViewModel→ru.tech.cookhelper.domain.use_case.cache_user.CacheUserUseCase
- Direction
- presentation.login_screen.viewModel uses domain.use_case.cache_user, so a change to domain.use_case.cache_user can break presentation.login_screen.viewModel, while a change to presentation.login_screen.viewModel can't break domain.use_case.cache_user.
- Position
- Below the diagonal: presentation.login_screen.viewModel uses a module listed above it, which is the healthy direction.
30→4 presentation.post_creation.viewModel uses domain.model✕
- Connections
- 1 pair of types, where a type in presentation.post_creation.viewModel uses a type in domain.model.
- The types involved
ru.tech.cookhelper.presentation.post_creation.viewModel.PostCreationViewModel→ru.tech.cookhelper.domain.model.User
- Direction
- presentation.post_creation.viewModel uses domain.model, so a change to domain.model can break presentation.post_creation.viewModel, while a change to presentation.post_creation.viewModel can't break domain.model.
- Position
- Below the diagonal: presentation.post_creation.viewModel uses a module listed above it, which is the healthy direction.
30→6 presentation.post_creation.viewModel uses presentation.ui.utils.event✕
- Connections
- 1 pair of types, where a type in presentation.post_creation.viewModel uses a type in presentation.ui.utils.event.
- The types involved
ru.tech.cookhelper.presentation.post_creation.viewModel.PostCreationViewModel→ru.tech.cookhelper.presentation.ui.utils.event.ViewModelEvents
- Direction
- presentation.post_creation.viewModel uses presentation.ui.utils.event, so a change to presentation.ui.utils.event can break presentation.post_creation.viewModel, while a change to presentation.post_creation.viewModel can't break presentation.ui.utils.event.
- Position
- Below the diagonal: presentation.post_creation.viewModel uses a module listed above it, which is the healthy direction.
30→20 presentation.post_creation.viewModel uses domain.use_case.get_user✕
- Connections
- 1 pair of types, where a type in presentation.post_creation.viewModel uses a type in domain.use_case.get_user.
- The types involved
ru.tech.cookhelper.presentation.post_creation.viewModel.PostCreationViewModel→ru.tech.cookhelper.domain.use_case.get_user.GetUserUseCase
- Direction
- presentation.post_creation.viewModel uses domain.use_case.get_user, so a change to domain.use_case.get_user can break presentation.post_creation.viewModel, while a change to presentation.post_creation.viewModel can't break domain.use_case.get_user.
- Position
- Below the diagonal: presentation.post_creation.viewModel uses a module listed above it, which is the healthy direction.
31→6 presentation.registration_screen.viewModel uses presentation.ui.utils.event✕
- Connections
- 1 pair of types, where a type in presentation.registration_screen.viewModel uses a type in presentation.ui.utils.event.
- The types involved
ru.tech.cookhelper.presentation.registration_screen.viewModel.RegistrationViewModel→ru.tech.cookhelper.presentation.ui.utils.event.ViewModelEvents
- Direction
- presentation.registration_screen.viewModel uses presentation.ui.utils.event, so a change to presentation.ui.utils.event can break presentation.registration_screen.viewModel, while a change to presentation.registration_screen.viewModel can't break presentation.ui.utils.event.
- Position
- Below the diagonal: presentation.registration_screen.viewModel uses a module listed above it, which is the healthy direction.
31→12 presentation.registration_screen.viewModel uses presentation.ui.utils.compose✕
- Connections
- 1 pair of types, where a type in presentation.registration_screen.viewModel uses a type in presentation.ui.utils.compose.
- The types involved
ru.tech.cookhelper.presentation.registration_screen.viewModel.RegistrationViewModel→ru.tech.cookhelper.presentation.ui.utils.compose.UIText
- Direction
- presentation.registration_screen.viewModel uses presentation.ui.utils.compose, so a change to presentation.ui.utils.compose can break presentation.registration_screen.viewModel, while a change to presentation.registration_screen.viewModel can't break presentation.ui.utils.compose.
- Position
- Below the diagonal: presentation.registration_screen.viewModel uses a module listed above it, which is the healthy direction.
31→19 presentation.registration_screen.viewModel uses domain.use_case.cache_user✕
- Connections
- 1 pair of types, where a type in presentation.registration_screen.viewModel uses a type in domain.use_case.cache_user.
- The types involved
ru.tech.cookhelper.presentation.registration_screen.viewModel.RegistrationViewModel→ru.tech.cookhelper.domain.use_case.cache_user.CacheUserUseCase
- Direction
- presentation.registration_screen.viewModel uses domain.use_case.cache_user, so a change to domain.use_case.cache_user can break presentation.registration_screen.viewModel, while a change to presentation.registration_screen.viewModel can't break domain.use_case.cache_user.
- Position
- Below the diagonal: presentation.registration_screen.viewModel uses a module listed above it, which is the healthy direction.
32→4 presentation.topic_creation.viewModel uses domain.model✕
- Connections
- 1 pair of types, where a type in presentation.topic_creation.viewModel uses a type in domain.model.
- The types involved
ru.tech.cookhelper.presentation.topic_creation.viewModel.TopicCreationViewModel→ru.tech.cookhelper.domain.model.User
- Direction
- presentation.topic_creation.viewModel uses domain.model, so a change to domain.model can break presentation.topic_creation.viewModel, while a change to presentation.topic_creation.viewModel can't break domain.model.
- Position
- Below the diagonal: presentation.topic_creation.viewModel uses a module listed above it, which is the healthy direction.
32→6 presentation.topic_creation.viewModel uses presentation.ui.utils.event✕
- Connections
- 1 pair of types, where a type in presentation.topic_creation.viewModel uses a type in presentation.ui.utils.event.
- The types involved
ru.tech.cookhelper.presentation.topic_creation.viewModel.TopicCreationViewModel→ru.tech.cookhelper.presentation.ui.utils.event.ViewModelEvents
- Direction
- presentation.topic_creation.viewModel uses presentation.ui.utils.event, so a change to presentation.ui.utils.event can break presentation.topic_creation.viewModel, while a change to presentation.topic_creation.viewModel can't break presentation.ui.utils.event.
- Position
- Below the diagonal: presentation.topic_creation.viewModel uses a module listed above it, which is the healthy direction.
32→20 presentation.topic_creation.viewModel uses domain.use_case.get_user✕
- Connections
- 1 pair of types, where a type in presentation.topic_creation.viewModel uses a type in domain.use_case.get_user.
- The types involved
ru.tech.cookhelper.presentation.topic_creation.viewModel.TopicCreationViewModel→ru.tech.cookhelper.domain.use_case.get_user.GetUserUseCase
- Direction
- presentation.topic_creation.viewModel uses domain.use_case.get_user, so a change to domain.use_case.get_user can break presentation.topic_creation.viewModel, while a change to presentation.topic_creation.viewModel can't break domain.use_case.get_user.
- Position
- Below the diagonal: presentation.topic_creation.viewModel uses a module listed above it, which is the healthy direction.
33→12 presentation.ui.utils.navigation uses presentation.ui.utils.compose✕
- Connections
- 1 pair of types, where a type in presentation.ui.utils.navigation uses a type in presentation.ui.utils.compose.
- The types involved
ru.tech.cookhelper.presentation.ui.utils.navigation.Screen→ru.tech.cookhelper.presentation.ui.utils.compose.UIText
- Direction
- presentation.ui.utils.navigation uses presentation.ui.utils.compose, so a change to presentation.ui.utils.compose can break presentation.ui.utils.navigation, while a change to presentation.ui.utils.navigation can't break presentation.ui.utils.compose.
- Position
- Below the diagonal: presentation.ui.utils.navigation uses a module listed above it, which is the healthy direction.
33→21 presentation.ui.utils.navigation uses presentation.ui.utils.navigation.Screen✕
- Connections
- 1 pair of types, where a type in presentation.ui.utils.navigation uses a type in presentation.ui.utils.navigation.Screen.
- The types involved
ru.tech.cookhelper.presentation.ui.utils.navigation.ScreenKt→ru.tech.cookhelper.presentation.ui.utils.navigation.Screen.Home
- Direction
- presentation.ui.utils.navigation uses presentation.ui.utils.navigation.Screen, so a change to presentation.ui.utils.navigation.Screen can break presentation.ui.utils.navigation, while a change to presentation.ui.utils.navigation can't break presentation.ui.utils.navigation.Screen.
- Position
- Below the diagonal: presentation.ui.utils.navigation uses a module listed above it, which is the healthy direction.
34→4 presentation.app.components uses domain.model✕
- Connections
- 1 pair of types, where a type in presentation.app.components uses a type in domain.model.
- The types involved
ru.tech.cookhelper.presentation.app.components.UserState→ru.tech.cookhelper.domain.model.User
- Direction
- presentation.app.components uses domain.model, so a change to domain.model can break presentation.app.components, while a change to presentation.app.components can't break domain.model.
- Position
- Below the diagonal: presentation.app.components uses a module listed above it, which is the healthy direction.
34→12 presentation.app.components uses presentation.ui.utils.compose✕
- Connections
- 1 pair of types, where a type in presentation.app.components uses a type in presentation.ui.utils.compose.
- The types involved
ru.tech.cookhelper.presentation.app.components.ScreenHostKt→ru.tech.cookhelper.presentation.ui.utils.compose.UIText
- Direction
- presentation.app.components uses presentation.ui.utils.compose, so a change to presentation.ui.utils.compose can break presentation.app.components, while a change to presentation.app.components can't break presentation.ui.utils.compose.
- Position
- Below the diagonal: presentation.app.components uses a module listed above it, which is the healthy direction.
34→25 presentation.app.components uses presentation.app.viewModel✕
- Connections
- 1 pair of types, where a type in presentation.app.components uses a type in presentation.app.viewModel.
- The types involved
ru.tech.cookhelper.presentation.app.components.CookHelperAppKt→ru.tech.cookhelper.presentation.app.viewModel.MainViewModel
- Direction
- presentation.app.components uses presentation.app.viewModel, so a change to presentation.app.viewModel can break presentation.app.components, while a change to presentation.app.components can't break presentation.app.viewModel.
- Position
- Below the diagonal: presentation.app.components uses a module listed above it, which is the healthy direction.
34→33 presentation.app.components uses presentation.ui.utils.navigation✕
- Connections
- 2 pairs of types, where a type in presentation.app.components uses a type in presentation.ui.utils.navigation.
- The types involved
ru.tech.cookhelper.presentation.app.components.MainModalDrawerContentKt→ru.tech.cookhelper.presentation.ui.utils.navigation.Screenru.tech.cookhelper.presentation.app.components.ScreenHostKt→ru.tech.cookhelper.presentation.ui.utils.navigation.Screen
- Direction
- presentation.app.components uses presentation.ui.utils.navigation, so a change to presentation.ui.utils.navigation can break presentation.app.components, while a change to presentation.app.components can't break presentation.ui.utils.navigation.
- Position
- Below the diagonal: presentation.app.components uses a module listed above it, which is the healthy direction.
35→6 presentation.edit_profile.viewModel uses presentation.ui.utils.event✕
- Connections
- 1 pair of types, where a type in presentation.edit_profile.viewModel uses a type in presentation.ui.utils.event.
- The types involved
ru.tech.cookhelper.presentation.edit_profile.viewModel.EditProfileViewModel→ru.tech.cookhelper.presentation.ui.utils.event.ViewModelEvents
- Direction
- presentation.edit_profile.viewModel uses presentation.ui.utils.event, so a change to presentation.ui.utils.event can break presentation.edit_profile.viewModel, while a change to presentation.edit_profile.viewModel can't break presentation.ui.utils.event.
- Position
- Below the diagonal: presentation.edit_profile.viewModel uses a module listed above it, which is the healthy direction.
35→12 presentation.edit_profile.viewModel uses presentation.ui.utils.compose✕
- Connections
- 1 pair of types, where a type in presentation.edit_profile.viewModel uses a type in presentation.ui.utils.compose.
- The types involved
ru.tech.cookhelper.presentation.edit_profile.viewModel.EditProfileViewModel→ru.tech.cookhelper.presentation.ui.utils.compose.UIText
- Direction
- presentation.edit_profile.viewModel uses presentation.ui.utils.compose, so a change to presentation.ui.utils.compose can break presentation.edit_profile.viewModel, while a change to presentation.edit_profile.viewModel can't break presentation.ui.utils.compose.
- Position
- Below the diagonal: presentation.edit_profile.viewModel uses a module listed above it, which is the healthy direction.
35→20 presentation.edit_profile.viewModel uses domain.use_case.get_user✕
- Connections
- 1 pair of types, where a type in presentation.edit_profile.viewModel uses a type in domain.use_case.get_user.
- The types involved
ru.tech.cookhelper.presentation.edit_profile.viewModel.EditProfileViewModel→ru.tech.cookhelper.domain.use_case.get_user.GetUserUseCase
- Direction
- presentation.edit_profile.viewModel uses domain.use_case.get_user, so a change to domain.use_case.get_user can break presentation.edit_profile.viewModel, while a change to presentation.edit_profile.viewModel can't break domain.use_case.get_user.
- Position
- Below the diagonal: presentation.edit_profile.viewModel uses a module listed above it, which is the healthy direction.
35→34 presentation.edit_profile.viewModel uses presentation.app.components✕
- Connections
- 1 pair of types, where a type in presentation.edit_profile.viewModel uses a type in presentation.app.components.
- The types involved
ru.tech.cookhelper.presentation.edit_profile.viewModel.EditProfileViewModel→ru.tech.cookhelper.presentation.app.components.UserState
- Direction
- presentation.edit_profile.viewModel uses presentation.app.components, so a change to presentation.app.components can break presentation.edit_profile.viewModel, while a change to presentation.edit_profile.viewModel can't break presentation.app.components.
- Position
- Below the diagonal: presentation.edit_profile.viewModel uses a module listed above it, which is the healthy direction.
36→6 presentation.feed_screen.viewModel uses presentation.ui.utils.event✕
- Connections
- 1 pair of types, where a type in presentation.feed_screen.viewModel uses a type in presentation.ui.utils.event.
- The types involved
ru.tech.cookhelper.presentation.feed_screen.viewModel.FeedViewModel→ru.tech.cookhelper.presentation.ui.utils.event.ViewModelEvents
- Direction
- presentation.feed_screen.viewModel uses presentation.ui.utils.event, so a change to presentation.ui.utils.event can break presentation.feed_screen.viewModel, while a change to presentation.feed_screen.viewModel can't break presentation.ui.utils.event.
- Position
- Below the diagonal: presentation.feed_screen.viewModel uses a module listed above it, which is the healthy direction.
36→20 presentation.feed_screen.viewModel uses domain.use_case.get_user✕
- Connections
- 1 pair of types, where a type in presentation.feed_screen.viewModel uses a type in domain.use_case.get_user.
- The types involved
ru.tech.cookhelper.presentation.feed_screen.viewModel.FeedViewModel→ru.tech.cookhelper.domain.use_case.get_user.GetUserUseCase
- Direction
- presentation.feed_screen.viewModel uses domain.use_case.get_user, so a change to domain.use_case.get_user can break presentation.feed_screen.viewModel, while a change to presentation.feed_screen.viewModel can't break domain.use_case.get_user.
- Position
- Below the diagonal: presentation.feed_screen.viewModel uses a module listed above it, which is the healthy direction.
36→34 presentation.feed_screen.viewModel uses presentation.app.components✕
- Connections
- 1 pair of types, where a type in presentation.feed_screen.viewModel uses a type in presentation.app.components.
- The types involved
ru.tech.cookhelper.presentation.feed_screen.viewModel.FeedViewModel→ru.tech.cookhelper.presentation.app.components.UserState
- Direction
- presentation.feed_screen.viewModel uses presentation.app.components, so a change to presentation.app.components can break presentation.feed_screen.viewModel, while a change to presentation.feed_screen.viewModel can't break presentation.app.components.
- Position
- Below the diagonal: presentation.feed_screen.viewModel uses a module listed above it, which is the healthy direction.
37→4 presentation.fridge_screen.viewModel uses domain.model✕
- Connections
- 1 pair of types, where a type in presentation.fridge_screen.viewModel uses a type in domain.model.
- The types involved
ru.tech.cookhelper.presentation.fridge_screen.viewModel.FridgeViewModel→ru.tech.cookhelper.domain.model.Product
- Direction
- presentation.fridge_screen.viewModel uses domain.model, so a change to domain.model can break presentation.fridge_screen.viewModel, while a change to presentation.fridge_screen.viewModel can't break domain.model.
- Position
- Below the diagonal: presentation.fridge_screen.viewModel uses a module listed above it, which is the healthy direction.
37→6 presentation.fridge_screen.viewModel uses presentation.ui.utils.event✕
- Connections
- 1 pair of types, where a type in presentation.fridge_screen.viewModel uses a type in presentation.ui.utils.event.
- The types involved
ru.tech.cookhelper.presentation.fridge_screen.viewModel.FridgeViewModel→ru.tech.cookhelper.presentation.ui.utils.event.ViewModelEvents
- Direction
- presentation.fridge_screen.viewModel uses presentation.ui.utils.event, so a change to presentation.ui.utils.event can break presentation.fridge_screen.viewModel, while a change to presentation.fridge_screen.viewModel can't break presentation.ui.utils.event.
- Position
- Below the diagonal: presentation.fridge_screen.viewModel uses a module listed above it, which is the healthy direction.
37→20 presentation.fridge_screen.viewModel uses domain.use_case.get_user✕
- Connections
- 1 pair of types, where a type in presentation.fridge_screen.viewModel uses a type in domain.use_case.get_user.
- The types involved
ru.tech.cookhelper.presentation.fridge_screen.viewModel.FridgeViewModel→ru.tech.cookhelper.domain.use_case.get_user.GetUserUseCase
- Direction
- presentation.fridge_screen.viewModel uses domain.use_case.get_user, so a change to domain.use_case.get_user can break presentation.fridge_screen.viewModel, while a change to presentation.fridge_screen.viewModel can't break domain.use_case.get_user.
- Position
- Below the diagonal: presentation.fridge_screen.viewModel uses a module listed above it, which is the healthy direction.
37→34 presentation.fridge_screen.viewModel uses presentation.app.components✕
- Connections
- 1 pair of types, where a type in presentation.fridge_screen.viewModel uses a type in presentation.app.components.
- The types involved
ru.tech.cookhelper.presentation.fridge_screen.viewModel.FridgeViewModel→ru.tech.cookhelper.presentation.app.components.UserState
- Direction
- presentation.fridge_screen.viewModel uses presentation.app.components, so a change to presentation.app.components can break presentation.fridge_screen.viewModel, while a change to presentation.fridge_screen.viewModel can't break presentation.app.components.
- Position
- Below the diagonal: presentation.fridge_screen.viewModel uses a module listed above it, which is the healthy direction.
38→6 presentation.matched_recipes.viewModel uses presentation.ui.utils.event✕
- Connections
- 1 pair of types, where a type in presentation.matched_recipes.viewModel uses a type in presentation.ui.utils.event.
- The types involved
ru.tech.cookhelper.presentation.matched_recipes.viewModel.MatchedRecipesViewModel→ru.tech.cookhelper.presentation.ui.utils.event.ViewModelEvents
- Direction
- presentation.matched_recipes.viewModel uses presentation.ui.utils.event, so a change to presentation.ui.utils.event can break presentation.matched_recipes.viewModel, while a change to presentation.matched_recipes.viewModel can't break presentation.ui.utils.event.
- Position
- Below the diagonal: presentation.matched_recipes.viewModel uses a module listed above it, which is the healthy direction.
38→20 presentation.matched_recipes.viewModel uses domain.use_case.get_user✕
- Connections
- 1 pair of types, where a type in presentation.matched_recipes.viewModel uses a type in domain.use_case.get_user.
- The types involved
ru.tech.cookhelper.presentation.matched_recipes.viewModel.MatchedRecipesViewModel→ru.tech.cookhelper.domain.use_case.get_user.GetUserUseCase
- Direction
- presentation.matched_recipes.viewModel uses domain.use_case.get_user, so a change to domain.use_case.get_user can break presentation.matched_recipes.viewModel, while a change to presentation.matched_recipes.viewModel can't break domain.use_case.get_user.
- Position
- Below the diagonal: presentation.matched_recipes.viewModel uses a module listed above it, which is the healthy direction.
38→34 presentation.matched_recipes.viewModel uses presentation.app.components✕
- Connections
- 1 pair of types, where a type in presentation.matched_recipes.viewModel uses a type in presentation.app.components.
- The types involved
ru.tech.cookhelper.presentation.matched_recipes.viewModel.MatchedRecipesViewModel→ru.tech.cookhelper.presentation.app.components.UserState
- Direction
- presentation.matched_recipes.viewModel uses presentation.app.components, so a change to presentation.app.components can break presentation.matched_recipes.viewModel, while a change to presentation.matched_recipes.viewModel can't break presentation.app.components.
- Position
- Below the diagonal: presentation.matched_recipes.viewModel uses a module listed above it, which is the healthy direction.
39→4 presentation.pick_products.viewModel uses domain.model✕
- Connections
- 1 pair of types, where a type in presentation.pick_products.viewModel uses a type in domain.model.
- The types involved
ru.tech.cookhelper.presentation.pick_products.viewModel.PickProductsViewModel→ru.tech.cookhelper.domain.model.Product
- Direction
- presentation.pick_products.viewModel uses domain.model, so a change to domain.model can break presentation.pick_products.viewModel, while a change to presentation.pick_products.viewModel can't break domain.model.
- Position
- Below the diagonal: presentation.pick_products.viewModel uses a module listed above it, which is the healthy direction.
39→6 presentation.pick_products.viewModel uses presentation.ui.utils.event✕
- Connections
- 1 pair of types, where a type in presentation.pick_products.viewModel uses a type in presentation.ui.utils.event.
- The types involved
ru.tech.cookhelper.presentation.pick_products.viewModel.PickProductsViewModel→ru.tech.cookhelper.presentation.ui.utils.event.ViewModelEvents
- Direction
- presentation.pick_products.viewModel uses presentation.ui.utils.event, so a change to presentation.ui.utils.event can break presentation.pick_products.viewModel, while a change to presentation.pick_products.viewModel can't break presentation.ui.utils.event.
- Position
- Below the diagonal: presentation.pick_products.viewModel uses a module listed above it, which is the healthy direction.
39→20 presentation.pick_products.viewModel uses domain.use_case.get_user✕
- Connections
- 1 pair of types, where a type in presentation.pick_products.viewModel uses a type in domain.use_case.get_user.
- The types involved
ru.tech.cookhelper.presentation.pick_products.viewModel.PickProductsViewModel→ru.tech.cookhelper.domain.use_case.get_user.GetUserUseCase
- Direction
- presentation.pick_products.viewModel uses domain.use_case.get_user, so a change to domain.use_case.get_user can break presentation.pick_products.viewModel, while a change to presentation.pick_products.viewModel can't break domain.use_case.get_user.
- Position
- Below the diagonal: presentation.pick_products.viewModel uses a module listed above it, which is the healthy direction.
39→34 presentation.pick_products.viewModel uses presentation.app.components✕
- Connections
- 1 pair of types, where a type in presentation.pick_products.viewModel uses a type in presentation.app.components.
- The types involved
ru.tech.cookhelper.presentation.pick_products.viewModel.PickProductsViewModel→ru.tech.cookhelper.presentation.app.components.UserState
- Direction
- presentation.pick_products.viewModel uses presentation.app.components, so a change to presentation.app.components can break presentation.pick_products.viewModel, while a change to presentation.pick_products.viewModel can't break presentation.app.components.
- Position
- Below the diagonal: presentation.pick_products.viewModel uses a module listed above it, which is the healthy direction.
40→20 presentation.profile.viewModel uses domain.use_case.get_user✕
- Connections
- 1 pair of types, where a type in presentation.profile.viewModel uses a type in domain.use_case.get_user.
- The types involved
ru.tech.cookhelper.presentation.profile.viewModel.ProfileViewModel→ru.tech.cookhelper.domain.use_case.get_user.GetUserUseCase
- Direction
- presentation.profile.viewModel uses domain.use_case.get_user, so a change to domain.use_case.get_user can break presentation.profile.viewModel, while a change to presentation.profile.viewModel can't break domain.use_case.get_user.
- Position
- Below the diagonal: presentation.profile.viewModel uses a module listed above it, which is the healthy direction.
40→34 presentation.profile.viewModel uses presentation.app.components✕
- Connections
- 1 pair of types, where a type in presentation.profile.viewModel uses a type in presentation.app.components.
- The types involved
ru.tech.cookhelper.presentation.profile.viewModel.ProfileViewModel→ru.tech.cookhelper.presentation.app.components.UserState
- Direction
- presentation.profile.viewModel uses presentation.app.components, so a change to presentation.app.components can break presentation.profile.viewModel, while a change to presentation.profile.viewModel can't break presentation.app.components.
- Position
- Below the diagonal: presentation.profile.viewModel uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Domain Modelling
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A07:2025 — Authentication Failures | 2 | High / Critical |
Roadmap
Top priorities: Resolve the 1 No automated tests finding(s) in Code Coverage; Resolve the 1 No ADRs found finding(s) in ADR Quality; Resolve the 95 Orphaned file finding(s) in Knowledge Freshness — start with RecipePostCreationScreen.kt, ForumDiscussionScreen.kt, Shapes.kt.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +5.5 pts | Low | ADR Quality |
| Resolve the 1 No automated tests finding(s) in Code Coverage. | +14.7 pts | High | Code Coverage |
| Resolve the 95 Orphaned file finding(s) in Knowledge Freshness — start with RecipePostCreationScreen.kt, ForumDiscussionScreen.kt, Shapes.kt. | +5.5 pts | Medium | Knowledge Freshness |
| Add a CI workflow that builds and runs the test suite on every push/PR. | +5.2 pts | Medium | CI/CD gates |
| Encrypt sensitive data at rest (open the store encrypted — SQLCipher's SupportFactory for Room, a Realm encryptionKey — or encrypt the fields with Tink's AEAD or an AES/GCM Cipher, or use Jetpack Security's EncryptedSharedPreferences on Android) keeping its key in the Android Keystore or a vault, and manage server-side keys in a vault (AWS KMS / Secrets Manager, GCP KMS / REDACTED Manager, Azure Key Vault, HashiCorp Vault). Skip if delegated to infra (Postgres TDE, KMS, etc.). | +5.0 pts | Medium | Data Protection |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +4.2 pts | Medium | Architecture documentation |
| Resolve the 1 REDACTED finding(s) in Secrets (history) — start with REDACTED. | +0.9 pts | Low | Secrets (history) |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +1.7 pts | Medium | Release Hygiene |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| app/src/main/java/ru/tech/cookhelper/presentation/post_creation/PostCreationScreen.kt | 5.5 | Mixed | God Classes: MethodTooLong: PostCreationScreenKt.PostCreationScreen |
| app/src/main/java/ru/tech/cookhelper/presentation/chat/ChatScreen.kt | 5.9 | Mixed | Cyclomatic Complexity: ChatScreenKt.ChatScreen (cyclomatic 21) |
| app/src/main/java/ru/tech/cookhelper/presentation/forum_discussion/ForumDiscussionScreen.kt | 6.0 | Mixed | Explicit Debt: TodoComment |
| app/src/main/java/ru/tech/cookhelper/presentation/profile/ProfileScreen.kt | 6.0 | Mixed | Explicit Debt: TodoComment |
| app/src/main/java/ru/tech/cookhelper/data/repository/UserRepositoryImpl.kt | 6.3 | Mixed | Code Duplication: Duplicated block (7 lines × 2) |
| app/src/main/java/ru/tech/cookhelper/presentation/edit_profile/EditProfileScreen.kt | 6.7 | Mixed | Explicit Debt: TodoComment |
| app/src/main/java/ru/tech/cookhelper/presentation/recipe_post_creation/RecipePostCreationScreen.kt | 7.0 | Near-clean | God Classes: MethodTooLong: RecipePostCreationScreenKt.RecipePostCreationScreen |
| app/src/main/java/ru/tech/cookhelper/presentation/chat/components/MessageBubbleItem.kt | 7.2 | Near-clean | Cyclomatic Complexity: MessageBubbleItemKt.MessageBubbleItem (cyclomatic 22) |
| app/src/main/java/ru/tech/cookhelper/presentation/registration_screen/RegistrationField.kt | 7.2 | Near-clean | Cyclomatic Complexity: RegistrationFieldKt.RegistrationField (cyclomatic 22) |
| app/src/main/java/ru/tech/cookhelper/presentation/pick_products/PickProductsDialog.kt | 7.2 | Near-clean | Cognitive Complexity: PickProductsDialogKt.PickProductsDialog (cognitive 20) |
| app/src/main/java/ru/tech/cookhelper/presentation/login_screen/LoginField.kt | 7.2 | Near-clean | Cognitive Complexity: LoginFieldKt.LoginField (cognitive 19) |
| app/src/main/java/ru/tech/cookhelper/presentation/recipe_post_creation/components/RoundedTextField.kt | 7.2 | Near-clean | Cognitive Complexity: RoundedTextFieldKt.RoundedTextField (cognitive 16) |
| REDACTED | 7.2 | Near-clean | Secrets (history): REDACTED: REDACTED |
| app/src/main/java/ru/tech/cookhelper/presentation/feed_screen/FeedScreen.kt | 7.3 | Near-clean | Explicit Debt: TodoComment |
| app/src/main/java/ru/tech/cookhelper/presentation/restore_password/RestorePasswordField.kt | 7.4 | Near-clean | Cyclomatic Complexity: RestorePasswordFieldKt.RestorePasswordField (cyclomatic 24) |
| app/src/main/java/ru/tech/cookhelper/presentation/authentication/components/OTPField.kt | 7.8 | Near-clean | Cyclomatic Complexity: OTPFieldKt.OTPField (cyclomatic 17) |
| app/src/main/java/ru/tech/cookhelper/presentation/recipe_post_creation/components/PickProductsWithMeasuresDialog.kt | 7.8 | Near-clean | Cognitive Complexity: PickProductsWithMeasuresDialogKt.PickProductsWithMeasuresDialog (cognitive 32) |
| app/src/main/java/ru/tech/cookhelper/presentation/ui/theme/Color.kt | 7.8 | Near-clean | God Classes: ClassTooLong: ColorScheme |
| app/src/main/java/ru/tech/cookhelper/presentation/ui/widgets/CozyTextField.kt | 7.8 | Near-clean | Code Duplication: Duplicated block (20 lines × 2) |
| app/src/main/java/ru/tech/cookhelper/data/repository/FridgeRepositoryImpl.kt | 7.8 | Near-clean | Code Duplication: Duplicated block (10 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 56 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 56 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, 194 of 293 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
- 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 (2 contributor(s) across 357 commit(s) sampled, automation and bot accounts excluded). One of them holds 100% of the history; the other 1 hold 0% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — 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's deterministic call-shape 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. This says nothing about whether that surface is consistent.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `app/src/main/java/ru/tech/cookhelper/core/Action.kt`, `app/src/main/java/ru/tech/cookhelper/presentation/settings/components/SettingsState.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.
- 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.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Boot via AndroidApp (app). the Android app did not build — `./gradlew :app:assembleDebug` exited 1: at java.base/java.lang.Thread.run(Thread.java:1583) FAILURE: Build failed with an exception. * What went wrong: Execution failed for task ':app:kaptGenerateStubsDebugKotlin'. > A failure occurred…; runtime evidence skipped (launch chosen because app/build.gradle.kts applies the Android application plugin and gradlew builds it).
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- DM8 Value-object opportunities — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check finds primitive parameters that travel together through several signatures of the domain (a missing value object). Its deterministic rule has not yet shown 95 % precision on adjudicated rows, so the clumps it finds are counted here and not published as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
- DM9 Scattered domain decisions — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not measured — scattered-decision detection needs expression-level symbol resolution: a comparison operand bound to the member it judges (arm one) and a construction bound to the type it produces (arm two). A Roslyn compilation carries both; arm two alone also runs on any frontend that declares whether a construction is produced or passed, and this target loaded neither.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Kotlin is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's Kotlin is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- 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.
- 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
5 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was RestorePasswordFieldKt.RestorePasswordField at 24. A further 3 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being StatusUtilsKt.getStatusString at 33 — they are counted neither in the figure above nor in this dimension's score. 3 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: app/src/main/java/ru/tech/cookhelper/presentation/ui/utils/StatusUtils.kt (StatusUtilsKt.getStatusString at 33), app/src/main/java/ru/tech/cookhelper/presentation/fridge_screen/components/ProductUtils.kt (ProductUtilsKt.getIcon at 21), app/src/main/java/ru/tech/cookhelper/presentation/app/components/ScreenHost.kt (ScreenHostKt.ScreenHost at 20). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 5 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with RestorePasswordFieldKt.RestorePasswordField (cyclomatic 24), MessageBubbleItemKt.MessageBubbleItem (cyclomatic 22), RegistrationFieldKt.RegistrationField (cyclomatic 22). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 5 together lifts Cyclomatic Complexity from 9.1 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
16 method(s) exceeded the cognitive complexity threshold of 15; the worst was RestorePasswordFieldKt.RestorePasswordField at 49.
What to do
- Bring the 16 bodies over 15 down to 15 or less in Cognitive Complexity — start with RestorePasswordFieldKt.RestorePasswordField (cognitive 49), MessageBubbleItemKt.MessageBubbleItem (cognitive 46), RegistrationFieldKt.RegistrationField (cognitive 37). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 16 together lifts Cognitive Complexity from 7.1 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
18 god class(es) detected.
What to do
- Resolve the 15 MethodTooLong finding(s) in God Classes — start with RecipePostCreationScreen.kt, ForumDiscussionScreen.kt, ChatScreen.kt. — One of this dimension's main actionable groups (15 warning-level).
- Resolve the 2 FileTooLong finding(s) in God Classes — start with Icons.kt, Color.kt. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 ClassTooLong finding(s) in God Classes — start with Color.kt. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
29 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 4 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with FridgeRepositoryImpl.kt (2), AllImagesScreen.kt, PostCreationScreen.kt. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 3 Duplicated block (14 lines × 2) finding(s) in Code Duplication — start with PickProductsDialog.kt, PostCreationScreen.kt, Options.kt. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 Duplicated block (20 lines × 2) finding(s) in Code Duplication — start with CozyTextField.kt (2). — One of this dimension's main actionable groups (2 warning-level).
D5 · Coupling
3 production modules (Gradle), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; edges a convention plugin adds from buildSrc or build-logic are not visible there; 1 module(s) off the main sequence, with abstractness counted on 2 of the 3 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What to do
- Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
D6 · Cohesion (LCOM4)
2 of 24 classes have LCOM4 above 3.
What to do
- Resolve the 2 Low cohesion finding(s) in Cohesion (LCOM4) — start with UserRepositoryImpl.kt, RegistrationViewModel.kt. — One of this dimension's main actionable groups (2 warning-level).
D8 · Code Coverage
No automated tests — no test code was found in this repository.
What to do
- Resolve the 1 No automated tests finding(s) in Code Coverage. — One of this dimension's main actionable groups (1 issue-level).
D12 · Dependency Hygiene
This repository's Gradle dependency graph was RESOLVED BY A BUILD, across every subproject rather than the root alone: 181 artifact(s) resolved, 96 of them gradable against Maven Central, and 88 behind a shipped release. Where a version was requested and a different one won conflict resolution, the RESOLVED version is what is graded — grading the request would recommend an upgrade already applied. Known CVEs in the same graph are a separate question again, reported under D30.
D13 · REDACTED Scanning
REDACTED scan ran and found no leaked secrets.
D14 · License Compliance
0 of 21 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 3 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 21 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 22790 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 ProfileScreen.kt (5), FeedScreen.kt (2), TopicCreationViewModel.kt. — One of this dimension's main actionable groups (13 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 1 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
1 of 2 build units (Gradle) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
1 finding(s): 0 critical, 1 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 1 REDACTED finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
semgrep found no security issues.
D34 · Knowledge Freshness
98 of 98 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is app/src/main/java/ru/tech/cookhelper/presentation/ui/theme/Icons.kt. Counted over 98 of the 278 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 95 Orphaned file finding(s) in Knowledge Freshness — start with RecipePostCreationScreen.kt, ForumDiscussionScreen.kt, Shapes.kt. — One of this dimension's main actionable groups (95 recommendation-level).
- Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with Icons.kt, Color.kt, Swipeable.kt. — One of this dimension's main actionable groups (3 recommendation-level).
- Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
Strongest change-coupling: ProfileScreen.kt↔ImageCarousel.kt 71%; CookHelperApp.kt↔Picture.kt 69%; MessageRepositoryImpl.kt↔ChatScreen.kt 62%
What to do
- Resolve the 3 Change coupling finding(s) in Change Coupling — start with ProfileScreen.kt, PostCreationScreen.kt, RecipePostCreationScreen.kt. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 Change-coupling hub finding(s) in Change Coupling — start with CookHelperApp.kt, ChatScreen.kt. — One of this dimension's main actionable groups (2 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 42 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX4 · Dependency direction
C1 · Data Protection
- No encryption usage (javax.crypto's Cipher in ENCRYPT_MODE, Tink, Jasypt, Spring Security's Encryptors, Jetpack Security's EncryptedSharedPreferences or EncryptedFile, the Android Keystore, SQLCipher, pgcrypto) was found, and this repository persists personal data in the model cited here — sensitive data at rest may be unprotected. If TDE/KMS/vault is delegated to infrastructure, ignore. — app/src/main/java/ru/tech/cookhelper/data/local/entity/UserEntity.kt:16
What to do
- Encrypt sensitive data at rest (open the store encrypted — SQLCipher's SupportFactory for Room, a Realm encryptionKey — or encrypt the fields with Tink's AEAD or an AES/GCM Cipher, or use Jetpack Security's EncryptedSharedPreferences on Android) keeping its key in the Android Keystore or a vault, and manage server-side keys in a vault (AWS KMS / Secrets Manager, GCP KMS / REDACTED Manager, Azure Key Vault, HashiCorp Vault). Skip if delegated to infra (Postgres TDE, KMS, etc.).
- Enforce HTTPS on the server that receives this data: terminate TLS in it (Ktor's sslConnector, Spring's server.ssl and requiresSecure, Netty's SslContextBuilder.forServer) and send Strict-Transport-Security (Ktor's HttpsRedirect), or run it behind a TLS-terminating proxy, so data in transit is always encrypted.
DM11 · Constructible invalid state
- `SettingsEntity`'s public constructor takes `option` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `SettingsEntity` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — app/src/main/java/ru/tech/cookhelper/data/local/entity/SettingsEntity.kt:9
- `UserEntity`'s public constructor takes `email`, `name`, `nickname`, `status`, … as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `UserEntity` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — app/src/main/java/ru/tech/cookhelper/data/local/entity/UserEntity.kt:11
What to do
- Give each aggregate one way in that can refuse — a guarded constructor, value-object parameters that validate themselves, or a private constructor behind a factory that returns a failure.
DM12 · Ambient inputs in the domain
DM6 · Domain ↔ infrastructure boundary
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.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Describe the projects a newcomer cannot place from the root README: 2 of 2 have no README of their own, in their folder or in their family's project (`app`, `dynamic_theme`).
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
What to do
- Start a test surface where your build system looks for one (tests/, test/, spec/, or your ecosystem's test source set) — the separation follows from putting the first tests in the right place.
P1 · CI/CD gates
- No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
What to do
- Add a CI workflow that builds and runs the test suite on every push/PR.
P10 · Library API & versioning
What to do
- Keep implementation types off the public surface (Kotlin: `internal`) — even for a small library, every public type is a stability contract.
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) — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 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.
What to do
- Run what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
PF3 · Async & latency hygiene
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
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
- `catch (_: Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — app/src/main/java/ru/tech/cookhelper/presentation/ui/utils/android/ImageUtils.kt:106
- `catch (e: Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — app/src/main/java/ru/tech/cookhelper/presentation/recipe_post_creation/components/PickProductsWithMeasuresDialog.kt:329
What to do
- Swallowed exception (caught, then discarded)
X30 · Support guard that admits what it rejects
X5 · Nullable reference types
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 74% | Strong | Solid. |
| Architecture | 83% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 38% | Weak — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 19% | Weak — gated by D8, P1, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 41% | Weak — gated by C1 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 70% | Adequate — gated by DM11 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 1 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 5 control(s) we could not find positive evidence for
- C3 Audit Trail — Repo shows no audit-logging mechanism (an audit-log table or model — an Exposed table, a data class, a Room entity or a SQL migration's table named for it — Hibernate Envers' @Audited, a JPA entity listener, Hibernate event listener or jOOQ RecordListener that records each change) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
- C4 Data Retention — Repo shows no data-retention / TTL / cleanup mechanism for personal data — absence of evidence is not evidence of a working control. Define retention periods and a purge/cleanup job (or TTL) in code, or document where retention is enforced, so this dimension can be scored.
- C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 69 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: Dagger rejects, at compile time, a component that holds a binding with a narrower scope than its own.
- 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.
- 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 — the Android app did not build — `./gradlew :app:assembleDebug` exited 1: at java.base/java.lang.Thread.run(Thread.java:1583) FAILURE: Build failed with an exception. * What went wrong: Execution failed for task ':app:kaptGenerateStubsDebugKotlin'. > A failure occurred…; runtime evidence skipped (launch chosen because app/build.gradle.kts applies the Android application plugin and gradlew builds it) This is a statement about this run, not a statement about your application: nothing here says the app is inaccessible, only that it was never run.
- 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.
- D10 Test Quality — No tests were found in the analyzed repository to assess for quality.
- D11 Test Reliability — No test suite was found to re-run, so reliability couldn't be assessed. Two searches produced that zero and both came back empty: the classifier that reads the loaded workspace recognised no suite it could run, and a walk of the source on disk — which covers the JS/TS `*.test.*` and `*.spec.*` conventions and probes for a Pester suite — found no test source in any other ecosystem either. Neither search reaches a suite that is missing from the loaded workspace and carries no name either walk recognises, so this is 'no suite found by those two searches', not a verdict that the repository has none.
- 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 not measured.
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed Kotlin surface was not measured.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .kt, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- 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) — 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) — 2 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
- 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) — 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
- D9 Test Distribution — No test suite could be collected, so there is no unit/integration/end-to-end mix to read. Not applicable: the absence of tests is D8's reading (Code Coverage), and is counted there once.
- 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
- DM2 Strongly-typed ids — no id-bearing domain types detected — strongly-typed-id adoption not assessable
- DM3 Integration-event coupling — no integration events detected — coupling check not applicable
- DM4 Rich vs anemic model — no data-bearing entities detected — rich-vs-anemic model not assessable
- DM5 Encapsulated state — no domain entities found — DM5 grades how entities protect their state, and this repository declares none
- DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
- DM8 Value-object opportunities — not scored — the deterministic rule found 0 candidate clump(s); its rows are withheld until it has a measured precision of 95 % (a sample of fewer than 10 rows cannot show one)
- DM9 Scattered domain decisions — not measured — scattered-decision detection needs expression-level symbol resolution: a comparison operand bound to the member it judges (arm one) and a construction bound to the type it produces (arm two). A Roslyn compilation carries both; arm two alone also runs on any frontend that declares whether a construction is produced or passed, and this target loaded neither
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby 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
- M4 Documentation accuracy — Not applicable: the 1 current-state document(s) make no claim of a kind M4 checks.
- P12 CI test-gate honesty — no CI workflow found
- P2 Observability — This repository's JVM source (2 module(s), 274 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — 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.
- X2 Cancellation propagation — no C# was loaded; this repository's Kotlin was read, and no request in it can be cancelled by a caller (Ktor, OkHttp's newCall or a URL stream, from a suspend function) — a Kotlin request outside a suspend function has no caller's cancellation to honour
- 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.
- X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Kotlin was read, and it logs through none that an assembled message defeats: Android's `Log` and Timber, java.util.logging and log4j-api-kotlin take one finished message (as log4net does in C#), or it makes no call through a named logger at all. Calls made through SLF4J, log4j 2 or kotlin-logging (`LoggerFactory.getLogger`, `KotlinLogging.logger {}`) would be judged.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Serious — 96 finding(s)
- MethodTooLong: RecipePostCreationScreenKt.RecipePostCreationScreen app/src/main/java/ru/tech/cookhelper/presentation/recipe_post_creation/RecipePostCreationScreen.kt:53
- MethodTooLong: ForumDiscussionScreenKt.ForumDiscussionScreen app/src/main/java/ru/tech/cookhelper/presentation/forum_discussion/ForumDiscussionScreen.kt:69
- MethodTooLong: ChatScreenKt.ChatScreen app/src/main/java/ru/tech/cookhelper/presentation/chat/ChatScreen.kt:68
- MethodTooLong: RegistrationFieldKt.RegistrationField app/src/main/java/ru/tech/cookhelper/presentation/registration_screen/RegistrationField.kt:44
- MethodTooLong: TopicCreationScreenKt.TopicCreationScreen app/src/main/java/ru/tech/cookhelper/presentation/topic_creation/TopicCreationScreen.kt:55
- MethodTooLong: PickProductsWithMeasuresDialogKt.PickProductsWithMeasuresDialog app/src/main/java/ru/tech/cookhelper/presentation/recipe_post_creation/components/PickProductsWithMeasuresDialog.kt:48
- MethodTooLong: ForumFilterBottomSheetKt.ForumFilterBottomSheet app/src/main/java/ru/tech/cookhelper/presentation/forum_screen/components/ForumFilterBottomSheet.kt:39
- MethodTooLong: EditProfileScreenKt.EditProfileScreen app/src/main/java/ru/tech/cookhelper/presentation/edit_profile/EditProfileScreen.kt:30
- MethodTooLong: PostCreationScreenKt.PostCreationScreen app/src/main/java/ru/tech/cookhelper/presentation/post_creation/PostCreationScreen.kt:57
- MethodTooLong: RestorePasswordFieldKt.RestorePasswordField app/src/main/java/ru/tech/cookhelper/presentation/restore_password/RestorePasswordField.kt:49
- MethodTooLong: PickProductsDialogKt.PickProductsDialog app/src/main/java/ru/tech/cookhelper/presentation/pick_products/PickProductsDialog.kt:42
- MethodTooLong: ProfileScreenKt.ProfileScreen app/src/main/java/ru/tech/cookhelper/presentation/profile/ProfileScreen.kt:40
- MethodTooLong: AppThemePreviewItemKt.AppThemePreviewItem app/src/main/java/ru/tech/cookhelper/presentation/settings/components/AppThemePreviewItem.kt:22
- MethodTooLong: LoginFieldKt.LoginField app/src/main/java/ru/tech/cookhelper/presentation/login_screen/LoginField.kt:45
- MethodTooLong: MessageBubbleItemKt.MessageBubbleItem app/src/main/java/ru/tech/cookhelper/presentation/chat/components/MessageBubbleItem.kt:23
- TodoComment app/src/main/java/ru/tech/cookhelper/presentation/topic_creation/viewModel/TopicCreationViewModel.kt:55
- TodoComment app/src/main/java/ru/tech/cookhelper/presentation/post_creation/viewModel/PostCreationViewModel.kt:50
- TodoComment app/src/main/java/ru/tech/cookhelper/presentation/recipe_post_creation/viewModel/RecipePostCreationViewModel.kt:62
- TodoComment app/src/main/java/ru/tech/cookhelper/presentation/profile/ProfileScreen.kt:151
- TodoComment app/src/main/java/ru/tech/cookhelper/presentation/feed_screen/FeedScreen.kt:60
- TodoComment app/src/main/java/ru/tech/cookhelper/presentation/profile/ProfileScreen.kt:154
- TodoComment app/src/main/java/ru/tech/cookhelper/presentation/profile/ProfileScreen.kt:157
- TodoComment app/src/main/java/ru/tech/cookhelper/presentation/profile/ProfileScreen.kt:161
- TodoComment app/src/main/java/ru/tech/cookhelper/presentation/profile/ProfileScreen.kt:185
- TodoComment app/src/main/java/ru/tech/cookhelper/presentation/profile/viewModel/ProfileViewModel.kt:48
- TodoComment app/src/main/java/ru/tech/cookhelper/presentation/forum_discussion/ForumDiscussionScreen.kt:284
- TodoComment app/src/main/java/ru/tech/cookhelper/presentation/feed_screen/FeedScreen.kt:57
- TodoComment app/src/main/java/ru/tech/cookhelper/presentation/edit_profile/EditProfileScreen.kt:119
- Duplicated block (10 lines × 2) app/src/main/java/ru/tech/cookhelper/data/repository/FridgeRepositoryImpl.kt:22
- Duplicated block (10 lines × 2) app/src/main/java/ru/tech/cookhelper/data/repository/FridgeRepositoryImpl.kt:39
- Duplicated block (10 lines × 2) app/src/main/java/ru/tech/cookhelper/presentation/all_images/AllImagesScreen.kt:60
- Duplicated block (10 lines × 2) app/src/main/java/ru/tech/cookhelper/presentation/post_creation/PostCreationScreen.kt:62
- Change coupling: ProfileScreen.kt ↔ ImageCarousel.kt app/src/main/java/ru/tech/cookhelper/presentation/profile/ProfileScreen.kt:1
- Change coupling: PostCreationScreen.kt ↔ RecipePostCreationScreen.kt app/src/main/java/ru/tech/cookhelper/presentation/post_creation/PostCreationScreen.kt:1
- Change coupling: RecipePostCreationScreen.kt ↔ PickProductsWithMeasuresDialog.kt app/src/main/java/ru/tech/cookhelper/presentation/recipe_post_creation/RecipePostCreationScreen.kt:1
- Duplicated block (14 lines × 2) app/src/main/java/ru/tech/cookhelper/presentation/pick_products/PickProductsDialog.kt:104
- Duplicated block (14 lines × 2) app/src/main/java/ru/tech/cookhelper/presentation/post_creation/PostCreationScreen.kt:257
- Duplicated block (14 lines × 2) app/src/main/java/ru/tech/cookhelper/presentation/settings/components/Options.kt:54
- FileTooLong: theme/Icons.kt app/src/main/java/ru/tech/cookhelper/presentation/ui/theme/Icons.kt
- FileTooLong: theme/Color.kt app/src/main/java/ru/tech/cookhelper/presentation/ui/theme/Color.kt
- Change-coupling hub: CookHelperApp.kt → ImageCarousel.kt, SettingsScreen.kt, Picture.kt app/src/main/java/ru/tech/cookhelper/presentation/app/components/CookHelperApp.kt
- Change-coupling hub: ChatScreen.kt → MessageRepositoryImpl.kt, AllImagesScreen.kt, ChatListViewModel.kt app/src/main/java/ru/tech/cookhelper/presentation/chat/ChatScreen.kt
- Duplicated block (20 lines × 2) app/src/main/java/ru/tech/cookhelper/presentation/ui/widgets/CozyTextField.kt:87
- Duplicated block (20 lines × 2) app/src/main/java/ru/tech/cookhelper/presentation/ui/widgets/CozyTextField.kt:181
- Low cohesion: UserRepositoryImpl (LCOM4 4) app/src/main/java/ru/tech/cookhelper/data/repository/UserRepositoryImpl.kt:34
- Low cohesion: RegistrationViewModel (LCOM4 4) app/src/main/java/ru/tech/cookhelper/presentation/registration_screen/viewModel/RegistrationViewModel.kt:47
- Constructible in an invalid state: SettingsEntity app/src/main/java/ru/tech/cookhelper/data/local/entity/SettingsEntity.kt:9
- Constructible in an invalid state: UserEntity app/src/main/java/ru/tech/cookhelper/data/local/entity/UserEntity.kt:11
- Swallowed exception (caught, then discarded) app/src/main/java/ru/tech/cookhelper/presentation/ui/utils/android/ImageUtils.kt:106
- Swallowed exception (caught, then discarded) app/src/main/java/ru/tech/cookhelper/presentation/recipe_post_creation/components/PickProductsWithMeasuresDialog.kt:329
- No data-protection/encryption app/src/main/java/ru/tech/cookhelper/data/local/entity/UserEntity.kt:16
- RestorePasswordFieldKt.RestorePasswordField (cyclomatic 24) app/src/main/java/ru/tech/cookhelper/presentation/restore_password/RestorePasswordField.kt:49
- MessageBubbleItemKt.MessageBubbleItem (cyclomatic 22) app/src/main/java/ru/tech/cookhelper/presentation/chat/components/MessageBubbleItem.kt:23
- RegistrationFieldKt.RegistrationField (cyclomatic 22) app/src/main/java/ru/tech/cookhelper/presentation/registration_screen/RegistrationField.kt:44
- ChatScreenKt.ChatScreen (cyclomatic 21) app/src/main/java/ru/tech/cookhelper/presentation/chat/ChatScreen.kt:68
- OTPFieldKt.OTPField (cyclomatic 17) app/src/main/java/ru/tech/cookhelper/presentation/authentication/components/OTPField.kt:38
- RestorePasswordFieldKt.RestorePasswordField (cognitive 49) app/src/main/java/ru/tech/cookhelper/presentation/restore_password/RestorePasswordField.kt:49
- MessageBubbleItemKt.MessageBubbleItem (cognitive 46) app/src/main/java/ru/tech/cookhelper/presentation/chat/components/MessageBubbleItem.kt:23
- RegistrationFieldKt.RegistrationField (cognitive 37) app/src/main/java/ru/tech/cookhelper/presentation/registration_screen/RegistrationField.kt:44
- PickProductsWithMeasuresDialogKt.PickProductsWithMeasuresDialog (cognitive 32) app/src/main/java/ru/tech/cookhelper/presentation/recipe_post_creation/components/PickProductsWithMeasuresDialog.kt:48
- ChatScreenKt.ChatScreen (cognitive 31) app/src/main/java/ru/tech/cookhelper/presentation/chat/ChatScreen.kt:68
- ImageUtils.blur (cognitive 29) app/src/main/java/ru/tech/cookhelper/presentation/ui/utils/android/ImageUtils.kt:112
- OTPFieldKt.OTPField (cognitive 26) app/src/main/java/ru/tech/cookhelper/presentation/authentication/components/OTPField.kt:38
- SwipeableKt.computeTarget (cognitive 23) app/src/main/java/ru/tech/cookhelper/presentation/ui/widgets/bottomsheet/Swipeable.kt:717
- PickProductsDialogKt.PickProductsDialog (cognitive 20) app/src/main/java/ru/tech/cookhelper/presentation/pick_products/PickProductsDialog.kt:42
- LoginFieldKt.LoginField (cognitive 19) app/src/main/java/ru/tech/cookhelper/presentation/login_screen/LoginField.kt:45
- FridgeScreenKt.FridgeScreen (cognitive 16) app/src/main/java/ru/tech/cookhelper/presentation/fridge_screen/FridgeScreen.kt:42
- RoundedTextFieldKt.RoundedTextField (cognitive 16) app/src/main/java/ru/tech/cookhelper/presentation/recipe_post_creation/components/RoundedTextField.kt:107
- RoundedTextFieldKt.RoundedTextFieldColors (cognitive 16) app/src/main/java/ru/tech/cookhelper/presentation/recipe_post_creation/components/RoundedTextField.kt:225
- ToggleGroupButtonKt.ToggleGroupButton (cognitive 16) app/src/main/java/ru/tech/cookhelper/presentation/settings/components/ToggleGroupButton.kt:20
- ContextUtils.getLanguages (cognitive 16) app/src/main/java/ru/tech/cookhelper/presentation/ui/utils/android/ContextUtils.kt:58
- PictureKt.Picture (cognitive 16) app/src/main/java/ru/tech/cookhelper/presentation/ui/widgets/Picture.kt:37
- ClassTooLong: ColorScheme app/src/main/java/ru/tech/cookhelper/presentation/ui/theme/Color.kt:12
- Near-duplicate member pair (151 shared lines) app/src/main/java/ru/tech/cookhelper/presentation/post_creation/PostCreationScreen.kt:61
- Duplicated block (50 lines × 2) app/src/main/java/ru/tech/cookhelper/presentation/post_creation/PostCreationScreen.kt:181
- Duplicated block (42 lines × 2) app/src/main/java/ru/tech/cookhelper/presentation/forum_screen/components/TabRow.kt:59
- Duplicated block (31–32 lines × 2) app/src/main/java/ru/tech/cookhelper/presentation/forum_discussion/ForumDiscussionScreen.kt:130
- Duplicated block (28–31 lines × 3) app/src/main/java/ru/tech/cookhelper/presentation/post_creation/PostCreationScreen.kt:90
- Duplicated block (31 lines × 2) dynamic_theme/src/main/java/com/cookhelper/dynamic/theme/DynamicTheme.kt:103
- Duplicated block (26 lines × 2) app/src/main/java/ru/tech/cookhelper/presentation/login_screen/LoginField.kt:166
- Duplicated block (23–24 lines × 2) app/src/main/java/ru/tech/cookhelper/presentation/pick_products/PickProductsDialog.kt:148
- Duplicated block (21–22 lines × 3) app/src/main/java/ru/tech/cookhelper/presentation/post_creation/PostCreationScreen.kt:208
- Duplicated block (21–22 lines × 2) app/src/main/java/ru/tech/cookhelper/presentation/login_screen/viewModel/LoginViewModel.kt:68
- Duplicated block (22 lines × 2) app/src/main/java/ru/tech/cookhelper/presentation/recipe_post_creation/components/RoundedTextField.kt:175
- Duplicated block (21 lines × 2) app/src/main/java/ru/tech/cookhelper/presentation/registration_screen/RegistrationField.kt:222
- Duplicated block (18 lines × 3) app/src/main/java/ru/tech/cookhelper/presentation/recipe_post_creation/components/RoundedTextField.kt:185
- Duplicated block (18 lines × 2) app/src/main/java/ru/tech/cookhelper/presentation/post_creation/PostCreationScreen.kt:139
- Duplicated block (16–17 lines × 2) app/src/main/java/ru/tech/cookhelper/presentation/confirm_email/ConfirmEmailField.kt:105
- Duplicated block (16 lines × 2) app/src/main/java/ru/tech/cookhelper/presentation/post_creation/PostCreationScreen.kt:158
- Duplicated block (15 lines × 2) app/src/main/java/ru/tech/cookhelper/presentation/post_creation/PostCreationScreen.kt:122
- Duplicated block (13–14 lines × 4) app/src/main/java/ru/tech/cookhelper/presentation/login_screen/LoginField.kt:120
- Duplicated block (12–13 lines × 2) app/src/main/java/ru/tech/cookhelper/presentation/chat/components/MessageBubbleItem.kt:128
- Duplicated block (7 lines × 2) app/src/main/java/ru/tech/cookhelper/data/repository/UserRepositoryImpl.kt:78
- Duplicated block (5 lines × 3) app/src/main/java/ru/tech/cookhelper/data/repository/UserRepositoryImpl.kt:64
- Off the main sequence: :dynamic_theme
- No CI pipeline
Minor — 107 finding(s)
- Orphaned file app/src/main/java/ru/tech/cookhelper/presentation/recipe_post_creation/RecipePostCreationScreen.kt:1
- Orphaned file app/src/main/java/ru/tech/cookhelper/presentation/forum_discussion/ForumDiscussionScreen.kt:1
- Orphaned file app/src/main/java/ru/tech/cookhelper/presentation/ui/theme/Shapes.kt:1
- Orphaned file app/src/main/java/ru/tech/cookhelper/presentation/chat/ChatScreen.kt:1
- Orphaned file app/src/main/java/ru/tech/cookhelper/presentation/recipe_post_creation/components/PickProductsWithMeasuresDialog.kt:1
- Orphaned file app/src/main/java/ru/tech/cookhelper/presentation/settings/components/Options.kt:1
- Orphaned file app/src/main/java/ru/tech/cookhelper/presentation/registration_screen/RegistrationField.kt:1
- Orphaned file app/src/main/java/ru/tech/cookhelper/presentation/topic_creation/TopicCreationScreen.kt:1
- Orphaned file app/src/main/java/ru/tech/cookhelper/presentation/settings/components/ColorSchemePreview.kt:1
- Orphaned file app/src/main/java/ru/tech/cookhelper/presentation/forum_screen/components/ForumFilterBottomSheet.kt:1
- Orphaned file app/src/main/java/ru/tech/cookhelper/presentation/ui/widgets/bottomsheet/ModalBottomSheet.kt:1
- Orphaned file app/src/main/java/ru/tech/cookhelper/presentation/ui/widgets/zooomable/Zoomable.kt:1
- Orphaned file app/src/main/java/ru/tech/cookhelper/presentation/ui/utils/android/ImageUtils.kt:1
- Orphaned file app/src/main/java/ru/tech/cookhelper/presentation/post_creation/PostCreationScreen.kt:1
- Orphaned file app/src/main/java/ru/tech/cookhelper/presentation/restore_password/RestorePasswordField.kt:1
- Orphaned file app/src/main/java/ru/tech/cookhelper/presentation/ui/widgets/CozyTextField.kt:1
- Orphaned file app/src/main/java/ru/tech/cookhelper/presentation/edit_profile/EditProfileScreen.kt:1
- Orphaned file app/src/main/java/ru/tech/cookhelper/presentation/pick_products/PickProductsDialog.kt:1
- Orphaned file app/src/main/java/ru/tech/cookhelper/presentation/settings/components/ColorDialog.kt:1
- Orphaned file app/src/main/java/ru/tech/cookhelper/presentation/registration_screen/viewModel/RegistrationViewModel.kt:1
- Orphaned file app/src/main/java/ru/tech/cookhelper/presentation/recipe_post_creation/components/RoundedTextField.kt:1
- Orphaned file app/src/main/java/ru/tech/cookhelper/presentation/profile/ProfileScreen.kt:1
- Orphaned file app/src/main/java/ru/tech/cookhelper/data/repository/UserRepositoryImpl.kt:1
- Orphaned file app/src/main/java/ru/tech/cookhelper/presentation/recipe_details/RecipeDetailsScreen.kt:1
- Orphaned file app/src/main/java/ru/tech/cookhelper/presentation/login_screen/LoginField.kt:1
- Most significant orphaned file app/src/main/java/ru/tech/cookhelper/presentation/ui/theme/Icons.kt:1
- Most significant orphaned file app/src/main/java/ru/tech/cookhelper/presentation/ui/theme/Color.kt:1
- Most significant orphaned file app/src/main/java/ru/tech/cookhelper/presentation/ui/widgets/bottomsheet/Swipeable.kt:1
- No ADRs found
- Projects may be oversized for their cohesion
- REDACTED
- Dormant codebase
- No ADRs
- No architecture diagram/doc
- No SAST
- No changelog
- Duplicated predicate app/src/main/java/ru/tech/cookhelper/presentation/registration_screen/RegistrationField.kt:240
Minor — 88 finding(s)
- Outdated (compile): org.jacoco:org.jacoco.ant
- Outdated (compile): org.jacoco:org.jacoco.core
- Outdated (compile): org.ow2.asm:asm
- Outdated (compile): org.ow2.asm:asm-commons
- Outdated (compile): org.ow2.asm:asm-tree
- Outdated (compile): org.ow2.asm:asm-analysis
- Outdated (compile): org.jacoco:org.jacoco.report
- Outdated (compile): org.jacoco:org.jacoco.agent
- Outdated (compile): org.jetbrains.kotlin:kotlin-stdlib-jdk8
- Outdated (compile): org.jetbrains.kotlin:kotlin-stdlib
- Outdated (compile): org.jetbrains.kotlin:kotlin-stdlib-common
- Outdated (compile): org.jetbrains:annotations
- Outdated (compile): org.jetbrains.kotlin:kotlin-stdlib-jdk7
- Outdated (compile): com.google.dagger:hilt-android-compiler
- Outdated (compile): com.google.dagger:dagger
- Outdated (compile): com.google.dagger:dagger-compiler
- Outdated (compile): com.google.dagger:dagger-producers
- Outdated (compile): com.google.guava:failureaccess
- Outdated (compile): com.google.guava:guava
- Outdated (compile): org.checkerframework:checker-qual
- Outdated (compile): com.google.errorprone:error_prone_annotations
- Outdated (compile): com.google.j2objc:j2objc-annotations
- Outdated (compile): org.checkerframework:checker-compat-qual
- Outdated (compile): com.google.dagger:dagger-spi
- Outdated (compile): com.google.devtools.ksp:symbol-processing-api
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-81d14dac08624f3a89066929a811358d/history.json --exit-code 0 --source . | 1 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-81d14dac08624f3a89066929a811358d/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 . | 0 | 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) — 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 2 file(s) — `app/src/main/java/ru/tech/cookhelper/core/Action.kt`, `app/src/main/java/ru/tech/cookhelper/presentation/settings/components/SettingsState.kt` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D36 · Supply-chain Provenance & Signing | provenance | — | provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for. | 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) — not scanned yet). | 0 | — |