Executive summary
wgtunnel/android falls short of our standard for production, in part because it has pipeline tools referenced by a changeable name. It scores 56 out of 100 and is rated Adequate, and all 68 of its critical findings are security problems in the build pipeline and in its automatic dependency updates.
Security and Compliance, at 52, is the weakest lens by a small margin, and the weakest lens counts most in the score. The best first step is recording design decisions, worth about 3 points. Fixing the two pipeline jobs with more access than they need would lift Security and Compliance itself, worth about 1 point.
Thirty-four pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Twenty-seven secrets can leak from the build pipeline, and five pipeline steps put outside input straight into a shell command, so an attacker can run commands in the build pipeline. Pinning each tool to an exact version, limiting each secret to its own step and passing outside input through environment variables would close these risks. Setting a waiting period for automatic updates would fix the automatic dependency update that takes a new release at once, and the pipeline step that installs packages without pinning their versions needs the packages it installs pinned to exact versions.
The product code is 28,571 lines, about €34,000 to rebuild.
The weakest lenses score close to each other, so improving any of them moves the score.
New since the last survey: 19 findings
- Cyclomatic Complexity · UpdateDownloadStatusKt.rememberUpdateDownloadPresentation (cyclomatic 29) app/src/main/java/com/zaneschepke/wireguardautotunnel/ui/screens/support/components/UpdateDownloadStatus.kt
- Cognitive Complexity · UpdateDownloadStatusKt.rememberUpdateDownloadPresentation (cognitive 33) app/src/main/java/com/zaneschepke/wireguardautotunnel/ui/screens/support/components/UpdateDownloadStatus.kt
- Cognitive Complexity · ThemeKt.WireguardAutoTunnelTheme (cognitive 16) app/src/main/java/com/zaneschepke/wireguardautotunnel/ui/theme/Theme.kt
- God Classes · MethodTooLong: AndroidIntegrationsScreenKt.AndroidIntegrationsScreen app/src/main/java/com/zaneschepke/wireguardautotunnel/ui/screens/settings/integrations/AndroidIntegrationsScreen.kt
- God Classes · MethodTooLong: WifiSettingsScreenKt.WifiSettingsScreen app/src/main/java/com/zaneschepke/wireguardautotunnel/ui/screens/autotunnel/wifi/WifiSettingsScreen.kt
- God Classes · FileTooLong: components/currentBackStackEntryAsNavbarState.kt app/src/main/java/com/zaneschepke/wireguardautotunnel/ui/navigation/components/currentBackStackEntryAsNavbarState.kt
- Code Duplication · Duplicated block (15–19 lines × 3) app/src/main/java/com/zaneschepke/wireguardautotunnel/ui/navigation/components/currentBackStackEntryAsNavbarState.kt
- Churn × Complexity Hotspots · Repeated repair: app/src/main/java/com/zaneschepke/wireguardautotunnel/ui/common/functions/Functions.kt app/src/main/java/com/zaneschepke/wireguardautotunnel/ui/common/functions/Functions.kt
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Change Coupling · Change-coupling hub: MainActivity.kt → DataStoreManager.kt, DataStoreAppStateRepository.kt, AppModule.kt, currentBackStackEntryAsNavbarState.kt, TunnelSettingsScreen.kt, GlobalAppUiState.kt, Constants.kt, ContextExtensions.kt app/src/main/java/com/zaneschepke/wireguardautotunnel/MainActivity.kt
- Change Coupling · Change coupling: TunnelsScreen.kt ↔ GlobalAppUiState.kt app/src/main/java/com/zaneschepke/wireguardautotunnel/ui/screens/tunnels/TunnelsScreen.kt
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
Fixed since the last survey: 2 findings
- Change Coupling · Change-coupling hub: MainActivity.kt → DataStoreManager.kt, DataStoreAppStateRepository.kt, Constants.kt, ContextExtensions.kt app/src/main/java/com/zaneschepke/wireguardautotunnel/MainActivity.kt
- Data Protection · No data-protection/encryption app/src/main/java/com/zaneschepke/wireguardautotunnel/data/entity/ProxySettings.kt
Rebuild cost: about €34,000 · Estimate
| Cost to rebuild | €11,000 to €56,000, for 186 to 589 hours of work, about 0.2 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 56. 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 | Medium: 28,571 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 logcatter.model | 2 wireguardautotunnel.domain.enums | 3 wireguardautotunnel.domain.sideeffect | 4 wireguardautotunnel.notification.AndroidNotificationService | 5 wireguardautotunnel.service | 6 wireguardautotunnel.ui.navigation | 7 wireguardautotunnel.ui.screens.tunnels.splittunnel.state | 8 wireguardautotunnel.ui.sideeffect.LocalSideEffect | 9 wireguardautotunnel.ui.theme | 10 wireguardautotunnel.util | 11 logcatter | 12 networkmonitor.AndroidNetworkMonitor | 13 networkmonitor.model | 14 wireguardautotunnel.data.entity | 15 wireguardautotunnel.domain.events | 16 wireguardautotunnel.notification.AndroidNotificationService.NotificationChannels | 17 networkmonitor.ActiveNetwork | 18 wireguardautotunnel.data.dao | 19 networkmonitor | 20 wireguardautotunnel.data | 21 wireguardautotunnel.ui.state | 22 wireguardautotunnel.domain.model | 23 wireguardautotunnel.notification | 24 wireguardautotunnel.core.orchestration.TunnelCoordinator | 25 wireguardautotunnel.domain.repository | 26 wireguardautotunnel.domain.sideeffect.GlobalSideEffect | 27 wireguardautotunnel.domain.state | 28 wireguardautotunnel.core.event | 29 wireguardautotunnel.core.tunnel | 30 wireguardautotunnel.data.repository | 31 wireguardautotunnel.service.autotunnel | 32 wireguardautotunnel.core.orchestration | 33 wireguardautotunnel.core.worker | 34 wireguardautotunnel.core.broadcast | 35 wireguardautotunnel.data.backup | 36 wireguardautotunnel.service.tile | 37 wireguardautotunnel.viewmodel | 38 wireguardautotunnel | 39 wireguardautotunnel.ui.navigation.components | 40 wireguardautotunnel.ui.screens.support.components |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 logcatter.model | ||||||||||||||||||||||||||||||||||||||||
| 2 wireguardautotunnel.domain.enums | ||||||||||||||||||||||||||||||||||||||||
| 3 wireguardautotunnel.domain.sideeffect | ||||||||||||||||||||||||||||||||||||||||
| 4 wireguardautotunnel.notification.AndroidNotificationService | ||||||||||||||||||||||||||||||||||||||||
| 5 wireguardautotunnel.service | ||||||||||||||||||||||||||||||||||||||||
| 6 wireguardautotunnel.ui.navigation | ||||||||||||||||||||||||||||||||||||||||
| 7 wireguardautotunnel.ui.screens.tunnels.splittunnel.state | ||||||||||||||||||||||||||||||||||||||||
| 8 wireguardautotunnel.ui.sideeffect.LocalSideEffect | ||||||||||||||||||||||||||||||||||||||||
| 9 wireguardautotunnel.ui.theme | ||||||||||||||||||||||||||||||||||||||||
| 10 wireguardautotunnel.util | ||||||||||||||||||||||||||||||||||||||||
| 11 logcatter | 3 | |||||||||||||||||||||||||||||||||||||||
| 12 networkmonitor.AndroidNetworkMonitor | 2 | |||||||||||||||||||||||||||||||||||||||
| 13 networkmonitor.model | 1 | |||||||||||||||||||||||||||||||||||||||
| 14 wireguardautotunnel.data.entity | 7 | |||||||||||||||||||||||||||||||||||||||
| 15 wireguardautotunnel.domain.events | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 16 wireguardautotunnel.notification.AndroidNotificationService.NotificationChannels | 6 | |||||||||||||||||||||||||||||||||||||||
| 17 networkmonitor.ActiveNetwork | 1 | 4 | ||||||||||||||||||||||||||||||||||||||
| 18 wireguardautotunnel.data.dao | 1 | 8 | ||||||||||||||||||||||||||||||||||||||
| 19 networkmonitor | 5 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 20 wireguardautotunnel.data | 7 | 8 | ||||||||||||||||||||||||||||||||||||||
| 21 wireguardautotunnel.ui.state | 1 | 2 | 1 | 1 | 2 | 20 | ||||||||||||||||||||||||||||||||||
| 22 wireguardautotunnel.domain.model | 7 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 23 wireguardautotunnel.notification | 3 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 24 wireguardautotunnel.core.orchestration.TunnelCoordinator | 1 | 9 | ||||||||||||||||||||||||||||||||||||||
| 25 wireguardautotunnel.domain.repository | 1 | 1 | 1 | 15 | ||||||||||||||||||||||||||||||||||||
| 26 wireguardautotunnel.domain.sideeffect.GlobalSideEffect | 1 | 8 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 27 wireguardautotunnel.domain.state | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 28 wireguardautotunnel.core.event | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 29 wireguardautotunnel.core.tunnel | 1 | 1 | 1 | 3 | 4 | 2 | ||||||||||||||||||||||||||||||||||
| 30 wireguardautotunnel.data.repository | 1 | 1 | 2 | 8 | 1 | 14 | 1 | 13 | ||||||||||||||||||||||||||||||||
| 31 wireguardautotunnel.service.autotunnel | 1 | 1 | 2 | 1 | 4 | 1 | 2 | |||||||||||||||||||||||||||||||||
| 32 wireguardautotunnel.core.orchestration | 2 | 2 | 1 | 1 | 1 | 3 | 2 | 21 | 1 | 1 | 3 | 1 | 1 | |||||||||||||||||||||||||||
| 33 wireguardautotunnel.core.worker | 1 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 34 wireguardautotunnel.core.broadcast | 1 | 1 | 3 | 5 | ||||||||||||||||||||||||||||||||||||
| 35 wireguardautotunnel.data.backup | 1 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 36 wireguardautotunnel.service.tile | 1 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 37 wireguardautotunnel.viewmodel | 1 | 10 | 10 | 2 | 1 | 1 | 2 | 1 | 3 | 7 | 10 | 37 | 2 | 12 | ||||||||||||||||||||||||||
| 38 wireguardautotunnel | 1 | 2 | 2 | 1 | 4 | 3 | ||||||||||||||||||||||||||||||||||
| 39 wireguardautotunnel.ui.navigation.components | 3 | 3 | 1 | |||||||||||||||||||||||||||||||||||||
| 40 wireguardautotunnel.ui.screens.support.components | 2 | 1 |
11→1 logcatter uses logcatter.model✕
- Connections
- 3 pairs of types, where a type in logcatter uses a type in logcatter.model.
- The types involved
com.zaneschepke.logcatter.LogReader→com.zaneschepke.logcatter.model.LogMessagecom.zaneschepke.logcatter.LogcatManager→com.zaneschepke.logcatter.model.LogMessagecom.zaneschepke.logcatter.LogcatStreamReader→com.zaneschepke.logcatter.model.LogMessage
- Direction
- logcatter uses logcatter.model, so a change to logcatter.model can break logcatter, while a change to logcatter can't break logcatter.model.
- Position
- Below the diagonal: logcatter uses a module listed above it, which is the healthy direction.
12→19 networkmonitor.AndroidNetworkMonitor uses networkmonitor part of a loop✕
- Connections
- 2 pairs of types, where a type in networkmonitor.AndroidNetworkMonitor uses a type in networkmonitor.
- The types involved
com.zaneschepke.networkmonitor.AndroidNetworkMonitor.NetworkData→com.zaneschepke.networkmonitor.TransportEventcom.zaneschepke.networkmonitor.AndroidNetworkMonitor.PrivateDnsSettings→com.zaneschepke.networkmonitor.PrivateDnsMode
- Direction
- networkmonitor.AndroidNetworkMonitor uses networkmonitor, so a change to networkmonitor can break networkmonitor.AndroidNetworkMonitor, while a change to networkmonitor.AndroidNetworkMonitor can't break networkmonitor.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→19 networkmonitor.model uses networkmonitor part of a loop✕
- Connections
- 1 pair of types, where a type in networkmonitor.model uses a type in networkmonitor.
- The types involved
com.zaneschepke.networkmonitor.model.StableNetworkSnapshot→com.zaneschepke.networkmonitor.ConnectivityState
- Direction
- networkmonitor.model uses networkmonitor, so a change to networkmonitor can break networkmonitor.model, while a change to networkmonitor.model can't break networkmonitor.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→2 wireguardautotunnel.data.entity uses wireguardautotunnel.domain.enums✕
- Connections
- 7 pairs of types, where a type in wireguardautotunnel.data.entity uses a type in wireguardautotunnel.domain.enums.
- The types involved
com.zaneschepke.wireguardautotunnel.data.entity.AutoTunnelSettings→com.zaneschepke.wireguardautotunnel.domain.enums.WifiDetectionMethodcom.zaneschepke.wireguardautotunnel.data.entity.DnsSettings→com.zaneschepke.wireguardautotunnel.domain.enums.BootstrapDnsProtocolcom.zaneschepke.wireguardautotunnel.data.entity.DnsSettings→com.zaneschepke.wireguardautotunnel.domain.enums.ForeignDnsPolicycom.zaneschepke.wireguardautotunnel.data.entity.DnsSettings→com.zaneschepke.wireguardautotunnel.domain.enums.SplitDnsSuffixTargetcom.zaneschepke.wireguardautotunnel.data.entity.DnsSettings→com.zaneschepke.wireguardautotunnel.domain.enums.TunnelDnsModecom.zaneschepke.wireguardautotunnel.data.entity.DnsSettings→com.zaneschepke.wireguardautotunnel.domain.enums.TunnelDnsProtocolcom.zaneschepke.wireguardautotunnel.data.entity.GeneralSettings→com.zaneschepke.wireguardautotunnel.domain.enums.TunnelMode
- Direction
- wireguardautotunnel.data.entity uses wireguardautotunnel.domain.enums, so a change to wireguardautotunnel.domain.enums can break wireguardautotunnel.data.entity, while a change to wireguardautotunnel.data.entity can't break wireguardautotunnel.domain.enums.
- Position
- Below the diagonal: wireguardautotunnel.data.entity uses a module listed above it, which is the healthy direction.
15→2 wireguardautotunnel.domain.events uses wireguardautotunnel.domain.enums✕
- Connections
- 1 pair of types, where a type in wireguardautotunnel.domain.events uses a type in wireguardautotunnel.domain.enums.
- The types involved
com.zaneschepke.wireguardautotunnel.domain.events.TunnelActionEvent→com.zaneschepke.wireguardautotunnel.domain.enums.TunnelActionSource
- Direction
- wireguardautotunnel.domain.events uses wireguardautotunnel.domain.enums, so a change to wireguardautotunnel.domain.enums can break wireguardautotunnel.domain.events, while a change to wireguardautotunnel.domain.events can't break wireguardautotunnel.domain.enums.
- Position
- Below the diagonal: wireguardautotunnel.domain.events uses a module listed above it, which is the healthy direction.
15→10 wireguardautotunnel.domain.events uses wireguardautotunnel.util✕
- Connections
- 1 pair of types, where a type in wireguardautotunnel.domain.events uses a type in wireguardautotunnel.util.
- The types involved
com.zaneschepke.wireguardautotunnel.domain.events.BackendCoreException→com.zaneschepke.wireguardautotunnel.util.StringValue
- Direction
- wireguardautotunnel.domain.events uses wireguardautotunnel.util, so a change to wireguardautotunnel.util can break wireguardautotunnel.domain.events, while a change to wireguardautotunnel.domain.events can't break wireguardautotunnel.util.
- Position
- Below the diagonal: wireguardautotunnel.domain.events uses a module listed above it, which is the healthy direction.
16→4 wireguardautotunnel.notification.AndroidNotificationService.NotificationChannels uses wireguardautotunnel.notification.AndroidNotificationService✕
- Connections
- 6 pairs of types, where a type in wireguardautotunnel.notification.AndroidNotificationService.NotificationChannels uses a type in wireguardautotunnel.notification.AndroidNotificationService.
- The types involved
com.zaneschepke.wireguardautotunnel.notification.AndroidNotificationService.NotificationChannels.App→com.zaneschepke.wireguardautotunnel.notification.AndroidNotificationService.NotificationChannelscom.zaneschepke.wireguardautotunnel.notification.AndroidNotificationService.NotificationChannels.AutoTunnel→com.zaneschepke.wireguardautotunnel.notification.AndroidNotificationService.NotificationChannelscom.zaneschepke.wireguardautotunnel.notification.AndroidNotificationService.NotificationChannels.Companion→com.zaneschepke.wireguardautotunnel.notification.AndroidNotificationService.NotificationChannelscom.zaneschepke.wireguardautotunnel.notification.AndroidNotificationService.NotificationChannels.Errors→com.zaneschepke.wireguardautotunnel.notification.AndroidNotificationService.NotificationChannelscom.zaneschepke.wireguardautotunnel.notification.AndroidNotificationService.NotificationChannels.Events→com.zaneschepke.wireguardautotunnel.notification.AndroidNotificationService.NotificationChannelscom.zaneschepke.wireguardautotunnel.notification.AndroidNotificationService.NotificationChannels.Tunnel→com.zaneschepke.wireguardautotunnel.notification.AndroidNotificationService.NotificationChannels
- Direction
- wireguardautotunnel.notification.AndroidNotificationService.NotificationChannels uses wireguardautotunnel.notification.AndroidNotificationService, so a change to wireguardautotunnel.notification.AndroidNotificationService can break wireguardautotunnel.notification.AndroidNotificationService.NotificationChannels, while a change to wireguardautotunnel.notification.AndroidNotificationService.NotificationChannels can't break wireguardautotunnel.notification.AndroidNotificationService.
- Position
- Below the diagonal: wireguardautotunnel.notification.AndroidNotificationService.NotificationChannels uses a module listed above it, which is the healthy direction.
17→13 networkmonitor.ActiveNetwork uses networkmonitor.model✕
- Connections
- 1 pair of types, where a type in networkmonitor.ActiveNetwork uses a type in networkmonitor.model.
- The types involved
com.zaneschepke.networkmonitor.ActiveNetwork.Wifi→com.zaneschepke.networkmonitor.model.LinkPropertiesSnapshot
- Direction
- networkmonitor.ActiveNetwork uses networkmonitor.model, so a change to networkmonitor.model can break networkmonitor.ActiveNetwork, while a change to networkmonitor.ActiveNetwork can't break networkmonitor.model.
- Position
- Below the diagonal: networkmonitor.ActiveNetwork uses a module listed above it, which is the healthy direction.
17→19 networkmonitor.ActiveNetwork uses networkmonitor part of a loop✕
- Connections
- 4 pairs of types, where a type in networkmonitor.ActiveNetwork uses a type in networkmonitor.
- The types involved
com.zaneschepke.networkmonitor.ActiveNetwork.Cellular→com.zaneschepke.networkmonitor.ActiveNetworkcom.zaneschepke.networkmonitor.ActiveNetwork.Disconnected→com.zaneschepke.networkmonitor.ActiveNetworkcom.zaneschepke.networkmonitor.ActiveNetwork.Ethernet→com.zaneschepke.networkmonitor.ActiveNetworkcom.zaneschepke.networkmonitor.ActiveNetwork.Wifi→com.zaneschepke.networkmonitor.ActiveNetwork
- Direction
- networkmonitor.ActiveNetwork uses networkmonitor, so a change to networkmonitor can break networkmonitor.ActiveNetwork, while a change to networkmonitor.ActiveNetwork can't break networkmonitor.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→2 wireguardautotunnel.data.dao uses wireguardautotunnel.domain.enums✕
- Connections
- 1 pair of types, where a type in wireguardautotunnel.data.dao uses a type in wireguardautotunnel.domain.enums.
- The types involved
com.zaneschepke.wireguardautotunnel.data.dao.GeneralSettingsDao→com.zaneschepke.wireguardautotunnel.domain.enums.TunnelMode
- Direction
- wireguardautotunnel.data.dao uses wireguardautotunnel.domain.enums, so a change to wireguardautotunnel.domain.enums can break wireguardautotunnel.data.dao, while a change to wireguardautotunnel.data.dao can't break wireguardautotunnel.domain.enums.
- Position
- Below the diagonal: wireguardautotunnel.data.dao uses a module listed above it, which is the healthy direction.
18→14 wireguardautotunnel.data.dao uses wireguardautotunnel.data.entity✕
- Connections
- 8 pairs of types, where a type in wireguardautotunnel.data.dao uses a type in wireguardautotunnel.data.entity.
- The types involved
com.zaneschepke.wireguardautotunnel.data.dao.AutoTunnelSettingsDao→com.zaneschepke.wireguardautotunnel.data.entity.AutoTunnelSettingscom.zaneschepke.wireguardautotunnel.data.dao.DnsSettingsDao→com.zaneschepke.wireguardautotunnel.data.entity.DnsSettingscom.zaneschepke.wireguardautotunnel.data.dao.GeneralSettingsDao→com.zaneschepke.wireguardautotunnel.data.entity.GeneralSettingscom.zaneschepke.wireguardautotunnel.data.dao.LockdownSettingsDao→com.zaneschepke.wireguardautotunnel.data.entity.LockdownSettingscom.zaneschepke.wireguardautotunnel.data.dao.MonitoringSettingsDao→com.zaneschepke.wireguardautotunnel.data.entity.MonitoringSettingscom.zaneschepke.wireguardautotunnel.data.dao.ProxySettingsDao→com.zaneschepke.wireguardautotunnel.data.entity.ProxySettingscom.zaneschepke.wireguardautotunnel.data.dao.TunnelConfigDao→com.zaneschepke.wireguardautotunnel.data.entity.TunnelConfigcom.zaneschepke.wireguardautotunnel.data.dao.TunnelGroupDao→com.zaneschepke.wireguardautotunnel.data.entity.TunnelGroup
- Direction
- wireguardautotunnel.data.dao uses wireguardautotunnel.data.entity, so a change to wireguardautotunnel.data.entity can break wireguardautotunnel.data.dao, while a change to wireguardautotunnel.data.dao can't break wireguardautotunnel.data.entity.
- Position
- Below the diagonal: wireguardautotunnel.data.dao uses a module listed above it, which is the healthy direction.
19→12 networkmonitor uses networkmonitor.AndroidNetworkMonitor✕
- Connections
- 5 pairs of types, where a type in networkmonitor uses a type in networkmonitor.AndroidNetworkMonitor.
- The types involved
com.zaneschepke.networkmonitor.AndroidNetworkMonitor→com.zaneschepke.networkmonitor.AndroidNetworkMonitor.ConfigurationListenercom.zaneschepke.networkmonitor.AndroidNetworkMonitor→com.zaneschepke.networkmonitor.AndroidNetworkMonitor.NetworkDatacom.zaneschepke.networkmonitor.AndroidNetworkMonitor→com.zaneschepke.networkmonitor.AndroidNetworkMonitor.PrivateDnsSettingscom.zaneschepke.networkmonitor.AndroidNetworkMonitor→com.zaneschepke.networkmonitor.AndroidNetworkMonitor.WifiDetailscom.zaneschepke.networkmonitor.AndroidNetworkMonitor→com.zaneschepke.networkmonitor.AndroidNetworkMonitor.WifiDetectionMethod
- Direction
- networkmonitor uses networkmonitor.AndroidNetworkMonitor, so a change to networkmonitor.AndroidNetworkMonitor can break networkmonitor, while a change to networkmonitor can't break networkmonitor.AndroidNetworkMonitor.
- Position
- Below the diagonal: networkmonitor uses a module listed above it, which is the healthy direction.
19→13 networkmonitor uses networkmonitor.model✕
- Connections
- 1 pair of types, where a type in networkmonitor uses a type in networkmonitor.model.
- The types involved
com.zaneschepke.networkmonitor.StableNetworkEngine→com.zaneschepke.networkmonitor.model.StableNetworkSnapshot
- Direction
- networkmonitor uses networkmonitor.model, so a change to networkmonitor.model can break networkmonitor, while a change to networkmonitor can't break networkmonitor.model.
- Position
- Below the diagonal: networkmonitor uses a module listed above it, which is the healthy direction.
19→17 networkmonitor uses networkmonitor.ActiveNetwork✕
- Connections
- 1 pair of types, where a type in networkmonitor uses a type in networkmonitor.ActiveNetwork.
- The types involved
com.zaneschepke.networkmonitor.AndroidNetworkMonitor→com.zaneschepke.networkmonitor.ActiveNetwork.Wifi
- Direction
- networkmonitor uses networkmonitor.ActiveNetwork, so a change to networkmonitor.ActiveNetwork can break networkmonitor, while a change to networkmonitor can't break networkmonitor.ActiveNetwork.
- Position
- Below the diagonal: networkmonitor uses a module listed above it, which is the healthy direction.
20→2 wireguardautotunnel.data uses wireguardautotunnel.domain.enums✕
- Connections
- 7 pairs of types, where a type in wireguardautotunnel.data uses a type in wireguardautotunnel.domain.enums.
- The types involved
com.zaneschepke.wireguardautotunnel.data.DatabaseConverters→com.zaneschepke.wireguardautotunnel.domain.enums.BootstrapDnsProtocolcom.zaneschepke.wireguardautotunnel.data.DatabaseConverters→com.zaneschepke.wireguardautotunnel.domain.enums.ForeignDnsPolicycom.zaneschepke.wireguardautotunnel.data.DatabaseConverters→com.zaneschepke.wireguardautotunnel.domain.enums.SplitDnsSuffixTargetcom.zaneschepke.wireguardautotunnel.data.DatabaseConverters→com.zaneschepke.wireguardautotunnel.domain.enums.TunnelDnsModecom.zaneschepke.wireguardautotunnel.data.DatabaseConverters→com.zaneschepke.wireguardautotunnel.domain.enums.TunnelDnsProtocolcom.zaneschepke.wireguardautotunnel.data.DatabaseConverters→com.zaneschepke.wireguardautotunnel.domain.enums.TunnelModecom.zaneschepke.wireguardautotunnel.data.DatabaseConverters→com.zaneschepke.wireguardautotunnel.domain.enums.WifiDetectionMethod
- Direction
- wireguardautotunnel.data uses wireguardautotunnel.domain.enums, so a change to wireguardautotunnel.domain.enums can break wireguardautotunnel.data, while a change to wireguardautotunnel.data can't break wireguardautotunnel.domain.enums.
- Position
- Below the diagonal: wireguardautotunnel.data uses a module listed above it, which is the healthy direction.
20→18 wireguardautotunnel.data uses wireguardautotunnel.data.dao✕
- Connections
- 8 pairs of types, where a type in wireguardautotunnel.data uses a type in wireguardautotunnel.data.dao.
- The types involved
com.zaneschepke.wireguardautotunnel.data.AppDatabase→com.zaneschepke.wireguardautotunnel.data.dao.AutoTunnelSettingsDaocom.zaneschepke.wireguardautotunnel.data.AppDatabase→com.zaneschepke.wireguardautotunnel.data.dao.DnsSettingsDaocom.zaneschepke.wireguardautotunnel.data.AppDatabase→com.zaneschepke.wireguardautotunnel.data.dao.GeneralSettingsDaocom.zaneschepke.wireguardautotunnel.data.AppDatabase→com.zaneschepke.wireguardautotunnel.data.dao.LockdownSettingsDaocom.zaneschepke.wireguardautotunnel.data.AppDatabase→com.zaneschepke.wireguardautotunnel.data.dao.MonitoringSettingsDaocom.zaneschepke.wireguardautotunnel.data.AppDatabase→com.zaneschepke.wireguardautotunnel.data.dao.ProxySettingsDaocom.zaneschepke.wireguardautotunnel.data.AppDatabase→com.zaneschepke.wireguardautotunnel.data.dao.TunnelConfigDaocom.zaneschepke.wireguardautotunnel.data.AppDatabase→com.zaneschepke.wireguardautotunnel.data.dao.TunnelGroupDao
- Direction
- wireguardautotunnel.data uses wireguardautotunnel.data.dao, so a change to wireguardautotunnel.data.dao can break wireguardautotunnel.data, while a change to wireguardautotunnel.data can't break wireguardautotunnel.data.dao.
- Position
- Below the diagonal: wireguardautotunnel.data uses a module listed above it, which is the healthy direction.
21→1 wireguardautotunnel.ui.state uses logcatter.model✕
- Connections
- 1 pair of types, where a type in wireguardautotunnel.ui.state uses a type in logcatter.model.
- The types involved
com.zaneschepke.wireguardautotunnel.ui.state.LoggerUiState→com.zaneschepke.logcatter.model.LogMessage
- Direction
- wireguardautotunnel.ui.state uses logcatter.model, so a change to logcatter.model can break wireguardautotunnel.ui.state, while a change to wireguardautotunnel.ui.state can't break logcatter.model.
- Position
- Below the diagonal: wireguardautotunnel.ui.state uses a module listed above it, which is the healthy direction.
21→2 wireguardautotunnel.ui.state uses wireguardautotunnel.domain.enums✕
- Connections
- 2 pairs of types, where a type in wireguardautotunnel.ui.state uses a type in wireguardautotunnel.domain.enums.
- The types involved
com.zaneschepke.wireguardautotunnel.ui.state.GlobalAppUiState→com.zaneschepke.wireguardautotunnel.domain.enums.TunnelModecom.zaneschepke.wireguardautotunnel.ui.state.MonitoringUiState→com.zaneschepke.wireguardautotunnel.domain.enums.StatisticRefresh
- Direction
- wireguardautotunnel.ui.state uses wireguardautotunnel.domain.enums, so a change to wireguardautotunnel.domain.enums can break wireguardautotunnel.ui.state, while a change to wireguardautotunnel.ui.state can't break wireguardautotunnel.domain.enums.
- Position
- Below the diagonal: wireguardautotunnel.ui.state uses a module listed above it, which is the healthy direction.
21→7 wireguardautotunnel.ui.state uses wireguardautotunnel.ui.screens.tunnels.splittunnel.state✕
- Connections
- 1 pair of types, where a type in wireguardautotunnel.ui.state uses a type in wireguardautotunnel.ui.screens.tunnels.splittunnel.state.
- The types involved
com.zaneschepke.wireguardautotunnel.ui.state.SplitTunnelUiState→com.zaneschepke.wireguardautotunnel.ui.screens.tunnels.splittunnel.state.SplitBehavior
- Direction
- wireguardautotunnel.ui.state uses wireguardautotunnel.ui.screens.tunnels.splittunnel.state, so a change to wireguardautotunnel.ui.screens.tunnels.splittunnel.state can break wireguardautotunnel.ui.state, while a change to wireguardautotunnel.ui.state can't break wireguardautotunnel.ui.screens.tunnels.splittunnel.state.
- Position
- Below the diagonal: wireguardautotunnel.ui.state uses a module listed above it, which is the healthy direction.
21→9 wireguardautotunnel.ui.state uses wireguardautotunnel.ui.theme✕
- Connections
- 1 pair of types, where a type in wireguardautotunnel.ui.state uses a type in wireguardautotunnel.ui.theme.
- The types involved
com.zaneschepke.wireguardautotunnel.ui.state.GlobalAppUiState→com.zaneschepke.wireguardautotunnel.ui.theme.Theme
- Direction
- wireguardautotunnel.ui.state uses wireguardautotunnel.ui.theme, so a change to wireguardautotunnel.ui.theme can break wireguardautotunnel.ui.state, while a change to wireguardautotunnel.ui.state can't break wireguardautotunnel.ui.theme.
- Position
- Below the diagonal: wireguardautotunnel.ui.state uses a module listed above it, which is the healthy direction.
21→19 wireguardautotunnel.ui.state uses networkmonitor✕
- Connections
- 2 pairs of types, where a type in wireguardautotunnel.ui.state uses a type in networkmonitor.
- The types involved
com.zaneschepke.wireguardautotunnel.ui.state.AutoTunnelUiState→com.zaneschepke.networkmonitor.ConnectivityStatecom.zaneschepke.wireguardautotunnel.ui.state.DnsUiState→com.zaneschepke.networkmonitor.DnsInfo
- Direction
- wireguardautotunnel.ui.state uses networkmonitor, so a change to networkmonitor can break wireguardautotunnel.ui.state, while a change to wireguardautotunnel.ui.state can't break networkmonitor.
- Position
- Below the diagonal: wireguardautotunnel.ui.state uses a module listed above it, which is the healthy direction.
21→22 wireguardautotunnel.ui.state uses wireguardautotunnel.domain.model part of a loop✕
- Connections
- 20 pairs of types, where a type in wireguardautotunnel.ui.state uses a type in wireguardautotunnel.domain.model.
- The types involved
com.zaneschepke.wireguardautotunnel.ui.state.AutoTunnelUiState→com.zaneschepke.wireguardautotunnel.domain.model.AutoTunnelSettingscom.zaneschepke.wireguardautotunnel.ui.state.AutoTunnelUiState→com.zaneschepke.wireguardautotunnel.domain.model.TunnelConfigcom.zaneschepke.wireguardautotunnel.ui.state.ConfigUiState→com.zaneschepke.wireguardautotunnel.domain.model.TunnelConfigcom.zaneschepke.wireguardautotunnel.ui.state.DnsUiState→com.zaneschepke.wireguardautotunnel.domain.model.DnsSettingscom.zaneschepke.wireguardautotunnel.ui.state.DnsUiState→com.zaneschepke.wireguardautotunnel.domain.model.TunnelConfigcom.zaneschepke.wireguardautotunnel.ui.state.LockdownSettingsUiState→com.zaneschepke.wireguardautotunnel.domain.model.LockdownSettingscom.zaneschepke.wireguardautotunnel.ui.state.LoggerUiState→com.zaneschepke.wireguardautotunnel.domain.model.MonitoringSettingscom.zaneschepke.wireguardautotunnel.ui.state.ProxySettingsUiState→com.zaneschepke.wireguardautotunnel.domain.model.ProxySettingscom.zaneschepke.wireguardautotunnel.ui.state.SettingUiState→com.zaneschepke.wireguardautotunnel.domain.model.GeneralSettingscom.zaneschepke.wireguardautotunnel.ui.state.SettingUiState→com.zaneschepke.wireguardautotunnel.domain.model.MonitoringSettingscom.zaneschepke.wireguardautotunnel.ui.state.SettingUiState→com.zaneschepke.wireguardautotunnel.domain.model.TunnelConfigcom.zaneschepke.wireguardautotunnel.ui.state.SplitTunnelUiState→com.zaneschepke.wireguardautotunnel.domain.model.InstalledPackagecom.zaneschepke.wireguardautotunnel.ui.state.SplitTunnelUiState→com.zaneschepke.wireguardautotunnel.domain.model.TunnelConfigcom.zaneschepke.wireguardautotunnel.ui.state.SupportUiState→com.zaneschepke.wireguardautotunnel.domain.model.AppUpdatecom.zaneschepke.wireguardautotunnel.ui.state.SupportUiState→com.zaneschepke.wireguardautotunnel.domain.model.UpdateDownloadStatecom.zaneschepke.wireguardautotunnel.ui.state.TunnelListRowsKt→com.zaneschepke.wireguardautotunnel.domain.model.TunnelConfigcom.zaneschepke.wireguardautotunnel.ui.state.TunnelListRowsKt→com.zaneschepke.wireguardautotunnel.domain.model.TunnelGroupcom.zaneschepke.wireguardautotunnel.ui.state.TunnelUiState→com.zaneschepke.wireguardautotunnel.domain.model.TunnelConfigcom.zaneschepke.wireguardautotunnel.ui.state.TunnelsUiState→com.zaneschepke.wireguardautotunnel.domain.model.TunnelConfigcom.zaneschepke.wireguardautotunnel.ui.state.TunnelsUiState→com.zaneschepke.wireguardautotunnel.domain.model.TunnelGroup
- Direction
- wireguardautotunnel.ui.state uses wireguardautotunnel.domain.model, so a change to wireguardautotunnel.domain.model can break wireguardautotunnel.ui.state, while a change to wireguardautotunnel.ui.state can't break wireguardautotunnel.domain.model.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
22→2 wireguardautotunnel.domain.model uses wireguardautotunnel.domain.enums✕
- Connections
- 7 pairs of types, where a type in wireguardautotunnel.domain.model uses a type in wireguardautotunnel.domain.enums.
- The types involved
com.zaneschepke.wireguardautotunnel.domain.model.AutoTunnelSettings→com.zaneschepke.wireguardautotunnel.domain.enums.WifiDetectionMethodcom.zaneschepke.wireguardautotunnel.domain.model.DnsSettings→com.zaneschepke.wireguardautotunnel.domain.enums.BootstrapDnsProtocolcom.zaneschepke.wireguardautotunnel.domain.model.DnsSettings→com.zaneschepke.wireguardautotunnel.domain.enums.ForeignDnsPolicycom.zaneschepke.wireguardautotunnel.domain.model.DnsSettings→com.zaneschepke.wireguardautotunnel.domain.enums.SplitDnsSuffixTargetcom.zaneschepke.wireguardautotunnel.domain.model.DnsSettings→com.zaneschepke.wireguardautotunnel.domain.enums.TunnelDnsModecom.zaneschepke.wireguardautotunnel.domain.model.DnsSettings→com.zaneschepke.wireguardautotunnel.domain.enums.TunnelDnsProtocolcom.zaneschepke.wireguardautotunnel.domain.model.GeneralSettings→com.zaneschepke.wireguardautotunnel.domain.enums.TunnelMode
- Direction
- wireguardautotunnel.domain.model uses wireguardautotunnel.domain.enums, so a change to wireguardautotunnel.domain.enums can break wireguardautotunnel.domain.model, while a change to wireguardautotunnel.domain.model can't break wireguardautotunnel.domain.enums.
- Position
- Below the diagonal: wireguardautotunnel.domain.model uses a module listed above it, which is the healthy direction.
22→9 wireguardautotunnel.domain.model uses wireguardautotunnel.ui.theme✕
- Connections
- 1 pair of types, where a type in wireguardautotunnel.domain.model uses a type in wireguardautotunnel.ui.theme.
- The types involved
com.zaneschepke.wireguardautotunnel.domain.model.GeneralSettings→com.zaneschepke.wireguardautotunnel.ui.theme.Theme
- Direction
- wireguardautotunnel.domain.model uses wireguardautotunnel.ui.theme, so a change to wireguardautotunnel.ui.theme can break wireguardautotunnel.domain.model, while a change to wireguardautotunnel.domain.model can't break wireguardautotunnel.ui.theme.
- Position
- Below the diagonal: wireguardautotunnel.domain.model uses a module listed above it, which is the healthy direction.
22→21 wireguardautotunnel.domain.model uses wireguardautotunnel.ui.state✕
- Connections
- 1 pair of types, where a type in wireguardautotunnel.domain.model uses a type in wireguardautotunnel.ui.state.
- The types involved
com.zaneschepke.wireguardautotunnel.domain.model.TunnelConfig→com.zaneschepke.wireguardautotunnel.ui.state.TunnelSummary
- Direction
- wireguardautotunnel.domain.model uses wireguardautotunnel.ui.state, so a change to wireguardautotunnel.ui.state can break wireguardautotunnel.domain.model, while a change to wireguardautotunnel.domain.model can't break wireguardautotunnel.ui.state.
- Position
- Below the diagonal: wireguardautotunnel.domain.model uses a module listed above it, which is the healthy direction.
23→2 wireguardautotunnel.notification uses wireguardautotunnel.domain.enums✕
- Connections
- 3 pairs of types, where a type in wireguardautotunnel.notification uses a type in wireguardautotunnel.domain.enums.
- The types involved
com.zaneschepke.wireguardautotunnel.notification.AndroidNotificationService→com.zaneschepke.wireguardautotunnel.domain.enums.NotificationActioncom.zaneschepke.wireguardautotunnel.notification.NotificationService→com.zaneschepke.wireguardautotunnel.domain.enums.NotificationActioncom.zaneschepke.wireguardautotunnel.notification.TunnelNotificationLine→com.zaneschepke.wireguardautotunnel.domain.enums.TunnelActionSource
- Direction
- wireguardautotunnel.notification uses wireguardautotunnel.domain.enums, so a change to wireguardautotunnel.domain.enums can break wireguardautotunnel.notification, while a change to wireguardautotunnel.notification can't break wireguardautotunnel.domain.enums.
- Position
- Below the diagonal: wireguardautotunnel.notification uses a module listed above it, which is the healthy direction.
23→4 wireguardautotunnel.notification uses wireguardautotunnel.notification.AndroidNotificationService✕
- Connections
- 2 pairs of types, where a type in wireguardautotunnel.notification uses a type in wireguardautotunnel.notification.AndroidNotificationService.
- The types involved
com.zaneschepke.wireguardautotunnel.notification.AndroidNotificationService→com.zaneschepke.wireguardautotunnel.notification.AndroidNotificationService.NotificationChannelscom.zaneschepke.wireguardautotunnel.notification.NotificationService→com.zaneschepke.wireguardautotunnel.notification.AndroidNotificationService.NotificationChannels
- Direction
- wireguardautotunnel.notification uses wireguardautotunnel.notification.AndroidNotificationService, so a change to wireguardautotunnel.notification.AndroidNotificationService can break wireguardautotunnel.notification, while a change to wireguardautotunnel.notification can't break wireguardautotunnel.notification.AndroidNotificationService.
- Position
- Below the diagonal: wireguardautotunnel.notification uses a module listed above it, which is the healthy direction.
23→16 wireguardautotunnel.notification uses wireguardautotunnel.notification.AndroidNotificationService.NotificationChannels✕
- Connections
- 1 pair of types, where a type in wireguardautotunnel.notification uses a type in wireguardautotunnel.notification.AndroidNotificationService.NotificationChannels.
- The types involved
com.zaneschepke.wireguardautotunnel.notification.AndroidTunnelNotificationService→com.zaneschepke.wireguardautotunnel.notification.AndroidNotificationService.NotificationChannels.Tunnel
- Direction
- wireguardautotunnel.notification uses wireguardautotunnel.notification.AndroidNotificationService.NotificationChannels, so a change to wireguardautotunnel.notification.AndroidNotificationService.NotificationChannels can break wireguardautotunnel.notification, while a change to wireguardautotunnel.notification can't break wireguardautotunnel.notification.AndroidNotificationService.NotificationChannels.
- Position
- Below the diagonal: wireguardautotunnel.notification uses a module listed above it, which is the healthy direction.
23→21 wireguardautotunnel.notification uses wireguardautotunnel.ui.state✕
- Connections
- 1 pair of types, where a type in wireguardautotunnel.notification uses a type in wireguardautotunnel.ui.state.
- The types involved
com.zaneschepke.wireguardautotunnel.notification.TunnelNotificationLine→com.zaneschepke.wireguardautotunnel.ui.state.DisplayTunnelState
- Direction
- wireguardautotunnel.notification uses wireguardautotunnel.ui.state, so a change to wireguardautotunnel.ui.state can break wireguardautotunnel.notification, while a change to wireguardautotunnel.notification can't break wireguardautotunnel.ui.state.
- Position
- Below the diagonal: wireguardautotunnel.notification uses a module listed above it, which is the healthy direction.
24→2 wireguardautotunnel.core.orchestration.TunnelCoordinator uses wireguardautotunnel.domain.enums✕
- Connections
- 1 pair of types, where a type in wireguardautotunnel.core.orchestration.TunnelCoordinator uses a type in wireguardautotunnel.domain.enums.
- The types involved
com.zaneschepke.wireguardautotunnel.core.orchestration.TunnelCoordinator.Exclusive→com.zaneschepke.wireguardautotunnel.domain.enums.TunnelActionSource
- Direction
- wireguardautotunnel.core.orchestration.TunnelCoordinator uses wireguardautotunnel.domain.enums, so a change to wireguardautotunnel.domain.enums can break wireguardautotunnel.core.orchestration.TunnelCoordinator, while a change to wireguardautotunnel.core.orchestration.TunnelCoordinator can't break wireguardautotunnel.domain.enums.
- Position
- Below the diagonal: wireguardautotunnel.core.orchestration.TunnelCoordinator uses a module listed above it, which is the healthy direction.
24→22 wireguardautotunnel.core.orchestration.TunnelCoordinator uses wireguardautotunnel.domain.model✕
- Connections
- 9 pairs of types, where a type in wireguardautotunnel.core.orchestration.TunnelCoordinator uses a type in wireguardautotunnel.domain.model.
- The types involved
com.zaneschepke.wireguardautotunnel.core.orchestration.TunnelCoordinator.Exclusive→com.zaneschepke.wireguardautotunnel.domain.model.TunnelConfigcom.zaneschepke.wireguardautotunnel.core.orchestration.TunnelCoordinator.LiveTunnelFeaturePayload→com.zaneschepke.wireguardautotunnel.domain.model.GeneralSettingscom.zaneschepke.wireguardautotunnel.core.orchestration.TunnelCoordinator.LiveTunnelFeaturePayload→com.zaneschepke.wireguardautotunnel.domain.model.MonitoringSettingscom.zaneschepke.wireguardautotunnel.core.orchestration.TunnelCoordinator.LiveTunnelFeaturePayload→com.zaneschepke.wireguardautotunnel.domain.model.TunnelConfigcom.zaneschepke.wireguardautotunnel.core.orchestration.TunnelCoordinator.RuntimeSettingsSnapshot→com.zaneschepke.wireguardautotunnel.domain.model.DnsSettingscom.zaneschepke.wireguardautotunnel.core.orchestration.TunnelCoordinator.RuntimeSettingsSnapshot→com.zaneschepke.wireguardautotunnel.domain.model.GeneralSettingscom.zaneschepke.wireguardautotunnel.core.orchestration.TunnelCoordinator.RuntimeSettingsSnapshot→com.zaneschepke.wireguardautotunnel.domain.model.LockdownSettingscom.zaneschepke.wireguardautotunnel.core.orchestration.TunnelCoordinator.RuntimeSettingsSnapshot→com.zaneschepke.wireguardautotunnel.domain.model.MonitoringSettingscom.zaneschepke.wireguardautotunnel.core.orchestration.TunnelCoordinator.RuntimeSettingsSnapshot→com.zaneschepke.wireguardautotunnel.domain.model.ProxySettings
- Direction
- wireguardautotunnel.core.orchestration.TunnelCoordinator uses wireguardautotunnel.domain.model, so a change to wireguardautotunnel.domain.model can break wireguardautotunnel.core.orchestration.TunnelCoordinator, while a change to wireguardautotunnel.core.orchestration.TunnelCoordinator can't break wireguardautotunnel.domain.model.
- Position
- Below the diagonal: wireguardautotunnel.core.orchestration.TunnelCoordinator uses a module listed above it, which is the healthy direction.
25→2 wireguardautotunnel.domain.repository uses wireguardautotunnel.domain.enums✕
- Connections
- 1 pair of types, where a type in wireguardautotunnel.domain.repository uses a type in wireguardautotunnel.domain.enums.
- The types involved
com.zaneschepke.wireguardautotunnel.domain.repository.GeneralSettingRepository→com.zaneschepke.wireguardautotunnel.domain.enums.TunnelMode
- Direction
- wireguardautotunnel.domain.repository uses wireguardautotunnel.domain.enums, so a change to wireguardautotunnel.domain.enums can break wireguardautotunnel.domain.repository, while a change to wireguardautotunnel.domain.repository can't break wireguardautotunnel.domain.enums.
- Position
- Below the diagonal: wireguardautotunnel.domain.repository uses a module listed above it, which is the healthy direction.
25→3 wireguardautotunnel.domain.repository uses wireguardautotunnel.domain.sideeffect✕
- Connections
- 1 pair of types, where a type in wireguardautotunnel.domain.repository uses a type in wireguardautotunnel.domain.sideeffect.
- The types involved
com.zaneschepke.wireguardautotunnel.domain.repository.GlobalEffectRepository→com.zaneschepke.wireguardautotunnel.domain.sideeffect.GlobalSideEffect
- Direction
- wireguardautotunnel.domain.repository uses wireguardautotunnel.domain.sideeffect, so a change to wireguardautotunnel.domain.sideeffect can break wireguardautotunnel.domain.repository, while a change to wireguardautotunnel.domain.repository can't break wireguardautotunnel.domain.sideeffect.
- Position
- Below the diagonal: wireguardautotunnel.domain.repository uses a module listed above it, which is the healthy direction.
25→9 wireguardautotunnel.domain.repository uses wireguardautotunnel.ui.theme✕
- Connections
- 1 pair of types, where a type in wireguardautotunnel.domain.repository uses a type in wireguardautotunnel.ui.theme.
- The types involved
com.zaneschepke.wireguardautotunnel.domain.repository.GeneralSettingRepository→com.zaneschepke.wireguardautotunnel.ui.theme.Theme
- Direction
- wireguardautotunnel.domain.repository uses wireguardautotunnel.ui.theme, so a change to wireguardautotunnel.ui.theme can break wireguardautotunnel.domain.repository, while a change to wireguardautotunnel.domain.repository can't break wireguardautotunnel.ui.theme.
- Position
- Below the diagonal: wireguardautotunnel.domain.repository uses a module listed above it, which is the healthy direction.
25→22 wireguardautotunnel.domain.repository uses wireguardautotunnel.domain.model✕
- Connections
- 15 pairs of types, where a type in wireguardautotunnel.domain.repository uses a type in wireguardautotunnel.domain.model.
- The types involved
com.zaneschepke.wireguardautotunnel.domain.repository.AppStateRepository→com.zaneschepke.wireguardautotunnel.domain.model.AppStatecom.zaneschepke.wireguardautotunnel.domain.repository.AutoTunnelSettingsRepository→com.zaneschepke.wireguardautotunnel.domain.model.AutoTunnelSettingscom.zaneschepke.wireguardautotunnel.domain.repository.DnsSettingsRepository→com.zaneschepke.wireguardautotunnel.domain.model.DnsSettingscom.zaneschepke.wireguardautotunnel.domain.repository.GeneralSettingRepository→com.zaneschepke.wireguardautotunnel.domain.model.GeneralSettingscom.zaneschepke.wireguardautotunnel.domain.repository.InstalledPackageRepository→com.zaneschepke.wireguardautotunnel.domain.model.InstalledPackagecom.zaneschepke.wireguardautotunnel.domain.repository.LockdownSettingsRepository→com.zaneschepke.wireguardautotunnel.domain.model.LockdownSettingscom.zaneschepke.wireguardautotunnel.domain.repository.MonitoringSettingsRepository→com.zaneschepke.wireguardautotunnel.domain.model.MonitoringSettingscom.zaneschepke.wireguardautotunnel.domain.repository.ProxySettingsRepository→com.zaneschepke.wireguardautotunnel.domain.model.ProxySettingscom.zaneschepke.wireguardautotunnel.domain.repository.TunnelGroupRepository→com.zaneschepke.wireguardautotunnel.domain.model.TunnelGroupcom.zaneschepke.wireguardautotunnel.domain.repository.TunnelRepository→com.zaneschepke.wireguardautotunnel.domain.model.TunnelConfigcom.zaneschepke.wireguardautotunnel.domain.repository.TunnelsSelection→com.zaneschepke.wireguardautotunnel.domain.model.TunnelConfigcom.zaneschepke.wireguardautotunnel.domain.repository.TunnelsSelection→com.zaneschepke.wireguardautotunnel.domain.model.TunnelGroupcom.zaneschepke.wireguardautotunnel.domain.repository.UpdateDownloader→com.zaneschepke.wireguardautotunnel.domain.model.AppUpdatecom.zaneschepke.wireguardautotunnel.domain.repository.UpdateDownloader→com.zaneschepke.wireguardautotunnel.domain.model.UpdateDownloadStatecom.zaneschepke.wireguardautotunnel.domain.repository.UpdateRepository→com.zaneschepke.wireguardautotunnel.domain.model.AppUpdate
- Direction
- wireguardautotunnel.domain.repository uses wireguardautotunnel.domain.model, so a change to wireguardautotunnel.domain.model can break wireguardautotunnel.domain.repository, while a change to wireguardautotunnel.domain.repository can't break wireguardautotunnel.domain.model.
- Position
- Below the diagonal: wireguardautotunnel.domain.repository uses a module listed above it, which is the healthy direction.
26→2 wireguardautotunnel.domain.sideeffect.GlobalSideEffect uses wireguardautotunnel.domain.enums✕
- Connections
- 1 pair of types, where a type in wireguardautotunnel.domain.sideeffect.GlobalSideEffect uses a type in wireguardautotunnel.domain.enums.
- The types involved
com.zaneschepke.wireguardautotunnel.domain.sideeffect.GlobalSideEffect.RequestVpnPermission→com.zaneschepke.wireguardautotunnel.domain.enums.TunnelMode
- Direction
- wireguardautotunnel.domain.sideeffect.GlobalSideEffect uses wireguardautotunnel.domain.enums, so a change to wireguardautotunnel.domain.enums can break wireguardautotunnel.domain.sideeffect.GlobalSideEffect, while a change to wireguardautotunnel.domain.sideeffect.GlobalSideEffect can't break wireguardautotunnel.domain.enums.
- Position
- Below the diagonal: wireguardautotunnel.domain.sideeffect.GlobalSideEffect uses a module listed above it, which is the healthy direction.
26→3 wireguardautotunnel.domain.sideeffect.GlobalSideEffect uses wireguardautotunnel.domain.sideeffect✕
- Connections
- 8 pairs of types, where a type in wireguardautotunnel.domain.sideeffect.GlobalSideEffect uses a type in wireguardautotunnel.domain.sideeffect.
- The types involved
com.zaneschepke.wireguardautotunnel.domain.sideeffect.GlobalSideEffect.ExportFile→com.zaneschepke.wireguardautotunnel.domain.sideeffect.GlobalSideEffectcom.zaneschepke.wireguardautotunnel.domain.sideeffect.GlobalSideEffect.InstallApk→com.zaneschepke.wireguardautotunnel.domain.sideeffect.GlobalSideEffectcom.zaneschepke.wireguardautotunnel.domain.sideeffect.GlobalSideEffect.LaunchUrl→com.zaneschepke.wireguardautotunnel.domain.sideeffect.GlobalSideEffectcom.zaneschepke.wireguardautotunnel.domain.sideeffect.GlobalSideEffect.PopBackStack→com.zaneschepke.wireguardautotunnel.domain.sideeffect.GlobalSideEffectcom.zaneschepke.wireguardautotunnel.domain.sideeffect.GlobalSideEffect.RequestNotificationPermission→com.zaneschepke.wireguardautotunnel.domain.sideeffect.GlobalSideEffectcom.zaneschepke.wireguardautotunnel.domain.sideeffect.GlobalSideEffect.RequestNotificationPermission→com.zaneschepke.wireguardautotunnel.domain.sideeffect.NotificationPendingActioncom.zaneschepke.wireguardautotunnel.domain.sideeffect.GlobalSideEffect.RequestVpnPermission→com.zaneschepke.wireguardautotunnel.domain.sideeffect.GlobalSideEffectcom.zaneschepke.wireguardautotunnel.domain.sideeffect.GlobalSideEffect.Snackbar→com.zaneschepke.wireguardautotunnel.domain.sideeffect.GlobalSideEffect
- Direction
- wireguardautotunnel.domain.sideeffect.GlobalSideEffect uses wireguardautotunnel.domain.sideeffect, so a change to wireguardautotunnel.domain.sideeffect can break wireguardautotunnel.domain.sideeffect.GlobalSideEffect, while a change to wireguardautotunnel.domain.sideeffect.GlobalSideEffect can't break wireguardautotunnel.domain.sideeffect.
- Position
- Below the diagonal: wireguardautotunnel.domain.sideeffect.GlobalSideEffect uses a module listed above it, which is the healthy direction.
26→10 wireguardautotunnel.domain.sideeffect.GlobalSideEffect uses wireguardautotunnel.util✕
- Connections
- 2 pairs of types, where a type in wireguardautotunnel.domain.sideeffect.GlobalSideEffect uses a type in wireguardautotunnel.util.
- The types involved
com.zaneschepke.wireguardautotunnel.domain.sideeffect.GlobalSideEffect.ExportFile→com.zaneschepke.wireguardautotunnel.util.StringValuecom.zaneschepke.wireguardautotunnel.domain.sideeffect.GlobalSideEffect.Snackbar→com.zaneschepke.wireguardautotunnel.util.StringValue
- Direction
- wireguardautotunnel.domain.sideeffect.GlobalSideEffect uses wireguardautotunnel.util, so a change to wireguardautotunnel.util can break wireguardautotunnel.domain.sideeffect.GlobalSideEffect, while a change to wireguardautotunnel.domain.sideeffect.GlobalSideEffect can't break wireguardautotunnel.util.
- Position
- Below the diagonal: wireguardautotunnel.domain.sideeffect.GlobalSideEffect uses a module listed above it, which is the healthy direction.
26→22 wireguardautotunnel.domain.sideeffect.GlobalSideEffect uses wireguardautotunnel.domain.model✕
- Connections
- 1 pair of types, where a type in wireguardautotunnel.domain.sideeffect.GlobalSideEffect uses a type in wireguardautotunnel.domain.model.
- The types involved
com.zaneschepke.wireguardautotunnel.domain.sideeffect.GlobalSideEffect.RequestVpnPermission→com.zaneschepke.wireguardautotunnel.domain.model.TunnelConfig
- Direction
- wireguardautotunnel.domain.sideeffect.GlobalSideEffect uses wireguardautotunnel.domain.model, so a change to wireguardautotunnel.domain.model can break wireguardautotunnel.domain.sideeffect.GlobalSideEffect, while a change to wireguardautotunnel.domain.sideeffect.GlobalSideEffect can't break wireguardautotunnel.domain.model.
- Position
- Below the diagonal: wireguardautotunnel.domain.sideeffect.GlobalSideEffect uses a module listed above it, which is the healthy direction.
27→2 wireguardautotunnel.domain.state uses wireguardautotunnel.domain.enums✕
- Connections
- 1 pair of types, where a type in wireguardautotunnel.domain.state uses a type in wireguardautotunnel.domain.enums.
- The types involved
com.zaneschepke.wireguardautotunnel.domain.state.AutoTunnelState→com.zaneschepke.wireguardautotunnel.domain.enums.TunnelMode
- Direction
- wireguardautotunnel.domain.state uses wireguardautotunnel.domain.enums, so a change to wireguardautotunnel.domain.enums can break wireguardautotunnel.domain.state, while a change to wireguardautotunnel.domain.state can't break wireguardautotunnel.domain.enums.
- Position
- Below the diagonal: wireguardautotunnel.domain.state uses a module listed above it, which is the healthy direction.
27→19 wireguardautotunnel.domain.state uses networkmonitor✕
- Connections
- 1 pair of types, where a type in wireguardautotunnel.domain.state uses a type in networkmonitor.
- The types involved
com.zaneschepke.wireguardautotunnel.domain.state.NetworkState→com.zaneschepke.networkmonitor.ActiveNetwork
- Direction
- wireguardautotunnel.domain.state uses networkmonitor, so a change to networkmonitor can break wireguardautotunnel.domain.state, while a change to wireguardautotunnel.domain.state can't break networkmonitor.
- Position
- Below the diagonal: wireguardautotunnel.domain.state uses a module listed above it, which is the healthy direction.
27→22 wireguardautotunnel.domain.state uses wireguardautotunnel.domain.model✕
- Connections
- 2 pairs of types, where a type in wireguardautotunnel.domain.state uses a type in wireguardautotunnel.domain.model.
- The types involved
com.zaneschepke.wireguardautotunnel.domain.state.AutoTunnelState→com.zaneschepke.wireguardautotunnel.domain.model.AutoTunnelSettingscom.zaneschepke.wireguardautotunnel.domain.state.AutoTunnelState→com.zaneschepke.wireguardautotunnel.domain.model.TunnelConfig
- Direction
- wireguardautotunnel.domain.state uses wireguardautotunnel.domain.model, so a change to wireguardautotunnel.domain.model can break wireguardautotunnel.domain.state, while a change to wireguardautotunnel.domain.state can't break wireguardautotunnel.domain.model.
- Position
- Below the diagonal: wireguardautotunnel.domain.state uses a module listed above it, which is the healthy direction.
28→23 wireguardautotunnel.core.event uses wireguardautotunnel.notification✕
- Connections
- 1 pair of types, where a type in wireguardautotunnel.core.event uses a type in wireguardautotunnel.notification.
- The types involved
com.zaneschepke.wireguardautotunnel.core.event.TunnelEventDispatcher→com.zaneschepke.wireguardautotunnel.notification.TunnelNotificationService
- Direction
- wireguardautotunnel.core.event uses wireguardautotunnel.notification, so a change to wireguardautotunnel.notification can break wireguardautotunnel.core.event, while a change to wireguardautotunnel.core.event can't break wireguardautotunnel.notification.
- Position
- Below the diagonal: wireguardautotunnel.core.event uses a module listed above it, which is the healthy direction.
28→25 wireguardautotunnel.core.event uses wireguardautotunnel.domain.repository✕
- Connections
- 2 pairs of types, where a type in wireguardautotunnel.core.event uses a type in wireguardautotunnel.domain.repository.
- The types involved
com.zaneschepke.wireguardautotunnel.core.event.TunnelEventDispatcher→com.zaneschepke.wireguardautotunnel.domain.repository.GlobalEffectRepositorycom.zaneschepke.wireguardautotunnel.core.event.TunnelEventDispatcher→com.zaneschepke.wireguardautotunnel.domain.repository.TunnelRepository
- Direction
- wireguardautotunnel.core.event uses wireguardautotunnel.domain.repository, so a change to wireguardautotunnel.domain.repository can break wireguardautotunnel.core.event, while a change to wireguardautotunnel.core.event can't break wireguardautotunnel.domain.repository.
- Position
- Below the diagonal: wireguardautotunnel.core.event uses a module listed above it, which is the healthy direction.
29→2 wireguardautotunnel.core.tunnel uses wireguardautotunnel.domain.enums✕
- Connections
- 1 pair of types, where a type in wireguardautotunnel.core.tunnel uses a type in wireguardautotunnel.domain.enums.
- The types involved
com.zaneschepke.wireguardautotunnel.core.tunnel.TunnelOriginHolder→com.zaneschepke.wireguardautotunnel.domain.enums.TunnelActionSource
- Direction
- wireguardautotunnel.core.tunnel uses wireguardautotunnel.domain.enums, so a change to wireguardautotunnel.domain.enums can break wireguardautotunnel.core.tunnel, while a change to wireguardautotunnel.core.tunnel can't break wireguardautotunnel.domain.enums.
- Position
- Below the diagonal: wireguardautotunnel.core.tunnel uses a module listed above it, which is the healthy direction.
29→4 wireguardautotunnel.core.tunnel uses wireguardautotunnel.notification.AndroidNotificationService✕
- Connections
- 1 pair of types, where a type in wireguardautotunnel.core.tunnel uses a type in wireguardautotunnel.notification.AndroidNotificationService.
- The types involved
com.zaneschepke.wireguardautotunnel.core.tunnel.AppProvider→com.zaneschepke.wireguardautotunnel.notification.AndroidNotificationService.NotificationChannels
- Direction
- wireguardautotunnel.core.tunnel uses wireguardautotunnel.notification.AndroidNotificationService, so a change to wireguardautotunnel.notification.AndroidNotificationService can break wireguardautotunnel.core.tunnel, while a change to wireguardautotunnel.core.tunnel can't break wireguardautotunnel.notification.AndroidNotificationService.
- Position
- Below the diagonal: wireguardautotunnel.core.tunnel uses a module listed above it, which is the healthy direction.
29→15 wireguardautotunnel.core.tunnel uses wireguardautotunnel.domain.events✕
- Connections
- 1 pair of types, where a type in wireguardautotunnel.core.tunnel uses a type in wireguardautotunnel.domain.events.
- The types involved
com.zaneschepke.wireguardautotunnel.core.tunnel.TunnelOriginHolder→com.zaneschepke.wireguardautotunnel.domain.events.TunnelActionEvent
- Direction
- wireguardautotunnel.core.tunnel uses wireguardautotunnel.domain.events, so a change to wireguardautotunnel.domain.events can break wireguardautotunnel.core.tunnel, while a change to wireguardautotunnel.core.tunnel can't break wireguardautotunnel.domain.events.
- Position
- Below the diagonal: wireguardautotunnel.core.tunnel uses a module listed above it, which is the healthy direction.
29→22 wireguardautotunnel.core.tunnel uses wireguardautotunnel.domain.model✕
- Connections
- 3 pairs of types, where a type in wireguardautotunnel.core.tunnel uses a type in wireguardautotunnel.domain.model.
- The types involved
com.zaneschepke.wireguardautotunnel.core.tunnel.AppProvider→com.zaneschepke.wireguardautotunnel.domain.model.GeneralSettingscom.zaneschepke.wireguardautotunnel.core.tunnel.TunnelBackendProvider→com.zaneschepke.wireguardautotunnel.domain.model.LockdownSettingscom.zaneschepke.wireguardautotunnel.core.tunnel.TunnelProvider→com.zaneschepke.wireguardautotunnel.domain.model.LockdownSettings
- Direction
- wireguardautotunnel.core.tunnel uses wireguardautotunnel.domain.model, so a change to wireguardautotunnel.domain.model can break wireguardautotunnel.core.tunnel, while a change to wireguardautotunnel.core.tunnel can't break wireguardautotunnel.domain.model.
- Position
- Below the diagonal: wireguardautotunnel.core.tunnel uses a module listed above it, which is the healthy direction.
29→23 wireguardautotunnel.core.tunnel uses wireguardautotunnel.notification✕
- Connections
- 4 pairs of types, where a type in wireguardautotunnel.core.tunnel uses a type in wireguardautotunnel.notification.
- The types involved
com.zaneschepke.wireguardautotunnel.core.tunnel.AppProvider→com.zaneschepke.wireguardautotunnel.notification.NotificationServicecom.zaneschepke.wireguardautotunnel.core.tunnel.AppProvider→com.zaneschepke.wireguardautotunnel.notification.TunnelNotificationLinecom.zaneschepke.wireguardautotunnel.core.tunnel.AppProvider→com.zaneschepke.wireguardautotunnel.notification.TunnelNotificationOptionscom.zaneschepke.wireguardautotunnel.core.tunnel.AppProvider→com.zaneschepke.wireguardautotunnel.notification.TunnelNotificationService
- Direction
- wireguardautotunnel.core.tunnel uses wireguardautotunnel.notification, so a change to wireguardautotunnel.notification can break wireguardautotunnel.core.tunnel, while a change to wireguardautotunnel.core.tunnel can't break wireguardautotunnel.notification.
- Position
- Below the diagonal: wireguardautotunnel.core.tunnel uses a module listed above it, which is the healthy direction.
29→25 wireguardautotunnel.core.tunnel uses wireguardautotunnel.domain.repository✕
- Connections
- 2 pairs of types, where a type in wireguardautotunnel.core.tunnel uses a type in wireguardautotunnel.domain.repository.
- The types involved
com.zaneschepke.wireguardautotunnel.core.tunnel.AppProvider→com.zaneschepke.wireguardautotunnel.domain.repository.GeneralSettingRepositorycom.zaneschepke.wireguardautotunnel.core.tunnel.AppProvider→com.zaneschepke.wireguardautotunnel.domain.repository.TunnelRepository
- Direction
- wireguardautotunnel.core.tunnel uses wireguardautotunnel.domain.repository, so a change to wireguardautotunnel.domain.repository can break wireguardautotunnel.core.tunnel, while a change to wireguardautotunnel.core.tunnel can't break wireguardautotunnel.domain.repository.
- Position
- Below the diagonal: wireguardautotunnel.core.tunnel uses a module listed above it, which is the healthy direction.
30→2 wireguardautotunnel.data.repository uses wireguardautotunnel.domain.enums✕
- Connections
- 1 pair of types, where a type in wireguardautotunnel.data.repository uses a type in wireguardautotunnel.domain.enums.
- The types involved
com.zaneschepke.wireguardautotunnel.data.repository.RoomSettingsRepository→com.zaneschepke.wireguardautotunnel.domain.enums.TunnelMode
- Direction
- wireguardautotunnel.data.repository uses wireguardautotunnel.domain.enums, so a change to wireguardautotunnel.domain.enums can break wireguardautotunnel.data.repository, while a change to wireguardautotunnel.data.repository can't break wireguardautotunnel.domain.enums.
- Position
- Below the diagonal: wireguardautotunnel.data.repository uses a module listed above it, which is the healthy direction.
30→9 wireguardautotunnel.data.repository uses wireguardautotunnel.ui.theme✕
- Connections
- 1 pair of types, where a type in wireguardautotunnel.data.repository uses a type in wireguardautotunnel.ui.theme.
- The types involved
com.zaneschepke.wireguardautotunnel.data.repository.RoomSettingsRepository→com.zaneschepke.wireguardautotunnel.ui.theme.Theme
- Direction
- wireguardautotunnel.data.repository uses wireguardautotunnel.ui.theme, so a change to wireguardautotunnel.ui.theme can break wireguardautotunnel.data.repository, while a change to wireguardautotunnel.data.repository can't break wireguardautotunnel.ui.theme.
- Position
- Below the diagonal: wireguardautotunnel.data.repository uses a module listed above it, which is the healthy direction.
30→14 wireguardautotunnel.data.repository uses wireguardautotunnel.data.entity✕
- Connections
- 2 pairs of types, where a type in wireguardautotunnel.data.repository uses a type in wireguardautotunnel.data.entity.
- The types involved
com.zaneschepke.wireguardautotunnel.data.repository.ApkAssetSelector→com.zaneschepke.wireguardautotunnel.data.entity.Assetcom.zaneschepke.wireguardautotunnel.data.repository.ApkChoice→com.zaneschepke.wireguardautotunnel.data.entity.Asset
- Direction
- wireguardautotunnel.data.repository uses wireguardautotunnel.data.entity, so a change to wireguardautotunnel.data.entity can break wireguardautotunnel.data.repository, while a change to wireguardautotunnel.data.repository can't break wireguardautotunnel.data.entity.
- Position
- Below the diagonal: wireguardautotunnel.data.repository uses a module listed above it, which is the healthy direction.
30→18 wireguardautotunnel.data.repository uses wireguardautotunnel.data.dao✕
- Connections
- 8 pairs of types, where a type in wireguardautotunnel.data.repository uses a type in wireguardautotunnel.data.dao.
- The types involved
com.zaneschepke.wireguardautotunnel.data.repository.RoomAutoTunnelSettingsRepository→com.zaneschepke.wireguardautotunnel.data.dao.AutoTunnelSettingsDaocom.zaneschepke.wireguardautotunnel.data.repository.RoomDnsSettingsRepository→com.zaneschepke.wireguardautotunnel.data.dao.DnsSettingsDaocom.zaneschepke.wireguardautotunnel.data.repository.RoomLockdownSettingsRepository→com.zaneschepke.wireguardautotunnel.data.dao.LockdownSettingsDaocom.zaneschepke.wireguardautotunnel.data.repository.RoomMonitoringSettingsRepository→com.zaneschepke.wireguardautotunnel.data.dao.MonitoringSettingsDaocom.zaneschepke.wireguardautotunnel.data.repository.RoomProxySettingsRepository→com.zaneschepke.wireguardautotunnel.data.dao.ProxySettingsDaocom.zaneschepke.wireguardautotunnel.data.repository.RoomSettingsRepository→com.zaneschepke.wireguardautotunnel.data.dao.GeneralSettingsDaocom.zaneschepke.wireguardautotunnel.data.repository.RoomTunnelGroupRepository→com.zaneschepke.wireguardautotunnel.data.dao.TunnelGroupDaocom.zaneschepke.wireguardautotunnel.data.repository.RoomTunnelRepository→com.zaneschepke.wireguardautotunnel.data.dao.TunnelConfigDao
- Direction
- wireguardautotunnel.data.repository uses wireguardautotunnel.data.dao, so a change to wireguardautotunnel.data.dao can break wireguardautotunnel.data.repository, while a change to wireguardautotunnel.data.repository can't break wireguardautotunnel.data.dao.
- Position
- Below the diagonal: wireguardautotunnel.data.repository uses a module listed above it, which is the healthy direction.
30→20 wireguardautotunnel.data.repository uses wireguardautotunnel.data✕
- Connections
- 1 pair of types, where a type in wireguardautotunnel.data.repository uses a type in wireguardautotunnel.data.
- The types involved
com.zaneschepke.wireguardautotunnel.data.repository.DataStoreAppStateRepository→com.zaneschepke.wireguardautotunnel.data.DataStoreManager
- Direction
- wireguardautotunnel.data.repository uses wireguardautotunnel.data, so a change to wireguardautotunnel.data can break wireguardautotunnel.data.repository, while a change to wireguardautotunnel.data.repository can't break wireguardautotunnel.data.
- Position
- Below the diagonal: wireguardautotunnel.data.repository uses a module listed above it, which is the healthy direction.
30→22 wireguardautotunnel.data.repository uses wireguardautotunnel.domain.model✕
- Connections
- 14 pairs of types, where a type in wireguardautotunnel.data.repository uses a type in wireguardautotunnel.domain.model.
- The types involved
com.zaneschepke.wireguardautotunnel.data.repository.DataStoreAppStateRepository→com.zaneschepke.wireguardautotunnel.domain.model.AppStatecom.zaneschepke.wireguardautotunnel.data.repository.DownloadManagerUpdateDownloader→com.zaneschepke.wireguardautotunnel.domain.model.AppUpdatecom.zaneschepke.wireguardautotunnel.data.repository.DownloadManagerUpdateDownloader→com.zaneschepke.wireguardautotunnel.domain.model.DownloadPausecom.zaneschepke.wireguardautotunnel.data.repository.DownloadManagerUpdateDownloader→com.zaneschepke.wireguardautotunnel.domain.model.UpdateDownloadStatecom.zaneschepke.wireguardautotunnel.data.repository.GitHubUpdateRepository→com.zaneschepke.wireguardautotunnel.domain.model.AppUpdatecom.zaneschepke.wireguardautotunnel.data.repository.InstalledAndroidPackageRepository→com.zaneschepke.wireguardautotunnel.domain.model.InstalledPackagecom.zaneschepke.wireguardautotunnel.data.repository.RoomAutoTunnelSettingsRepository→com.zaneschepke.wireguardautotunnel.domain.model.AutoTunnelSettingscom.zaneschepke.wireguardautotunnel.data.repository.RoomDnsSettingsRepository→com.zaneschepke.wireguardautotunnel.domain.model.DnsSettingscom.zaneschepke.wireguardautotunnel.data.repository.RoomLockdownSettingsRepository→com.zaneschepke.wireguardautotunnel.domain.model.LockdownSettingscom.zaneschepke.wireguardautotunnel.data.repository.RoomMonitoringSettingsRepository→com.zaneschepke.wireguardautotunnel.domain.model.MonitoringSettingscom.zaneschepke.wireguardautotunnel.data.repository.RoomProxySettingsRepository→com.zaneschepke.wireguardautotunnel.domain.model.ProxySettingscom.zaneschepke.wireguardautotunnel.data.repository.RoomSettingsRepository→com.zaneschepke.wireguardautotunnel.domain.model.GeneralSettingscom.zaneschepke.wireguardautotunnel.data.repository.RoomTunnelGroupRepository→com.zaneschepke.wireguardautotunnel.domain.model.TunnelGroupcom.zaneschepke.wireguardautotunnel.data.repository.RoomTunnelRepository→com.zaneschepke.wireguardautotunnel.domain.model.TunnelConfig
- Direction
- wireguardautotunnel.data.repository uses wireguardautotunnel.domain.model, so a change to wireguardautotunnel.domain.model can break wireguardautotunnel.data.repository, while a change to wireguardautotunnel.data.repository can't break wireguardautotunnel.domain.model.
- Position
- Below the diagonal: wireguardautotunnel.data.repository uses a module listed above it, which is the healthy direction.
30→23 wireguardautotunnel.data.repository uses wireguardautotunnel.notification✕
- Connections
- 1 pair of types, where a type in wireguardautotunnel.data.repository uses a type in wireguardautotunnel.notification.
- The types involved
com.zaneschepke.wireguardautotunnel.data.repository.DownloadManagerUpdateDownloader→com.zaneschepke.wireguardautotunnel.notification.NotificationService
- Direction
- wireguardautotunnel.data.repository uses wireguardautotunnel.notification, so a change to wireguardautotunnel.notification can break wireguardautotunnel.data.repository, while a change to wireguardautotunnel.data.repository can't break wireguardautotunnel.notification.
- Position
- Below the diagonal: wireguardautotunnel.data.repository uses a module listed above it, which is the healthy direction.
30→25 wireguardautotunnel.data.repository uses wireguardautotunnel.domain.repository✕
- Connections
- 13 pairs of types, where a type in wireguardautotunnel.data.repository uses a type in wireguardautotunnel.domain.repository.
- The types involved
com.zaneschepke.wireguardautotunnel.data.repository.DataStoreAppStateRepository→com.zaneschepke.wireguardautotunnel.domain.repository.AppStateRepositorycom.zaneschepke.wireguardautotunnel.data.repository.DownloadManagerUpdateDownloader→com.zaneschepke.wireguardautotunnel.domain.repository.GlobalEffectRepositorycom.zaneschepke.wireguardautotunnel.data.repository.DownloadManagerUpdateDownloader→com.zaneschepke.wireguardautotunnel.domain.repository.UpdateDownloadercom.zaneschepke.wireguardautotunnel.data.repository.GitHubUpdateRepository→com.zaneschepke.wireguardautotunnel.domain.repository.UpdateRepositorycom.zaneschepke.wireguardautotunnel.data.repository.InstalledAndroidPackageRepository→com.zaneschepke.wireguardautotunnel.domain.repository.InstalledPackageRepositorycom.zaneschepke.wireguardautotunnel.data.repository.RoomAutoTunnelSettingsRepository→com.zaneschepke.wireguardautotunnel.domain.repository.AutoTunnelSettingsRepositorycom.zaneschepke.wireguardautotunnel.data.repository.RoomDnsSettingsRepository→com.zaneschepke.wireguardautotunnel.domain.repository.DnsSettingsRepositorycom.zaneschepke.wireguardautotunnel.data.repository.RoomLockdownSettingsRepository→com.zaneschepke.wireguardautotunnel.domain.repository.LockdownSettingsRepositorycom.zaneschepke.wireguardautotunnel.data.repository.RoomMonitoringSettingsRepository→com.zaneschepke.wireguardautotunnel.domain.repository.MonitoringSettingsRepositorycom.zaneschepke.wireguardautotunnel.data.repository.RoomProxySettingsRepository→com.zaneschepke.wireguardautotunnel.domain.repository.ProxySettingsRepositorycom.zaneschepke.wireguardautotunnel.data.repository.RoomSettingsRepository→com.zaneschepke.wireguardautotunnel.domain.repository.GeneralSettingRepositorycom.zaneschepke.wireguardautotunnel.data.repository.RoomTunnelGroupRepository→com.zaneschepke.wireguardautotunnel.domain.repository.TunnelGroupRepositorycom.zaneschepke.wireguardautotunnel.data.repository.RoomTunnelRepository→com.zaneschepke.wireguardautotunnel.domain.repository.TunnelRepository
- Direction
- wireguardautotunnel.data.repository uses wireguardautotunnel.domain.repository, so a change to wireguardautotunnel.domain.repository can break wireguardautotunnel.data.repository, while a change to wireguardautotunnel.data.repository can't break wireguardautotunnel.domain.repository.
- Position
- Below the diagonal: wireguardautotunnel.data.repository uses a module listed above it, which is the healthy direction.
31→2 wireguardautotunnel.service.autotunnel uses wireguardautotunnel.domain.enums✕
- Connections
- 1 pair of types, where a type in wireguardautotunnel.service.autotunnel uses a type in wireguardautotunnel.domain.enums.
- The types involved
com.zaneschepke.wireguardautotunnel.service.autotunnel.AutoTunnelService→com.zaneschepke.wireguardautotunnel.domain.enums.TunnelMode
- Direction
- wireguardautotunnel.service.autotunnel uses wireguardautotunnel.domain.enums, so a change to wireguardautotunnel.domain.enums can break wireguardautotunnel.service.autotunnel, while a change to wireguardautotunnel.service.autotunnel can't break wireguardautotunnel.domain.enums.
- Position
- Below the diagonal: wireguardautotunnel.service.autotunnel uses a module listed above it, which is the healthy direction.
31→19 wireguardautotunnel.service.autotunnel uses networkmonitor✕
- Connections
- 1 pair of types, where a type in wireguardautotunnel.service.autotunnel uses a type in networkmonitor.
- The types involved
com.zaneschepke.wireguardautotunnel.service.autotunnel.AutoTunnelService→com.zaneschepke.networkmonitor.StableNetworkEngine
- Direction
- wireguardautotunnel.service.autotunnel uses networkmonitor, so a change to networkmonitor can break wireguardautotunnel.service.autotunnel, while a change to wireguardautotunnel.service.autotunnel can't break networkmonitor.
- Position
- Below the diagonal: wireguardautotunnel.service.autotunnel uses a module listed above it, which is the healthy direction.
31→22 wireguardautotunnel.service.autotunnel uses wireguardautotunnel.domain.model✕
- Connections
- 2 pairs of types, where a type in wireguardautotunnel.service.autotunnel uses a type in wireguardautotunnel.domain.model.
- The types involved
com.zaneschepke.wireguardautotunnel.service.autotunnel.AutoTunnelService→com.zaneschepke.wireguardautotunnel.domain.model.AutoTunnelSettingscom.zaneschepke.wireguardautotunnel.service.autotunnel.AutoTunnelService→com.zaneschepke.wireguardautotunnel.domain.model.TunnelConfig
- Direction
- wireguardautotunnel.service.autotunnel uses wireguardautotunnel.domain.model, so a change to wireguardautotunnel.domain.model can break wireguardautotunnel.service.autotunnel, while a change to wireguardautotunnel.service.autotunnel can't break wireguardautotunnel.domain.model.
- Position
- Below the diagonal: wireguardautotunnel.service.autotunnel uses a module listed above it, which is the healthy direction.
31→23 wireguardautotunnel.service.autotunnel uses wireguardautotunnel.notification✕
- Connections
- 1 pair of types, where a type in wireguardautotunnel.service.autotunnel uses a type in wireguardautotunnel.notification.
- The types involved
com.zaneschepke.wireguardautotunnel.service.autotunnel.AutoTunnelService→com.zaneschepke.wireguardautotunnel.notification.NotificationService
- Direction
- wireguardautotunnel.service.autotunnel uses wireguardautotunnel.notification, so a change to wireguardautotunnel.notification can break wireguardautotunnel.service.autotunnel, while a change to wireguardautotunnel.service.autotunnel can't break wireguardautotunnel.notification.
- Position
- Below the diagonal: wireguardautotunnel.service.autotunnel uses a module listed above it, which is the healthy direction.
31→25 wireguardautotunnel.service.autotunnel uses wireguardautotunnel.domain.repository✕
- Connections
- 4 pairs of types, where a type in wireguardautotunnel.service.autotunnel uses a type in wireguardautotunnel.domain.repository.
- The types involved
com.zaneschepke.wireguardautotunnel.service.autotunnel.AndroidAutoTunnelHost→com.zaneschepke.wireguardautotunnel.domain.repository.TunnelRepositorycom.zaneschepke.wireguardautotunnel.service.autotunnel.AutoTunnelService→com.zaneschepke.wireguardautotunnel.domain.repository.AutoTunnelSettingsRepositorycom.zaneschepke.wireguardautotunnel.service.autotunnel.AutoTunnelService→com.zaneschepke.wireguardautotunnel.domain.repository.GeneralSettingRepositorycom.zaneschepke.wireguardautotunnel.service.autotunnel.AutoTunnelService→com.zaneschepke.wireguardautotunnel.domain.repository.TunnelRepository
- Direction
- wireguardautotunnel.service.autotunnel uses wireguardautotunnel.domain.repository, so a change to wireguardautotunnel.domain.repository can break wireguardautotunnel.service.autotunnel, while a change to wireguardautotunnel.service.autotunnel can't break wireguardautotunnel.domain.repository.
- Position
- Below the diagonal: wireguardautotunnel.service.autotunnel uses a module listed above it, which is the healthy direction.
31→27 wireguardautotunnel.service.autotunnel uses wireguardautotunnel.domain.state✕
- Connections
- 1 pair of types, where a type in wireguardautotunnel.service.autotunnel uses a type in wireguardautotunnel.domain.state.
- The types involved
com.zaneschepke.wireguardautotunnel.service.autotunnel.AutoTunnelService→com.zaneschepke.wireguardautotunnel.domain.state.AutoTunnelState
- Direction
- wireguardautotunnel.service.autotunnel uses wireguardautotunnel.domain.state, so a change to wireguardautotunnel.domain.state can break wireguardautotunnel.service.autotunnel, while a change to wireguardautotunnel.service.autotunnel can't break wireguardautotunnel.domain.state.
- Position
- Below the diagonal: wireguardautotunnel.service.autotunnel uses a module listed above it, which is the healthy direction.
31→32 wireguardautotunnel.service.autotunnel uses wireguardautotunnel.core.orchestration part of a loop✕
- Connections
- 2 pairs of types, where a type in wireguardautotunnel.service.autotunnel uses a type in wireguardautotunnel.core.orchestration.
- The types involved
com.zaneschepke.wireguardautotunnel.service.autotunnel.AndroidAutoTunnelHost→com.zaneschepke.wireguardautotunnel.core.orchestration.TunnelCoordinatorcom.zaneschepke.wireguardautotunnel.service.autotunnel.AutoTunnelService→com.zaneschepke.wireguardautotunnel.core.orchestration.TunnelCoordinator
- Direction
- wireguardautotunnel.service.autotunnel uses wireguardautotunnel.core.orchestration, so a change to wireguardautotunnel.core.orchestration can break wireguardautotunnel.service.autotunnel, while a change to wireguardautotunnel.service.autotunnel can't break wireguardautotunnel.core.orchestration.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
32→2 wireguardautotunnel.core.orchestration uses wireguardautotunnel.domain.enums✕
- Connections
- 2 pairs of types, where a type in wireguardautotunnel.core.orchestration uses a type in wireguardautotunnel.domain.enums.
- The types involved
com.zaneschepke.wireguardautotunnel.core.orchestration.TunnelBackendCoordinator→com.zaneschepke.wireguardautotunnel.domain.enums.TunnelModecom.zaneschepke.wireguardautotunnel.core.orchestration.TunnelCoordinator→com.zaneschepke.wireguardautotunnel.domain.enums.TunnelActionSource
- Direction
- wireguardautotunnel.core.orchestration uses wireguardautotunnel.domain.enums, so a change to wireguardautotunnel.domain.enums can break wireguardautotunnel.core.orchestration, while a change to wireguardautotunnel.core.orchestration can't break wireguardautotunnel.domain.enums.
- Position
- Below the diagonal: wireguardautotunnel.core.orchestration uses a module listed above it, which is the healthy direction.
32→5 wireguardautotunnel.core.orchestration uses wireguardautotunnel.service✕
- Connections
- 2 pairs of types, where a type in wireguardautotunnel.core.orchestration uses a type in wireguardautotunnel.service.
- The types involved
com.zaneschepke.wireguardautotunnel.core.orchestration.AutoTunnelCoordinator→com.zaneschepke.wireguardautotunnel.service.ServiceManagercom.zaneschepke.wireguardautotunnel.core.orchestration.TunnelCoordinator→com.zaneschepke.wireguardautotunnel.service.ServiceManager
- Direction
- wireguardautotunnel.core.orchestration uses wireguardautotunnel.service, so a change to wireguardautotunnel.service can break wireguardautotunnel.core.orchestration, while a change to wireguardautotunnel.core.orchestration can't break wireguardautotunnel.service.
- Position
- Below the diagonal: wireguardautotunnel.core.orchestration uses a module listed above it, which is the healthy direction.
32→10 wireguardautotunnel.core.orchestration uses wireguardautotunnel.util✕
- Connections
- 1 pair of types, where a type in wireguardautotunnel.core.orchestration uses a type in wireguardautotunnel.util.
- The types involved
com.zaneschepke.wireguardautotunnel.core.orchestration.FileExportCoordinator→com.zaneschepke.wireguardautotunnel.util.FileUtils
- Direction
- wireguardautotunnel.core.orchestration uses wireguardautotunnel.util, so a change to wireguardautotunnel.util can break wireguardautotunnel.core.orchestration, while a change to wireguardautotunnel.core.orchestration can't break wireguardautotunnel.util.
- Position
- Below the diagonal: wireguardautotunnel.core.orchestration uses a module listed above it, which is the healthy direction.
32→11 wireguardautotunnel.core.orchestration uses logcatter✕
- Connections
- 1 pair of types, where a type in wireguardautotunnel.core.orchestration uses a type in logcatter.
- The types involved
com.zaneschepke.wireguardautotunnel.core.orchestration.AppBoostrapCoordinator→com.zaneschepke.logcatter.LogReader
- Direction
- wireguardautotunnel.core.orchestration uses logcatter, so a change to logcatter can break wireguardautotunnel.core.orchestration, while a change to wireguardautotunnel.core.orchestration can't break logcatter.
- Position
- Below the diagonal: wireguardautotunnel.core.orchestration uses a module listed above it, which is the healthy direction.
32→15 wireguardautotunnel.core.orchestration uses wireguardautotunnel.domain.events✕
- Connections
- 1 pair of types, where a type in wireguardautotunnel.core.orchestration uses a type in wireguardautotunnel.domain.events.
- The types involved
com.zaneschepke.wireguardautotunnel.core.orchestration.TunnelCoordinator→com.zaneschepke.wireguardautotunnel.domain.events.TunnelActionEvent
- Direction
- wireguardautotunnel.core.orchestration uses wireguardautotunnel.domain.events, so a change to wireguardautotunnel.domain.events can break wireguardautotunnel.core.orchestration, while a change to wireguardautotunnel.core.orchestration can't break wireguardautotunnel.domain.events.
- Position
- Below the diagonal: wireguardautotunnel.core.orchestration uses a module listed above it, which is the healthy direction.
32→22 wireguardautotunnel.core.orchestration uses wireguardautotunnel.domain.model✕
- Connections
- 3 pairs of types, where a type in wireguardautotunnel.core.orchestration uses a type in wireguardautotunnel.domain.model.
- The types involved
com.zaneschepke.wireguardautotunnel.core.orchestration.DnsSettingsCoordinator→com.zaneschepke.wireguardautotunnel.domain.model.DnsSettingscom.zaneschepke.wireguardautotunnel.core.orchestration.TunnelCoordinator→com.zaneschepke.wireguardautotunnel.domain.model.LockdownSettingscom.zaneschepke.wireguardautotunnel.core.orchestration.TunnelCoordinator→com.zaneschepke.wireguardautotunnel.domain.model.TunnelConfig
- Direction
- wireguardautotunnel.core.orchestration uses wireguardautotunnel.domain.model, so a change to wireguardautotunnel.domain.model can break wireguardautotunnel.core.orchestration, while a change to wireguardautotunnel.core.orchestration can't break wireguardautotunnel.domain.model.
- Position
- Below the diagonal: wireguardautotunnel.core.orchestration uses a module listed above it, which is the healthy direction.
32→24 wireguardautotunnel.core.orchestration uses wireguardautotunnel.core.orchestration.TunnelCoordinator✕
- Connections
- 2 pairs of types, where a type in wireguardautotunnel.core.orchestration uses a type in wireguardautotunnel.core.orchestration.TunnelCoordinator.
- The types involved
com.zaneschepke.wireguardautotunnel.core.orchestration.TunnelCoordinator→com.zaneschepke.wireguardautotunnel.core.orchestration.TunnelCoordinator.Exclusivecom.zaneschepke.wireguardautotunnel.core.orchestration.TunnelCoordinator→com.zaneschepke.wireguardautotunnel.core.orchestration.TunnelCoordinator.RuntimeSettingsSnapshot
- Direction
- wireguardautotunnel.core.orchestration uses wireguardautotunnel.core.orchestration.TunnelCoordinator, so a change to wireguardautotunnel.core.orchestration.TunnelCoordinator can break wireguardautotunnel.core.orchestration, while a change to wireguardautotunnel.core.orchestration can't break wireguardautotunnel.core.orchestration.TunnelCoordinator.
- Position
- Below the diagonal: wireguardautotunnel.core.orchestration uses a module listed above it, which is the healthy direction.
32→25 wireguardautotunnel.core.orchestration uses wireguardautotunnel.domain.repository✕
- Connections
- 21 pairs of types, where a type in wireguardautotunnel.core.orchestration uses a type in wireguardautotunnel.domain.repository.
- The types involved
com.zaneschepke.wireguardautotunnel.core.orchestration.AppBoostrapCoordinator→com.zaneschepke.wireguardautotunnel.domain.repository.DnsSettingsRepositorycom.zaneschepke.wireguardautotunnel.core.orchestration.AppBoostrapCoordinator→com.zaneschepke.wireguardautotunnel.domain.repository.GeneralSettingRepositorycom.zaneschepke.wireguardautotunnel.core.orchestration.AppBoostrapCoordinator→com.zaneschepke.wireguardautotunnel.domain.repository.LockdownSettingsRepositorycom.zaneschepke.wireguardautotunnel.core.orchestration.AppBoostrapCoordinator→com.zaneschepke.wireguardautotunnel.domain.repository.MonitoringSettingsRepositorycom.zaneschepke.wireguardautotunnel.core.orchestration.AppBoostrapCoordinator→com.zaneschepke.wireguardautotunnel.domain.repository.TunnelRepositorycom.zaneschepke.wireguardautotunnel.core.orchestration.AutoTunnelCoordinator→com.zaneschepke.wireguardautotunnel.domain.repository.AutoTunnelSettingsRepositorycom.zaneschepke.wireguardautotunnel.core.orchestration.FileExportCoordinator→com.zaneschepke.wireguardautotunnel.domain.repository.GlobalEffectRepositorycom.zaneschepke.wireguardautotunnel.core.orchestration.ShortcutCoordinator→com.zaneschepke.wireguardautotunnel.domain.repository.GeneralSettingRepositorycom.zaneschepke.wireguardautotunnel.core.orchestration.ShortcutCoordinator→com.zaneschepke.wireguardautotunnel.domain.repository.TunnelRepositorycom.zaneschepke.wireguardautotunnel.core.orchestration.StartupCoordinator→com.zaneschepke.wireguardautotunnel.domain.repository.AppStateRepositorycom.zaneschepke.wireguardautotunnel.core.orchestration.StartupCoordinator→com.zaneschepke.wireguardautotunnel.domain.repository.GeneralSettingRepositorycom.zaneschepke.wireguardautotunnel.core.orchestration.StartupCoordinator→com.zaneschepke.wireguardautotunnel.domain.repository.TunnelRepositorycom.zaneschepke.wireguardautotunnel.core.orchestration.TunnelBackendCoordinator→com.zaneschepke.wireguardautotunnel.domain.repository.GeneralSettingRepositorycom.zaneschepke.wireguardautotunnel.core.orchestration.TunnelBackendCoordinator→com.zaneschepke.wireguardautotunnel.domain.repository.LockdownSettingsRepositorycom.zaneschepke.wireguardautotunnel.core.orchestration.TunnelCoordinator→com.zaneschepke.wireguardautotunnel.domain.repository.AppStateRepositorycom.zaneschepke.wireguardautotunnel.core.orchestration.TunnelCoordinator→com.zaneschepke.wireguardautotunnel.domain.repository.GeneralSettingRepositorycom.zaneschepke.wireguardautotunnel.core.orchestration.TunnelCoordinator→com.zaneschepke.wireguardautotunnel.domain.repository.GlobalEffectRepositorycom.zaneschepke.wireguardautotunnel.core.orchestration.TunnelCoordinator→com.zaneschepke.wireguardautotunnel.domain.repository.LockdownSettingsRepositorycom.zaneschepke.wireguardautotunnel.core.orchestration.TunnelCoordinator→com.zaneschepke.wireguardautotunnel.domain.repository.MonitoringSettingsRepositorycom.zaneschepke.wireguardautotunnel.core.orchestration.TunnelCoordinator→com.zaneschepke.wireguardautotunnel.domain.repository.ProxySettingsRepositorycom.zaneschepke.wireguardautotunnel.core.orchestration.TunnelCoordinator→com.zaneschepke.wireguardautotunnel.domain.repository.TunnelRepository
- Direction
- wireguardautotunnel.core.orchestration uses wireguardautotunnel.domain.repository, so a change to wireguardautotunnel.domain.repository can break wireguardautotunnel.core.orchestration, while a change to wireguardautotunnel.core.orchestration can't break wireguardautotunnel.domain.repository.
- Position
- Below the diagonal: wireguardautotunnel.core.orchestration uses a module listed above it, which is the healthy direction.
32→26 wireguardautotunnel.core.orchestration uses wireguardautotunnel.domain.sideeffect.GlobalSideEffect✕
- Connections
- 1 pair of types, where a type in wireguardautotunnel.core.orchestration uses a type in wireguardautotunnel.domain.sideeffect.GlobalSideEffect.
- The types involved
com.zaneschepke.wireguardautotunnel.core.orchestration.FileExportCoordinator→com.zaneschepke.wireguardautotunnel.domain.sideeffect.GlobalSideEffect.ExportFile
- Direction
- wireguardautotunnel.core.orchestration uses wireguardautotunnel.domain.sideeffect.GlobalSideEffect, so a change to wireguardautotunnel.domain.sideeffect.GlobalSideEffect can break wireguardautotunnel.core.orchestration, while a change to wireguardautotunnel.core.orchestration can't break wireguardautotunnel.domain.sideeffect.GlobalSideEffect.
- Position
- Below the diagonal: wireguardautotunnel.core.orchestration uses a module listed above it, which is the healthy direction.
32→28 wireguardautotunnel.core.orchestration uses wireguardautotunnel.core.event✕
- Connections
- 1 pair of types, where a type in wireguardautotunnel.core.orchestration uses a type in wireguardautotunnel.core.event.
- The types involved
com.zaneschepke.wireguardautotunnel.core.orchestration.TunnelCoordinator→com.zaneschepke.wireguardautotunnel.core.event.TunnelErrorEvent
- Direction
- wireguardautotunnel.core.orchestration uses wireguardautotunnel.core.event, so a change to wireguardautotunnel.core.event can break wireguardautotunnel.core.orchestration, while a change to wireguardautotunnel.core.orchestration can't break wireguardautotunnel.core.event.
- Position
- Below the diagonal: wireguardautotunnel.core.orchestration uses a module listed above it, which is the healthy direction.
32→29 wireguardautotunnel.core.orchestration uses wireguardautotunnel.core.tunnel✕
- Connections
- 3 pairs of types, where a type in wireguardautotunnel.core.orchestration uses a type in wireguardautotunnel.core.tunnel.
- The types involved
com.zaneschepke.wireguardautotunnel.core.orchestration.AppBoostrapCoordinator→com.zaneschepke.wireguardautotunnel.core.tunnel.TunnelProvidercom.zaneschepke.wireguardautotunnel.core.orchestration.TunnelBackendCoordinator→com.zaneschepke.wireguardautotunnel.core.tunnel.TunnelProvidercom.zaneschepke.wireguardautotunnel.core.orchestration.TunnelCoordinator→com.zaneschepke.wireguardautotunnel.core.tunnel.TunnelProvider
- Direction
- wireguardautotunnel.core.orchestration uses wireguardautotunnel.core.tunnel, so a change to wireguardautotunnel.core.tunnel can break wireguardautotunnel.core.orchestration, while a change to wireguardautotunnel.core.orchestration can't break wireguardautotunnel.core.tunnel.
- Position
- Below the diagonal: wireguardautotunnel.core.orchestration uses a module listed above it, which is the healthy direction.
32→30 wireguardautotunnel.core.orchestration uses wireguardautotunnel.data.repository✕
- Connections
- 1 pair of types, where a type in wireguardautotunnel.core.orchestration uses a type in wireguardautotunnel.data.repository.
- The types involved
com.zaneschepke.wireguardautotunnel.core.orchestration.TunnelCoordinator→com.zaneschepke.wireguardautotunnel.data.repository.RoomDnsSettingsRepository
- Direction
- wireguardautotunnel.core.orchestration uses wireguardautotunnel.data.repository, so a change to wireguardautotunnel.data.repository can break wireguardautotunnel.core.orchestration, while a change to wireguardautotunnel.core.orchestration can't break wireguardautotunnel.data.repository.
- Position
- Below the diagonal: wireguardautotunnel.core.orchestration uses a module listed above it, which is the healthy direction.
32→31 wireguardautotunnel.core.orchestration uses wireguardautotunnel.service.autotunnel✕
- Connections
- 1 pair of types, where a type in wireguardautotunnel.core.orchestration uses a type in wireguardautotunnel.service.autotunnel.
- The types involved
com.zaneschepke.wireguardautotunnel.core.orchestration.AutoTunnelCoordinator→com.zaneschepke.wireguardautotunnel.service.autotunnel.AutoTunnelStateHolder
- Direction
- wireguardautotunnel.core.orchestration uses wireguardautotunnel.service.autotunnel, so a change to wireguardautotunnel.service.autotunnel can break wireguardautotunnel.core.orchestration, while a change to wireguardautotunnel.core.orchestration can't break wireguardautotunnel.service.autotunnel.
- Position
- Below the diagonal: wireguardautotunnel.core.orchestration uses a module listed above it, which is the healthy direction.
33→5 wireguardautotunnel.core.worker uses wireguardautotunnel.service✕
- Connections
- 1 pair of types, where a type in wireguardautotunnel.core.worker uses a type in wireguardautotunnel.service.
- The types involved
com.zaneschepke.wireguardautotunnel.core.worker.ServiceWorker→com.zaneschepke.wireguardautotunnel.service.ServiceManager
- Direction
- wireguardautotunnel.core.worker uses wireguardautotunnel.service, so a change to wireguardautotunnel.service can break wireguardautotunnel.core.worker, while a change to wireguardautotunnel.core.worker can't break wireguardautotunnel.service.
- Position
- Below the diagonal: wireguardautotunnel.core.worker uses a module listed above it, which is the healthy direction.
33→23 wireguardautotunnel.core.worker uses wireguardautotunnel.notification✕
- Connections
- 1 pair of types, where a type in wireguardautotunnel.core.worker uses a type in wireguardautotunnel.notification.
- The types involved
com.zaneschepke.wireguardautotunnel.core.worker.UpdateCheckWorker→com.zaneschepke.wireguardautotunnel.notification.NotificationService
- Direction
- wireguardautotunnel.core.worker uses wireguardautotunnel.notification, so a change to wireguardautotunnel.notification can break wireguardautotunnel.core.worker, while a change to wireguardautotunnel.core.worker can't break wireguardautotunnel.notification.
- Position
- Below the diagonal: wireguardautotunnel.core.worker uses a module listed above it, which is the healthy direction.
33→25 wireguardautotunnel.core.worker uses wireguardautotunnel.domain.repository✕
- Connections
- 2 pairs of types, where a type in wireguardautotunnel.core.worker uses a type in wireguardautotunnel.domain.repository.
- The types involved
com.zaneschepke.wireguardautotunnel.core.worker.ServiceWorker→com.zaneschepke.wireguardautotunnel.domain.repository.AutoTunnelSettingsRepositorycom.zaneschepke.wireguardautotunnel.core.worker.UpdateCheckWorker→com.zaneschepke.wireguardautotunnel.domain.repository.UpdateRepository
- Direction
- wireguardautotunnel.core.worker uses wireguardautotunnel.domain.repository, so a change to wireguardautotunnel.domain.repository can break wireguardautotunnel.core.worker, while a change to wireguardautotunnel.core.worker can't break wireguardautotunnel.domain.repository.
- Position
- Below the diagonal: wireguardautotunnel.core.worker uses a module listed above it, which is the healthy direction.
33→31 wireguardautotunnel.core.worker uses wireguardautotunnel.service.autotunnel✕
- Connections
- 1 pair of types, where a type in wireguardautotunnel.core.worker uses a type in wireguardautotunnel.service.autotunnel.
- The types involved
com.zaneschepke.wireguardautotunnel.core.worker.ServiceWorker→com.zaneschepke.wireguardautotunnel.service.autotunnel.AutoTunnelStateHolder
- Direction
- wireguardautotunnel.core.worker uses wireguardautotunnel.service.autotunnel, so a change to wireguardautotunnel.service.autotunnel can break wireguardautotunnel.core.worker, while a change to wireguardautotunnel.core.worker can't break wireguardautotunnel.service.autotunnel.
- Position
- Below the diagonal: wireguardautotunnel.core.worker uses a module listed above it, which is the healthy direction.
34→11 wireguardautotunnel.core.broadcast uses logcatter✕
- Connections
- 1 pair of types, where a type in wireguardautotunnel.core.broadcast uses a type in logcatter.
- The types involved
com.zaneschepke.wireguardautotunnel.core.broadcast.RestartReceiver→com.zaneschepke.logcatter.LogReader
- Direction
- wireguardautotunnel.core.broadcast uses logcatter, so a change to logcatter can break wireguardautotunnel.core.broadcast, while a change to wireguardautotunnel.core.broadcast can't break logcatter.
- Position
- Below the diagonal: wireguardautotunnel.core.broadcast uses a module listed above it, which is the healthy direction.
34→22 wireguardautotunnel.core.broadcast uses wireguardautotunnel.domain.model✕
- Connections
- 1 pair of types, where a type in wireguardautotunnel.core.broadcast uses a type in wireguardautotunnel.domain.model.
- The types involved
com.zaneschepke.wireguardautotunnel.core.broadcast.RemoteControlReceiver→com.zaneschepke.wireguardautotunnel.domain.model.GeneralSettings
- Direction
- wireguardautotunnel.core.broadcast uses wireguardautotunnel.domain.model, so a change to wireguardautotunnel.domain.model can break wireguardautotunnel.core.broadcast, while a change to wireguardautotunnel.core.broadcast can't break wireguardautotunnel.domain.model.
- Position
- Below the diagonal: wireguardautotunnel.core.broadcast uses a module listed above it, which is the healthy direction.
34→25 wireguardautotunnel.core.broadcast uses wireguardautotunnel.domain.repository✕
- Connections
- 3 pairs of types, where a type in wireguardautotunnel.core.broadcast uses a type in wireguardautotunnel.domain.repository.
- The types involved
com.zaneschepke.wireguardautotunnel.core.broadcast.RemoteControlReceiver→com.zaneschepke.wireguardautotunnel.domain.repository.GeneralSettingRepositorycom.zaneschepke.wireguardautotunnel.core.broadcast.RemoteControlReceiver→com.zaneschepke.wireguardautotunnel.domain.repository.TunnelRepositorycom.zaneschepke.wireguardautotunnel.core.broadcast.RestartReceiver→com.zaneschepke.wireguardautotunnel.domain.repository.AppStateRepository
- Direction
- wireguardautotunnel.core.broadcast uses wireguardautotunnel.domain.repository, so a change to wireguardautotunnel.domain.repository can break wireguardautotunnel.core.broadcast, while a change to wireguardautotunnel.core.broadcast can't break wireguardautotunnel.domain.repository.
- Position
- Below the diagonal: wireguardautotunnel.core.broadcast uses a module listed above it, which is the healthy direction.
34→32 wireguardautotunnel.core.broadcast uses wireguardautotunnel.core.orchestration✕
- Connections
- 5 pairs of types, where a type in wireguardautotunnel.core.broadcast uses a type in wireguardautotunnel.core.orchestration.
- The types involved
com.zaneschepke.wireguardautotunnel.core.broadcast.NotificationActionReceiver→com.zaneschepke.wireguardautotunnel.core.orchestration.AutoTunnelCoordinatorcom.zaneschepke.wireguardautotunnel.core.broadcast.NotificationActionReceiver→com.zaneschepke.wireguardautotunnel.core.orchestration.TunnelCoordinatorcom.zaneschepke.wireguardautotunnel.core.broadcast.RemoteControlReceiver→com.zaneschepke.wireguardautotunnel.core.orchestration.AutoTunnelCoordinatorcom.zaneschepke.wireguardautotunnel.core.broadcast.RemoteControlReceiver→com.zaneschepke.wireguardautotunnel.core.orchestration.TunnelCoordinatorcom.zaneschepke.wireguardautotunnel.core.broadcast.RestartReceiver→com.zaneschepke.wireguardautotunnel.core.orchestration.StartupCoordinator
- Direction
- wireguardautotunnel.core.broadcast uses wireguardautotunnel.core.orchestration, so a change to wireguardautotunnel.core.orchestration can break wireguardautotunnel.core.broadcast, while a change to wireguardautotunnel.core.broadcast can't break wireguardautotunnel.core.orchestration.
- Position
- Below the diagonal: wireguardautotunnel.core.broadcast uses a module listed above it, which is the healthy direction.
35→10 wireguardautotunnel.data.backup uses wireguardautotunnel.util✕
- Connections
- 1 pair of types, where a type in wireguardautotunnel.data.backup uses a type in wireguardautotunnel.util.
- The types involved
com.zaneschepke.wireguardautotunnel.data.backup.DatabaseBackup→com.zaneschepke.wireguardautotunnel.util.FileUtils
- Direction
- wireguardautotunnel.data.backup uses wireguardautotunnel.util, so a change to wireguardautotunnel.util can break wireguardautotunnel.data.backup, while a change to wireguardautotunnel.data.backup can't break wireguardautotunnel.util.
- Position
- Below the diagonal: wireguardautotunnel.data.backup uses a module listed above it, which is the healthy direction.
35→20 wireguardautotunnel.data.backup uses wireguardautotunnel.data✕
- Connections
- 1 pair of types, where a type in wireguardautotunnel.data.backup uses a type in wireguardautotunnel.data.
- The types involved
com.zaneschepke.wireguardautotunnel.data.backup.DatabaseBackup→com.zaneschepke.wireguardautotunnel.data.AppDatabase
- Direction
- wireguardautotunnel.data.backup uses wireguardautotunnel.data, so a change to wireguardautotunnel.data can break wireguardautotunnel.data.backup, while a change to wireguardautotunnel.data.backup can't break wireguardautotunnel.data.
- Position
- Below the diagonal: wireguardautotunnel.data.backup uses a module listed above it, which is the healthy direction.
35→29 wireguardautotunnel.data.backup uses wireguardautotunnel.core.tunnel✕
- Connections
- 1 pair of types, where a type in wireguardautotunnel.data.backup uses a type in wireguardautotunnel.core.tunnel.
- The types involved
com.zaneschepke.wireguardautotunnel.data.backup.DatabaseBackup→com.zaneschepke.wireguardautotunnel.core.tunnel.TunnelProvider
- Direction
- wireguardautotunnel.data.backup uses wireguardautotunnel.core.tunnel, so a change to wireguardautotunnel.core.tunnel can break wireguardautotunnel.data.backup, while a change to wireguardautotunnel.data.backup can't break wireguardautotunnel.core.tunnel.
- Position
- Below the diagonal: wireguardautotunnel.data.backup uses a module listed above it, which is the healthy direction.
35→32 wireguardautotunnel.data.backup uses wireguardautotunnel.core.orchestration✕
- Connections
- 2 pairs of types, where a type in wireguardautotunnel.data.backup uses a type in wireguardautotunnel.core.orchestration.
- The types involved
com.zaneschepke.wireguardautotunnel.data.backup.DatabaseBackup→com.zaneschepke.wireguardautotunnel.core.orchestration.AutoTunnelCoordinatorcom.zaneschepke.wireguardautotunnel.data.backup.DatabaseBackup→com.zaneschepke.wireguardautotunnel.core.orchestration.TunnelCoordinator
- Direction
- wireguardautotunnel.data.backup uses wireguardautotunnel.core.orchestration, so a change to wireguardautotunnel.core.orchestration can break wireguardautotunnel.data.backup, while a change to wireguardautotunnel.data.backup can't break wireguardautotunnel.core.orchestration.
- Position
- Below the diagonal: wireguardautotunnel.data.backup uses a module listed above it, which is the healthy direction.
36→22 wireguardautotunnel.service.tile uses wireguardautotunnel.domain.model✕
- Connections
- 1 pair of types, where a type in wireguardautotunnel.service.tile uses a type in wireguardautotunnel.domain.model.
- The types involved
com.zaneschepke.wireguardautotunnel.service.tile.TunnelControlTile→com.zaneschepke.wireguardautotunnel.domain.model.TunnelConfig
- Direction
- wireguardautotunnel.service.tile uses wireguardautotunnel.domain.model, so a change to wireguardautotunnel.domain.model can break wireguardautotunnel.service.tile, while a change to wireguardautotunnel.service.tile can't break wireguardautotunnel.domain.model.
- Position
- Below the diagonal: wireguardautotunnel.service.tile uses a module listed above it, which is the healthy direction.
36→25 wireguardautotunnel.service.tile uses wireguardautotunnel.domain.repository✕
- Connections
- 1 pair of types, where a type in wireguardautotunnel.service.tile uses a type in wireguardautotunnel.domain.repository.
- The types involved
com.zaneschepke.wireguardautotunnel.service.tile.TunnelControlTile→com.zaneschepke.wireguardautotunnel.domain.repository.TunnelRepository
- Direction
- wireguardautotunnel.service.tile uses wireguardautotunnel.domain.repository, so a change to wireguardautotunnel.domain.repository can break wireguardautotunnel.service.tile, while a change to wireguardautotunnel.service.tile can't break wireguardautotunnel.domain.repository.
- Position
- Below the diagonal: wireguardautotunnel.service.tile uses a module listed above it, which is the healthy direction.
36→31 wireguardautotunnel.service.tile uses wireguardautotunnel.service.autotunnel✕
- Connections
- 1 pair of types, where a type in wireguardautotunnel.service.tile uses a type in wireguardautotunnel.service.autotunnel.
- The types involved
com.zaneschepke.wireguardautotunnel.service.tile.AutoTunnelControlTile→com.zaneschepke.wireguardautotunnel.service.autotunnel.AutoTunnelStateHolder
- Direction
- wireguardautotunnel.service.tile uses wireguardautotunnel.service.autotunnel, so a change to wireguardautotunnel.service.autotunnel can break wireguardautotunnel.service.tile, while a change to wireguardautotunnel.service.tile can't break wireguardautotunnel.service.autotunnel.
- Position
- Below the diagonal: wireguardautotunnel.service.tile uses a module listed above it, which is the healthy direction.
36→32 wireguardautotunnel.service.tile uses wireguardautotunnel.core.orchestration✕
- Connections
- 2 pairs of types, where a type in wireguardautotunnel.service.tile uses a type in wireguardautotunnel.core.orchestration.
- The types involved
com.zaneschepke.wireguardautotunnel.service.tile.AutoTunnelControlTile→com.zaneschepke.wireguardautotunnel.core.orchestration.AutoTunnelCoordinatorcom.zaneschepke.wireguardautotunnel.service.tile.TunnelControlTile→com.zaneschepke.wireguardautotunnel.core.orchestration.TunnelCoordinator
- Direction
- wireguardautotunnel.service.tile uses wireguardautotunnel.core.orchestration, so a change to wireguardautotunnel.core.orchestration can break wireguardautotunnel.service.tile, while a change to wireguardautotunnel.service.tile can't break wireguardautotunnel.core.orchestration.
- Position
- Below the diagonal: wireguardautotunnel.service.tile uses a module listed above it, which is the healthy direction.
37→1 wireguardautotunnel.viewmodel uses logcatter.model✕
- Connections
- 1 pair of types, where a type in wireguardautotunnel.viewmodel uses a type in logcatter.model.
- The types involved
com.zaneschepke.wireguardautotunnel.viewmodel.LoggerViewModel→com.zaneschepke.logcatter.model.LogMessage
- Direction
- wireguardautotunnel.viewmodel uses logcatter.model, so a change to logcatter.model can break wireguardautotunnel.viewmodel, while a change to wireguardautotunnel.viewmodel can't break logcatter.model.
- Position
- Below the diagonal: wireguardautotunnel.viewmodel uses a module listed above it, which is the healthy direction.
37→2 wireguardautotunnel.viewmodel uses wireguardautotunnel.domain.enums✕
- Connections
- 10 pairs of types, where a type in wireguardautotunnel.viewmodel uses a type in wireguardautotunnel.domain.enums.
- The types involved
com.zaneschepke.wireguardautotunnel.viewmodel.AutoTunnelViewModel→com.zaneschepke.wireguardautotunnel.domain.enums.TunnelModecom.zaneschepke.wireguardautotunnel.viewmodel.AutoTunnelViewModel→com.zaneschepke.wireguardautotunnel.domain.enums.WifiDetectionMethodcom.zaneschepke.wireguardautotunnel.viewmodel.ConfigEditViewModel→com.zaneschepke.wireguardautotunnel.domain.enums.MimicModecom.zaneschepke.wireguardautotunnel.viewmodel.DnsViewModel→com.zaneschepke.wireguardautotunnel.domain.enums.BootstrapDnsProtocolcom.zaneschepke.wireguardautotunnel.viewmodel.DnsViewModel→com.zaneschepke.wireguardautotunnel.domain.enums.ForeignDnsPolicycom.zaneschepke.wireguardautotunnel.viewmodel.DnsViewModel→com.zaneschepke.wireguardautotunnel.domain.enums.SplitDnsSuffixTargetcom.zaneschepke.wireguardautotunnel.viewmodel.DnsViewModel→com.zaneschepke.wireguardautotunnel.domain.enums.TunnelDnsModecom.zaneschepke.wireguardautotunnel.viewmodel.DnsViewModel→com.zaneschepke.wireguardautotunnel.domain.enums.TunnelDnsProtocolcom.zaneschepke.wireguardautotunnel.viewmodel.MonitoringViewModel→com.zaneschepke.wireguardautotunnel.domain.enums.StatisticRefreshcom.zaneschepke.wireguardautotunnel.viewmodel.SharedAppViewModel→com.zaneschepke.wireguardautotunnel.domain.enums.TunnelMode
- Direction
- wireguardautotunnel.viewmodel uses wireguardautotunnel.domain.enums, so a change to wireguardautotunnel.domain.enums can break wireguardautotunnel.viewmodel, while a change to wireguardautotunnel.viewmodel can't break wireguardautotunnel.domain.enums.
- Position
- Below the diagonal: wireguardautotunnel.viewmodel uses a module listed above it, which is the healthy direction.
37→3 wireguardautotunnel.viewmodel uses wireguardautotunnel.domain.sideeffect✕
- Connections
- 10 pairs of types, where a type in wireguardautotunnel.viewmodel uses a type in wireguardautotunnel.domain.sideeffect.
- The types involved
com.zaneschepke.wireguardautotunnel.viewmodel.AutoTunnelViewModel→com.zaneschepke.wireguardautotunnel.domain.sideeffect.GlobalSideEffectcom.zaneschepke.wireguardautotunnel.viewmodel.ConfigEditViewModel→com.zaneschepke.wireguardautotunnel.domain.sideeffect.GlobalSideEffectcom.zaneschepke.wireguardautotunnel.viewmodel.DnsViewModel→com.zaneschepke.wireguardautotunnel.domain.sideeffect.GlobalSideEffectcom.zaneschepke.wireguardautotunnel.viewmodel.LockdownViewModel→com.zaneschepke.wireguardautotunnel.domain.sideeffect.GlobalSideEffectcom.zaneschepke.wireguardautotunnel.viewmodel.LoggerViewModel→com.zaneschepke.wireguardautotunnel.domain.sideeffect.GlobalSideEffectcom.zaneschepke.wireguardautotunnel.viewmodel.ProxySettingsViewModel→com.zaneschepke.wireguardautotunnel.domain.sideeffect.GlobalSideEffectcom.zaneschepke.wireguardautotunnel.viewmodel.SettingsViewModel→com.zaneschepke.wireguardautotunnel.domain.sideeffect.GlobalSideEffectcom.zaneschepke.wireguardautotunnel.viewmodel.SharedAppViewModel→com.zaneschepke.wireguardautotunnel.domain.sideeffect.GlobalSideEffectcom.zaneschepke.wireguardautotunnel.viewmodel.SplitTunnelViewModel→com.zaneschepke.wireguardautotunnel.domain.sideeffect.GlobalSideEffectcom.zaneschepke.wireguardautotunnel.viewmodel.SupportViewModel→com.zaneschepke.wireguardautotunnel.domain.sideeffect.GlobalSideEffect
- Direction
- wireguardautotunnel.viewmodel uses wireguardautotunnel.domain.sideeffect, so a change to wireguardautotunnel.domain.sideeffect can break wireguardautotunnel.viewmodel, while a change to wireguardautotunnel.viewmodel can't break wireguardautotunnel.domain.sideeffect.
- Position
- Below the diagonal: wireguardautotunnel.viewmodel uses a module listed above it, which is the healthy direction.
37→5 wireguardautotunnel.viewmodel uses wireguardautotunnel.service✕
- Connections
- 2 pairs of types, where a type in wireguardautotunnel.viewmodel uses a type in wireguardautotunnel.service.
- The types involved
com.zaneschepke.wireguardautotunnel.viewmodel.AutoTunnelViewModel→com.zaneschepke.wireguardautotunnel.service.ServiceManagercom.zaneschepke.wireguardautotunnel.viewmodel.SharedAppViewModel→com.zaneschepke.wireguardautotunnel.service.ServiceManager
- Direction
- wireguardautotunnel.viewmodel uses wireguardautotunnel.service, so a change to wireguardautotunnel.service can break wireguardautotunnel.viewmodel, while a change to wireguardautotunnel.viewmodel can't break wireguardautotunnel.service.
- Position
- Below the diagonal: wireguardautotunnel.viewmodel uses a module listed above it, which is the healthy direction.
37→7 wireguardautotunnel.viewmodel uses wireguardautotunnel.ui.screens.tunnels.splittunnel.state✕
- Connections
- 1 pair of types, where a type in wireguardautotunnel.viewmodel uses a type in wireguardautotunnel.ui.screens.tunnels.splittunnel.state.
- The types involved
com.zaneschepke.wireguardautotunnel.viewmodel.SplitTunnelViewModel→com.zaneschepke.wireguardautotunnel.ui.screens.tunnels.splittunnel.state.SplitBehavior
- Direction
- wireguardautotunnel.viewmodel uses wireguardautotunnel.ui.screens.tunnels.splittunnel.state, so a change to wireguardautotunnel.ui.screens.tunnels.splittunnel.state can break wireguardautotunnel.viewmodel, while a change to wireguardautotunnel.viewmodel can't break wireguardautotunnel.ui.screens.tunnels.splittunnel.state.
- Position
- Below the diagonal: wireguardautotunnel.viewmodel uses a module listed above it, which is the healthy direction.
37→9 wireguardautotunnel.viewmodel uses wireguardautotunnel.ui.theme✕
- Connections
- 1 pair of types, where a type in wireguardautotunnel.viewmodel uses a type in wireguardautotunnel.ui.theme.
- The types involved
com.zaneschepke.wireguardautotunnel.viewmodel.SharedAppViewModel→com.zaneschepke.wireguardautotunnel.ui.theme.Theme
- Direction
- wireguardautotunnel.viewmodel uses wireguardautotunnel.ui.theme, so a change to wireguardautotunnel.ui.theme can break wireguardautotunnel.viewmodel, while a change to wireguardautotunnel.viewmodel can't break wireguardautotunnel.ui.theme.
- Position
- Below the diagonal: wireguardautotunnel.viewmodel uses a module listed above it, which is the healthy direction.
37→10 wireguardautotunnel.viewmodel uses wireguardautotunnel.util✕
- Connections
- 2 pairs of types, where a type in wireguardautotunnel.viewmodel uses a type in wireguardautotunnel.util.
- The types involved
com.zaneschepke.wireguardautotunnel.viewmodel.SharedAppViewModel→com.zaneschepke.wireguardautotunnel.util.FileUtilscom.zaneschepke.wireguardautotunnel.viewmodel.SharedAppViewModel→com.zaneschepke.wireguardautotunnel.util.StringValue
- Direction
- wireguardautotunnel.viewmodel uses wireguardautotunnel.util, so a change to wireguardautotunnel.util can break wireguardautotunnel.viewmodel, while a change to wireguardautotunnel.viewmodel can't break wireguardautotunnel.util.
- Position
- Below the diagonal: wireguardautotunnel.viewmodel uses a module listed above it, which is the healthy direction.
37→11 wireguardautotunnel.viewmodel uses logcatter✕
- Connections
- 1 pair of types, where a type in wireguardautotunnel.viewmodel uses a type in logcatter.
- The types involved
com.zaneschepke.wireguardautotunnel.viewmodel.LoggerViewModel→com.zaneschepke.logcatter.LogReader
- Direction
- wireguardautotunnel.viewmodel uses logcatter, so a change to logcatter can break wireguardautotunnel.viewmodel, while a change to wireguardautotunnel.viewmodel can't break logcatter.
- Position
- Below the diagonal: wireguardautotunnel.viewmodel uses a module listed above it, which is the healthy direction.
37→19 wireguardautotunnel.viewmodel uses networkmonitor✕
- Connections
- 3 pairs of types, where a type in wireguardautotunnel.viewmodel uses a type in networkmonitor.
- The types involved
com.zaneschepke.wireguardautotunnel.viewmodel.AutoTunnelViewModel→com.zaneschepke.networkmonitor.NetworkMonitorcom.zaneschepke.wireguardautotunnel.viewmodel.AutoTunnelViewModel→com.zaneschepke.networkmonitor.StableNetworkEnginecom.zaneschepke.wireguardautotunnel.viewmodel.DnsViewModel→com.zaneschepke.networkmonitor.NetworkMonitor
- Direction
- wireguardautotunnel.viewmodel uses networkmonitor, so a change to networkmonitor can break wireguardautotunnel.viewmodel, while a change to wireguardautotunnel.viewmodel can't break networkmonitor.
- Position
- Below the diagonal: wireguardautotunnel.viewmodel uses a module listed above it, which is the healthy direction.
37→21 wireguardautotunnel.viewmodel uses wireguardautotunnel.ui.state✕
- Connections
- 7 pairs of types, where a type in wireguardautotunnel.viewmodel uses a type in wireguardautotunnel.ui.state.
- The types involved
com.zaneschepke.wireguardautotunnel.viewmodel.ConfigEditSnapshot→com.zaneschepke.wireguardautotunnel.ui.state.EditableInterfacecom.zaneschepke.wireguardautotunnel.viewmodel.ConfigEditSnapshot→com.zaneschepke.wireguardautotunnel.ui.state.GlobalSettingsStatecom.zaneschepke.wireguardautotunnel.viewmodel.ConfigEditSnapshot→com.zaneschepke.wireguardautotunnel.ui.state.TunnelSummarycom.zaneschepke.wireguardautotunnel.viewmodel.ConfigEditViewModel→com.zaneschepke.wireguardautotunnel.ui.state.EditableInterfacecom.zaneschepke.wireguardautotunnel.viewmodel.ConfigEditViewModel→com.zaneschepke.wireguardautotunnel.ui.state.EditablePeercom.zaneschepke.wireguardautotunnel.viewmodel.SplitTunnelViewModel→com.zaneschepke.wireguardautotunnel.ui.state.SplitAppListSummarycom.zaneschepke.wireguardautotunnel.viewmodel.TunnelViewModel→com.zaneschepke.wireguardautotunnel.ui.state.AppliedSplitApps
- Direction
- wireguardautotunnel.viewmodel uses wireguardautotunnel.ui.state, so a change to wireguardautotunnel.ui.state can break wireguardautotunnel.viewmodel, while a change to wireguardautotunnel.viewmodel can't break wireguardautotunnel.ui.state.
- Position
- Below the diagonal: wireguardautotunnel.viewmodel uses a module listed above it, which is the healthy direction.
37→22 wireguardautotunnel.viewmodel uses wireguardautotunnel.domain.model✕
- Connections
- 10 pairs of types, where a type in wireguardautotunnel.viewmodel uses a type in wireguardautotunnel.domain.model.
- The types involved
com.zaneschepke.wireguardautotunnel.viewmodel.AutoTunnelViewModel→com.zaneschepke.wireguardautotunnel.domain.model.TunnelConfigcom.zaneschepke.wireguardautotunnel.viewmodel.ConfigEditSnapshot→com.zaneschepke.wireguardautotunnel.domain.model.TunnelConfigcom.zaneschepke.wireguardautotunnel.viewmodel.ReorderDraft→com.zaneschepke.wireguardautotunnel.domain.model.TunnelConfigcom.zaneschepke.wireguardautotunnel.viewmodel.ReorderDraft→com.zaneschepke.wireguardautotunnel.domain.model.TunnelGroupcom.zaneschepke.wireguardautotunnel.viewmodel.SharedAppViewModel→com.zaneschepke.wireguardautotunnel.domain.model.TunnelConfigcom.zaneschepke.wireguardautotunnel.viewmodel.SharedAppViewModel→com.zaneschepke.wireguardautotunnel.domain.model.TunnelGroupcom.zaneschepke.wireguardautotunnel.viewmodel.SplitTunnelViewModel→com.zaneschepke.wireguardautotunnel.domain.model.GeneralSettingscom.zaneschepke.wireguardautotunnel.viewmodel.SplitTunnelViewModel→com.zaneschepke.wireguardautotunnel.domain.model.TunnelConfigcom.zaneschepke.wireguardautotunnel.viewmodel.TunnelViewModel→com.zaneschepke.wireguardautotunnel.domain.model.GeneralSettingscom.zaneschepke.wireguardautotunnel.viewmodel.TunnelViewModel→com.zaneschepke.wireguardautotunnel.domain.model.TunnelConfig
- Direction
- wireguardautotunnel.viewmodel uses wireguardautotunnel.domain.model, so a change to wireguardautotunnel.domain.model can break wireguardautotunnel.viewmodel, while a change to wireguardautotunnel.viewmodel can't break wireguardautotunnel.domain.model.
- Position
- Below the diagonal: wireguardautotunnel.viewmodel uses a module listed above it, which is the healthy direction.
37→25 wireguardautotunnel.viewmodel uses wireguardautotunnel.domain.repository✕
- Connections
- 37 pairs of types, where a type in wireguardautotunnel.viewmodel uses a type in wireguardautotunnel.domain.repository. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.zaneschepke.wireguardautotunnel.viewmodel.AutoTunnelViewModel→com.zaneschepke.wireguardautotunnel.domain.repository.AppStateRepositorycom.zaneschepke.wireguardautotunnel.viewmodel.AutoTunnelViewModel→com.zaneschepke.wireguardautotunnel.domain.repository.AutoTunnelSettingsRepositorycom.zaneschepke.wireguardautotunnel.viewmodel.AutoTunnelViewModel→com.zaneschepke.wireguardautotunnel.domain.repository.GlobalEffectRepositorycom.zaneschepke.wireguardautotunnel.viewmodel.AutoTunnelViewModel→com.zaneschepke.wireguardautotunnel.domain.repository.TunnelRepositorycom.zaneschepke.wireguardautotunnel.viewmodel.ConfigEditViewModel→com.zaneschepke.wireguardautotunnel.domain.repository.DnsSettingsRepositorycom.zaneschepke.wireguardautotunnel.viewmodel.ConfigEditViewModel→com.zaneschepke.wireguardautotunnel.domain.repository.GeneralSettingRepositorycom.zaneschepke.wireguardautotunnel.viewmodel.ConfigEditViewModel→com.zaneschepke.wireguardautotunnel.domain.repository.GlobalEffectRepositorycom.zaneschepke.wireguardautotunnel.viewmodel.ConfigEditViewModel→com.zaneschepke.wireguardautotunnel.domain.repository.TunnelGroupRepositorycom.zaneschepke.wireguardautotunnel.viewmodel.ConfigEditViewModel→com.zaneschepke.wireguardautotunnel.domain.repository.TunnelRepositorycom.zaneschepke.wireguardautotunnel.viewmodel.DnsViewModel→com.zaneschepke.wireguardautotunnel.domain.repository.DnsSettingsRepositorycom.zaneschepke.wireguardautotunnel.viewmodel.DnsViewModel→com.zaneschepke.wireguardautotunnel.domain.repository.GlobalEffectRepositorycom.zaneschepke.wireguardautotunnel.viewmodel.DnsViewModel→com.zaneschepke.wireguardautotunnel.domain.repository.TunnelRepositorycom.zaneschepke.wireguardautotunnel.viewmodel.LockdownViewModel→com.zaneschepke.wireguardautotunnel.domain.repository.GlobalEffectRepositorycom.zaneschepke.wireguardautotunnel.viewmodel.LockdownViewModel→com.zaneschepke.wireguardautotunnel.domain.repository.LockdownSettingsRepositorycom.zaneschepke.wireguardautotunnel.viewmodel.LoggerViewModel→com.zaneschepke.wireguardautotunnel.domain.repository.GlobalEffectRepositorycom.zaneschepke.wireguardautotunnel.viewmodel.MonitoringViewModel→com.zaneschepke.wireguardautotunnel.domain.repository.MonitoringSettingsRepositorycom.zaneschepke.wireguardautotunnel.viewmodel.ProxySettingsViewModel→com.zaneschepke.wireguardautotunnel.domain.repository.GlobalEffectRepositorycom.zaneschepke.wireguardautotunnel.viewmodel.ProxySettingsViewModel→com.zaneschepke.wireguardautotunnel.domain.repository.ProxySettingsRepositorycom.zaneschepke.wireguardautotunnel.viewmodel.SettingsViewModel→com.zaneschepke.wireguardautotunnel.domain.repository.GeneralSettingRepositorycom.zaneschepke.wireguardautotunnel.viewmodel.SettingsViewModel→com.zaneschepke.wireguardautotunnel.domain.repository.GlobalEffectRepositorycom.zaneschepke.wireguardautotunnel.viewmodel.SettingsViewModel→com.zaneschepke.wireguardautotunnel.domain.repository.MonitoringSettingsRepositorycom.zaneschepke.wireguardautotunnel.viewmodel.SettingsViewModel→com.zaneschepke.wireguardautotunnel.domain.repository.TunnelRepositorycom.zaneschepke.wireguardautotunnel.viewmodel.SharedAppViewModel→com.zaneschepke.wireguardautotunnel.domain.repository.AppStateRepositorycom.zaneschepke.wireguardautotunnel.viewmodel.SharedAppViewModel→com.zaneschepke.wireguardautotunnel.domain.repository.GeneralSettingRepositorycom.zaneschepke.wireguardautotunnel.viewmodel.SharedAppViewModel→com.zaneschepke.wireguardautotunnel.domain.repository.GlobalEffectRepository
- Direction
- wireguardautotunnel.viewmodel uses wireguardautotunnel.domain.repository, so a change to wireguardautotunnel.domain.repository can break wireguardautotunnel.viewmodel, while a change to wireguardautotunnel.viewmodel can't break wireguardautotunnel.domain.repository.
- Position
- Below the diagonal: wireguardautotunnel.viewmodel uses a module listed above it, which is the healthy direction.
37→31 wireguardautotunnel.viewmodel uses wireguardautotunnel.service.autotunnel✕
- Connections
- 2 pairs of types, where a type in wireguardautotunnel.viewmodel uses a type in wireguardautotunnel.service.autotunnel.
- The types involved
com.zaneschepke.wireguardautotunnel.viewmodel.AutoTunnelViewModel→com.zaneschepke.wireguardautotunnel.service.autotunnel.AutoTunnelStateHoldercom.zaneschepke.wireguardautotunnel.viewmodel.SharedAppViewModel→com.zaneschepke.wireguardautotunnel.service.autotunnel.AutoTunnelStateHolder
- Direction
- wireguardautotunnel.viewmodel uses wireguardautotunnel.service.autotunnel, so a change to wireguardautotunnel.service.autotunnel can break wireguardautotunnel.viewmodel, while a change to wireguardautotunnel.viewmodel can't break wireguardautotunnel.service.autotunnel.
- Position
- Below the diagonal: wireguardautotunnel.viewmodel uses a module listed above it, which is the healthy direction.
37→32 wireguardautotunnel.viewmodel uses wireguardautotunnel.core.orchestration✕
- Connections
- 12 pairs of types, where a type in wireguardautotunnel.viewmodel uses a type in wireguardautotunnel.core.orchestration.
- The types involved
com.zaneschepke.wireguardautotunnel.viewmodel.AutoTunnelViewModel→com.zaneschepke.wireguardautotunnel.core.orchestration.AutoTunnelCoordinatorcom.zaneschepke.wireguardautotunnel.viewmodel.ConfigEditViewModel→com.zaneschepke.wireguardautotunnel.core.orchestration.TunnelCoordinatorcom.zaneschepke.wireguardautotunnel.viewmodel.DnsViewModel→com.zaneschepke.wireguardautotunnel.core.orchestration.DnsSettingsCoordinatorcom.zaneschepke.wireguardautotunnel.viewmodel.DnsViewModel→com.zaneschepke.wireguardautotunnel.core.orchestration.TunnelCoordinatorcom.zaneschepke.wireguardautotunnel.viewmodel.LockdownViewModel→com.zaneschepke.wireguardautotunnel.core.orchestration.TunnelCoordinatorcom.zaneschepke.wireguardautotunnel.viewmodel.ProxySettingsViewModel→com.zaneschepke.wireguardautotunnel.core.orchestration.TunnelCoordinatorcom.zaneschepke.wireguardautotunnel.viewmodel.SettingsViewModel→com.zaneschepke.wireguardautotunnel.core.orchestration.TunnelCoordinatorcom.zaneschepke.wireguardautotunnel.viewmodel.SharedAppViewModel→com.zaneschepke.wireguardautotunnel.core.orchestration.AutoTunnelCoordinatorcom.zaneschepke.wireguardautotunnel.viewmodel.SharedAppViewModel→com.zaneschepke.wireguardautotunnel.core.orchestration.TunnelBackendCoordinatorcom.zaneschepke.wireguardautotunnel.viewmodel.SharedAppViewModel→com.zaneschepke.wireguardautotunnel.core.orchestration.TunnelCoordinatorcom.zaneschepke.wireguardautotunnel.viewmodel.SplitTunnelViewModel→com.zaneschepke.wireguardautotunnel.core.orchestration.TunnelCoordinatorcom.zaneschepke.wireguardautotunnel.viewmodel.TunnelViewModel→com.zaneschepke.wireguardautotunnel.core.orchestration.TunnelCoordinator
- Direction
- wireguardautotunnel.viewmodel uses wireguardautotunnel.core.orchestration, so a change to wireguardautotunnel.core.orchestration can break wireguardautotunnel.viewmodel, while a change to wireguardautotunnel.viewmodel can't break wireguardautotunnel.core.orchestration.
- Position
- Below the diagonal: wireguardautotunnel.viewmodel uses a module listed above it, which is the healthy direction.
38→19 wireguardautotunnel uses networkmonitor✕
- Connections
- 1 pair of types, where a type in wireguardautotunnel uses a type in networkmonitor.
- The types involved
com.zaneschepke.wireguardautotunnel.MainActivity→com.zaneschepke.networkmonitor.NetworkMonitor
- Direction
- wireguardautotunnel uses networkmonitor, so a change to networkmonitor can break wireguardautotunnel, while a change to wireguardautotunnel can't break networkmonitor.
- Position
- Below the diagonal: wireguardautotunnel uses a module listed above it, which is the healthy direction.
38→23 wireguardautotunnel uses wireguardautotunnel.notification✕
- Connections
- 2 pairs of types, where a type in wireguardautotunnel uses a type in wireguardautotunnel.notification.
- The types involved
com.zaneschepke.wireguardautotunnel.MainActivity→com.zaneschepke.wireguardautotunnel.notification.NotificationServicecom.zaneschepke.wireguardautotunnel.WireGuardAutoTunnel→com.zaneschepke.wireguardautotunnel.notification.NotificationService
- Direction
- wireguardautotunnel uses wireguardautotunnel.notification, so a change to wireguardautotunnel.notification can break wireguardautotunnel, while a change to wireguardautotunnel can't break wireguardautotunnel.notification.
- Position
- Below the diagonal: wireguardautotunnel uses a module listed above it, which is the healthy direction.
38→25 wireguardautotunnel uses wireguardautotunnel.domain.repository✕
- Connections
- 2 pairs of types, where a type in wireguardautotunnel uses a type in wireguardautotunnel.domain.repository.
- The types involved
com.zaneschepke.wireguardautotunnel.MainActivity→com.zaneschepke.wireguardautotunnel.domain.repository.AppStateRepositorycom.zaneschepke.wireguardautotunnel.MainActivity→com.zaneschepke.wireguardautotunnel.domain.repository.TunnelRepository
- Direction
- wireguardautotunnel uses wireguardautotunnel.domain.repository, so a change to wireguardautotunnel.domain.repository can break wireguardautotunnel, while a change to wireguardautotunnel can't break wireguardautotunnel.domain.repository.
- Position
- Below the diagonal: wireguardautotunnel uses a module listed above it, which is the healthy direction.
38→26 wireguardautotunnel uses wireguardautotunnel.domain.sideeffect.GlobalSideEffect✕
- Connections
- 1 pair of types, where a type in wireguardautotunnel uses a type in wireguardautotunnel.domain.sideeffect.GlobalSideEffect.
- The types involved
com.zaneschepke.wireguardautotunnel.MainActivity→com.zaneschepke.wireguardautotunnel.domain.sideeffect.GlobalSideEffect.Snackbar
- Direction
- wireguardautotunnel uses wireguardautotunnel.domain.sideeffect.GlobalSideEffect, so a change to wireguardautotunnel.domain.sideeffect.GlobalSideEffect can break wireguardautotunnel, while a change to wireguardautotunnel can't break wireguardautotunnel.domain.sideeffect.GlobalSideEffect.
- Position
- Below the diagonal: wireguardautotunnel uses a module listed above it, which is the healthy direction.
38→32 wireguardautotunnel uses wireguardautotunnel.core.orchestration✕
- Connections
- 4 pairs of types, where a type in wireguardautotunnel uses a type in wireguardautotunnel.core.orchestration.
- The types involved
com.zaneschepke.wireguardautotunnel.MainActivity→com.zaneschepke.wireguardautotunnel.core.orchestration.FileExportCoordinatorcom.zaneschepke.wireguardautotunnel.WireGuardAutoTunnel→com.zaneschepke.wireguardautotunnel.core.orchestration.AppBoostrapCoordinatorcom.zaneschepke.wireguardautotunnel.WireGuardAutoTunnel→com.zaneschepke.wireguardautotunnel.core.orchestration.StartupCoordinatorcom.zaneschepke.wireguardautotunnel.WireGuardAutoTunnel→com.zaneschepke.wireguardautotunnel.core.orchestration.TunnelCoordinator
- Direction
- wireguardautotunnel uses wireguardautotunnel.core.orchestration, so a change to wireguardautotunnel.core.orchestration can break wireguardautotunnel, while a change to wireguardautotunnel can't break wireguardautotunnel.core.orchestration.
- Position
- Below the diagonal: wireguardautotunnel uses a module listed above it, which is the healthy direction.
38→35 wireguardautotunnel uses wireguardautotunnel.data.backup✕
- Connections
- 3 pairs of types, where a type in wireguardautotunnel uses a type in wireguardautotunnel.data.backup.
- The types involved
com.zaneschepke.wireguardautotunnel.MainActivity→com.zaneschepke.wireguardautotunnel.data.backup.BackupWriteResultcom.zaneschepke.wireguardautotunnel.MainActivity→com.zaneschepke.wireguardautotunnel.data.backup.DatabaseBackupcom.zaneschepke.wireguardautotunnel.MainActivity→com.zaneschepke.wireguardautotunnel.data.backup.RestoreResult
- Direction
- wireguardautotunnel uses wireguardautotunnel.data.backup, so a change to wireguardautotunnel.data.backup can break wireguardautotunnel, while a change to wireguardautotunnel can't break wireguardautotunnel.data.backup.
- Position
- Below the diagonal: wireguardautotunnel uses a module listed above it, which is the healthy direction.
39→6 wireguardautotunnel.ui.navigation.components uses wireguardautotunnel.ui.navigation✕
- Connections
- 3 pairs of types, where a type in wireguardautotunnel.ui.navigation.components uses a type in wireguardautotunnel.ui.navigation.
- The types involved
com.zaneschepke.wireguardautotunnel.ui.navigation.components.BottomNavbarKt→com.zaneschepke.wireguardautotunnel.ui.navigation.Tabcom.zaneschepke.wireguardautotunnel.ui.navigation.components.CurrentBackStackEntryAsNavbarStateKt→com.zaneschepke.wireguardautotunnel.ui.navigation.NavControllercom.zaneschepke.wireguardautotunnel.ui.navigation.components.CurrentBackStackEntryAsNavbarStateKt→com.zaneschepke.wireguardautotunnel.ui.navigation.Route
- Direction
- wireguardautotunnel.ui.navigation.components uses wireguardautotunnel.ui.navigation, so a change to wireguardautotunnel.ui.navigation can break wireguardautotunnel.ui.navigation.components, while a change to wireguardautotunnel.ui.navigation.components can't break wireguardautotunnel.ui.navigation.
- Position
- Below the diagonal: wireguardautotunnel.ui.navigation.components uses a module listed above it, which is the healthy direction.
39→21 wireguardautotunnel.ui.navigation.components uses wireguardautotunnel.ui.state✕
- Connections
- 3 pairs of types, where a type in wireguardautotunnel.ui.navigation.components uses a type in wireguardautotunnel.ui.state.
- The types involved
com.zaneschepke.wireguardautotunnel.ui.navigation.components.CurrentBackStackEntryAsNavbarStateKt→com.zaneschepke.wireguardautotunnel.ui.state.GlobalAppUiStatecom.zaneschepke.wireguardautotunnel.ui.navigation.components.CurrentBackStackEntryAsNavbarStateKt→com.zaneschepke.wireguardautotunnel.ui.state.NavbarStatecom.zaneschepke.wireguardautotunnel.ui.navigation.components.DynamicTopAppBarKt→com.zaneschepke.wireguardautotunnel.ui.state.NavbarState
- Direction
- wireguardautotunnel.ui.navigation.components uses wireguardautotunnel.ui.state, so a change to wireguardautotunnel.ui.state can break wireguardautotunnel.ui.navigation.components, while a change to wireguardautotunnel.ui.navigation.components can't break wireguardautotunnel.ui.state.
- Position
- Below the diagonal: wireguardautotunnel.ui.navigation.components uses a module listed above it, which is the healthy direction.
39→37 wireguardautotunnel.ui.navigation.components uses wireguardautotunnel.viewmodel✕
- Connections
- 1 pair of types, where a type in wireguardautotunnel.ui.navigation.components uses a type in wireguardautotunnel.viewmodel.
- The types involved
com.zaneschepke.wireguardautotunnel.ui.navigation.components.CurrentBackStackEntryAsNavbarStateKt→com.zaneschepke.wireguardautotunnel.viewmodel.SharedAppViewModel
- Direction
- wireguardautotunnel.ui.navigation.components uses wireguardautotunnel.viewmodel, so a change to wireguardautotunnel.viewmodel can break wireguardautotunnel.ui.navigation.components, while a change to wireguardautotunnel.ui.navigation.components can't break wireguardautotunnel.viewmodel.
- Position
- Below the diagonal: wireguardautotunnel.ui.navigation.components uses a module listed above it, which is the healthy direction.
40→22 wireguardautotunnel.ui.screens.support.components uses wireguardautotunnel.domain.model✕
- Connections
- 2 pairs of types, where a type in wireguardautotunnel.ui.screens.support.components uses a type in wireguardautotunnel.domain.model.
- The types involved
com.zaneschepke.wireguardautotunnel.ui.screens.support.components.UpdateDownloadPresentation→com.zaneschepke.wireguardautotunnel.domain.model.DownloadPausecom.zaneschepke.wireguardautotunnel.ui.screens.support.components.UpdateDownloadStatusKt→com.zaneschepke.wireguardautotunnel.domain.model.UpdateDownloadState
- Direction
- wireguardautotunnel.ui.screens.support.components uses wireguardautotunnel.domain.model, so a change to wireguardautotunnel.domain.model can break wireguardautotunnel.ui.screens.support.components, while a change to wireguardautotunnel.ui.screens.support.components can't break wireguardautotunnel.domain.model.
- Position
- Below the diagonal: wireguardautotunnel.ui.screens.support.components uses a module listed above it, which is the healthy direction.
40→37 wireguardautotunnel.ui.screens.support.components uses wireguardautotunnel.viewmodel✕
- Connections
- 1 pair of types, where a type in wireguardautotunnel.ui.screens.support.components uses a type in wireguardautotunnel.viewmodel.
- The types involved
com.zaneschepke.wireguardautotunnel.ui.screens.support.components.UpdateDialogKt→com.zaneschepke.wireguardautotunnel.viewmodel.SupportViewModel
- Direction
- wireguardautotunnel.ui.screens.support.components uses wireguardautotunnel.viewmodel, so a change to wireguardautotunnel.viewmodel can break wireguardautotunnel.ui.screens.support.components, while a change to wireguardautotunnel.ui.screens.support.components can't break wireguardautotunnel.viewmodel.
- Position
- Below the diagonal: wireguardautotunnel.ui.screens.support.components uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Domain Modelling
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 68 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 6 | Medium |
Roadmap
Begin by addressing the absence of Architecture Decision Records to properly document significant design choices and their consequences. Next, resolve critical security findings in the CI/CD pipelines, specifically targeting secret handling issues in nightly, publish, and build workflows. Finally, tighten supply-chain security by restricting workflow token permissions and addressing additional secret interpolation vulnerabilities in the notifications and publishing pipelines.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +3.2 pts | Low | ADR Quality |
| 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. | +2.9 pts | Medium | Architecture documentation |
| Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED (2). | +1.3 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 8 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (6), REDACTED, REDACTED. | +1.2 pts | Low | Static Analysis (SAST) |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +0.8 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +0.8 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 12 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (5), REDACTED (5), REDACTED. | +1.6 pts | Medium | Static Analysis (SAST) |
| Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite. | +1.2 pts | Medium | Documentation (README) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 1.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.5 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| app/src/main/java/com/zaneschepke/wireguardautotunnel/MainActivity.kt | 5.6 | Mixed | Cyclomatic Complexity: MainActivity.onCreate (cyclomatic 59) |
| app/src/main/java/com/zaneschepke/wireguardautotunnel/ui/screens/tunnels/TunnelsScreen.kt | 5.9 | Mixed | Cyclomatic Complexity: TunnelsScreenKt.TunnelsScreen (cyclomatic 35) |
| app/src/main/java/com/zaneschepke/wireguardautotunnel/viewmodel/SharedAppViewModel.kt | 5.9 | Mixed | God Classes: TooManyMethods: SharedAppViewModel |
| app/src/main/java/com/zaneschepke/wireguardautotunnel/notification/AndroidTunnelNotificationService.kt | 6.7 | Mixed | Explicit Debt: TodoComment |
| app/src/main/java/com/zaneschepke/wireguardautotunnel/ui/screens/tunnels/components/TunnelList.kt | 7.1 | Mixed | Cyclomatic Complexity: TunnelListKt.ListRow (cyclomatic 25) |
| app/src/main/java/com/zaneschepke/wireguardautotunnel/ui/navigation/components/currentBackStackEntryAsNavbarState.kt | 7.1 | Mixed | Cyclomatic Complexity: CurrentBackStackEntryAsNavbarStateKt.currentRouteAsNavbarState (cyclomatic 59) |
| networkmonitor/src/main/java/com/zaneschepke/networkmonitor/AndroidNetworkMonitor.kt | 7.2 | Mixed | Cognitive Complexity: AndroidNetworkMonitor.createWifiNetworkCallbackFlow (cognitive 20) |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| app/src/main/java/com/zaneschepke/wireguardautotunnel/ui/screens/settings/dns/DnsSettingsScreen.kt | 7.4 | Mixed | Cyclomatic Complexity: DnsSettingsScreenKt.DnsSettingsScreen (cyclomatic 25) |
| app/src/main/java/com/zaneschepke/wireguardautotunnel/ui/screens/autotunnel/preferred/PreferredTunnelScreen.kt | 7.4 | Mixed | Cyclomatic Complexity: PreferredTunnelScreenKt.PreferredTunnelScreen (cyclomatic 21) |
| app/src/main/java/com/zaneschepke/wireguardautotunnel/ui/screens/settings/SettingsScreen.kt | 7.4 | Mixed | Cyclomatic Complexity: SettingsScreenKt.SettingsScreen (cyclomatic 16) |
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
Watchdog 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. 65 of 65 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
What we checked — 65 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, 186 of 199 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, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — 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 |
| Watchdog 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 |
| LLM (sampled · advisory) | Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement | — | ◐ LLM · sampled · advisory |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.kt) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage read, produce a coverage report in a standard format (JaCoCo XML — the Gradle `jacocoTestReport` task) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (JaCoCo XML — the Gradle `jacocoTestReport` task) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
- D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.kt) and this repository declares a JVM test suite (repository root, Gradle), but it was not re-run: the analyzer environment could not run it. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D14 License Compliance — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares a Gradle build (build.gradle/build.gradle.kts), but the licence verdict published here was taken over its gem dependencies. Nothing was read about its Gradle dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (31 contributor(s) across 1295 commit(s) sampled, automation and bot accounts excluded). One of them holds 91% of the history; the other 30 hold 0.3% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — Watchdog 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 (pinger/build.gradle.kts), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict.
- D24 Comment Value — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D27 Navigability — not measured this run — Watchdog 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. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- D32 Data Compliance (PII/GDPR) — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `app/src/main/java/com/zaneschepke/wireguardautotunnel/viewmodel/AutoTunnelViewModel.kt`, `app/src/main/java/com/zaneschepke/wireguardautotunnel/viewmodel/SupportViewModel.kt`, `networkmonitor/src/main/java/com/zaneschepke/networkmonitor/AndroidNetworkMonitor.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 — Watchdog 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.
- AX6 Interface segregation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AXR1 Runtime accessibility — not measured this run — Watchdog 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: uld not resolve com.github.topjohnwu.libsu:core:6.0.0. > Could not get resource 'https://jitpack.io/com/github/topjohnwu/libsu/core/6.0.0/core-6.0.0.pom'. > Could not GET 'https:/…; 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 — Watchdog 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check finds primitive parameters that travel together through several signatures of the domain (a missing value object). Its deterministic rule has not yet shown 95 % precision on adjudicated rows, so the clumps it finds are counted here and not published as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
- DM9 Scattered domain decisions — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not measured — scattered-decision detection needs expression-level symbol resolution: a comparison operand bound to the member it judges (arm one) and a construction bound to the type it produces (arm two). A Roslyn compilation carries both; arm two alone also runs on any frontend that declares whether a construction is produced or passed, and this target loaded neither.
- GD1 Unfinished & placeholder code — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Kotlin is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's Kotlin is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- P1 CI/CD gates — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. A CI pipeline exists and the word "test" appears, but no explicit test-runner invocation (your stack's test command, or a test job) was matched — so either the gate runs tests through a step this pass could not recognise, or "test" is incidental here (a path, "latest", a reporter). Which of the two it is cannot be settled from this dimension's evidence; the coverage dimensions report whether a suite exists at all. You can widen what we reach: name the test runner explicitly in the pipeline step (your stack's test command, or a job named for the suite) so the gate is unambiguous to a reader and to this pass.
- S1 Web-Security Posture — not measured this run — Watchdog 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- 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 is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- DM4 Rich vs anemic model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
- 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.
- 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".
- P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
- 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
14 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was MainActivity.onCreate at 59. 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 Tab.fromRoute at 34 — 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: app/src/main/java/com/zaneschepke/wireguardautotunnel/ui/navigation/Route.kt (Tab.fromRoute at 34). 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 3 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with MainActivity.onCreate (cyclomatic 59), CurrentBackStackEntryAsNavbarStateKt.currentRouteAsNavbarState (cyclomatic 59), TunnelsScreenKt.TunnelsScreen (cyclomatic 35). — 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 3 together lifts Cyclomatic Complexity from 7.4 to about 8.2/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
18 method(s) exceeded the cognitive complexity threshold of 15; the worst was MainActivity.onCreate at 66.
What to do
- Bring the 18 bodies over 15 down to 15 or less in Cognitive Complexity — start with MainActivity.onCreate (cognitive 66), TunnelListKt.ListRow (cognitive 52), CurrentBackStackEntryAsNavbarStateKt.currentRouteAsNavbarState (cognitive 50). — 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 18 together lifts Cognitive Complexity from 7.0 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
22 god class(es) detected.
What to do
- Resolve the 16 MethodTooLong finding(s) in God Classes — start with TunnelList.kt (2), MainActivity.kt, currentBackStackEntryAsNavbarState.kt. — One of this dimension's main actionable groups (16 warning-level).
- Resolve the 3 FileTooLong finding(s) in God Classes — start with MainActivity.kt, SharedAppViewModel.kt, currentBackStackEntryAsNavbarState.kt. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 ClassTooLong finding(s) in God Classes — start with MainActivity.kt, SharedAppViewModel.kt. — One of this dimension's main actionable groups (2 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
16 duplicated block group(s) detected.
What to do
- Resolve the 3 Duplicated block (12 lines × 2) finding(s) in Code Duplication — start with TunnelGlobalsScreen.kt, TunnelSettingsScreen.kt, PingStats.kt. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 Duplicated block (17 lines × 2) finding(s) in Code Duplication — start with SettingsMapper.kt, TunnelConfigMapper.kt. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with ProtocolBottomSheet.kt, LockdownSettingsScreen.kt. — One of this dimension's main actionable groups (2 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
5 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; 2 module(s) off the main sequence, with abstractness counted on 4 of the 5 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What to do
- Resolve the 2 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (2 warning-level).
- Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
1 of 36 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with SharedAppViewModel.kt. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D12 · Dependency Hygiene
0 outdated direct gem(s), 1 pinning defect(s). 2 declaration(s) graded against rubygems.org, none of them against a committed Gemfile.lock — this repository commits none, which a published gem correctly does not, so currency is read off the declared requirements: a declaration that does not cap below the current release resolves to it on `bundle install`. Whether any of these gems is DEPRECATED or YANKED is not graded — rubygems.org publishes no deprecation marker, and a yank removes a version rather than flagging it. Whether any is UNMAINTAINED is not graded either: no registry publishes a maintenance status, and release age does not stand in for one. Whether any is UNUSED is a source question, not a registry one. Known CVEs in this dependency graph are D30's question, read from the manifest there.
What to do
- Resolve the 1 No Gemfile.lock committed by an application finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 2 shipped gem(s) use a banned license. Licences were resolved from rubygems.org over the 2 runtime gem(s) this repository declares. It commits no Gemfile.lock to close that set over, so the verdict covers the declarations rather than the whole resolved graph. Development-group and `add_development_dependency` gems are excluded: they are not distributed with this repository. ★ COVERAGE OF THIS VERDICT: it grades this repository's gem dependencies and nothing else. The repository also declares a Gradle build (build.gradle/build.gradle.kts), and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
D15 · Churn × Complexity Hotspots
Top hotspots: app/src/main/java/com/zaneschepke/wireguardautotunnel/MainActivity.kt (13×59=767); app/src/main/java/com/zaneschepke/wireguardautotunnel/ui/navigation/components/currentBackStackEntryAsNavbarState.kt (8×59=472); app/src/main/java/com/zaneschepke/wireguardautotunnel/ui/screens/tunnels/TunnelsScreen.kt (9×35=315) Repeated repair below the complexity floor: app/src/main/java/com/zaneschepke/wireguardautotunnel/service/autotunnel/AutoTunnelService.kt (6 of 6 changes were fixes); app/src/main/java/com/zaneschepke/wireguardautotunnel/util/FileUtils.kt (5 of 7 changes were fixes); app/src/main/java/com/zaneschepke/wireguardautotunnel/ui/common/functions/Functions.kt (4 of 4 changes were fixes)
What to do
- Resolve the 10 Hotspot finding(s) in Churn × Complexity Hotspots — start with MainActivity.kt, currentBackStackEntryAsNavbarState.kt, TunnelsScreen.kt. — One of this dimension's main actionable groups (10 warning-level).
- Resolve the 4 Repeated repair finding(s) in Churn × Complexity Hotspots — start with AutoTunnelService.kt, FileUtils.kt, Functions.kt. — One of this dimension's main actionable groups (4 warning-level).
D17 · Explicit Debt
1 deducted task-comment markers across 28571 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 1 TodoComment finding(s) in Explicit Debt — start with AndroidTunnelNotificationService.kt. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 1 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. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
1 of 5 build units (Gradle) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
68 finding(s): 0 critical, 68 high, 0 medium, 0 low. 34 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 1 file(s) — `gradlew` (line 74, line 178) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 5 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 12 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (5), REDACTED (5), REDACTED. — One of this dimension's main actionable groups (12 issue-level).
- Resolve the 8 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (6), REDACTED, REDACTED. — One of this dimension's main actionable groups (8 issue-level).
- No action in Static Analysis (SAST) — all 34 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 (34 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
No known-vulnerable dependencies in any ecosystem this repository declares. No known-vulnerable gem among the 2 declared gem(s) osv.dev was asked about. This repository commits no Gemfile.lock — which a published gem correctly does not — so osv-scanner had no resolved graph to read, and the question was put to osv.dev instead over the releases `bundle install` resolves this repository's 2 declared requirement(s) to. The verdict therefore covers the DIRECT declarations at their resolved releases, not the transitive graph a lock would close over.
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 141 of the 377 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: MainActivity.kt↔DataStoreAppStateRepository.kt 82%; AutoTunnelControlTile.kt↔TunnelControlTile.kt 80%; MainActivity.kt↔GlobalAppUiState.kt 80%
What to do
- Resolve the 5 Change coupling finding(s) in Change Coupling — start with ShortcutsActivity.kt (2), AutoTunnelControlTile.kt, AutoTunnelService.kt. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 1 Change-coupling hub finding(s) in Change Coupling — start with MainActivity.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 (2). — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
D37 · Vulnerability-disclosure Policy
A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious. No known-vulnerable gem among the 2 declared gem(s) osv.dev was asked about. This repository commits no Gemfile.lock — which a published gem correctly does not — so osv-scanner had no resolved graph to read, and the question was put to osv.dev instead over the releases `bundle install` resolves this repository's 2 declared requirement(s) to. The verdict therefore covers the DIRECT declarations at their resolved releases, not the transitive graph a lock would close over.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 69 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX4 · Dependency direction
C1 · Data Protection
What to do
- Strengthen data-at-rest protection: vault your keys (AWS KMS / Secrets Manager, GCP KMS / Secret Manager, Azure Key Vault, HashiCorp Vault — not a key compiled into the app) and encrypt the store that holds the personal data (SQLCipher, a Realm encryptionKey, field-level AEAD) — partial coverage still leaves gaps.
- Enforce HTTPS on the server that receives this data: terminate TLS in it (Ktor's sslConnector, Spring's server.ssl and requiresSecure, Netty's SslContextBuilder.forServer) and send Strict-Transport-Security (Ktor's HttpsRedirect), or run it behind a TLS-terminating proxy, so data in transit is always encrypted.
DM10 · One transaction, one aggregate
DM11 · Constructible invalid state
- `DnsSettings`'s public constructor takes `bootstrapDnsEndpoint`, `tunnelDnsEndpoint`, `localSuffixes` 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` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `DnsSettings` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — app/src/main/java/com/zaneschepke/wireguardautotunnel/data/entity/DnsSettings.kt:13
- `GeneralSettings`'s public constructor takes `theme`, `locale`, `remoteKey` 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` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `GeneralSettings` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — app/src/main/java/com/zaneschepke/wireguardautotunnel/data/entity/GeneralSettings.kt:9
- `ProxySettings`'s public constructor takes `socks5ProxyBindAddress`, `httpProxyBindAddress`, `proxyUsername`, `proxyPassword` 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` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `ProxySettings` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — app/src/main/java/com/zaneschepke/wireguardautotunnel/data/entity/ProxySettings.kt:8
- `TunnelConfig`'s public constructor takes `name`, `quickConfig` 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` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `TunnelConfig` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — app/src/main/java/com/zaneschepke/wireguardautotunnel/data/entity/TunnelConfig.kt:27
- `TunnelGroup`'s public constructor takes `name` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `TunnelGroup` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — app/src/main/java/com/zaneschepke/wireguardautotunnel/data/entity/TunnelGroup.kt:9
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
DM2 · Strongly-typed ids
- `GeneralSettings.remoteKey` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that. — app/src/main/java/com/zaneschepke/wireguardautotunnel/data/entity/GeneralSettings.kt:23
- `TunnelConfig.groupId` is a raw `Int` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int`, in whatever form your language spells that. — app/src/main/java/com/zaneschepke/wireguardautotunnel/data/entity/TunnelConfig.kt:48
- `TunnelConfig.entryTunnelId` is a raw `Int` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int`, in whatever form your language spells that. — app/src/main/java/com/zaneschepke/wireguardautotunnel/data/entity/TunnelConfig.kt:49
- `TunnelActionEvent.tunnelId` is a raw `Int` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int`, in whatever form your language spells that. — app/src/main/java/com/zaneschepke/wireguardautotunnel/domain/events/TunnelActionEvent.kt:8
What to do
- Adopt strongly-typed ids across the domain — finish the migration or document the boundary; primitive ids invite transposed-argument bugs.
DM4 · Rich vs anemic model
- `AutoTunnelSettings` is an aggregate/entity with 13 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/src/main/java/com/zaneschepke/wireguardautotunnel/data/entity/AutoTunnelSettings.kt:9
- `DnsSettings` is an aggregate/entity with 11 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/src/main/java/com/zaneschepke/wireguardautotunnel/data/entity/DnsSettings.kt:13
- `GeneralSettings` is an aggregate/entity with 23 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/src/main/java/com/zaneschepke/wireguardautotunnel/data/entity/GeneralSettings.kt:9
- `LockdownSettings` is an aggregate/entity with 4 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/src/main/java/com/zaneschepke/wireguardautotunnel/data/entity/LockdownSettings.kt:8
- `MonitoringSettings` is an aggregate/entity with 4 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/src/main/java/com/zaneschepke/wireguardautotunnel/data/entity/MonitoringSettings.kt:8
- `ProxySettings` is an aggregate/entity with 8 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/src/main/java/com/zaneschepke/wireguardautotunnel/data/entity/ProxySettings.kt:8
- `TunnelConfig` is an aggregate/entity with 16 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/src/main/java/com/zaneschepke/wireguardautotunnel/data/entity/TunnelConfig.kt:27
- `TunnelGroup` is an aggregate/entity with 4 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/src/main/java/com/zaneschepke/wireguardautotunnel/data/entity/TunnelGroup.kt:9
What to do
- Move business rules onto the aggregates/entities they govern so invariants are enforced at the source, not in anemic services.
DM5 · Encapsulated state
DM6 · Domain ↔ infrastructure boundary
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Add a README to the 5 of 5 project(s) that lack one — worth up to 2 pts.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- 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
P1 · CI/CD gates
What to do
- Run the test suite in CI via an explicit runner step (`./gradlew test` for the toolchain this pipeline already uses) and gate merges on it.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add spotbugs with find-sec-bugs (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 30474 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.
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.
- Dependabot is configured but does not watch `bundler`, `gitsubmodule` — add those `package-ecosystem` entries to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
What to do
- Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
P5 · DR & Backup
What to do
- Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).
P6 · Release Hygiene
PF3 · Async & latency hygiene
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X2 · Cancellation propagation
X20 · Mistyped argument guard
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
- 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. — logcatter/src/main/java/com/zaneschepke/logcatter/LogFileManager.kt:69
- `catch (_: Exception)` 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, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×2) — app/src/main/java/com/zaneschepke/wireguardautotunnel/viewmodel/SharedAppViewModel.kt:606, app/src/main/java/com/zaneschepke/wireguardautotunnel/viewmodel/SharedAppViewModel.kt:618
- `catch (e: Exception)` 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, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — app/src/main/java/com/zaneschepke/wireguardautotunnel/ui/state/EditableInterface.kt:195
What to do
- Swallowed exception (empty catch)
X30 · Support guard that admits what it rejects
X5 · Nullable reference types
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 83% | Strong | Solid. |
| Architecture | 86% | Strong | Solid. |
| Maturity | 54% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 57% | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 52% | Adequate — gated by D29, D36, C1 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 58% | Adequate — gated by DM2, DM4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 1 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 3 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 3 control(s) we could not find positive evidence for
- C3 Audit Trail — Repo shows no audit-logging mechanism (an audit-log table or model — an Exposed table, a data class, a Room entity or a SQL migration's table named for it — Hibernate Envers' @Audited, a JPA entity listener, Hibernate event listener or jOOQ RecordListener that records each change) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
- C4 Data Retention — Repo shows no data-retention / TTL / cleanup mechanism for personal data — absence of evidence is not evidence of a working control. Define retention periods and a purge/cleanup job (or TTL) in code, or document where retention is enforced, so this dimension can be scored.
- C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
Not included — 61 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — not 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.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — the Android app did not build — `./gradlew :app:assembleDebug` exited 1: uld not resolve com.github.topjohnwu.libsu:core:6.0.0. > Could not get resource 'https://jitpack.io/com/github/topjohnwu/libsu/core/6.0.0/core-6.0.0.pom'. > Could not GET 'https:/…; 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.
- 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.
- D10 Test Quality — ~133 lines of test source are present (.kt) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not included — the .kt suite was found but not re-run
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — Naming consistency is measured on C# only; Kotlin not measured.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ projects each declaring an entity of their own. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C# and Visual Basic comments only — this repository's production source is .kt, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.kt), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- 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) — 3 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- D9 Test Distribution — Test source is present (.kt) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so its unit/integration/BDD/E2E split couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- DM1 Aggregate boundaries — no aggregates detected — aggregate-boundary check not applicable
- DM3 Integration-event coupling — no integration events detected — coupling check not applicable
- DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
- DM8 Value-object opportunities — not scored — the deterministic rule found 0 candidate clump(s); its rows are withheld until it has a measured precision of 95 % (a sample of fewer than 10 rows cannot show one)
- DM9 Scattered domain decisions — not measured — scattered-decision detection needs expression-level symbol resolution: a comparison operand bound to the member it judges (arm one) and a construction bound to the type it produces (arm two). A Roslyn compilation carries both; arm two alone also runs on any frontend that declares whether a construction is produced or passed, and this target loaded neither
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- M4 Documentation accuracy — Not applicable: the 1 current-state document(s) make no claim of a kind M4 checks.
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P2 Observability — This repository's JVM source (5 module(s), 370 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (JaCoCo XML — the Gradle `jacocoTestReport` task) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a pom.xml, Gradle or sbt build, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not applicable: allocation awareness is rated where code engineers for it — at least 400 production lines that ship benchmarks or already use allocation-aware idioms (8 or more). This repository's Kotlin code has 31,516 production line(s), 5 such use(s) and no benchmarks, so there is no allocation work to rate. The card is reward-only: its absence costs nothing.
- 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.
- X24 Document value interpolated into markup unescaped — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Kotlin was read, and it logs through none that an assembled message defeats: Android's `Log` and Timber, java.util.logging and log4j-api-kotlin take one finished message (as log4net does in C#), or it makes no call through a named logger at all. Calls made through SLF4J, log4j 2 or kotlin-logging (`LoggerFactory.getLogger`, `KotlinLogging.logger {}`) would be judged.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 68 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 116 finding(s)
- MethodTooLong: MainActivity.onCreate app/src/main/java/com/zaneschepke/wireguardautotunnel/MainActivity.kt:217
- MethodTooLong: CurrentBackStackEntryAsNavbarStateKt.currentRouteAsNavbarState app/src/main/java/com/zaneschepke/wireguardautotunnel/ui/navigation/components/currentBackStackEntryAsNavbarState.kt:83
- MethodTooLong: AmneziaSectionKt.AmneziaSection app/src/main/java/com/zaneschepke/wireguardautotunnel/ui/screens/tunnels/settings/config/edit/components/AmneziaSection.kt:21
- MethodTooLong: DnsSettingsScreenKt.DnsSettingsScreen app/src/main/java/com/zaneschepke/wireguardautotunnel/ui/screens/settings/dns/DnsSettingsScreen.kt:65
- MethodTooLong: AutoTunnelScreenKt.AutoTunnelScreen app/src/main/java/com/zaneschepke/wireguardautotunnel/ui/screens/autotunnel/AutoTunnelScreen.kt:73
- MethodTooLong: TunnelsScreenKt.TunnelsScreen app/src/main/java/com/zaneschepke/wireguardautotunnel/ui/screens/tunnels/TunnelsScreen.kt:53
- MethodTooLong: SettingsScreenKt.SettingsScreen app/src/main/java/com/zaneschepke/wireguardautotunnel/ui/screens/settings/SettingsScreen.kt:72
- MethodTooLong: LibsBuilderKt.buildLibsWithAdditionalLibraries app/src/main/java/com/zaneschepke/wireguardautotunnel/ui/screens/support/license/LibsBuilder.kt:11
- MethodTooLong: TunnelListKt.TunnelList app/src/main/java/com/zaneschepke/wireguardautotunnel/ui/screens/tunnels/components/TunnelList.kt:80
- MethodTooLong: TunnelEventDispatcher.bind app/src/main/java/com/zaneschepke/wireguardautotunnel/core/event/TunnelEventDispatcher.kt:29
- MethodTooLong: TunnelListKt.ListRow app/src/main/java/com/zaneschepke/wireguardautotunnel/ui/screens/tunnels/components/TunnelList.kt:311
- MethodTooLong: ProxySettingsScreenKt.ProxySettingsScreen app/src/main/java/com/zaneschepke/wireguardautotunnel/ui/screens/settings/proxy/ProxySettingsScreen.kt:47
- MethodTooLong: TunnelSettingsScreenKt.TunnelSettingsScreen app/src/main/java/com/zaneschepke/wireguardautotunnel/ui/screens/tunnels/settings/TunnelSettingsScreen.kt:44
- MethodTooLong: AndroidIntegrationsScreenKt.AndroidIntegrationsScreen app/src/main/java/com/zaneschepke/wireguardautotunnel/ui/screens/settings/integrations/AndroidIntegrationsScreen.kt:53
- MethodTooLong: PreferredTunnelScreenKt.PreferredTunnelScreen app/src/main/java/com/zaneschepke/wireguardautotunnel/ui/screens/autotunnel/preferred/PreferredTunnelScreen.kt:49
- MethodTooLong: WifiSettingsScreenKt.WifiSettingsScreen app/src/main/java/com/zaneschepke/wireguardautotunnel/ui/screens/autotunnel/wifi/WifiSettingsScreen.kt:50
- Hotspot: app/src/main/java/com/zaneschepke/wireguardautotunnel/MainActivity.kt app/src/main/java/com/zaneschepke/wireguardautotunnel/MainActivity.kt:217
- Hotspot: app/src/main/java/com/zaneschepke/wireguardautotunnel/ui/navigation/components/currentBackStackEntryAsNavbarState.kt app/src/main/java/com/zaneschepke/wireguardautotunnel/ui/navigation/components/currentBackStackEntryAsNavbarState.kt:83
- Hotspot: app/src/main/java/com/zaneschepke/wireguardautotunnel/ui/screens/tunnels/TunnelsScreen.kt app/src/main/java/com/zaneschepke/wireguardautotunnel/ui/screens/tunnels/TunnelsScreen.kt:53
- Hotspot: app/src/main/java/com/zaneschepke/wireguardautotunnel/ui/screens/tunnels/components/TunnelList.kt app/src/main/java/com/zaneschepke/wireguardautotunnel/ui/screens/tunnels/components/TunnelList.kt:311
- Hotspot: app/src/main/java/com/zaneschepke/wireguardautotunnel/ui/navigation/Route.kt app/src/main/java/com/zaneschepke/wireguardautotunnel/ui/navigation/Route.kt:189
- Hotspot: app/src/main/java/com/zaneschepke/wireguardautotunnel/ui/screens/settings/dns/DnsSettingsScreen.kt app/src/main/java/com/zaneschepke/wireguardautotunnel/ui/screens/settings/dns/DnsSettingsScreen.kt:65
- Hotspot: app/src/main/java/com/zaneschepke/wireguardautotunnel/ui/screens/support/SupportScreen.kt app/src/main/java/com/zaneschepke/wireguardautotunnel/ui/screens/support/SupportScreen.kt:75
- Hotspot: app/src/main/java/com/zaneschepke/wireguardautotunnel/viewmodel/DnsViewModel.kt app/src/main/java/com/zaneschepke/wireguardautotunnel/viewmodel/DnsViewModel.kt:83
- Hotspot: app/src/main/java/com/zaneschepke/wireguardautotunnel/ui/screens/settings/SettingsScreen.kt app/src/main/java/com/zaneschepke/wireguardautotunnel/ui/screens/settings/SettingsScreen.kt:72
- Hotspot: app/src/main/java/com/zaneschepke/wireguardautotunnel/ui/screens/autotunnel/AutoTunnelScreen.kt app/src/main/java/com/zaneschepke/wireguardautotunnel/ui/screens/autotunnel/AutoTunnelScreen.kt:73
- Anemic entity: AutoTunnelSettings app/src/main/java/com/zaneschepke/wireguardautotunnel/data/entity/AutoTunnelSettings.kt:9
- Anemic entity: DnsSettings app/src/main/java/com/zaneschepke/wireguardautotunnel/data/entity/DnsSettings.kt:13
- Anemic entity: GeneralSettings app/src/main/java/com/zaneschepke/wireguardautotunnel/data/entity/GeneralSettings.kt:9
- Anemic entity: LockdownSettings app/src/main/java/com/zaneschepke/wireguardautotunnel/data/entity/LockdownSettings.kt:8
- Anemic entity: MonitoringSettings app/src/main/java/com/zaneschepke/wireguardautotunnel/data/entity/MonitoringSettings.kt:8
- Anemic entity: ProxySettings app/src/main/java/com/zaneschepke/wireguardautotunnel/data/entity/ProxySettings.kt:8
- Anemic entity: TunnelConfig app/src/main/java/com/zaneschepke/wireguardautotunnel/data/entity/TunnelConfig.kt:27
- Anemic entity: TunnelGroup app/src/main/java/com/zaneschepke/wireguardautotunnel/data/entity/TunnelGroup.kt:9
- Change coupling: AutoTunnelControlTile.kt ↔ TunnelControlTile.kt app/src/main/java/com/zaneschepke/wireguardautotunnel/service/tile/AutoTunnelControlTile.kt:1
- Change coupling: ShortcutsActivity.kt ↔ TunnelControlTile.kt app/src/main/java/com/zaneschepke/wireguardautotunnel/core/shortcut/ShortcutsActivity.kt:1
- Change coupling: ShortcutsActivity.kt ↔ AutoTunnelService.kt app/src/main/java/com/zaneschepke/wireguardautotunnel/core/shortcut/ShortcutsActivity.kt:1
- Change coupling: AutoTunnelService.kt ↔ AutoTunnelViewModel.kt app/src/main/java/com/zaneschepke/wireguardautotunnel/service/autotunnel/AutoTunnelService.kt:1
- Change coupling: TunnelsScreen.kt ↔ GlobalAppUiState.kt app/src/main/java/com/zaneschepke/wireguardautotunnel/ui/screens/tunnels/TunnelsScreen.kt:1
- Constructible in an invalid state: DnsSettings app/src/main/java/com/zaneschepke/wireguardautotunnel/data/entity/DnsSettings.kt:13
- Constructible in an invalid state: GeneralSettings app/src/main/java/com/zaneschepke/wireguardautotunnel/data/entity/GeneralSettings.kt:9
- Constructible in an invalid state: ProxySettings app/src/main/java/com/zaneschepke/wireguardautotunnel/data/entity/ProxySettings.kt:8
- Constructible in an invalid state: TunnelConfig app/src/main/java/com/zaneschepke/wireguardautotunnel/data/entity/TunnelConfig.kt:27
- Constructible in an invalid state: TunnelGroup app/src/main/java/com/zaneschepke/wireguardautotunnel/data/entity/TunnelGroup.kt:9
- Repeated repair: app/src/main/java/com/zaneschepke/wireguardautotunnel/service/autotunnel/AutoTunnelService.kt app/src/main/java/com/zaneschepke/wireguardautotunnel/service/autotunnel/AutoTunnelService.kt:224
- Repeated repair: app/src/main/java/com/zaneschepke/wireguardautotunnel/util/FileUtils.kt app/src/main/java/com/zaneschepke/wireguardautotunnel/util/FileUtils.kt:59
- Repeated repair: app/src/main/java/com/zaneschepke/wireguardautotunnel/ui/common/functions/Functions.kt app/src/main/java/com/zaneschepke/wireguardautotunnel/ui/common/functions/Functions.kt:21
- Repeated repair: app/src/main/java/com/zaneschepke/wireguardautotunnel/util/extensions/ContextExtensions.kt app/src/main/java/com/zaneschepke/wireguardautotunnel/util/extensions/ContextExtensions.kt:38
- FileTooLong: wireguardautotunnel/MainActivity.kt app/src/main/java/com/zaneschepke/wireguardautotunnel/MainActivity.kt
- FileTooLong: viewmodel/SharedAppViewModel.kt app/src/main/java/com/zaneschepke/wireguardautotunnel/viewmodel/SharedAppViewModel.kt
- FileTooLong: components/currentBackStackEntryAsNavbarState.kt app/src/main/java/com/zaneschepke/wireguardautotunnel/ui/navigation/components/currentBackStackEntryAsNavbarState.kt
- Duplicated block (12 lines × 2) app/src/main/java/com/zaneschepke/wireguardautotunnel/ui/screens/settings/globals/TunnelGlobalsScreen.kt:61
- Duplicated block (12 lines × 2) app/src/main/java/com/zaneschepke/wireguardautotunnel/ui/screens/tunnels/settings/TunnelSettingsScreen.kt:52
- Duplicated block (12 lines × 2) app/src/main/java/com/zaneschepke/wireguardautotunnel/util/network/PingStats.kt:14
- Swallowed exception (caught, then discarded) app/src/main/java/com/zaneschepke/wireguardautotunnel/viewmodel/SharedAppViewModel.kt:606
- Swallowed exception (caught, then discarded) app/src/main/java/com/zaneschepke/wireguardautotunnel/viewmodel/SharedAppViewModel.kt:618
- Swallowed exception (caught, then discarded) app/src/main/java/com/zaneschepke/wireguardautotunnel/ui/state/EditableInterface.kt:195
- ClassTooLong: MainActivity app/src/main/java/com/zaneschepke/wireguardautotunnel/MainActivity.kt:176
- ClassTooLong: SharedAppViewModel app/src/main/java/com/zaneschepke/wireguardautotunnel/viewmodel/SharedAppViewModel.kt:80
- REDACTED
- REDACTED
- Duplicated block (17 lines × 2) app/src/main/java/com/zaneschepke/wireguardautotunnel/data/mapper/SettingsMapper.kt:16
- Duplicated block (17 lines × 2) app/src/main/java/com/zaneschepke/wireguardautotunnel/data/mapper/TunnelConfigMapper.kt:8
- Duplicated block (11 lines × 2) app/src/main/java/com/zaneschepke/wireguardautotunnel/ui/screens/settings/dns/components/ProtocolBottomSheet.kt:23
- Duplicated block (11 lines × 2) app/src/main/java/com/zaneschepke/wireguardautotunnel/ui/screens/settings/lockdown/LockdownSettingsScreen.kt:69
- Duplicated block (8 lines × 2) app/src/main/java/com/zaneschepke/wireguardautotunnel/data/network/KtorGitHubApi.kt:18
- Duplicated block (8 lines × 2) app/src/main/java/com/zaneschepke/wireguardautotunnel/ui/screens/tunnels/settings/config/edit/components/AmneziaSection.kt:302
- Off the main sequence: :logcatter
- Off the main sequence: :networkmonitor
- MainActivity.onCreate (cyclomatic 59) app/src/main/java/com/zaneschepke/wireguardautotunnel/MainActivity.kt:217
- CurrentBackStackEntryAsNavbarStateKt.currentRouteAsNavbarState (cyclomatic 59) app/src/main/java/com/zaneschepke/wireguardautotunnel/ui/navigation/components/currentBackStackEntryAsNavbarState.kt:83
- TunnelsScreenKt.TunnelsScreen (cyclomatic 35) app/src/main/java/com/zaneschepke/wireguardautotunnel/ui/screens/tunnels/TunnelsScreen.kt:53
- UpdateDownloadStatusKt.rememberUpdateDownloadPresentation (cyclomatic 29) app/src/main/java/com/zaneschepke/wireguardautotunnel/ui/screens/support/components/UpdateDownloadStatus.kt:48
- DnsSettingsScreenKt.DnsSettingsScreen (cyclomatic 25) app/src/main/java/com/zaneschepke/wireguardautotunnel/ui/screens/settings/dns/DnsSettingsScreen.kt:65
- TunnelListKt.ListRow (cyclomatic 25) app/src/main/java/com/zaneschepke/wireguardautotunnel/ui/screens/tunnels/components/TunnelList.kt:311
- SupportScreenKt.SupportScreen (cyclomatic 23) app/src/main/java/com/zaneschepke/wireguardautotunnel/ui/screens/support/SupportScreen.kt:75
- TunnelListKt.TunnelList (cyclomatic 22) app/src/main/java/com/zaneschepke/wireguardautotunnel/ui/screens/tunnels/components/TunnelList.kt:80
- PreferredTunnelScreenKt.PreferredTunnelScreen (cyclomatic 21) app/src/main/java/com/zaneschepke/wireguardautotunnel/ui/screens/autotunnel/preferred/PreferredTunnelScreen.kt:49
- Socks5SocketFactory.createSocks5Socket (cyclomatic 17) pinger/src/main/java/com/zaneschepke/pinger/Socks5SocketFactory.kt:54
- AutoTunnelScreenKt.AutoTunnelScreen (cyclomatic 17) app/src/main/java/com/zaneschepke/wireguardautotunnel/ui/screens/autotunnel/AutoTunnelScreen.kt:73
- BackupEncryptedDialogKt.BackupEncryptionDialog (cyclomatic 17) app/src/main/java/com/zaneschepke/wireguardautotunnel/ui/screens/settings/components/BackupEncryptedDialog.kt:24
- DnsViewModel.save (cyclomatic 17) app/src/main/java/com/zaneschepke/wireguardautotunnel/viewmodel/DnsViewModel.kt:83
- SettingsScreenKt.SettingsScreen (cyclomatic 16) app/src/main/java/com/zaneschepke/wireguardautotunnel/ui/screens/settings/SettingsScreen.kt:72
- No Gemfile.lock committed by an application
- TodoComment app/src/main/java/com/zaneschepke/wireguardautotunnel/notification/AndroidTunnelNotificationService.kt:237
- MainActivity.onCreate (cognitive 66) app/src/main/java/com/zaneschepke/wireguardautotunnel/MainActivity.kt:217
- TunnelListKt.ListRow (cognitive 52) app/src/main/java/com/zaneschepke/wireguardautotunnel/ui/screens/tunnels/components/TunnelList.kt:311
- CurrentBackStackEntryAsNavbarStateKt.currentRouteAsNavbarState (cognitive 50) app/src/main/java/com/zaneschepke/wireguardautotunnel/ui/navigation/components/currentBackStackEntryAsNavbarState.kt:83
- TunnelListKt.TunnelList (cognitive 39) app/src/main/java/com/zaneschepke/wireguardautotunnel/ui/screens/tunnels/components/TunnelList.kt:80
- TunnelsScreenKt.TunnelsScreen (cognitive 37) app/src/main/java/com/zaneschepke/wireguardautotunnel/ui/screens/tunnels/TunnelsScreen.kt:53
- BackupEncryptedDialogKt.BackupEncryptionDialog (cognitive 36) app/src/main/java/com/zaneschepke/wireguardautotunnel/ui/screens/settings/components/BackupEncryptedDialog.kt:24
- DnsSettingsScreenKt.DnsSettingsScreen (cognitive 35) app/src/main/java/com/zaneschepke/wireguardautotunnel/ui/screens/settings/dns/DnsSettingsScreen.kt:65
- UpdateDownloadStatusKt.rememberUpdateDownloadPresentation (cognitive 33) app/src/main/java/com/zaneschepke/wireguardautotunnel/ui/screens/support/components/UpdateDownloadStatus.kt:48
- SupportScreenKt.SupportScreen (cognitive 25) app/src/main/java/com/zaneschepke/wireguardautotunnel/ui/screens/support/SupportScreen.kt:75
- AndroidNetworkMonitor.createWifiNetworkCallbackFlow (cognitive 20) networkmonitor/src/main/java/com/zaneschepke/networkmonitor/AndroidNetworkMonitor.kt:422
- SurfaceRowKt.SurfaceRow (cognitive 20) app/src/main/java/com/zaneschepke/wireguardautotunnel/ui/common/button/SurfaceRow.kt:42
- DnsViewModel.save (cognitive 20) app/src/main/java/com/zaneschepke/wireguardautotunnel/viewmodel/DnsViewModel.kt:83
- PreferredTunnelScreenKt.PreferredTunnelScreen (cognitive 19) app/src/main/java/com/zaneschepke/wireguardautotunnel/ui/screens/autotunnel/preferred/PreferredTunnelScreen.kt:49
- ProxySettingsScreenKt.ProxySettingsScreen (cognitive 19) app/src/main/java/com/zaneschepke/wireguardautotunnel/ui/screens/settings/proxy/ProxySettingsScreen.kt:47
- Socks5SocketFactory.createSocks5Socket (cognitive 18) pinger/src/main/java/com/zaneschepke/pinger/Socks5SocketFactory.kt:54
- SettingsScreenKt.SettingsScreen (cognitive 18) app/src/main/java/com/zaneschepke/wireguardautotunnel/ui/screens/settings/SettingsScreen.kt:72
- AndroidTunnelNotificationService.createGroupNotification (cognitive 17) app/src/main/java/com/zaneschepke/wireguardautotunnel/notification/AndroidTunnelNotificationService.kt:20
- ThemeKt.WireguardAutoTunnelTheme (cognitive 16) app/src/main/java/com/zaneschepke/wireguardautotunnel/ui/theme/Theme.kt:61
- TooManyMethods: SharedAppViewModel app/src/main/java/com/zaneschepke/wireguardautotunnel/viewmodel/SharedAppViewModel.kt:80
- Change-coupling hub: MainActivity.kt → DataStoreManager.kt, DataStoreAppStateRepository.kt, AppModule.kt, currentBackStackEntryAsNavbarState.kt, TunnelSettingsScreen.kt, GlobalAppUiState.kt, Constants.kt, ContextExtensions.kt app/src/main/java/com/zaneschepke/wireguardautotunnel/MainActivity.kt
- REDACTED
- REDACTED
- Duplicated block (15–19 lines × 3) app/src/main/java/com/zaneschepke/wireguardautotunnel/ui/navigation/components/currentBackStackEntryAsNavbarState.kt:289
- Duplicated block (15 lines × 2) app/src/main/java/com/zaneschepke/wireguardautotunnel/viewmodel/AutoTunnelViewModel.kt:299
- Duplicated block (14–15 lines × 2) networkmonitor/src/main/java/com/zaneschepke/networkmonitor/AndroidNetworkMonitor.kt:482
- Duplicated block (9–10 lines × 2) app/src/main/java/com/zaneschepke/wireguardautotunnel/core/tunnel/AppProvider.kt:176
- Duplicated block (6 lines × 2) networkmonitor/src/main/java/com/zaneschepke/networkmonitor/AndroidNetworkMonitor.kt:699
- Duplicated block (5 lines × 2) networkmonitor/src/main/java/com/zaneschepke/networkmonitor/AndroidNetworkMonitor.kt:802
- Duplicated block (9 lines × 3) app/src/main/java/com/zaneschepke/wireguardautotunnel/ui/screens/tunnels/settings/config/edit/components/AmneziaSection.kt:318
- Low cohesion: SharedAppViewModel (LCOM4 6) app/src/main/java/com/zaneschepke/wireguardautotunnel/viewmodel/SharedAppViewModel.kt:80
- Swallowed exception (empty catch) logcatter/src/main/java/com/zaneschepke/logcatter/LogFileManager.kt:69
Minor — 15 finding(s)
- Primitive id on a domain type: GeneralSettings.remoteKey app/src/main/java/com/zaneschepke/wireguardautotunnel/data/entity/GeneralSettings.kt:23
- Primitive id on a domain type: TunnelConfig.groupId app/src/main/java/com/zaneschepke/wireguardautotunnel/data/entity/TunnelConfig.kt:48
- Primitive id on a domain type: TunnelConfig.entryTunnelId app/src/main/java/com/zaneschepke/wireguardautotunnel/data/entity/TunnelConfig.kt:49
- Primitive id on a domain type: TunnelActionEvent.tunnelId app/src/main/java/com/zaneschepke/wireguardautotunnel/domain/events/TunnelActionEvent.kt:8
- Duplicated predicate app/src/main/java/com/zaneschepke/wireguardautotunnel/viewmodel/AutoTunnelViewModel.kt:91
- Duplicated predicate networkmonitor/src/main/java/com/zaneschepke/networkmonitor/AndroidNetworkMonitor.kt:804
- Duplicated predicate networkmonitor/src/main/java/com/zaneschepke/networkmonitor/AndroidNetworkMonitor.kt:701
- No ADRs found
- Projects may be oversized for their cohesion
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- No SAST
- No release approval gate
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-37e9855c450c46bdb35cc071f1bbe095/history.json --exit-code 0 --source . | 2 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-37e9855c450c46bdb35cc071f1bbe095/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/watchdog-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 . | 68 | artifacts/raw/semgrep.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 3 file(s) — `app/src/main/java/com/zaneschepke/wireguardautotunnel/viewmodel/AutoTunnelViewModel.kt`, `app/src/main/java/com/zaneschepke/wireguardautotunnel/viewmodel/SupportViewModel.kt`, `networkmonitor/src/main/java/com/zaneschepke/networkmonitor/AndroidNetworkMonitor.kt` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 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 | — |