Executive summary
zouhir96/hackertab-mobile falls short of our standard for production because the project has no automated tests and we found no logging, tracing or health checks in the code. It scores 33.0 out of 100 and is rated Weak, and 15 of its 31 critical findings are security problems in the build pipeline.
Production Readiness, at 16.3, is the weakest lens and counts most in the score. The best first step is adding automated tests, worth about 14.2 points. Adding a diagnostic log comes next, worth about 4.2 points. Raising Production Readiness to 70 would lift the score to about 46.6.
Nine pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Five secrets can leak from the build pipeline, and twelve buttons or links have no name a screen reader can say. Pinning each tool to an exact version, limiting each secret to its own step and naming the buttons and links would close these risks. Correcting the flagged pipeline settings would fix the weakness in the build pipeline's configuration. The control that only works with a mouse needs to work with the keyboard, or to become a real button.
The product code is 12,580 lines, about €12,000 to rebuild. The check for the health of its packages couldn't finish, so that result is missing, not a clean pass.
If Production Readiness rose from 16.3 to 70, the lowest score rated Strong, the score would rise from 33.0 to about 46.6.
Rebuild cost: about €12,000 · Estimate
| Cost to rebuild | €4,100 to €21,000, for 68 to 216 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 33. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 12,580 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 analytics.models | 2 database.entities | 3 design.components.buttons | 4 domain.common | 5 domain.models | 6 network.api | 7 com.zrcoding.hackertab | 8 analytics | 9 data.mappers | 10 data.repositories.AggregatedArticleRepositoryImpl | 11 data.repositories.SettingRepositoryImpl | 12 database.daos | 13 design.components | 14 design.components.buttons.ButtonSize | 15 design.components.cards | 16 design.theme | 17 domain.models.NetworkErrors | 18 domain.models.Profile | 19 domain.models.Resource | 20 domain.repositories | 21 domain.usecases.GetStartDestinationUseCase | 22 home.presentation.HomeViewModel | 23 analytics.impl | 24 bookmarks.presentation | 25 database | 26 domain.usecases | 27 home.presentation.HomeViewModel.FetchResult | 28 onboarding.profile | 29 onboarding.sources | 30 onboarding.topics | 31 settings.presentation.about | 32 settings.presentation.appearance | 33 settings.presentation.master | 34 settings.presentation.topics | 35 shared.navigation | 36 bookmarks.presentation.GroupBy | 37 data.repositories | 38 home.presentation | 39 settings.presentation.sources | 40 shared.app |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 analytics.models | ||||||||||||||||||||||||||||||||||||||||
| 2 database.entities | ||||||||||||||||||||||||||||||||||||||||
| 3 design.components.buttons | ||||||||||||||||||||||||||||||||||||||||
| 4 domain.common | ||||||||||||||||||||||||||||||||||||||||
| 5 domain.models | ||||||||||||||||||||||||||||||||||||||||
| 6 network.api | ||||||||||||||||||||||||||||||||||||||||
| 7 com.zrcoding.hackertab | 1 | |||||||||||||||||||||||||||||||||||||||
| 8 analytics | 3 | |||||||||||||||||||||||||||||||||||||||
| 9 data.mappers | 1 | 5 | ||||||||||||||||||||||||||||||||||||||
| 10 data.repositories.AggregatedArticleRepositoryImpl | 2 | |||||||||||||||||||||||||||||||||||||||
| 11 data.repositories.SettingRepositoryImpl | 1 | |||||||||||||||||||||||||||||||||||||||
| 12 database.daos | 1 | |||||||||||||||||||||||||||||||||||||||
| 13 design.components | 3 | |||||||||||||||||||||||||||||||||||||||
| 14 design.components.buttons.ButtonSize | 3 | |||||||||||||||||||||||||||||||||||||||
| 15 design.components.cards | 5 | |||||||||||||||||||||||||||||||||||||||
| 16 design.theme | 3 | |||||||||||||||||||||||||||||||||||||||
| 17 domain.models.NetworkErrors | 3 | |||||||||||||||||||||||||||||||||||||||
| 18 domain.models.Profile | 9 | |||||||||||||||||||||||||||||||||||||||
| 19 domain.models.Resource | 2 | |||||||||||||||||||||||||||||||||||||||
| 20 domain.repositories | 19 | |||||||||||||||||||||||||||||||||||||||
| 21 domain.usecases.GetStartDestinationUseCase | 1 | |||||||||||||||||||||||||||||||||||||||
| 22 home.presentation.HomeViewModel | 2 | |||||||||||||||||||||||||||||||||||||||
| 23 analytics.impl | 4 | 2 | ||||||||||||||||||||||||||||||||||||||
| 24 bookmarks.presentation | 4 | 1 | ||||||||||||||||||||||||||||||||||||||
| 25 database | 1 | |||||||||||||||||||||||||||||||||||||||
| 26 domain.usecases | 2 | 3 | 1 | |||||||||||||||||||||||||||||||||||||
| 27 home.presentation.HomeViewModel.FetchResult | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 28 onboarding.profile | 3 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 29 onboarding.sources | 1 | 3 | 1 | |||||||||||||||||||||||||||||||||||||
| 30 onboarding.topics | 2 | 1 | 3 | 1 | ||||||||||||||||||||||||||||||||||||
| 31 settings.presentation.about | 1 | |||||||||||||||||||||||||||||||||||||||
| 32 settings.presentation.appearance | 6 | 1 | ||||||||||||||||||||||||||||||||||||||
| 33 settings.presentation.master | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 34 settings.presentation.topics | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 35 shared.navigation | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 36 bookmarks.presentation.GroupBy | 3 | |||||||||||||||||||||||||||||||||||||||
| 37 data.repositories | 19 | 1 | 1 | 6 | 1 | |||||||||||||||||||||||||||||||||||
| 38 home.presentation | 11 | 1 | 3 | 1 | 2 | |||||||||||||||||||||||||||||||||||
| 39 settings.presentation.sources | 1 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 40 shared.app | 3 | 1 | 1 | 1 |
7→4 com.zrcoding.hackertab uses domain.common✕
- Connections
- 1 pair of types, where a type in com.zrcoding.hackertab uses a type in domain.common.
- The types involved
com.zrcoding.hackertab.AppConfigImpl→com.zrcoding.hackertab.domain.common.AppConfig
- Direction
- com.zrcoding.hackertab uses domain.common, so a change to domain.common can break com.zrcoding.hackertab, while a change to com.zrcoding.hackertab can't break domain.common.
- Position
- Below the diagonal: com.zrcoding.hackertab uses a module listed above it, which is the healthy direction.
8→1 analytics uses analytics.models✕
- Connections
- 3 pairs of types, where a type in analytics uses a type in analytics.models.
- The types involved
com.zrcoding.hackertab.analytics.AnalyticsHelper→com.zrcoding.hackertab.analytics.models.AnalyticsEventcom.zrcoding.hackertab.analytics.AnalyticsHelper→com.zrcoding.hackertab.analytics.models.UserPropertiescom.zrcoding.hackertab.analytics.AnalyticsHelperKt→com.zrcoding.hackertab.analytics.models.Param
- Direction
- analytics uses analytics.models, so a change to analytics.models can break analytics, while a change to analytics can't break analytics.models.
- Position
- Below the diagonal: analytics uses a module listed above it, which is the healthy direction.
9→2 data.mappers uses database.entities✕
- Connections
- 1 pair of types, where a type in data.mappers uses a type in database.entities.
- The types involved
com.zrcoding.hackertab.data.mappers.MappersKt→com.zrcoding.hackertab.database.entities.BookmarkedArticleEntity
- Direction
- data.mappers uses database.entities, so a change to database.entities can break data.mappers, while a change to data.mappers can't break database.entities.
- Position
- Below the diagonal: data.mappers uses a module listed above it, which is the healthy direction.
9→5 data.mappers uses domain.models✕
- Connections
- 5 pairs of types, where a type in data.mappers uses a type in domain.models.
- The types involved
com.zrcoding.hackertab.data.mappers.MappersKt→com.zrcoding.hackertab.domain.models.Articlecom.zrcoding.hackertab.data.mappers.MappersKt→com.zrcoding.hackertab.domain.models.BookmarkedArticlecom.zrcoding.hackertab.data.mappers.MappersKt→com.zrcoding.hackertab.domain.models.Conferencecom.zrcoding.hackertab.data.mappers.MappersKt→com.zrcoding.hackertab.domain.models.GithubRepocom.zrcoding.hackertab.data.mappers.MappersKt→com.zrcoding.hackertab.domain.models.ProductHunt
- Direction
- data.mappers uses domain.models, so a change to domain.models can break data.mappers, while a change to data.mappers can't break domain.models.
- Position
- Below the diagonal: data.mappers uses a module listed above it, which is the healthy direction.
10→5 data.repositories.AggregatedArticleRepositoryImpl uses domain.models✕
- Connections
- 2 pairs of types, where a type in data.repositories.AggregatedArticleRepositoryImpl uses a type in domain.models.
- The types involved
com.zrcoding.hackertab.data.repositories.AggregatedArticleRepositoryImpl.CacheKey→com.zrcoding.hackertab.domain.models.Sourcecom.zrcoding.hackertab.data.repositories.AggregatedArticleRepositoryImpl.Companion→com.zrcoding.hackertab.domain.models.Source
- Direction
- data.repositories.AggregatedArticleRepositoryImpl uses domain.models, so a change to domain.models can break data.repositories.AggregatedArticleRepositoryImpl, while a change to data.repositories.AggregatedArticleRepositoryImpl can't break domain.models.
- Position
- Below the diagonal: data.repositories.AggregatedArticleRepositoryImpl uses a module listed above it, which is the healthy direction.
11→5 data.repositories.SettingRepositoryImpl uses domain.models✕
- Connections
- 1 pair of types, where a type in data.repositories.SettingRepositoryImpl uses a type in domain.models.
- The types involved
com.zrcoding.hackertab.data.repositories.SettingRepositoryImpl.Companion→com.zrcoding.hackertab.domain.models.Topic
- Direction
- data.repositories.SettingRepositoryImpl uses domain.models, so a change to domain.models can break data.repositories.SettingRepositoryImpl, while a change to data.repositories.SettingRepositoryImpl can't break domain.models.
- Position
- Below the diagonal: data.repositories.SettingRepositoryImpl uses a module listed above it, which is the healthy direction.
12→2 database.daos uses database.entities✕
- Connections
- 1 pair of types, where a type in database.daos uses a type in database.entities.
- The types involved
com.zrcoding.hackertab.database.daos.BookmarkedArticleDao→com.zrcoding.hackertab.database.entities.BookmarkedArticleEntity
- Direction
- database.daos uses database.entities, so a change to database.entities can break database.daos, while a change to database.daos can't break database.entities.
- Position
- Below the diagonal: database.daos uses a module listed above it, which is the healthy direction.
13→5 design.components uses domain.models✕
- Connections
- 3 pairs of types, where a type in design.components uses a type in domain.models.
- The types involved
com.zrcoding.hackertab.design.components.SourceRailKt→com.zrcoding.hackertab.domain.models.Sourcecom.zrcoding.hackertab.design.components.SourceTagKt→com.zrcoding.hackertab.domain.models.Sourcecom.zrcoding.hackertab.design.components.TopicChipStripKt→com.zrcoding.hackertab.domain.models.Topic
- Direction
- design.components uses domain.models, so a change to domain.models can break design.components, while a change to design.components can't break domain.models.
- Position
- Below the diagonal: design.components uses a module listed above it, which is the healthy direction.
14→3 design.components.buttons.ButtonSize uses design.components.buttons✕
- Connections
- 3 pairs of types, where a type in design.components.buttons.ButtonSize uses a type in design.components.buttons.
- The types involved
com.zrcoding.hackertab.design.components.buttons.ButtonSize.Large→com.zrcoding.hackertab.design.components.buttons.ButtonSizecom.zrcoding.hackertab.design.components.buttons.ButtonSize.Medium→com.zrcoding.hackertab.design.components.buttons.ButtonSizecom.zrcoding.hackertab.design.components.buttons.ButtonSize.Small→com.zrcoding.hackertab.design.components.buttons.ButtonSize
- Direction
- design.components.buttons.ButtonSize uses design.components.buttons, so a change to design.components.buttons can break design.components.buttons.ButtonSize, while a change to design.components.buttons.ButtonSize can't break design.components.buttons.
- Position
- Below the diagonal: design.components.buttons.ButtonSize uses a module listed above it, which is the healthy direction.
15→5 design.components.cards uses domain.models✕
- Connections
- 5 pairs of types, where a type in design.components.cards uses a type in domain.models.
- The types involved
com.zrcoding.hackertab.design.components.cards.ArticleCardKt→com.zrcoding.hackertab.domain.models.Articlecom.zrcoding.hackertab.design.components.cards.BookmarkCardKt→com.zrcoding.hackertab.domain.models.BookmarkedArticlecom.zrcoding.hackertab.design.components.cards.ConferenceCardKt→com.zrcoding.hackertab.domain.models.Conferencecom.zrcoding.hackertab.design.components.cards.LaunchCardKt→com.zrcoding.hackertab.domain.models.ProductHuntcom.zrcoding.hackertab.design.components.cards.RepoCardKt→com.zrcoding.hackertab.domain.models.GithubRepo
- Direction
- design.components.cards uses domain.models, so a change to domain.models can break design.components.cards, while a change to design.components.cards can't break domain.models.
- Position
- Below the diagonal: design.components.cards uses a module listed above it, which is the healthy direction.
16→5 design.theme uses domain.models✕
- Connections
- 3 pairs of types, where a type in design.theme uses a type in domain.models.
- The types involved
com.zrcoding.hackertab.design.theme.ThemeKt→com.zrcoding.hackertab.domain.models.ThemeFontcom.zrcoding.hackertab.design.theme.ThemeKt→com.zrcoding.hackertab.domain.models.ThemeModecom.zrcoding.hackertab.design.theme.ThemeKt→com.zrcoding.hackertab.domain.models.ThemePalette
- Direction
- design.theme uses domain.models, so a change to domain.models can break design.theme, while a change to design.theme can't break domain.models.
- Position
- Below the diagonal: design.theme uses a module listed above it, which is the healthy direction.
17→5 domain.models.NetworkErrors uses domain.models✕
- Connections
- 3 pairs of types, where a type in domain.models.NetworkErrors uses a type in domain.models.
- The types involved
com.zrcoding.hackertab.domain.models.NetworkErrors.NO_INTERNET→com.zrcoding.hackertab.domain.models.NetworkErrorscom.zrcoding.hackertab.domain.models.NetworkErrors.REQUEST_TIMEOUT→com.zrcoding.hackertab.domain.models.NetworkErrorscom.zrcoding.hackertab.domain.models.NetworkErrors.UNKNOWN→com.zrcoding.hackertab.domain.models.NetworkErrors
- Direction
- domain.models.NetworkErrors uses domain.models, so a change to domain.models can break domain.models.NetworkErrors, while a change to domain.models.NetworkErrors can't break domain.models.
- Position
- Below the diagonal: domain.models.NetworkErrors uses a module listed above it, which is the healthy direction.
18→5 domain.models.Profile uses domain.models✕
- Connections
- 9 pairs of types, where a type in domain.models.Profile uses a type in domain.models.
- The types involved
com.zrcoding.hackertab.domain.models.Profile.BACKEND_ENGINEER→com.zrcoding.hackertab.domain.models.Profilecom.zrcoding.hackertab.domain.models.Profile.DATA_ENGINEER→com.zrcoding.hackertab.domain.models.Profilecom.zrcoding.hackertab.domain.models.Profile.DEVOPS_ENGINEER→com.zrcoding.hackertab.domain.models.Profilecom.zrcoding.hackertab.domain.models.Profile.FRONTEND_ENGINEER→com.zrcoding.hackertab.domain.models.Profilecom.zrcoding.hackertab.domain.models.Profile.FULL_STACK_ENGINEER→com.zrcoding.hackertab.domain.models.Profilecom.zrcoding.hackertab.domain.models.Profile.ML_ENGINEER→com.zrcoding.hackertab.domain.models.Profilecom.zrcoding.hackertab.domain.models.Profile.MOBILE_ENGINEER→com.zrcoding.hackertab.domain.models.Profilecom.zrcoding.hackertab.domain.models.Profile.OTHER→com.zrcoding.hackertab.domain.models.Profilecom.zrcoding.hackertab.domain.models.Profile.SECURITY_ENGINEER→com.zrcoding.hackertab.domain.models.Profile
- Direction
- domain.models.Profile uses domain.models, so a change to domain.models can break domain.models.Profile, while a change to domain.models.Profile can't break domain.models.
- Position
- Below the diagonal: domain.models.Profile uses a module listed above it, which is the healthy direction.
19→5 domain.models.Resource uses domain.models✕
- Connections
- 2 pairs of types, where a type in domain.models.Resource uses a type in domain.models.
- The types involved
com.zrcoding.hackertab.domain.models.Resource.Failure→com.zrcoding.hackertab.domain.models.Resourcecom.zrcoding.hackertab.domain.models.Resource.Success→com.zrcoding.hackertab.domain.models.Resource
- Direction
- domain.models.Resource uses domain.models, so a change to domain.models can break domain.models.Resource, while a change to domain.models.Resource can't break domain.models.
- Position
- Below the diagonal: domain.models.Resource uses a module listed above it, which is the healthy direction.
20→5 domain.repositories uses domain.models✕
- Connections
- 19 pairs of types, where a type in domain.repositories uses a type in domain.models.
- The types involved
com.zrcoding.hackertab.domain.repositories.AggregatedArticleRepository→com.zrcoding.hackertab.domain.models.Sourcecom.zrcoding.hackertab.domain.repositories.AggregatedArticleRepository→com.zrcoding.hackertab.domain.models.Topiccom.zrcoding.hackertab.domain.repositories.AggregatedFeedResult→com.zrcoding.hackertab.domain.models.BaseArticlecom.zrcoding.hackertab.domain.repositories.AggregatedFeedResult→com.zrcoding.hackertab.domain.models.Sourcecom.zrcoding.hackertab.domain.repositories.AggregatedFeedResult→com.zrcoding.hackertab.domain.models.SourceLoadStatecom.zrcoding.hackertab.domain.repositories.ArticleRepository→com.zrcoding.hackertab.domain.models.Articlecom.zrcoding.hackertab.domain.repositories.ArticleRepository→com.zrcoding.hackertab.domain.models.Conferencecom.zrcoding.hackertab.domain.repositories.ArticleRepository→com.zrcoding.hackertab.domain.models.GithubRepocom.zrcoding.hackertab.domain.repositories.ArticleRepository→com.zrcoding.hackertab.domain.models.NetworkErrorscom.zrcoding.hackertab.domain.repositories.ArticleRepository→com.zrcoding.hackertab.domain.models.ProductHuntcom.zrcoding.hackertab.domain.repositories.ArticleRepository→com.zrcoding.hackertab.domain.models.Resourcecom.zrcoding.hackertab.domain.repositories.ArticleRepository→com.zrcoding.hackertab.domain.models.Sourcecom.zrcoding.hackertab.domain.repositories.BookmarkRepository→com.zrcoding.hackertab.domain.models.BaseArticlecom.zrcoding.hackertab.domain.repositories.BookmarkRepository→com.zrcoding.hackertab.domain.models.BookmarkedArticlecom.zrcoding.hackertab.domain.repositories.SettingRepository→com.zrcoding.hackertab.domain.models.Profilecom.zrcoding.hackertab.domain.repositories.SettingRepository→com.zrcoding.hackertab.domain.models.ThemeFontcom.zrcoding.hackertab.domain.repositories.SettingRepository→com.zrcoding.hackertab.domain.models.ThemeModecom.zrcoding.hackertab.domain.repositories.SettingRepository→com.zrcoding.hackertab.domain.models.ThemePalettecom.zrcoding.hackertab.domain.repositories.SettingRepository→com.zrcoding.hackertab.domain.models.Topic
- Direction
- domain.repositories uses domain.models, so a change to domain.models can break domain.repositories, while a change to domain.repositories can't break domain.models.
- Position
- Below the diagonal: domain.repositories uses a module listed above it, which is the healthy direction.
21→5 domain.usecases.GetStartDestinationUseCase uses domain.models✕
- Connections
- 1 pair of types, where a type in domain.usecases.GetStartDestinationUseCase uses a type in domain.models.
- The types involved
com.zrcoding.hackertab.domain.usecases.GetStartDestinationUseCase.Result→com.zrcoding.hackertab.domain.models.Profile
- Direction
- domain.usecases.GetStartDestinationUseCase uses domain.models, so a change to domain.models can break domain.usecases.GetStartDestinationUseCase, while a change to domain.usecases.GetStartDestinationUseCase can't break domain.models.
- Position
- Below the diagonal: domain.usecases.GetStartDestinationUseCase uses a module listed above it, which is the healthy direction.
22→5 home.presentation.HomeViewModel uses domain.models✕
- Connections
- 2 pairs of types, where a type in home.presentation.HomeViewModel uses a type in domain.models.
- The types involved
com.zrcoding.hackertab.home.presentation.HomeViewModel.FetchParams→com.zrcoding.hackertab.domain.models.Sourcecom.zrcoding.hackertab.home.presentation.HomeViewModel.FetchParams→com.zrcoding.hackertab.domain.models.Topic
- Direction
- home.presentation.HomeViewModel uses domain.models, so a change to domain.models can break home.presentation.HomeViewModel, while a change to home.presentation.HomeViewModel can't break domain.models.
- Position
- Below the diagonal: home.presentation.HomeViewModel uses a module listed above it, which is the healthy direction.
23→1 analytics.impl uses analytics.models✕
- Connections
- 4 pairs of types, where a type in analytics.impl uses a type in analytics.models.
- The types involved
com.zrcoding.hackertab.analytics.impl.AnalyticsHelperImpl→com.zrcoding.hackertab.analytics.models.AnalyticsEventcom.zrcoding.hackertab.analytics.impl.AnalyticsHelperImpl→com.zrcoding.hackertab.analytics.models.UserPropertiescom.zrcoding.hackertab.analytics.impl.AnalyticsHelperStubImpl→com.zrcoding.hackertab.analytics.models.AnalyticsEventcom.zrcoding.hackertab.analytics.impl.AnalyticsHelperStubImpl→com.zrcoding.hackertab.analytics.models.UserProperties
- Direction
- analytics.impl uses analytics.models, so a change to analytics.models can break analytics.impl, while a change to analytics.impl can't break analytics.models.
- Position
- Below the diagonal: analytics.impl uses a module listed above it, which is the healthy direction.
23→8 analytics.impl uses analytics✕
- Connections
- 2 pairs of types, where a type in analytics.impl uses a type in analytics.
- The types involved
com.zrcoding.hackertab.analytics.impl.AnalyticsHelperImpl→com.zrcoding.hackertab.analytics.AnalyticsHelpercom.zrcoding.hackertab.analytics.impl.AnalyticsHelperStubImpl→com.zrcoding.hackertab.analytics.AnalyticsHelper
- Direction
- analytics.impl uses analytics, so a change to analytics can break analytics.impl, while a change to analytics.impl can't break analytics.
- Position
- Below the diagonal: analytics.impl uses a module listed above it, which is the healthy direction.
24→5 bookmarks.presentation uses domain.models✕
- Connections
- 4 pairs of types, where a type in bookmarks.presentation uses a type in domain.models.
- The types involved
com.zrcoding.hackertab.bookmarks.presentation.BookmarksScreenKt→com.zrcoding.hackertab.domain.models.BookmarkedArticlecom.zrcoding.hackertab.bookmarks.presentation.BookmarksSearchScreenKt→com.zrcoding.hackertab.domain.models.BookmarkedArticlecom.zrcoding.hackertab.bookmarks.presentation.BookmarksViewModel→com.zrcoding.hackertab.domain.models.BookmarkedArticlecom.zrcoding.hackertab.bookmarks.presentation.BookmarksViewState→com.zrcoding.hackertab.domain.models.BookmarkedArticle
- Direction
- bookmarks.presentation uses domain.models, so a change to domain.models can break bookmarks.presentation, while a change to bookmarks.presentation can't break domain.models.
- Position
- Below the diagonal: bookmarks.presentation uses a module listed above it, which is the healthy direction.
24→20 bookmarks.presentation uses domain.repositories✕
- Connections
- 1 pair of types, where a type in bookmarks.presentation uses a type in domain.repositories.
- The types involved
com.zrcoding.hackertab.bookmarks.presentation.BookmarksViewModel→com.zrcoding.hackertab.domain.repositories.BookmarkRepository
- Direction
- bookmarks.presentation uses domain.repositories, so a change to domain.repositories can break bookmarks.presentation, while a change to bookmarks.presentation can't break domain.repositories.
- Position
- Below the diagonal: bookmarks.presentation uses a module listed above it, which is the healthy direction.
25→12 database uses database.daos✕
- Connections
- 1 pair of types, where a type in database uses a type in database.daos.
- The types involved
com.zrcoding.hackertab.database.AppDatabase→com.zrcoding.hackertab.database.daos.BookmarkedArticleDao
- Direction
- database uses database.daos, so a change to database.daos can break database, while a change to database can't break database.daos.
- Position
- Below the diagonal: database uses a module listed above it, which is the healthy direction.
26→5 domain.usecases uses domain.models✕
- Connections
- 2 pairs of types, where a type in domain.usecases uses a type in domain.models.
- The types involved
com.zrcoding.hackertab.domain.usecases.ObserveSelectedSourcesUseCase→com.zrcoding.hackertab.domain.models.Sourcecom.zrcoding.hackertab.domain.usecases.ObserveSelectedTopicsUseCase→com.zrcoding.hackertab.domain.models.Topic
- Direction
- domain.usecases uses domain.models, so a change to domain.models can break domain.usecases, while a change to domain.usecases can't break domain.models.
- Position
- Below the diagonal: domain.usecases uses a module listed above it, which is the healthy direction.
26→20 domain.usecases uses domain.repositories✕
- Connections
- 3 pairs of types, where a type in domain.usecases uses a type in domain.repositories.
- The types involved
com.zrcoding.hackertab.domain.usecases.GetStartDestinationUseCase→com.zrcoding.hackertab.domain.repositories.SettingRepositorycom.zrcoding.hackertab.domain.usecases.ObserveSelectedSourcesUseCase→com.zrcoding.hackertab.domain.repositories.SettingRepositorycom.zrcoding.hackertab.domain.usecases.ObserveSelectedTopicsUseCase→com.zrcoding.hackertab.domain.repositories.SettingRepository
- Direction
- domain.usecases uses domain.repositories, so a change to domain.repositories can break domain.usecases, while a change to domain.usecases can't break domain.repositories.
- Position
- Below the diagonal: domain.usecases uses a module listed above it, which is the healthy direction.
26→21 domain.usecases uses domain.usecases.GetStartDestinationUseCase✕
- Connections
- 1 pair of types, where a type in domain.usecases uses a type in domain.usecases.GetStartDestinationUseCase.
- The types involved
com.zrcoding.hackertab.domain.usecases.GetStartDestinationUseCase→com.zrcoding.hackertab.domain.usecases.GetStartDestinationUseCase.Result
- Direction
- domain.usecases uses domain.usecases.GetStartDestinationUseCase, so a change to domain.usecases.GetStartDestinationUseCase can break domain.usecases, while a change to domain.usecases can't break domain.usecases.GetStartDestinationUseCase.
- Position
- Below the diagonal: domain.usecases uses a module listed above it, which is the healthy direction.
27→5 home.presentation.HomeViewModel.FetchResult uses domain.models✕
- Connections
- 1 pair of types, where a type in home.presentation.HomeViewModel.FetchResult uses a type in domain.models.
- The types involved
com.zrcoding.hackertab.home.presentation.HomeViewModel.FetchResult.Success→com.zrcoding.hackertab.domain.models.BaseArticle
- Direction
- home.presentation.HomeViewModel.FetchResult uses domain.models, so a change to domain.models can break home.presentation.HomeViewModel.FetchResult, while a change to home.presentation.HomeViewModel.FetchResult can't break domain.models.
- Position
- Below the diagonal: home.presentation.HomeViewModel.FetchResult uses a module listed above it, which is the healthy direction.
27→22 home.presentation.HomeViewModel.FetchResult uses home.presentation.HomeViewModel✕
- Connections
- 2 pairs of types, where a type in home.presentation.HomeViewModel.FetchResult uses a type in home.presentation.HomeViewModel.
- The types involved
com.zrcoding.hackertab.home.presentation.HomeViewModel.FetchResult.Failure→com.zrcoding.hackertab.home.presentation.HomeViewModel.FetchResultcom.zrcoding.hackertab.home.presentation.HomeViewModel.FetchResult.Success→com.zrcoding.hackertab.home.presentation.HomeViewModel.FetchResult
- Direction
- home.presentation.HomeViewModel.FetchResult uses home.presentation.HomeViewModel, so a change to home.presentation.HomeViewModel can break home.presentation.HomeViewModel.FetchResult, while a change to home.presentation.HomeViewModel.FetchResult can't break home.presentation.HomeViewModel.
- Position
- Below the diagonal: home.presentation.HomeViewModel.FetchResult uses a module listed above it, which is the healthy direction.
28→5 onboarding.profile uses domain.models✕
- Connections
- 3 pairs of types, where a type in onboarding.profile uses a type in domain.models.
- The types involved
com.zrcoding.hackertab.onboarding.profile.SetupProfileScreenKt→com.zrcoding.hackertab.domain.models.Profilecom.zrcoding.hackertab.onboarding.profile.SetupProfileViewModel→com.zrcoding.hackertab.domain.models.Profilecom.zrcoding.hackertab.onboarding.profile.SetupProfileViewState→com.zrcoding.hackertab.domain.models.Profile
- Direction
- onboarding.profile uses domain.models, so a change to domain.models can break onboarding.profile, while a change to onboarding.profile can't break domain.models.
- Position
- Below the diagonal: onboarding.profile uses a module listed above it, which is the healthy direction.
28→8 onboarding.profile uses analytics✕
- Connections
- 1 pair of types, where a type in onboarding.profile uses a type in analytics.
- The types involved
com.zrcoding.hackertab.onboarding.profile.SetupProfileViewModel→com.zrcoding.hackertab.analytics.AnalyticsHelper
- Direction
- onboarding.profile uses analytics, so a change to analytics can break onboarding.profile, while a change to onboarding.profile can't break analytics.
- Position
- Below the diagonal: onboarding.profile uses a module listed above it, which is the healthy direction.
28→20 onboarding.profile uses domain.repositories✕
- Connections
- 1 pair of types, where a type in onboarding.profile uses a type in domain.repositories.
- The types involved
com.zrcoding.hackertab.onboarding.profile.SetupProfileViewModel→com.zrcoding.hackertab.domain.repositories.SettingRepository
- Direction
- onboarding.profile uses domain.repositories, so a change to domain.repositories can break onboarding.profile, while a change to onboarding.profile can't break domain.repositories.
- Position
- Below the diagonal: onboarding.profile uses a module listed above it, which is the healthy direction.
29→8 onboarding.sources uses analytics✕
- Connections
- 1 pair of types, where a type in onboarding.sources uses a type in analytics.
- The types involved
com.zrcoding.hackertab.onboarding.sources.SetupSourcesViewModel→com.zrcoding.hackertab.analytics.AnalyticsHelper
- Direction
- onboarding.sources uses analytics, so a change to analytics can break onboarding.sources, while a change to onboarding.sources can't break analytics.
- Position
- Below the diagonal: onboarding.sources uses a module listed above it, which is the healthy direction.
29→13 onboarding.sources uses design.components✕
- Connections
- 3 pairs of types, where a type in onboarding.sources uses a type in design.components.
- The types involved
com.zrcoding.hackertab.onboarding.sources.SetupSourcesScreenKt→com.zrcoding.hackertab.design.components.ChipDatacom.zrcoding.hackertab.onboarding.sources.SetupSourcesViewModel→com.zrcoding.hackertab.design.components.ChipDatacom.zrcoding.hackertab.onboarding.sources.SetupSourcesViewState→com.zrcoding.hackertab.design.components.ChipData
- Direction
- onboarding.sources uses design.components, so a change to design.components can break onboarding.sources, while a change to onboarding.sources can't break design.components.
- Position
- Below the diagonal: onboarding.sources uses a module listed above it, which is the healthy direction.
29→20 onboarding.sources uses domain.repositories✕
- Connections
- 1 pair of types, where a type in onboarding.sources uses a type in domain.repositories.
- The types involved
com.zrcoding.hackertab.onboarding.sources.SetupSourcesViewModel→com.zrcoding.hackertab.domain.repositories.SettingRepository
- Direction
- onboarding.sources uses domain.repositories, so a change to domain.repositories can break onboarding.sources, while a change to onboarding.sources can't break domain.repositories.
- Position
- Below the diagonal: onboarding.sources uses a module listed above it, which is the healthy direction.
30→5 onboarding.topics uses domain.models✕
- Connections
- 2 pairs of types, where a type in onboarding.topics uses a type in domain.models.
- The types involved
com.zrcoding.hackertab.onboarding.topics.SetupTopicsScreenKt→com.zrcoding.hackertab.domain.models.Profilecom.zrcoding.hackertab.onboarding.topics.SetupTopicsViewModel→com.zrcoding.hackertab.domain.models.Profile
- Direction
- onboarding.topics uses domain.models, so a change to domain.models can break onboarding.topics, while a change to onboarding.topics can't break domain.models.
- Position
- Below the diagonal: onboarding.topics uses a module listed above it, which is the healthy direction.
30→8 onboarding.topics uses analytics✕
- Connections
- 1 pair of types, where a type in onboarding.topics uses a type in analytics.
- The types involved
com.zrcoding.hackertab.onboarding.topics.SetupTopicsViewModel→com.zrcoding.hackertab.analytics.AnalyticsHelper
- Direction
- onboarding.topics uses analytics, so a change to analytics can break onboarding.topics, while a change to onboarding.topics can't break analytics.
- Position
- Below the diagonal: onboarding.topics uses a module listed above it, which is the healthy direction.
30→13 onboarding.topics uses design.components✕
- Connections
- 3 pairs of types, where a type in onboarding.topics uses a type in design.components.
- The types involved
com.zrcoding.hackertab.onboarding.topics.SetupTopicsScreenKt→com.zrcoding.hackertab.design.components.ChipDatacom.zrcoding.hackertab.onboarding.topics.SetupTopicsViewModel→com.zrcoding.hackertab.design.components.ChipDatacom.zrcoding.hackertab.onboarding.topics.SetupTopicsViewState→com.zrcoding.hackertab.design.components.ChipData
- Direction
- onboarding.topics uses design.components, so a change to design.components can break onboarding.topics, while a change to onboarding.topics can't break design.components.
- Position
- Below the diagonal: onboarding.topics uses a module listed above it, which is the healthy direction.
30→20 onboarding.topics uses domain.repositories✕
- Connections
- 1 pair of types, where a type in onboarding.topics uses a type in domain.repositories.
- The types involved
com.zrcoding.hackertab.onboarding.topics.SetupTopicsViewModel→com.zrcoding.hackertab.domain.repositories.SettingRepository
- Direction
- onboarding.topics uses domain.repositories, so a change to domain.repositories can break onboarding.topics, while a change to onboarding.topics can't break domain.repositories.
- Position
- Below the diagonal: onboarding.topics uses a module listed above it, which is the healthy direction.
31→20 settings.presentation.about uses domain.repositories✕
- Connections
- 1 pair of types, where a type in settings.presentation.about uses a type in domain.repositories.
- The types involved
com.zrcoding.hackertab.settings.presentation.about.SettingsAboutViewModel→com.zrcoding.hackertab.domain.repositories.SettingRepository
- Direction
- settings.presentation.about uses domain.repositories, so a change to domain.repositories can break settings.presentation.about, while a change to settings.presentation.about can't break domain.repositories.
- Position
- Below the diagonal: settings.presentation.about uses a module listed above it, which is the healthy direction.
32→5 settings.presentation.appearance uses domain.models✕
- Connections
- 6 pairs of types, where a type in settings.presentation.appearance uses a type in domain.models.
- The types involved
com.zrcoding.hackertab.settings.presentation.appearance.SettingsAppearanceScreenKt→com.zrcoding.hackertab.domain.models.ThemeFontcom.zrcoding.hackertab.settings.presentation.appearance.SettingsAppearanceScreenKt→com.zrcoding.hackertab.domain.models.ThemeModecom.zrcoding.hackertab.settings.presentation.appearance.SettingsAppearanceScreenKt→com.zrcoding.hackertab.domain.models.ThemePalettecom.zrcoding.hackertab.settings.presentation.appearance.SettingsAppearanceViewModel→com.zrcoding.hackertab.domain.models.ThemeFontcom.zrcoding.hackertab.settings.presentation.appearance.SettingsAppearanceViewModel→com.zrcoding.hackertab.domain.models.ThemeModecom.zrcoding.hackertab.settings.presentation.appearance.SettingsAppearanceViewModel→com.zrcoding.hackertab.domain.models.ThemePalette
- Direction
- settings.presentation.appearance uses domain.models, so a change to domain.models can break settings.presentation.appearance, while a change to settings.presentation.appearance can't break domain.models.
- Position
- Below the diagonal: settings.presentation.appearance uses a module listed above it, which is the healthy direction.
32→20 settings.presentation.appearance uses domain.repositories✕
- Connections
- 1 pair of types, where a type in settings.presentation.appearance uses a type in domain.repositories.
- The types involved
com.zrcoding.hackertab.settings.presentation.appearance.SettingsAppearanceViewModel→com.zrcoding.hackertab.domain.repositories.SettingRepository
- Direction
- settings.presentation.appearance uses domain.repositories, so a change to domain.repositories can break settings.presentation.appearance, while a change to settings.presentation.appearance can't break domain.repositories.
- Position
- Below the diagonal: settings.presentation.appearance uses a module listed above it, which is the healthy direction.
33→5 settings.presentation.master uses domain.models✕
- Connections
- 3 pairs of types, where a type in settings.presentation.master uses a type in domain.models.
- The types involved
com.zrcoding.hackertab.settings.presentation.master.SettingsMasterScreenKt→com.zrcoding.hackertab.domain.models.Profilecom.zrcoding.hackertab.settings.presentation.master.SettingsMasterUiState→com.zrcoding.hackertab.domain.models.Profilecom.zrcoding.hackertab.settings.presentation.master.SettingsMasterUiState→com.zrcoding.hackertab.domain.models.ThemeMode
- Direction
- settings.presentation.master uses domain.models, so a change to domain.models can break settings.presentation.master, while a change to settings.presentation.master can't break domain.models.
- Position
- Below the diagonal: settings.presentation.master uses a module listed above it, which is the healthy direction.
33→20 settings.presentation.master uses domain.repositories✕
- Connections
- 1 pair of types, where a type in settings.presentation.master uses a type in domain.repositories.
- The types involved
com.zrcoding.hackertab.settings.presentation.master.SettingsMasterViewModel→com.zrcoding.hackertab.domain.repositories.SettingRepository
- Direction
- settings.presentation.master uses domain.repositories, so a change to domain.repositories can break settings.presentation.master, while a change to settings.presentation.master can't break domain.repositories.
- Position
- Below the diagonal: settings.presentation.master uses a module listed above it, which is the healthy direction.
34→8 settings.presentation.topics uses analytics✕
- Connections
- 1 pair of types, where a type in settings.presentation.topics uses a type in analytics.
- The types involved
com.zrcoding.hackertab.settings.presentation.topics.SettingTopicsViewModel→com.zrcoding.hackertab.analytics.AnalyticsHelper
- Direction
- settings.presentation.topics uses analytics, so a change to analytics can break settings.presentation.topics, while a change to settings.presentation.topics can't break analytics.
- Position
- Below the diagonal: settings.presentation.topics uses a module listed above it, which is the healthy direction.
34→13 settings.presentation.topics uses design.components✕
- Connections
- 1 pair of types, where a type in settings.presentation.topics uses a type in design.components.
- The types involved
com.zrcoding.hackertab.settings.presentation.topics.SettingTopicsViewModel→com.zrcoding.hackertab.design.components.ChipData
- Direction
- settings.presentation.topics uses design.components, so a change to design.components can break settings.presentation.topics, while a change to settings.presentation.topics can't break design.components.
- Position
- Below the diagonal: settings.presentation.topics uses a module listed above it, which is the healthy direction.
34→20 settings.presentation.topics uses domain.repositories✕
- Connections
- 1 pair of types, where a type in settings.presentation.topics uses a type in domain.repositories.
- The types involved
com.zrcoding.hackertab.settings.presentation.topics.SettingTopicsViewModel→com.zrcoding.hackertab.domain.repositories.SettingRepository
- Direction
- settings.presentation.topics uses domain.repositories, so a change to domain.repositories can break settings.presentation.topics, while a change to settings.presentation.topics can't break domain.repositories.
- Position
- Below the diagonal: settings.presentation.topics uses a module listed above it, which is the healthy direction.
35→5 shared.navigation uses domain.models✕
- Connections
- 1 pair of types, where a type in shared.navigation uses a type in domain.models.
- The types involved
com.zrcoding.hackertab.shared.navigation.SetupTopicsScreen→com.zrcoding.hackertab.domain.models.Profile
- Direction
- shared.navigation uses domain.models, so a change to domain.models can break shared.navigation, while a change to shared.navigation can't break domain.models.
- Position
- Below the diagonal: shared.navigation uses a module listed above it, which is the healthy direction.
35→13 shared.navigation uses design.components✕
- Connections
- 1 pair of types, where a type in shared.navigation uses a type in design.components.
- The types involved
com.zrcoding.hackertab.shared.navigation.MainNavHostKt→com.zrcoding.hackertab.design.components.BottomNavItem
- Direction
- shared.navigation uses design.components, so a change to design.components can break shared.navigation, while a change to shared.navigation can't break design.components.
- Position
- Below the diagonal: shared.navigation uses a module listed above it, which is the healthy direction.
35→21 shared.navigation uses domain.usecases.GetStartDestinationUseCase✕
- Connections
- 1 pair of types, where a type in shared.navigation uses a type in domain.usecases.GetStartDestinationUseCase.
- The types involved
com.zrcoding.hackertab.shared.navigation.MainNavHostKt→com.zrcoding.hackertab.domain.usecases.GetStartDestinationUseCase.Result
- Direction
- shared.navigation uses domain.usecases.GetStartDestinationUseCase, so a change to domain.usecases.GetStartDestinationUseCase can break shared.navigation, while a change to shared.navigation can't break domain.usecases.GetStartDestinationUseCase.
- Position
- Below the diagonal: shared.navigation uses a module listed above it, which is the healthy direction.
36→24 bookmarks.presentation.GroupBy uses bookmarks.presentation✕
- Connections
- 3 pairs of types, where a type in bookmarks.presentation.GroupBy uses a type in bookmarks.presentation.
- The types involved
com.zrcoding.hackertab.bookmarks.presentation.GroupBy.ALL→com.zrcoding.hackertab.bookmarks.presentation.GroupBycom.zrcoding.hackertab.bookmarks.presentation.GroupBy.BY_DATE→com.zrcoding.hackertab.bookmarks.presentation.GroupBycom.zrcoding.hackertab.bookmarks.presentation.GroupBy.BY_SOURCE→com.zrcoding.hackertab.bookmarks.presentation.GroupBy
- Direction
- bookmarks.presentation.GroupBy uses bookmarks.presentation, so a change to bookmarks.presentation can break bookmarks.presentation.GroupBy, while a change to bookmarks.presentation.GroupBy can't break bookmarks.presentation.
- Position
- Below the diagonal: bookmarks.presentation.GroupBy uses a module listed above it, which is the healthy direction.
37→5 data.repositories uses domain.models✕
- Connections
- 19 pairs of types, where a type in data.repositories uses a type in domain.models.
- The types involved
com.zrcoding.hackertab.data.repositories.AggregatedArticleRepositoryImpl→com.zrcoding.hackertab.domain.models.BaseArticlecom.zrcoding.hackertab.data.repositories.AggregatedArticleRepositoryImpl→com.zrcoding.hackertab.domain.models.NetworkErrorscom.zrcoding.hackertab.data.repositories.AggregatedArticleRepositoryImpl→com.zrcoding.hackertab.domain.models.Resourcecom.zrcoding.hackertab.data.repositories.AggregatedArticleRepositoryImpl→com.zrcoding.hackertab.domain.models.Sourcecom.zrcoding.hackertab.data.repositories.AggregatedArticleRepositoryImpl→com.zrcoding.hackertab.domain.models.Topiccom.zrcoding.hackertab.data.repositories.ArticleRepositoryImpl→com.zrcoding.hackertab.domain.models.Articlecom.zrcoding.hackertab.data.repositories.ArticleRepositoryImpl→com.zrcoding.hackertab.domain.models.Conferencecom.zrcoding.hackertab.data.repositories.ArticleRepositoryImpl→com.zrcoding.hackertab.domain.models.GithubRepocom.zrcoding.hackertab.data.repositories.ArticleRepositoryImpl→com.zrcoding.hackertab.domain.models.NetworkErrorscom.zrcoding.hackertab.data.repositories.ArticleRepositoryImpl→com.zrcoding.hackertab.domain.models.ProductHuntcom.zrcoding.hackertab.data.repositories.ArticleRepositoryImpl→com.zrcoding.hackertab.domain.models.Resourcecom.zrcoding.hackertab.data.repositories.ArticleRepositoryImpl→com.zrcoding.hackertab.domain.models.Sourcecom.zrcoding.hackertab.data.repositories.BookmarkRepositoryImpl→com.zrcoding.hackertab.domain.models.BaseArticlecom.zrcoding.hackertab.data.repositories.BookmarkRepositoryImpl→com.zrcoding.hackertab.domain.models.BookmarkedArticlecom.zrcoding.hackertab.data.repositories.SettingRepositoryImpl→com.zrcoding.hackertab.domain.models.Profilecom.zrcoding.hackertab.data.repositories.SettingRepositoryImpl→com.zrcoding.hackertab.domain.models.ThemeFontcom.zrcoding.hackertab.data.repositories.SettingRepositoryImpl→com.zrcoding.hackertab.domain.models.ThemeModecom.zrcoding.hackertab.data.repositories.SettingRepositoryImpl→com.zrcoding.hackertab.domain.models.ThemePalettecom.zrcoding.hackertab.data.repositories.SettingRepositoryImpl→com.zrcoding.hackertab.domain.models.Topic
- Direction
- data.repositories uses domain.models, so a change to domain.models can break data.repositories, while a change to data.repositories can't break domain.models.
- Position
- Below the diagonal: data.repositories uses a module listed above it, which is the healthy direction.
37→6 data.repositories uses network.api✕
- Connections
- 1 pair of types, where a type in data.repositories uses a type in network.api.
- The types involved
com.zrcoding.hackertab.data.repositories.ArticleRepositoryImpl→com.zrcoding.hackertab.network.api.ArticlesNetworkDataSource
- Direction
- data.repositories uses network.api, so a change to network.api can break data.repositories, while a change to data.repositories can't break network.api.
- Position
- Below the diagonal: data.repositories uses a module listed above it, which is the healthy direction.
37→10 data.repositories uses data.repositories.AggregatedArticleRepositoryImpl✕
- Connections
- 1 pair of types, where a type in data.repositories uses a type in data.repositories.AggregatedArticleRepositoryImpl.
- The types involved
com.zrcoding.hackertab.data.repositories.AggregatedArticleRepositoryImpl→com.zrcoding.hackertab.data.repositories.AggregatedArticleRepositoryImpl.CacheKey
- Direction
- data.repositories uses data.repositories.AggregatedArticleRepositoryImpl, so a change to data.repositories.AggregatedArticleRepositoryImpl can break data.repositories, while a change to data.repositories can't break data.repositories.AggregatedArticleRepositoryImpl.
- Position
- Below the diagonal: data.repositories uses a module listed above it, which is the healthy direction.
37→20 data.repositories uses domain.repositories✕
- Connections
- 6 pairs of types, where a type in data.repositories uses a type in domain.repositories.
- The types involved
com.zrcoding.hackertab.data.repositories.AggregatedArticleRepositoryImpl→com.zrcoding.hackertab.domain.repositories.AggregatedArticleRepositorycom.zrcoding.hackertab.data.repositories.AggregatedArticleRepositoryImpl→com.zrcoding.hackertab.domain.repositories.AggregatedFeedResultcom.zrcoding.hackertab.data.repositories.AggregatedArticleRepositoryImpl→com.zrcoding.hackertab.domain.repositories.ArticleRepositorycom.zrcoding.hackertab.data.repositories.ArticleRepositoryImpl→com.zrcoding.hackertab.domain.repositories.ArticleRepositorycom.zrcoding.hackertab.data.repositories.BookmarkRepositoryImpl→com.zrcoding.hackertab.domain.repositories.BookmarkRepositorycom.zrcoding.hackertab.data.repositories.SettingRepositoryImpl→com.zrcoding.hackertab.domain.repositories.SettingRepository
- Direction
- data.repositories uses domain.repositories, so a change to domain.repositories can break data.repositories, while a change to data.repositories can't break domain.repositories.
- Position
- Below the diagonal: data.repositories uses a module listed above it, which is the healthy direction.
37→25 data.repositories uses database✕
- Connections
- 1 pair of types, where a type in data.repositories uses a type in database.
- The types involved
com.zrcoding.hackertab.data.repositories.BookmarkRepositoryImpl→com.zrcoding.hackertab.database.AppDatabase
- Direction
- data.repositories uses database, so a change to database can break data.repositories, while a change to data.repositories can't break database.
- Position
- Below the diagonal: data.repositories uses a module listed above it, which is the healthy direction.
38→5 home.presentation uses domain.models✕
- Connections
- 11 pairs of types, where a type in home.presentation uses a type in domain.models.
- The types involved
com.zrcoding.hackertab.home.presentation.HomeScreenKt→com.zrcoding.hackertab.domain.models.BaseArticlecom.zrcoding.hackertab.home.presentation.HomeScreenKt→com.zrcoding.hackertab.domain.models.Topiccom.zrcoding.hackertab.home.presentation.HomeViewModel→com.zrcoding.hackertab.domain.models.BaseArticlecom.zrcoding.hackertab.home.presentation.HomeViewModel→com.zrcoding.hackertab.domain.models.NetworkErrorscom.zrcoding.hackertab.home.presentation.HomeViewModel→com.zrcoding.hackertab.domain.models.Resourcecom.zrcoding.hackertab.home.presentation.HomeViewModel→com.zrcoding.hackertab.domain.models.Sourcecom.zrcoding.hackertab.home.presentation.HomeViewModel→com.zrcoding.hackertab.domain.models.Topiccom.zrcoding.hackertab.home.presentation.HomeViewState→com.zrcoding.hackertab.domain.models.BaseArticlecom.zrcoding.hackertab.home.presentation.HomeViewState→com.zrcoding.hackertab.domain.models.Sourcecom.zrcoding.hackertab.home.presentation.HomeViewState→com.zrcoding.hackertab.domain.models.Topiccom.zrcoding.hackertab.home.presentation.LongPressActionSheetKt→com.zrcoding.hackertab.domain.models.BaseArticle
- Direction
- home.presentation uses domain.models, so a change to domain.models can break home.presentation, while a change to home.presentation can't break domain.models.
- Position
- Below the diagonal: home.presentation uses a module listed above it, which is the healthy direction.
38→8 home.presentation uses analytics✕
- Connections
- 1 pair of types, where a type in home.presentation uses a type in analytics.
- The types involved
com.zrcoding.hackertab.home.presentation.HomeViewModel→com.zrcoding.hackertab.analytics.AnalyticsHelper
- Direction
- home.presentation uses analytics, so a change to analytics can break home.presentation, while a change to home.presentation can't break analytics.
- Position
- Below the diagonal: home.presentation uses a module listed above it, which is the healthy direction.
38→20 home.presentation uses domain.repositories✕
- Connections
- 3 pairs of types, where a type in home.presentation uses a type in domain.repositories.
- The types involved
com.zrcoding.hackertab.home.presentation.HomeViewModel→com.zrcoding.hackertab.domain.repositories.ArticleRepositorycom.zrcoding.hackertab.home.presentation.HomeViewModel→com.zrcoding.hackertab.domain.repositories.BookmarkRepositorycom.zrcoding.hackertab.home.presentation.HomeViewModel→com.zrcoding.hackertab.domain.repositories.SettingRepository
- Direction
- home.presentation uses domain.repositories, so a change to domain.repositories can break home.presentation, while a change to home.presentation can't break domain.repositories.
- Position
- Below the diagonal: home.presentation uses a module listed above it, which is the healthy direction.
38→22 home.presentation uses home.presentation.HomeViewModel✕
- Connections
- 1 pair of types, where a type in home.presentation uses a type in home.presentation.HomeViewModel.
- The types involved
com.zrcoding.hackertab.home.presentation.HomeViewModel→com.zrcoding.hackertab.home.presentation.HomeViewModel.FetchResult
- Direction
- home.presentation uses home.presentation.HomeViewModel, so a change to home.presentation.HomeViewModel can break home.presentation, while a change to home.presentation can't break home.presentation.HomeViewModel.
- Position
- Below the diagonal: home.presentation uses a module listed above it, which is the healthy direction.
38→26 home.presentation uses domain.usecases✕
- Connections
- 2 pairs of types, where a type in home.presentation uses a type in domain.usecases.
- The types involved
com.zrcoding.hackertab.home.presentation.HomeViewModel→com.zrcoding.hackertab.domain.usecases.ObserveSelectedSourcesUseCasecom.zrcoding.hackertab.home.presentation.HomeViewModel→com.zrcoding.hackertab.domain.usecases.ObserveSelectedTopicsUseCase
- Direction
- home.presentation uses domain.usecases, so a change to domain.usecases can break home.presentation, while a change to home.presentation can't break domain.usecases.
- Position
- Below the diagonal: home.presentation uses a module listed above it, which is the healthy direction.
39→8 settings.presentation.sources uses analytics✕
- Connections
- 1 pair of types, where a type in settings.presentation.sources uses a type in analytics.
- The types involved
com.zrcoding.hackertab.settings.presentation.sources.SettingSourcesViewModel→com.zrcoding.hackertab.analytics.AnalyticsHelper
- Direction
- settings.presentation.sources uses analytics, so a change to analytics can break settings.presentation.sources, while a change to settings.presentation.sources can't break analytics.
- Position
- Below the diagonal: settings.presentation.sources uses a module listed above it, which is the healthy direction.
39→13 settings.presentation.sources uses design.components✕
- Connections
- 2 pairs of types, where a type in settings.presentation.sources uses a type in design.components.
- The types involved
com.zrcoding.hackertab.settings.presentation.sources.SettingSourcesScreenKt→com.zrcoding.hackertab.design.components.ChipDatacom.zrcoding.hackertab.settings.presentation.sources.SettingSourcesViewModel→com.zrcoding.hackertab.design.components.ChipData
- Direction
- settings.presentation.sources uses design.components, so a change to design.components can break settings.presentation.sources, while a change to settings.presentation.sources can't break design.components.
- Position
- Below the diagonal: settings.presentation.sources uses a module listed above it, which is the healthy direction.
39→20 settings.presentation.sources uses domain.repositories✕
- Connections
- 1 pair of types, where a type in settings.presentation.sources uses a type in domain.repositories.
- The types involved
com.zrcoding.hackertab.settings.presentation.sources.SettingSourcesViewModel→com.zrcoding.hackertab.domain.repositories.SettingRepository
- Direction
- settings.presentation.sources uses domain.repositories, so a change to domain.repositories can break settings.presentation.sources, while a change to settings.presentation.sources can't break domain.repositories.
- Position
- Below the diagonal: settings.presentation.sources uses a module listed above it, which is the healthy direction.
39→26 settings.presentation.sources uses domain.usecases✕
- Connections
- 1 pair of types, where a type in settings.presentation.sources uses a type in domain.usecases.
- The types involved
com.zrcoding.hackertab.settings.presentation.sources.SettingSourcesViewModel→com.zrcoding.hackertab.domain.usecases.ObserveSelectedSourcesUseCase
- Direction
- settings.presentation.sources uses domain.usecases, so a change to domain.usecases can break settings.presentation.sources, while a change to settings.presentation.sources can't break domain.usecases.
- Position
- Below the diagonal: settings.presentation.sources uses a module listed above it, which is the healthy direction.
40→5 shared.app uses domain.models✕
- Connections
- 3 pairs of types, where a type in shared.app uses a type in domain.models.
- The types involved
com.zrcoding.hackertab.shared.app.AppViewState→com.zrcoding.hackertab.domain.models.ThemeFontcom.zrcoding.hackertab.shared.app.AppViewState→com.zrcoding.hackertab.domain.models.ThemeModecom.zrcoding.hackertab.shared.app.AppViewState→com.zrcoding.hackertab.domain.models.ThemePalette
- Direction
- shared.app uses domain.models, so a change to domain.models can break shared.app, while a change to shared.app can't break domain.models.
- Position
- Below the diagonal: shared.app uses a module listed above it, which is the healthy direction.
40→20 shared.app uses domain.repositories✕
- Connections
- 1 pair of types, where a type in shared.app uses a type in domain.repositories.
- The types involved
com.zrcoding.hackertab.shared.app.AppViewModel→com.zrcoding.hackertab.domain.repositories.SettingRepository
- Direction
- shared.app uses domain.repositories, so a change to domain.repositories can break shared.app, while a change to shared.app can't break domain.repositories.
- Position
- Below the diagonal: shared.app uses a module listed above it, which is the healthy direction.
40→21 shared.app uses domain.usecases.GetStartDestinationUseCase✕
- Connections
- 1 pair of types, where a type in shared.app uses a type in domain.usecases.GetStartDestinationUseCase.
- The types involved
com.zrcoding.hackertab.shared.app.AppViewState→com.zrcoding.hackertab.domain.usecases.GetStartDestinationUseCase.Result
- Direction
- shared.app uses domain.usecases.GetStartDestinationUseCase, so a change to domain.usecases.GetStartDestinationUseCase can break shared.app, while a change to shared.app can't break domain.usecases.GetStartDestinationUseCase.
- Position
- Below the diagonal: shared.app uses a module listed above it, which is the healthy direction.
40→26 shared.app uses domain.usecases✕
- Connections
- 1 pair of types, where a type in shared.app uses a type in domain.usecases.
- The types involved
com.zrcoding.hackertab.shared.app.AppViewModel→com.zrcoding.hackertab.domain.usecases.GetStartDestinationUseCase
- Direction
- shared.app uses domain.usecases, so a change to domain.usecases can break shared.app, while a change to shared.app can't break domain.usecases.
- Position
- Below the diagonal: shared.app uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Domain Modelling
At a glance — Accessibility
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 27 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 6 | Medium |
Roadmap
Top priorities: Resolve the 1 No automated tests finding(s) in Code Coverage; Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce; Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No automated tests finding(s) in Code Coverage. | +14.2 pts | High | Code Coverage |
| Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce. | +4.2 pts | Medium | Observability |
| Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing. | +4.2 pts | Medium | Security & performance tooling |
| Add tests that import the unreached modules (directly or through their public entry). | +4.2 pts | Medium | Test Coverage |
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with project.pbxproj. | +1.3 pts | Low | ADR Quality |
| Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video. | +2.1 pts | Medium | Text alternatives |
| Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up. | +2.0 pts | Medium | Type Safety |
| Resolve the 2 redundant comment finding(s) in Comment Value — start with Components.jsx (2). | +0.8 pts | Low | Comment Value |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 0.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| feature/bookmarks/src/commonMain/kotlin/com/zrcoding/hackertab/bookmarks/presentation/BookmarksScreen.kt | 6.5 | Mixed | Change Coupling: Boundary-crossing change coupling: BookmarksScreen.kt ↔ MainNavHost.kt |
| feature/settings/src/androidMain/kotlin/com/zrcoding/hackertab/settings/presentation/about/ContactSupport.android.kt | 6.7 | Mixed | Explicit Debt: TodoComment |
| REDACTED | 6.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| feature/settings/src/commonMain/kotlin/com/zrcoding/hackertab/settings/presentation/sources/SettingSourcesViewModel.kt | 7.0 | Mixed | Code Duplication: Edited copy of a member (17 corresponding lines) |
| feature/home/src/commonMain/kotlin/com/zrcoding/hackertab/home/presentation/HomeScreen.kt | 7.2 | Mixed | God Classes: MethodTooLong: HomeScreenKt.ToFeedCard |
| core/design/src/commonMain/kotlin/com/zrcoding/hackertab/design/components/states/EmptyState.kt | 7.2 | Mixed | Code Duplication: Near-duplicate member pair (36 shared lines) |
| core/design/src/commonMain/kotlin/com/zrcoding/hackertab/design/components/buttons/DestructiveButton.kt | 7.4 | Mixed | Code Duplication: Edited copies of one member (3 members, 34+ corresponding lines) |
| feature/onboarding/src/commonMain/kotlin/com/zrcoding/hackertab/onboarding/profile/SetupProfileScreen.kt | 7.4 | Mixed | Code Duplication: Edited copies of one member (3 members, 12+ corresponding lines) |
| shared/src/commonMain/kotlin/com/zrcoding/hackertab/shared/navigation/MainNavHost.kt | 7.8 | Mixed | Cyclomatic Complexity: MainNavHostKt.MainNavHost (cyclomatic 18) |
| feature/settings/src/commonMain/kotlin/com/zrcoding/hackertab/settings/presentation/appearance/SettingsAppearanceScreen.kt | 7.8 | Mixed | Code Duplication: Edited copy of a member (37 corresponding lines) |
| core/data/src/commonMain/kotlin/com/zrcoding/hackertab/data/repositories/SettingRepositoryImpl.kt | 8.2 | Near-clean | Explicit Debt: TodoComment |
| core/design/src/commonMain/kotlin/com/zrcoding/hackertab/design/components/inputs/HackertabTextField.kt | 8.5 | Near-clean | Cognitive Complexity: HackertabTextFieldKt.HackertabTextField (cognitive 16) |
| design/project/components/MoodBoard.jsx | 8.5 | Near-clean | God Classes: FunctionTooLong: MoodBoard.MoodBoard |
| design/project/components/Screens.jsx | 8.5 | Near-clean | God Classes: FileTooLong: components/Screens.jsx |
| design/project/components/Tokens.jsx | 8.5 | Near-clean | God Classes: FunctionTooLong: Tokens.Tokens |
| design/project/components/Library.jsx | 8.5 | Near-clean | God Classes: FunctionTooLong: Library.Library |
| design/project/components/Handoff.jsx | 8.5 | Near-clean | God Classes: FunctionTooLong: Handoff.Handoff |
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 62 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 62 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, 143 of 162 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This repository's dependency manifests WERE read and their pinning discipline assessed; what went unanswered is the currency half, because api.foojay.io — the registry that answers it — was asked and did not reply (the build stopped because api.foojay.io, a repository this project declares, refused it with HTTP 403 — what this scan's egress allowlist returns for a host that is not on it, so the dependency graph was not resolved). This is OUR side and it is an ENVIRONMENT fault, not a missing collector: the collector exists and ran. An HTTP 403 here is what this scan's egress allowlist returns for a host that is not on it, so the remedy is to add api.foojay.io to the allowlist and re-run — not to build anything.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (shared/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. For npm the surface is what a published package.json's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
- D24 Comment Value — 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 source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- 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/data/src/commonMain/kotlin/com/zrcoding/hackertab/data/repositories/AggregatedArticleRepository.kt` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- AX1 Captive dependencies — 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 Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository's container is Koin, whose lifetimes are not modelled 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.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Boot via AndroidApp (app). the Android app did not build — `./gradlew :app:assembleDebug` exited 1: * What went wrong: Unable to download toolchain matching the requirements ({languageVersion=17, vendor=Amazon Corretto, implementation=vendor-specific}) from 'https://api.foojay.io/disco/v3.0/ids/f54…; runtime evidence skipped (launch chosen because app/build.gradle.kts applies the Android application plugin and gradlew builds it).
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- DM8 Value-object opportunities — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check finds primitive parameters that travel together through several signatures of the domain (a missing value object). Its deterministic rule has not yet shown 95 % precision on adjudicated rows, so the clumps it finds are counted here and not published as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
- DM9 Scattered domain decisions — 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. Arm two tells a construction that PRODUCES a measurement from one that merely passes it along, and this repository's frontend does not compute that fact. A measurement built independently in two places would not appear above.
- DM9 Scattered domain decisions — 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. Some of this repository's production types come from a frontend that does not bind comparison operands to the members they read, which arm one needs, and those types were not walked for this dimension. The counts above speak for the languages that declare it.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java source only, and this repository's Kotlin, Swift is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby, Scala and Rust source only, and this repository's Kotlin, Swift is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
- 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.
- AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
- AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
- AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
7 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was design-canvas.dcExport at 38. A further 1 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being Icons.Icon at 44 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: design/project/components/Icons.jsx (Icons.Icon at 44). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 7 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with design-canvas.dcExport (cyclomatic 38), design-canvas.DCViewport (cyclomatic 32), design-canvas.DesignCanvas (cyclomatic 30). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 7 together lifts Cyclomatic Complexity from 8.5 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
6 method(s) exceeded the cognitive complexity threshold of 15; the worst was design-canvas.dcExport at 48.
What to do
- Bring the 1 body over 30 down to 30 or less in Cognitive Complexity — start with design-canvas.dcExport (cognitive 48). — Refactoring it lifts Cognitive Complexity from 8.3 to about 8.8/10.
D3 · God Classes
7 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 4 FunctionTooLong finding(s) in God Classes — start with MoodBoard.jsx, Tokens.jsx, Library.jsx. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 2 FileTooLong finding(s) in God Classes — start with Screens.jsx, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 MethodTooLong finding(s) in God Classes — start with HomeScreen.kt. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
13 duplicated block group(s) detected. 5.9 % of the production lines (748 of 12,580) are in a reported copy. A further 12 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
What to do
- Resolve the 2 Edited copy of a member (16 corresponding lines) finding(s) in Code Duplication — start with ContactSupport.android.kt, BookmarksScreen.kt. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Edited copy of a member (17 corresponding lines) finding(s) in Code Duplication — start with SettingSourcesViewModel.kt, SettingsMasterScreen.kt. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Duplicated block (13 lines × 2) finding(s) in Code Duplication — start with SettingsAppearanceScreen.kt, SetupSourcesViewModel.kt. — One of this dimension's main actionable groups (2 warning-level).
D5 · Coupling
14 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; 6 module(s) off the main sequence.
What to do
- Resolve the 6 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (6 warning-level).
D6 · Cohesion (LCOM4)
0 of 14 classes have LCOM4 above 3.
D8 · Code Coverage
No automated tests — no test code was found in this repository.
What to do
- Resolve the 1 No automated tests finding(s) in Code Coverage. — One of this dimension's main actionable groups (1 issue-level).
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 27 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 15 Maven/Gradle manifest(s) declare with a version resolvable from the manifest itself — the same declaration-site closure this analysis reads for dependency currency. The JVM has no lockfile a checkout is guaranteed to carry, so this is deliberately NOT the transitive closure. 8 further coordinate(s) are declared with no version at the declaration site — inherited from a parent POM, a BOM or an unresolved Gradle version reference — and are NOT graded: this verdict covers what the checkout pins, not the full transitive graph. A further 9 coordinate(s) are not published to Maven Central — another repository (Google's Maven hosts androidx), a SNAPSHOT, or a private artifact — so their licences are not readable from here and they are outside this verdict.
D15 · Churn × Complexity Hotspots
Top hotspots: shared/src/commonMain/kotlin/com/zrcoding/hackertab/shared/navigation/MainNavHost.kt (12×18=216)
What to do
- Resolve the 1 Hotspot finding(s) in Churn × Complexity Hotspots — start with MainNavHost.kt. — One of this dimension's main actionable groups (1 warning-level).
D17 · Explicit Debt
2 deducted task-comment markers across 12580 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 2 TodoComment finding(s) in Explicit Debt — start with ContactSupport.android.kt, SettingRepositoryImpl.kt. — One of this dimension's main actionable groups (2 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 3 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with project.pbxproj. — One of this dimension's main actionable groups (1 recommendation-level).
D24 · Comment Value
2 of 51 judged comments only repeat the code they sit on (3.9 %). 5 comment(s) in another language or script were not judged.
What to do
- Resolve the 2 redundant comment finding(s) in Comment Value — start with Components.jsx (2). — One of this dimension's main actionable groups (2 recommendation-level).
D26 · Project Cohesion
0 of 15 build units (Gradle, Xcode) 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)
27 finding(s): 0 critical, 15 high, 12 medium, 0 low. 9 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 1 file(s) — `gradlew` (line 177) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
What to do
- Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4). — One of this dimension's main actionable groups (4 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 9 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 (9 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 66 of the 189 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: SettingSourcesViewModel.kt↔SettingTopicsViewModel.kt 70%; BookmarksScreen.kt↔MainNavHost.kt 70%; Color.kt↔Theme.kt 64%
What to do
- Resolve the 1 Boundary-crossing change coupling finding(s) in Change Coupling — start with BookmarksScreen.kt. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 2 Change coupling finding(s) in Change Coupling — start with Color.kt, SettingSourcesScreen.kt. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Change-coupling hub finding(s) in Change Coupling — start with SettingSourcesViewModel.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 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-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 36 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
AC1 · Text alternatives
- An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative. — REDACTED:580
What to do
- Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
AC2 · Forms & labels
- A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one). (×12) — design/project/components/Components.jsx:121, design/project/components/Library.jsx:117, design/project/components/Screens.jsx:335, …
What to do
- Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
AC3 · Page structure
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="root">, so there is no content here to wrap — render the <main> from the component mounted into it. — REDACTED:2
What to do
- Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC4 · Keyboard semantics
- A click handler on a plain element with no role and no tabindex: even where another element's key handler can reach it, assistive tech can neither focus it nor announce what it is. Use a <button>, or add role + tabIndex={0}. — REDACTED:737
What to do
- Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
AC5 · ARIA correctness
AC6 · Visual & motion safety
- <span> moves — its inline style sets `animation: blink 1s steps(2) infinite` — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:. — design/project/components/MoodBoard.jsx:166
- <span> moves — its inline style sets `transition: left 200ms` — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:. — design/project/components/Screens.jsx:623
- <div> moves — its inline style sets `animation: spin 1s linear infinite` — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:. — design/project/components/Screens.jsx:811
- The inline foreground/background colours fall below the 4.5:1 WCAG AA minimum for normal text. Darken/lighten one of them. — design/project/components/Screens.jsx:919
What to do
- Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
- `SettingRepository` declares 21 abstract methods: `getTopics`, `observeSavedTopicsIds`, `saveTopics`, `removeTopic`, `observeSavedSourcesIds`, `saveSource`, `removeSource`, `getSavedProfile`, `getProfiles`, `saveProfile`, `observeThemeMode`, `setThemeMode`, `observeThemePalette`, `setThemePalette`, `observeThemeFont`, `setThemeFont`, `observeCoachmarksSeen`, `setCoachmarksSeen`, `resetCoachmarks`, `getLastVisitedAt`, `setLastVisitedAt`. Counted over its public functions with no body, once per name; default-bodied functions and properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — core/domain/src/commonMain/kotlin/com/zrcoding/hackertab/domain/repositories/SettingRepository.kt:11
What to do
- Split fat interfaces into focused role-interfaces so clients depend only on what they use.
DM11 · Constructible invalid state
- `BookmarkedArticleEntity`'s public constructor takes `id`, `title`, `url`, `source` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `BookmarkedArticleEntity` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — core/database/src/commonMain/kotlin/com/zrcoding/hackertab/database/entities/Entities.kt:8
What to do
- Give each aggregate one way in that can refuse — a guarded constructor, value-object parameters that validate themselves, or a private constructor behind a factory that returns a failure.
DM12 · Ambient inputs in the domain
DM6 · Domain ↔ infrastructure boundary
DM9 · Scattered domain decisions
M1 · Documentation (README)
What to do
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P2 · Observability
- No logging or diagnostics emission found. This repository ships a binary its users launch rather than a service you operate, so there is no operator to page — but when a run fails on a user's machine, neither they nor you have anything to read.
What to do
- Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add spotbugs with find-sec-bugs (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 2 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:4
- `app/build.gradle.kts` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — app/build.gradle.kts:66
What to do
- Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
What to do
- Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
PF3 · Async & latency hygiene
R1 · Type Safety
- 0 typed · 11 plain JS — the untyped files are design/project/components/Components.jsx, design/project/components/Handoff.jsx, design/project/components/Icons.jsx, design/project/components/Library.jsx, design/project/components/MoodBoard.jsx, design/project/components/Motion.jsx (+5 more).
What to do
- Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
R10 · Code Duplication
- design/project/components/Screens.jsx:123 · design/project/components/Screens.jsx:566 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — design/project/components/Screens.jsx:123
- design/project/components/Screens.jsx:147 · design/project/components/Screens.jsx:205 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — design/project/components/Screens.jsx:147
- design/project/components/Components.jsx:49 · design/project/components/Components.jsx:92 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — design/project/components/Components.jsx:49
- design/project/components/Components.jsx:271 · design/project/components/Components.jsx:304 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — design/project/components/Components.jsx:271
- design/project/components/Screens.jsx:796 · design/project/components/Screens.jsx:817 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — design/project/components/Screens.jsx:796
- design/project/components/Tokens.jsx:180 · design/project/components/Tokens.jsx:194 · design/project/components/Tokens.jsx:223 — all 3 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — design/project/components/Tokens.jsx:180
- design/project/components/Handoff.jsx:8 · design/project/components/Library.jsx:60 · design/project/components/Motion.jsx:42 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — design/project/components/Handoff.jsx:8
- design/project/components/Library.jsx:58 · design/project/components/MoodBoard.jsx:21 · design/project/components/Motion.jsx:41 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — design/project/components/Library.jsx:58
- design/project/components/Library.jsx:194 · design/project/components/Screens.jsx:849 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — design/project/components/Library.jsx:194
- design/project/components/Screens.jsx:635 · design/project/components/Screens.jsx:686 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — design/project/components/Screens.jsx:635
- design/project/components/Components.jsx:332 · design/project/components/Screens.jsx:124 · design/project/components/Screens.jsx:567 — the 3 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — design/project/components/Components.jsx:332
- design/project/components/Screens.jsx:39 · design/project/components/Screens.jsx:104 · design/project/components/Screens.jsx:164 — all 3 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — design/project/components/Screens.jsx:39
- design/project/components/Screens.jsx:328 · design/project/components/Screens.jsx:445 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — design/project/components/Screens.jsx:328
- design/project/components/Tokens.jsx:239 · design/project/components/Tokens.jsx:252 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — design/project/components/Tokens.jsx:239
- design/project/components/Components.jsx:321 · design/project/components/Screens.jsx:409 · design/project/components/Screens.jsx:972 — the 3 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — design/project/components/Components.jsx:321
- design/project/components/Screens.jsx:395 · design/project/components/Screens.jsx:966 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — design/project/components/Screens.jsx:395
- design/project/components/Screens.jsx:408 · design/project/components/Screens.jsx:465 · design/project/components/Screens.jsx:971 — all 3 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — design/project/components/Screens.jsx:408
- design/project/components/Screens.jsx:431 · design/project/components/Screens.jsx:767 · design/project/components/Screens.jsx:787 — all 3 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — design/project/components/Screens.jsx:431
- design/project/components/Screens.jsx:540 · design/project/components/Screens.jsx:593 · design/project/components/Screens.jsx:654 · design/project/components/Screens.jsx:700 — all 4 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — design/project/components/Screens.jsx:540
- design/project/components/Screens.jsx:673 · design/project/components/Screens.jsx:680 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — design/project/components/Screens.jsx:673
- design/project/components/Screens.jsx:724 · design/project/components/Screens.jsx:799 · design/project/components/Screens.jsx:820 — all 3 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — design/project/components/Screens.jsx:724
- design/project/components/Screens.jsx:855 · design/project/components/Screens.jsx:938 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — design/project/components/Screens.jsx:855
- design/project/components/Tokens.jsx:139 · design/project/components/Tokens.jsx:152 · design/project/components/Tokens.jsx:158 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. — design/project/components/Tokens.jsx:139
What to do
- Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
R2 · Cyclomatic Complexity
R3 · Large Files
- design/project/components/Screens.jsx has 976 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — design/project/components/Screens.jsx:1
- REDACTED has 878 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
What to do
- Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
R4 · Test Coverage
- 0% of 11 production file(s) reachable from 0 test file(s) via the import graph — 'production' here is the RESIDUE: every source file left once tests, tooling, generated output, config, declarations and declaration-only modules, fixture corpora, type fixtures, behaviour-free data modules, re-export barrels, registration/constant data modules and service workers are set aside, so the percentage is taken over a smaller denominator than the workspace's file count
What to do
- Add tests that import the unreached modules (directly or through their public entry).
R7 · Dead Code
- Unreachable from the 10 application, 0 tooling and 0 test entry point(s) detected in this repo. This repository declares no build, type-check or test script, so nothing here would fail on a wrong deletion — confirm by hand that nothing loads each file (including by a path built at runtime) before removing it. An undetected custom entry would make these reachable.
- no import path from any entry point (10 application, 0 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make — design/project/ios-frame.jsx
What to do
- Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
R9 · Circular Imports
X1 · Async correctness
X12 · Unreachable branch
X16 · Unfloored truncation loop
X2 · Cancellation propagation
- Only 4/5 functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http; Ktor, OkHttp newCall, URL streams) accept an AbortSignal or the coroutine's cancellation or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, a cancelled request, a shutdown, an expired deadline. Take a `signal` () and hand it to the request; in a Kotlin suspend function, make the request with a call that suspends — Ktor, OkHttp's `executeAsync()`, or a `suspendCancellableCoroutine` that cancels the `Call` — not a blocking `execute()`: `withContext(Dispatchers.IO)` moves the call off the caller's thread but does not make it cancellable; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
- `dcExport` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — REDACTED:529
What to do
- Thread an AbortSignal or the coroutine's cancellation through functions that make requests, so the work stops when its caller gives up.
X21 · Side-effecting pattern guard
X3 · Exception handling
- `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it. (×3) — REDACTED:145, REDACTED:155, REDACTED:547
- An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×5) — REDACTED:270, REDACTED:277, REDACTED:285, …
- `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included. — REDACTED:567
What to do
- Swallowed exception (empty catch)
X30 · Support guard that admits what it rejects
X5 · Nullable reference types
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC1 · Text alternatives | 1.1.1, 1.2.2, 1.2.5 | Partial signal |
| AC2 · Forms & labels | 1.3.1, 3.3.2, 4.1.2 | Partial signal |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC4 · Keyboard semantics | 2.1.1, 2.4.3 | Partial signal |
| AC5 · ARIA correctness | 4.1.2 | Partial signal |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 40.2 | Weak — gated by R1, R3, X3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 94.9 | Exemplary | Solid. |
| Maturity | 53.6 | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 16.3 | Critical — gated by D8, R4, P2, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 61.0 | Adequate — gated by D29, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 69.7 | Adequate — gated by DM11 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Accessibility | 40.1 | Weak — gated by AC1, AC4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100.0 | Exemplary | Strongest area. |
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 — 75 check(s) not relevant to this codebase
- AX1 Captive dependencies — 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
- 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 Swift request handler (a Vapor, Hummingbird, Kitura, Swifter or Perfect route handler, as a method or a registered closure) is declared, so no state is shared between request threads. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — the Android app did not build — `./gradlew :app:assembleDebug` exited 1: * What went wrong: Unable to download toolchain matching the requirements ({languageVersion=17, vendor=Amazon Corretto, implementation=vendor-specific}) from 'https://api.foojay.io/disco/v3.0/ids/f54…; runtime evidence skipped (launch chosen because app/build.gradle.kts applies the Android application plugin and gradlew builds it) This is a statement about this run, not a statement about your application: nothing here says the app is inaccessible, only that it was never run.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no data at rest for these controls to protect.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named column (email, first_name, date_of_birth, phone_number, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — No tests were found in the analyzed repository to assess for quality.
- D11 Test Reliability — No test suite was found to re-run, so reliability couldn't be assessed. Two searches produced that zero and both came back empty: the classifier that reads the loaded workspace recognised no suite it could run, and a walk of the source on disk — which covers the JS/TS `*.test.*` and `*.spec.*` conventions and probes for a Pester suite — found no test source in any other ecosystem either. Neither search reaches a suite that is missing from the loaded workspace and carries no name either walk recognises, so this is 'no suite found by those two searches', not a verdict that the repository has none.
- D12 Dependency Hygiene — Dependency currency not established — api.foojay.io did not answer
- D16 Bus Factor — bus factor 1 — one contributor carries this repository
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — D21 withholds its case and prefix conventions rows: 3 candidate(s) found and not reported.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- 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) — 1 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- DM1 Aggregate boundaries — no aggregates detected — aggregate-boundary check not applicable
- DM10 One transaction, one aggregate — no repository writes detected — no operation to judge against the one-aggregate rule
- DM2 Strongly-typed ids — no id-bearing domain types detected — strongly-typed-id adoption not assessable
- DM3 Integration-event coupling — no integration events detected — coupling check not applicable
- DM4 Rich vs anemic model — no data-bearing entities detected — rich-vs-anemic model not assessable
- DM5 Encapsulated state — no domain entities found — DM5 grades how entities protect their state, and this repository declares none
- DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
- DM8 Value-object opportunities — not scored — the deterministic rule found 0 candidate clump(s); its rows are withheld until it has a measured precision of 95 % (a sample of fewer than 10 rows cannot show one)
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and this analysis resolves a call's owner only where the receiver's type is written down in the source. Reported as guidance rather than measured
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM, JavaScript/TypeScript, Swift source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a pom.xml, Gradle or sbt build, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
- R5 Dependency Freshness — no package-lock.json — dependency freshness not measured (would require an npm lockfile); JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
- R6 Tooling — no package.json in the repository — test/lint/typecheck wiring is read from package.json scripts (corroborated against CI), so this project's own toolchain isn't measured here
- R8 Dependency Hygiene — Not measured — no package.json declares any dependency, so there is nothing to check imports against (imports may resolve through a host runtime rather than node).
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — X24 reached only 22% of this repository's production lines — kotlin (12,539 lines), swift (41 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X27 Collection changed while being enumerated — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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 — 31 finding(s)
- <button> with no accessible text design/project/components/Components.jsx:121
- <button> with no accessible text design/project/components/Library.jsx:117
- <button> with no accessible text design/project/components/Screens.jsx:335
- <button> with no accessible text design/project/components/Screens.jsx:340
- <button> with no accessible text design/project/components/Screens.jsx:367
- <button> with no accessible text design/project/components/Screens.jsx:415
- <button> with no accessible text design/project/components/Screens.jsx:451
- <button> with no accessible text design/project/components/Screens.jsx:922
- <button> with no accessible text design/project/components/Screens.jsx:923
- <button> with no accessible text design/project/components/Screens.jsx:924
- <button> with no accessible text REDACTED:829
- <button> with no accessible text REDACTED:908
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- <img> without a text alternative REDACTED:580
- Click handler on a non-interactive <div> REDACTED:737
- REDACTED
- REDACTED
- Boundary-crossing change coupling: BookmarksScreen.kt ↔ MainNavHost.kt feature/bookmarks/src/commonMain/kotlin/com/zrcoding/hackertab/bookmarks/presentation/BookmarksScreen.kt:1
- No automated tests
Serious — 118 finding(s)
- Swallowed exception (empty catch) REDACTED:145
- Swallowed exception (empty catch) REDACTED:155
- Swallowed exception (empty catch) REDACTED:270
- Swallowed exception (empty catch) REDACTED:277
- Swallowed exception (empty catch) REDACTED:285
- Swallowed exception (empty catch) REDACTED:530
- Swallowed exception (empty catch) REDACTED:547
- Swallowed exception (empty catch) REDACTED:580
- Off the main sequence: hackertab:core:network
- Off the main sequence: hackertab:feature:bookmarks
- Off the main sequence: hackertab:feature:onboarding
- Off the main sequence: hackertab:feature:settings
- Off the main sequence: hackertab:feature:home
- Off the main sequence: hackertab:core:domain
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (5 lines × 3 locations) design/project/components/Components.jsx:321
- Duplicated block (5 lines × 3 locations) design/project/components/Screens.jsx:408
- Duplicated block (5 lines × 3 locations) design/project/components/Screens.jsx:431
- Duplicated block (5 lines × 3 locations) design/project/components/Screens.jsx:724
- Duplicated block (5 lines × 3 locations) design/project/components/Tokens.jsx:139
- FunctionTooLong: MoodBoard.MoodBoard design/project/components/MoodBoard.jsx:26
- FunctionTooLong: Tokens.Tokens design/project/components/Tokens.jsx:63
- FunctionTooLong: Library.Library design/project/components/Library.jsx:64
- FunctionTooLong: Handoff.Handoff design/project/components/Handoff.jsx:12
- Animation without a prefers-reduced-motion guard design/project/components/MoodBoard.jsx:166
- Animation without a prefers-reduced-motion guard design/project/components/Screens.jsx:623
- Animation without a prefers-reduced-motion guard design/project/components/Screens.jsx:811
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (5 lines × 2 locations) design/project/components/Screens.jsx:395
- Duplicated block (5 lines × 2 locations) design/project/components/Screens.jsx:673
- Duplicated block (5 lines × 2 locations) design/project/components/Screens.jsx:855
- TodoComment feature/settings/src/androidMain/kotlin/com/zrcoding/hackertab/settings/presentation/about/ContactSupport.android.kt:21
- TodoComment core/data/src/commonMain/kotlin/com/zrcoding/hackertab/data/repositories/SettingRepositoryImpl.kt:34
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- FileTooLong: components/Screens.jsx design/project/components/Screens.jsx
- FileTooLong: REDACTED REDACTED
- Change coupling: Color.kt ↔ Theme.kt core/design/src/commonMain/kotlin/com/zrcoding/hackertab/design/theme/Color.kt:1
- Change coupling: SettingSourcesScreen.kt ↔ SettingTopicsViewModel.kt feature/settings/src/commonMain/kotlin/com/zrcoding/hackertab/settings/presentation/sources/SettingSourcesScreen.kt:1
- REDACTED
- REDACTED
- Edited copy of a member (16 corresponding lines) feature/settings/src/androidMain/kotlin/com/zrcoding/hackertab/settings/presentation/about/ContactSupport.android.kt:31
- Edited copy of a member (16 corresponding lines) feature/bookmarks/src/commonMain/kotlin/com/zrcoding/hackertab/bookmarks/presentation/BookmarksScreen.kt:311
- Edited copy of a member (17 corresponding lines) feature/settings/src/commonMain/kotlin/com/zrcoding/hackertab/settings/presentation/sources/SettingSourcesViewModel.kt:64
- Edited copy of a member (17 corresponding lines) feature/settings/src/commonMain/kotlin/com/zrcoding/hackertab/settings/presentation/master/SettingsMasterScreen.kt:276
- Duplicated block (13 lines × 2) feature/settings/src/commonMain/kotlin/com/zrcoding/hackertab/settings/presentation/appearance/SettingsAppearanceScreen.kt:241
- Duplicated block (13 lines × 2) feature/onboarding/src/commonMain/kotlin/com/zrcoding/hackertab/onboarding/sources/SetupSourcesViewModel.kt:49
- Duplicated block (12 lines × 2) core/design/src/commonMain/kotlin/com/zrcoding/hackertab/design/components/states/EmptyState.kt:76
- Duplicated block (12 lines × 2) feature/home/src/commonMain/kotlin/com/zrcoding/hackertab/home/presentation/HomeScreen.kt:389
- Duplicated block (11 lines × 2 locations) design/project/components/Components.jsx:49
- Duplicated block (11 lines × 2 locations) design/project/components/Components.jsx:271
- Duplicated block (7 lines × 3 locations) design/project/components/Handoff.jsx:8
- Duplicated block (7 lines × 3 locations) design/project/components/Library.jsx:58
- Duplicated block (7 lines × 2 locations) design/project/components/Library.jsx:194
- Duplicated block (7 lines × 2 locations) design/project/components/Screens.jsx:635
- Duplicated block (6 lines × 3 locations) design/project/components/Components.jsx:332
- Duplicated block (6 lines × 3 locations) design/project/components/Screens.jsx:39
- Duplicated block (6 lines × 2 locations) design/project/components/Screens.jsx:328
- Duplicated block (6 lines × 2 locations) design/project/components/Tokens.jsx:239
- Page without a main landmark REDACTED:2
- Low contrast colour pair (2.9:1) design/project/components/Screens.jsx:919
- design-canvas.dcExport (cyclomatic 38) REDACTED:529
- design-canvas.DCViewport (cyclomatic 32) REDACTED:244
- design-canvas.DesignCanvas (cyclomatic 30) REDACTED:125
- design-canvas.DCArtboardFrame (cyclomatic 20) REDACTED:642
- design-canvas.DCSection (cyclomatic 19) REDACTED:464
- MainNavHostKt.MainNavHost (cyclomatic 18) shared/src/commonMain/kotlin/com/zrcoding/hackertab/shared/navigation/MainNavHost.kt:151
- design-canvas.DCFocusOverlay (cyclomatic 18) REDACTED:789
- Hotspot: shared/src/commonMain/kotlin/com/zrcoding/hackertab/shared/navigation/MainNavHost.kt shared/src/commonMain/kotlin/com/zrcoding/hackertab/shared/navigation/MainNavHost.kt:151
- bus factor 1 — one contributor carries this repository
- design-canvas.dcExport (cognitive 48) REDACTED:529
- design-canvas.DCViewport (cognitive 27) REDACTED:244
- design-canvas.DesignCanvas (cognitive 26) REDACTED:125
- design-canvas.DCArtboardFrame (cognitive 18) REDACTED:642
- MainNavHostKt.MainNavHost (cognitive 16) shared/src/commonMain/kotlin/com/zrcoding/hackertab/shared/navigation/MainNavHost.kt:151
- HackertabTextFieldKt.HackertabTextField (cognitive 16) core/design/src/commonMain/kotlin/com/zrcoding/hackertab/design/components/inputs/HackertabTextField.kt:41
- MethodTooLong: HomeScreenKt.ToFeedCard feature/home/src/commonMain/kotlin/com/zrcoding/hackertab/home/presentation/HomeScreen.kt:302
- Change-coupling hub: SettingSourcesViewModel.kt → SettingRepositoryImpl.kt, SettingTopicsScreen.kt, SettingTopicsViewModel.kt feature/settings/src/commonMain/kotlin/com/zrcoding/hackertab/settings/presentation/sources/SettingSourcesViewModel.kt
- REDACTED
- Near-duplicate member pair (36 shared lines) core/design/src/commonMain/kotlin/com/zrcoding/hackertab/design/components/states/EmptyState.kt:49
- Edited copies of one member (3 members, 34+ corresponding lines) core/design/src/commonMain/kotlin/com/zrcoding/hackertab/design/components/buttons/DestructiveButton.kt:34
- Edited copy of a member (37 corresponding lines) feature/settings/src/commonMain/kotlin/com/zrcoding/hackertab/settings/presentation/appearance/SettingsAppearanceScreen.kt:239
- Edited copy of a member (25 corresponding lines) feature/settings/src/commonMain/kotlin/com/zrcoding/hackertab/settings/presentation/about/SettingsAboutScreen.kt:234
- Edited copy of a member (22 corresponding lines) core/design/src/commonMain/kotlin/com/zrcoding/hackertab/design/components/Chips.kt:38
- Edited copies of one member (3 members, 12+ corresponding lines) feature/onboarding/src/commonMain/kotlin/com/zrcoding/hackertab/onboarding/profile/SetupProfileScreen.kt:65
- Edited copies of one member (3 members, 14+ corresponding lines) core/design/src/commonMain/kotlin/com/zrcoding/hackertab/design/components/cards/MetaItem.kt:29
- Edited copy of a member (10 corresponding lines) core/data/src/iosMain/kotlin/com/zrcoding/hackertab/data/IosDataStore.kt:24
- Duplicated block (21 lines × 2) core/design/src/commonMain/kotlin/com/zrcoding/hackertab/design/components/buttons/DestructiveButton.kt:43
- Duplicated block (19 lines × 2) core/design/src/commonMain/kotlin/com/zrcoding/hackertab/design/components/cards/ArticleCard.kt:66
- Duplicated block (15 lines × 2) core/design/src/commonMain/kotlin/com/zrcoding/hackertab/design/components/states/EmptyState.kt:52
- Duplicated block (14 lines × 2) core/design/src/commonMain/kotlin/com/zrcoding/hackertab/design/components/buttons/DestructiveButton.kt:55
- Duplicated block (11 lines × 3) feature/onboarding/src/commonMain/kotlin/com/zrcoding/hackertab/onboarding/profile/SetupProfileScreen.kt:84
- Duplicated block (9 lines × 2) core/design/src/commonMain/kotlin/com/zrcoding/hackertab/design/components/states/EmptyState.kt:123
- Duplicated block (8 lines × 4) feature/home/src/commonMain/kotlin/com/zrcoding/hackertab/home/presentation/HomeScreen.kt:350
- Duplicated block (8 lines × 3) feature/home/src/commonMain/kotlin/com/zrcoding/hackertab/home/presentation/HomeScreen.kt:389
- Duplicated block (8 lines × 2) feature/onboarding/src/commonMain/kotlin/com/zrcoding/hackertab/onboarding/profile/SetupProfileScreen.kt:96
- Constructible in an invalid state: BookmarkedArticleEntity core/database/src/commonMain/kotlin/com/zrcoding/hackertab/database/entities/Entities.kt:8
- No structured logging
- Type Safety
- Duplicated block (21 lines × 2 locations) design/project/components/Screens.jsx:123
- Duplicated block (14 lines × 2 locations) design/project/components/Screens.jsx:147
- Duplicated block (8 lines × 2 locations) design/project/components/Screens.jsx:796
- Duplicated block (8 lines × 3 locations) design/project/components/Tokens.jsx:180
- Duplicated block (5 lines × 4 locations) design/project/components/Screens.jsx:540
- design/project/components/Screens.jsx: 976 lines of code design/project/components/Screens.jsx:1
- REDACTED: 878 lines of code REDACTED:1
- Test Coverage
- Dead file (~338 LoC) design/project/ios-frame.jsx
- Async function without AbortSignal: dcExport REDACTED:529
- Swallowed exception (caught, then discarded) REDACTED:567
Minor — 13 finding(s)
- redundant comment design/project/components/Components.jsx:250
- redundant comment design/project/components/Components.jsx:277
- Fat interface: SettingRepository (21 abstract methods) core/domain/src/commonMain/kotlin/com/zrcoding/hackertab/domain/repositories/SettingRepository.kt:11
- No ADRs found iosApp/iosApp.xcodeproj/project.pbxproj:1
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- No SAST REDACTED:4
- No dependency-update automation app/build.gradle.kts:66
- No changelog
- Not all functions that make a request accept an AbortSignal or the coroutine's cancellation
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=0 --max-count=200" --report-format json --report-path /tmp/watchdog-gitleaks-36f255cb576a48169a054930060f380b/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=200 --max-count=264" --report-format json --report-path /tmp/watchdog-gitleaks-36f255cb576a48169a054930060f380b/history-1.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history-1.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-36f255cb576a48169a054930060f380b/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 . | 27 | 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 1 file(s) — `core/data/src/commonMain/kotlin/com/zrcoding/hackertab/data/repositories/AggregatedArticleRepository.kt` — so the PII/GDPR sweep did not cover them at all. | 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 |