Executive summary
HariKulhari06/Covid-19-Tracker falls short of our standard for production because its Testing dimensions are rated Critical, and the project has no automated tests. It scores 52 out of 100, which alone would earn Adequate, but it is rated Weak: a rating can't sit more than one step above its weakest group.
Production Readiness, at 33, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 10 points. Adding automated security scanning would lift Production Readiness itself, also worth about 10. Raising Production Readiness to 70 would lift the score to about 64.
Two pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. The project has no automated tests, so a change can break it without warning. Pinning each tool to an exact version and adding automated tests would close both risks.
The product code is 2,517 lines, about €2,400 to rebuild. The check for the health of its packages couldn't finish, so that result is missing, not a clean pass.
If Production Readiness rose from 33 to 70, the lowest score rated Strong, the score would rise from 52 to about 64.
New since the last survey: 7 findings
- Code Duplication · Edited copy of a member (33 corresponding lines) app/src/main/java/com/hari/covid_19app/firebaseDatabase/FirebaseDatabaseImp.kt
- Code Duplication · Edited copy of a member (40 corresponding lines) app/src/main/java/com/hari/covid_19app/ui/preventions/PreventionsFragment.kt
- Code Duplication · Edited copies of one member (3 members, 18+ corresponding lines) app/src/main/java/com/hari/covid_19app/utils/ext/LiveDatas.kt
- Code Duplication · Edited copy of a member (14 corresponding lines) app/src/main/java/com/hari/covid_19app/utils/ext/LiveDatas.kt
- Code Duplication · Edited copy of a member (15 corresponding lines) app/src/main/java/com/hari/covid_19app/repository/CovidRepositoryImp.kt
- Code Duplication · Duplicated block (16 lines × 2) app/src/main/java/com/hari/covid_19app/firebaseDatabase/FirebaseDatabaseImp.kt
- Code Duplication · Duplicated block (10 lines × 2) app/src/main/java/com/hari/covid_19app/utils/ext/Activities.kt
Fixed since the last survey: 4 findings
- Code Duplication · Duplicated block (16 lines × 2) app/src/main/java/com/hari/covid_19app/firebaseDatabase/FirebaseDatabaseImp.kt
- Code Duplication · Duplicated block (10 lines × 2) app/src/main/java/com/hari/covid_19app/utils/ext/Activities.kt
- Secret Scanning · Leaked secret: private-key-store app/src/debug/debug.keystore
- Secrets (history) · High secret: WD-SECRET-0004 app/src/debug/debug.keystore
Rebuild cost: about €2,400 · Estimate
| Cost to rebuild | €800 to €4,000, for 13 to 42 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 | ×0.7 at a score of 52. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 2,517 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 api.response.GlobalStateResponse | 2 di.appinitializer | 3 firebaseDatabase.FirebaseDatabaseImp | 4 model | 5 api.response | 6 db.entity | 7 di.initializer | 8 firebaseDatabase | 9 model.AppError | 10 model.LoadState | 11 model.LoadingState | 12 model.NightMode | 13 model.ResultState | 14 ui.SystemViewModel | 15 ui.preventions.PreventionsViewModel | 16 ui.questions.PopularQuestionsViewModel | 17 utils.ext | 18 com.hari.covid_19app | 19 api | 20 db.dao | 21 mapper | 22 model.AppError.ApiException | 23 model.AppError.ExternalIntegrationError | 24 ui.SystemViewModel.UiModel | 25 ui.home.HomeViewModel | 26 ui.item | 27 ui.preventions.PreventionsViewModel.UiModel | 28 ui.questions.PopularQuestionsViewModel.UiModel | 29 utils.binding | 30 db | 31 ui.home.HomeViewModel.UiModel | 32 repository | 33 di.module | 34 ui.home | 35 ui.statistics | 36 workmanager | 37 ui | 38 ui.PageConfiguration | 39 ui.preventions | 40 ui.questions |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 api.response.GlobalStateResponse | ||||||||||||||||||||||||||||||||||||||||
| 2 di.appinitializer | ||||||||||||||||||||||||||||||||||||||||
| 3 firebaseDatabase.FirebaseDatabaseImp | ||||||||||||||||||||||||||||||||||||||||
| 4 model | ||||||||||||||||||||||||||||||||||||||||
| 5 api.response | 1 | |||||||||||||||||||||||||||||||||||||||
| 6 db.entity | 2 | |||||||||||||||||||||||||||||||||||||||
| 7 di.initializer | 3 | |||||||||||||||||||||||||||||||||||||||
| 8 firebaseDatabase | 6 | |||||||||||||||||||||||||||||||||||||||
| 9 model.AppError | 3 | |||||||||||||||||||||||||||||||||||||||
| 10 model.LoadState | 3 | |||||||||||||||||||||||||||||||||||||||
| 11 model.LoadingState | 3 | |||||||||||||||||||||||||||||||||||||||
| 12 model.NightMode | 2 | |||||||||||||||||||||||||||||||||||||||
| 13 model.ResultState | 2 | |||||||||||||||||||||||||||||||||||||||
| 14 ui.SystemViewModel | 1 | |||||||||||||||||||||||||||||||||||||||
| 15 ui.preventions.PreventionsViewModel | 2 | |||||||||||||||||||||||||||||||||||||||
| 16 ui.questions.PopularQuestionsViewModel | 2 | |||||||||||||||||||||||||||||||||||||||
| 17 utils.ext | 3 | |||||||||||||||||||||||||||||||||||||||
| 18 com.hari.covid_19app | 1 | |||||||||||||||||||||||||||||||||||||||
| 19 api | 2 | |||||||||||||||||||||||||||||||||||||||
| 20 db.dao | 2 | |||||||||||||||||||||||||||||||||||||||
| 21 mapper | 2 | 2 | 2 | |||||||||||||||||||||||||||||||||||||
| 22 model.AppError.ApiException | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 23 model.AppError.ExternalIntegrationError | 1 | |||||||||||||||||||||||||||||||||||||||
| 24 ui.SystemViewModel.UiModel | 1 | |||||||||||||||||||||||||||||||||||||||
| 25 ui.home.HomeViewModel | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 26 ui.item | 3 | 5 | ||||||||||||||||||||||||||||||||||||||
| 27 ui.preventions.PreventionsViewModel.UiModel | 1 | |||||||||||||||||||||||||||||||||||||||
| 28 ui.questions.PopularQuestionsViewModel.UiModel | 1 | |||||||||||||||||||||||||||||||||||||||
| 29 utils.binding | 1 | |||||||||||||||||||||||||||||||||||||||
| 30 db | 4 | 4 | ||||||||||||||||||||||||||||||||||||||
| 31 ui.home.HomeViewModel.UiModel | 1 | |||||||||||||||||||||||||||||||||||||||
| 32 repository | 6 | 4 | 1 | 2 | 2 | 1 | ||||||||||||||||||||||||||||||||||
| 33 di.module | 1 | 2 | 2 | 2 | 2 | 3 | 2 | |||||||||||||||||||||||||||||||||
| 34 ui.home | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 35 ui.statistics | 1 | |||||||||||||||||||||||||||||||||||||||
| 36 workmanager | 1 | |||||||||||||||||||||||||||||||||||||||
| 37 ui | 3 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 38 ui.PageConfiguration | 7 | |||||||||||||||||||||||||||||||||||||||
| 39 ui.preventions | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 40 ui.questions | 1 | 1 | 1 |
5→1 api.response uses api.response.GlobalStateResponse✕
- Connections
- 1 pair of types, where a type in api.response uses a type in api.response.GlobalStateResponse.
- The types involved
com.hari.covid_19app.api.response.GlobalStateResponse→com.hari.covid_19app.api.response.GlobalStateResponse.Result
- Direction
- api.response uses api.response.GlobalStateResponse, so a change to api.response.GlobalStateResponse can break api.response, while a change to api.response can't break api.response.GlobalStateResponse.
- Position
- Below the diagonal: api.response uses a module listed above it, which is the healthy direction.
6→4 db.entity uses model✕
- Connections
- 2 pairs of types, where a type in db.entity uses a type in model.
- The types involved
com.hari.covid_19app.db.entity.GlobalState→com.hari.covid_19app.model.CovidEntitycom.hari.covid_19app.db.entity.State→com.hari.covid_19app.model.CovidEntity
- Direction
- db.entity uses model, so a change to model can break db.entity, while a change to db.entity can't break model.
- Position
- Below the diagonal: db.entity uses a module listed above it, which is the healthy direction.
7→2 di.initializer uses di.appinitializer✕
- Connections
- 3 pairs of types, where a type in di.initializer uses a type in di.appinitializer.
- The types involved
com.hari.covid_19app.di.initializer.AppInitializers→com.hari.covid_19app.di.appinitializer.AppInitializercom.hari.covid_19app.di.initializer.FirebaseDatabaseInitializer→com.hari.covid_19app.di.appinitializer.AppInitializercom.hari.covid_19app.di.initializer.ThemeInitializer→com.hari.covid_19app.di.appinitializer.AppInitializer
- Direction
- di.initializer uses di.appinitializer, so a change to di.appinitializer can break di.initializer, while a change to di.initializer can't break di.appinitializer.
- Position
- Below the diagonal: di.initializer uses a module listed above it, which is the healthy direction.
8→4 firebaseDatabase uses model✕
- Connections
- 6 pairs of types, where a type in firebaseDatabase uses a type in model.
- The types involved
com.hari.covid_19app.firebaseDatabase.FirebaseDatabase→com.hari.covid_19app.model.LoadStatecom.hari.covid_19app.firebaseDatabase.FirebaseDatabase→com.hari.covid_19app.model.Preventioncom.hari.covid_19app.firebaseDatabase.FirebaseDatabase→com.hari.covid_19app.model.Questioncom.hari.covid_19app.firebaseDatabase.FirebaseDatabaseImp→com.hari.covid_19app.model.LoadStatecom.hari.covid_19app.firebaseDatabase.FirebaseDatabaseImp→com.hari.covid_19app.model.Preventioncom.hari.covid_19app.firebaseDatabase.FirebaseDatabaseImp→com.hari.covid_19app.model.Question
- Direction
- firebaseDatabase uses model, so a change to model can break firebaseDatabase, while a change to firebaseDatabase can't break model.
- Position
- Below the diagonal: firebaseDatabase uses a module listed above it, which is the healthy direction.
9→4 model.AppError uses model✕
- Connections
- 3 pairs of types, where a type in model.AppError uses a type in model.
- The types involved
com.hari.covid_19app.model.AppError.ApiException→com.hari.covid_19app.model.AppErrorcom.hari.covid_19app.model.AppError.ExternalIntegrationError→com.hari.covid_19app.model.AppErrorcom.hari.covid_19app.model.AppError.UnknownException→com.hari.covid_19app.model.AppError
- Direction
- model.AppError uses model, so a change to model can break model.AppError, while a change to model.AppError can't break model.
- Position
- Below the diagonal: model.AppError uses a module listed above it, which is the healthy direction.
10→4 model.LoadState uses model✕
- Connections
- 3 pairs of types, where a type in model.LoadState uses a type in model.
- The types involved
com.hari.covid_19app.model.LoadState.Error→com.hari.covid_19app.model.LoadStatecom.hari.covid_19app.model.LoadState.Loaded→com.hari.covid_19app.model.LoadStatecom.hari.covid_19app.model.LoadState.Loading→com.hari.covid_19app.model.LoadState
- Direction
- model.LoadState uses model, so a change to model can break model.LoadState, while a change to model.LoadState can't break model.
- Position
- Below the diagonal: model.LoadState uses a module listed above it, which is the healthy direction.
11→4 model.LoadingState uses model✕
- Connections
- 3 pairs of types, where a type in model.LoadingState uses a type in model.
- The types involved
com.hari.covid_19app.model.LoadingState.Error→com.hari.covid_19app.model.LoadingStatecom.hari.covid_19app.model.LoadingState.Loaded→com.hari.covid_19app.model.LoadingStatecom.hari.covid_19app.model.LoadingState.Loading→com.hari.covid_19app.model.LoadingState
- Direction
- model.LoadingState uses model, so a change to model can break model.LoadingState, while a change to model.LoadingState can't break model.
- Position
- Below the diagonal: model.LoadingState uses a module listed above it, which is the healthy direction.
12→4 model.NightMode uses model✕
- Connections
- 2 pairs of types, where a type in model.NightMode uses a type in model.
- The types involved
com.hari.covid_19app.model.NightMode.NO→com.hari.covid_19app.model.NightModecom.hari.covid_19app.model.NightMode.YES→com.hari.covid_19app.model.NightMode
- Direction
- model.NightMode uses model, so a change to model can break model.NightMode, while a change to model.NightMode can't break model.
- Position
- Below the diagonal: model.NightMode uses a module listed above it, which is the healthy direction.
13→4 model.ResultState uses model✕
- Connections
- 2 pairs of types, where a type in model.ResultState uses a type in model.
- The types involved
com.hari.covid_19app.model.ResultState.Error→com.hari.covid_19app.model.ResultStatecom.hari.covid_19app.model.ResultState.Success→com.hari.covid_19app.model.ResultState
- Direction
- model.ResultState uses model, so a change to model can break model.ResultState, while a change to model.ResultState can't break model.
- Position
- Below the diagonal: model.ResultState uses a module listed above it, which is the healthy direction.
14→4 ui.SystemViewModel uses model✕
- Connections
- 1 pair of types, where a type in ui.SystemViewModel uses a type in model.
- The types involved
com.hari.covid_19app.ui.SystemViewModel.UiModel→com.hari.covid_19app.model.NightMode
- Direction
- ui.SystemViewModel uses model, so a change to model can break ui.SystemViewModel, while a change to ui.SystemViewModel can't break model.
- Position
- Below the diagonal: ui.SystemViewModel uses a module listed above it, which is the healthy direction.
15→4 ui.preventions.PreventionsViewModel uses model✕
- Connections
- 2 pairs of types, where a type in ui.preventions.PreventionsViewModel uses a type in model.
- The types involved
com.hari.covid_19app.ui.preventions.PreventionsViewModel.UiModel→com.hari.covid_19app.model.AppErrorcom.hari.covid_19app.ui.preventions.PreventionsViewModel.UiModel→com.hari.covid_19app.model.Prevention
- Direction
- ui.preventions.PreventionsViewModel uses model, so a change to model can break ui.preventions.PreventionsViewModel, while a change to ui.preventions.PreventionsViewModel can't break model.
- Position
- Below the diagonal: ui.preventions.PreventionsViewModel uses a module listed above it, which is the healthy direction.
16→4 ui.questions.PopularQuestionsViewModel uses model✕
- Connections
- 2 pairs of types, where a type in ui.questions.PopularQuestionsViewModel uses a type in model.
- The types involved
com.hari.covid_19app.ui.questions.PopularQuestionsViewModel.UiModel→com.hari.covid_19app.model.AppErrorcom.hari.covid_19app.ui.questions.PopularQuestionsViewModel.UiModel→com.hari.covid_19app.model.Question
- Direction
- ui.questions.PopularQuestionsViewModel uses model, so a change to model can break ui.questions.PopularQuestionsViewModel, while a change to ui.questions.PopularQuestionsViewModel can't break model.
- Position
- Below the diagonal: ui.questions.PopularQuestionsViewModel uses a module listed above it, which is the healthy direction.
17→4 utils.ext uses model✕
- Connections
- 3 pairs of types, where a type in utils.ext uses a type in model.
- The types involved
com.hari.covid_19app.utils.ext.AppErrorsKt→com.hari.covid_19app.model.AppErrorcom.hari.covid_19app.utils.ext.RetrofitExtensionsKt→com.hari.covid_19app.model.LoadStatecom.hari.covid_19app.utils.ext.RetrofitExtensionsKt→com.hari.covid_19app.model.Result
- Direction
- utils.ext uses model, so a change to model can break utils.ext, while a change to utils.ext can't break model.
- Position
- Below the diagonal: utils.ext uses a module listed above it, which is the healthy direction.
18→7 com.hari.covid_19app uses di.initializer✕
- Connections
- 1 pair of types, where a type in com.hari.covid_19app uses a type in di.initializer.
- The types involved
com.hari.covid_19app.CovidApp→com.hari.covid_19app.di.initializer.AppInitializers
- Direction
- com.hari.covid_19app uses di.initializer, so a change to di.initializer can break com.hari.covid_19app, while a change to com.hari.covid_19app can't break di.initializer.
- Position
- Below the diagonal: com.hari.covid_19app uses a module listed above it, which is the healthy direction.
19→5 api uses api.response✕
- Connections
- 2 pairs of types, where a type in api uses a type in api.response.
- The types involved
com.hari.covid_19app.api.CovidApiService→com.hari.covid_19app.api.response.DataApiResponsecom.hari.covid_19app.api.VirusTrackerApi→com.hari.covid_19app.api.response.GlobalStateResponse
- Direction
- api uses api.response, so a change to api.response can break api, while a change to api can't break api.response.
- Position
- Below the diagonal: api uses a module listed above it, which is the healthy direction.
20→6 db.dao uses db.entity✕
- Connections
- 2 pairs of types, where a type in db.dao uses a type in db.entity.
- The types involved
com.hari.covid_19app.db.dao.GlobalStateDao→com.hari.covid_19app.db.entity.GlobalStatecom.hari.covid_19app.db.dao.StateDao→com.hari.covid_19app.db.entity.State
- Direction
- db.dao uses db.entity, so a change to db.entity can break db.dao, while a change to db.dao can't break db.entity.
- Position
- Below the diagonal: db.dao uses a module listed above it, which is the healthy direction.
21→4 mapper uses model✕
- Connections
- 2 pairs of types, where a type in mapper uses a type in model.
- The types involved
com.hari.covid_19app.mapper.DataApiResponseToStateEntity→com.hari.covid_19app.model.Mappercom.hari.covid_19app.mapper.GlobalStateResponseToGlobalState→com.hari.covid_19app.model.Mapper
- Direction
- mapper uses model, so a change to model can break mapper, while a change to mapper can't break model.
- Position
- Below the diagonal: mapper uses a module listed above it, which is the healthy direction.
21→5 mapper uses api.response✕
- Connections
- 2 pairs of types, where a type in mapper uses a type in api.response.
- The types involved
com.hari.covid_19app.mapper.DataApiResponseToStateEntity→com.hari.covid_19app.api.response.DataApiResponsecom.hari.covid_19app.mapper.GlobalStateResponseToGlobalState→com.hari.covid_19app.api.response.GlobalStateResponse
- Direction
- mapper uses api.response, so a change to api.response can break mapper, while a change to mapper can't break api.response.
- Position
- Below the diagonal: mapper uses a module listed above it, which is the healthy direction.
21→6 mapper uses db.entity✕
- Connections
- 2 pairs of types, where a type in mapper uses a type in db.entity.
- The types involved
com.hari.covid_19app.mapper.DataApiResponseToStateEntity→com.hari.covid_19app.db.entity.Statecom.hari.covid_19app.mapper.GlobalStateResponseToGlobalState→com.hari.covid_19app.db.entity.GlobalState
- Direction
- mapper uses db.entity, so a change to db.entity can break mapper, while a change to mapper can't break db.entity.
- Position
- Below the diagonal: mapper uses a module listed above it, which is the healthy direction.
22→4 model.AppError.ApiException uses model✕
- Connections
- 2 pairs of types, where a type in model.AppError.ApiException uses a type in model.
- The types involved
com.hari.covid_19app.model.AppError.ApiException.SessionNotFoundException→com.hari.covid_19app.model.AppErrorcom.hari.covid_19app.model.AppError.ApiException.UnknownException→com.hari.covid_19app.model.AppError
- Direction
- model.AppError.ApiException uses model, so a change to model can break model.AppError.ApiException, while a change to model.AppError.ApiException can't break model.
- Position
- Below the diagonal: model.AppError.ApiException uses a module listed above it, which is the healthy direction.
22→9 model.AppError.ApiException uses model.AppError✕
- Connections
- 2 pairs of types, where a type in model.AppError.ApiException uses a type in model.AppError.
- The types involved
com.hari.covid_19app.model.AppError.ApiException.NetworkException→com.hari.covid_19app.model.AppError.ApiExceptioncom.hari.covid_19app.model.AppError.ApiException.ServerException→com.hari.covid_19app.model.AppError.ApiException
- Direction
- model.AppError.ApiException uses model.AppError, so a change to model.AppError can break model.AppError.ApiException, while a change to model.AppError.ApiException can't break model.AppError.
- Position
- Below the diagonal: model.AppError.ApiException uses a module listed above it, which is the healthy direction.
23→9 model.AppError.ExternalIntegrationError uses model.AppError✕
- Connections
- 1 pair of types, where a type in model.AppError.ExternalIntegrationError uses a type in model.AppError.
- The types involved
com.hari.covid_19app.model.AppError.ExternalIntegrationError.NoCalendarIntegrationFoundException→com.hari.covid_19app.model.AppError.ExternalIntegrationError
- Direction
- model.AppError.ExternalIntegrationError uses model.AppError, so a change to model.AppError can break model.AppError.ExternalIntegrationError, while a change to model.AppError.ExternalIntegrationError can't break model.AppError.
- Position
- Below the diagonal: model.AppError.ExternalIntegrationError uses a module listed above it, which is the healthy direction.
24→14 ui.SystemViewModel.UiModel uses ui.SystemViewModel✕
- Connections
- 1 pair of types, where a type in ui.SystemViewModel.UiModel uses a type in ui.SystemViewModel.
- The types involved
com.hari.covid_19app.ui.SystemViewModel.UiModel.Companion→com.hari.covid_19app.ui.SystemViewModel.UiModel
- Direction
- ui.SystemViewModel.UiModel uses ui.SystemViewModel, so a change to ui.SystemViewModel can break ui.SystemViewModel.UiModel, while a change to ui.SystemViewModel.UiModel can't break ui.SystemViewModel.
- Position
- Below the diagonal: ui.SystemViewModel.UiModel uses a module listed above it, which is the healthy direction.
25→4 ui.home.HomeViewModel uses model✕
- Connections
- 1 pair of types, where a type in ui.home.HomeViewModel uses a type in model.
- The types involved
com.hari.covid_19app.ui.home.HomeViewModel.UiModel→com.hari.covid_19app.model.AppError
- Direction
- ui.home.HomeViewModel uses model, so a change to model can break ui.home.HomeViewModel, while a change to ui.home.HomeViewModel can't break model.
- Position
- Below the diagonal: ui.home.HomeViewModel uses a module listed above it, which is the healthy direction.
25→6 ui.home.HomeViewModel uses db.entity✕
- Connections
- 1 pair of types, where a type in ui.home.HomeViewModel uses a type in db.entity.
- The types involved
com.hari.covid_19app.ui.home.HomeViewModel.UiModel→com.hari.covid_19app.db.entity.State
- Direction
- ui.home.HomeViewModel uses db.entity, so a change to db.entity can break ui.home.HomeViewModel, while a change to ui.home.HomeViewModel can't break db.entity.
- Position
- Below the diagonal: ui.home.HomeViewModel uses a module listed above it, which is the healthy direction.
26→4 ui.item uses model✕
- Connections
- 3 pairs of types, where a type in ui.item uses a type in model.
- The types involved
com.hari.covid_19app.ui.item.ItemBigImageLeftSide→com.hari.covid_19app.model.Preventioncom.hari.covid_19app.ui.item.ItemBigImageRightSide→com.hari.covid_19app.model.Preventioncom.hari.covid_19app.ui.item.ItemPopularQuestion→com.hari.covid_19app.model.Question
- Direction
- ui.item uses model, so a change to model can break ui.item, while a change to ui.item can't break model.
- Position
- Below the diagonal: ui.item uses a module listed above it, which is the healthy direction.
26→6 ui.item uses db.entity✕
- Connections
- 5 pairs of types, where a type in ui.item uses a type in db.entity.
- The types involved
com.hari.covid_19app.ui.item.ItemGlobalStatusCard→com.hari.covid_19app.db.entity.GlobalStatecom.hari.covid_19app.ui.item.ItemIndiaStatusCard→com.hari.covid_19app.db.entity.Statecom.hari.covid_19app.ui.item.ItemNews→com.hari.covid_19app.db.entity.Statecom.hari.covid_19app.ui.item.ItemStateAndUtStatusCard→com.hari.covid_19app.db.entity.Statecom.hari.covid_19app.ui.item.ItemStatisticsCard→com.hari.covid_19app.db.entity.State
- Direction
- ui.item uses db.entity, so a change to db.entity can break ui.item, while a change to ui.item can't break db.entity.
- Position
- Below the diagonal: ui.item uses a module listed above it, which is the healthy direction.
27→15 ui.preventions.PreventionsViewModel.UiModel uses ui.preventions.PreventionsViewModel✕
- Connections
- 1 pair of types, where a type in ui.preventions.PreventionsViewModel.UiModel uses a type in ui.preventions.PreventionsViewModel.
- The types involved
com.hari.covid_19app.ui.preventions.PreventionsViewModel.UiModel.Companion→com.hari.covid_19app.ui.preventions.PreventionsViewModel.UiModel
- Direction
- ui.preventions.PreventionsViewModel.UiModel uses ui.preventions.PreventionsViewModel, so a change to ui.preventions.PreventionsViewModel can break ui.preventions.PreventionsViewModel.UiModel, while a change to ui.preventions.PreventionsViewModel.UiModel can't break ui.preventions.PreventionsViewModel.
- Position
- Below the diagonal: ui.preventions.PreventionsViewModel.UiModel uses a module listed above it, which is the healthy direction.
28→16 ui.questions.PopularQuestionsViewModel.UiModel uses ui.questions.PopularQuestionsViewModel✕
- Connections
- 1 pair of types, where a type in ui.questions.PopularQuestionsViewModel.UiModel uses a type in ui.questions.PopularQuestionsViewModel.
- The types involved
com.hari.covid_19app.ui.questions.PopularQuestionsViewModel.UiModel.Companion→com.hari.covid_19app.ui.questions.PopularQuestionsViewModel.UiModel
- Direction
- ui.questions.PopularQuestionsViewModel.UiModel uses ui.questions.PopularQuestionsViewModel, so a change to ui.questions.PopularQuestionsViewModel can break ui.questions.PopularQuestionsViewModel.UiModel, while a change to ui.questions.PopularQuestionsViewModel.UiModel can't break ui.questions.PopularQuestionsViewModel.
- Position
- Below the diagonal: ui.questions.PopularQuestionsViewModel.UiModel uses a module listed above it, which is the healthy direction.
29→6 utils.binding uses db.entity✕
- Connections
- 1 pair of types, where a type in utils.binding uses a type in db.entity.
- The types involved
com.hari.covid_19app.utils.binding.BindingAdapterKt→com.hari.covid_19app.db.entity.State
- Direction
- utils.binding uses db.entity, so a change to db.entity can break utils.binding, while a change to utils.binding can't break db.entity.
- Position
- Below the diagonal: utils.binding uses a module listed above it, which is the healthy direction.
30→6 db uses db.entity✕
- Connections
- 4 pairs of types, where a type in db uses a type in db.entity.
- The types involved
com.hari.covid_19app.db.CovidDatabase→com.hari.covid_19app.db.entity.GlobalStatecom.hari.covid_19app.db.CovidDatabase→com.hari.covid_19app.db.entity.Statecom.hari.covid_19app.db.RoomDatabase→com.hari.covid_19app.db.entity.GlobalStatecom.hari.covid_19app.db.RoomDatabase→com.hari.covid_19app.db.entity.State
- Direction
- db uses db.entity, so a change to db.entity can break db, while a change to db can't break db.entity.
- Position
- Below the diagonal: db uses a module listed above it, which is the healthy direction.
30→20 db uses db.dao✕
- Connections
- 4 pairs of types, where a type in db uses a type in db.dao.
- The types involved
com.hari.covid_19app.db.CacheDatabase→com.hari.covid_19app.db.dao.GlobalStateDaocom.hari.covid_19app.db.CacheDatabase→com.hari.covid_19app.db.dao.StateDaocom.hari.covid_19app.db.RoomDatabase→com.hari.covid_19app.db.dao.GlobalStateDaocom.hari.covid_19app.db.RoomDatabase→com.hari.covid_19app.db.dao.StateDao
- Direction
- db uses db.dao, so a change to db.dao can break db, while a change to db can't break db.dao.
- Position
- Below the diagonal: db uses a module listed above it, which is the healthy direction.
31→25 ui.home.HomeViewModel.UiModel uses ui.home.HomeViewModel✕
- Connections
- 1 pair of types, where a type in ui.home.HomeViewModel.UiModel uses a type in ui.home.HomeViewModel.
- The types involved
com.hari.covid_19app.ui.home.HomeViewModel.UiModel.Companion→com.hari.covid_19app.ui.home.HomeViewModel.UiModel
- Direction
- ui.home.HomeViewModel.UiModel uses ui.home.HomeViewModel, so a change to ui.home.HomeViewModel can break ui.home.HomeViewModel.UiModel, while a change to ui.home.HomeViewModel.UiModel can't break ui.home.HomeViewModel.
- Position
- Below the diagonal: ui.home.HomeViewModel.UiModel uses a module listed above it, which is the healthy direction.
32→4 repository uses model✕
- Connections
- 6 pairs of types, where a type in repository uses a type in model.
- The types involved
com.hari.covid_19app.repository.CovidRepository→com.hari.covid_19app.model.LoadStatecom.hari.covid_19app.repository.CovidRepository→com.hari.covid_19app.model.Preventioncom.hari.covid_19app.repository.CovidRepository→com.hari.covid_19app.model.Questioncom.hari.covid_19app.repository.CovidRepositoryImp→com.hari.covid_19app.model.LoadStatecom.hari.covid_19app.repository.CovidRepositoryImp→com.hari.covid_19app.model.Preventioncom.hari.covid_19app.repository.CovidRepositoryImp→com.hari.covid_19app.model.Question
- Direction
- repository uses model, so a change to model can break repository, while a change to repository can't break model.
- Position
- Below the diagonal: repository uses a module listed above it, which is the healthy direction.
32→6 repository uses db.entity✕
- Connections
- 4 pairs of types, where a type in repository uses a type in db.entity.
- The types involved
com.hari.covid_19app.repository.CovidRepository→com.hari.covid_19app.db.entity.GlobalStatecom.hari.covid_19app.repository.CovidRepository→com.hari.covid_19app.db.entity.Statecom.hari.covid_19app.repository.CovidRepositoryImp→com.hari.covid_19app.db.entity.GlobalStatecom.hari.covid_19app.repository.CovidRepositoryImp→com.hari.covid_19app.db.entity.State
- Direction
- repository uses db.entity, so a change to db.entity can break repository, while a change to repository can't break db.entity.
- Position
- Below the diagonal: repository uses a module listed above it, which is the healthy direction.
32→8 repository uses firebaseDatabase✕
- Connections
- 1 pair of types, where a type in repository uses a type in firebaseDatabase.
- The types involved
com.hari.covid_19app.repository.CovidRepositoryImp→com.hari.covid_19app.firebaseDatabase.FirebaseDatabase
- Direction
- repository uses firebaseDatabase, so a change to firebaseDatabase can break repository, while a change to repository can't break firebaseDatabase.
- Position
- Below the diagonal: repository uses a module listed above it, which is the healthy direction.
32→19 repository uses api✕
- Connections
- 2 pairs of types, where a type in repository uses a type in api.
- The types involved
com.hari.covid_19app.repository.CovidRepositoryImp→com.hari.covid_19app.api.CovidApiServicecom.hari.covid_19app.repository.CovidRepositoryImp→com.hari.covid_19app.api.VirusTrackerApi
- Direction
- repository uses api, so a change to api can break repository, while a change to repository can't break api.
- Position
- Below the diagonal: repository uses a module listed above it, which is the healthy direction.
32→21 repository uses mapper✕
- Connections
- 2 pairs of types, where a type in repository uses a type in mapper.
- The types involved
com.hari.covid_19app.repository.CovidRepositoryImp→com.hari.covid_19app.mapper.DataApiResponseToStateEntitycom.hari.covid_19app.repository.CovidRepositoryImp→com.hari.covid_19app.mapper.GlobalStateResponseToGlobalState
- Direction
- repository uses mapper, so a change to mapper can break repository, while a change to repository can't break mapper.
- Position
- Below the diagonal: repository uses a module listed above it, which is the healthy direction.
32→30 repository uses db✕
- Connections
- 1 pair of types, where a type in repository uses a type in db.
- The types involved
com.hari.covid_19app.repository.CovidRepositoryImp→com.hari.covid_19app.db.CovidDatabase
- Direction
- repository uses db, so a change to db can break repository, while a change to repository can't break db.
- Position
- Below the diagonal: repository uses a module listed above it, which is the healthy direction.
33→2 di.module uses di.appinitializer✕
- Connections
- 1 pair of types, where a type in di.module uses a type in di.appinitializer.
- The types involved
com.hari.covid_19app.di.module.AppModuleBinds→com.hari.covid_19app.di.appinitializer.AppInitializer
- Direction
- di.module uses di.appinitializer, so a change to di.appinitializer can break di.module, while a change to di.module can't break di.appinitializer.
- Position
- Below the diagonal: di.module uses a module listed above it, which is the healthy direction.
33→7 di.module uses di.initializer✕
- Connections
- 2 pairs of types, where a type in di.module uses a type in di.initializer.
- The types involved
com.hari.covid_19app.di.module.AppModuleBinds→com.hari.covid_19app.di.initializer.FirebaseDatabaseInitializercom.hari.covid_19app.di.module.AppModuleBinds→com.hari.covid_19app.di.initializer.ThemeInitializer
- Direction
- di.module uses di.initializer, so a change to di.initializer can break di.module, while a change to di.module can't break di.initializer.
- Position
- Below the diagonal: di.module uses a module listed above it, which is the healthy direction.
33→8 di.module uses firebaseDatabase✕
- Connections
- 2 pairs of types, where a type in di.module uses a type in firebaseDatabase.
- The types involved
com.hari.covid_19app.di.module.AppModuleBinds→com.hari.covid_19app.firebaseDatabase.FirebaseDatabasecom.hari.covid_19app.di.module.AppModuleBinds→com.hari.covid_19app.firebaseDatabase.FirebaseDatabaseImp
- Direction
- di.module uses firebaseDatabase, so a change to firebaseDatabase can break di.module, while a change to di.module can't break firebaseDatabase.
- Position
- Below the diagonal: di.module uses a module listed above it, which is the healthy direction.
33→19 di.module uses api✕
- Connections
- 2 pairs of types, where a type in di.module uses a type in api.
- The types involved
com.hari.covid_19app.di.module.AppModule→com.hari.covid_19app.api.CovidApiServicecom.hari.covid_19app.di.module.AppModule→com.hari.covid_19app.api.VirusTrackerApi
- Direction
- di.module uses api, so a change to api can break di.module, while a change to di.module can't break api.
- Position
- Below the diagonal: di.module uses a module listed above it, which is the healthy direction.
33→20 di.module uses db.dao✕
- Connections
- 2 pairs of types, where a type in di.module uses a type in db.dao.
- The types involved
com.hari.covid_19app.di.module.AppModule→com.hari.covid_19app.db.dao.GlobalStateDaocom.hari.covid_19app.di.module.AppModule→com.hari.covid_19app.db.dao.StateDao
- Direction
- di.module uses db.dao, so a change to db.dao can break di.module, while a change to di.module can't break db.dao.
- Position
- Below the diagonal: di.module uses a module listed above it, which is the healthy direction.
33→30 di.module uses db✕
- Connections
- 3 pairs of types, where a type in di.module uses a type in db.
- The types involved
com.hari.covid_19app.di.module.AppModule→com.hari.covid_19app.db.CacheDatabasecom.hari.covid_19app.di.module.AppModuleBinds→com.hari.covid_19app.db.CovidDatabasecom.hari.covid_19app.di.module.AppModuleBinds→com.hari.covid_19app.db.RoomDatabase
- Direction
- di.module uses db, so a change to db can break di.module, while a change to di.module can't break db.
- Position
- Below the diagonal: di.module uses a module listed above it, which is the healthy direction.
33→32 di.module uses repository✕
- Connections
- 2 pairs of types, where a type in di.module uses a type in repository.
- The types involved
com.hari.covid_19app.di.module.AppModuleBinds→com.hari.covid_19app.repository.CovidRepositorycom.hari.covid_19app.di.module.AppModuleBinds→com.hari.covid_19app.repository.CovidRepositoryImp
- Direction
- di.module uses repository, so a change to repository can break di.module, while a change to di.module can't break repository.
- Position
- Below the diagonal: di.module uses a module listed above it, which is the healthy direction.
34→25 ui.home uses ui.home.HomeViewModel✕
- Connections
- 1 pair of types, where a type in ui.home uses a type in ui.home.HomeViewModel.
- The types involved
com.hari.covid_19app.ui.home.HomeViewModel→com.hari.covid_19app.ui.home.HomeViewModel.UiModel
- Direction
- ui.home uses ui.home.HomeViewModel, so a change to ui.home.HomeViewModel can break ui.home, while a change to ui.home can't break ui.home.HomeViewModel.
- Position
- Below the diagonal: ui.home uses a module listed above it, which is the healthy direction.
34→32 ui.home uses repository✕
- Connections
- 1 pair of types, where a type in ui.home uses a type in repository.
- The types involved
com.hari.covid_19app.ui.home.HomeViewModel→com.hari.covid_19app.repository.CovidRepository
- Direction
- ui.home uses repository, so a change to repository can break ui.home, while a change to ui.home can't break repository.
- Position
- Below the diagonal: ui.home uses a module listed above it, which is the healthy direction.
35→32 ui.statistics uses repository✕
- Connections
- 1 pair of types, where a type in ui.statistics uses a type in repository.
- The types involved
com.hari.covid_19app.ui.statistics.StatisticsViewModel→com.hari.covid_19app.repository.CovidRepository
- Direction
- ui.statistics uses repository, so a change to repository can break ui.statistics, while a change to ui.statistics can't break repository.
- Position
- Below the diagonal: ui.statistics uses a module listed above it, which is the healthy direction.
36→32 workmanager uses repository✕
- Connections
- 1 pair of types, where a type in workmanager uses a type in repository.
- The types involved
com.hari.covid_19app.workmanager.SyncWorker→com.hari.covid_19app.repository.CovidRepository
- Direction
- workmanager uses repository, so a change to repository can break workmanager, while a change to workmanager can't break repository.
- Position
- Below the diagonal: workmanager uses a module listed above it, which is the healthy direction.
37→4 ui uses model✕
- Connections
- 3 pairs of types, where a type in ui uses a type in model.
- The types involved
com.hari.covid_19app.ui.MainActivity→com.hari.covid_19app.model.NightModecom.hari.covid_19app.ui.SystemViewModel→com.hari.covid_19app.model.AppErrorcom.hari.covid_19app.ui.SystemViewModel→com.hari.covid_19app.model.NightMode
- Direction
- ui uses model, so a change to model can break ui, while a change to ui can't break model.
- Position
- Below the diagonal: ui uses a module listed above it, which is the healthy direction.
37→14 ui uses ui.SystemViewModel✕
- Connections
- 1 pair of types, where a type in ui uses a type in ui.SystemViewModel.
- The types involved
com.hari.covid_19app.ui.SystemViewModel→com.hari.covid_19app.ui.SystemViewModel.UiModel
- Direction
- ui uses ui.SystemViewModel, so a change to ui.SystemViewModel can break ui, while a change to ui can't break ui.SystemViewModel.
- Position
- Below the diagonal: ui uses a module listed above it, which is the healthy direction.
37→36 ui uses workmanager✕
- Connections
- 1 pair of types, where a type in ui uses a type in workmanager.
- The types involved
com.hari.covid_19app.ui.MainActivity→com.hari.covid_19app.workmanager.SyncWork
- Direction
- ui uses workmanager, so a change to workmanager can break ui, while a change to ui can't break workmanager.
- Position
- Below the diagonal: ui uses a module listed above it, which is the healthy direction.
38→37 ui.PageConfiguration uses ui✕
- Connections
- 7 pairs of types, where a type in ui.PageConfiguration uses a type in ui.
- The types involved
com.hari.covid_19app.ui.PageConfiguration.Companion→com.hari.covid_19app.ui.PageConfigurationcom.hari.covid_19app.ui.PageConfiguration.HOME→com.hari.covid_19app.ui.PageConfigurationcom.hari.covid_19app.ui.PageConfiguration.OTHER→com.hari.covid_19app.ui.PageConfigurationcom.hari.covid_19app.ui.PageConfiguration.PREVENTIONS→com.hari.covid_19app.ui.PageConfigurationcom.hari.covid_19app.ui.PageConfiguration.QUESTIONS→com.hari.covid_19app.ui.PageConfigurationcom.hari.covid_19app.ui.PageConfiguration.STATISTICS→com.hari.covid_19app.ui.PageConfigurationcom.hari.covid_19app.ui.PageConfiguration.SYMPTOMS→com.hari.covid_19app.ui.PageConfiguration
- Direction
- ui.PageConfiguration uses ui, so a change to ui can break ui.PageConfiguration, while a change to ui.PageConfiguration can't break ui.
- Position
- Below the diagonal: ui.PageConfiguration uses a module listed above it, which is the healthy direction.
39→15 ui.preventions uses ui.preventions.PreventionsViewModel✕
- Connections
- 1 pair of types, where a type in ui.preventions uses a type in ui.preventions.PreventionsViewModel.
- The types involved
com.hari.covid_19app.ui.preventions.PreventionsViewModel→com.hari.covid_19app.ui.preventions.PreventionsViewModel.UiModel
- Direction
- ui.preventions uses ui.preventions.PreventionsViewModel, so a change to ui.preventions.PreventionsViewModel can break ui.preventions, while a change to ui.preventions can't break ui.preventions.PreventionsViewModel.
- Position
- Below the diagonal: ui.preventions uses a module listed above it, which is the healthy direction.
39→32 ui.preventions uses repository✕
- Connections
- 1 pair of types, where a type in ui.preventions uses a type in repository.
- The types involved
com.hari.covid_19app.ui.preventions.PreventionsViewModel→com.hari.covid_19app.repository.CovidRepository
- Direction
- ui.preventions uses repository, so a change to repository can break ui.preventions, while a change to ui.preventions can't break repository.
- Position
- Below the diagonal: ui.preventions uses a module listed above it, which is the healthy direction.
39→37 ui.preventions uses ui✕
- Connections
- 1 pair of types, where a type in ui.preventions uses a type in ui.
- The types involved
com.hari.covid_19app.ui.preventions.PreventionsFragment→com.hari.covid_19app.ui.SystemViewModel
- Direction
- ui.preventions uses ui, so a change to ui can break ui.preventions, while a change to ui.preventions can't break ui.
- Position
- Below the diagonal: ui.preventions uses a module listed above it, which is the healthy direction.
40→16 ui.questions uses ui.questions.PopularQuestionsViewModel✕
- Connections
- 1 pair of types, where a type in ui.questions uses a type in ui.questions.PopularQuestionsViewModel.
- The types involved
com.hari.covid_19app.ui.questions.PopularQuestionsViewModel→com.hari.covid_19app.ui.questions.PopularQuestionsViewModel.UiModel
- Direction
- ui.questions uses ui.questions.PopularQuestionsViewModel, so a change to ui.questions.PopularQuestionsViewModel can break ui.questions, while a change to ui.questions can't break ui.questions.PopularQuestionsViewModel.
- Position
- Below the diagonal: ui.questions uses a module listed above it, which is the healthy direction.
40→32 ui.questions uses repository✕
- Connections
- 1 pair of types, where a type in ui.questions uses a type in repository.
- The types involved
com.hari.covid_19app.ui.questions.PopularQuestionsViewModel→com.hari.covid_19app.repository.CovidRepository
- Direction
- ui.questions uses repository, so a change to repository can break ui.questions, while a change to ui.questions can't break repository.
- Position
- Below the diagonal: ui.questions uses a module listed above it, which is the healthy direction.
40→37 ui.questions uses ui✕
- Connections
- 1 pair of types, where a type in ui.questions uses a type in ui.
- The types involved
com.hari.covid_19app.ui.questions.PopularQuestionFragment→com.hari.covid_19app.ui.SystemViewModel
- Direction
- ui.questions uses ui, so a change to ui can break ui.questions, while a change to ui.questions can't break ui.
- Position
- Below the diagonal: ui.questions 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 |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 5 | Medium |
| A05:2025 — Injection | 4 | High / Critical |
Roadmap
Top priorities: Resolve the 1 No automated tests finding(s) in Code Coverage; Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.gradle; Resolve the 15 Orphaned file finding(s) in Knowledge Freshness — start with versions.gradle, MainActivity.kt, LiveDatas.kt.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.gradle. | +10.5 pts | Low | ADR Quality |
| Resolve the 15 Orphaned file finding(s) in Knowledge Freshness — start with versions.gradle, MainActivity.kt, LiveDatas.kt. | +10.2 pts | Medium | Knowledge Freshness |
| Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing. | +9.7 pts | Medium | Security & performance tooling |
| Resolve the 1 No automated tests finding(s) in Code Coverage. | +17.2 pts | High | Code Coverage |
| 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. | +5.4 pts | Medium | Architecture documentation |
| Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. | +0.8 pts | Low | Knowledge Freshness |
| Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite. | +1.5 pts | Medium | Documentation (README) |
| Run the test suite in CI via an explicit runner step (`./gradlew test` for the toolchain this pipeline already uses) and gate merges on it. | +1.4 pts | Medium | CI/CD gates |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.1 | Slop | Static Analysis (SAST): High: REDACTED |
| app/src/main/java/com/hari/covid_19app/firebaseDatabase/FirebaseDatabaseImp.kt | 7.8 | Mixed | Code Duplication: Edited copy of a member (33 corresponding lines) |
| app/src/main/java/com/hari/covid_19app/utils/ext/LiveDatas.kt | 7.8 | Mixed | Code Duplication: Edited copies of one member (3 members, 18+ corresponding lines) |
| app/src/main/java/com/hari/covid_19app/utils/ext/RetrofitExtensions.kt | 8.5 | Near-clean | Cognitive Complexity: RetrofitExtensionsKt.executeWithRetry (cognitive 16) |
| app/src/main/java/com/hari/covid_19app/ui/preventions/PreventionsFragment.kt | 8.5 | Near-clean | Code Duplication: Edited copy of a member (40 corresponding lines) |
| app/src/main/java/com/hari/covid_19app/repository/CovidRepositoryImp.kt | 8.5 | Near-clean | Code Duplication: Edited copy of a member (15 corresponding lines) |
| app/src/main/java/com/hari/covid_19app/utils/ext/Activities.kt | 8.5 | Near-clean | Code Duplication: Duplicated block (10 lines × 2) |
| app/build.gradle | 9.5 | Near-clean | ADR Quality: No ADRs found |
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 36 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 36 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, 30 of 37 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D12 Dependency Hygiene — 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 repository's dependency manifests WERE read and their pinning discipline assessed; what went unanswered is the currency half, because jcenter.bintray.com — the registry that answers it — was asked and did not reply (the build stopped because jcenter.bintray.com, a repository this project declares, refused it with HTTP 403 — what this scan's egress allowlist returns for a host that is not on it, so the dependency graph was not resolved). This is OUR side and it is an ENVIRONMENT fault, not a missing collector: the collector exists and ran. An HTTP 403 here is what this scan's egress allowlist returns for a host that is not on it, so the remedy is to add jcenter.bintray.com to the allowlist and re-run — not to build anything.
- 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 62 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.
- 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. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `app/src/main/java/com/hari/covid_19app/ui/MainActivity.kt` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Boot via AndroidApp (app). the Android app did not build — `./gradlew :app:assembleDebug` exited 1: > com.android.tools:sdklib:26.6.0 > com.android.tools:repository:26.6.0 > Could not resolve com.google.jimfs:jimfs:1.1. > Could not get resource 'https://jcenter.bintray.com/com/google/…; 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.
- P1 CI/CD gates — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. A CI pipeline exists and the word "test" appears, but no explicit test-runner invocation (your stack's test command, or a test job) was matched — so either the gate runs tests through a step this pass could not recognise, or "test" is incidental here (a path, "latest", a reporter). Which of the two it is cannot be settled from this dimension's evidence; the coverage dimensions report whether a suite exists at all. You can widen what we reach: name the test runner explicitly in the pipeline step (your stack's test command, or a job named for the suite) so the gate is unambiguous to a reader and to this pass.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
Dimensions
D1 · Cyclomatic Complexity
0 method(s) exceeded the cyclomatic complexity threshold of 15.
D2 · Cognitive Complexity
1 method(s) exceeded the cognitive complexity threshold of 15; the worst was RetrofitExtensionsKt.executeWithRetry at 16.
What to do
- Bring the 1 body over 15 down to 15 or less in Cognitive Complexity — start with RetrofitExtensionsKt.executeWithRetry (cognitive 16). — Refactoring it lifts Cognitive Complexity from 9.9 to about 10.0/10.
D3 · God Classes
0 god class(es) detected.
D4 · Code Duplication
2 duplicated block group(s) detected. 10.1 % of the production lines (253 of 2,517) are in a reported copy. A further 5 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
What to do
- Resolve the 1 Edited copy of a member (33 corresponding lines) finding(s) in Code Duplication — start with FirebaseDatabaseImp.kt. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Edited copy of a member (40 corresponding lines) finding(s) in Code Duplication — start with PreventionsFragment.kt. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Edited copies of one member (3 members, 18+ corresponding lines) finding(s) in Code Duplication — start with LiveDatas.kt. — One of this dimension's main actionable groups (1 warning-level).
D5 · Coupling
2 production modules (Gradle), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; edges a convention plugin adds from buildSrc or build-logic are not visible there; 0 module(s) off the main sequence, with abstractness counted on 1 of the 2 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
D6 · Cohesion (LCOM4)
0 of 16 classes have LCOM4 above 3.
D8 · Code Coverage
No automated tests — no test code was found in this repository.
What to do
- Resolve the 1 No automated tests finding(s) in Code Coverage. — One of this dimension's main actionable groups (1 issue-level).
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 1 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 2 Maven/Gradle manifest(s) declare with a version resolvable from the manifest itself — the same declaration-site closure this analysis reads for dependency currency. The JVM has no lockfile a checkout is guaranteed to carry, so this is deliberately NOT the transitive closure. A further 2 coordinate(s) are not published to Maven Central — another repository (Google's Maven hosts androidx), a SNAPSHOT, or a private artifact — so their licences are not readable from here and they are outside this verdict.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
0 deducted task-comment markers across 2517 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
1 of 1 documentation facets pass in full. 2 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.gradle. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
4 finding(s): 0 critical, 2 high, 2 medium, 0 low. 2 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 1 file(s) — `gradlew` (lines 144–145, line 146, line 147, …) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
What to do
- 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 2 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 (2 issue-level, 0 of them charged here).
D34 · Knowledge Freshness
15 of 15 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is versions.gradle. Counted over 15 of the 78 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 15 Orphaned file finding(s) in Knowledge Freshness — start with versions.gradle, MainActivity.kt, LiveDatas.kt. — One of this dimension's main actionable groups (15 recommendation-level).
- Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 3 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX2 · Stateful singletons
AX3 · Project dependency cycles
AX4 · Dependency direction
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
P1 · CI/CD gates
What to do
- Run the test suite in CI via an explicit runner step (`./gradlew test` for the toolchain this pipeline already uses) and gate merges on it.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add spotbugs with find-sec-bugs (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 1 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:7
What to do
- Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
PF3 · Async & latency hygiene
X1 · Async correctness
X12 · Unreachable branch
X16 · Unfloored truncation loop
X21 · Side-effecting pattern guard
X25 · Inert configuration knob
X3 · Exception handling
X5 · Nullable reference types
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 95% | Exemplary | Solid. |
| Architecture | 97% | Exemplary | Solid. |
| Maturity | 47% | Weak — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 33% | Weak — gated by D8, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 79% | Adequate — gated by D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
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 — 77 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: Dagger rejects, at compile time, a component that holds a binding with a narrower scope than its own.
- 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: > com.android.tools:sdklib:26.6.0 > com.android.tools:repository:26.6.0 > Could not resolve com.google.jimfs:jimfs:1.1. > Could not get resource 'https://jcenter.bintray.com/com/google/…; 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 — No tests were found in the analyzed repository to assess for quality.
- D11 Test Reliability — No test suite was found to re-run, so reliability couldn't be assessed. Two searches produced that zero and both came back empty: the classifier that reads the loaded workspace recognised no suite it could run, and a walk of the source on disk — which covers the JS/TS `*.test.*` and `*.spec.*` conventions and probes for a Pester suite — found no test source in any other ecosystem either. Neither search reaches a suite that is missing from the loaded workspace and carries no name either walk recognises, so this is 'no suite found by those two searches', not a verdict that the repository has none.
- D12 Dependency Hygiene — Dependency currency not established — jcenter.bintray.com did not answer
- 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.
- D21 Naming Consistency — D21 withholds its sibling role token rows: 1 candidate(s) found and not reported.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .kt, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D26 Project Cohesion — This repository is one build unit, `app` (2517 LoC, 123 module-visible types across 27 directories), within the size bounds. Not scored: a single unit of this size gives project cohesion nothing to grade.
- 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) — 1 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — 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
- DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 5 value object(s); 1 repository port(s) loading or saving an aggregate/entity
- 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 2 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), 74 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- 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.
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — no C# was loaded; this repository's Kotlin was read, and no request in it can be cancelled by a caller (Ktor, OkHttp's newCall or a URL stream, from a suspend function) — a Kotlin request outside a suspend function has no caller's cancellation to honour
- X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X27 Collection changed while being enumerated — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Kotlin was read, and it logs through none that an assembled message defeats: Android's `Log` and Timber, java.util.logging and log4j-api-kotlin take one finished message (as log4net does in C#), or it makes no call through a named logger at all. Calls made through SLF4J, log4j 2 or kotlin-logging (`LoggerFactory.getLogger`, `KotlinLogging.logger {}`) would be judged.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 3 finding(s)
- REDACTED
- REDACTED
- No automated tests
Serious — 12 finding(s)
- REDACTED
- REDACTED
- RetrofitExtensionsKt.executeWithRetry (cognitive 16) app/src/main/java/com/hari/covid_19app/utils/ext/RetrofitExtensions.kt:20
- REDACTED
- REDACTED
- Edited copy of a member (33 corresponding lines) app/src/main/java/com/hari/covid_19app/firebaseDatabase/FirebaseDatabaseImp.kt:20
- Edited copy of a member (40 corresponding lines) app/src/main/java/com/hari/covid_19app/ui/preventions/PreventionsFragment.kt:31
- Edited copies of one member (3 members, 18+ corresponding lines) app/src/main/java/com/hari/covid_19app/utils/ext/LiveDatas.kt:55
- Edited copy of a member (14 corresponding lines) app/src/main/java/com/hari/covid_19app/utils/ext/LiveDatas.kt:13
- Edited copy of a member (15 corresponding lines) app/src/main/java/com/hari/covid_19app/repository/CovidRepositoryImp.kt:40
- Duplicated block (16 lines × 2) app/src/main/java/com/hari/covid_19app/firebaseDatabase/FirebaseDatabaseImp.kt:23
- Duplicated block (10 lines × 2) app/src/main/java/com/hari/covid_19app/utils/ext/Activities.kt:10
Minor — 22 finding(s)
- Orphaned file versions.gradle:1
- Orphaned file app/src/main/java/com/hari/covid_19app/ui/MainActivity.kt:1
- Orphaned file app/src/main/java/com/hari/covid_19app/utils/ext/LiveDatas.kt:1
- Orphaned file app/src/main/java/com/hari/covid_19app/utils/ext/RetrofitExtensions.kt:1
- Orphaned file app/src/main/java/com/hari/covid_19app/api/response/ApiResponse.kt:1
- Orphaned file app/src/main/java/com/hari/covid_19app/ui/item/ItemStatisticsCard.kt:1
- Orphaned file app/build.gradle:1
- Orphaned file app/src/main/java/com/hari/covid_19app/firebaseDatabase/FirebaseDatabaseImp.kt:1
- Orphaned file app/src/main/java/com/hari/covid_19app/utils/ext/Fragments.kt:1
- Orphaned file app/src/main/java/com/hari/covid_19app/ui/preventions/PreventionsFragment.kt:1
- Orphaned file app/src/main/java/com/hari/covid_19app/repository/CovidRepositoryImp.kt:1
- Orphaned file app/src/main/java/com/hari/covid_19app/di/module/AppModule.kt:1
- Orphaned file app/src/main/java/com/hari/covid_19app/ui/questions/PopularQuestionFragment.kt:1
- Orphaned file app/src/main/java/com/hari/covid_19app/utils/notification/NotificationHelper.kt:1
- Orphaned file app/src/main/java/com/hari/covid_19app/ui/statistics/StatisticsFragment.kt:1
- No ADRs found app/build.gradle:2
- Orphaned files with no living knowledge
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No SAST REDACTED:7
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-1bde1277062a40c38aaecfd8f8316bbb/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-1bde1277062a40c38aaecfd8f8316bbb/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 . | 4 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet). | 0 | — |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 1 file(s) — `app/src/main/java/com/hari/covid_19app/ui/MainActivity.kt` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet). | 0 | — |