Executive summary
atick-faisal/Jetpack-Android-Starter meets our standard for a template or a sample. It scores 75 out of 100 and is rated Strong, and 37 of its 39 critical findings are security problems in the build pipeline.
Every lens scores high enough to be rated Strong, so no single lens holds the score back. The best first step is protecting outgoing calls with timeouts, worth about 6 points. Adding a release approval comes next, worth about 4 points.
Thirty-five pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. One pipeline step installs packages that can change without warning, and two sets of files in separate parts keep changing together, which points to hidden dependencies. Pinning each tool to an exact version, pinning what the pipeline installs and making the hidden dependencies explicit would close these risks. Limiting each secret to its own step would fix the secret exposed to more of the pipeline than needed.
The product code is 15,991 lines, about €28,000 to rebuild.
Every lens already scores high enough to be rated Strong, so no single lens holds the score back.
Fixed since the last survey: 2 findings
- Cyclomatic Complexity · check_docs.check (cyclomatic 21) scripts/check_docs.py
- Cognitive Complexity · check_docs.check (cognitive 47) scripts/check_docs.py
Rebuild cost: about €28,000 · Estimate
| Cost to rebuild | €9,300 to €47,000, for 155 to 491 hours of work, about 0.2 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×1.1 at a score of 75. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 15,991 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 compose.navigation | 2 core.navigation | 3 core.network.model | 4 core.network.utils | 5 core.preferences.model | 6 core.room.model | 7 core.ui.components | 8 core.utils | 9 data.utils | 10 firebase.analytics.utils | 11 firebase.auth.model | 12 firebase.firestore.model | 13 core.network.api | 14 core.preferences.data | 15 core.room.data | 16 core.ui.utils | 17 data.model.home | 18 data.model.profile | 19 data.model.settings | 20 firebase.auth.data | 21 firebase.firestore.data | 22 compose | 23 compose.ui | 24 core.network.data | 25 core.preferences.di | 26 core.testing.data | 27 data.repository.auth | 28 data.repository.home | 29 data.repository.profile | 30 data.repository.settings | 31 feature.auth.navigation | 32 feature.home.navigation | 33 core.network.di | 34 data.di | 35 feature.auth.ui.signin | 36 feature.auth.ui.signup | 37 feature.home.ui.home | 38 feature.home.ui.item | 39 feature.profile.ui | 40 feature.settings.ui |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 compose.navigation | ||||||||||||||||||||||||||||||||||||||||
| 2 core.navigation | ||||||||||||||||||||||||||||||||||||||||
| 3 core.network.model | ||||||||||||||||||||||||||||||||||||||||
| 4 core.network.utils | ||||||||||||||||||||||||||||||||||||||||
| 5 core.preferences.model | ||||||||||||||||||||||||||||||||||||||||
| 6 core.room.model | ||||||||||||||||||||||||||||||||||||||||
| 7 core.ui.components | ||||||||||||||||||||||||||||||||||||||||
| 8 core.utils | ||||||||||||||||||||||||||||||||||||||||
| 9 data.utils | ||||||||||||||||||||||||||||||||||||||||
| 10 firebase.analytics.utils | ||||||||||||||||||||||||||||||||||||||||
| 11 firebase.auth.model | ||||||||||||||||||||||||||||||||||||||||
| 12 firebase.firestore.model | ||||||||||||||||||||||||||||||||||||||||
| 13 core.network.api | 1 | |||||||||||||||||||||||||||||||||||||||
| 14 core.preferences.data | 6 | |||||||||||||||||||||||||||||||||||||||
| 15 core.room.data | 3 | |||||||||||||||||||||||||||||||||||||||
| 16 core.ui.utils | 1 | |||||||||||||||||||||||||||||||||||||||
| 17 data.model.home | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 18 data.model.profile | 1 | |||||||||||||||||||||||||||||||||||||||
| 19 data.model.settings | 1 | |||||||||||||||||||||||||||||||||||||||
| 20 firebase.auth.data | 2 | |||||||||||||||||||||||||||||||||||||||
| 21 firebase.firestore.data | 2 | |||||||||||||||||||||||||||||||||||||||
| 22 compose | 1 | 2 | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||
| 23 compose.ui | 1 | 2 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 24 core.network.data | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 25 core.preferences.di | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 26 core.testing.data | 3 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 27 data.repository.auth | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 28 data.repository.home | 3 | 1 | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||
| 29 data.repository.profile | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 30 data.repository.settings | 1 | 4 | 1 | |||||||||||||||||||||||||||||||||||||
| 31 feature.auth.navigation | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 32 feature.home.navigation | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 33 core.network.di | 2 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 34 data.di | 2 | 2 | 2 | 2 | ||||||||||||||||||||||||||||||||||||
| 35 feature.auth.ui.signin | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 36 feature.auth.ui.signup | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 37 feature.home.ui.home | 2 | 3 | 1 | |||||||||||||||||||||||||||||||||||||
| 38 feature.home.ui.item | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 39 feature.profile.ui | 2 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 40 feature.settings.ui | 1 | 2 | 6 | 1 |
13→3 core.network.api uses core.network.model✕
- Connections
- 1 pair of types, where a type in core.network.api uses a type in core.network.model.
- The types involved
dev.atick.core.network.api.JetpackRestApi→dev.atick.core.network.model.NetworkPost
- Direction
- core.network.api uses core.network.model, so a change to core.network.model can break core.network.api, while a change to core.network.api can't break core.network.model.
- Position
- Below the diagonal: core.network.api uses a module listed above it, which is the healthy direction.
14→5 core.preferences.data uses core.preferences.model✕
- Connections
- 6 pairs of types, where a type in core.preferences.data uses a type in core.preferences.model.
- The types involved
dev.atick.core.preferences.data.UserPreferencesDataSource→dev.atick.core.preferences.model.DarkThemeConfigPreferencesdev.atick.core.preferences.data.UserPreferencesDataSource→dev.atick.core.preferences.model.PreferencesUserProfiledev.atick.core.preferences.data.UserPreferencesDataSource→dev.atick.core.preferences.model.UserDataPreferencesdev.atick.core.preferences.data.UserPreferencesDataSourceImpl→dev.atick.core.preferences.model.DarkThemeConfigPreferencesdev.atick.core.preferences.data.UserPreferencesDataSourceImpl→dev.atick.core.preferences.model.PreferencesUserProfiledev.atick.core.preferences.data.UserPreferencesDataSourceImpl→dev.atick.core.preferences.model.UserDataPreferences
- Direction
- core.preferences.data uses core.preferences.model, so a change to core.preferences.model can break core.preferences.data, while a change to core.preferences.data can't break core.preferences.model.
- Position
- Below the diagonal: core.preferences.data uses a module listed above it, which is the healthy direction.
15→6 core.room.data uses core.room.model✕
- Connections
- 3 pairs of types, where a type in core.room.data uses a type in core.room.model.
- The types involved
dev.atick.core.room.data.JetpackDao→dev.atick.core.room.model.JetpackEntitydev.atick.core.room.data.LocalDataSource→dev.atick.core.room.model.JetpackEntitydev.atick.core.room.data.LocalDataSourceImpl→dev.atick.core.room.model.JetpackEntity
- Direction
- core.room.data uses core.room.model, so a change to core.room.model can break core.room.data, while a change to core.room.data can't break core.room.model.
- Position
- Below the diagonal: core.room.data uses a module listed above it, which is the healthy direction.
16→8 core.ui.utils uses core.utils✕
- Connections
- 1 pair of types, where a type in core.ui.utils uses a type in core.utils.
- The types involved
dev.atick.core.ui.utils.UiState→dev.atick.core.utils.OneTimeEvent
- Direction
- core.ui.utils uses core.utils, so a change to core.utils can break core.ui.utils, while a change to core.ui.utils can't break core.utils.
- Position
- Below the diagonal: core.ui.utils uses a module listed above it, which is the healthy direction.
17→6 data.model.home uses core.room.model✕
- Connections
- 1 pair of types, where a type in data.model.home uses a type in core.room.model.
- The types involved
dev.atick.data.model.home.JetpackKt→dev.atick.core.room.model.JetpackEntity
- Direction
- data.model.home uses core.room.model, so a change to core.room.model can break data.model.home, while a change to data.model.home can't break core.room.model.
- Position
- Below the diagonal: data.model.home uses a module listed above it, which is the healthy direction.
17→12 data.model.home uses firebase.firestore.model✕
- Connections
- 1 pair of types, where a type in data.model.home uses a type in firebase.firestore.model.
- The types involved
dev.atick.data.model.home.JetpackKt→dev.atick.firebase.firestore.model.FirebaseJetpack
- Direction
- data.model.home uses firebase.firestore.model, so a change to firebase.firestore.model can break data.model.home, while a change to data.model.home can't break firebase.firestore.model.
- Position
- Below the diagonal: data.model.home uses a module listed above it, which is the healthy direction.
18→5 data.model.profile uses core.preferences.model✕
- Connections
- 1 pair of types, where a type in data.model.profile uses a type in core.preferences.model.
- The types involved
dev.atick.data.model.profile.ProfileKt→dev.atick.core.preferences.model.PreferencesUserProfile
- Direction
- data.model.profile uses core.preferences.model, so a change to core.preferences.model can break data.model.profile, while a change to data.model.profile can't break core.preferences.model.
- Position
- Below the diagonal: data.model.profile uses a module listed above it, which is the healthy direction.
19→5 data.model.settings uses core.preferences.model✕
- Connections
- 1 pair of types, where a type in data.model.settings uses a type in core.preferences.model.
- The types involved
dev.atick.data.model.settings.SettingsKt→dev.atick.core.preferences.model.DarkThemeConfigPreferences
- Direction
- data.model.settings uses core.preferences.model, so a change to core.preferences.model can break data.model.settings, while a change to data.model.settings can't break core.preferences.model.
- Position
- Below the diagonal: data.model.settings uses a module listed above it, which is the healthy direction.
20→11 firebase.auth.data uses firebase.auth.model✕
- Connections
- 2 pairs of types, where a type in firebase.auth.data uses a type in firebase.auth.model.
- The types involved
dev.atick.firebase.auth.data.AuthDataSource→dev.atick.firebase.auth.model.AuthUserdev.atick.firebase.auth.data.AuthDataSourceImpl→dev.atick.firebase.auth.model.AuthUser
- Direction
- firebase.auth.data uses firebase.auth.model, so a change to firebase.auth.model can break firebase.auth.data, while a change to firebase.auth.data can't break firebase.auth.model.
- Position
- Below the diagonal: firebase.auth.data uses a module listed above it, which is the healthy direction.
21→12 firebase.firestore.data uses firebase.firestore.model✕
- Connections
- 2 pairs of types, where a type in firebase.firestore.data uses a type in firebase.firestore.model.
- The types involved
dev.atick.firebase.firestore.data.FirebaseDataSource→dev.atick.firebase.firestore.model.FirebaseJetpackdev.atick.firebase.firestore.data.FirebaseDataSourceImpl→dev.atick.firebase.firestore.model.FirebaseJetpack
- Direction
- firebase.firestore.data uses firebase.firestore.model, so a change to firebase.firestore.model can break firebase.firestore.data, while a change to firebase.firestore.data can't break firebase.firestore.model.
- Position
- Below the diagonal: firebase.firestore.data uses a module listed above it, which is the healthy direction.
22→4 compose uses core.network.utils✕
- Connections
- 1 pair of types, where a type in compose uses a type in core.network.utils.
- The types involved
dev.atick.compose.MainActivity→dev.atick.core.network.utils.NetworkUtils
- Direction
- compose uses core.network.utils, so a change to core.network.utils can break compose, while a change to compose can't break core.network.utils.
- Position
- Below the diagonal: compose uses a module listed above it, which is the healthy direction.
22→5 compose uses core.preferences.model✕
- Connections
- 2 pairs of types, where a type in compose uses a type in core.preferences.model.
- The types involved
dev.atick.compose.MainActivityKt→dev.atick.core.preferences.model.UserDataPreferencesdev.atick.compose.MainActivityViewModel→dev.atick.core.preferences.model.UserDataPreferences
- Direction
- compose uses core.preferences.model, so a change to core.preferences.model can break compose, while a change to compose can't break core.preferences.model.
- Position
- Below the diagonal: compose uses a module listed above it, which is the healthy direction.
22→10 compose uses firebase.analytics.utils✕
- Connections
- 1 pair of types, where a type in compose uses a type in firebase.analytics.utils.
- The types involved
dev.atick.compose.MainActivity→dev.atick.firebase.analytics.utils.CrashReporter
- Direction
- compose uses firebase.analytics.utils, so a change to firebase.analytics.utils can break compose, while a change to compose can't break firebase.analytics.utils.
- Position
- Below the diagonal: compose uses a module listed above it, which is the healthy direction.
22→14 compose uses core.preferences.data✕
- Connections
- 1 pair of types, where a type in compose uses a type in core.preferences.data.
- The types involved
dev.atick.compose.MainActivityViewModel→dev.atick.core.preferences.data.UserPreferencesDataSource
- Direction
- compose uses core.preferences.data, so a change to core.preferences.data can break compose, while a change to compose can't break core.preferences.data.
- Position
- Below the diagonal: compose uses a module listed above it, which is the healthy direction.
22→16 compose uses core.ui.utils✕
- Connections
- 2 pairs of types, where a type in compose uses a type in core.ui.utils.
- The types involved
dev.atick.compose.MainActivityKt→dev.atick.core.ui.utils.UiStatedev.atick.compose.MainActivityViewModel→dev.atick.core.ui.utils.UiState
- Direction
- compose uses core.ui.utils, so a change to core.ui.utils can break compose, while a change to compose can't break core.ui.utils.
- Position
- Below the diagonal: compose uses a module listed above it, which is the healthy direction.
23→1 compose.ui uses compose.navigation✕
- Connections
- 1 pair of types, where a type in compose.ui uses a type in compose.navigation.
- The types involved
dev.atick.compose.ui.JetpackAppKt→dev.atick.compose.navigation.TopLevelDestination
- Direction
- compose.ui uses compose.navigation, so a change to compose.navigation can break compose.ui, while a change to compose.ui can't break compose.navigation.
- Position
- Below the diagonal: compose.ui uses a module listed above it, which is the healthy direction.
23→4 compose.ui uses core.network.utils✕
- Connections
- 2 pairs of types, where a type in compose.ui uses a type in core.network.utils.
- The types involved
dev.atick.compose.ui.JetpackAppState→dev.atick.core.network.utils.NetworkUtilsdev.atick.compose.ui.JetpackAppStateKt→dev.atick.core.network.utils.NetworkUtils
- Direction
- compose.ui uses core.network.utils, so a change to core.network.utils can break compose.ui, while a change to compose.ui can't break core.network.utils.
- Position
- Below the diagonal: compose.ui uses a module listed above it, which is the healthy direction.
23→10 compose.ui uses firebase.analytics.utils✕
- Connections
- 2 pairs of types, where a type in compose.ui uses a type in firebase.analytics.utils.
- The types involved
dev.atick.compose.ui.JetpackAppState→dev.atick.firebase.analytics.utils.CrashReporterdev.atick.compose.ui.JetpackAppStateKt→dev.atick.firebase.analytics.utils.CrashReporter
- Direction
- compose.ui uses firebase.analytics.utils, so a change to firebase.analytics.utils can break compose.ui, while a change to compose.ui can't break firebase.analytics.utils.
- Position
- Below the diagonal: compose.ui uses a module listed above it, which is the healthy direction.
23→16 compose.ui uses core.ui.utils✕
- Connections
- 1 pair of types, where a type in compose.ui uses a type in core.ui.utils.
- The types involved
dev.atick.compose.ui.JetpackAppKt→dev.atick.core.ui.utils.SnackbarAction
- Direction
- compose.ui uses core.ui.utils, so a change to core.ui.utils can break compose.ui, while a change to compose.ui can't break core.ui.utils.
- Position
- Below the diagonal: compose.ui uses a module listed above it, which is the healthy direction.
24→3 core.network.data uses core.network.model✕
- Connections
- 2 pairs of types, where a type in core.network.data uses a type in core.network.model.
- The types involved
dev.atick.core.network.data.NetworkDataSource→dev.atick.core.network.model.NetworkPostdev.atick.core.network.data.NetworkDataSourceImpl→dev.atick.core.network.model.NetworkPost
- Direction
- core.network.data uses core.network.model, so a change to core.network.model can break core.network.data, while a change to core.network.data can't break core.network.model.
- Position
- Below the diagonal: core.network.data uses a module listed above it, which is the healthy direction.
24→13 core.network.data uses core.network.api✕
- Connections
- 1 pair of types, where a type in core.network.data uses a type in core.network.api.
- The types involved
dev.atick.core.network.data.NetworkDataSourceImpl→dev.atick.core.network.api.JetpackRestApi
- Direction
- core.network.data uses core.network.api, so a change to core.network.api can break core.network.data, while a change to core.network.data can't break core.network.api.
- Position
- Below the diagonal: core.network.data uses a module listed above it, which is the healthy direction.
25→5 core.preferences.di uses core.preferences.model✕
- Connections
- 1 pair of types, where a type in core.preferences.di uses a type in core.preferences.model.
- The types involved
dev.atick.core.preferences.di.DatastoreModule→dev.atick.core.preferences.model.UserDataPreferences
- Direction
- core.preferences.di uses core.preferences.model, so a change to core.preferences.model can break core.preferences.di, while a change to core.preferences.di can't break core.preferences.model.
- Position
- Below the diagonal: core.preferences.di uses a module listed above it, which is the healthy direction.
25→14 core.preferences.di uses core.preferences.data✕
- Connections
- 2 pairs of types, where a type in core.preferences.di uses a type in core.preferences.data.
- The types involved
dev.atick.core.preferences.di.PreferencesDataSourceModule→dev.atick.core.preferences.data.UserPreferencesDataSourcedev.atick.core.preferences.di.PreferencesDataSourceModule→dev.atick.core.preferences.data.UserPreferencesDataSourceImpl
- Direction
- core.preferences.di uses core.preferences.data, so a change to core.preferences.data can break core.preferences.di, while a change to core.preferences.di can't break core.preferences.data.
- Position
- Below the diagonal: core.preferences.di uses a module listed above it, which is the healthy direction.
26→5 core.testing.data uses core.preferences.model✕
- Connections
- 3 pairs of types, where a type in core.testing.data uses a type in core.preferences.model.
- The types involved
dev.atick.core.testing.data.FakeUserPreferencesDataSource→dev.atick.core.preferences.model.DarkThemeConfigPreferencesdev.atick.core.testing.data.FakeUserPreferencesDataSource→dev.atick.core.preferences.model.PreferencesUserProfiledev.atick.core.testing.data.FakeUserPreferencesDataSource→dev.atick.core.preferences.model.UserDataPreferences
- Direction
- core.testing.data uses core.preferences.model, so a change to core.preferences.model can break core.testing.data, while a change to core.testing.data can't break core.preferences.model.
- Position
- Below the diagonal: core.testing.data uses a module listed above it, which is the healthy direction.
26→11 core.testing.data uses firebase.auth.model✕
- Connections
- 1 pair of types, where a type in core.testing.data uses a type in firebase.auth.model.
- The types involved
dev.atick.core.testing.data.FakeAuthDataSource→dev.atick.firebase.auth.model.AuthUser
- Direction
- core.testing.data uses firebase.auth.model, so a change to firebase.auth.model can break core.testing.data, while a change to core.testing.data can't break firebase.auth.model.
- Position
- Below the diagonal: core.testing.data uses a module listed above it, which is the healthy direction.
26→14 core.testing.data uses core.preferences.data✕
- Connections
- 1 pair of types, where a type in core.testing.data uses a type in core.preferences.data.
- The types involved
dev.atick.core.testing.data.FakeUserPreferencesDataSource→dev.atick.core.preferences.data.UserPreferencesDataSource
- Direction
- core.testing.data uses core.preferences.data, so a change to core.preferences.data can break core.testing.data, while a change to core.testing.data can't break core.preferences.data.
- Position
- Below the diagonal: core.testing.data uses a module listed above it, which is the healthy direction.
26→20 core.testing.data uses firebase.auth.data✕
- Connections
- 1 pair of types, where a type in core.testing.data uses a type in firebase.auth.data.
- The types involved
dev.atick.core.testing.data.FakeAuthDataSource→dev.atick.firebase.auth.data.AuthDataSource
- Direction
- core.testing.data uses firebase.auth.data, so a change to firebase.auth.data can break core.testing.data, while a change to core.testing.data can't break firebase.auth.data.
- Position
- Below the diagonal: core.testing.data uses a module listed above it, which is the healthy direction.
27→5 data.repository.auth uses core.preferences.model✕
- Connections
- 1 pair of types, where a type in data.repository.auth uses a type in core.preferences.model.
- The types involved
dev.atick.data.repository.auth.AuthRepositoryImpl→dev.atick.core.preferences.model.PreferencesUserProfile
- Direction
- data.repository.auth uses core.preferences.model, so a change to core.preferences.model can break data.repository.auth, while a change to data.repository.auth can't break core.preferences.model.
- Position
- Below the diagonal: data.repository.auth uses a module listed above it, which is the healthy direction.
27→14 data.repository.auth uses core.preferences.data✕
- Connections
- 1 pair of types, where a type in data.repository.auth uses a type in core.preferences.data.
- The types involved
dev.atick.data.repository.auth.AuthRepositoryImpl→dev.atick.core.preferences.data.UserPreferencesDataSource
- Direction
- data.repository.auth uses core.preferences.data, so a change to core.preferences.data can break data.repository.auth, while a change to data.repository.auth can't break core.preferences.data.
- Position
- Below the diagonal: data.repository.auth uses a module listed above it, which is the healthy direction.
27→20 data.repository.auth uses firebase.auth.data✕
- Connections
- 1 pair of types, where a type in data.repository.auth uses a type in firebase.auth.data.
- The types involved
dev.atick.data.repository.auth.AuthRepositoryImpl→dev.atick.firebase.auth.data.AuthDataSource
- Direction
- data.repository.auth uses firebase.auth.data, so a change to firebase.auth.data can break data.repository.auth, while a change to data.repository.auth can't break firebase.auth.data.
- Position
- Below the diagonal: data.repository.auth uses a module listed above it, which is the healthy direction.
28→9 data.repository.home uses data.utils✕
- Connections
- 3 pairs of types, where a type in data.repository.home uses a type in data.utils.
- The types involved
dev.atick.data.repository.home.HomeRepository→dev.atick.data.utils.Syncabledev.atick.data.repository.home.HomeRepositoryImpl→dev.atick.data.utils.SyncManagerdev.atick.data.repository.home.HomeRepositoryImpl→dev.atick.data.utils.SyncProgress
- Direction
- data.repository.home uses data.utils, so a change to data.utils can break data.repository.home, while a change to data.repository.home can't break data.utils.
- Position
- Below the diagonal: data.repository.home uses a module listed above it, which is the healthy direction.
28→14 data.repository.home uses core.preferences.data✕
- Connections
- 1 pair of types, where a type in data.repository.home uses a type in core.preferences.data.
- The types involved
dev.atick.data.repository.home.HomeRepositoryImpl→dev.atick.core.preferences.data.UserPreferencesDataSource
- Direction
- data.repository.home uses core.preferences.data, so a change to core.preferences.data can break data.repository.home, while a change to data.repository.home can't break core.preferences.data.
- Position
- Below the diagonal: data.repository.home uses a module listed above it, which is the healthy direction.
28→15 data.repository.home uses core.room.data✕
- Connections
- 1 pair of types, where a type in data.repository.home uses a type in core.room.data.
- The types involved
dev.atick.data.repository.home.HomeRepositoryImpl→dev.atick.core.room.data.LocalDataSource
- Direction
- data.repository.home uses core.room.data, so a change to core.room.data can break data.repository.home, while a change to data.repository.home can't break core.room.data.
- Position
- Below the diagonal: data.repository.home uses a module listed above it, which is the healthy direction.
28→17 data.repository.home uses data.model.home✕
- Connections
- 2 pairs of types, where a type in data.repository.home uses a type in data.model.home.
- The types involved
dev.atick.data.repository.home.HomeRepository→dev.atick.data.model.home.Jetpackdev.atick.data.repository.home.HomeRepositoryImpl→dev.atick.data.model.home.Jetpack
- Direction
- data.repository.home uses data.model.home, so a change to data.model.home can break data.repository.home, while a change to data.repository.home can't break data.model.home.
- Position
- Below the diagonal: data.repository.home uses a module listed above it, which is the healthy direction.
28→21 data.repository.home uses firebase.firestore.data✕
- Connections
- 1 pair of types, where a type in data.repository.home uses a type in firebase.firestore.data.
- The types involved
dev.atick.data.repository.home.HomeRepositoryImpl→dev.atick.firebase.firestore.data.FirebaseDataSource
- Direction
- data.repository.home uses firebase.firestore.data, so a change to firebase.firestore.data can break data.repository.home, while a change to data.repository.home can't break firebase.firestore.data.
- Position
- Below the diagonal: data.repository.home uses a module listed above it, which is the healthy direction.
29→14 data.repository.profile uses core.preferences.data✕
- Connections
- 1 pair of types, where a type in data.repository.profile uses a type in core.preferences.data.
- The types involved
dev.atick.data.repository.profile.ProfileRepositoryImpl→dev.atick.core.preferences.data.UserPreferencesDataSource
- Direction
- data.repository.profile uses core.preferences.data, so a change to core.preferences.data can break data.repository.profile, while a change to data.repository.profile can't break core.preferences.data.
- Position
- Below the diagonal: data.repository.profile uses a module listed above it, which is the healthy direction.
29→18 data.repository.profile uses data.model.profile✕
- Connections
- 2 pairs of types, where a type in data.repository.profile uses a type in data.model.profile.
- The types involved
dev.atick.data.repository.profile.ProfileRepository→dev.atick.data.model.profile.Profiledev.atick.data.repository.profile.ProfileRepositoryImpl→dev.atick.data.model.profile.Profile
- Direction
- data.repository.profile uses data.model.profile, so a change to data.model.profile can break data.repository.profile, while a change to data.repository.profile can't break data.model.profile.
- Position
- Below the diagonal: data.repository.profile uses a module listed above it, which is the healthy direction.
29→20 data.repository.profile uses firebase.auth.data✕
- Connections
- 1 pair of types, where a type in data.repository.profile uses a type in firebase.auth.data.
- The types involved
dev.atick.data.repository.profile.ProfileRepositoryImpl→dev.atick.firebase.auth.data.AuthDataSource
- Direction
- data.repository.profile uses firebase.auth.data, so a change to firebase.auth.data can break data.repository.profile, while a change to data.repository.profile can't break firebase.auth.data.
- Position
- Below the diagonal: data.repository.profile uses a module listed above it, which is the healthy direction.
30→14 data.repository.settings uses core.preferences.data✕
- Connections
- 1 pair of types, where a type in data.repository.settings uses a type in core.preferences.data.
- The types involved
dev.atick.data.repository.settings.SettingsRepositoryImpl→dev.atick.core.preferences.data.UserPreferencesDataSource
- Direction
- data.repository.settings uses core.preferences.data, so a change to core.preferences.data can break data.repository.settings, while a change to data.repository.settings can't break core.preferences.data.
- Position
- Below the diagonal: data.repository.settings uses a module listed above it, which is the healthy direction.
30→19 data.repository.settings uses data.model.settings✕
- Connections
- 4 pairs of types, where a type in data.repository.settings uses a type in data.model.settings.
- The types involved
dev.atick.data.repository.settings.SettingsRepository→dev.atick.data.model.settings.DarkThemeConfigdev.atick.data.repository.settings.SettingsRepository→dev.atick.data.model.settings.Settingsdev.atick.data.repository.settings.SettingsRepositoryImpl→dev.atick.data.model.settings.DarkThemeConfigdev.atick.data.repository.settings.SettingsRepositoryImpl→dev.atick.data.model.settings.Settings
- Direction
- data.repository.settings uses data.model.settings, so a change to data.model.settings can break data.repository.settings, while a change to data.repository.settings can't break data.model.settings.
- Position
- Below the diagonal: data.repository.settings uses a module listed above it, which is the healthy direction.
30→20 data.repository.settings uses firebase.auth.data✕
- Connections
- 1 pair of types, where a type in data.repository.settings uses a type in firebase.auth.data.
- The types involved
dev.atick.data.repository.settings.SettingsRepositoryImpl→dev.atick.firebase.auth.data.AuthDataSource
- Direction
- data.repository.settings uses firebase.auth.data, so a change to firebase.auth.data can break data.repository.settings, while a change to data.repository.settings can't break firebase.auth.data.
- Position
- Below the diagonal: data.repository.settings uses a module listed above it, which is the healthy direction.
31→2 feature.auth.navigation uses core.navigation✕
- Connections
- 1 pair of types, where a type in feature.auth.navigation uses a type in core.navigation.
- The types involved
dev.atick.feature.auth.navigation.AuthNavigationKt→dev.atick.core.navigation.Navigator
- Direction
- feature.auth.navigation uses core.navigation, so a change to core.navigation can break feature.auth.navigation, while a change to feature.auth.navigation can't break core.navigation.
- Position
- Below the diagonal: feature.auth.navigation uses a module listed above it, which is the healthy direction.
31→16 feature.auth.navigation uses core.ui.utils✕
- Connections
- 1 pair of types, where a type in feature.auth.navigation uses a type in core.ui.utils.
- The types involved
dev.atick.feature.auth.navigation.AuthNavigationKt→dev.atick.core.ui.utils.SnackbarAction
- Direction
- feature.auth.navigation uses core.ui.utils, so a change to core.ui.utils can break feature.auth.navigation, while a change to feature.auth.navigation can't break core.ui.utils.
- Position
- Below the diagonal: feature.auth.navigation uses a module listed above it, which is the healthy direction.
32→2 feature.home.navigation uses core.navigation✕
- Connections
- 1 pair of types, where a type in feature.home.navigation uses a type in core.navigation.
- The types involved
dev.atick.feature.home.navigation.HomeNavigationKt→dev.atick.core.navigation.Navigator
- Direction
- feature.home.navigation uses core.navigation, so a change to core.navigation can break feature.home.navigation, while a change to feature.home.navigation can't break core.navigation.
- Position
- Below the diagonal: feature.home.navigation uses a module listed above it, which is the healthy direction.
32→16 feature.home.navigation uses core.ui.utils✕
- Connections
- 1 pair of types, where a type in feature.home.navigation uses a type in core.ui.utils.
- The types involved
dev.atick.feature.home.navigation.HomeNavigationKt→dev.atick.core.ui.utils.SnackbarAction
- Direction
- feature.home.navigation uses core.ui.utils, so a change to core.ui.utils can break feature.home.navigation, while a change to feature.home.navigation can't break core.ui.utils.
- Position
- Below the diagonal: feature.home.navigation uses a module listed above it, which is the healthy direction.
33→4 core.network.di uses core.network.utils✕
- Connections
- 2 pairs of types, where a type in core.network.di uses a type in core.network.utils.
- The types involved
dev.atick.core.network.di.NetworkUtilsModule→dev.atick.core.network.utils.NetworkUtilsdev.atick.core.network.di.NetworkUtilsModule→dev.atick.core.network.utils.NetworkUtilsImpl
- Direction
- core.network.di uses core.network.utils, so a change to core.network.utils can break core.network.di, while a change to core.network.di can't break core.network.utils.
- Position
- Below the diagonal: core.network.di uses a module listed above it, which is the healthy direction.
33→13 core.network.di uses core.network.api✕
- Connections
- 1 pair of types, where a type in core.network.di uses a type in core.network.api.
- The types involved
dev.atick.core.network.di.RestApiModule→dev.atick.core.network.api.JetpackRestApi
- Direction
- core.network.di uses core.network.api, so a change to core.network.api can break core.network.di, while a change to core.network.di can't break core.network.api.
- Position
- Below the diagonal: core.network.di uses a module listed above it, which is the healthy direction.
33→24 core.network.di uses core.network.data✕
- Connections
- 2 pairs of types, where a type in core.network.di uses a type in core.network.data.
- The types involved
dev.atick.core.network.di.DataSourceModule→dev.atick.core.network.data.NetworkDataSourcedev.atick.core.network.di.DataSourceModule→dev.atick.core.network.data.NetworkDataSourceImpl
- Direction
- core.network.di uses core.network.data, so a change to core.network.data can break core.network.di, while a change to core.network.di can't break core.network.data.
- Position
- Below the diagonal: core.network.di uses a module listed above it, which is the healthy direction.
34→27 data.di uses data.repository.auth✕
- Connections
- 2 pairs of types, where a type in data.di uses a type in data.repository.auth.
- The types involved
dev.atick.data.di.RepositoryModule→dev.atick.data.repository.auth.AuthRepositorydev.atick.data.di.RepositoryModule→dev.atick.data.repository.auth.AuthRepositoryImpl
- Direction
- data.di uses data.repository.auth, so a change to data.repository.auth can break data.di, while a change to data.di can't break data.repository.auth.
- Position
- Below the diagonal: data.di uses a module listed above it, which is the healthy direction.
34→28 data.di uses data.repository.home✕
- Connections
- 2 pairs of types, where a type in data.di uses a type in data.repository.home.
- The types involved
dev.atick.data.di.RepositoryModule→dev.atick.data.repository.home.HomeRepositorydev.atick.data.di.RepositoryModule→dev.atick.data.repository.home.HomeRepositoryImpl
- Direction
- data.di uses data.repository.home, so a change to data.repository.home can break data.di, while a change to data.di can't break data.repository.home.
- Position
- Below the diagonal: data.di uses a module listed above it, which is the healthy direction.
34→29 data.di uses data.repository.profile✕
- Connections
- 2 pairs of types, where a type in data.di uses a type in data.repository.profile.
- The types involved
dev.atick.data.di.RepositoryModule→dev.atick.data.repository.profile.ProfileRepositorydev.atick.data.di.RepositoryModule→dev.atick.data.repository.profile.ProfileRepositoryImpl
- Direction
- data.di uses data.repository.profile, so a change to data.repository.profile can break data.di, while a change to data.di can't break data.repository.profile.
- Position
- Below the diagonal: data.di uses a module listed above it, which is the healthy direction.
34→30 data.di uses data.repository.settings✕
- Connections
- 2 pairs of types, where a type in data.di uses a type in data.repository.settings.
- The types involved
dev.atick.data.di.RepositoryModule→dev.atick.data.repository.settings.SettingsRepositorydev.atick.data.di.RepositoryModule→dev.atick.data.repository.settings.SettingsRepositoryImpl
- Direction
- data.di uses data.repository.settings, so a change to data.repository.settings can break data.di, while a change to data.di can't break data.repository.settings.
- Position
- Below the diagonal: data.di uses a module listed above it, which is the healthy direction.
35→16 feature.auth.ui.signin uses core.ui.utils✕
- Connections
- 3 pairs of types, where a type in feature.auth.ui.signin uses a type in core.ui.utils.
- The types involved
dev.atick.feature.auth.ui.signin.SignInScreenData→dev.atick.core.ui.utils.TextFieldDatadev.atick.feature.auth.ui.signin.SignInScreenKt→dev.atick.core.ui.utils.SnackbarActiondev.atick.feature.auth.ui.signin.SignInViewModel→dev.atick.core.ui.utils.UiState
- Direction
- feature.auth.ui.signin uses core.ui.utils, so a change to core.ui.utils can break feature.auth.ui.signin, while a change to feature.auth.ui.signin can't break core.ui.utils.
- Position
- Below the diagonal: feature.auth.ui.signin uses a module listed above it, which is the healthy direction.
35→27 feature.auth.ui.signin uses data.repository.auth✕
- Connections
- 1 pair of types, where a type in feature.auth.ui.signin uses a type in data.repository.auth.
- The types involved
dev.atick.feature.auth.ui.signin.SignInViewModel→dev.atick.data.repository.auth.AuthRepository
- Direction
- feature.auth.ui.signin uses data.repository.auth, so a change to data.repository.auth can break feature.auth.ui.signin, while a change to feature.auth.ui.signin can't break data.repository.auth.
- Position
- Below the diagonal: feature.auth.ui.signin uses a module listed above it, which is the healthy direction.
36→16 feature.auth.ui.signup uses core.ui.utils✕
- Connections
- 3 pairs of types, where a type in feature.auth.ui.signup uses a type in core.ui.utils.
- The types involved
dev.atick.feature.auth.ui.signup.SignUpScreenData→dev.atick.core.ui.utils.TextFieldDatadev.atick.feature.auth.ui.signup.SignUpScreenKt→dev.atick.core.ui.utils.SnackbarActiondev.atick.feature.auth.ui.signup.SignUpViewModel→dev.atick.core.ui.utils.UiState
- Direction
- feature.auth.ui.signup uses core.ui.utils, so a change to core.ui.utils can break feature.auth.ui.signup, while a change to feature.auth.ui.signup can't break core.ui.utils.
- Position
- Below the diagonal: feature.auth.ui.signup uses a module listed above it, which is the healthy direction.
36→27 feature.auth.ui.signup uses data.repository.auth✕
- Connections
- 1 pair of types, where a type in feature.auth.ui.signup uses a type in data.repository.auth.
- The types involved
dev.atick.feature.auth.ui.signup.SignUpViewModel→dev.atick.data.repository.auth.AuthRepository
- Direction
- feature.auth.ui.signup uses data.repository.auth, so a change to data.repository.auth can break feature.auth.ui.signup, while a change to feature.auth.ui.signup can't break data.repository.auth.
- Position
- Below the diagonal: feature.auth.ui.signup uses a module listed above it, which is the healthy direction.
37→16 feature.home.ui.home uses core.ui.utils✕
- Connections
- 2 pairs of types, where a type in feature.home.ui.home uses a type in core.ui.utils.
- The types involved
dev.atick.feature.home.ui.home.HomeScreenKt→dev.atick.core.ui.utils.SnackbarActiondev.atick.feature.home.ui.home.HomeViewModel→dev.atick.core.ui.utils.UiState
- Direction
- feature.home.ui.home uses core.ui.utils, so a change to core.ui.utils can break feature.home.ui.home, while a change to feature.home.ui.home can't break core.ui.utils.
- Position
- Below the diagonal: feature.home.ui.home uses a module listed above it, which is the healthy direction.
37→17 feature.home.ui.home uses data.model.home✕
- Connections
- 3 pairs of types, where a type in feature.home.ui.home uses a type in data.model.home.
- The types involved
dev.atick.feature.home.ui.home.HomeScreenData→dev.atick.data.model.home.Jetpackdev.atick.feature.home.ui.home.HomeScreenKt→dev.atick.data.model.home.Jetpackdev.atick.feature.home.ui.home.HomeViewModel→dev.atick.data.model.home.Jetpack
- Direction
- feature.home.ui.home uses data.model.home, so a change to data.model.home can break feature.home.ui.home, while a change to feature.home.ui.home can't break data.model.home.
- Position
- Below the diagonal: feature.home.ui.home uses a module listed above it, which is the healthy direction.
37→28 feature.home.ui.home uses data.repository.home✕
- Connections
- 1 pair of types, where a type in feature.home.ui.home uses a type in data.repository.home.
- The types involved
dev.atick.feature.home.ui.home.HomeViewModel→dev.atick.data.repository.home.HomeRepository
- Direction
- feature.home.ui.home uses data.repository.home, so a change to data.repository.home can break feature.home.ui.home, while a change to feature.home.ui.home can't break data.repository.home.
- Position
- Below the diagonal: feature.home.ui.home uses a module listed above it, which is the healthy direction.
38→8 feature.home.ui.item uses core.utils✕
- Connections
- 1 pair of types, where a type in feature.home.ui.item uses a type in core.utils.
- The types involved
dev.atick.feature.home.ui.item.ItemScreenData→dev.atick.core.utils.OneTimeEvent
- Direction
- feature.home.ui.item uses core.utils, so a change to core.utils can break feature.home.ui.item, while a change to feature.home.ui.item can't break core.utils.
- Position
- Below the diagonal: feature.home.ui.item uses a module listed above it, which is the healthy direction.
38→16 feature.home.ui.item uses core.ui.utils✕
- Connections
- 2 pairs of types, where a type in feature.home.ui.item uses a type in core.ui.utils.
- The types involved
dev.atick.feature.home.ui.item.ItemScreenKt→dev.atick.core.ui.utils.SnackbarActiondev.atick.feature.home.ui.item.ItemViewModel→dev.atick.core.ui.utils.UiState
- Direction
- feature.home.ui.item uses core.ui.utils, so a change to core.ui.utils can break feature.home.ui.item, while a change to feature.home.ui.item can't break core.ui.utils.
- Position
- Below the diagonal: feature.home.ui.item uses a module listed above it, which is the healthy direction.
38→28 feature.home.ui.item uses data.repository.home✕
- Connections
- 1 pair of types, where a type in feature.home.ui.item uses a type in data.repository.home.
- The types involved
dev.atick.feature.home.ui.item.ItemViewModel→dev.atick.data.repository.home.HomeRepository
- Direction
- feature.home.ui.item uses data.repository.home, so a change to data.repository.home can break feature.home.ui.item, while a change to feature.home.ui.item can't break data.repository.home.
- Position
- Below the diagonal: feature.home.ui.item uses a module listed above it, which is the healthy direction.
39→16 feature.profile.ui uses core.ui.utils✕
- Connections
- 2 pairs of types, where a type in feature.profile.ui uses a type in core.ui.utils.
- The types involved
dev.atick.feature.profile.ui.ProfileScreenKt→dev.atick.core.ui.utils.SnackbarActiondev.atick.feature.profile.ui.ProfileViewModel→dev.atick.core.ui.utils.UiState
- Direction
- feature.profile.ui uses core.ui.utils, so a change to core.ui.utils can break feature.profile.ui, while a change to feature.profile.ui can't break core.ui.utils.
- Position
- Below the diagonal: feature.profile.ui uses a module listed above it, which is the healthy direction.
39→18 feature.profile.ui uses data.model.profile✕
- Connections
- 2 pairs of types, where a type in feature.profile.ui uses a type in data.model.profile.
- The types involved
dev.atick.feature.profile.ui.ProfileScreenKt→dev.atick.data.model.profile.Profiledev.atick.feature.profile.ui.ProfileViewModel→dev.atick.data.model.profile.Profile
- Direction
- feature.profile.ui uses data.model.profile, so a change to data.model.profile can break feature.profile.ui, while a change to feature.profile.ui can't break data.model.profile.
- Position
- Below the diagonal: feature.profile.ui uses a module listed above it, which is the healthy direction.
39→29 feature.profile.ui uses data.repository.profile✕
- Connections
- 1 pair of types, where a type in feature.profile.ui uses a type in data.repository.profile.
- The types involved
dev.atick.feature.profile.ui.ProfileViewModel→dev.atick.data.repository.profile.ProfileRepository
- Direction
- feature.profile.ui uses data.repository.profile, so a change to data.repository.profile can break feature.profile.ui, while a change to feature.profile.ui can't break data.repository.profile.
- Position
- Below the diagonal: feature.profile.ui uses a module listed above it, which is the healthy direction.
40→7 feature.settings.ui uses core.ui.components✕
- Connections
- 1 pair of types, where a type in feature.settings.ui uses a type in core.ui.components.
- The types involved
dev.atick.feature.settings.ui.SettingsDialogKt→dev.atick.core.ui.components.ToggleOption
- Direction
- feature.settings.ui uses core.ui.components, so a change to core.ui.components can break feature.settings.ui, while a change to feature.settings.ui can't break core.ui.components.
- Position
- Below the diagonal: feature.settings.ui uses a module listed above it, which is the healthy direction.
40→16 feature.settings.ui uses core.ui.utils✕
- Connections
- 2 pairs of types, where a type in feature.settings.ui uses a type in core.ui.utils.
- The types involved
dev.atick.feature.settings.ui.SettingsDialogKt→dev.atick.core.ui.utils.SnackbarActiondev.atick.feature.settings.ui.SettingsViewModel→dev.atick.core.ui.utils.UiState
- Direction
- feature.settings.ui uses core.ui.utils, so a change to core.ui.utils can break feature.settings.ui, while a change to feature.settings.ui can't break core.ui.utils.
- Position
- Below the diagonal: feature.settings.ui uses a module listed above it, which is the healthy direction.
40→19 feature.settings.ui uses data.model.settings✕
- Connections
- 6 pairs of types, where a type in feature.settings.ui uses a type in data.model.settings.
- The types involved
dev.atick.feature.settings.ui.SettingsDialogKt→dev.atick.data.model.settings.DarkThemeConfigdev.atick.feature.settings.ui.SettingsDialogKt→dev.atick.data.model.settings.Languagedev.atick.feature.settings.ui.SettingsDialogKt→dev.atick.data.model.settings.Settingsdev.atick.feature.settings.ui.SettingsViewModel→dev.atick.data.model.settings.DarkThemeConfigdev.atick.feature.settings.ui.SettingsViewModel→dev.atick.data.model.settings.Languagedev.atick.feature.settings.ui.SettingsViewModel→dev.atick.data.model.settings.Settings
- Direction
- feature.settings.ui uses data.model.settings, so a change to data.model.settings can break feature.settings.ui, while a change to feature.settings.ui can't break data.model.settings.
- Position
- Below the diagonal: feature.settings.ui uses a module listed above it, which is the healthy direction.
40→30 feature.settings.ui uses data.repository.settings✕
- Connections
- 1 pair of types, where a type in feature.settings.ui uses a type in data.repository.settings.
- The types involved
dev.atick.feature.settings.ui.SettingsViewModel→dev.atick.data.repository.settings.SettingsRepository
- Direction
- feature.settings.ui uses data.repository.settings, so a change to data.repository.settings can break feature.settings.ui, while a change to feature.settings.ui can't break data.repository.settings.
- Position
- Below the diagonal: feature.settings.ui uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 37 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 7 | Medium |
Roadmap
Top priorities: Set connect and read timeouts on every client (`RestTemplateBuilder.connectTimeout/readTimeout`, WebClient `responseTimeout`, `HttpRequest.Builder.timeout`, `HttpURLConnection.setReadTimeout`, Feign `connectTimeout`/`readTimeout` in configuration), and wrap calls to dependencies in resilience4j `@Retry`/`@CircuitBreaker`/`@TimeLimiter` (or Spring Retry); Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it; Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Set connect and read timeouts on every client (`RestTemplateBuilder.connectTimeout/readTimeout`, WebClient `responseTimeout`, `HttpRequest.Builder.timeout`, `HttpURLConnection.setReadTimeout`, Feign `connectTimeout`/`readTimeout` in configuration), and wrap calls to dependencies in resilience4j `@Retry`/`@CircuitBreaker`/`@TimeLimiter` (or Spring Retry). | +6.0 pts | Medium | Outbound HTTP resilience |
| Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it. | +4.1 pts | Medium | Deployment & Rollback |
| 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. | +1.9 pts | Medium | Architecture documentation |
| Set security response headers on the surface this repository serves: an `add_header` directive per header in the nginx/Caddy/Apache config, a `_headers` / `vercel.json` / `netlify.toml` entry for a static host, or `helmet()` in the HTTP server. `Content-Security-Policy` is the one that pays for itself first — it is what contains an injected script once one reaches the page — followed by `X-Content-Type-Options: nosniff` and a frame policy (`X-Frame-Options: DENY`, or CSP `frame-ancestors`). Where the app is served from a build container, the header configuration belongs in the image beside the built assets, so it ships with them rather than depending on where it lands. | +1.8 pts | Medium | Web-Security Posture |
| Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. | +0.8 pts | Low | Static Analysis (SAST) |
| Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. | +0.8 pts | Low | Static Analysis (SAST) |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. | +0.5 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +0.5 pts | Low | Supply-chain Provenance & Signing |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.3 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.3 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.3 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| app/src/main/kotlin/dev/atick/compose/ui/JetpackAppState.kt | 7.0 | Near-clean | Change Coupling: Boundary-crossing change coupling: JetpackAppState.kt ↔ ProfileNavigation.kt |
| core/ui/src/main/kotlin/dev/atick/core/ui/components/Button.kt | 7.3 | Near-clean | Explicit Debt: TodoComment |
| core/ui/src/main/kotlin/dev/atick/core/ui/components/IconButton.kt | 7.3 | Near-clean | Explicit Debt: TodoComment |
| feature/auth/src/main/kotlin/dev/atick/feature/auth/ui/signin/SignInScreen.kt | 7.8 | Near-clean | Code Duplication: Duplicated block (43 lines × 2) |
| feature/auth/src/main/kotlin/dev/atick/feature/auth/navigation/AuthNavigation.kt | 7.8 | Near-clean | Change Coupling: Change coupling: AuthNavigation.kt ↔ SignUpScreen.kt |
| data/src/main/kotlin/dev/atick/data/repository/home/HomeRepositoryImpl.kt | 8.2 | Near-clean | Explicit Debt: TodoComment |
| core/ui/src/main/kotlin/dev/atick/core/ui/components/Chip.kt | 8.2 | Near-clean | Explicit Debt: TodoComment |
| core/ui/src/main/kotlin/dev/atick/core/ui/components/Tag.kt | 8.2 | Near-clean | Explicit Debt: TodoComment |
| core/room/src/main/kotlin/dev/atick/core/room/di/DatabaseModule.kt | 8.2 | Near-clean | Explicit Debt: TodoComment |
| core/android/src/main/kotlin/dev/atick/core/extensions/ContextExtensions.kt | 8.2 | Near-clean | Explicit Debt: TodoComment |
| build-logic/convention/src/main/kotlin/DokkaConventionPlugin.kt | 8.2 | Near-clean | Explicit Debt: TodoComment |
| core/android/src/main/kotlin/dev/atick/core/extensions/NumberExtensions.kt | 8.5 | Near-clean | Cognitive Complexity: NumberExtensionsKt.format (cognitive 16) |
| build-logic/convention/src/main/kotlin/ApplicationConventionPlugin.kt | 8.5 | Near-clean | Change Coupling: Change coupling clique: ApplicationConventionPlugin.kt, LibraryConventionPlugin.kt, UiLibraryConventionPlugin.kt |
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 58 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 58 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, 60 of 68 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.kt) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage read, produce a coverage report in a standard format (JaCoCo XML — the Gradle `jacocoTestReport` task) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (JaCoCo XML — the Gradle `jacocoTestReport` task) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.kt) and this repository declares a JVM test suite (repository root, Gradle), but it was not re-run: no test result was produced. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares a Gradle build (build.gradle/build.gradle.kts), but the licence verdict published here was taken over its gem dependencies. Nothing was read about its Gradle dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- 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 965 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. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (lint/build.gradle.kts), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `core/android/src/main/kotlin/dev/atick/core/extensions/NumberExtensions.kt`, `core/navigation/src/main/kotlin/dev/atick/core/navigation/Navigator.kt`, `core/network/src/main/kotlin/dev/atick/core/network/di/RestApiModule.kt`, `core/network/src/main/kotlin/dev/atick/core/network/di/okhttp/OkHttpClientModule.kt`, `core/network/src/main/kotlin/dev/atick/core/network/di/retrofit/RetrofitModule.kt`, … (+4 more) 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.
- AXB1 Runtime evidence locked — no reproducible boot — 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. Subject: a native UI project (sync/src/main/AndroidManifest.xml). The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. We then boot it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Kotlin is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's Kotlin is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- 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.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
0 method(s) exceeded the cyclomatic complexity threshold of 15.
D2 · Cognitive Complexity
1 method(s) exceeded the cognitive complexity threshold of 15; the worst was NumberExtensionsKt.format at 16.
What to do
- Bring the 1 body over 15 down to 15 or less in Cognitive Complexity — start with NumberExtensionsKt.format (cognitive 16). — Refactoring it lifts Cognitive Complexity from 9.9 to about 10.0/10.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
0 god class(es) detected.
D4 · Code Duplication
2 duplicated block group(s) detected.
What to do
- Resolve the 1 Duplicated block (43 lines × 2) finding(s) in Code Duplication — start with SignInScreen.kt. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (30–31 lines × 2) finding(s) in Code Duplication — start with SignInScreen.kt. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
20 production modules (Gradle), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; edges a convention plugin adds from buildSrc or build-logic are not visible there; 1 module(s) off the main sequence.
What to do
- Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
0 of 22 classes have LCOM4 above 3.
D9 · Test Distribution
11 test methods: 11 unit, 0 integration, 0 BDD, 0 e2e. The Python suite contributes 11 test function(s) across 2 file(s) declaring at least one — every `def test…` in a file pytest or unittest would collect, which is those frameworks' own definition of a case; a parametrize table counts once, so this is a floor. Its tier split is read from file names and paths only.
D12 · Dependency Hygiene
1 outdated direct gem(s), 0 pinning defect(s). 3 declaration(s) graded against rubygems.org, 3 of them against a version resolved in a committed Gemfile.lock. Whether any of these gems is DEPRECATED or YANKED is not graded — rubygems.org publishes no deprecation marker, and a yank removes a version rather than flagging it. Whether any is UNMAINTAINED is not graded either: no registry publishes a maintenance status, and release age does not stand in for one. Whether any is UNUSED is a source question, not a registry one. Known CVEs in this dependency graph are D30's question, read from the manifest there.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 101 shipped gem(s) use a banned license. Licences were resolved from rubygems.org over the 101 gem(s) a consumer installs — this repository's runtime declarations closed transitively over its committed Gemfile.lock. Development-group and `add_development_dependency` gems are excluded: they are not distributed with this repository. 1 of them publish no licence on rubygems.org; that is missing data, not a violation, and none of them is charged. ★ COVERAGE OF THIS VERDICT: it grades this repository's gem dependencies and nothing else. The repository also declares a Gradle build (build.gradle/build.gradle.kts), and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
10 deducted task-comment markers across 15991 LoC (0.1/KLoC) → score 9.9. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 10 TodoComment finding(s) in Explicit Debt — start with Button.kt (2), IconButton.kt (2), HomeRepositoryImpl.kt. — One of this dimension's main actionable groups (10 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 49 document(s) read across 1 unit(s).
D26 · Project Cohesion
0 of 20 build units (Gradle) flagged as possibly oversized/incoherent.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
37 finding(s): 0 critical, 37 high, 0 medium, 0 low. 35 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 2 file(s) — `core/android/src/main/kotlin/dev/atick/core/extensions/NumberExtensions.kt`, `gradlew` (line 74, line 178) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
What to do
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 35 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 (35 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
No known-vulnerable dependencies in any ecosystem this repository declares.
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 101 of the 184 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
Strongest change-coupling: LibraryConventionPlugin.kt↔UiLibraryConventionPlugin.kt 80%; ApplicationConventionPlugin.kt↔UiLibraryConventionPlugin.kt 73%; ApplicationConventionPlugin.kt↔LibraryConventionPlugin.kt 70%
What to do
- Resolve the 2 Boundary-crossing change coupling finding(s) in Change Coupling — start with JetpackAppState.kt (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 2 Change coupling finding(s) in Change Coupling — start with AuthNavigation.kt (2). — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Change coupling clique finding(s) in Change Coupling — start with ApplicationConventionPlugin.kt. — One of this dimension's main actionable groups (1 warning-level).
D36 · Supply-chain Provenance & Signing
1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 2 platform declaration(s) and 77 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX4 · Dependency direction
AX8 · Test isolation
M1 · Documentation (README)
What to do
- Add a README to the 1 of 20 project(s) that lack one — worth up to 0.1 pts.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
P1 · CI/CD gates
P3 · Security & performance tooling
What to do
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
What to do
- Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
P6 · Release Hygiene
P7 · Outbound HTTP resilience
- `Retrofit.Builder(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — core/network/src/main/kotlin/dev/atick/core/network/di/retrofit/RetrofitModule.kt:54
What to do
- Set connect and read timeouts on every client (`RestTemplateBuilder.connectTimeout/readTimeout`, WebClient `responseTimeout`, `HttpRequest.Builder.timeout`, `HttpURLConnection.setReadTimeout`, Feign `connectTimeout`/`readTimeout` in configuration), and wrap calls to dependencies in resilience4j `@Retry`/`@CircuitBreaker`/`@TimeLimiter` (or Spring Retry).
PF1 · Benchmark discipline
PF3 · Async & latency hygiene
S1 · Web-Security Posture
- None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. This is reported because `firebase.json` configures this repository's static hosting, including its response headers, so the configuration that would carry these headers is in this repository and was read in full. (−2.0 on this card.) — firebase.json:1
What to do
- Set security response headers on the surface this repository serves: an `add_header` directive per header in the nginx/Caddy/Apache config, a `_headers` / `vercel.json` / `netlify.toml` entry for a static host, or `helmet()` in the HTTP server. `Content-Security-Policy` is the one that pays for itself first — it is what contains an injected script once one reaches the page — followed by `X-Content-Type-Options: nosniff` and a frame policy (`X-Frame-Options: DENY`, or CSP `frame-ancestors`). Where the app is served from a build container, the header configuration belongs in the image beside the built assets, so it ships with them rather than depending on where it lands.
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X20 · Mistyped argument guard
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
X30 · Support guard that admits what it rejects
X5 · Nullable reference types
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 99% | Exemplary | Strongest area. |
| Architecture | 92% | Exemplary | Solid. |
| Maturity | 81% | Exemplary | Solid. |
| Readiness | 65% | Adequate — gated by P7 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 77% | Adequate — gated by D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 94% | Exemplary | Solid. |
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 59 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: Dagger rejects, at compile time, a component that holds a binding with a narrower scope than its own.
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Kotlin code is a Spring, JSR-330 or CDI singleton bean. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no data at rest for these controls to protect.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named column (email, first_name, date_of_birth, phone_number, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~2935 lines of test source are present (.kt) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not included — the .kt suite was found but not re-run
- D16 Bus Factor — single-contributor repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D20 ADR Quality — N/A — this repo declares itself a template / kata / sample / demo; a formal ADR log is deferred to a real application built from it.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; Kotlin, Python not measured.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .kt, .py, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — symbol resolution incomplete — navigability not assessed
- 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) — 9 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (17 value object(s))
- 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 47 current-state document(s) make no claim of a kind M4 checks. 65 claim(s) of kinds M4 does not check were not checked (path 55, environment variable 10); M4 checks only links and versions and artefact counts.
- 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 (19 module(s), 151 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (JaCoCo XML — the Gradle `jacocoTestReport` task) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- 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.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X2 Cancellation propagation — no C# was loaded; this repository's Kotlin was read, and no request in it can be cancelled by a caller (Ktor, OkHttp's newCall or a URL stream, from a suspend function) — a Kotlin request outside a suspend function has no caller's cancellation to honour
- X24 Document value interpolated into markup unescaped — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Kotlin was read, and it logs through none that an assembled message defeats: Android's `Log` and Timber, java.util.logging and log4j-api-kotlin take one finished message (as log4net does in C#), or it makes no call through a named logger at all. Calls made through SLF4J, log4j 2 or kotlin-logging (`LoggerFactory.getLogger`, `KotlinLogging.logger {}`) would be judged.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 39 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Boundary-crossing change coupling: JetpackAppState.kt ↔ ProfileNavigation.kt app/src/main/kotlin/dev/atick/compose/ui/JetpackAppState.kt:1
- Boundary-crossing change coupling: JetpackAppState.kt ↔ AuthNavigation.kt app/src/main/kotlin/dev/atick/compose/ui/JetpackAppState.kt:1
- REDACTED
- REDACTED
Serious — 22 finding(s)
- TodoComment data/src/main/kotlin/dev/atick/data/repository/home/HomeRepositoryImpl.kt:53
- TodoComment core/ui/src/main/kotlin/dev/atick/core/ui/components/Button.kt:278
- TodoComment core/ui/src/main/kotlin/dev/atick/core/ui/components/Button.kt:282
- TodoComment core/ui/src/main/kotlin/dev/atick/core/ui/components/Chip.kt:148
- TodoComment core/ui/src/main/kotlin/dev/atick/core/ui/components/IconButton.kt:83
- TodoComment core/ui/src/main/kotlin/dev/atick/core/ui/components/IconButton.kt:110
- TodoComment core/ui/src/main/kotlin/dev/atick/core/ui/components/Tag.kt:120
- TodoComment core/room/src/main/kotlin/dev/atick/core/room/di/DatabaseModule.kt:66
- TodoComment core/android/src/main/kotlin/dev/atick/core/extensions/ContextExtensions.kt:270
- TodoComment build-logic/convention/src/main/kotlin/DokkaConventionPlugin.kt:37
- Change coupling: AuthNavigation.kt ↔ SignUpScreen.kt feature/auth/src/main/kotlin/dev/atick/feature/auth/navigation/AuthNavigation.kt:1
- Change coupling: AuthNavigation.kt ↔ SignInScreen.kt feature/auth/src/main/kotlin/dev/atick/feature/auth/navigation/AuthNavigation.kt:1
- NumberExtensionsKt.format (cognitive 16) core/android/src/main/kotlin/dev/atick/core/extensions/NumberExtensions.kt:50
- Change coupling clique: ApplicationConventionPlugin.kt, LibraryConventionPlugin.kt, UiLibraryConventionPlugin.kt build-logic/convention/src/main/kotlin/ApplicationConventionPlugin.kt
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (43 lines × 2) feature/auth/src/main/kotlin/dev/atick/feature/auth/ui/signin/SignInScreen.kt:193
- Duplicated block (30–31 lines × 2) feature/auth/src/main/kotlin/dev/atick/feature/auth/ui/signin/SignInScreen.kt:154
- Off the main sequence: Jetpack:core:navigation
- Outbound HTTP without resilience core/network/src/main/kotlin/dev/atick/core/network/di/retrofit/RetrofitModule.kt:54
Minor — 6 finding(s)
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No release approval gate
- No security response headers detected firebase.json:1
Minor — 1 finding(s)
- Outdated: fastlane
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-90ff00ab51f140f4b11cdd22b5ca663e/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-90ff00ab51f140f4b11cdd22b5ca663e/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 . | 37 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 9 file(s) — `core/android/src/main/kotlin/dev/atick/core/extensions/NumberExtensions.kt`, `core/navigation/src/main/kotlin/dev/atick/core/navigation/Navigator.kt`, `core/network/src/main/kotlin/dev/atick/core/network/di/RestApiModule.kt`, `core/network/src/main/kotlin/dev/atick/core/network/di/okhttp/OkHttpClientModule.kt`, `core/network/src/main/kotlin/dev/atick/core/network/di/retrofit/RetrofitModule.kt`, … (+4 more) — 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 | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |