Executive summary
rubenquadros/Jetpack-Compose-Video-Games-Example falls short of our standard for a template or a sample because its Dependencies dimensions are rated Weak. It scores 69 out of 100, which alone would earn Strong, but it is rated Adequate: a rating can't sit more than one step above its weakest group.
Every lens scores high enough to be rated Strong, so no single lens holds the score back. The best first steps are improving the documentation and adding automated security scanning, each worth about 9 points.
Five pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Pinning each tool to an exact version would close this risk.
The product code is 4,352 lines, about €8,100 to rebuild.
Every lens already scores high enough to be rated Strong, so no single lens holds the score back.
Rebuild cost: about €8,100 · Estimate
| Cost to rebuild | €2,700 to €14,000, for 45 to 143 hours of work, under 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 | ×1.0 at a score of 69. 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: 4,352 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 domain | 2 domain.entity.base | 3 domain.entity.gamedetails | 4 domain.entity.games | 5 domain.entity.gamevideos | 6 domain.interactor.GameSearchUseCase | 7 domain.interactor.GetGameDetailsUseCase | 8 domain.interactor.GetGameVideosUseCase | 9 presentation | 10 presentation.base | 11 remote.model.request | 12 domain.entity.base.ErrorRecord | 13 domain.repository | 14 presentation.activity | 15 presentation.base.ScreenState | 16 presentation.home.ui | 17 remote.model.response.common | 18 remote.model.response.gamevideos | 19 domain.interactor | 20 presentation.home.ui.HomeSideEffect | 21 remote.model.response.allgames | 22 remote.model.response.gamedetails | 23 presentation.details | 24 presentation.home | 25 presentation.search | 26 presentation.videos | 27 remote.model.response.search | 28 presentation.details.DescriptionStatus | 29 presentation.details.GameDetailsSideEffect | 30 presentation.search.SearchSideEffect | 31 presentation.search.SearchState | 32 presentation.videos.GameVideosSideEffect | 33 remote.retrofit | 34 remote.rest | 35 remote | 36 data | 37 data.mapper | 38 remote.RemoteException | 39 data.repository | 40 injection |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 domain | ||||||||||||||||||||||||||||||||||||||||
| 2 domain.entity.base | ||||||||||||||||||||||||||||||||||||||||
| 3 domain.entity.gamedetails | ||||||||||||||||||||||||||||||||||||||||
| 4 domain.entity.games | ||||||||||||||||||||||||||||||||||||||||
| 5 domain.entity.gamevideos | ||||||||||||||||||||||||||||||||||||||||
| 6 domain.interactor.GameSearchUseCase | ||||||||||||||||||||||||||||||||||||||||
| 7 domain.interactor.GetGameDetailsUseCase | ||||||||||||||||||||||||||||||||||||||||
| 8 domain.interactor.GetGameVideosUseCase | ||||||||||||||||||||||||||||||||||||||||
| 9 presentation | ||||||||||||||||||||||||||||||||||||||||
| 10 presentation.base | ||||||||||||||||||||||||||||||||||||||||
| 11 remote.model.request | ||||||||||||||||||||||||||||||||||||||||
| 12 domain.entity.base.ErrorRecord | 4 | |||||||||||||||||||||||||||||||||||||||
| 13 domain.repository | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 14 presentation.activity | 2 | |||||||||||||||||||||||||||||||||||||||
| 15 presentation.base.ScreenState | 3 | |||||||||||||||||||||||||||||||||||||||
| 16 presentation.home.ui | 1 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 17 remote.model.response.common | 9 | |||||||||||||||||||||||||||||||||||||||
| 18 remote.model.response.gamevideos | 2 | |||||||||||||||||||||||||||||||||||||||
| 19 domain.interactor | 3 | 3 | 1 | 2 | 1 | 1 | 1 | 1 | 4 | |||||||||||||||||||||||||||||||
| 20 presentation.home.ui.HomeSideEffect | 1 | |||||||||||||||||||||||||||||||||||||||
| 21 remote.model.response.allgames | 1 | 8 | ||||||||||||||||||||||||||||||||||||||
| 22 remote.model.response.gamedetails | 3 | 9 | ||||||||||||||||||||||||||||||||||||||
| 23 presentation.details | 1 | 2 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 24 presentation.home | 1 | 1 | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||
| 25 presentation.search | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 26 presentation.videos | 1 | 5 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 27 remote.model.response.search | 1 | |||||||||||||||||||||||||||||||||||||||
| 28 presentation.details.DescriptionStatus | 3 | |||||||||||||||||||||||||||||||||||||||
| 29 presentation.details.GameDetailsSideEffect | 2 | |||||||||||||||||||||||||||||||||||||||
| 30 presentation.search.SearchSideEffect | 1 | |||||||||||||||||||||||||||||||||||||||
| 31 presentation.search.SearchState | 1 | 5 | ||||||||||||||||||||||||||||||||||||||
| 32 presentation.videos.GameVideosSideEffect | 3 | |||||||||||||||||||||||||||||||||||||||
| 33 remote.retrofit | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 34 remote.rest | 8 | 2 | 2 | 2 | 2 | 1 | ||||||||||||||||||||||||||||||||||
| 35 remote | 2 | |||||||||||||||||||||||||||||||||||||||
| 36 data | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 37 data.mapper | 2 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||
| 38 remote.RemoteException | 4 | |||||||||||||||||||||||||||||||||||||||
| 39 data.repository | 1 | 1 | 1 | 1 | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||
| 40 injection | 1 | 3 | 1 | 1 | 1 |
12→2 domain.entity.base.ErrorRecord uses domain.entity.base✕
- Connections
- 4 pairs of types, where a type in domain.entity.base.ErrorRecord uses a type in domain.entity.base.
- The types involved
com.ruben.epicworld.domain.entity.base.ErrorRecord.ClientError→com.ruben.epicworld.domain.entity.base.ErrorRecordcom.ruben.epicworld.domain.entity.base.ErrorRecord.GenericError→com.ruben.epicworld.domain.entity.base.ErrorRecordcom.ruben.epicworld.domain.entity.base.ErrorRecord.NetworkError→com.ruben.epicworld.domain.entity.base.ErrorRecordcom.ruben.epicworld.domain.entity.base.ErrorRecord.ServerError→com.ruben.epicworld.domain.entity.base.ErrorRecord
- Direction
- domain.entity.base.ErrorRecord uses domain.entity.base, so a change to domain.entity.base can break domain.entity.base.ErrorRecord, while a change to domain.entity.base.ErrorRecord can't break domain.entity.base.
- Position
- Below the diagonal: domain.entity.base.ErrorRecord uses a module listed above it, which is the healthy direction.
13→2 domain.repository uses domain.entity.base✕
- Connections
- 1 pair of types, where a type in domain.repository uses a type in domain.entity.base.
- The types involved
com.ruben.epicworld.domain.repository.GamesRepository→com.ruben.epicworld.domain.entity.base.Record
- Direction
- domain.repository uses domain.entity.base, so a change to domain.entity.base can break domain.repository, while a change to domain.repository can't break domain.entity.base.
- Position
- Below the diagonal: domain.repository uses a module listed above it, which is the healthy direction.
13→3 domain.repository uses domain.entity.gamedetails✕
- Connections
- 1 pair of types, where a type in domain.repository uses a type in domain.entity.gamedetails.
- The types involved
com.ruben.epicworld.domain.repository.GamesRepository→com.ruben.epicworld.domain.entity.gamedetails.GameDetailsEntity
- Direction
- domain.repository uses domain.entity.gamedetails, so a change to domain.entity.gamedetails can break domain.repository, while a change to domain.repository can't break domain.entity.gamedetails.
- Position
- Below the diagonal: domain.repository uses a module listed above it, which is the healthy direction.
13→4 domain.repository uses domain.entity.games✕
- Connections
- 1 pair of types, where a type in domain.repository uses a type in domain.entity.games.
- The types involved
com.ruben.epicworld.domain.repository.GamesRepository→com.ruben.epicworld.domain.entity.games.GamesEntity
- Direction
- domain.repository uses domain.entity.games, so a change to domain.entity.games can break domain.repository, while a change to domain.repository can't break domain.entity.games.
- Position
- Below the diagonal: domain.repository uses a module listed above it, which is the healthy direction.
13→5 domain.repository uses domain.entity.gamevideos✕
- Connections
- 1 pair of types, where a type in domain.repository uses a type in domain.entity.gamevideos.
- The types involved
com.ruben.epicworld.domain.repository.GamesRepository→com.ruben.epicworld.domain.entity.gamevideos.GameVideosEntity
- Direction
- domain.repository uses domain.entity.gamevideos, so a change to domain.entity.gamevideos can break domain.repository, while a change to domain.repository can't break domain.entity.gamevideos.
- Position
- Below the diagonal: domain.repository uses a module listed above it, which is the healthy direction.
14→10 presentation.activity uses presentation.base✕
- Connections
- 2 pairs of types, where a type in presentation.activity uses a type in presentation.base.
- The types involved
com.ruben.epicworld.presentation.activity.MainActivity→com.ruben.epicworld.presentation.base.BaseActivitycom.ruben.epicworld.presentation.activity.MainActivityViewModel→com.ruben.epicworld.presentation.base.BaseViewModel
- Direction
- presentation.activity uses presentation.base, so a change to presentation.base can break presentation.activity, while a change to presentation.activity can't break presentation.base.
- Position
- Below the diagonal: presentation.activity uses a module listed above it, which is the healthy direction.
15→10 presentation.base.ScreenState uses presentation.base✕
- Connections
- 3 pairs of types, where a type in presentation.base.ScreenState uses a type in presentation.base.
- The types involved
com.ruben.epicworld.presentation.base.ScreenState.Error→com.ruben.epicworld.presentation.base.ScreenStatecom.ruben.epicworld.presentation.base.ScreenState.Loading→com.ruben.epicworld.presentation.base.ScreenStatecom.ruben.epicworld.presentation.base.ScreenState.Success→com.ruben.epicworld.presentation.base.ScreenState
- Direction
- presentation.base.ScreenState uses presentation.base, so a change to presentation.base can break presentation.base.ScreenState, while a change to presentation.base.ScreenState can't break presentation.base.
- Position
- Below the diagonal: presentation.base.ScreenState uses a module listed above it, which is the healthy direction.
16→2 presentation.home.ui uses domain.entity.base✕
- Connections
- 1 pair of types, where a type in presentation.home.ui uses a type in domain.entity.base.
- The types involved
com.ruben.epicworld.presentation.home.ui.HomeState→com.ruben.epicworld.domain.entity.base.ErrorRecord
- Direction
- presentation.home.ui uses domain.entity.base, so a change to domain.entity.base can break presentation.home.ui, while a change to presentation.home.ui can't break domain.entity.base.
- Position
- Below the diagonal: presentation.home.ui uses a module listed above it, which is the healthy direction.
16→4 presentation.home.ui uses domain.entity.games✕
- Connections
- 2 pairs of types, where a type in presentation.home.ui uses a type in domain.entity.games.
- The types involved
com.ruben.epicworld.presentation.home.ui.HomeScreenKt→com.ruben.epicworld.domain.entity.games.GameResultEntitycom.ruben.epicworld.presentation.home.ui.HomeState→com.ruben.epicworld.domain.entity.games.GameResultEntity
- Direction
- presentation.home.ui uses domain.entity.games, so a change to domain.entity.games can break presentation.home.ui, while a change to presentation.home.ui can't break domain.entity.games.
- Position
- Below the diagonal: presentation.home.ui uses a module listed above it, which is the healthy direction.
16→10 presentation.home.ui uses presentation.base✕
- Connections
- 1 pair of types, where a type in presentation.home.ui uses a type in presentation.base.
- The types involved
com.ruben.epicworld.presentation.home.ui.HomeState→com.ruben.epicworld.presentation.base.ScreenState
- Direction
- presentation.home.ui uses presentation.base, so a change to presentation.base can break presentation.home.ui, while a change to presentation.home.ui can't break presentation.base.
- Position
- Below the diagonal: presentation.home.ui uses a module listed above it, which is the healthy direction.
16→24 presentation.home.ui uses presentation.home part of a loop✕
- Connections
- 1 pair of types, where a type in presentation.home.ui uses a type in presentation.home.
- The types involved
com.ruben.epicworld.presentation.home.ui.HomeScreenKt→com.ruben.epicworld.presentation.home.HomeViewModel
- Direction
- presentation.home.ui uses presentation.home, so a change to presentation.home can break presentation.home.ui, while a change to presentation.home.ui can't break presentation.home.
- 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.
17→3 remote.model.response.common uses domain.entity.gamedetails✕
- Connections
- 9 pairs of types, where a type in remote.model.response.common uses a type in domain.entity.gamedetails.
- The types involved
com.ruben.epicworld.remote.model.response.common.GenresKt→com.ruben.epicworld.domain.entity.gamedetails.GenresEntitycom.ruben.epicworld.remote.model.response.common.ParentPlatformsKt→com.ruben.epicworld.domain.entity.gamedetails.ParentPlatformsEntitycom.ruben.epicworld.remote.model.response.common.PlatformKt→com.ruben.epicworld.domain.entity.gamedetails.PlatformEntitycom.ruben.epicworld.remote.model.response.common.PlatformsKt→com.ruben.epicworld.domain.entity.gamedetails.PlatformsEntitycom.ruben.epicworld.remote.model.response.common.RatingsKt→com.ruben.epicworld.domain.entity.gamedetails.RatingsEntitycom.ruben.epicworld.remote.model.response.common.RequirementsKt→com.ruben.epicworld.domain.entity.gamedetails.RequirementsEntitycom.ruben.epicworld.remote.model.response.common.StoreKt→com.ruben.epicworld.domain.entity.gamedetails.StoreEntitycom.ruben.epicworld.remote.model.response.common.StoresKt→com.ruben.epicworld.domain.entity.gamedetails.StoresEntitycom.ruben.epicworld.remote.model.response.common.TagsKt→com.ruben.epicworld.domain.entity.gamedetails.TagsEntity
- Direction
- remote.model.response.common uses domain.entity.gamedetails, so a change to domain.entity.gamedetails can break remote.model.response.common, while a change to remote.model.response.common can't break domain.entity.gamedetails.
- Position
- Below the diagonal: remote.model.response.common uses a module listed above it, which is the healthy direction.
18→5 remote.model.response.gamevideos uses domain.entity.gamevideos✕
- Connections
- 2 pairs of types, where a type in remote.model.response.gamevideos uses a type in domain.entity.gamevideos.
- The types involved
com.ruben.epicworld.remote.model.response.gamevideos.GetGameVideosResponseKt→com.ruben.epicworld.domain.entity.gamevideos.GameVideosEntitycom.ruben.epicworld.remote.model.response.gamevideos.VideoResultKt→com.ruben.epicworld.domain.entity.gamevideos.VideoResultEntity
- Direction
- remote.model.response.gamevideos uses domain.entity.gamevideos, so a change to domain.entity.gamevideos can break remote.model.response.gamevideos, while a change to remote.model.response.gamevideos can't break domain.entity.gamevideos.
- Position
- Below the diagonal: remote.model.response.gamevideos uses a module listed above it, which is the healthy direction.
19→1 domain.interactor uses domain✕
- Connections
- 3 pairs of types, where a type in domain.interactor uses a type in domain.
- The types involved
com.ruben.epicworld.domain.interactor.GameSearchUseCase→com.ruben.epicworld.domain.BaseUseCasecom.ruben.epicworld.domain.interactor.GetGameDetailsUseCase→com.ruben.epicworld.domain.BaseUseCasecom.ruben.epicworld.domain.interactor.GetGameVideosUseCase→com.ruben.epicworld.domain.BaseUseCase
- Direction
- domain.interactor uses domain, so a change to domain can break domain.interactor, while a change to domain.interactor can't break domain.
- Position
- Below the diagonal: domain.interactor uses a module listed above it, which is the healthy direction.
19→2 domain.interactor uses domain.entity.base✕
- Connections
- 3 pairs of types, where a type in domain.interactor uses a type in domain.entity.base.
- The types involved
com.ruben.epicworld.domain.interactor.GameSearchUseCase→com.ruben.epicworld.domain.entity.base.Recordcom.ruben.epicworld.domain.interactor.GetGameDetailsUseCase→com.ruben.epicworld.domain.entity.base.Recordcom.ruben.epicworld.domain.interactor.GetGameVideosUseCase→com.ruben.epicworld.domain.entity.base.Record
- Direction
- domain.interactor uses domain.entity.base, so a change to domain.entity.base can break domain.interactor, while a change to domain.interactor can't break domain.entity.base.
- Position
- Below the diagonal: domain.interactor uses a module listed above it, which is the healthy direction.
19→3 domain.interactor uses domain.entity.gamedetails✕
- Connections
- 1 pair of types, where a type in domain.interactor uses a type in domain.entity.gamedetails.
- The types involved
com.ruben.epicworld.domain.interactor.GetGameDetailsUseCase→com.ruben.epicworld.domain.entity.gamedetails.GameDetailsEntity
- Direction
- domain.interactor uses domain.entity.gamedetails, so a change to domain.entity.gamedetails can break domain.interactor, while a change to domain.interactor can't break domain.entity.gamedetails.
- Position
- Below the diagonal: domain.interactor uses a module listed above it, which is the healthy direction.
19→4 domain.interactor uses domain.entity.games✕
- Connections
- 2 pairs of types, where a type in domain.interactor uses a type in domain.entity.games.
- The types involved
com.ruben.epicworld.domain.interactor.GameSearchUseCase→com.ruben.epicworld.domain.entity.games.GamesEntitycom.ruben.epicworld.domain.interactor.GamesSource→com.ruben.epicworld.domain.entity.games.GameResultEntity
- Direction
- domain.interactor uses domain.entity.games, so a change to domain.entity.games can break domain.interactor, while a change to domain.interactor can't break domain.entity.games.
- Position
- Below the diagonal: domain.interactor uses a module listed above it, which is the healthy direction.
19→5 domain.interactor uses domain.entity.gamevideos✕
- Connections
- 1 pair of types, where a type in domain.interactor uses a type in domain.entity.gamevideos.
- The types involved
com.ruben.epicworld.domain.interactor.GetGameVideosUseCase→com.ruben.epicworld.domain.entity.gamevideos.GameVideosEntity
- Direction
- domain.interactor uses domain.entity.gamevideos, so a change to domain.entity.gamevideos can break domain.interactor, while a change to domain.interactor can't break domain.entity.gamevideos.
- Position
- Below the diagonal: domain.interactor uses a module listed above it, which is the healthy direction.
19→6 domain.interactor uses domain.interactor.GameSearchUseCase✕
- Connections
- 1 pair of types, where a type in domain.interactor uses a type in domain.interactor.GameSearchUseCase.
- The types involved
com.ruben.epicworld.domain.interactor.GameSearchUseCase→com.ruben.epicworld.domain.interactor.GameSearchUseCase.RequestValue
- Direction
- domain.interactor uses domain.interactor.GameSearchUseCase, so a change to domain.interactor.GameSearchUseCase can break domain.interactor, while a change to domain.interactor can't break domain.interactor.GameSearchUseCase.
- Position
- Below the diagonal: domain.interactor uses a module listed above it, which is the healthy direction.
19→7 domain.interactor uses domain.interactor.GetGameDetailsUseCase✕
- Connections
- 1 pair of types, where a type in domain.interactor uses a type in domain.interactor.GetGameDetailsUseCase.
- The types involved
com.ruben.epicworld.domain.interactor.GetGameDetailsUseCase→com.ruben.epicworld.domain.interactor.GetGameDetailsUseCase.RequestValue
- Direction
- domain.interactor uses domain.interactor.GetGameDetailsUseCase, so a change to domain.interactor.GetGameDetailsUseCase can break domain.interactor, while a change to domain.interactor can't break domain.interactor.GetGameDetailsUseCase.
- Position
- Below the diagonal: domain.interactor uses a module listed above it, which is the healthy direction.
19→8 domain.interactor uses domain.interactor.GetGameVideosUseCase✕
- Connections
- 1 pair of types, where a type in domain.interactor uses a type in domain.interactor.GetGameVideosUseCase.
- The types involved
com.ruben.epicworld.domain.interactor.GetGameVideosUseCase→com.ruben.epicworld.domain.interactor.GetGameVideosUseCase.RequestValue
- Direction
- domain.interactor uses domain.interactor.GetGameVideosUseCase, so a change to domain.interactor.GetGameVideosUseCase can break domain.interactor, while a change to domain.interactor can't break domain.interactor.GetGameVideosUseCase.
- Position
- Below the diagonal: domain.interactor uses a module listed above it, which is the healthy direction.
19→13 domain.interactor uses domain.repository✕
- Connections
- 4 pairs of types, where a type in domain.interactor uses a type in domain.repository.
- The types involved
com.ruben.epicworld.domain.interactor.GameSearchUseCase→com.ruben.epicworld.domain.repository.GamesRepositorycom.ruben.epicworld.domain.interactor.GamesSource→com.ruben.epicworld.domain.repository.GamesRepositorycom.ruben.epicworld.domain.interactor.GetGameDetailsUseCase→com.ruben.epicworld.domain.repository.GamesRepositorycom.ruben.epicworld.domain.interactor.GetGameVideosUseCase→com.ruben.epicworld.domain.repository.GamesRepository
- Direction
- domain.interactor uses domain.repository, so a change to domain.repository can break domain.interactor, while a change to domain.interactor can't break domain.repository.
- Position
- Below the diagonal: domain.interactor uses a module listed above it, which is the healthy direction.
20→16 presentation.home.ui.HomeSideEffect uses presentation.home.ui✕
- Connections
- 1 pair of types, where a type in presentation.home.ui.HomeSideEffect uses a type in presentation.home.ui.
- The types involved
com.ruben.epicworld.presentation.home.ui.HomeSideEffect.ShowSnackBar→com.ruben.epicworld.presentation.home.ui.HomeSideEffect
- Direction
- presentation.home.ui.HomeSideEffect uses presentation.home.ui, so a change to presentation.home.ui can break presentation.home.ui.HomeSideEffect, while a change to presentation.home.ui.HomeSideEffect can't break presentation.home.ui.
- Position
- Below the diagonal: presentation.home.ui.HomeSideEffect uses a module listed above it, which is the healthy direction.
21→4 remote.model.response.allgames uses domain.entity.games✕
- Connections
- 1 pair of types, where a type in remote.model.response.allgames uses a type in domain.entity.games.
- The types involved
com.ruben.epicworld.remote.model.response.allgames.ResultsKt→com.ruben.epicworld.domain.entity.games.GameResultEntity
- Direction
- remote.model.response.allgames uses domain.entity.games, so a change to domain.entity.games can break remote.model.response.allgames, while a change to remote.model.response.allgames can't break domain.entity.games.
- Position
- Below the diagonal: remote.model.response.allgames uses a module listed above it, which is the healthy direction.
21→17 remote.model.response.allgames uses remote.model.response.common✕
- Connections
- 8 pairs of types, where a type in remote.model.response.allgames uses a type in remote.model.response.common.
- The types involved
com.ruben.epicworld.remote.model.response.allgames.Results→com.ruben.epicworld.remote.model.response.common.AddedByStatuscom.ruben.epicworld.remote.model.response.allgames.Results→com.ruben.epicworld.remote.model.response.common.EsrbRatingcom.ruben.epicworld.remote.model.response.allgames.Results→com.ruben.epicworld.remote.model.response.common.Genrescom.ruben.epicworld.remote.model.response.allgames.Results→com.ruben.epicworld.remote.model.response.common.ParentPlatformscom.ruben.epicworld.remote.model.response.allgames.Results→com.ruben.epicworld.remote.model.response.common.Platformscom.ruben.epicworld.remote.model.response.allgames.Results→com.ruben.epicworld.remote.model.response.common.Ratingscom.ruben.epicworld.remote.model.response.allgames.Results→com.ruben.epicworld.remote.model.response.common.Storescom.ruben.epicworld.remote.model.response.allgames.Results→com.ruben.epicworld.remote.model.response.common.Tags
- Direction
- remote.model.response.allgames uses remote.model.response.common, so a change to remote.model.response.common can break remote.model.response.allgames, while a change to remote.model.response.allgames can't break remote.model.response.common.
- Position
- Below the diagonal: remote.model.response.allgames uses a module listed above it, which is the healthy direction.
22→3 remote.model.response.gamedetails uses domain.entity.gamedetails✕
- Connections
- 3 pairs of types, where a type in remote.model.response.gamedetails uses a type in domain.entity.gamedetails.
- The types involved
com.ruben.epicworld.remote.model.response.gamedetails.DevelopersKt→com.ruben.epicworld.domain.entity.gamedetails.DevelopersEntitycom.ruben.epicworld.remote.model.response.gamedetails.GetGameDetailsResponseKt→com.ruben.epicworld.domain.entity.gamedetails.GameDetailsEntitycom.ruben.epicworld.remote.model.response.gamedetails.PublishersKt→com.ruben.epicworld.domain.entity.gamedetails.PublishersEntity
- Direction
- remote.model.response.gamedetails uses domain.entity.gamedetails, so a change to domain.entity.gamedetails can break remote.model.response.gamedetails, while a change to remote.model.response.gamedetails can't break domain.entity.gamedetails.
- Position
- Below the diagonal: remote.model.response.gamedetails uses a module listed above it, which is the healthy direction.
22→17 remote.model.response.gamedetails uses remote.model.response.common✕
- Connections
- 9 pairs of types, where a type in remote.model.response.gamedetails uses a type in remote.model.response.common.
- The types involved
com.ruben.epicworld.remote.model.response.gamedetails.GetGameDetailsResponse→com.ruben.epicworld.remote.model.response.common.AddedByStatuscom.ruben.epicworld.remote.model.response.gamedetails.GetGameDetailsResponse→com.ruben.epicworld.remote.model.response.common.EsrbRatingcom.ruben.epicworld.remote.model.response.gamedetails.GetGameDetailsResponse→com.ruben.epicworld.remote.model.response.common.Genrescom.ruben.epicworld.remote.model.response.gamedetails.GetGameDetailsResponse→com.ruben.epicworld.remote.model.response.common.ParentPlatformscom.ruben.epicworld.remote.model.response.gamedetails.GetGameDetailsResponse→com.ruben.epicworld.remote.model.response.common.Platformscom.ruben.epicworld.remote.model.response.gamedetails.GetGameDetailsResponse→com.ruben.epicworld.remote.model.response.common.Ratingscom.ruben.epicworld.remote.model.response.gamedetails.GetGameDetailsResponse→com.ruben.epicworld.remote.model.response.common.Storescom.ruben.epicworld.remote.model.response.gamedetails.GetGameDetailsResponse→com.ruben.epicworld.remote.model.response.common.Tagscom.ruben.epicworld.remote.model.response.gamedetails.MetaCriticPlatforms→com.ruben.epicworld.remote.model.response.common.Platform
- Direction
- remote.model.response.gamedetails uses remote.model.response.common, so a change to remote.model.response.common can break remote.model.response.gamedetails, while a change to remote.model.response.gamedetails can't break remote.model.response.common.
- Position
- Below the diagonal: remote.model.response.gamedetails uses a module listed above it, which is the healthy direction.
23→2 presentation.details uses domain.entity.base✕
- Connections
- 1 pair of types, where a type in presentation.details uses a type in domain.entity.base.
- The types involved
com.ruben.epicworld.presentation.details.GameDetailsState→com.ruben.epicworld.domain.entity.base.ErrorRecord
- Direction
- presentation.details uses domain.entity.base, so a change to domain.entity.base can break presentation.details, while a change to presentation.details can't break domain.entity.base.
- Position
- Below the diagonal: presentation.details uses a module listed above it, which is the healthy direction.
23→3 presentation.details uses domain.entity.gamedetails✕
- Connections
- 2 pairs of types, where a type in presentation.details uses a type in domain.entity.gamedetails.
- The types involved
com.ruben.epicworld.presentation.details.GameDetailsScreenKt→com.ruben.epicworld.domain.entity.gamedetails.GameDetailsEntitycom.ruben.epicworld.presentation.details.GameDetailsState→com.ruben.epicworld.domain.entity.gamedetails.GameDetailsEntity
- Direction
- presentation.details uses domain.entity.gamedetails, so a change to domain.entity.gamedetails can break presentation.details, while a change to presentation.details can't break domain.entity.gamedetails.
- Position
- Below the diagonal: presentation.details uses a module listed above it, which is the healthy direction.
23→10 presentation.details uses presentation.base✕
- Connections
- 2 pairs of types, where a type in presentation.details uses a type in presentation.base.
- The types involved
com.ruben.epicworld.presentation.details.GameDetailsState→com.ruben.epicworld.presentation.base.ScreenStatecom.ruben.epicworld.presentation.details.GameDetailsViewModel→com.ruben.epicworld.presentation.base.BaseViewModel
- Direction
- presentation.details uses presentation.base, so a change to presentation.base can break presentation.details, while a change to presentation.details can't break presentation.base.
- Position
- Below the diagonal: presentation.details uses a module listed above it, which is the healthy direction.
23→19 presentation.details uses domain.interactor✕
- Connections
- 1 pair of types, where a type in presentation.details uses a type in domain.interactor.
- The types involved
com.ruben.epicworld.presentation.details.GameDetailsViewModel→com.ruben.epicworld.domain.interactor.GetGameDetailsUseCase
- Direction
- presentation.details uses domain.interactor, so a change to domain.interactor can break presentation.details, while a change to presentation.details can't break domain.interactor.
- Position
- Below the diagonal: presentation.details uses a module listed above it, which is the healthy direction.
24→4 presentation.home uses domain.entity.games✕
- Connections
- 1 pair of types, where a type in presentation.home uses a type in domain.entity.games.
- The types involved
com.ruben.epicworld.presentation.home.HomeViewModel→com.ruben.epicworld.domain.entity.games.GameResultEntity
- Direction
- presentation.home uses domain.entity.games, so a change to domain.entity.games can break presentation.home, while a change to presentation.home can't break domain.entity.games.
- Position
- Below the diagonal: presentation.home uses a module listed above it, which is the healthy direction.
24→10 presentation.home uses presentation.base✕
- Connections
- 1 pair of types, where a type in presentation.home uses a type in presentation.base.
- The types involved
com.ruben.epicworld.presentation.home.HomeViewModel→com.ruben.epicworld.presentation.base.BaseViewModel
- Direction
- presentation.home uses presentation.base, so a change to presentation.base can break presentation.home, while a change to presentation.home can't break presentation.base.
- Position
- Below the diagonal: presentation.home uses a module listed above it, which is the healthy direction.
24→13 presentation.home uses domain.repository✕
- Connections
- 1 pair of types, where a type in presentation.home uses a type in domain.repository.
- The types involved
com.ruben.epicworld.presentation.home.HomeModule→com.ruben.epicworld.domain.repository.GamesRepository
- Direction
- presentation.home uses domain.repository, so a change to domain.repository can break presentation.home, while a change to presentation.home can't break domain.repository.
- Position
- Below the diagonal: presentation.home uses a module listed above it, which is the healthy direction.
24→16 presentation.home uses presentation.home.ui✕
- Connections
- 1 pair of types, where a type in presentation.home uses a type in presentation.home.ui.
- The types involved
com.ruben.epicworld.presentation.home.HomeViewModel→com.ruben.epicworld.presentation.home.ui.HomeState
- Direction
- presentation.home uses presentation.home.ui, so a change to presentation.home.ui can break presentation.home, while a change to presentation.home can't break presentation.home.ui.
- Position
- Below the diagonal: presentation.home uses a module listed above it, which is the healthy direction.
24→19 presentation.home uses domain.interactor✕
- Connections
- 2 pairs of types, where a type in presentation.home uses a type in domain.interactor.
- The types involved
com.ruben.epicworld.presentation.home.HomeModule→com.ruben.epicworld.domain.interactor.GamesSourcecom.ruben.epicworld.presentation.home.HomeViewModel→com.ruben.epicworld.domain.interactor.GamesSource
- Direction
- presentation.home uses domain.interactor, so a change to domain.interactor can break presentation.home, while a change to presentation.home can't break domain.interactor.
- Position
- Below the diagonal: presentation.home uses a module listed above it, which is the healthy direction.
25→4 presentation.search uses domain.entity.games✕
- Connections
- 2 pairs of types, where a type in presentation.search uses a type in domain.entity.games.
- The types involved
com.ruben.epicworld.presentation.search.GameSearchScreenKt→com.ruben.epicworld.domain.entity.games.GameResultEntitycom.ruben.epicworld.presentation.search.GameSearchScreenKt→com.ruben.epicworld.domain.entity.games.GameResultsEntity
- Direction
- presentation.search uses domain.entity.games, so a change to domain.entity.games can break presentation.search, while a change to presentation.search can't break domain.entity.games.
- Position
- Below the diagonal: presentation.search uses a module listed above it, which is the healthy direction.
25→10 presentation.search uses presentation.base✕
- Connections
- 1 pair of types, where a type in presentation.search uses a type in presentation.base.
- The types involved
com.ruben.epicworld.presentation.search.GameSearchViewModel→com.ruben.epicworld.presentation.base.BaseViewModel
- Direction
- presentation.search uses presentation.base, so a change to presentation.base can break presentation.search, while a change to presentation.search can't break presentation.base.
- Position
- Below the diagonal: presentation.search uses a module listed above it, which is the healthy direction.
25→19 presentation.search uses domain.interactor✕
- Connections
- 1 pair of types, where a type in presentation.search uses a type in domain.interactor.
- The types involved
com.ruben.epicworld.presentation.search.GameSearchViewModel→com.ruben.epicworld.domain.interactor.GameSearchUseCase
- Direction
- presentation.search uses domain.interactor, so a change to domain.interactor can break presentation.search, while a change to presentation.search can't break domain.interactor.
- Position
- Below the diagonal: presentation.search uses a module listed above it, which is the healthy direction.
26→2 presentation.videos uses domain.entity.base✕
- Connections
- 1 pair of types, where a type in presentation.videos uses a type in domain.entity.base.
- The types involved
com.ruben.epicworld.presentation.videos.GameVideosState→com.ruben.epicworld.domain.entity.base.ErrorRecord
- Direction
- presentation.videos uses domain.entity.base, so a change to domain.entity.base can break presentation.videos, while a change to presentation.videos can't break domain.entity.base.
- Position
- Below the diagonal: presentation.videos uses a module listed above it, which is the healthy direction.
26→5 presentation.videos uses domain.entity.gamevideos✕
- Connections
- 5 pairs of types, where a type in presentation.videos uses a type in domain.entity.gamevideos.
- The types involved
com.ruben.epicworld.presentation.videos.GameVideosScreenKt→com.ruben.epicworld.domain.entity.gamevideos.GameVideosEntitycom.ruben.epicworld.presentation.videos.GameVideosScreenKt→com.ruben.epicworld.domain.entity.gamevideos.PlayerWrappercom.ruben.epicworld.presentation.videos.GameVideosScreenKt→com.ruben.epicworld.domain.entity.gamevideos.VideoResultEntitycom.ruben.epicworld.presentation.videos.GameVideosState→com.ruben.epicworld.domain.entity.gamevideos.GameVideosEntitycom.ruben.epicworld.presentation.videos.PlayerViewKt→com.ruben.epicworld.domain.entity.gamevideos.PlayerWrapper
- Direction
- presentation.videos uses domain.entity.gamevideos, so a change to domain.entity.gamevideos can break presentation.videos, while a change to presentation.videos can't break domain.entity.gamevideos.
- Position
- Below the diagonal: presentation.videos uses a module listed above it, which is the healthy direction.
26→10 presentation.videos uses presentation.base✕
- Connections
- 2 pairs of types, where a type in presentation.videos uses a type in presentation.base.
- The types involved
com.ruben.epicworld.presentation.videos.GameVideosState→com.ruben.epicworld.presentation.base.ScreenStatecom.ruben.epicworld.presentation.videos.GameVideosViewModel→com.ruben.epicworld.presentation.base.BaseViewModel
- Direction
- presentation.videos uses presentation.base, so a change to presentation.base can break presentation.videos, while a change to presentation.videos can't break presentation.base.
- Position
- Below the diagonal: presentation.videos uses a module listed above it, which is the healthy direction.
26→19 presentation.videos uses domain.interactor✕
- Connections
- 1 pair of types, where a type in presentation.videos uses a type in domain.interactor.
- The types involved
com.ruben.epicworld.presentation.videos.GameVideosViewModel→com.ruben.epicworld.domain.interactor.GetGameVideosUseCase
- Direction
- presentation.videos uses domain.interactor, so a change to domain.interactor can break presentation.videos, while a change to presentation.videos can't break domain.interactor.
- Position
- Below the diagonal: presentation.videos uses a module listed above it, which is the healthy direction.
27→21 remote.model.response.search uses remote.model.response.allgames✕
- Connections
- 1 pair of types, where a type in remote.model.response.search uses a type in remote.model.response.allgames.
- The types involved
com.ruben.epicworld.remote.model.response.search.SearchGamesResponse→com.ruben.epicworld.remote.model.response.allgames.Results
- Direction
- remote.model.response.search uses remote.model.response.allgames, so a change to remote.model.response.allgames can break remote.model.response.search, while a change to remote.model.response.search can't break remote.model.response.allgames.
- Position
- Below the diagonal: remote.model.response.search uses a module listed above it, which is the healthy direction.
28→23 presentation.details.DescriptionStatus uses presentation.details✕
- Connections
- 3 pairs of types, where a type in presentation.details.DescriptionStatus uses a type in presentation.details.
- The types involved
com.ruben.epicworld.presentation.details.DescriptionStatus.DEFAULT→com.ruben.epicworld.presentation.details.DescriptionStatuscom.ruben.epicworld.presentation.details.DescriptionStatus.SHOW_LESS→com.ruben.epicworld.presentation.details.DescriptionStatuscom.ruben.epicworld.presentation.details.DescriptionStatus.SHOW_MORE→com.ruben.epicworld.presentation.details.DescriptionStatus
- Direction
- presentation.details.DescriptionStatus uses presentation.details, so a change to presentation.details can break presentation.details.DescriptionStatus, while a change to presentation.details.DescriptionStatus can't break presentation.details.
- Position
- Below the diagonal: presentation.details.DescriptionStatus uses a module listed above it, which is the healthy direction.
29→23 presentation.details.GameDetailsSideEffect uses presentation.details✕
- Connections
- 2 pairs of types, where a type in presentation.details.GameDetailsSideEffect uses a type in presentation.details.
- The types involved
com.ruben.epicworld.presentation.details.GameDetailsSideEffect.ShowGameDetailsErrorToast→com.ruben.epicworld.presentation.details.GameDetailsSideEffectcom.ruben.epicworld.presentation.details.GameDetailsSideEffect.ShowGameIdErrorToast→com.ruben.epicworld.presentation.details.GameDetailsSideEffect
- Direction
- presentation.details.GameDetailsSideEffect uses presentation.details, so a change to presentation.details can break presentation.details.GameDetailsSideEffect, while a change to presentation.details.GameDetailsSideEffect can't break presentation.details.
- Position
- Below the diagonal: presentation.details.GameDetailsSideEffect uses a module listed above it, which is the healthy direction.
30→25 presentation.search.SearchSideEffect uses presentation.search✕
- Connections
- 1 pair of types, where a type in presentation.search.SearchSideEffect uses a type in presentation.search.
- The types involved
com.ruben.epicworld.presentation.search.SearchSideEffect.NavigateToDetails→com.ruben.epicworld.presentation.search.SearchSideEffect
- Direction
- presentation.search.SearchSideEffect uses presentation.search, so a change to presentation.search can break presentation.search.SearchSideEffect, while a change to presentation.search.SearchSideEffect can't break presentation.search.
- Position
- Below the diagonal: presentation.search.SearchSideEffect uses a module listed above it, which is the healthy direction.
31→4 presentation.search.SearchState uses domain.entity.games✕
- Connections
- 1 pair of types, where a type in presentation.search.SearchState uses a type in domain.entity.games.
- The types involved
com.ruben.epicworld.presentation.search.SearchState.SearchResultState→com.ruben.epicworld.domain.entity.games.GameResultsEntity
- Direction
- presentation.search.SearchState uses domain.entity.games, so a change to domain.entity.games can break presentation.search.SearchState, while a change to presentation.search.SearchState can't break domain.entity.games.
- Position
- Below the diagonal: presentation.search.SearchState uses a module listed above it, which is the healthy direction.
31→25 presentation.search.SearchState uses presentation.search✕
- Connections
- 5 pairs of types, where a type in presentation.search.SearchState uses a type in presentation.search.
- The types involved
com.ruben.epicworld.presentation.search.SearchState.ErrorState→com.ruben.epicworld.presentation.search.SearchStatecom.ruben.epicworld.presentation.search.SearchState.InitialState→com.ruben.epicworld.presentation.search.SearchStatecom.ruben.epicworld.presentation.search.SearchState.LoadingState→com.ruben.epicworld.presentation.search.SearchStatecom.ruben.epicworld.presentation.search.SearchState.NoResultsState→com.ruben.epicworld.presentation.search.SearchStatecom.ruben.epicworld.presentation.search.SearchState.SearchResultState→com.ruben.epicworld.presentation.search.SearchState
- Direction
- presentation.search.SearchState uses presentation.search, so a change to presentation.search can break presentation.search.SearchState, while a change to presentation.search.SearchState can't break presentation.search.
- Position
- Below the diagonal: presentation.search.SearchState uses a module listed above it, which is the healthy direction.
32→26 presentation.videos.GameVideosSideEffect uses presentation.videos✕
- Connections
- 3 pairs of types, where a type in presentation.videos.GameVideosSideEffect uses a type in presentation.videos.
- The types involved
com.ruben.epicworld.presentation.videos.GameVideosSideEffect.GameVideosError→com.ruben.epicworld.presentation.videos.GameVideosSideEffectcom.ruben.epicworld.presentation.videos.GameVideosSideEffect.ShowGameIdErrorToast→com.ruben.epicworld.presentation.videos.GameVideosSideEffectcom.ruben.epicworld.presentation.videos.GameVideosSideEffect.ShowNoGameVideosToast→com.ruben.epicworld.presentation.videos.GameVideosSideEffect
- Direction
- presentation.videos.GameVideosSideEffect uses presentation.videos, so a change to presentation.videos can break presentation.videos.GameVideosSideEffect, while a change to presentation.videos.GameVideosSideEffect can't break presentation.videos.
- Position
- Below the diagonal: presentation.videos.GameVideosSideEffect uses a module listed above it, which is the healthy direction.
33→18 remote.retrofit uses remote.model.response.gamevideos✕
- Connections
- 1 pair of types, where a type in remote.retrofit uses a type in remote.model.response.gamevideos.
- The types involved
com.ruben.epicworld.remote.retrofit.RetrofitApi→com.ruben.epicworld.remote.model.response.gamevideos.GetGameVideosResponse
- Direction
- remote.retrofit uses remote.model.response.gamevideos, so a change to remote.model.response.gamevideos can break remote.retrofit, while a change to remote.retrofit can't break remote.model.response.gamevideos.
- Position
- Below the diagonal: remote.retrofit uses a module listed above it, which is the healthy direction.
33→21 remote.retrofit uses remote.model.response.allgames✕
- Connections
- 1 pair of types, where a type in remote.retrofit uses a type in remote.model.response.allgames.
- The types involved
com.ruben.epicworld.remote.retrofit.RetrofitApi→com.ruben.epicworld.remote.model.response.allgames.GetAllGamesResponse
- Direction
- remote.retrofit uses remote.model.response.allgames, so a change to remote.model.response.allgames can break remote.retrofit, while a change to remote.retrofit can't break remote.model.response.allgames.
- Position
- Below the diagonal: remote.retrofit uses a module listed above it, which is the healthy direction.
33→22 remote.retrofit uses remote.model.response.gamedetails✕
- Connections
- 1 pair of types, where a type in remote.retrofit uses a type in remote.model.response.gamedetails.
- The types involved
com.ruben.epicworld.remote.retrofit.RetrofitApi→com.ruben.epicworld.remote.model.response.gamedetails.GetGameDetailsResponse
- Direction
- remote.retrofit uses remote.model.response.gamedetails, so a change to remote.model.response.gamedetails can break remote.retrofit, while a change to remote.retrofit can't break remote.model.response.gamedetails.
- Position
- Below the diagonal: remote.retrofit uses a module listed above it, which is the healthy direction.
33→27 remote.retrofit uses remote.model.response.search✕
- Connections
- 1 pair of types, where a type in remote.retrofit uses a type in remote.model.response.search.
- The types involved
com.ruben.epicworld.remote.retrofit.RetrofitApi→com.ruben.epicworld.remote.model.response.search.SearchGamesResponse
- Direction
- remote.retrofit uses remote.model.response.search, so a change to remote.model.response.search can break remote.retrofit, while a change to remote.retrofit can't break remote.model.response.search.
- Position
- Below the diagonal: remote.retrofit uses a module listed above it, which is the healthy direction.
34→11 remote.rest uses remote.model.request✕
- Connections
- 8 pairs of types, where a type in remote.rest uses a type in remote.model.request.
- The types involved
com.ruben.epicworld.remote.rest.RestApi→com.ruben.epicworld.remote.model.request.GetAllGamesRequestcom.ruben.epicworld.remote.rest.RestApi→com.ruben.epicworld.remote.model.request.GetGameDetailsRequestcom.ruben.epicworld.remote.rest.RestApi→com.ruben.epicworld.remote.model.request.GetGameVideosRequestcom.ruben.epicworld.remote.rest.RestApi→com.ruben.epicworld.remote.model.request.SearchGamesRequestcom.ruben.epicworld.remote.rest.RestApiImpl→com.ruben.epicworld.remote.model.request.GetAllGamesRequestcom.ruben.epicworld.remote.rest.RestApiImpl→com.ruben.epicworld.remote.model.request.GetGameDetailsRequestcom.ruben.epicworld.remote.rest.RestApiImpl→com.ruben.epicworld.remote.model.request.GetGameVideosRequestcom.ruben.epicworld.remote.rest.RestApiImpl→com.ruben.epicworld.remote.model.request.SearchGamesRequest
- Direction
- remote.rest uses remote.model.request, so a change to remote.model.request can break remote.rest, while a change to remote.rest can't break remote.model.request.
- Position
- Below the diagonal: remote.rest uses a module listed above it, which is the healthy direction.
34→18 remote.rest uses remote.model.response.gamevideos✕
- Connections
- 2 pairs of types, where a type in remote.rest uses a type in remote.model.response.gamevideos.
- The types involved
com.ruben.epicworld.remote.rest.RestApi→com.ruben.epicworld.remote.model.response.gamevideos.GetGameVideosResponsecom.ruben.epicworld.remote.rest.RestApiImpl→com.ruben.epicworld.remote.model.response.gamevideos.GetGameVideosResponse
- Direction
- remote.rest uses remote.model.response.gamevideos, so a change to remote.model.response.gamevideos can break remote.rest, while a change to remote.rest can't break remote.model.response.gamevideos.
- Position
- Below the diagonal: remote.rest uses a module listed above it, which is the healthy direction.
34→21 remote.rest uses remote.model.response.allgames✕
- Connections
- 2 pairs of types, where a type in remote.rest uses a type in remote.model.response.allgames.
- The types involved
com.ruben.epicworld.remote.rest.RestApi→com.ruben.epicworld.remote.model.response.allgames.GetAllGamesResponsecom.ruben.epicworld.remote.rest.RestApiImpl→com.ruben.epicworld.remote.model.response.allgames.GetAllGamesResponse
- Direction
- remote.rest uses remote.model.response.allgames, so a change to remote.model.response.allgames can break remote.rest, while a change to remote.rest can't break remote.model.response.allgames.
- Position
- Below the diagonal: remote.rest uses a module listed above it, which is the healthy direction.
34→22 remote.rest uses remote.model.response.gamedetails✕
- Connections
- 2 pairs of types, where a type in remote.rest uses a type in remote.model.response.gamedetails.
- The types involved
com.ruben.epicworld.remote.rest.RestApi→com.ruben.epicworld.remote.model.response.gamedetails.GetGameDetailsResponsecom.ruben.epicworld.remote.rest.RestApiImpl→com.ruben.epicworld.remote.model.response.gamedetails.GetGameDetailsResponse
- Direction
- remote.rest uses remote.model.response.gamedetails, so a change to remote.model.response.gamedetails can break remote.rest, while a change to remote.rest can't break remote.model.response.gamedetails.
- Position
- Below the diagonal: remote.rest uses a module listed above it, which is the healthy direction.
34→27 remote.rest uses remote.model.response.search✕
- Connections
- 2 pairs of types, where a type in remote.rest uses a type in remote.model.response.search.
- The types involved
com.ruben.epicworld.remote.rest.RestApi→com.ruben.epicworld.remote.model.response.search.SearchGamesResponsecom.ruben.epicworld.remote.rest.RestApiImpl→com.ruben.epicworld.remote.model.response.search.SearchGamesResponse
- Direction
- remote.rest uses remote.model.response.search, so a change to remote.model.response.search can break remote.rest, while a change to remote.rest can't break remote.model.response.search.
- Position
- Below the diagonal: remote.rest uses a module listed above it, which is the healthy direction.
34→33 remote.rest uses remote.retrofit✕
- Connections
- 1 pair of types, where a type in remote.rest uses a type in remote.retrofit.
- The types involved
com.ruben.epicworld.remote.rest.RestApiImpl→com.ruben.epicworld.remote.retrofit.RetrofitApi
- Direction
- remote.rest uses remote.retrofit, so a change to remote.retrofit can break remote.rest, while a change to remote.rest can't break remote.retrofit.
- Position
- Below the diagonal: remote.rest uses a module listed above it, which is the healthy direction.
35→34 remote uses remote.rest✕
- Connections
- 2 pairs of types, where a type in remote uses a type in remote.rest.
- The types involved
com.ruben.epicworld.remote.NetworkManager→com.ruben.epicworld.remote.rest.RestApicom.ruben.epicworld.remote.NetworkManagerImpl→com.ruben.epicworld.remote.rest.RestApi
- Direction
- remote uses remote.rest, so a change to remote.rest can break remote, while a change to remote can't break remote.rest.
- Position
- Below the diagonal: remote uses a module listed above it, which is the healthy direction.
36→34 data uses remote.rest✕
- Connections
- 1 pair of types, where a type in data uses a type in remote.rest.
- The types involved
com.ruben.epicworld.data.DataSourceImpl→com.ruben.epicworld.remote.rest.RestApi
- Direction
- data uses remote.rest, so a change to remote.rest can break data, while a change to data can't break remote.rest.
- Position
- Below the diagonal: data uses a module listed above it, which is the healthy direction.
36→35 data uses remote✕
- Connections
- 2 pairs of types, where a type in data uses a type in remote.
- The types involved
com.ruben.epicworld.data.DataSource→com.ruben.epicworld.remote.NetworkManagercom.ruben.epicworld.data.DataSourceImpl→com.ruben.epicworld.remote.NetworkManager
- Direction
- data uses remote, so a change to remote can break data, while a change to data can't break remote.
- Position
- Below the diagonal: data uses a module listed above it, which is the healthy direction.
37→2 data.mapper uses domain.entity.base✕
- Connections
- 2 pairs of types, where a type in data.mapper uses a type in domain.entity.base.
- The types involved
com.ruben.epicworld.data.mapper.ErrorMapper→com.ruben.epicworld.domain.entity.base.Recordcom.ruben.epicworld.data.mapper.GamesMapper→com.ruben.epicworld.domain.entity.base.Record
- Direction
- data.mapper uses domain.entity.base, so a change to domain.entity.base can break data.mapper, while a change to data.mapper can't break domain.entity.base.
- Position
- Below the diagonal: data.mapper uses a module listed above it, which is the healthy direction.
37→3 data.mapper uses domain.entity.gamedetails✕
- Connections
- 1 pair of types, where a type in data.mapper uses a type in domain.entity.gamedetails.
- The types involved
com.ruben.epicworld.data.mapper.GamesMapper→com.ruben.epicworld.domain.entity.gamedetails.GameDetailsEntity
- Direction
- data.mapper uses domain.entity.gamedetails, so a change to domain.entity.gamedetails can break data.mapper, while a change to data.mapper can't break domain.entity.gamedetails.
- Position
- Below the diagonal: data.mapper uses a module listed above it, which is the healthy direction.
37→4 data.mapper uses domain.entity.games✕
- Connections
- 1 pair of types, where a type in data.mapper uses a type in domain.entity.games.
- The types involved
com.ruben.epicworld.data.mapper.GamesMapper→com.ruben.epicworld.domain.entity.games.GamesEntity
- Direction
- data.mapper uses domain.entity.games, so a change to domain.entity.games can break data.mapper, while a change to data.mapper can't break domain.entity.games.
- Position
- Below the diagonal: data.mapper uses a module listed above it, which is the healthy direction.
37→5 data.mapper uses domain.entity.gamevideos✕
- Connections
- 1 pair of types, where a type in data.mapper uses a type in domain.entity.gamevideos.
- The types involved
com.ruben.epicworld.data.mapper.GamesMapper→com.ruben.epicworld.domain.entity.gamevideos.GameVideosEntity
- Direction
- data.mapper uses domain.entity.gamevideos, so a change to domain.entity.gamevideos can break data.mapper, while a change to data.mapper can't break domain.entity.gamevideos.
- Position
- Below the diagonal: data.mapper uses a module listed above it, which is the healthy direction.
37→18 data.mapper uses remote.model.response.gamevideos✕
- Connections
- 1 pair of types, where a type in data.mapper uses a type in remote.model.response.gamevideos.
- The types involved
com.ruben.epicworld.data.mapper.GamesMapper→com.ruben.epicworld.remote.model.response.gamevideos.GetGameVideosResponse
- Direction
- data.mapper uses remote.model.response.gamevideos, so a change to remote.model.response.gamevideos can break data.mapper, while a change to data.mapper can't break remote.model.response.gamevideos.
- Position
- Below the diagonal: data.mapper uses a module listed above it, which is the healthy direction.
37→21 data.mapper uses remote.model.response.allgames✕
- Connections
- 1 pair of types, where a type in data.mapper uses a type in remote.model.response.allgames.
- The types involved
com.ruben.epicworld.data.mapper.GamesMapper→com.ruben.epicworld.remote.model.response.allgames.GetAllGamesResponse
- Direction
- data.mapper uses remote.model.response.allgames, so a change to remote.model.response.allgames can break data.mapper, while a change to data.mapper can't break remote.model.response.allgames.
- Position
- Below the diagonal: data.mapper uses a module listed above it, which is the healthy direction.
37→22 data.mapper uses remote.model.response.gamedetails✕
- Connections
- 1 pair of types, where a type in data.mapper uses a type in remote.model.response.gamedetails.
- The types involved
com.ruben.epicworld.data.mapper.GamesMapper→com.ruben.epicworld.remote.model.response.gamedetails.GetGameDetailsResponse
- Direction
- data.mapper uses remote.model.response.gamedetails, so a change to remote.model.response.gamedetails can break data.mapper, while a change to data.mapper can't break remote.model.response.gamedetails.
- Position
- Below the diagonal: data.mapper uses a module listed above it, which is the healthy direction.
37→27 data.mapper uses remote.model.response.search✕
- Connections
- 1 pair of types, where a type in data.mapper uses a type in remote.model.response.search.
- The types involved
com.ruben.epicworld.data.mapper.GamesMapper→com.ruben.epicworld.remote.model.response.search.SearchGamesResponse
- Direction
- data.mapper uses remote.model.response.search, so a change to remote.model.response.search can break data.mapper, while a change to data.mapper can't break remote.model.response.search.
- Position
- Below the diagonal: data.mapper uses a module listed above it, which is the healthy direction.
37→35 data.mapper uses remote✕
- Connections
- 1 pair of types, where a type in data.mapper uses a type in remote.
- The types involved
com.ruben.epicworld.data.mapper.ErrorMapper→com.ruben.epicworld.remote.RemoteException
- Direction
- data.mapper uses remote, so a change to remote can break data.mapper, while a change to data.mapper can't break remote.
- Position
- Below the diagonal: data.mapper uses a module listed above it, which is the healthy direction.
38→35 remote.RemoteException uses remote✕
- Connections
- 4 pairs of types, where a type in remote.RemoteException uses a type in remote.
- The types involved
com.ruben.epicworld.remote.RemoteException.ClientError→com.ruben.epicworld.remote.RemoteExceptioncom.ruben.epicworld.remote.RemoteException.GenericError→com.ruben.epicworld.remote.RemoteExceptioncom.ruben.epicworld.remote.RemoteException.NoNetworkError→com.ruben.epicworld.remote.RemoteExceptioncom.ruben.epicworld.remote.RemoteException.ServerError→com.ruben.epicworld.remote.RemoteException
- Direction
- remote.RemoteException uses remote, so a change to remote can break remote.RemoteException, while a change to remote.RemoteException can't break remote.
- Position
- Below the diagonal: remote.RemoteException uses a module listed above it, which is the healthy direction.
39→2 data.repository uses domain.entity.base✕
- Connections
- 1 pair of types, where a type in data.repository uses a type in domain.entity.base.
- The types involved
com.ruben.epicworld.data.repository.GamesRepositoryImpl→com.ruben.epicworld.domain.entity.base.Record
- Direction
- data.repository uses domain.entity.base, so a change to domain.entity.base can break data.repository, while a change to data.repository can't break domain.entity.base.
- Position
- Below the diagonal: data.repository uses a module listed above it, which is the healthy direction.
39→3 data.repository uses domain.entity.gamedetails✕
- Connections
- 1 pair of types, where a type in data.repository uses a type in domain.entity.gamedetails.
- The types involved
com.ruben.epicworld.data.repository.GamesRepositoryImpl→com.ruben.epicworld.domain.entity.gamedetails.GameDetailsEntity
- Direction
- data.repository uses domain.entity.gamedetails, so a change to domain.entity.gamedetails can break data.repository, while a change to data.repository can't break domain.entity.gamedetails.
- Position
- Below the diagonal: data.repository uses a module listed above it, which is the healthy direction.
39→4 data.repository uses domain.entity.games✕
- Connections
- 1 pair of types, where a type in data.repository uses a type in domain.entity.games.
- The types involved
com.ruben.epicworld.data.repository.GamesRepositoryImpl→com.ruben.epicworld.domain.entity.games.GamesEntity
- Direction
- data.repository uses domain.entity.games, so a change to domain.entity.games can break data.repository, while a change to data.repository can't break domain.entity.games.
- Position
- Below the diagonal: data.repository uses a module listed above it, which is the healthy direction.
39→5 data.repository uses domain.entity.gamevideos✕
- Connections
- 1 pair of types, where a type in data.repository uses a type in domain.entity.gamevideos.
- The types involved
com.ruben.epicworld.data.repository.GamesRepositoryImpl→com.ruben.epicworld.domain.entity.gamevideos.GameVideosEntity
- Direction
- data.repository uses domain.entity.gamevideos, so a change to domain.entity.gamevideos can break data.repository, while a change to data.repository can't break domain.entity.gamevideos.
- Position
- Below the diagonal: data.repository uses a module listed above it, which is the healthy direction.
39→13 data.repository uses domain.repository✕
- Connections
- 1 pair of types, where a type in data.repository uses a type in domain.repository.
- The types involved
com.ruben.epicworld.data.repository.GamesRepositoryImpl→com.ruben.epicworld.domain.repository.GamesRepository
- Direction
- data.repository uses domain.repository, so a change to domain.repository can break data.repository, while a change to data.repository can't break domain.repository.
- Position
- Below the diagonal: data.repository uses a module listed above it, which is the healthy direction.
39→36 data.repository uses data✕
- Connections
- 1 pair of types, where a type in data.repository uses a type in data.
- The types involved
com.ruben.epicworld.data.repository.GamesRepositoryImpl→com.ruben.epicworld.data.DataSource
- Direction
- data.repository uses data, so a change to data can break data.repository, while a change to data.repository can't break data.
- Position
- Below the diagonal: data.repository uses a module listed above it, which is the healthy direction.
39→37 data.repository uses data.mapper✕
- Connections
- 2 pairs of types, where a type in data.repository uses a type in data.mapper.
- The types involved
com.ruben.epicworld.data.repository.GamesRepositoryImpl→com.ruben.epicworld.data.mapper.ErrorMappercom.ruben.epicworld.data.repository.GamesRepositoryImpl→com.ruben.epicworld.data.mapper.GamesMapper
- Direction
- data.repository uses data.mapper, so a change to data.mapper can break data.repository, while a change to data.repository can't break data.mapper.
- Position
- Below the diagonal: data.repository uses a module listed above it, which is the healthy direction.
40→13 injection uses domain.repository✕
- Connections
- 1 pair of types, where a type in injection uses a type in domain.repository.
- The types involved
com.ruben.epicworld.injection.RepositoryModule→com.ruben.epicworld.domain.repository.GamesRepository
- Direction
- injection uses domain.repository, so a change to domain.repository can break injection, while a change to injection can't break domain.repository.
- Position
- Below the diagonal: injection uses a module listed above it, which is the healthy direction.
40→33 injection uses remote.retrofit✕
- Connections
- 3 pairs of types, where a type in injection uses a type in remote.retrofit.
- The types involved
com.ruben.epicworld.injection.AppModule→com.ruben.epicworld.remote.retrofit.RetrofitApicom.ruben.epicworld.injection.RetrofitModule→com.ruben.epicworld.remote.retrofit.RetrofitApicom.ruben.epicworld.injection.RetrofitModule→com.ruben.epicworld.remote.retrofit.RetrofitInterceptor
- Direction
- injection uses remote.retrofit, so a change to remote.retrofit can break injection, while a change to injection can't break remote.retrofit.
- Position
- Below the diagonal: injection uses a module listed above it, which is the healthy direction.
40→34 injection uses remote.rest✕
- Connections
- 1 pair of types, where a type in injection uses a type in remote.rest.
- The types involved
com.ruben.epicworld.injection.AppModule→com.ruben.epicworld.remote.rest.RestApi
- Direction
- injection uses remote.rest, so a change to remote.rest can break injection, while a change to injection can't break remote.rest.
- Position
- Below the diagonal: injection uses a module listed above it, which is the healthy direction.
40→36 injection uses data✕
- Connections
- 1 pair of types, where a type in injection uses a type in data.
- The types involved
com.ruben.epicworld.injection.AppModule→com.ruben.epicworld.data.DataSource
- Direction
- injection uses data, so a change to data can break injection, while a change to injection can't break data.
- Position
- Below the diagonal: injection uses a module listed above it, which is the healthy direction.
40→39 injection uses data.repository✕
- Connections
- 1 pair of types, where a type in injection uses a type in data.repository.
- The types involved
com.ruben.epicworld.injection.RepositoryModule→com.ruben.epicworld.data.repository.GamesRepositoryImpl
- Direction
- injection uses data.repository, so a change to data.repository can break injection, while a change to injection can't break data.repository.
- Position
- Below the diagonal: injection uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 7 | High / Critical |
Roadmap
Top priorities: Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md; 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; Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md. | +9.2 pts | Low | Documentation Quality |
| 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. | +8.7 pts | Medium | Security & performance tooling |
| 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. | +6.7 pts | Medium | Architecture documentation |
| Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite. | +2.3 pts | Medium | Documentation (README) |
| Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). | +0.3 pts | Low | Static Analysis (SAST) |
| Resolve the 2 MethodTooLong finding(s) in God Classes — start with PlayerControls.kt, GameDetailsScreen.kt. | +0.1 pts | Medium | God Classes |
| Enable measurement for Architecture & structure. | unlocks measurement | Low | Architecture & structure |
| Enable measurement for Slice cohesion. | unlocks measurement | Low | Slice cohesion |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.9 | Slop | Static Analysis (SAST): High: REDACTED |
| app/src/main/java/com/ruben/epicworld/presentation/videos/PlayerControls.kt | 8.5 | Near-clean | God Classes: MethodTooLong: PlayerControlsKt.PlayerControls |
| app/src/main/java/com/ruben/epicworld/presentation/details/GameDetailsScreen.kt | 8.5 | Near-clean | God Classes: MethodTooLong: GameDetailsScreenKt.GameDetails |
| README.md | 9.5 | Near-clean | Documentation Quality: Documentation: no build, run or usage example |
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 47 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.7, the weighted average across measured dimensions.
What we checked — 47 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, 12 of 182 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.kt) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage read, produce a coverage report in a standard format (JaCoCo XML — the Gradle `jacocoTestReport` task) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (JaCoCo XML — the Gradle `jacocoTestReport` task) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.kt) and this repository declares a JVM test suite (repository root, Gradle), but it was not re-run: the analyzer environment could not run it. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D12 Dependency Hygiene — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Currency was graded against Maven Central, but whether an artifact is DEPRECATED is not: Maven Central publishes no deprecation marker, exactly as rubygems.org does not. Whether one is UNMAINTAINED is not graded either — no registry publishes a maintenance status, and release age does not stand in for one. Two of this dimension's four signals are therefore unread on a Gradle tree, and its score reflects currency alone.
- D14 License Compliance — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — this repository's 2 Maven/Gradle manifest(s) were read and none of the dependency coordinates they declare carries a version resolvable from the manifest itself: every one is inherited from a parent POM, a <dependencyManagement> block, an imported BOM or a Gradle version reference the catalogue does not define. Licences are resolved from the POMs Maven Central publishes, which requires a version to ask about, and grading whichever release happens to be newest today would be a verdict about a dependency graph this repository has not pinned. NOT a finding that this repository's licences are compliant: this dimension asserts nothing about its licensing in either direction.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-contributor repository — bus factor is not applicable (1 contributor(s) across 48 commit(s) sampled, automation and bot accounts excluded). Concentration needs a team to concentrate: with one contributor there is nobody to spread the knowledge to, so there is nothing here for the owner to act on.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D34 Knowledge Freshness — 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. Too few commits to judge knowledge freshness (48 commit(s) sampled).
- AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Boot via AndroidApp (app). the Android app did not build — `./gradlew :app:assembleDebug` exited 1: dPoolExecutor.runWorker(ThreadPoolExecutor.java:1144) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642) at java.base/java.lang.Thread.run(Thread.java:1583)…; runtime evidence skipped (launch chosen because app/build.gradle applies the Android application plugin and gradlew builds it).
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Kotlin is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's Kotlin is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- 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").
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
Dimensions
D1 · Cyclomatic Complexity
0 method(s) exceeded the cyclomatic complexity threshold of 15.
D2 · Cognitive Complexity
0 method(s) exceeded the cognitive complexity threshold of 15.
D3 · God Classes
2 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 2 MethodTooLong finding(s) in God Classes — start with PlayerControls.kt, GameDetailsScreen.kt. — One of this dimension's main actionable groups (2 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
0 duplicated block group(s) detected.
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 6 classes have LCOM4 above 3.
D12 · Dependency Hygiene
This repository's Gradle dependency graph was RESOLVED BY A BUILD, across every subproject rather than the root alone: 322 artifact(s) resolved, 198 of them gradable against Maven Central, and 168 behind a shipped release. Where a version was requested and a different one won conflict resolution, the RESOLVED version is what is graded — grading the request would recommend an upgrade already applied. Known CVEs in the same graph are a separate question again, reported under D30.
What to do
- Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
0 deducted task-comment markers across 4352 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
D19 · Documentation Quality
0 of 1 documentation facets pass in full; short on: F2 example. 1 document(s) read across 1 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).
D26 · Project Cohesion
0 of 1 build units (Gradle) flagged as possibly oversized/incoherent.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
7 finding(s): 0 critical, 5 high, 2 medium, 0 low. 5 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 1 file(s) — `gradlew` (line 177) — 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 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
- No action in Static Analysis (SAST) — all 5 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (5 issue-level, 0 of them charged here).
D35 · Change Coupling
No strong hidden change-coupling between production files.
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 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX4 · Dependency direction
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.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Add a README to the 1 of 1 project(s) that lack one — worth up to 2 pts.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
P1 · CI/CD gates
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add spotbugs with find-sec-bugs (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 1558 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:10
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.
P7 · Outbound HTTP resilience
PF3 · Async & latency hygiene
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X20 · Mistyped argument guard
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
X30 · Support guard that admits what it rejects
X5 · Nullable reference types
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 99% | Exemplary | Solid. |
| Architecture | 99% | Exemplary | Solid. |
| Maturity | 62% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 55% | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 97% | Exemplary | Solid. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 1 check(s) recorded observations but carry no score
- D36 Supply-chain Provenance & Signing — 1 observation(s) recorded · The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
Not evidenced — 3 control(s) we could not find positive evidence for
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
- P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo
Not included — 68 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: Dagger rejects, at compile time, a component that holds a binding with a narrower scope than its own.
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Kotlin code is a Spring, JSR-330 or CDI singleton bean.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — the Android app did not build — `./gradlew :app:assembleDebug` exited 1: dPoolExecutor.runWorker(ThreadPoolExecutor.java:1144) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642) at java.base/java.lang.Thread.run(Thread.java:1583)…; 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 — ~2046 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
- D14 License Compliance — JVM licences not graded — no declared coordinate carries a version the manifest itself resolves
- D16 Bus Factor — single-contributor repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D20 ADR Quality — N/A — this repo declares itself a template / kata / sample / demo; a formal ADR log is deferred to a real application built from it.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; Kotlin not measured.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .kt, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — symbol resolution incomplete — navigability not assessed
- D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet).
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — 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.
- D34 Knowledge Freshness — too few commits to judge knowledge freshness
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet).
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- D9 Test Distribution — Test source is present (.kt) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so its unit/integration/BDD/E2E split couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 45 value object(s); a Domain/Aggregates/ValueObjects layer
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- M4 Documentation accuracy — Not applicable: the 1 current-state document(s) make no claim of a kind M4 checks.
- P12 CI test-gate honesty — 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), 114 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.
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (JaCoCo XML — the Gradle `jacocoTestReport` task) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a pom.xml, Gradle or sbt build, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X2 Cancellation propagation — no C# was loaded; this repository's Kotlin was read, and no request in it can be cancelled by a caller (Ktor, OkHttp's newCall or a URL stream, from a suspend function) — a Kotlin request outside a suspend function has no caller's cancellation to honour
- X24 Document value interpolated into markup unescaped — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Kotlin was read, and it logs through none that an assembled message defeats: Android's `Log` and Timber, java.util.logging and log4j-api-kotlin take one finished message (as log4net does in C#), or it makes no call through a named logger at all. Calls made through SLF4J, log4j 2 or kotlin-logging (`LoggerFactory.getLogger`, `KotlinLogging.logger {}`) would be judged.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 5 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 5 finding(s)
- REDACTED
- REDACTED
- MethodTooLong: PlayerControlsKt.PlayerControls app/src/main/java/com/ruben/epicworld/presentation/videos/PlayerControls.kt:48
- MethodTooLong: GameDetailsScreenKt.GameDetails app/src/main/java/com/ruben/epicworld/presentation/details/GameDetailsScreen.kt:126
- REDACTED
Minor — 4 finding(s)
- Documentation: no build, run or usage example README.md:1
- REDACTED
- No ADRs
- No SAST REDACTED:10
Minor — 168 finding(s)
- Outdated (compile): com.google.dagger:hilt-android-compiler
- Outdated (compile): com.google.dagger:dagger
- Outdated (compile): com.google.dagger:dagger-compiler
- Outdated (compile): com.google.dagger:dagger-producers
- Outdated (compile): com.google.guava:failureaccess
- Outdated (compile): com.google.guava:guava
- Outdated (compile): org.checkerframework:checker-qual
- Outdated (compile): com.google.errorprone:error_prone_annotations
- Outdated (compile): com.google.j2objc:j2objc-annotations
- Outdated (compile): org.codehaus.mojo:animal-sniffer-annotations
- Outdated (compile): org.checkerframework:checker-compat-qual
- Outdated (compile): com.google.dagger:dagger-spi
- Outdated (compile): com.google.devtools.ksp:symbol-processing-api
- Outdated (compile): org.jetbrains.kotlin:kotlin-stdlib-jdk8
- Outdated (compile): org.jetbrains.kotlin:kotlin-stdlib
- Outdated (compile): org.jetbrains:annotations
- Outdated (compile): org.jetbrains.kotlin:kotlin-stdlib-common
- Outdated (compile): org.jetbrains.kotlin:kotlin-stdlib-jdk7
- Outdated (compile): com.google.googlejavaformat:google-java-format
- Outdated (compile): com.google.errorprone:javac-shaded
- Outdated (compile): net.ltgt.gradle.incap:incap
- Outdated (compile): org.jetbrains.kotlinx:kotlinx-metadata-jvm
- Outdated (compile): org.jacoco:org.jacoco.ant
- Outdated (compile): org.jacoco:org.jacoco.core
- Outdated (compile): org.ow2.asm:asm
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-2fdcfbbd71014bb3b789c62f30c24a4d/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-2fdcfbbd71014bb3b789c62f30c24a4d/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 . | 7 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet). | 0 | — |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet). | 0 | — |