Executive summary
lneugebauer/nextcloud-cookbook falls short of our standard for a preview release because we found no automated security scanning of the code, its secrets or its dependencies. It scores 60.5 out of 100 and is rated Adequate, and all 13 of its critical findings are security problems in the build pipeline and in the packages it uses.
Production Readiness, at 47.7, is the weakest lens and counts most in the score. The best first step is adding automated security scanning, worth about 9.0 points. Improving the documentation comes next, worth about 3.9 points. Raising Production Readiness to 62 would lift the score to about 67.1.
Six known security holes in the packages the code depends on can be used by attackers. Six pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and one secret can leak from the build pipeline. Updating the vulnerable packages, pinning each tool to an exact version and limiting the secret to its own step would close these risks.
The product code is 12,544 lines, about €19,000 to rebuild.
If Production Readiness rose from 47.7 to 62, the lowest score rated Strong, the score would rise from 60.5 to about 67.1.
Rebuild cost: about €19,000 · Estimate
| Cost to rebuild | €6,200 to €31,000, for 104 to 328 hours of work, about 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 61. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 12,544 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture: which parts of the code depend on which
| uses → | 1 auth.domain.state | 2 category.domain.model | 3 core.data.remote.response | 4 core.domain.model | 5 auth.domain.model | 6 category.data.dto | 7 recipe.domain.model | 8 auth.data.remote.response | 9 recipe.domain | 10 recipe.domain.dao | 11 recipe.domain.util | 12 core.data | 13 core.util | 14 auth.data.api | 15 auth.domain.repository | 16 auth.presentation.start | 17 category.domain.repository | 18 core.domain.repository | 19 recipe.data.dto | 20 recipe.domain.state | 21 auth.data.repository | 22 auth.presentation.splash | 23 category.data.repository | 24 core.data.api | 25 core.domain.usecase | 26 recipe.domain.repository | 27 recipe.domain.state.RecipeCreateEditState | 28 auth.presentation.browser | 29 auth.presentation.manual | 30 core.data.repository | 31 di | 32 recipe.data.repository | 33 recipe.domain.usecase | 34 recipe.presentation.detail | 35 recipe.presentation.list | 36 settings.presentation.settings | 37 recipe.util | 38 recipe.presentation.create | 39 recipe.presentation.download | 40 recipe.presentation.edit |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 auth.domain.state | ||||||||||||||||||||||||||||||||||||||||
| 2 category.domain.model | ||||||||||||||||||||||||||||||||||||||||
| 3 core.data.remote.response | ||||||||||||||||||||||||||||||||||||||||
| 4 core.domain.model | ||||||||||||||||||||||||||||||||||||||||
| 5 auth.domain.model | 1 | |||||||||||||||||||||||||||||||||||||||
| 6 category.data.dto | 1 | |||||||||||||||||||||||||||||||||||||||
| 7 recipe.domain.model | 1 | |||||||||||||||||||||||||||||||||||||||
| 8 auth.data.remote.response | 2 | |||||||||||||||||||||||||||||||||||||||
| 9 recipe.domain | 2 | |||||||||||||||||||||||||||||||||||||||
| 10 recipe.domain.dao | 3 | |||||||||||||||||||||||||||||||||||||||
| 11 recipe.domain.util | 1 | |||||||||||||||||||||||||||||||||||||||
| 12 core.data | 2 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 13 core.util | 1 | |||||||||||||||||||||||||||||||||||||||
| 14 auth.data.api | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 15 auth.domain.repository | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 16 auth.presentation.start | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 17 category.domain.repository | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 18 core.domain.repository | 4 | 2 | ||||||||||||||||||||||||||||||||||||||
| 19 recipe.data.dto | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 20 recipe.domain.state | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 21 auth.data.repository | 2 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 22 auth.presentation.splash | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 23 category.data.repository | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 24 core.data.api | 3 | 1 | 1 | 1 | 1 | 3 | ||||||||||||||||||||||||||||||||||
| 25 core.domain.usecase | 1 | 1 | 1 | 1 | 6 | |||||||||||||||||||||||||||||||||||
| 26 recipe.domain.repository | 3 | 2 | 2 | |||||||||||||||||||||||||||||||||||||
| 27 recipe.domain.state.RecipeCreateEditState | 1 | 2 | 2 | 5 | ||||||||||||||||||||||||||||||||||||
| 28 auth.presentation.browser | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 29 auth.presentation.manual | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 30 core.data.repository | 4 | 1 | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||
| 31 di | 1 | 2 | 4 | 4 | 1 | 1 | 1 | 1 | 3 | 3 | 1 | |||||||||||||||||||||||||||||
| 32 recipe.data.repository | 1 | 1 | 3 | 1 | 2 | 1 | 3 | 1 | 1 | |||||||||||||||||||||||||||||||
| 33 recipe.domain.usecase | 1 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 34 recipe.presentation.detail | 7 | 2 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 35 recipe.presentation.list | 3 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 36 settings.presentation.settings | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 37 recipe.util | 1 | 3 | 1 | 1 | 1 | 3 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||
| 38 recipe.presentation.create | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 39 recipe.presentation.download | 1 | 2 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 40 recipe.presentation.edit | 1 | 1 | 1 | 1 | 1 |
5→4 auth.domain.model uses core.domain.model✕
- Connections
- 1 pair of types, where a type in auth.domain.model uses a type in core.domain.model.
- The types involved
de.lukasneugebauer.nextcloudcookbook.auth.domain.model.LoginResult→de.lukasneugebauer.nextcloudcookbook.core.domain.model.NcAccount
- Direction
- auth.domain.model uses core.domain.model, so a change to core.domain.model can break auth.domain.model, while a change to auth.domain.model can't break core.domain.model.
- Position
- Below the diagonal: auth.domain.model uses a module listed above it, which is the healthy direction.
6→2 category.data.dto uses category.domain.model✕
- Connections
- 1 pair of types, where a type in category.data.dto uses a type in category.domain.model.
- The types involved
de.lukasneugebauer.nextcloudcookbook.category.data.dto.CategoryDto→de.lukasneugebauer.nextcloudcookbook.category.domain.model.Category
- Direction
- category.data.dto uses category.domain.model, so a change to category.domain.model can break category.data.dto, while a change to category.data.dto can't break category.domain.model.
- Position
- Below the diagonal: category.data.dto uses a module listed above it, which is the healthy direction.
7→13 recipe.domain.model uses core.util part of a loop✕
- Connections
- 1 pair of types, where a type in recipe.domain.model uses a type in core.util.
- The types involved
de.lukasneugebauer.nextcloudcookbook.recipe.domain.model.RecipeListScreenFlowData→de.lukasneugebauer.nextcloudcookbook.core.util.DataResult
- Direction
- recipe.domain.model uses core.util, so a change to core.util can break recipe.domain.model, while a change to recipe.domain.model can't break core.util.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→5 auth.data.remote.response uses auth.domain.model✕
- Connections
- 2 pairs of types, where a type in auth.data.remote.response uses a type in auth.domain.model.
- The types involved
de.lukasneugebauer.nextcloudcookbook.auth.data.remote.response.LoginEndpointResponse→de.lukasneugebauer.nextcloudcookbook.auth.domain.model.LoginEndpointResultde.lukasneugebauer.nextcloudcookbook.auth.data.remote.response.LoginResponse→de.lukasneugebauer.nextcloudcookbook.auth.domain.model.LoginResult
- Direction
- auth.data.remote.response uses auth.domain.model, so a change to auth.domain.model can break auth.data.remote.response, while a change to auth.data.remote.response can't break auth.domain.model.
- Position
- Below the diagonal: auth.data.remote.response uses a module listed above it, which is the healthy direction.
9→7 recipe.domain uses recipe.domain.model✕
- Connections
- 2 pairs of types, where a type in recipe.domain uses a type in recipe.domain.model.
- The types involved
de.lukasneugebauer.nextcloudcookbook.recipe.domain.RecipeFormatter→de.lukasneugebauer.nextcloudcookbook.recipe.domain.model.Recipede.lukasneugebauer.nextcloudcookbook.recipe.domain.YieldCalculator→de.lukasneugebauer.nextcloudcookbook.recipe.domain.model.CalculatedIngredient
- Direction
- recipe.domain uses recipe.domain.model, so a change to recipe.domain.model can break recipe.domain, while a change to recipe.domain can't break recipe.domain.model.
- Position
- Below the diagonal: recipe.domain uses a module listed above it, which is the healthy direction.
10→7 recipe.domain.dao uses recipe.domain.model✕
- Connections
- 3 pairs of types, where a type in recipe.domain.dao uses a type in recipe.domain.model.
- The types involved
de.lukasneugebauer.nextcloudcookbook.recipe.domain.dao.RecipeDao→de.lukasneugebauer.nextcloudcookbook.recipe.domain.model.RecipeEntityde.lukasneugebauer.nextcloudcookbook.recipe.domain.dao.RecipeDao→de.lukasneugebauer.nextcloudcookbook.recipe.domain.model.RecipeSyncStatede.lukasneugebauer.nextcloudcookbook.recipe.domain.dao.RecipePreviewDao→de.lukasneugebauer.nextcloudcookbook.recipe.domain.model.RecipePreviewEntity
- Direction
- recipe.domain.dao uses recipe.domain.model, so a change to recipe.domain.model can break recipe.domain.dao, while a change to recipe.domain.dao can't break recipe.domain.model.
- Position
- Below the diagonal: recipe.domain.dao uses a module listed above it, which is the healthy direction.
11→7 recipe.domain.util uses recipe.domain.model✕
- Connections
- 1 pair of types, where a type in recipe.domain.util uses a type in recipe.domain.model.
- The types involved
de.lukasneugebauer.nextcloudcookbook.recipe.domain.util.ImageCompressionService→de.lukasneugebauer.nextcloudcookbook.recipe.domain.model.RecipeImageUpload
- Direction
- recipe.domain.util uses recipe.domain.model, so a change to recipe.domain.model can break recipe.domain.util, while a change to recipe.domain.util can't break recipe.domain.model.
- Position
- Below the diagonal: recipe.domain.util uses a module listed above it, which is the healthy direction.
12→4 core.data uses core.domain.model✕
- Connections
- 2 pairs of types, where a type in core.data uses a type in core.domain.model.
- The types involved
de.lukasneugebauer.nextcloudcookbook.core.data.PreferencesManager→de.lukasneugebauer.nextcloudcookbook.core.domain.model.NcAccountde.lukasneugebauer.nextcloudcookbook.core.data.PreferencesManager→de.lukasneugebauer.nextcloudcookbook.core.domain.model.RecipeOfTheDay
- Direction
- core.data uses core.domain.model, so a change to core.domain.model can break core.data, while a change to core.data can't break core.domain.model.
- Position
- Below the diagonal: core.data uses a module listed above it, which is the healthy direction.
12→10 core.data uses recipe.domain.dao✕
- Connections
- 2 pairs of types, where a type in core.data uses a type in recipe.domain.dao.
- The types involved
de.lukasneugebauer.nextcloudcookbook.core.data.CookbookDatabase→de.lukasneugebauer.nextcloudcookbook.recipe.domain.dao.RecipeDaode.lukasneugebauer.nextcloudcookbook.core.data.CookbookDatabase→de.lukasneugebauer.nextcloudcookbook.recipe.domain.dao.RecipePreviewDao
- Direction
- core.data uses recipe.domain.dao, so a change to recipe.domain.dao can break core.data, while a change to core.data can't break recipe.domain.dao.
- Position
- Below the diagonal: core.data uses a module listed above it, which is the healthy direction.
12→13 core.data uses core.util part of a loop✕
- Connections
- 1 pair of types, where a type in core.data uses a type in core.util.
- The types involved
de.lukasneugebauer.nextcloudcookbook.core.data.StoreReadResponseExtensionsKt→de.lukasneugebauer.nextcloudcookbook.core.util.DataResult
- Direction
- core.data uses core.util, so a change to core.util can break core.data, while a change to core.data can't break core.util.
- 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→12 core.util uses core.data✕
- Connections
- 1 pair of types, where a type in core.util uses a type in core.data.
- The types involved
de.lukasneugebauer.nextcloudcookbook.core.util.OkHttpClientProvider→de.lukasneugebauer.nextcloudcookbook.core.data.PreferencesManager
- Direction
- core.util uses core.data, so a change to core.data can break core.util, while a change to core.util can't break core.data.
- Position
- Below the diagonal: core.util uses a module listed above it, which is the healthy direction.
14→8 auth.data.api uses auth.data.remote.response✕
- Connections
- 2 pairs of types, where a type in auth.data.api uses a type in auth.data.remote.response.
- The types involved
de.lukasneugebauer.nextcloudcookbook.auth.data.api.AuthApi→de.lukasneugebauer.nextcloudcookbook.auth.data.remote.response.LoginEndpointResponsede.lukasneugebauer.nextcloudcookbook.auth.data.api.AuthApi→de.lukasneugebauer.nextcloudcookbook.auth.data.remote.response.LoginResponse
- Direction
- auth.data.api uses auth.data.remote.response, so a change to auth.data.remote.response can break auth.data.api, while a change to auth.data.api can't break auth.data.remote.response.
- Position
- Below the diagonal: auth.data.api uses a module listed above it, which is the healthy direction.
14→13 auth.data.api uses core.util✕
- Connections
- 1 pair of types, where a type in auth.data.api uses a type in core.util.
- The types involved
de.lukasneugebauer.nextcloudcookbook.auth.data.api.AuthApiProvider→de.lukasneugebauer.nextcloudcookbook.core.util.OkHttpClientProvider
- Direction
- auth.data.api uses core.util, so a change to core.util can break auth.data.api, while a change to auth.data.api can't break core.util.
- Position
- Below the diagonal: auth.data.api uses a module listed above it, which is the healthy direction.
15→5 auth.domain.repository uses auth.domain.model✕
- Connections
- 2 pairs of types, where a type in auth.domain.repository uses a type in auth.domain.model.
- The types involved
de.lukasneugebauer.nextcloudcookbook.auth.domain.repository.AuthRepository→de.lukasneugebauer.nextcloudcookbook.auth.domain.model.LoginEndpointResultde.lukasneugebauer.nextcloudcookbook.auth.domain.repository.AuthRepository→de.lukasneugebauer.nextcloudcookbook.auth.domain.model.LoginResult
- Direction
- auth.domain.repository uses auth.domain.model, so a change to auth.domain.model can break auth.domain.repository, while a change to auth.domain.repository can't break auth.domain.model.
- Position
- Below the diagonal: auth.domain.repository uses a module listed above it, which is the healthy direction.
15→13 auth.domain.repository uses core.util✕
- Connections
- 1 pair of types, where a type in auth.domain.repository uses a type in core.util.
- The types involved
de.lukasneugebauer.nextcloudcookbook.auth.domain.repository.AuthRepository→de.lukasneugebauer.nextcloudcookbook.core.util.Resource
- Direction
- auth.domain.repository uses core.util, so a change to core.util can break auth.domain.repository, while a change to auth.domain.repository can't break core.util.
- Position
- Below the diagonal: auth.domain.repository uses a module listed above it, which is the healthy direction.
16→1 auth.presentation.start uses auth.domain.state✕
- Connections
- 2 pairs of types, where a type in auth.presentation.start uses a type in auth.domain.state.
- The types involved
de.lukasneugebauer.nextcloudcookbook.auth.presentation.start.StartScreenViewModel→de.lukasneugebauer.nextcloudcookbook.auth.domain.state.StartScreenSignInEventde.lukasneugebauer.nextcloudcookbook.auth.presentation.start.StartScreenViewModel→de.lukasneugebauer.nextcloudcookbook.auth.domain.state.StartScreenState
- Direction
- auth.presentation.start uses auth.domain.state, so a change to auth.domain.state can break auth.presentation.start, while a change to auth.presentation.start can't break auth.domain.state.
- Position
- Below the diagonal: auth.presentation.start uses a module listed above it, which is the healthy direction.
16→12 auth.presentation.start uses core.data✕
- Connections
- 1 pair of types, where a type in auth.presentation.start uses a type in core.data.
- The types involved
de.lukasneugebauer.nextcloudcookbook.auth.presentation.start.StartScreenViewModel→de.lukasneugebauer.nextcloudcookbook.core.data.PreferencesManager
- Direction
- auth.presentation.start uses core.data, so a change to core.data can break auth.presentation.start, while a change to auth.presentation.start can't break core.data.
- Position
- Below the diagonal: auth.presentation.start uses a module listed above it, which is the healthy direction.
16→13 auth.presentation.start uses core.util✕
- Connections
- 1 pair of types, where a type in auth.presentation.start uses a type in core.util.
- The types involved
de.lukasneugebauer.nextcloudcookbook.auth.presentation.start.StartScreenKt→de.lukasneugebauer.nextcloudcookbook.core.util.UiText
- Direction
- auth.presentation.start uses core.util, so a change to core.util can break auth.presentation.start, while a change to auth.presentation.start can't break core.util.
- Position
- Below the diagonal: auth.presentation.start uses a module listed above it, which is the healthy direction.
17→2 category.domain.repository uses category.domain.model✕
- Connections
- 1 pair of types, where a type in category.domain.repository uses a type in category.domain.model.
- The types involved
de.lukasneugebauer.nextcloudcookbook.category.domain.repository.CategoryRepository→de.lukasneugebauer.nextcloudcookbook.category.domain.model.Category
- Direction
- category.domain.repository uses category.domain.model, so a change to category.domain.model can break category.domain.repository, while a change to category.domain.repository can't break category.domain.model.
- Position
- Below the diagonal: category.domain.repository uses a module listed above it, which is the healthy direction.
17→13 category.domain.repository uses core.util✕
- Connections
- 1 pair of types, where a type in category.domain.repository uses a type in core.util.
- The types involved
de.lukasneugebauer.nextcloudcookbook.category.domain.repository.CategoryRepository→de.lukasneugebauer.nextcloudcookbook.core.util.DataResult
- Direction
- category.domain.repository uses core.util, so a change to core.util can break category.domain.repository, while a change to category.domain.repository can't break core.util.
- Position
- Below the diagonal: category.domain.repository uses a module listed above it, which is the healthy direction.
18→4 core.domain.repository uses core.domain.model✕
- Connections
- 4 pairs of types, where a type in core.domain.repository uses a type in core.domain.model.
- The types involved
de.lukasneugebauer.nextcloudcookbook.core.domain.repository.AccountRepository→de.lukasneugebauer.nextcloudcookbook.core.domain.model.Capabilitiesde.lukasneugebauer.nextcloudcookbook.core.domain.repository.AccountRepository→de.lukasneugebauer.nextcloudcookbook.core.domain.model.CookbookVersionde.lukasneugebauer.nextcloudcookbook.core.domain.repository.AccountRepository→de.lukasneugebauer.nextcloudcookbook.core.domain.model.NcAccountde.lukasneugebauer.nextcloudcookbook.core.domain.repository.AccountRepository→de.lukasneugebauer.nextcloudcookbook.core.domain.model.UserMetadata
- Direction
- core.domain.repository uses core.domain.model, so a change to core.domain.model can break core.domain.repository, while a change to core.domain.repository can't break core.domain.model.
- Position
- Below the diagonal: core.domain.repository uses a module listed above it, which is the healthy direction.
18→13 core.domain.repository uses core.util✕
- Connections
- 2 pairs of types, where a type in core.domain.repository uses a type in core.util.
- The types involved
de.lukasneugebauer.nextcloudcookbook.core.domain.repository.AccountRepository→de.lukasneugebauer.nextcloudcookbook.core.util.Resourcede.lukasneugebauer.nextcloudcookbook.core.domain.repository.BaseRepository→de.lukasneugebauer.nextcloudcookbook.core.util.UiText
- Direction
- core.domain.repository uses core.util, so a change to core.util can break core.domain.repository, while a change to core.domain.repository can't break core.util.
- Position
- Below the diagonal: core.domain.repository uses a module listed above it, which is the healthy direction.
19→7 recipe.data.dto uses recipe.domain.model✕
- Connections
- 3 pairs of types, where a type in recipe.data.dto uses a type in recipe.domain.model.
- The types involved
de.lukasneugebauer.nextcloudcookbook.recipe.data.dto.NutritionDto→de.lukasneugebauer.nextcloudcookbook.recipe.domain.model.Nutritionde.lukasneugebauer.nextcloudcookbook.recipe.data.dto.RecipeDto→de.lukasneugebauer.nextcloudcookbook.recipe.domain.model.Recipede.lukasneugebauer.nextcloudcookbook.recipe.data.dto.RecipePreviewDto→de.lukasneugebauer.nextcloudcookbook.recipe.domain.model.RecipePreview
- Direction
- recipe.data.dto uses recipe.domain.model, so a change to recipe.domain.model can break recipe.data.dto, while a change to recipe.data.dto can't break recipe.domain.model.
- Position
- Below the diagonal: recipe.data.dto uses a module listed above it, which is the healthy direction.
19→13 recipe.data.dto uses core.util✕
- Connections
- 1 pair of types, where a type in recipe.data.dto uses a type in core.util.
- The types involved
de.lukasneugebauer.nextcloudcookbook.recipe.data.dto.RecipeConflictDto→de.lukasneugebauer.nextcloudcookbook.core.util.UiText
- Direction
- recipe.data.dto uses core.util, so a change to core.util can break recipe.data.dto, while a change to recipe.data.dto can't break core.util.
- Position
- Below the diagonal: recipe.data.dto uses a module listed above it, which is the healthy direction.
20→7 recipe.domain.state uses recipe.domain.model✕
- Connections
- 2 pairs of types, where a type in recipe.domain.state uses a type in recipe.domain.model.
- The types involved
de.lukasneugebauer.nextcloudcookbook.recipe.domain.state.RecipeDetailState→de.lukasneugebauer.nextcloudcookbook.recipe.domain.model.CalculatedIngredientde.lukasneugebauer.nextcloudcookbook.recipe.domain.state.RecipeDetailState→de.lukasneugebauer.nextcloudcookbook.recipe.domain.model.Recipe
- Direction
- recipe.domain.state uses recipe.domain.model, so a change to recipe.domain.model can break recipe.domain.state, while a change to recipe.domain.state can't break recipe.domain.model.
- Position
- Below the diagonal: recipe.domain.state uses a module listed above it, which is the healthy direction.
20→13 recipe.domain.state uses core.util✕
- Connections
- 1 pair of types, where a type in recipe.domain.state uses a type in core.util.
- The types involved
de.lukasneugebauer.nextcloudcookbook.recipe.domain.state.RecipeDetailState→de.lukasneugebauer.nextcloudcookbook.core.util.UiText
- Direction
- recipe.domain.state uses core.util, so a change to core.util can break recipe.domain.state, while a change to recipe.domain.state can't break core.util.
- Position
- Below the diagonal: recipe.domain.state uses a module listed above it, which is the healthy direction.
21→5 auth.data.repository uses auth.domain.model✕
- Connections
- 2 pairs of types, where a type in auth.data.repository uses a type in auth.domain.model.
- The types involved
de.lukasneugebauer.nextcloudcookbook.auth.data.repository.AuthRepositoryImpl→de.lukasneugebauer.nextcloudcookbook.auth.domain.model.LoginEndpointResultde.lukasneugebauer.nextcloudcookbook.auth.data.repository.AuthRepositoryImpl→de.lukasneugebauer.nextcloudcookbook.auth.domain.model.LoginResult
- Direction
- auth.data.repository uses auth.domain.model, so a change to auth.domain.model can break auth.data.repository, while a change to auth.data.repository can't break auth.domain.model.
- Position
- Below the diagonal: auth.data.repository uses a module listed above it, which is the healthy direction.
21→13 auth.data.repository uses core.util✕
- Connections
- 1 pair of types, where a type in auth.data.repository uses a type in core.util.
- The types involved
de.lukasneugebauer.nextcloudcookbook.auth.data.repository.AuthRepositoryImpl→de.lukasneugebauer.nextcloudcookbook.core.util.Resource
- Direction
- auth.data.repository uses core.util, so a change to core.util can break auth.data.repository, while a change to auth.data.repository can't break core.util.
- Position
- Below the diagonal: auth.data.repository uses a module listed above it, which is the healthy direction.
21→14 auth.data.repository uses auth.data.api✕
- Connections
- 1 pair of types, where a type in auth.data.repository uses a type in auth.data.api.
- The types involved
de.lukasneugebauer.nextcloudcookbook.auth.data.repository.AuthRepositoryImpl→de.lukasneugebauer.nextcloudcookbook.auth.data.api.AuthApiProvider
- Direction
- auth.data.repository uses auth.data.api, so a change to auth.data.api can break auth.data.repository, while a change to auth.data.repository can't break auth.data.api.
- Position
- Below the diagonal: auth.data.repository uses a module listed above it, which is the healthy direction.
21→15 auth.data.repository uses auth.domain.repository✕
- Connections
- 1 pair of types, where a type in auth.data.repository uses a type in auth.domain.repository.
- The types involved
de.lukasneugebauer.nextcloudcookbook.auth.data.repository.AuthRepositoryImpl→de.lukasneugebauer.nextcloudcookbook.auth.domain.repository.AuthRepository
- Direction
- auth.data.repository uses auth.domain.repository, so a change to auth.domain.repository can break auth.data.repository, while a change to auth.data.repository can't break auth.domain.repository.
- Position
- Below the diagonal: auth.data.repository uses a module listed above it, which is the healthy direction.
21→18 auth.data.repository uses core.domain.repository✕
- Connections
- 1 pair of types, where a type in auth.data.repository uses a type in core.domain.repository.
- The types involved
de.lukasneugebauer.nextcloudcookbook.auth.data.repository.AuthRepositoryImpl→de.lukasneugebauer.nextcloudcookbook.core.domain.repository.BaseRepository
- Direction
- auth.data.repository uses core.domain.repository, so a change to core.domain.repository can break auth.data.repository, while a change to auth.data.repository can't break core.domain.repository.
- Position
- Below the diagonal: auth.data.repository uses a module listed above it, which is the healthy direction.
22→1 auth.presentation.splash uses auth.domain.state✕
- Connections
- 1 pair of types, where a type in auth.presentation.splash uses a type in auth.domain.state.
- The types involved
de.lukasneugebauer.nextcloudcookbook.auth.presentation.splash.SplashViewModel→de.lukasneugebauer.nextcloudcookbook.auth.domain.state.SplashScreenState
- Direction
- auth.presentation.splash uses auth.domain.state, so a change to auth.domain.state can break auth.presentation.splash, while a change to auth.presentation.splash can't break auth.domain.state.
- Position
- Below the diagonal: auth.presentation.splash uses a module listed above it, which is the healthy direction.
22→18 auth.presentation.splash uses core.domain.repository✕
- Connections
- 1 pair of types, where a type in auth.presentation.splash uses a type in core.domain.repository.
- The types involved
de.lukasneugebauer.nextcloudcookbook.auth.presentation.splash.SplashViewModel→de.lukasneugebauer.nextcloudcookbook.core.domain.repository.AccountRepository
- Direction
- auth.presentation.splash uses core.domain.repository, so a change to core.domain.repository can break auth.presentation.splash, while a change to auth.presentation.splash can't break core.domain.repository.
- Position
- Below the diagonal: auth.presentation.splash uses a module listed above it, which is the healthy direction.
23→2 category.data.repository uses category.domain.model✕
- Connections
- 1 pair of types, where a type in category.data.repository uses a type in category.domain.model.
- The types involved
de.lukasneugebauer.nextcloudcookbook.category.data.repository.CategoryRepositoryImpl→de.lukasneugebauer.nextcloudcookbook.category.domain.model.Category
- Direction
- category.data.repository uses category.domain.model, so a change to category.domain.model can break category.data.repository, while a change to category.data.repository can't break category.domain.model.
- Position
- Below the diagonal: category.data.repository uses a module listed above it, which is the healthy direction.
23→6 category.data.repository uses category.data.dto✕
- Connections
- 1 pair of types, where a type in category.data.repository uses a type in category.data.dto.
- The types involved
de.lukasneugebauer.nextcloudcookbook.category.data.repository.CategoryRepositoryImpl→de.lukasneugebauer.nextcloudcookbook.category.data.dto.CategoryDto
- Direction
- category.data.repository uses category.data.dto, so a change to category.data.dto can break category.data.repository, while a change to category.data.repository can't break category.data.dto.
- Position
- Below the diagonal: category.data.repository uses a module listed above it, which is the healthy direction.
23→13 category.data.repository uses core.util✕
- Connections
- 1 pair of types, where a type in category.data.repository uses a type in core.util.
- The types involved
de.lukasneugebauer.nextcloudcookbook.category.data.repository.CategoryRepositoryImpl→de.lukasneugebauer.nextcloudcookbook.core.util.DataResult
- Direction
- category.data.repository uses core.util, so a change to core.util can break category.data.repository, while a change to category.data.repository can't break core.util.
- Position
- Below the diagonal: category.data.repository uses a module listed above it, which is the healthy direction.
23→17 category.data.repository uses category.domain.repository✕
- Connections
- 1 pair of types, where a type in category.data.repository uses a type in category.domain.repository.
- The types involved
de.lukasneugebauer.nextcloudcookbook.category.data.repository.CategoryRepositoryImpl→de.lukasneugebauer.nextcloudcookbook.category.domain.repository.CategoryRepository
- Direction
- category.data.repository uses category.domain.repository, so a change to category.domain.repository can break category.data.repository, while a change to category.data.repository can't break category.domain.repository.
- Position
- Below the diagonal: category.data.repository uses a module listed above it, which is the healthy direction.
23→19 category.data.repository uses recipe.data.dto✕
- Connections
- 1 pair of types, where a type in category.data.repository uses a type in recipe.data.dto.
- The types involved
de.lukasneugebauer.nextcloudcookbook.category.data.repository.CategoryRepositoryImpl→de.lukasneugebauer.nextcloudcookbook.recipe.data.dto.RecipePreviewDto
- Direction
- category.data.repository uses recipe.data.dto, so a change to recipe.data.dto can break category.data.repository, while a change to category.data.repository can't break recipe.data.dto.
- Position
- Below the diagonal: category.data.repository uses a module listed above it, which is the healthy direction.
24→3 core.data.api uses core.data.remote.response✕
- Connections
- 3 pairs of types, where a type in core.data.api uses a type in core.data.remote.response.
- The types involved
de.lukasneugebauer.nextcloudcookbook.core.data.api.NcCookbookApi→de.lukasneugebauer.nextcloudcookbook.core.data.remote.response.CapabilitiesResponsede.lukasneugebauer.nextcloudcookbook.core.data.api.NcCookbookApi→de.lukasneugebauer.nextcloudcookbook.core.data.remote.response.ErrorResponsede.lukasneugebauer.nextcloudcookbook.core.data.api.NcCookbookApi→de.lukasneugebauer.nextcloudcookbook.core.data.remote.response.UserMetadataResponse
- Direction
- core.data.api uses core.data.remote.response, so a change to core.data.remote.response can break core.data.api, while a change to core.data.api can't break core.data.remote.response.
- Position
- Below the diagonal: core.data.api uses a module listed above it, which is the healthy direction.
24→4 core.data.api uses core.domain.model✕
- Connections
- 1 pair of types, where a type in core.data.api uses a type in core.domain.model.
- The types involved
de.lukasneugebauer.nextcloudcookbook.core.data.api.NcCookbookApiProvider→de.lukasneugebauer.nextcloudcookbook.core.domain.model.NcAccount
- Direction
- core.data.api uses core.domain.model, so a change to core.domain.model can break core.data.api, while a change to core.data.api can't break core.domain.model.
- Position
- Below the diagonal: core.data.api uses a module listed above it, which is the healthy direction.
24→6 core.data.api uses category.data.dto✕
- Connections
- 1 pair of types, where a type in core.data.api uses a type in category.data.dto.
- The types involved
de.lukasneugebauer.nextcloudcookbook.core.data.api.NcCookbookApi→de.lukasneugebauer.nextcloudcookbook.category.data.dto.CategoryDto
- Direction
- core.data.api uses category.data.dto, so a change to category.data.dto can break core.data.api, while a change to core.data.api can't break category.data.dto.
- Position
- Below the diagonal: core.data.api uses a module listed above it, which is the healthy direction.
24→12 core.data.api uses core.data✕
- Connections
- 1 pair of types, where a type in core.data.api uses a type in core.data.
- The types involved
de.lukasneugebauer.nextcloudcookbook.core.data.api.NcCookbookApiProvider→de.lukasneugebauer.nextcloudcookbook.core.data.PreferencesManager
- Direction
- core.data.api uses core.data, so a change to core.data can break core.data.api, while a change to core.data.api can't break core.data.
- Position
- Below the diagonal: core.data.api uses a module listed above it, which is the healthy direction.
24→13 core.data.api uses core.util✕
- Connections
- 1 pair of types, where a type in core.data.api uses a type in core.util.
- The types involved
de.lukasneugebauer.nextcloudcookbook.core.data.api.NcCookbookApiProvider→de.lukasneugebauer.nextcloudcookbook.core.util.OkHttpClientProvider
- Direction
- core.data.api uses core.util, so a change to core.util can break core.data.api, while a change to core.data.api can't break core.util.
- Position
- Below the diagonal: core.data.api uses a module listed above it, which is the healthy direction.
24→19 core.data.api uses recipe.data.dto✕
- Connections
- 3 pairs of types, where a type in core.data.api uses a type in recipe.data.dto.
- The types involved
de.lukasneugebauer.nextcloudcookbook.core.data.api.NcCookbookApi→de.lukasneugebauer.nextcloudcookbook.recipe.data.dto.ImportUrlDtode.lukasneugebauer.nextcloudcookbook.core.data.api.NcCookbookApi→de.lukasneugebauer.nextcloudcookbook.recipe.data.dto.RecipeDtode.lukasneugebauer.nextcloudcookbook.core.data.api.NcCookbookApi→de.lukasneugebauer.nextcloudcookbook.recipe.data.dto.RecipePreviewDto
- Direction
- core.data.api uses recipe.data.dto, so a change to recipe.data.dto can break core.data.api, while a change to core.data.api can't break recipe.data.dto.
- Position
- Below the diagonal: core.data.api uses a module listed above it, which is the healthy direction.
25→6 core.domain.usecase uses category.data.dto✕
- Connections
- 1 pair of types, where a type in core.domain.usecase uses a type in category.data.dto.
- The types involved
de.lukasneugebauer.nextcloudcookbook.core.domain.usecase.ClearAllStoresUseCase→de.lukasneugebauer.nextcloudcookbook.category.data.dto.CategoryDto
- Direction
- core.domain.usecase uses category.data.dto, so a change to category.data.dto can break core.domain.usecase, while a change to core.domain.usecase can't break category.data.dto.
- Position
- Below the diagonal: core.domain.usecase uses a module listed above it, which is the healthy direction.
25→7 core.domain.usecase uses recipe.domain.model✕
- Connections
- 1 pair of types, where a type in core.domain.usecase uses a type in recipe.domain.model.
- The types involved
de.lukasneugebauer.nextcloudcookbook.core.domain.usecase.SyncRecipesUseCase→de.lukasneugebauer.nextcloudcookbook.recipe.domain.model.RecipeSyncState
- Direction
- core.domain.usecase uses recipe.domain.model, so a change to recipe.domain.model can break core.domain.usecase, while a change to core.domain.usecase can't break recipe.domain.model.
- Position
- Below the diagonal: core.domain.usecase uses a module listed above it, which is the healthy direction.
25→10 core.domain.usecase uses recipe.domain.dao✕
- Connections
- 1 pair of types, where a type in core.domain.usecase uses a type in recipe.domain.dao.
- The types involved
de.lukasneugebauer.nextcloudcookbook.core.domain.usecase.SyncRecipesUseCase→de.lukasneugebauer.nextcloudcookbook.recipe.domain.dao.RecipeDao
- Direction
- core.domain.usecase uses recipe.domain.dao, so a change to recipe.domain.dao can break core.domain.usecase, while a change to core.domain.usecase can't break recipe.domain.dao.
- Position
- Below the diagonal: core.domain.usecase uses a module listed above it, which is the healthy direction.
25→12 core.domain.usecase uses core.data✕
- Connections
- 1 pair of types, where a type in core.domain.usecase uses a type in core.data.
- The types involved
de.lukasneugebauer.nextcloudcookbook.core.domain.usecase.ClearPreferencesUseCase→de.lukasneugebauer.nextcloudcookbook.core.data.PreferencesManager
- Direction
- core.domain.usecase uses core.data, so a change to core.data can break core.domain.usecase, while a change to core.domain.usecase can't break core.data.
- Position
- Below the diagonal: core.domain.usecase uses a module listed above it, which is the healthy direction.
25→19 core.domain.usecase uses recipe.data.dto✕
- Connections
- 6 pairs of types, where a type in core.domain.usecase uses a type in recipe.data.dto.
- The types involved
de.lukasneugebauer.nextcloudcookbook.core.domain.usecase.ClearAllStoresUseCase→de.lukasneugebauer.nextcloudcookbook.recipe.data.dto.RecipeDtode.lukasneugebauer.nextcloudcookbook.core.domain.usecase.ClearAllStoresUseCase→de.lukasneugebauer.nextcloudcookbook.recipe.data.dto.RecipePreviewDtode.lukasneugebauer.nextcloudcookbook.core.domain.usecase.RefreshAllRecipesUseCase→de.lukasneugebauer.nextcloudcookbook.recipe.data.dto.RecipeDtode.lukasneugebauer.nextcloudcookbook.core.domain.usecase.RefreshAllRecipesUseCase→de.lukasneugebauer.nextcloudcookbook.recipe.data.dto.RecipePreviewDtode.lukasneugebauer.nextcloudcookbook.core.domain.usecase.SyncRecipesUseCase→de.lukasneugebauer.nextcloudcookbook.recipe.data.dto.RecipeDtode.lukasneugebauer.nextcloudcookbook.core.domain.usecase.SyncRecipesUseCase→de.lukasneugebauer.nextcloudcookbook.recipe.data.dto.RecipePreviewDto
- Direction
- core.domain.usecase uses recipe.data.dto, so a change to recipe.data.dto can break core.domain.usecase, while a change to core.domain.usecase can't break recipe.data.dto.
- Position
- Below the diagonal: core.domain.usecase uses a module listed above it, which is the healthy direction.
26→7 recipe.domain.repository uses recipe.domain.model✕
- Connections
- 3 pairs of types, where a type in recipe.domain.repository uses a type in recipe.domain.model.
- The types involved
de.lukasneugebauer.nextcloudcookbook.recipe.domain.repository.RecipeRepository→de.lukasneugebauer.nextcloudcookbook.recipe.domain.model.Recipede.lukasneugebauer.nextcloudcookbook.recipe.domain.repository.RecipeRepository→de.lukasneugebauer.nextcloudcookbook.recipe.domain.model.RecipeImageUploadde.lukasneugebauer.nextcloudcookbook.recipe.domain.repository.RecipeRepository→de.lukasneugebauer.nextcloudcookbook.recipe.domain.model.RecipePreview
- Direction
- recipe.domain.repository uses recipe.domain.model, so a change to recipe.domain.model can break recipe.domain.repository, while a change to recipe.domain.repository can't break recipe.domain.model.
- Position
- Below the diagonal: recipe.domain.repository uses a module listed above it, which is the healthy direction.
26→13 recipe.domain.repository uses core.util✕
- Connections
- 2 pairs of types, where a type in recipe.domain.repository uses a type in core.util.
- The types involved
de.lukasneugebauer.nextcloudcookbook.recipe.domain.repository.RecipeRepository→de.lukasneugebauer.nextcloudcookbook.core.util.DataResultde.lukasneugebauer.nextcloudcookbook.recipe.domain.repository.RecipeRepository→de.lukasneugebauer.nextcloudcookbook.core.util.Resource
- Direction
- recipe.domain.repository uses core.util, so a change to core.util can break recipe.domain.repository, while a change to recipe.domain.repository can't break core.util.
- Position
- Below the diagonal: recipe.domain.repository uses a module listed above it, which is the healthy direction.
26→19 recipe.domain.repository uses recipe.data.dto✕
- Connections
- 2 pairs of types, where a type in recipe.domain.repository uses a type in recipe.data.dto.
- The types involved
de.lukasneugebauer.nextcloudcookbook.recipe.domain.repository.RecipeRepository→de.lukasneugebauer.nextcloudcookbook.recipe.data.dto.ImportUrlDtode.lukasneugebauer.nextcloudcookbook.recipe.domain.repository.RecipeRepository→de.lukasneugebauer.nextcloudcookbook.recipe.data.dto.RecipeDto
- Direction
- recipe.domain.repository uses recipe.data.dto, so a change to recipe.data.dto can break recipe.domain.repository, while a change to recipe.domain.repository can't break recipe.data.dto.
- Position
- Below the diagonal: recipe.domain.repository uses a module listed above it, which is the healthy direction.
27→2 recipe.domain.state.RecipeCreateEditState uses category.domain.model✕
- Connections
- 1 pair of types, where a type in recipe.domain.state.RecipeCreateEditState uses a type in category.domain.model.
- The types involved
de.lukasneugebauer.nextcloudcookbook.recipe.domain.state.RecipeCreateEditState.Success→de.lukasneugebauer.nextcloudcookbook.category.domain.model.Category
- Direction
- recipe.domain.state.RecipeCreateEditState uses category.domain.model, so a change to category.domain.model can break recipe.domain.state.RecipeCreateEditState, while a change to recipe.domain.state.RecipeCreateEditState can't break category.domain.model.
- Position
- Below the diagonal: recipe.domain.state.RecipeCreateEditState uses a module listed above it, which is the healthy direction.
27→7 recipe.domain.state.RecipeCreateEditState uses recipe.domain.model✕
- Connections
- 2 pairs of types, where a type in recipe.domain.state.RecipeCreateEditState uses a type in recipe.domain.model.
- The types involved
de.lukasneugebauer.nextcloudcookbook.recipe.domain.state.RecipeCreateEditState.Success→de.lukasneugebauer.nextcloudcookbook.recipe.domain.model.DurationComponentsde.lukasneugebauer.nextcloudcookbook.recipe.domain.state.RecipeCreateEditState.Success→de.lukasneugebauer.nextcloudcookbook.recipe.domain.model.Recipe
- Direction
- recipe.domain.state.RecipeCreateEditState uses recipe.domain.model, so a change to recipe.domain.model can break recipe.domain.state.RecipeCreateEditState, while a change to recipe.domain.state.RecipeCreateEditState can't break recipe.domain.model.
- Position
- Below the diagonal: recipe.domain.state.RecipeCreateEditState uses a module listed above it, which is the healthy direction.
27→13 recipe.domain.state.RecipeCreateEditState uses core.util✕
- Connections
- 2 pairs of types, where a type in recipe.domain.state.RecipeCreateEditState uses a type in core.util.
- The types involved
de.lukasneugebauer.nextcloudcookbook.recipe.domain.state.RecipeCreateEditState.Error→de.lukasneugebauer.nextcloudcookbook.core.util.UiTextde.lukasneugebauer.nextcloudcookbook.recipe.domain.state.RecipeCreateEditState.Success→de.lukasneugebauer.nextcloudcookbook.core.util.UiText
- Direction
- recipe.domain.state.RecipeCreateEditState uses core.util, so a change to core.util can break recipe.domain.state.RecipeCreateEditState, while a change to recipe.domain.state.RecipeCreateEditState can't break core.util.
- Position
- Below the diagonal: recipe.domain.state.RecipeCreateEditState uses a module listed above it, which is the healthy direction.
27→20 recipe.domain.state.RecipeCreateEditState uses recipe.domain.state✕
- Connections
- 5 pairs of types, where a type in recipe.domain.state.RecipeCreateEditState uses a type in recipe.domain.state.
- The types involved
de.lukasneugebauer.nextcloudcookbook.recipe.domain.state.RecipeCreateEditState.Error→de.lukasneugebauer.nextcloudcookbook.recipe.domain.state.RecipeCreateEditStatede.lukasneugebauer.nextcloudcookbook.recipe.domain.state.RecipeCreateEditState.Loading→de.lukasneugebauer.nextcloudcookbook.recipe.domain.state.RecipeCreateEditStatede.lukasneugebauer.nextcloudcookbook.recipe.domain.state.RecipeCreateEditState.Saving→de.lukasneugebauer.nextcloudcookbook.recipe.domain.state.RecipeCreateEditStatede.lukasneugebauer.nextcloudcookbook.recipe.domain.state.RecipeCreateEditState.Success→de.lukasneugebauer.nextcloudcookbook.recipe.domain.state.RecipeCreateEditStatede.lukasneugebauer.nextcloudcookbook.recipe.domain.state.RecipeCreateEditState.Updated→de.lukasneugebauer.nextcloudcookbook.recipe.domain.state.RecipeCreateEditState
- Direction
- recipe.domain.state.RecipeCreateEditState uses recipe.domain.state, so a change to recipe.domain.state can break recipe.domain.state.RecipeCreateEditState, while a change to recipe.domain.state.RecipeCreateEditState can't break recipe.domain.state.
- Position
- Below the diagonal: recipe.domain.state.RecipeCreateEditState uses a module listed above it, which is the healthy direction.
28→1 auth.presentation.browser uses auth.domain.state✕
- Connections
- 1 pair of types, where a type in auth.presentation.browser uses a type in auth.domain.state.
- The types involved
de.lukasneugebauer.nextcloudcookbook.auth.presentation.browser.BrowserLoginViewModel→de.lukasneugebauer.nextcloudcookbook.auth.domain.state.BrowserLoginScreenState
- Direction
- auth.presentation.browser uses auth.domain.state, so a change to auth.domain.state can break auth.presentation.browser, while a change to auth.presentation.browser can't break auth.domain.state.
- Position
- Below the diagonal: auth.presentation.browser uses a module listed above it, which is the healthy direction.
28→12 auth.presentation.browser uses core.data✕
- Connections
- 1 pair of types, where a type in auth.presentation.browser uses a type in core.data.
- The types involved
de.lukasneugebauer.nextcloudcookbook.auth.presentation.browser.BrowserLoginViewModel→de.lukasneugebauer.nextcloudcookbook.core.data.PreferencesManager
- Direction
- auth.presentation.browser uses core.data, so a change to core.data can break auth.presentation.browser, while a change to auth.presentation.browser can't break core.data.
- Position
- Below the diagonal: auth.presentation.browser uses a module listed above it, which is the healthy direction.
28→15 auth.presentation.browser uses auth.domain.repository✕
- Connections
- 1 pair of types, where a type in auth.presentation.browser uses a type in auth.domain.repository.
- The types involved
de.lukasneugebauer.nextcloudcookbook.auth.presentation.browser.BrowserLoginViewModel→de.lukasneugebauer.nextcloudcookbook.auth.domain.repository.AuthRepository
- Direction
- auth.presentation.browser uses auth.domain.repository, so a change to auth.domain.repository can break auth.presentation.browser, while a change to auth.presentation.browser can't break auth.domain.repository.
- Position
- Below the diagonal: auth.presentation.browser uses a module listed above it, which is the healthy direction.
28→18 auth.presentation.browser uses core.domain.repository✕
- Connections
- 1 pair of types, where a type in auth.presentation.browser uses a type in core.domain.repository.
- The types involved
de.lukasneugebauer.nextcloudcookbook.auth.presentation.browser.BrowserLoginViewModel→de.lukasneugebauer.nextcloudcookbook.core.domain.repository.AccountRepository
- Direction
- auth.presentation.browser uses core.domain.repository, so a change to core.domain.repository can break auth.presentation.browser, while a change to auth.presentation.browser can't break core.domain.repository.
- Position
- Below the diagonal: auth.presentation.browser uses a module listed above it, which is the healthy direction.
28→24 auth.presentation.browser uses core.data.api✕
- Connections
- 1 pair of types, where a type in auth.presentation.browser uses a type in core.data.api.
- The types involved
de.lukasneugebauer.nextcloudcookbook.auth.presentation.browser.BrowserLoginViewModel→de.lukasneugebauer.nextcloudcookbook.core.data.api.NcCookbookApiProvider
- Direction
- auth.presentation.browser uses core.data.api, so a change to core.data.api can break auth.presentation.browser, while a change to auth.presentation.browser can't break core.data.api.
- Position
- Below the diagonal: auth.presentation.browser uses a module listed above it, which is the healthy direction.
28→25 auth.presentation.browser uses core.domain.usecase✕
- Connections
- 1 pair of types, where a type in auth.presentation.browser uses a type in core.domain.usecase.
- The types involved
de.lukasneugebauer.nextcloudcookbook.auth.presentation.browser.BrowserLoginViewModel→de.lukasneugebauer.nextcloudcookbook.core.domain.usecase.ClearPreferencesUseCase
- Direction
- auth.presentation.browser uses core.domain.usecase, so a change to core.domain.usecase can break auth.presentation.browser, while a change to auth.presentation.browser can't break core.domain.usecase.
- Position
- Below the diagonal: auth.presentation.browser uses a module listed above it, which is the healthy direction.
29→1 auth.presentation.manual uses auth.domain.state✕
- Connections
- 1 pair of types, where a type in auth.presentation.manual uses a type in auth.domain.state.
- The types involved
de.lukasneugebauer.nextcloudcookbook.auth.presentation.manual.ManualLoginViewModel→de.lukasneugebauer.nextcloudcookbook.auth.domain.state.ManualLoginScreenState
- Direction
- auth.presentation.manual uses auth.domain.state, so a change to auth.domain.state can break auth.presentation.manual, while a change to auth.presentation.manual can't break auth.domain.state.
- Position
- Below the diagonal: auth.presentation.manual uses a module listed above it, which is the healthy direction.
29→12 auth.presentation.manual uses core.data✕
- Connections
- 1 pair of types, where a type in auth.presentation.manual uses a type in core.data.
- The types involved
de.lukasneugebauer.nextcloudcookbook.auth.presentation.manual.ManualLoginViewModel→de.lukasneugebauer.nextcloudcookbook.core.data.PreferencesManager
- Direction
- auth.presentation.manual uses core.data, so a change to core.data can break auth.presentation.manual, while a change to auth.presentation.manual can't break core.data.
- Position
- Below the diagonal: auth.presentation.manual uses a module listed above it, which is the healthy direction.
29→13 auth.presentation.manual uses core.util✕
- Connections
- 1 pair of types, where a type in auth.presentation.manual uses a type in core.util.
- The types involved
de.lukasneugebauer.nextcloudcookbook.auth.presentation.manual.ManualLoginScreenKt→de.lukasneugebauer.nextcloudcookbook.core.util.UiText
- Direction
- auth.presentation.manual uses core.util, so a change to core.util can break auth.presentation.manual, while a change to auth.presentation.manual can't break core.util.
- Position
- Below the diagonal: auth.presentation.manual uses a module listed above it, which is the healthy direction.
29→18 auth.presentation.manual uses core.domain.repository✕
- Connections
- 1 pair of types, where a type in auth.presentation.manual uses a type in core.domain.repository.
- The types involved
de.lukasneugebauer.nextcloudcookbook.auth.presentation.manual.ManualLoginViewModel→de.lukasneugebauer.nextcloudcookbook.core.domain.repository.AccountRepository
- Direction
- auth.presentation.manual uses core.domain.repository, so a change to core.domain.repository can break auth.presentation.manual, while a change to auth.presentation.manual can't break core.domain.repository.
- Position
- Below the diagonal: auth.presentation.manual uses a module listed above it, which is the healthy direction.
29→24 auth.presentation.manual uses core.data.api✕
- Connections
- 1 pair of types, where a type in auth.presentation.manual uses a type in core.data.api.
- The types involved
de.lukasneugebauer.nextcloudcookbook.auth.presentation.manual.ManualLoginViewModel→de.lukasneugebauer.nextcloudcookbook.core.data.api.NcCookbookApiProvider
- Direction
- auth.presentation.manual uses core.data.api, so a change to core.data.api can break auth.presentation.manual, while a change to auth.presentation.manual can't break core.data.api.
- Position
- Below the diagonal: auth.presentation.manual uses a module listed above it, which is the healthy direction.
29→25 auth.presentation.manual uses core.domain.usecase✕
- Connections
- 1 pair of types, where a type in auth.presentation.manual uses a type in core.domain.usecase.
- The types involved
de.lukasneugebauer.nextcloudcookbook.auth.presentation.manual.ManualLoginViewModel→de.lukasneugebauer.nextcloudcookbook.core.domain.usecase.ClearPreferencesUseCase
- Direction
- auth.presentation.manual uses core.domain.usecase, so a change to core.domain.usecase can break auth.presentation.manual, while a change to auth.presentation.manual can't break core.domain.usecase.
- Position
- Below the diagonal: auth.presentation.manual uses a module listed above it, which is the healthy direction.
30→4 core.data.repository uses core.domain.model✕
- Connections
- 4 pairs of types, where a type in core.data.repository uses a type in core.domain.model.
- The types involved
de.lukasneugebauer.nextcloudcookbook.core.data.repository.AccountRepositoryImpl→de.lukasneugebauer.nextcloudcookbook.core.domain.model.Capabilitiesde.lukasneugebauer.nextcloudcookbook.core.data.repository.AccountRepositoryImpl→de.lukasneugebauer.nextcloudcookbook.core.domain.model.CookbookVersionde.lukasneugebauer.nextcloudcookbook.core.data.repository.AccountRepositoryImpl→de.lukasneugebauer.nextcloudcookbook.core.domain.model.NcAccountde.lukasneugebauer.nextcloudcookbook.core.data.repository.AccountRepositoryImpl→de.lukasneugebauer.nextcloudcookbook.core.domain.model.UserMetadata
- Direction
- core.data.repository uses core.domain.model, so a change to core.domain.model can break core.data.repository, while a change to core.data.repository can't break core.domain.model.
- Position
- Below the diagonal: core.data.repository uses a module listed above it, which is the healthy direction.
30→12 core.data.repository uses core.data✕
- Connections
- 1 pair of types, where a type in core.data.repository uses a type in core.data.
- The types involved
de.lukasneugebauer.nextcloudcookbook.core.data.repository.AccountRepositoryImpl→de.lukasneugebauer.nextcloudcookbook.core.data.PreferencesManager
- Direction
- core.data.repository uses core.data, so a change to core.data can break core.data.repository, while a change to core.data.repository can't break core.data.
- Position
- Below the diagonal: core.data.repository uses a module listed above it, which is the healthy direction.
30→13 core.data.repository uses core.util✕
- Connections
- 1 pair of types, where a type in core.data.repository uses a type in core.util.
- The types involved
de.lukasneugebauer.nextcloudcookbook.core.data.repository.AccountRepositoryImpl→de.lukasneugebauer.nextcloudcookbook.core.util.Resource
- Direction
- core.data.repository uses core.util, so a change to core.util can break core.data.repository, while a change to core.data.repository can't break core.util.
- Position
- Below the diagonal: core.data.repository uses a module listed above it, which is the healthy direction.
30→18 core.data.repository uses core.domain.repository✕
- Connections
- 2 pairs of types, where a type in core.data.repository uses a type in core.domain.repository.
- The types involved
de.lukasneugebauer.nextcloudcookbook.core.data.repository.AccountRepositoryImpl→de.lukasneugebauer.nextcloudcookbook.core.domain.repository.AccountRepositoryde.lukasneugebauer.nextcloudcookbook.core.data.repository.AccountRepositoryImpl→de.lukasneugebauer.nextcloudcookbook.core.domain.repository.BaseRepository
- Direction
- core.data.repository uses core.domain.repository, so a change to core.domain.repository can break core.data.repository, while a change to core.data.repository can't break core.domain.repository.
- Position
- Below the diagonal: core.data.repository uses a module listed above it, which is the healthy direction.
30→24 core.data.repository uses core.data.api✕
- Connections
- 1 pair of types, where a type in core.data.repository uses a type in core.data.api.
- The types involved
de.lukasneugebauer.nextcloudcookbook.core.data.repository.AccountRepositoryImpl→de.lukasneugebauer.nextcloudcookbook.core.data.api.NcCookbookApiProvider
- Direction
- core.data.repository uses core.data.api, so a change to core.data.api can break core.data.repository, while a change to core.data.repository can't break core.data.api.
- Position
- Below the diagonal: core.data.repository uses a module listed above it, which is the healthy direction.
31→6 di uses category.data.dto✕
- Connections
- 1 pair of types, where a type in di uses a type in category.data.dto.
- The types involved
de.lukasneugebauer.nextcloudcookbook.di.CategoryModule→de.lukasneugebauer.nextcloudcookbook.category.data.dto.CategoryDto
- Direction
- di uses category.data.dto, so a change to category.data.dto can break di, while a change to di can't break category.data.dto.
- Position
- Below the diagonal: di uses a module listed above it, which is the healthy direction.
31→9 di uses recipe.domain✕
- Connections
- 2 pairs of types, where a type in di uses a type in recipe.domain.
- The types involved
de.lukasneugebauer.nextcloudcookbook.di.RecipeModule→de.lukasneugebauer.nextcloudcookbook.recipe.domain.RecipeFormatterde.lukasneugebauer.nextcloudcookbook.di.RecipeModule→de.lukasneugebauer.nextcloudcookbook.recipe.domain.YieldCalculator
- Direction
- di uses recipe.domain, so a change to recipe.domain can break di, while a change to di can't break recipe.domain.
- Position
- Below the diagonal: di uses a module listed above it, which is the healthy direction.
31→10 di uses recipe.domain.dao✕
- Connections
- 4 pairs of types, where a type in di uses a type in recipe.domain.dao.
- The types involved
de.lukasneugebauer.nextcloudcookbook.di.DatabaseModule→de.lukasneugebauer.nextcloudcookbook.recipe.domain.dao.RecipeDaode.lukasneugebauer.nextcloudcookbook.di.DatabaseModule→de.lukasneugebauer.nextcloudcookbook.recipe.domain.dao.RecipePreviewDaode.lukasneugebauer.nextcloudcookbook.di.RecipeModule→de.lukasneugebauer.nextcloudcookbook.recipe.domain.dao.RecipeDaode.lukasneugebauer.nextcloudcookbook.di.RecipeModule→de.lukasneugebauer.nextcloudcookbook.recipe.domain.dao.RecipePreviewDao
- Direction
- di uses recipe.domain.dao, so a change to recipe.domain.dao can break di, while a change to di can't break recipe.domain.dao.
- Position
- Below the diagonal: di uses a module listed above it, which is the healthy direction.
31→12 di uses core.data✕
- Connections
- 4 pairs of types, where a type in di uses a type in core.data.
- The types involved
de.lukasneugebauer.nextcloudcookbook.di.AccountModule→de.lukasneugebauer.nextcloudcookbook.core.data.PreferencesManagerde.lukasneugebauer.nextcloudcookbook.di.AppModule→de.lukasneugebauer.nextcloudcookbook.core.data.PreferencesManagerde.lukasneugebauer.nextcloudcookbook.di.DatabaseModule→de.lukasneugebauer.nextcloudcookbook.core.data.CookbookDatabasede.lukasneugebauer.nextcloudcookbook.di.RecipeModule→de.lukasneugebauer.nextcloudcookbook.core.data.PreferencesManager
- Direction
- di uses core.data, so a change to core.data can break di, while a change to di can't break core.data.
- Position
- Below the diagonal: di uses a module listed above it, which is the healthy direction.
31→14 di uses auth.data.api✕
- Connections
- 1 pair of types, where a type in di uses a type in auth.data.api.
- The types involved
de.lukasneugebauer.nextcloudcookbook.di.AuthModule→de.lukasneugebauer.nextcloudcookbook.auth.data.api.AuthApiProvider
- Direction
- di uses auth.data.api, so a change to auth.data.api can break di, while a change to di can't break auth.data.api.
- Position
- Below the diagonal: di uses a module listed above it, which is the healthy direction.
31→15 di uses auth.domain.repository✕
- Connections
- 1 pair of types, where a type in di uses a type in auth.domain.repository.
- The types involved
de.lukasneugebauer.nextcloudcookbook.di.AuthModule→de.lukasneugebauer.nextcloudcookbook.auth.domain.repository.AuthRepository
- Direction
- di uses auth.domain.repository, so a change to auth.domain.repository can break di, while a change to di can't break auth.domain.repository.
- Position
- Below the diagonal: di uses a module listed above it, which is the healthy direction.
31→17 di uses category.domain.repository✕
- Connections
- 1 pair of types, where a type in di uses a type in category.domain.repository.
- The types involved
de.lukasneugebauer.nextcloudcookbook.di.CategoryModule→de.lukasneugebauer.nextcloudcookbook.category.domain.repository.CategoryRepository
- Direction
- di uses category.domain.repository, so a change to category.domain.repository can break di, while a change to di can't break category.domain.repository.
- Position
- Below the diagonal: di uses a module listed above it, which is the healthy direction.
31→18 di uses core.domain.repository✕
- Connections
- 1 pair of types, where a type in di uses a type in core.domain.repository.
- The types involved
de.lukasneugebauer.nextcloudcookbook.di.AccountModule→de.lukasneugebauer.nextcloudcookbook.core.domain.repository.AccountRepository
- Direction
- di uses core.domain.repository, so a change to core.domain.repository can break di, while a change to di can't break core.domain.repository.
- Position
- Below the diagonal: di uses a module listed above it, which is the healthy direction.
31→19 di uses recipe.data.dto✕
- Connections
- 3 pairs of types, where a type in di uses a type in recipe.data.dto.
- The types involved
de.lukasneugebauer.nextcloudcookbook.di.CategoryModule→de.lukasneugebauer.nextcloudcookbook.recipe.data.dto.RecipePreviewDtode.lukasneugebauer.nextcloudcookbook.di.RecipeModule→de.lukasneugebauer.nextcloudcookbook.recipe.data.dto.RecipeDtode.lukasneugebauer.nextcloudcookbook.di.RecipeModule→de.lukasneugebauer.nextcloudcookbook.recipe.data.dto.RecipePreviewDto
- Direction
- di uses recipe.data.dto, so a change to recipe.data.dto can break di, while a change to di can't break recipe.data.dto.
- Position
- Below the diagonal: di uses a module listed above it, which is the healthy direction.
31→24 di uses core.data.api✕
- Connections
- 3 pairs of types, where a type in di uses a type in core.data.api.
- The types involved
de.lukasneugebauer.nextcloudcookbook.di.AccountModule→de.lukasneugebauer.nextcloudcookbook.core.data.api.NcCookbookApiProviderde.lukasneugebauer.nextcloudcookbook.di.CategoryModule→de.lukasneugebauer.nextcloudcookbook.core.data.api.NcCookbookApiProviderde.lukasneugebauer.nextcloudcookbook.di.RecipeModule→de.lukasneugebauer.nextcloudcookbook.core.data.api.NcCookbookApiProvider
- Direction
- di uses core.data.api, so a change to core.data.api can break di, while a change to di can't break core.data.api.
- Position
- Below the diagonal: di uses a module listed above it, which is the healthy direction.
31→26 di uses recipe.domain.repository✕
- Connections
- 1 pair of types, where a type in di uses a type in recipe.domain.repository.
- The types involved
de.lukasneugebauer.nextcloudcookbook.di.RecipeModule→de.lukasneugebauer.nextcloudcookbook.recipe.domain.repository.RecipeRepository
- Direction
- di uses recipe.domain.repository, so a change to recipe.domain.repository can break di, while a change to di can't break recipe.domain.repository.
- Position
- Below the diagonal: di uses a module listed above it, which is the healthy direction.
32→3 recipe.data.repository uses core.data.remote.response✕
- Connections
- 1 pair of types, where a type in recipe.data.repository uses a type in core.data.remote.response.
- The types involved
de.lukasneugebauer.nextcloudcookbook.recipe.data.repository.RecipeRepositoryImpl→de.lukasneugebauer.nextcloudcookbook.core.data.remote.response.ErrorResponse
- Direction
- recipe.data.repository uses core.data.remote.response, so a change to core.data.remote.response can break recipe.data.repository, while a change to recipe.data.repository can't break core.data.remote.response.
- Position
- Below the diagonal: recipe.data.repository uses a module listed above it, which is the healthy direction.
32→4 recipe.data.repository uses core.domain.model✕
- Connections
- 1 pair of types, where a type in recipe.data.repository uses a type in core.domain.model.
- The types involved
de.lukasneugebauer.nextcloudcookbook.recipe.data.repository.RecipeRepositoryImpl→de.lukasneugebauer.nextcloudcookbook.core.domain.model.NcAccount
- Direction
- recipe.data.repository uses core.domain.model, so a change to core.domain.model can break recipe.data.repository, while a change to recipe.data.repository can't break core.domain.model.
- Position
- Below the diagonal: recipe.data.repository uses a module listed above it, which is the healthy direction.
32→7 recipe.data.repository uses recipe.domain.model✕
- Connections
- 3 pairs of types, where a type in recipe.data.repository uses a type in recipe.domain.model.
- The types involved
de.lukasneugebauer.nextcloudcookbook.recipe.data.repository.RecipeRepositoryImpl→de.lukasneugebauer.nextcloudcookbook.recipe.domain.model.Recipede.lukasneugebauer.nextcloudcookbook.recipe.data.repository.RecipeRepositoryImpl→de.lukasneugebauer.nextcloudcookbook.recipe.domain.model.RecipeImageUploadde.lukasneugebauer.nextcloudcookbook.recipe.data.repository.RecipeRepositoryImpl→de.lukasneugebauer.nextcloudcookbook.recipe.domain.model.RecipePreview
- Direction
- recipe.data.repository uses recipe.domain.model, so a change to recipe.domain.model can break recipe.data.repository, while a change to recipe.data.repository can't break recipe.domain.model.
- Position
- Below the diagonal: recipe.data.repository uses a module listed above it, which is the healthy direction.
32→12 recipe.data.repository uses core.data✕
- Connections
- 1 pair of types, where a type in recipe.data.repository uses a type in core.data.
- The types involved
de.lukasneugebauer.nextcloudcookbook.recipe.data.repository.RecipeRepositoryImpl→de.lukasneugebauer.nextcloudcookbook.core.data.PreferencesManager
- Direction
- recipe.data.repository uses core.data, so a change to core.data can break recipe.data.repository, while a change to recipe.data.repository can't break core.data.
- Position
- Below the diagonal: recipe.data.repository uses a module listed above it, which is the healthy direction.
32→13 recipe.data.repository uses core.util✕
- Connections
- 2 pairs of types, where a type in recipe.data.repository uses a type in core.util.
- The types involved
de.lukasneugebauer.nextcloudcookbook.recipe.data.repository.RecipeRepositoryImpl→de.lukasneugebauer.nextcloudcookbook.core.util.DataResultde.lukasneugebauer.nextcloudcookbook.recipe.data.repository.RecipeRepositoryImpl→de.lukasneugebauer.nextcloudcookbook.core.util.Resource
- Direction
- recipe.data.repository uses core.util, so a change to core.util can break recipe.data.repository, while a change to recipe.data.repository can't break core.util.
- Position
- Below the diagonal: recipe.data.repository uses a module listed above it, which is the healthy direction.
32→18 recipe.data.repository uses core.domain.repository✕
- Connections
- 1 pair of types, where a type in recipe.data.repository uses a type in core.domain.repository.
- The types involved
de.lukasneugebauer.nextcloudcookbook.recipe.data.repository.RecipeRepositoryImpl→de.lukasneugebauer.nextcloudcookbook.core.domain.repository.BaseRepository
- Direction
- recipe.data.repository uses core.domain.repository, so a change to core.domain.repository can break recipe.data.repository, while a change to recipe.data.repository can't break core.domain.repository.
- Position
- Below the diagonal: recipe.data.repository uses a module listed above it, which is the healthy direction.
32→19 recipe.data.repository uses recipe.data.dto✕
- Connections
- 3 pairs of types, where a type in recipe.data.repository uses a type in recipe.data.dto.
- The types involved
de.lukasneugebauer.nextcloudcookbook.recipe.data.repository.RecipeRepositoryImpl→de.lukasneugebauer.nextcloudcookbook.recipe.data.dto.ImportUrlDtode.lukasneugebauer.nextcloudcookbook.recipe.data.repository.RecipeRepositoryImpl→de.lukasneugebauer.nextcloudcookbook.recipe.data.dto.RecipeDtode.lukasneugebauer.nextcloudcookbook.recipe.data.repository.RecipeRepositoryImpl→de.lukasneugebauer.nextcloudcookbook.recipe.data.dto.RecipePreviewDto
- Direction
- recipe.data.repository uses recipe.data.dto, so a change to recipe.data.dto can break recipe.data.repository, while a change to recipe.data.repository can't break recipe.data.dto.
- Position
- Below the diagonal: recipe.data.repository uses a module listed above it, which is the healthy direction.
32→24 recipe.data.repository uses core.data.api✕
- Connections
- 1 pair of types, where a type in recipe.data.repository uses a type in core.data.api.
- The types involved
de.lukasneugebauer.nextcloudcookbook.recipe.data.repository.RecipeRepositoryImpl→de.lukasneugebauer.nextcloudcookbook.core.data.api.NcCookbookApiProvider
- Direction
- recipe.data.repository uses core.data.api, so a change to core.data.api can break recipe.data.repository, while a change to recipe.data.repository can't break core.data.api.
- Position
- Below the diagonal: recipe.data.repository uses a module listed above it, which is the healthy direction.
32→26 recipe.data.repository uses recipe.domain.repository✕
- Connections
- 1 pair of types, where a type in recipe.data.repository uses a type in recipe.domain.repository.
- The types involved
de.lukasneugebauer.nextcloudcookbook.recipe.data.repository.RecipeRepositoryImpl→de.lukasneugebauer.nextcloudcookbook.recipe.domain.repository.RecipeRepository
- Direction
- recipe.data.repository uses recipe.domain.repository, so a change to recipe.domain.repository can break recipe.data.repository, while a change to recipe.data.repository can't break recipe.domain.repository.
- Position
- Below the diagonal: recipe.data.repository uses a module listed above it, which is the healthy direction.
33→7 recipe.domain.usecase uses recipe.domain.model✕
- Connections
- 1 pair of types, where a type in recipe.domain.usecase uses a type in recipe.domain.model.
- The types involved
de.lukasneugebauer.nextcloudcookbook.recipe.domain.usecase.GetHomeScreenDataUseCase→de.lukasneugebauer.nextcloudcookbook.recipe.domain.model.HomeScreenDataResult
- Direction
- recipe.domain.usecase uses recipe.domain.model, so a change to recipe.domain.model can break recipe.domain.usecase, while a change to recipe.domain.usecase can't break recipe.domain.model.
- Position
- Below the diagonal: recipe.domain.usecase uses a module listed above it, which is the healthy direction.
33→12 recipe.domain.usecase uses core.data✕
- Connections
- 1 pair of types, where a type in recipe.domain.usecase uses a type in core.data.
- The types involved
de.lukasneugebauer.nextcloudcookbook.recipe.domain.usecase.GetHomeScreenDataUseCase→de.lukasneugebauer.nextcloudcookbook.core.data.PreferencesManager
- Direction
- recipe.domain.usecase uses core.data, so a change to core.data can break recipe.domain.usecase, while a change to recipe.domain.usecase can't break core.data.
- Position
- Below the diagonal: recipe.domain.usecase uses a module listed above it, which is the healthy direction.
33→19 recipe.domain.usecase uses recipe.data.dto✕
- Connections
- 2 pairs of types, where a type in recipe.domain.usecase uses a type in recipe.data.dto.
- The types involved
de.lukasneugebauer.nextcloudcookbook.recipe.domain.usecase.GetHomeScreenDataUseCase→de.lukasneugebauer.nextcloudcookbook.recipe.data.dto.RecipeDtode.lukasneugebauer.nextcloudcookbook.recipe.domain.usecase.GetHomeScreenDataUseCase→de.lukasneugebauer.nextcloudcookbook.recipe.data.dto.RecipePreviewDto
- Direction
- recipe.domain.usecase uses recipe.data.dto, so a change to recipe.data.dto can break recipe.domain.usecase, while a change to recipe.domain.usecase can't break recipe.data.dto.
- Position
- Below the diagonal: recipe.domain.usecase uses a module listed above it, which is the healthy direction.
33→26 recipe.domain.usecase uses recipe.domain.repository✕
- Connections
- 1 pair of types, where a type in recipe.domain.usecase uses a type in recipe.domain.repository.
- The types involved
de.lukasneugebauer.nextcloudcookbook.recipe.domain.usecase.GetAllKeywordsUseCase→de.lukasneugebauer.nextcloudcookbook.recipe.domain.repository.RecipeRepository
- Direction
- recipe.domain.usecase uses recipe.domain.repository, so a change to recipe.domain.repository can break recipe.domain.usecase, while a change to recipe.domain.usecase can't break recipe.domain.repository.
- Position
- Below the diagonal: recipe.domain.usecase uses a module listed above it, which is the healthy direction.
34→7 recipe.presentation.detail uses recipe.domain.model✕
- Connections
- 7 pairs of types, where a type in recipe.presentation.detail uses a type in recipe.domain.model.
- The types involved
de.lukasneugebauer.nextcloudcookbook.recipe.presentation.detail.RecipeDetailScreenKt→de.lukasneugebauer.nextcloudcookbook.recipe.domain.model.CalculatedIngredientde.lukasneugebauer.nextcloudcookbook.recipe.presentation.detail.RecipeDetailScreenKt→de.lukasneugebauer.nextcloudcookbook.recipe.domain.model.Instructionde.lukasneugebauer.nextcloudcookbook.recipe.presentation.detail.RecipeDetailScreenKt→de.lukasneugebauer.nextcloudcookbook.recipe.domain.model.Nutritionde.lukasneugebauer.nextcloudcookbook.recipe.presentation.detail.RecipeDetailScreenKt→de.lukasneugebauer.nextcloudcookbook.recipe.domain.model.Recipede.lukasneugebauer.nextcloudcookbook.recipe.presentation.detail.RecipeDetailScreenKt→de.lukasneugebauer.nextcloudcookbook.recipe.domain.model.Toolde.lukasneugebauer.nextcloudcookbook.recipe.presentation.detail.RecipeDetailViewModel→de.lukasneugebauer.nextcloudcookbook.recipe.domain.model.Recipede.lukasneugebauer.nextcloudcookbook.recipe.presentation.detail.RecipeDetailViewModel→de.lukasneugebauer.nextcloudcookbook.recipe.domain.model.RecipePreview
- Direction
- recipe.presentation.detail uses recipe.domain.model, so a change to recipe.domain.model can break recipe.presentation.detail, while a change to recipe.presentation.detail can't break recipe.domain.model.
- Position
- Below the diagonal: recipe.presentation.detail uses a module listed above it, which is the healthy direction.
34→9 recipe.presentation.detail uses recipe.domain✕
- Connections
- 2 pairs of types, where a type in recipe.presentation.detail uses a type in recipe.domain.
- The types involved
de.lukasneugebauer.nextcloudcookbook.recipe.presentation.detail.RecipeDetailViewModel→de.lukasneugebauer.nextcloudcookbook.recipe.domain.RecipeFormatterde.lukasneugebauer.nextcloudcookbook.recipe.presentation.detail.RecipeDetailViewModel→de.lukasneugebauer.nextcloudcookbook.recipe.domain.YieldCalculator
- Direction
- recipe.presentation.detail uses recipe.domain, so a change to recipe.domain can break recipe.presentation.detail, while a change to recipe.presentation.detail can't break recipe.domain.
- Position
- Below the diagonal: recipe.presentation.detail uses a module listed above it, which is the healthy direction.
34→12 recipe.presentation.detail uses core.data✕
- Connections
- 1 pair of types, where a type in recipe.presentation.detail uses a type in core.data.
- The types involved
de.lukasneugebauer.nextcloudcookbook.recipe.presentation.detail.RecipeDetailViewModel→de.lukasneugebauer.nextcloudcookbook.core.data.PreferencesManager
- Direction
- recipe.presentation.detail uses core.data, so a change to core.data can break recipe.presentation.detail, while a change to recipe.presentation.detail can't break core.data.
- Position
- Below the diagonal: recipe.presentation.detail uses a module listed above it, which is the healthy direction.
34→13 recipe.presentation.detail uses core.util✕
- Connections
- 1 pair of types, where a type in recipe.presentation.detail uses a type in core.util.
- The types involved
de.lukasneugebauer.nextcloudcookbook.recipe.presentation.detail.RecipeDetailScreenKt→de.lukasneugebauer.nextcloudcookbook.core.util.UiText
- Direction
- recipe.presentation.detail uses core.util, so a change to core.util can break recipe.presentation.detail, while a change to recipe.presentation.detail can't break core.util.
- Position
- Below the diagonal: recipe.presentation.detail uses a module listed above it, which is the healthy direction.
34→20 recipe.presentation.detail uses recipe.domain.state✕
- Connections
- 1 pair of types, where a type in recipe.presentation.detail uses a type in recipe.domain.state.
- The types involved
de.lukasneugebauer.nextcloudcookbook.recipe.presentation.detail.RecipeDetailViewModel→de.lukasneugebauer.nextcloudcookbook.recipe.domain.state.RecipeDetailState
- Direction
- recipe.presentation.detail uses recipe.domain.state, so a change to recipe.domain.state can break recipe.presentation.detail, while a change to recipe.presentation.detail can't break recipe.domain.state.
- Position
- Below the diagonal: recipe.presentation.detail uses a module listed above it, which is the healthy direction.
34→26 recipe.presentation.detail uses recipe.domain.repository✕
- Connections
- 1 pair of types, where a type in recipe.presentation.detail uses a type in recipe.domain.repository.
- The types involved
de.lukasneugebauer.nextcloudcookbook.recipe.presentation.detail.RecipeDetailViewModel→de.lukasneugebauer.nextcloudcookbook.recipe.domain.repository.RecipeRepository
- Direction
- recipe.presentation.detail uses recipe.domain.repository, so a change to recipe.domain.repository can break recipe.presentation.detail, while a change to recipe.presentation.detail can't break recipe.domain.repository.
- Position
- Below the diagonal: recipe.presentation.detail uses a module listed above it, which is the healthy direction.
35→7 recipe.presentation.list uses recipe.domain.model✕
- Connections
- 3 pairs of types, where a type in recipe.presentation.list uses a type in recipe.domain.model.
- The types involved
de.lukasneugebauer.nextcloudcookbook.recipe.presentation.list.RecipeListScreenKt→de.lukasneugebauer.nextcloudcookbook.recipe.domain.model.RecipeListScreenOrderde.lukasneugebauer.nextcloudcookbook.recipe.presentation.list.RecipeListScreenKt→de.lukasneugebauer.nextcloudcookbook.recipe.domain.model.RecipePreviewde.lukasneugebauer.nextcloudcookbook.recipe.presentation.list.RecipeListViewModel→de.lukasneugebauer.nextcloudcookbook.recipe.domain.model.RecipeListScreenOrder
- Direction
- recipe.presentation.list uses recipe.domain.model, so a change to recipe.domain.model can break recipe.presentation.list, while a change to recipe.presentation.list can't break recipe.domain.model.
- Position
- Below the diagonal: recipe.presentation.list uses a module listed above it, which is the healthy direction.
35→20 recipe.presentation.list uses recipe.domain.state✕
- Connections
- 2 pairs of types, where a type in recipe.presentation.list uses a type in recipe.domain.state.
- The types involved
de.lukasneugebauer.nextcloudcookbook.recipe.presentation.list.RecipeListViewModel→de.lukasneugebauer.nextcloudcookbook.recipe.domain.state.RecipeListScreenStatede.lukasneugebauer.nextcloudcookbook.recipe.presentation.list.RecipeListViewModel→de.lukasneugebauer.nextcloudcookbook.recipe.domain.state.SearchAppBarState
- Direction
- recipe.presentation.list uses recipe.domain.state, so a change to recipe.domain.state can break recipe.presentation.list, while a change to recipe.presentation.list can't break recipe.domain.state.
- Position
- Below the diagonal: recipe.presentation.list uses a module listed above it, which is the healthy direction.
35→25 recipe.presentation.list uses core.domain.usecase✕
- Connections
- 1 pair of types, where a type in recipe.presentation.list uses a type in core.domain.usecase.
- The types involved
de.lukasneugebauer.nextcloudcookbook.recipe.presentation.list.RecipeListViewModel→de.lukasneugebauer.nextcloudcookbook.core.domain.usecase.RefreshAllRecipesUseCase
- Direction
- recipe.presentation.list uses core.domain.usecase, so a change to core.domain.usecase can break recipe.presentation.list, while a change to recipe.presentation.list can't break core.domain.usecase.
- Position
- Below the diagonal: recipe.presentation.list uses a module listed above it, which is the healthy direction.
35→26 recipe.presentation.list uses recipe.domain.repository✕
- Connections
- 1 pair of types, where a type in recipe.presentation.list uses a type in recipe.domain.repository.
- The types involved
de.lukasneugebauer.nextcloudcookbook.recipe.presentation.list.RecipeListViewModel→de.lukasneugebauer.nextcloudcookbook.recipe.domain.repository.RecipeRepository
- Direction
- recipe.presentation.list uses recipe.domain.repository, so a change to recipe.domain.repository can break recipe.presentation.list, while a change to recipe.presentation.list can't break recipe.domain.repository.
- Position
- Below the diagonal: recipe.presentation.list uses a module listed above it, which is the healthy direction.
36→12 settings.presentation.settings uses core.data✕
- Connections
- 1 pair of types, where a type in settings.presentation.settings uses a type in core.data.
- The types involved
de.lukasneugebauer.nextcloudcookbook.settings.presentation.settings.SettingsViewModel→de.lukasneugebauer.nextcloudcookbook.core.data.PreferencesManager
- Direction
- settings.presentation.settings uses core.data, so a change to core.data can break settings.presentation.settings, while a change to settings.presentation.settings can't break core.data.
- Position
- Below the diagonal: settings.presentation.settings uses a module listed above it, which is the healthy direction.
36→24 settings.presentation.settings uses core.data.api✕
- Connections
- 1 pair of types, where a type in settings.presentation.settings uses a type in core.data.api.
- The types involved
de.lukasneugebauer.nextcloudcookbook.settings.presentation.settings.SettingsViewModel→de.lukasneugebauer.nextcloudcookbook.core.data.api.NcCookbookApiProvider
- Direction
- settings.presentation.settings uses core.data.api, so a change to core.data.api can break settings.presentation.settings, while a change to settings.presentation.settings can't break core.data.api.
- Position
- Below the diagonal: settings.presentation.settings uses a module listed above it, which is the healthy direction.
36→25 settings.presentation.settings uses core.domain.usecase✕
- Connections
- 2 pairs of types, where a type in settings.presentation.settings uses a type in core.domain.usecase.
- The types involved
de.lukasneugebauer.nextcloudcookbook.settings.presentation.settings.SettingsViewModel→de.lukasneugebauer.nextcloudcookbook.core.domain.usecase.ClearAllStoresUseCasede.lukasneugebauer.nextcloudcookbook.settings.presentation.settings.SettingsViewModel→de.lukasneugebauer.nextcloudcookbook.core.domain.usecase.ClearPreferencesUseCase
- Direction
- settings.presentation.settings uses core.domain.usecase, so a change to core.domain.usecase can break settings.presentation.settings, while a change to settings.presentation.settings can't break core.domain.usecase.
- Position
- Below the diagonal: settings.presentation.settings uses a module listed above it, which is the healthy direction.
37→2 recipe.util uses category.domain.model✕
- Connections
- 1 pair of types, where a type in recipe.util uses a type in category.domain.model.
- The types involved
de.lukasneugebauer.nextcloudcookbook.recipe.util.RecipeCreateEditViewModel→de.lukasneugebauer.nextcloudcookbook.category.domain.model.Category
- Direction
- recipe.util uses category.domain.model, so a change to category.domain.model can break recipe.util, while a change to recipe.util can't break category.domain.model.
- Position
- Below the diagonal: recipe.util uses a module listed above it, which is the healthy direction.
37→7 recipe.util uses recipe.domain.model✕
- Connections
- 3 pairs of types, where a type in recipe.util uses a type in recipe.domain.model.
- The types involved
de.lukasneugebauer.nextcloudcookbook.recipe.util.DurationToDurationComponentsKt→de.lukasneugebauer.nextcloudcookbook.recipe.domain.model.DurationComponentsde.lukasneugebauer.nextcloudcookbook.recipe.util.EmptyRecipeKt→de.lukasneugebauer.nextcloudcookbook.recipe.domain.model.Recipede.lukasneugebauer.nextcloudcookbook.recipe.util.RecipeCreateEditViewModel→de.lukasneugebauer.nextcloudcookbook.recipe.domain.model.DurationComponents
- Direction
- recipe.util uses recipe.domain.model, so a change to recipe.domain.model can break recipe.util, while a change to recipe.util can't break recipe.domain.model.
- Position
- Below the diagonal: recipe.util uses a module listed above it, which is the healthy direction.
37→11 recipe.util uses recipe.domain.util✕
- Connections
- 1 pair of types, where a type in recipe.util uses a type in recipe.domain.util.
- The types involved
de.lukasneugebauer.nextcloudcookbook.recipe.util.RecipeCreateEditViewModel→de.lukasneugebauer.nextcloudcookbook.recipe.domain.util.ImageCompressionService
- Direction
- recipe.util uses recipe.domain.util, so a change to recipe.domain.util can break recipe.util, while a change to recipe.util can't break recipe.domain.util.
- Position
- Below the diagonal: recipe.util uses a module listed above it, which is the healthy direction.
37→13 recipe.util uses core.util✕
- Connections
- 1 pair of types, where a type in recipe.util uses a type in core.util.
- The types involved
de.lukasneugebauer.nextcloudcookbook.recipe.util.RecipeCreateEditViewModel→de.lukasneugebauer.nextcloudcookbook.core.util.UiText
- Direction
- recipe.util uses core.util, so a change to core.util can break recipe.util, while a change to recipe.util can't break core.util.
- Position
- Below the diagonal: recipe.util uses a module listed above it, which is the healthy direction.
37→17 recipe.util uses category.domain.repository✕
- Connections
- 1 pair of types, where a type in recipe.util uses a type in category.domain.repository.
- The types involved
de.lukasneugebauer.nextcloudcookbook.recipe.util.RecipeCreateEditViewModel→de.lukasneugebauer.nextcloudcookbook.category.domain.repository.CategoryRepository
- Direction
- recipe.util uses category.domain.repository, so a change to category.domain.repository can break recipe.util, while a change to recipe.util can't break category.domain.repository.
- Position
- Below the diagonal: recipe.util uses a module listed above it, which is the healthy direction.
37→19 recipe.util uses recipe.data.dto✕
- Connections
- 3 pairs of types, where a type in recipe.util uses a type in recipe.data.dto.
- The types involved
de.lukasneugebauer.nextcloudcookbook.recipe.util.EmptyRecipeDtoKt→de.lukasneugebauer.nextcloudcookbook.recipe.data.dto.RecipeDtode.lukasneugebauer.nextcloudcookbook.recipe.util.RecipeCreateEditViewModel→de.lukasneugebauer.nextcloudcookbook.recipe.data.dto.NutritionDtode.lukasneugebauer.nextcloudcookbook.recipe.util.RecipeCreateEditViewModel→de.lukasneugebauer.nextcloudcookbook.recipe.data.dto.RecipeDto
- Direction
- recipe.util uses recipe.data.dto, so a change to recipe.data.dto can break recipe.util, while a change to recipe.util can't break recipe.data.dto.
- Position
- Below the diagonal: recipe.util uses a module listed above it, which is the healthy direction.
37→20 recipe.util uses recipe.domain.state✕
- Connections
- 1 pair of types, where a type in recipe.util uses a type in recipe.domain.state.
- The types involved
de.lukasneugebauer.nextcloudcookbook.recipe.util.RecipeCreateEditViewModel→de.lukasneugebauer.nextcloudcookbook.recipe.domain.state.RecipeCreateEditState
- Direction
- recipe.util uses recipe.domain.state, so a change to recipe.domain.state can break recipe.util, while a change to recipe.util can't break recipe.domain.state.
- Position
- Below the diagonal: recipe.util uses a module listed above it, which is the healthy direction.
37→26 recipe.util uses recipe.domain.repository✕
- Connections
- 1 pair of types, where a type in recipe.util uses a type in recipe.domain.repository.
- The types involved
de.lukasneugebauer.nextcloudcookbook.recipe.util.RecipeCreateEditViewModel→de.lukasneugebauer.nextcloudcookbook.recipe.domain.repository.RecipeRepository
- Direction
- recipe.util uses recipe.domain.repository, so a change to recipe.domain.repository can break recipe.util, while a change to recipe.util can't break recipe.domain.repository.
- Position
- Below the diagonal: recipe.util uses a module listed above it, which is the healthy direction.
37→27 recipe.util uses recipe.domain.state.RecipeCreateEditState✕
- Connections
- 1 pair of types, where a type in recipe.util uses a type in recipe.domain.state.RecipeCreateEditState.
- The types involved
de.lukasneugebauer.nextcloudcookbook.recipe.util.RecipeCreateEditViewModel→de.lukasneugebauer.nextcloudcookbook.recipe.domain.state.RecipeCreateEditState.Success
- Direction
- recipe.util uses recipe.domain.state.RecipeCreateEditState, so a change to recipe.domain.state.RecipeCreateEditState can break recipe.util, while a change to recipe.util can't break recipe.domain.state.RecipeCreateEditState.
- Position
- Below the diagonal: recipe.util uses a module listed above it, which is the healthy direction.
37→33 recipe.util uses recipe.domain.usecase✕
- Connections
- 1 pair of types, where a type in recipe.util uses a type in recipe.domain.usecase.
- The types involved
de.lukasneugebauer.nextcloudcookbook.recipe.util.RecipeCreateEditViewModel→de.lukasneugebauer.nextcloudcookbook.recipe.domain.usecase.GetAllKeywordsUseCase
- Direction
- recipe.util uses recipe.domain.usecase, so a change to recipe.domain.usecase can break recipe.util, while a change to recipe.util can't break recipe.domain.usecase.
- Position
- Below the diagonal: recipe.util uses a module listed above it, which is the healthy direction.
38→11 recipe.presentation.create uses recipe.domain.util✕
- Connections
- 1 pair of types, where a type in recipe.presentation.create uses a type in recipe.domain.util.
- The types involved
de.lukasneugebauer.nextcloudcookbook.recipe.presentation.create.RecipeCreateViewModel→de.lukasneugebauer.nextcloudcookbook.recipe.domain.util.ImageCompressionService
- Direction
- recipe.presentation.create uses recipe.domain.util, so a change to recipe.domain.util can break recipe.presentation.create, while a change to recipe.presentation.create can't break recipe.domain.util.
- Position
- Below the diagonal: recipe.presentation.create uses a module listed above it, which is the healthy direction.
38→17 recipe.presentation.create uses category.domain.repository✕
- Connections
- 1 pair of types, where a type in recipe.presentation.create uses a type in category.domain.repository.
- The types involved
de.lukasneugebauer.nextcloudcookbook.recipe.presentation.create.RecipeCreateViewModel→de.lukasneugebauer.nextcloudcookbook.category.domain.repository.CategoryRepository
- Direction
- recipe.presentation.create uses category.domain.repository, so a change to category.domain.repository can break recipe.presentation.create, while a change to recipe.presentation.create can't break category.domain.repository.
- Position
- Below the diagonal: recipe.presentation.create uses a module listed above it, which is the healthy direction.
38→26 recipe.presentation.create uses recipe.domain.repository✕
- Connections
- 1 pair of types, where a type in recipe.presentation.create uses a type in recipe.domain.repository.
- The types involved
de.lukasneugebauer.nextcloudcookbook.recipe.presentation.create.RecipeCreateViewModel→de.lukasneugebauer.nextcloudcookbook.recipe.domain.repository.RecipeRepository
- Direction
- recipe.presentation.create uses recipe.domain.repository, so a change to recipe.domain.repository can break recipe.presentation.create, while a change to recipe.presentation.create can't break recipe.domain.repository.
- Position
- Below the diagonal: recipe.presentation.create uses a module listed above it, which is the healthy direction.
38→33 recipe.presentation.create uses recipe.domain.usecase✕
- Connections
- 1 pair of types, where a type in recipe.presentation.create uses a type in recipe.domain.usecase.
- The types involved
de.lukasneugebauer.nextcloudcookbook.recipe.presentation.create.RecipeCreateViewModel→de.lukasneugebauer.nextcloudcookbook.recipe.domain.usecase.GetAllKeywordsUseCase
- Direction
- recipe.presentation.create uses recipe.domain.usecase, so a change to recipe.domain.usecase can break recipe.presentation.create, while a change to recipe.presentation.create can't break recipe.domain.usecase.
- Position
- Below the diagonal: recipe.presentation.create uses a module listed above it, which is the healthy direction.
38→37 recipe.presentation.create uses recipe.util✕
- Connections
- 1 pair of types, where a type in recipe.presentation.create uses a type in recipe.util.
- The types involved
de.lukasneugebauer.nextcloudcookbook.recipe.presentation.create.RecipeCreateViewModel→de.lukasneugebauer.nextcloudcookbook.recipe.util.RecipeCreateEditViewModel
- Direction
- recipe.presentation.create uses recipe.util, so a change to recipe.util can break recipe.presentation.create, while a change to recipe.presentation.create can't break recipe.util.
- Position
- Below the diagonal: recipe.presentation.create uses a module listed above it, which is the healthy direction.
39→13 recipe.presentation.download uses core.util✕
- Connections
- 1 pair of types, where a type in recipe.presentation.download uses a type in core.util.
- The types involved
de.lukasneugebauer.nextcloudcookbook.recipe.presentation.download.DownloadRecipeScreenKt→de.lukasneugebauer.nextcloudcookbook.core.util.UiText
- Direction
- recipe.presentation.download uses core.util, so a change to core.util can break recipe.presentation.download, while a change to recipe.presentation.download can't break core.util.
- Position
- Below the diagonal: recipe.presentation.download uses a module listed above it, which is the healthy direction.
39→20 recipe.presentation.download uses recipe.domain.state✕
- Connections
- 2 pairs of types, where a type in recipe.presentation.download uses a type in recipe.domain.state.
- The types involved
de.lukasneugebauer.nextcloudcookbook.recipe.presentation.download.DownloadRecipeScreenKt→de.lukasneugebauer.nextcloudcookbook.recipe.domain.state.DownloadRecipeScreenStatede.lukasneugebauer.nextcloudcookbook.recipe.presentation.download.DownloadRecipeViewModel→de.lukasneugebauer.nextcloudcookbook.recipe.domain.state.DownloadRecipeScreenState
- Direction
- recipe.presentation.download uses recipe.domain.state, so a change to recipe.domain.state can break recipe.presentation.download, while a change to recipe.presentation.download can't break recipe.domain.state.
- Position
- Below the diagonal: recipe.presentation.download uses a module listed above it, which is the healthy direction.
39→26 recipe.presentation.download uses recipe.domain.repository✕
- Connections
- 1 pair of types, where a type in recipe.presentation.download uses a type in recipe.domain.repository.
- The types involved
de.lukasneugebauer.nextcloudcookbook.recipe.presentation.download.DownloadRecipeViewModel→de.lukasneugebauer.nextcloudcookbook.recipe.domain.repository.RecipeRepository
- Direction
- recipe.presentation.download uses recipe.domain.repository, so a change to recipe.domain.repository can break recipe.presentation.download, while a change to recipe.presentation.download can't break recipe.domain.repository.
- Position
- Below the diagonal: recipe.presentation.download uses a module listed above it, which is the healthy direction.
39→37 recipe.presentation.download uses recipe.util✕
- Connections
- 2 pairs of types, where a type in recipe.presentation.download uses a type in recipe.util.
- The types involved
de.lukasneugebauer.nextcloudcookbook.recipe.presentation.download.DownloadRecipeScreenKt→de.lukasneugebauer.nextcloudcookbook.recipe.util.ConflictStatede.lukasneugebauer.nextcloudcookbook.recipe.presentation.download.DownloadRecipeViewModel→de.lukasneugebauer.nextcloudcookbook.recipe.util.ConflictState
- Direction
- recipe.presentation.download uses recipe.util, so a change to recipe.util can break recipe.presentation.download, while a change to recipe.presentation.download can't break recipe.util.
- Position
- Below the diagonal: recipe.presentation.download uses a module listed above it, which is the healthy direction.
40→11 recipe.presentation.edit uses recipe.domain.util✕
- Connections
- 1 pair of types, where a type in recipe.presentation.edit uses a type in recipe.domain.util.
- The types involved
de.lukasneugebauer.nextcloudcookbook.recipe.presentation.edit.RecipeEditViewModel→de.lukasneugebauer.nextcloudcookbook.recipe.domain.util.ImageCompressionService
- Direction
- recipe.presentation.edit uses recipe.domain.util, so a change to recipe.domain.util can break recipe.presentation.edit, while a change to recipe.presentation.edit can't break recipe.domain.util.
- Position
- Below the diagonal: recipe.presentation.edit uses a module listed above it, which is the healthy direction.
40→17 recipe.presentation.edit uses category.domain.repository✕
- Connections
- 1 pair of types, where a type in recipe.presentation.edit uses a type in category.domain.repository.
- The types involved
de.lukasneugebauer.nextcloudcookbook.recipe.presentation.edit.RecipeEditViewModel→de.lukasneugebauer.nextcloudcookbook.category.domain.repository.CategoryRepository
- Direction
- recipe.presentation.edit uses category.domain.repository, so a change to category.domain.repository can break recipe.presentation.edit, while a change to recipe.presentation.edit can't break category.domain.repository.
- Position
- Below the diagonal: recipe.presentation.edit uses a module listed above it, which is the healthy direction.
40→26 recipe.presentation.edit uses recipe.domain.repository✕
- Connections
- 1 pair of types, where a type in recipe.presentation.edit uses a type in recipe.domain.repository.
- The types involved
de.lukasneugebauer.nextcloudcookbook.recipe.presentation.edit.RecipeEditViewModel→de.lukasneugebauer.nextcloudcookbook.recipe.domain.repository.RecipeRepository
- Direction
- recipe.presentation.edit uses recipe.domain.repository, so a change to recipe.domain.repository can break recipe.presentation.edit, while a change to recipe.presentation.edit can't break recipe.domain.repository.
- Position
- Below the diagonal: recipe.presentation.edit uses a module listed above it, which is the healthy direction.
40→33 recipe.presentation.edit uses recipe.domain.usecase✕
- Connections
- 1 pair of types, where a type in recipe.presentation.edit uses a type in recipe.domain.usecase.
- The types involved
de.lukasneugebauer.nextcloudcookbook.recipe.presentation.edit.RecipeEditViewModel→de.lukasneugebauer.nextcloudcookbook.recipe.domain.usecase.GetAllKeywordsUseCase
- Direction
- recipe.presentation.edit uses recipe.domain.usecase, so a change to recipe.domain.usecase can break recipe.presentation.edit, while a change to recipe.presentation.edit can't break recipe.domain.usecase.
- Position
- Below the diagonal: recipe.presentation.edit uses a module listed above it, which is the healthy direction.
40→37 recipe.presentation.edit uses recipe.util✕
- Connections
- 1 pair of types, where a type in recipe.presentation.edit uses a type in recipe.util.
- The types involved
de.lukasneugebauer.nextcloudcookbook.recipe.presentation.edit.RecipeEditViewModel→de.lukasneugebauer.nextcloudcookbook.recipe.util.RecipeCreateEditViewModel
- Direction
- recipe.presentation.edit uses recipe.util, so a change to recipe.util can break recipe.presentation.edit, while a change to recipe.presentation.edit can't break recipe.util.
- Position
- Below the diagonal: recipe.presentation.edit 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 |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 14 | High / Critical |
| A05:2025 — Injection | 8 | High / Critical |
Roadmap
Top priorities: Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing; Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md; Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.gradle.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing. | +9.0 pts | Medium | Security & performance tooling |
| Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md. | +3.9 pts | Low | Documentation Quality |
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.gradle. | +3.9 pts | Low | ADR Quality |
| Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it. | +3.6 pts | Medium | Deployment & Rollback |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +3.6 pts | Medium | Release Hygiene |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +3.2 pts | Medium | Architecture documentation |
| Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. | +1.4 pts | Low | Bus Factor |
| Resolve the 1 Off-boarding risk finding(s) in Bus Factor. | +1.4 pts | Low | Bus Factor |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.4 | Slop | Dependency Vulnerabilities: High vulnerability: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Mixed | Static Analysis (SAST): High: REDACTED |
| app/src/main/java/de/lukasneugebauer/nextcloudcookbook/recipe/presentation/components/CreateEditRecipeForm.kt | 5.5 | Mixed | God Classes: FileTooLong: components/CreateEditRecipeForm.kt |
| app/src/main/java/de/lukasneugebauer/nextcloudcookbook/recipe/presentation/detail/RecipeDetailScreen.kt | 6.0 | Mixed | Explicit Debt: TodoComment |
| app/src/main/java/de/lukasneugebauer/nextcloudcookbook/recipe/presentation/create/RecipeCreateScreen.kt | 6.3 | Mixed | God Classes: MethodTooLong: RecipeCreateScreenKt.RecipeCreateScreen |
| app/src/main/java/de/lukasneugebauer/nextcloudcookbook/recipe/data/repository/RecipeRepositoryImpl.kt | 7.0 | Near-clean | Code Duplication: Edited copy of a member (18 corresponding lines) |
| app/src/main/java/de/lukasneugebauer/nextcloudcookbook/recipe/presentation/create/RecipeCreateViewModel.kt | 7.0 | Near-clean | Code Duplication: Duplicated block (11 lines × 2) |
| app/src/main/java/de/lukasneugebauer/nextcloudcookbook/core/domain/repository/BaseRepository.kt | 7.8 | Near-clean | Cyclomatic Complexity: BaseRepository.handleResponseError (cyclomatic 26) |
| app/src/main/java/de/lukasneugebauer/nextcloudcookbook/core/presentation/MainActivity.kt | 7.8 | Near-clean | Cyclomatic Complexity: MainActivityKt.NextcloudCookbookApp (cyclomatic 19) |
| app/src/main/java/de/lukasneugebauer/nextcloudcookbook/recipe/presentation/list/RecipeListViewModel.kt | 7.8 | Near-clean | Cyclomatic Complexity: RecipeListViewModel.getRecipePreviews (cyclomatic 18) |
| app/src/main/java/de/lukasneugebauer/nextcloudcookbook/recipe/util/RecipeCreateEditViewModel.kt | 7.8 | Near-clean | God Classes: TooManyMethods: RecipeCreateEditViewModel |
| app/src/main/java/de/lukasneugebauer/nextcloudcookbook/auth/presentation/browser/BrowserLoginViewModel.kt | 7.8 | Near-clean | Code Duplication: Edited copy of a member (30 corresponding lines) |
| app/src/main/java/de/lukasneugebauer/nextcloudcookbook/settings/presentation/info/InfoScreen.kt | 7.8 | Near-clean | Code Duplication: Duplicated block (30 lines × 2) |
| REDACTED | 7.9 | Near-clean | Static Analysis (SAST): Medium: REDACTED |
| app/src/main/java/de/lukasneugebauer/nextcloudcookbook/recipe/domain/model/Recipe.kt | 8.2 | Near-clean | Explicit Debt: TodoComment |
| app/src/main/java/de/lukasneugebauer/nextcloudcookbook/recipe/domain/model/RecipePreview.kt | 8.2 | Near-clean | Explicit Debt: TodoComment |
| app/src/main/java/de/lukasneugebauer/nextcloudcookbook/recipe/data/YieldCalculatorImpl.kt | 8.5 | Near-clean | Cognitive Complexity: YieldCalculatorImpl.recalculateIngredients (cognitive 22) |
| app/src/main/java/de/lukasneugebauer/nextcloudcookbook/recipe/data/RecipeFormatterImpl.kt | 8.5 | Near-clean | Cognitive Complexity: RecipeFormatterImpl.format (cognitive 16) |
| app/src/main/java/de/lukasneugebauer/nextcloudcookbook/recipe/presentation/edit/RecipeEditScreen.kt | 8.5 | Near-clean | God Classes: MethodTooLong: RecipeEditScreenKt.RecipeEditScreen |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 46 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 46 dimensions across the health lenses
- Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 77 of 87 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.kt) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.kt) and this repository declares a JVM test suite (repository root, Gradle), but it was not re-run: no test result was produced. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares a Gradle build (build.gradle/build.gradle.kts), but the licence verdict published here was taken over its gem dependencies. Nothing was read about its Gradle dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares package.json, but the licence verdict published here was taken over its gem dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is a COLLECTOR gap, not an environment fault: no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
- 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. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- D26 Project Cohesion — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `app` (12508 LoC, 276 module-visible types across 65 directories) is over its size bounds, and whether one unit is a coherent whole or a grab-bag is read from its type references: the parts of it that reach the rest only through its shared core. Those are read over the C#/VB code model, which this unit's source did not supply. Its size alone is no verdict on its cohesion, so none is published.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `app/src/main/java/de/lukasneugebauer/nextcloudcookbook/recipe/presentation/detail/RecipeDetailScreen.kt` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Boot via AndroidApp (app). the Android app did not build — `./gradlew :app:assembleDebug` exited 1: Unable to download toolchain matching the requirements ({languageVersion=21, vendor=JetBrains, implementation=vendor-specific, nativeImageCapable=false}) from 'https://api.foojay.io/disco/v3.0/ids/ecd…; runtime evidence skipped (launch chosen because app/build.gradle applies the Android application plugin and gradlew builds it).
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- DM8 Value-object opportunities — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check finds primitive parameters that travel together through several signatures of the domain (a missing value object). Its deterministic rule has not yet shown 95 % precision on adjudicated rows, so the clumps it finds are counted here and not published as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
- DM9 Scattered domain decisions — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not measured — scattered-decision detection needs expression-level symbol resolution: a comparison operand bound to the member it judges (arm one) and a construction bound to the type it produces (arm two). A Roslyn compilation carries both; arm two alone also runs on any frontend that declares whether a construction is produced or passed, and this target loaded neither.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java source only, and this repository's Kotlin, Vue components is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby, Scala and Rust source only, and this repository's Kotlin, Vue components is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P1 CI/CD gates — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. A CI pipeline exists and the word "test" appears, but no explicit test-runner invocation (your stack's test command, or a test job) was matched — so either the gate runs tests through a step this pass could not recognise, or "test" is incidental here (a path, "latest", a reporter). Which of the two it is cannot be settled from this dimension's evidence; the coverage dimensions report whether a suite exists at all. You can widen what we reach: name the test runner explicitly in the pipeline step (your stack's test command, or a job named for the suite) so the gate is unambiguous to a reader and to this pass.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
4 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was BaseRepository.handleResponseError at 26.
What to do
- Bring the 4 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with BaseRepository.handleResponseError (cyclomatic 26), MainActivityKt.NextcloudCookbookApp (cyclomatic 19), RecipeDetailScreenKt.RecipeDetailLayout (cyclomatic 19). — 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 4 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
5 method(s) exceeded the cognitive complexity threshold of 15; the worst was RecipeDetailScreenKt.RecipeDetailLayout at 29.
What to do
- Bring the 5 bodies over 15 down to 15 or less in Cognitive Complexity — start with RecipeDetailScreenKt.RecipeDetailLayout (cognitive 29), YieldCalculatorImpl.recalculateIngredients (cognitive 22), MainActivityKt.NextcloudCookbookApp (cognitive 21). — 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 Cognitive Complexity from 8.9 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
7 god class(es) detected.
What to do
- Resolve the 4 MethodTooLong finding(s) in God Classes — start with RecipeDetailScreen.kt (2), RecipeCreateScreen.kt, RecipeEditScreen.kt. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 2 FileTooLong finding(s) in God Classes — start with CreateEditRecipeForm.kt, RecipeDetailScreen.kt. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 TooManyMethods finding(s) in God Classes — start with RecipeCreateEditViewModel.kt. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
11 duplicated block group(s) detected. 9.8 % of the production lines (1,226 of 12,544) are in a reported copy. A further 10 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
What to do
- Resolve the 2 Edited copy of a member (20 corresponding lines) finding(s) in Code Duplication — start with AccountRepositoryImpl.kt, RecipeListScreen.kt. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Edited copies of one member (3 members, 63+ corresponding lines) finding(s) in Code Duplication — start with CreateEditRecipeForm.kt. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Edited copies of one member (3 members, 49+ corresponding lines) finding(s) in Code Duplication — start with SettingsScreen.kt. — One of this dimension's main actionable groups (1 warning-level).
D5 · Coupling
2 production modules (Gradle), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; edges a convention plugin adds from buildSrc or build-logic are not visible there; 0 module(s) off the main sequence, with abstractness counted on 1 of the 2 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
D6 · Cohesion (LCOM4)
0 of 21 classes have LCOM4 above 3.
D12 · Dependency Hygiene
1 outdated direct gem(s), 0 pinning defect(s). 1 declaration(s) graded against rubygems.org, 1 of them against a version resolved in a committed Gemfile.lock. Whether any of these gems is DEPRECATED or YANKED is not graded — rubygems.org publishes no deprecation marker, and a yank removes a version rather than flagging it. Whether any is UNMAINTAINED is not graded either: no registry publishes a maintenance status, and release age does not stand in for one. Whether any is UNUSED is a source question, not a registry one. Known CVEs in this dependency graph are D30's question, read from the manifest there.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 105 shipped gem(s) use a banned license. Licences were resolved from rubygems.org over the 105 gem(s) a consumer installs — this repository's runtime declarations closed transitively over its committed Gemfile.lock. Development-group and `add_development_dependency` gems are excluded: they are not distributed with this repository. 1 of them publish no licence on rubygems.org; that is missing data, not a violation, and none of them is charged. ★ COVERAGE OF THIS VERDICT: it grades this repository's gem dependencies and nothing else. The repository also declares a Gradle build (build.gradle/build.gradle.kts) and package.json, and the licences of those dependency graphs were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
D15 · Churn × Complexity Hotspots
Top hotspots: app/src/main/java/de/lukasneugebauer/nextcloudcookbook/recipe/presentation/detail/RecipeDetailScreen.kt (5×19=95) Repeated repair below the complexity floor: app/src/main/java/de/lukasneugebauer/nextcloudcookbook/recipe/presentation/detail/RecipeDetailViewModel.kt (3 of 3 changes were fixes); app/src/main/java/de/lukasneugebauer/nextcloudcookbook/auth/presentation/browser/BrowserLoginViewModel.kt (3 of 3 changes were fixes)
What to do
- Resolve the 2 Repeated repair finding(s) in Churn × Complexity Hotspots — start with RecipeDetailViewModel.kt, BrowserLoginViewModel.kt. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Hotspot finding(s) in Churn × Complexity Hotspots — start with RecipeDetailScreen.kt. — One of this dimension's main actionable groups (1 warning-level).
D16 · Bus Factor
16 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is app/src/main/java/de/lukasneugebauer/nextcloudcookbook/recipe/presentation/home/HomeScreen.kt. Counted over 52 of the 188 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
D17 · Explicit Debt
4 deducted task-comment markers across 12544 LoC (0.0/KLoC) → score 9.9. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 4 TodoComment finding(s) in Explicit Debt — start with RecipeDetailScreen.kt (2), Recipe.kt, RecipePreview.kt. — One of this dimension's main actionable groups (4 warning-level).
D19 · Documentation Quality
0 of 1 documentation facets pass in full; short on: F2 example. 8 document(s) read across 2 unit(s).
What to do
- Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md. — One of this dimension's main actionable groups (1 recommendation-level).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.gradle. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
8 finding(s): 0 critical, 7 high, 1 medium, 0 low. 6 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 1 file(s) — `gradlew` (line 74, line 181) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
What to do
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- No action in Static Analysis (SAST) — all 6 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (6 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
7 finding(s): 0 critical, 6 high, 1 medium, 0 low.
What to do
- Resolve the 5 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (5). — One of this dimension's main actionable groups (5 issue-level).
- Resolve the 1 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Medium vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 52 of the 188 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
Strongest change-coupling: RecipeCreateViewModel.kt↔RecipeEditScreen.kt 82%; CategoryListScreen.kt↔RecipeListScreen.kt 78%; NcCookbookApi.kt↔AccountRepositoryImpl.kt 75%
What to do
- Resolve the 5 Change coupling finding(s) in Change Coupling — start with RecipeCreateViewModel.kt, CategoryListScreen.kt, RecipeCreateScreen.kt. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 2 Change-coupling hub finding(s) in Change Coupling — start with NcCookbookApi.kt, CreateEditRecipeForm.kt. — One of this dimension's main actionable groups (2 warning-level).
D36 · Supply-chain Provenance & Signing
1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 43 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX2 · Stateful singletons
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
DM11 · Constructible invalid state
- `CategoryEntity`'s public constructor takes `name` 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 `CategoryEntity` 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/de/lukasneugebauer/nextcloudcookbook/category/domain/model/CategoryEntity.kt:7
- `RecipeEntity`'s public constructor takes `id`, `json`, `syncedDateModified` 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 `RecipeEntity` 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/de/lukasneugebauer/nextcloudcookbook/recipe/domain/model/RecipeEntity.kt:7
- `RecipePreviewEntity`'s public constructor takes `id`, `name`, `keywords`, `category`, … 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 `RecipePreviewEntity` 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/de/lukasneugebauer/nextcloudcookbook/recipe/domain/model/RecipePreviewEntity.kt:7
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
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
What to do
- Run the test suite in CI via an explicit runner step (`bundle exec rspec` for the toolchain this pipeline already uses) and gate merges on it.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add spotbugs with find-sec-bugs (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 2 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:8
- `package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — package.json:2
What to do
- Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
What to do
- Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
PF3 · Async & latency hygiene
X1 · Async correctness
X12 · Unreachable branch
X16 · Unfloored truncation loop
X21 · Side-effecting pattern guard
X23 · Unguarded diagnostic materialisation
X3 · Exception handling
X5 · Nullable reference types
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 93.6 | Exemplary | Solid. |
| Architecture | 94.2 | Exemplary | Solid. |
| Maturity | 63.6 | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 47.7 | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 76.2 | Adequate — gated by D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 69.7 | Adequate — gated by DM11 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100.0 | Exemplary | Strongest area. |
Unscored — 1 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 80 check(s) not relevant to this codebase
- AC1 Text alternatives — Frontend below the scale floor (6 DOM element(s) < 25) — too little surface to assess accessibility.
- AC2 Forms & labels — Frontend below the scale floor (6 DOM element(s) < 25) — too little surface to assess accessibility.
- AC3 Page structure — Frontend below the scale floor (6 DOM element(s) < 25) — too little surface to assess accessibility.
- AC4 Keyboard semantics — Frontend below the scale floor (6 DOM element(s) < 25) — too little surface to assess accessibility.
- AC5 ARIA correctness — Frontend below the scale floor (6 DOM element(s) < 25) — too little surface to assess accessibility.
- AC6 Visual & motion safety — Frontend below the scale floor (6 DOM element(s) < 25) — too little surface to assess accessibility.
- AX1 Captive dependencies — Not applicable: Dagger rejects, at compile time, a component that holds a binding with a narrower scope than its own.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — the Android app did not build — `./gradlew :app:assembleDebug` exited 1: Unable to download toolchain matching the requirements ({languageVersion=21, vendor=JetBrains, implementation=vendor-specific, nativeImageCapable=false}) from 'https://api.foojay.io/disco/v3.0/ids/ecd…; runtime evidence skipped (launch chosen because app/build.gradle applies the Android application plugin and gradlew builds it) This is a statement about this run, not a statement about your application: nothing here says the app is inaccessible, only that it was never run.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no data at rest for these controls to protect.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named column (email, first_name, date_of_birth, phone_number, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~2443 lines of test source are present (.kt) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not included — the .kt suite was found but not re-run
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (1843 declarations, no unit with a dominant convention).
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .kt source were not judged.
- D25 ADR Conformance — no ADRs to check
- D26 Project Cohesion — D26 could not read how the parts of this repository's one build unit reference each other, so its cohesion was not measured. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D27 Navigability — symbol resolution incomplete — navigability not assessed
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — 1 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Aggregate boundaries — no aggregates detected — aggregate-boundary check not applicable
- 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, Scala, Rust and Java, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P2 Observability — This repository's JVM source (1 module(s), 185 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 — no outbound HTTP usage detected — no HTTP client call or construction in the JVM, JavaScript/TypeScript source (service entry point: app/src/main/java/de/lukasneugebauer/nextcloudcookbook/core/data/api/NcCookbookApi.kt:51 (@Path())
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a pom.xml, Gradle or sbt build, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — no C# was loaded; this repository's Kotlin was read, and no request in it can be cancelled by a caller (Ktor, OkHttp's newCall or a URL stream, from a suspend function) — a Kotlin request outside a suspend function has no caller's cancellation to honour
- X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X27 Collection changed while being enumerated — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Kotlin was read, and it logs through none that an assembled message defeats: Android's `Log` and Timber, java.util.logging and log4j-api-kotlin take one finished message (as log4net does in C#), or it makes no call through a named logger at all. Calls made through SLF4J, log4j 2 or kotlin-logging (`LoggerFactory.getLogger`, `KotlinLogging.logger {}`) would be judged.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 13 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 60 finding(s)
- Change coupling: RecipeCreateViewModel.kt ↔ RecipeEditScreen.kt app/src/main/java/de/lukasneugebauer/nextcloudcookbook/recipe/presentation/create/RecipeCreateViewModel.kt:1
- Change coupling: CategoryListScreen.kt ↔ RecipeListScreen.kt app/src/main/java/de/lukasneugebauer/nextcloudcookbook/category/presentation/list/CategoryListScreen.kt:1
- Change coupling: RecipeCreateScreen.kt ↔ RecipeEditViewModel.kt app/src/main/java/de/lukasneugebauer/nextcloudcookbook/recipe/presentation/create/RecipeCreateScreen.kt:1
- Change coupling: CategoryListViewModel.kt ↔ RecipeDetailViewModel.kt app/src/main/java/de/lukasneugebauer/nextcloudcookbook/category/presentation/list/CategoryListViewModel.kt:1
- Change coupling: RecipeRepositoryImpl.kt ↔ RecipeEditViewModel.kt app/src/main/java/de/lukasneugebauer/nextcloudcookbook/recipe/data/repository/RecipeRepositoryImpl.kt:1
- TodoComment app/src/main/java/de/lukasneugebauer/nextcloudcookbook/recipe/presentation/detail/RecipeDetailScreen.kt:592
- TodoComment app/src/main/java/de/lukasneugebauer/nextcloudcookbook/recipe/presentation/detail/RecipeDetailScreen.kt:600
- TodoComment app/src/main/java/de/lukasneugebauer/nextcloudcookbook/recipe/domain/model/Recipe.kt:22
- TodoComment app/src/main/java/de/lukasneugebauer/nextcloudcookbook/recipe/domain/model/RecipePreview.kt:9
- MethodTooLong: RecipeCreateScreenKt.RecipeCreateScreen app/src/main/java/de/lukasneugebauer/nextcloudcookbook/recipe/presentation/create/RecipeCreateScreen.kt:26
- MethodTooLong: RecipeEditScreenKt.RecipeEditScreen app/src/main/java/de/lukasneugebauer/nextcloudcookbook/recipe/presentation/edit/RecipeEditScreen.kt:26
- MethodTooLong: RecipeDetailScreenKt.Ingredients app/src/main/java/de/lukasneugebauer/nextcloudcookbook/recipe/presentation/detail/RecipeDetailScreen.kt:662
- MethodTooLong: RecipeDetailScreenKt.RecipeDetailLayout app/src/main/java/de/lukasneugebauer/nextcloudcookbook/recipe/presentation/detail/RecipeDetailScreen.kt:356
- Constructible in an invalid state: CategoryEntity app/src/main/java/de/lukasneugebauer/nextcloudcookbook/category/domain/model/CategoryEntity.kt:7
- Constructible in an invalid state: RecipeEntity app/src/main/java/de/lukasneugebauer/nextcloudcookbook/recipe/domain/model/RecipeEntity.kt:7
- Constructible in an invalid state: RecipePreviewEntity app/src/main/java/de/lukasneugebauer/nextcloudcookbook/recipe/domain/model/RecipePreviewEntity.kt:7
- Repeated repair: app/src/main/java/de/lukasneugebauer/nextcloudcookbook/recipe/presentation/detail/RecipeDetailViewModel.kt app/src/main/java/de/lukasneugebauer/nextcloudcookbook/recipe/presentation/detail/RecipeDetailViewModel.kt:56
- Repeated repair: app/src/main/java/de/lukasneugebauer/nextcloudcookbook/auth/presentation/browser/BrowserLoginViewModel.kt app/src/main/java/de/lukasneugebauer/nextcloudcookbook/auth/presentation/browser/BrowserLoginViewModel.kt:113
- FileTooLong: components/CreateEditRecipeForm.kt app/src/main/java/de/lukasneugebauer/nextcloudcookbook/recipe/presentation/components/CreateEditRecipeForm.kt
- FileTooLong: detail/RecipeDetailScreen.kt app/src/main/java/de/lukasneugebauer/nextcloudcookbook/recipe/presentation/detail/RecipeDetailScreen.kt
- Change-coupling hub: NcCookbookApi.kt → AccountRepositoryImpl.kt, Constants.kt, RecipeRepositoryImpl.kt, RecipeRepository.kt app/src/main/java/de/lukasneugebauer/nextcloudcookbook/core/data/api/NcCookbookApi.kt
- Change-coupling hub: CreateEditRecipeForm.kt → RecipeCreateEditState.kt, RecipeCreateScreen.kt, RecipeEditScreen.kt app/src/main/java/de/lukasneugebauer/nextcloudcookbook/recipe/presentation/components/CreateEditRecipeForm.kt
- REDACTED
- REDACTED
- Edited copy of a member (20 corresponding lines) app/src/main/java/de/lukasneugebauer/nextcloudcookbook/core/data/repository/AccountRepositoryImpl.kt:32
- Edited copy of a member (20 corresponding lines) app/src/main/java/de/lukasneugebauer/nextcloudcookbook/recipe/presentation/list/RecipeListScreen.kt:414
- BaseRepository.handleResponseError (cyclomatic 26) app/src/main/java/de/lukasneugebauer/nextcloudcookbook/core/domain/repository/BaseRepository.kt:22
- MainActivityKt.NextcloudCookbookApp (cyclomatic 19) app/src/main/java/de/lukasneugebauer/nextcloudcookbook/core/presentation/MainActivity.kt:137
- RecipeDetailScreenKt.RecipeDetailLayout (cyclomatic 19) app/src/main/java/de/lukasneugebauer/nextcloudcookbook/recipe/presentation/detail/RecipeDetailScreen.kt:356
- RecipeListViewModel.getRecipePreviews (cyclomatic 18) app/src/main/java/de/lukasneugebauer/nextcloudcookbook/recipe/presentation/list/RecipeListViewModel.kt:95
- Hotspot: app/src/main/java/de/lukasneugebauer/nextcloudcookbook/recipe/presentation/detail/RecipeDetailScreen.kt app/src/main/java/de/lukasneugebauer/nextcloudcookbook/recipe/presentation/detail/RecipeDetailScreen.kt:356
- RecipeDetailScreenKt.RecipeDetailLayout (cognitive 29) app/src/main/java/de/lukasneugebauer/nextcloudcookbook/recipe/presentation/detail/RecipeDetailScreen.kt:356
- YieldCalculatorImpl.recalculateIngredients (cognitive 22) app/src/main/java/de/lukasneugebauer/nextcloudcookbook/recipe/data/YieldCalculatorImpl.kt:30
- MainActivityKt.NextcloudCookbookApp (cognitive 21) app/src/main/java/de/lukasneugebauer/nextcloudcookbook/core/presentation/MainActivity.kt:137
- RecipeListViewModel.getRecipePreviews (cognitive 20) app/src/main/java/de/lukasneugebauer/nextcloudcookbook/recipe/presentation/list/RecipeListViewModel.kt:95
- RecipeFormatterImpl.format (cognitive 16) app/src/main/java/de/lukasneugebauer/nextcloudcookbook/recipe/data/RecipeFormatterImpl.kt:15
- REDACTED
- TooManyMethods: RecipeCreateEditViewModel app/src/main/java/de/lukasneugebauer/nextcloudcookbook/recipe/util/RecipeCreateEditViewModel.kt:35
- REDACTED
- REDACTED
- REDACTED
- Edited copies of one member (3 members, 63+ corresponding lines) app/src/main/java/de/lukasneugebauer/nextcloudcookbook/recipe/presentation/components/CreateEditRecipeForm.kt:661
- Edited copies of one member (3 members, 49+ corresponding lines) app/src/main/java/de/lukasneugebauer/nextcloudcookbook/settings/presentation/settings/SettingsScreen.kt:228
- Edited copy of a member (22 corresponding lines) app/src/main/java/de/lukasneugebauer/nextcloudcookbook/di/CategoryModule.kt:36
- Edited copy of a member (30 corresponding lines) app/src/main/java/de/lukasneugebauer/nextcloudcookbook/auth/presentation/browser/BrowserLoginViewModel.kt:158
- Edited copies of one member (3 members, 15+ corresponding lines) app/src/main/java/de/lukasneugebauer/nextcloudcookbook/recipe/util/RecipeCreateEditViewModel.kt:291
- Edited copy of a member (18 corresponding lines) app/src/main/java/de/lukasneugebauer/nextcloudcookbook/recipe/data/repository/RecipeRepositoryImpl.kt:205
- Edited copies of one member (3 members, 21+ corresponding lines) app/src/main/java/de/lukasneugebauer/nextcloudcookbook/recipe/presentation/components/CreateEditRecipeForm.kt:336
- Edited copies of one member (3 members, 13+ corresponding lines) app/src/main/java/de/lukasneugebauer/nextcloudcookbook/recipe/presentation/download/DownloadRecipeScreen.kt:185
- Duplicated block (163 lines × 2) app/src/main/java/de/lukasneugebauer/nextcloudcookbook/recipe/presentation/create/RecipeCreateScreen.kt:31
- Duplicated block (30 lines × 2) app/src/main/java/de/lukasneugebauer/nextcloudcookbook/settings/presentation/info/InfoScreen.kt:58
- Duplicated block (29 lines × 3) app/src/main/java/de/lukasneugebauer/nextcloudcookbook/recipe/presentation/components/CreateEditRecipeForm.kt:671
- Duplicated block (22 lines × 2) app/src/main/java/de/lukasneugebauer/nextcloudcookbook/settings/presentation/info/InfoScreen.kt:109
- Duplicated block (16 lines × 2) app/src/main/java/de/lukasneugebauer/nextcloudcookbook/recipe/presentation/components/CreateEditRecipeForm.kt:713
- Duplicated block (14 lines × 2) app/src/main/java/de/lukasneugebauer/nextcloudcookbook/auth/presentation/browser/BrowserLoginScreen.kt:154
- Duplicated block (13 lines × 2) app/src/main/java/de/lukasneugebauer/nextcloudcookbook/auth/presentation/browser/BrowserLoginViewModel.kt:163
- Duplicated block (12 lines × 2) app/src/main/java/de/lukasneugebauer/nextcloudcookbook/recipe/presentation/components/CreateEditRecipeForm.kt:1121
- Duplicated block (11 lines × 2) app/src/main/java/de/lukasneugebauer/nextcloudcookbook/recipe/presentation/create/RecipeCreateViewModel.kt:47
- Duplicated block (8 lines × 2) app/src/main/java/de/lukasneugebauer/nextcloudcookbook/recipe/presentation/components/CreateEditRecipeForm.kt:543
- Duplicated block (10 lines × 2) app/src/main/java/de/lukasneugebauer/nextcloudcookbook/core/domain/repository/BaseRepository.kt:36
Minor — 13 finding(s)
- Duplicated predicate app/src/main/java/de/lukasneugebauer/nextcloudcookbook/recipe/data/RecipeFormatterImpl.kt:44
- Duplicated predicate app/src/main/java/de/lukasneugebauer/nextcloudcookbook/recipe/presentation/create/RecipeCreateViewModel.kt:43
- Off-boarding risk: anonymized user #1
- Further sole-owners (lower concentration)
- Documentation: no build, run or usage example README.md:1
- No ADRs found app/build.gradle:2
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No SAST REDACTED:8
- No dependency-update automation package.json:2
- No changelog
Minor — 1 finding(s)
- Outdated: fastlane
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=0 --max-count=200" --report-format json --report-path /tmp/watchdog-gitleaks-11d79d1d3d8d490190c14ec66a01799b/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=200 --max-count=800" --report-format json --report-path /tmp/watchdog-gitleaks-11d79d1d3d8d490190c14ec66a01799b/history-1.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history-1.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=1000 --max-count=222" --report-format json --report-path /tmp/watchdog-gitleaks-11d79d1d3d8d490190c14ec66a01799b/history-2.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history-2.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-11d79d1d3d8d490190c14ec66a01799b/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 . | 8 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 7 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 1 file(s) — `app/src/main/java/de/lukasneugebauer/nextcloudcookbook/recipe/presentation/detail/RecipeDetailScreen.kt` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |