Executive summary
wgtunnel/desktop falls short of our standard for production, in part because we found no logging, tracing or health checks in the code. It scores 47.5 out of 100 and is rated Weak, and all 64 of its critical findings are security problems in the build pipeline and in its automatic dependency updates.
Production Readiness, at 39.5, is the weakest lens and counts most in the score. The best first step is adopting a logging library, worth about 5.0 points. Recording design decisions comes next, worth about 2.2 points. Raising Production Readiness to 70 would lift the score to about 53.6.
Thirty-four pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Eighteen secrets can leak from the build pipeline, and ten 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 18,169 lines, about €19,000 to rebuild.
If Production Readiness rose from 39.5 to 70, the lowest score rated Strong, the score would rise from 47.5 to about 53.6.
Rebuild cost: about €19,000 · Estimate
| Cost to rebuild | €6,300 to €32,000, for 106 to 335 hours of work, about 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 48. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 18,169 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 client.data.model | 2 client.domain.enums | 3 core.ipc.IpcKeyFileValidator | 4 core.wifi | 5 daemon.tunnel | 6 desktop.ui.navigation | 7 desktop.update | 8 client.data.entity | 9 core.ipc.IpcKeyFileValidator.Result | 10 core.ipc.dto.request | 11 desktop.ui.screens.tunnels | 12 desktop.util | 13 client.data.dao | 14 core.ipc | 15 core.ipc.dto | 16 client.data | 17 client.domain.model | 18 client.service | 19 client.util | 20 core.log | 21 daemon.data | 22 daemon.tunnel.RunningTunnel | 23 client.data.mapper | 24 client.domain.repository | 25 client.orchestration.TunnelCoordinator | 26 daemon.autotunnel | 27 daemon.dto | 28 daemon.log | 29 desktop.ui.state | 30 desktop.wifi | 31 client.data.repository | 32 client.data.service | 33 client.orchestration | 34 daemon | 35 daemon.routes | 36 desktop.ui.screens.tunnels.components | 37 desktop.viewmodel | 38 desktop | 39 desktop.ui.screens.autotunnel.preferred | 40 desktop.ui.screens.autotunnel.wifi |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 client.data.model | ||||||||||||||||||||||||||||||||||||||||
| 2 client.domain.enums | ||||||||||||||||||||||||||||||||||||||||
| 3 core.ipc.IpcKeyFileValidator | ||||||||||||||||||||||||||||||||||||||||
| 4 core.wifi | ||||||||||||||||||||||||||||||||||||||||
| 5 daemon.tunnel | ||||||||||||||||||||||||||||||||||||||||
| 6 desktop.ui.navigation | ||||||||||||||||||||||||||||||||||||||||
| 7 desktop.update | ||||||||||||||||||||||||||||||||||||||||
| 8 client.data.entity | 2 | |||||||||||||||||||||||||||||||||||||||
| 9 core.ipc.IpcKeyFileValidator.Result | 2 | |||||||||||||||||||||||||||||||||||||||
| 10 core.ipc.dto.request | 6 | |||||||||||||||||||||||||||||||||||||||
| 11 desktop.ui.screens.tunnels | 1 | |||||||||||||||||||||||||||||||||||||||
| 12 desktop.util | 1 | |||||||||||||||||||||||||||||||||||||||
| 13 client.data.dao | 8 | |||||||||||||||||||||||||||||||||||||||
| 14 core.ipc | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 15 core.ipc.dto | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 client.data | 8 | |||||||||||||||||||||||||||||||||||||||
| 17 client.domain.model | 3 | 6 | 2 | |||||||||||||||||||||||||||||||||||||
| 18 client.service | 2 | 5 | ||||||||||||||||||||||||||||||||||||||
| 19 client.util | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 20 core.log | 1 | |||||||||||||||||||||||||||||||||||||||
| 21 daemon.data | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 22 daemon.tunnel.RunningTunnel | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 23 client.data.mapper | 8 | 8 | ||||||||||||||||||||||||||||||||||||||
| 24 client.domain.repository | 3 | 1 | 9 | |||||||||||||||||||||||||||||||||||||
| 25 client.orchestration.TunnelCoordinator | 5 | |||||||||||||||||||||||||||||||||||||||
| 26 daemon.autotunnel | 1 | 3 | 1 | |||||||||||||||||||||||||||||||||||||
| 27 daemon.dto | 5 | 1 | ||||||||||||||||||||||||||||||||||||||
| 28 daemon.log | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 29 desktop.ui.state | 3 | 4 | 1 | 4 | 17 | |||||||||||||||||||||||||||||||||||
| 30 desktop.wifi | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 31 client.data.repository | 3 | 1 | 8 | 9 | 9 | |||||||||||||||||||||||||||||||||||
| 32 client.data.service | 2 | 5 | 5 | 4 | ||||||||||||||||||||||||||||||||||||
| 33 client.orchestration | 1 | 2 | 4 | 5 | 7 | 1 | 19 | 2 | ||||||||||||||||||||||||||||||||
| 34 daemon | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 35 daemon.routes | 1 | 3 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 36 desktop.ui.screens.tunnels.components | 2 | 1 | 4 | 1 | ||||||||||||||||||||||||||||||||||||
| 37 desktop.viewmodel | 3 | 7 | 2 | 2 | 4 | 9 | 22 | 1 | 9 | |||||||||||||||||||||||||||||||
| 38 desktop | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 39 desktop.ui.screens.autotunnel.preferred | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 40 desktop.ui.screens.autotunnel.wifi | 1 | 1 |
8→1 client.data.entity uses client.data.model✕
- Connections
- 2 pairs of types, where a type in client.data.entity uses a type in client.data.model.
- The types involved
com.zaneschepke.wireguardautotunnel.client.data.entity.ProxySettings→com.zaneschepke.wireguardautotunnel.client.data.model.EncryptedFieldcom.zaneschepke.wireguardautotunnel.client.data.entity.TunnelConfig→com.zaneschepke.wireguardautotunnel.client.data.model.EncryptedField
- Direction
- client.data.entity uses client.data.model, so a change to client.data.model can break client.data.entity, while a change to client.data.entity can't break client.data.model.
- Position
- Below the diagonal: client.data.entity uses a module listed above it, which is the healthy direction.
9→3 core.ipc.IpcKeyFileValidator.Result uses core.ipc.IpcKeyFileValidator✕
- Connections
- 2 pairs of types, where a type in core.ipc.IpcKeyFileValidator.Result uses a type in core.ipc.IpcKeyFileValidator.
- The types involved
com.zaneschepke.wireguardautotunnel.core.ipc.IpcKeyFileValidator.Result.Rejected→com.zaneschepke.wireguardautotunnel.core.ipc.IpcKeyFileValidator.Resultcom.zaneschepke.wireguardautotunnel.core.ipc.IpcKeyFileValidator.Result.Trusted→com.zaneschepke.wireguardautotunnel.core.ipc.IpcKeyFileValidator.Result
- Direction
- core.ipc.IpcKeyFileValidator.Result uses core.ipc.IpcKeyFileValidator, so a change to core.ipc.IpcKeyFileValidator can break core.ipc.IpcKeyFileValidator.Result, while a change to core.ipc.IpcKeyFileValidator.Result can't break core.ipc.IpcKeyFileValidator.
- Position
- Below the diagonal: core.ipc.IpcKeyFileValidator.Result uses a module listed above it, which is the healthy direction.
10→15 core.ipc.dto.request uses core.ipc.dto part of a loop✕
- Connections
- 6 pairs of types, where a type in core.ipc.dto.request uses a type in core.ipc.dto.
- The types involved
com.zaneschepke.wireguardautotunnel.core.ipc.dto.request.KillSwitchRequest→com.zaneschepke.wireguardautotunnel.core.ipc.dto.KillSwitchConfigDtocom.zaneschepke.wireguardautotunnel.core.ipc.dto.request.StartTunnelRequest→com.zaneschepke.wireguardautotunnel.core.ipc.dto.KillSwitchConfigDtocom.zaneschepke.wireguardautotunnel.core.ipc.dto.request.StartTunnelRequest→com.zaneschepke.wireguardautotunnel.core.ipc.dto.ProxyConfigDtocom.zaneschepke.wireguardautotunnel.core.ipc.dto.request.StartTunnelRequest→com.zaneschepke.wireguardautotunnel.core.ipc.dto.TunnelDnsConfigDtocom.zaneschepke.wireguardautotunnel.core.ipc.dto.request.StartTunnelRequest→com.zaneschepke.wireguardautotunnel.core.ipc.dto.TunnelFeaturesDtocom.zaneschepke.wireguardautotunnel.core.ipc.dto.request.StartTunnelRequest→com.zaneschepke.wireguardautotunnel.core.ipc.dto.TunnelModeDto
- Direction
- core.ipc.dto.request uses core.ipc.dto, so a change to core.ipc.dto can break core.ipc.dto.request, while a change to core.ipc.dto.request can't break core.ipc.dto.
- 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.
11→37 desktop.ui.screens.tunnels uses desktop.viewmodel part of a loop✕
- Connections
- 1 pair of types, where a type in desktop.ui.screens.tunnels uses a type in desktop.viewmodel.
- The types involved
com.zaneschepke.wireguardautotunnel.desktop.ui.screens.tunnels.TunnelsScreenKt→com.zaneschepke.wireguardautotunnel.desktop.viewmodel.TunnelsViewModel
- Direction
- desktop.ui.screens.tunnels uses desktop.viewmodel, so a change to desktop.viewmodel can break desktop.ui.screens.tunnels, while a change to desktop.ui.screens.tunnels can't break desktop.viewmodel.
- 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.
12→2 desktop.util uses client.domain.enums✕
- Connections
- 1 pair of types, where a type in desktop.util uses a type in client.domain.enums.
- The types involved
com.zaneschepke.wireguardautotunnel.desktop.util.EnumStringsKt→com.zaneschepke.wireguardautotunnel.client.domain.enums.TunnelMode
- Direction
- desktop.util uses client.domain.enums, so a change to client.domain.enums can break desktop.util, while a change to desktop.util can't break client.domain.enums.
- Position
- Below the diagonal: desktop.util uses a module listed above it, which is the healthy direction.
13→8 client.data.dao uses client.data.entity✕
- Connections
- 8 pairs of types, where a type in client.data.dao uses a type in client.data.entity.
- The types involved
com.zaneschepke.wireguardautotunnel.client.data.dao.AutoTunnelSettingsDao→com.zaneschepke.wireguardautotunnel.client.data.entity.AutoTunnelSettingscom.zaneschepke.wireguardautotunnel.client.data.dao.DnsSettingsDao→com.zaneschepke.wireguardautotunnel.client.data.entity.DnsSettingscom.zaneschepke.wireguardautotunnel.client.data.dao.GeneralSettingsDao→com.zaneschepke.wireguardautotunnel.client.data.entity.GeneralSettingscom.zaneschepke.wireguardautotunnel.client.data.dao.LockdownSettingsDao→com.zaneschepke.wireguardautotunnel.client.data.entity.LockdownSettingscom.zaneschepke.wireguardautotunnel.client.data.dao.MonitoringSettingsDao→com.zaneschepke.wireguardautotunnel.client.data.entity.MonitoringSettingscom.zaneschepke.wireguardautotunnel.client.data.dao.ProxySettingsDao→com.zaneschepke.wireguardautotunnel.client.data.entity.ProxySettingscom.zaneschepke.wireguardautotunnel.client.data.dao.TunnelConfigDao→com.zaneschepke.wireguardautotunnel.client.data.entity.TunnelConfigcom.zaneschepke.wireguardautotunnel.client.data.dao.TunnelGroupDao→com.zaneschepke.wireguardautotunnel.client.data.entity.TunnelGroup
- Direction
- client.data.dao uses client.data.entity, so a change to client.data.entity can break client.data.dao, while a change to client.data.dao can't break client.data.entity.
- Position
- Below the diagonal: client.data.dao uses a module listed above it, which is the healthy direction.
14→3 core.ipc uses core.ipc.IpcKeyFileValidator✕
- Connections
- 1 pair of types, where a type in core.ipc uses a type in core.ipc.IpcKeyFileValidator.
- The types involved
com.zaneschepke.wireguardautotunnel.core.ipc.IpcKeyFileValidator→com.zaneschepke.wireguardautotunnel.core.ipc.IpcKeyFileValidator.Result
- Direction
- core.ipc uses core.ipc.IpcKeyFileValidator, so a change to core.ipc.IpcKeyFileValidator can break core.ipc, while a change to core.ipc can't break core.ipc.IpcKeyFileValidator.
- Position
- Below the diagonal: core.ipc uses a module listed above it, which is the healthy direction.
14→9 core.ipc uses core.ipc.IpcKeyFileValidator.Result✕
- Connections
- 1 pair of types, where a type in core.ipc uses a type in core.ipc.IpcKeyFileValidator.Result.
- The types involved
com.zaneschepke.wireguardautotunnel.core.ipc.IpcKeyFileValidator→com.zaneschepke.wireguardautotunnel.core.ipc.IpcKeyFileValidator.Result.Rejected
- Direction
- core.ipc uses core.ipc.IpcKeyFileValidator.Result, so a change to core.ipc.IpcKeyFileValidator.Result can break core.ipc, while a change to core.ipc can't break core.ipc.IpcKeyFileValidator.Result.
- Position
- Below the diagonal: core.ipc uses a module listed above it, which is the healthy direction.
15→10 core.ipc.dto uses core.ipc.dto.request✕
- Connections
- 1 pair of types, where a type in core.ipc.dto uses a type in core.ipc.dto.request.
- The types involved
com.zaneschepke.wireguardautotunnel.core.ipc.dto.AutoTunnelTunnelConfigDto→com.zaneschepke.wireguardautotunnel.core.ipc.dto.request.StartTunnelRequest
- Direction
- core.ipc.dto uses core.ipc.dto.request, so a change to core.ipc.dto.request can break core.ipc.dto, while a change to core.ipc.dto can't break core.ipc.dto.request.
- Position
- Below the diagonal: core.ipc.dto uses a module listed above it, which is the healthy direction.
16→13 client.data uses client.data.dao✕
- Connections
- 8 pairs of types, where a type in client.data uses a type in client.data.dao.
- The types involved
com.zaneschepke.wireguardautotunnel.client.data.AppDatabase→com.zaneschepke.wireguardautotunnel.client.data.dao.AutoTunnelSettingsDaocom.zaneschepke.wireguardautotunnel.client.data.AppDatabase→com.zaneschepke.wireguardautotunnel.client.data.dao.DnsSettingsDaocom.zaneschepke.wireguardautotunnel.client.data.AppDatabase→com.zaneschepke.wireguardautotunnel.client.data.dao.GeneralSettingsDaocom.zaneschepke.wireguardautotunnel.client.data.AppDatabase→com.zaneschepke.wireguardautotunnel.client.data.dao.LockdownSettingsDaocom.zaneschepke.wireguardautotunnel.client.data.AppDatabase→com.zaneschepke.wireguardautotunnel.client.data.dao.MonitoringSettingsDaocom.zaneschepke.wireguardautotunnel.client.data.AppDatabase→com.zaneschepke.wireguardautotunnel.client.data.dao.ProxySettingsDaocom.zaneschepke.wireguardautotunnel.client.data.AppDatabase→com.zaneschepke.wireguardautotunnel.client.data.dao.TunnelConfigDaocom.zaneschepke.wireguardautotunnel.client.data.AppDatabase→com.zaneschepke.wireguardautotunnel.client.data.dao.TunnelGroupDao
- Direction
- client.data uses client.data.dao, so a change to client.data.dao can break client.data, while a change to client.data can't break client.data.dao.
- Position
- Below the diagonal: client.data uses a module listed above it, which is the healthy direction.
17→1 client.domain.model uses client.data.model✕
- Connections
- 3 pairs of types, where a type in client.domain.model uses a type in client.data.model.
- The types involved
com.zaneschepke.wireguardautotunnel.client.domain.model.GeneralSettings→com.zaneschepke.wireguardautotunnel.client.data.model.AccentStylecom.zaneschepke.wireguardautotunnel.client.domain.model.GeneralSettings→com.zaneschepke.wireguardautotunnel.client.data.model.Themecom.zaneschepke.wireguardautotunnel.client.domain.model.GeneralSettings→com.zaneschepke.wireguardautotunnel.client.data.model.TrayIconAppearance
- Direction
- client.domain.model uses client.data.model, so a change to client.data.model can break client.domain.model, while a change to client.domain.model can't break client.data.model.
- Position
- Below the diagonal: client.domain.model uses a module listed above it, which is the healthy direction.
17→2 client.domain.model uses client.domain.enums✕
- Connections
- 6 pairs of types, where a type in client.domain.model uses a type in client.domain.enums.
- The types involved
com.zaneschepke.wireguardautotunnel.client.domain.model.DnsSettings→com.zaneschepke.wireguardautotunnel.client.domain.enums.BootstrapDnsProtocolcom.zaneschepke.wireguardautotunnel.client.domain.model.DnsSettings→com.zaneschepke.wireguardautotunnel.client.domain.enums.SplitDnsSuffixTargetcom.zaneschepke.wireguardautotunnel.client.domain.model.DnsSettings→com.zaneschepke.wireguardautotunnel.client.domain.enums.TransitDnsPolicycom.zaneschepke.wireguardautotunnel.client.domain.model.DnsSettings→com.zaneschepke.wireguardautotunnel.client.domain.enums.TunnelDnsModecom.zaneschepke.wireguardautotunnel.client.domain.model.DnsSettings→com.zaneschepke.wireguardautotunnel.client.domain.enums.TunnelDnsProtocolcom.zaneschepke.wireguardautotunnel.client.domain.model.GeneralSettings→com.zaneschepke.wireguardautotunnel.client.domain.enums.TunnelMode
- Direction
- client.domain.model uses client.domain.enums, so a change to client.domain.enums can break client.domain.model, while a change to client.domain.model can't break client.domain.enums.
- Position
- Below the diagonal: client.domain.model uses a module listed above it, which is the healthy direction.
17→15 client.domain.model uses core.ipc.dto✕
- Connections
- 2 pairs of types, where a type in client.domain.model uses a type in core.ipc.dto.
- The types involved
com.zaneschepke.wireguardautotunnel.client.domain.model.LockdownSettings→com.zaneschepke.wireguardautotunnel.core.ipc.dto.KillSwitchConfigDtocom.zaneschepke.wireguardautotunnel.client.domain.model.ProxySettings→com.zaneschepke.wireguardautotunnel.core.ipc.dto.ProxyConfigDto
- Direction
- client.domain.model uses core.ipc.dto, so a change to core.ipc.dto can break client.domain.model, while a change to client.domain.model can't break core.ipc.dto.
- Position
- Below the diagonal: client.domain.model uses a module listed above it, which is the healthy direction.
18→10 client.service uses core.ipc.dto.request✕
- Connections
- 2 pairs of types, where a type in client.service uses a type in core.ipc.dto.request.
- The types involved
com.zaneschepke.wireguardautotunnel.client.service.BackendService→com.zaneschepke.wireguardautotunnel.core.ipc.dto.request.BootstrapDnsModeRequestcom.zaneschepke.wireguardautotunnel.client.service.TunnelService→com.zaneschepke.wireguardautotunnel.core.ipc.dto.request.StartTunnelRequest
- Direction
- client.service uses core.ipc.dto.request, so a change to core.ipc.dto.request can break client.service, while a change to client.service can't break core.ipc.dto.request.
- Position
- Below the diagonal: client.service uses a module listed above it, which is the healthy direction.
18→15 client.service uses core.ipc.dto✕
- Connections
- 5 pairs of types, where a type in client.service uses a type in core.ipc.dto.
- The types involved
com.zaneschepke.wireguardautotunnel.client.service.BackendService→com.zaneschepke.wireguardautotunnel.core.ipc.dto.BackendStatuscom.zaneschepke.wireguardautotunnel.client.service.BackendService→com.zaneschepke.wireguardautotunnel.core.ipc.dto.KillSwitchConfigDtocom.zaneschepke.wireguardautotunnel.client.service.DaemonService→com.zaneschepke.wireguardautotunnel.core.ipc.dto.AutoTunnelConfigDtocom.zaneschepke.wireguardautotunnel.client.service.DaemonService→com.zaneschepke.wireguardautotunnel.core.ipc.dto.AutoTunnelStatusDtocom.zaneschepke.wireguardautotunnel.client.service.DaemonService→com.zaneschepke.wireguardautotunnel.core.ipc.dto.LogMessageDto
- Direction
- client.service uses core.ipc.dto, so a change to core.ipc.dto can break client.service, while a change to client.service can't break core.ipc.dto.
- Position
- Below the diagonal: client.service uses a module listed above it, which is the healthy direction.
19→10 client.util uses core.ipc.dto.request✕
- Connections
- 1 pair of types, where a type in client.util uses a type in core.ipc.dto.request.
- The types involved
com.zaneschepke.wireguardautotunnel.client.util.DnsSettingsExtensionsKt→com.zaneschepke.wireguardautotunnel.core.ipc.dto.request.BootstrapDnsModeRequest
- Direction
- client.util uses core.ipc.dto.request, so a change to core.ipc.dto.request can break client.util, while a change to client.util can't break core.ipc.dto.request.
- Position
- Below the diagonal: client.util uses a module listed above it, which is the healthy direction.
19→15 client.util uses core.ipc.dto✕
- Connections
- 1 pair of types, where a type in client.util uses a type in core.ipc.dto.
- The types involved
com.zaneschepke.wireguardautotunnel.client.util.DnsSettingsExtensionsKt→com.zaneschepke.wireguardautotunnel.core.ipc.dto.TunnelDnsConfigDto
- Direction
- client.util uses core.ipc.dto, so a change to core.ipc.dto can break client.util, while a change to client.util can't break core.ipc.dto.
- Position
- Below the diagonal: client.util uses a module listed above it, which is the healthy direction.
20→15 core.log uses core.ipc.dto✕
- Connections
- 1 pair of types, where a type in core.log uses a type in core.ipc.dto.
- The types involved
com.zaneschepke.wireguardautotunnel.core.log.LogRecorder→com.zaneschepke.wireguardautotunnel.core.ipc.dto.LogMessageDto
- Direction
- core.log uses core.ipc.dto, so a change to core.ipc.dto can break core.log, while a change to core.log can't break core.ipc.dto.
- Position
- Below the diagonal: core.log uses a module listed above it, which is the healthy direction.
21→10 daemon.data uses core.ipc.dto.request✕
- Connections
- 2 pairs of types, where a type in daemon.data uses a type in core.ipc.dto.request.
- The types involved
com.zaneschepke.wireguardautotunnel.daemon.data.DaemonCacheRepository→com.zaneschepke.wireguardautotunnel.core.ipc.dto.request.BootstrapDnsModeRequestcom.zaneschepke.wireguardautotunnel.daemon.data.SettingsDaemonCacheRepository→com.zaneschepke.wireguardautotunnel.core.ipc.dto.request.BootstrapDnsModeRequest
- Direction
- daemon.data uses core.ipc.dto.request, so a change to core.ipc.dto.request can break daemon.data, while a change to daemon.data can't break core.ipc.dto.request.
- Position
- Below the diagonal: daemon.data uses a module listed above it, which is the healthy direction.
21→15 daemon.data uses core.ipc.dto✕
- Connections
- 2 pairs of types, where a type in daemon.data uses a type in core.ipc.dto.
- The types involved
com.zaneschepke.wireguardautotunnel.daemon.data.DaemonCacheRepository→com.zaneschepke.wireguardautotunnel.core.ipc.dto.KillSwitchConfigDtocom.zaneschepke.wireguardautotunnel.daemon.data.SettingsDaemonCacheRepository→com.zaneschepke.wireguardautotunnel.core.ipc.dto.KillSwitchConfigDto
- Direction
- daemon.data uses core.ipc.dto, so a change to core.ipc.dto can break daemon.data, while a change to daemon.data can't break core.ipc.dto.
- Position
- Below the diagonal: daemon.data uses a module listed above it, which is the healthy direction.
22→5 daemon.tunnel.RunningTunnel uses daemon.tunnel✕
- Connections
- 1 pair of types, where a type in daemon.tunnel.RunningTunnel uses a type in daemon.tunnel.
- The types involved
com.zaneschepke.wireguardautotunnel.daemon.tunnel.RunningTunnel.Companion→com.zaneschepke.wireguardautotunnel.daemon.tunnel.RunningTunnel
- Direction
- daemon.tunnel.RunningTunnel uses daemon.tunnel, so a change to daemon.tunnel can break daemon.tunnel.RunningTunnel, while a change to daemon.tunnel.RunningTunnel can't break daemon.tunnel.
- Position
- Below the diagonal: daemon.tunnel.RunningTunnel uses a module listed above it, which is the healthy direction.
22→10 daemon.tunnel.RunningTunnel uses core.ipc.dto.request✕
- Connections
- 1 pair of types, where a type in daemon.tunnel.RunningTunnel uses a type in core.ipc.dto.request.
- The types involved
com.zaneschepke.wireguardautotunnel.daemon.tunnel.RunningTunnel.Companion→com.zaneschepke.wireguardautotunnel.core.ipc.dto.request.StartTunnelRequest
- Direction
- daemon.tunnel.RunningTunnel uses core.ipc.dto.request, so a change to core.ipc.dto.request can break daemon.tunnel.RunningTunnel, while a change to daemon.tunnel.RunningTunnel can't break core.ipc.dto.request.
- Position
- Below the diagonal: daemon.tunnel.RunningTunnel uses a module listed above it, which is the healthy direction.
22→15 daemon.tunnel.RunningTunnel uses core.ipc.dto✕
- Connections
- 1 pair of types, where a type in daemon.tunnel.RunningTunnel uses a type in core.ipc.dto.
- The types involved
com.zaneschepke.wireguardautotunnel.daemon.tunnel.RunningTunnel.Companion→com.zaneschepke.wireguardautotunnel.core.ipc.dto.TunnelFeaturesDto
- Direction
- daemon.tunnel.RunningTunnel uses core.ipc.dto, so a change to core.ipc.dto can break daemon.tunnel.RunningTunnel, while a change to daemon.tunnel.RunningTunnel can't break core.ipc.dto.
- Position
- Below the diagonal: daemon.tunnel.RunningTunnel uses a module listed above it, which is the healthy direction.
23→8 client.data.mapper uses client.data.entity✕
- Connections
- 8 pairs of types, where a type in client.data.mapper uses a type in client.data.entity.
- The types involved
com.zaneschepke.wireguardautotunnel.client.data.mapper.AutoTunnelSettingsMapperKt→com.zaneschepke.wireguardautotunnel.client.data.entity.AutoTunnelSettingscom.zaneschepke.wireguardautotunnel.client.data.mapper.DnsSettingsMapperKt→com.zaneschepke.wireguardautotunnel.client.data.entity.DnsSettingscom.zaneschepke.wireguardautotunnel.client.data.mapper.LockdownMapperKt→com.zaneschepke.wireguardautotunnel.client.data.entity.LockdownSettingscom.zaneschepke.wireguardautotunnel.client.data.mapper.MonitoringSettingsMapperKt→com.zaneschepke.wireguardautotunnel.client.data.entity.MonitoringSettingscom.zaneschepke.wireguardautotunnel.client.data.mapper.ProxySettingsMapperKt→com.zaneschepke.wireguardautotunnel.client.data.entity.ProxySettingscom.zaneschepke.wireguardautotunnel.client.data.mapper.SettingsMapperKt→com.zaneschepke.wireguardautotunnel.client.data.entity.GeneralSettingscom.zaneschepke.wireguardautotunnel.client.data.mapper.TunnelConfigMapperKt→com.zaneschepke.wireguardautotunnel.client.data.entity.TunnelConfigcom.zaneschepke.wireguardautotunnel.client.data.mapper.TunnelGroupMapperKt→com.zaneschepke.wireguardautotunnel.client.data.entity.TunnelGroup
- Direction
- client.data.mapper uses client.data.entity, so a change to client.data.entity can break client.data.mapper, while a change to client.data.mapper can't break client.data.entity.
- Position
- Below the diagonal: client.data.mapper uses a module listed above it, which is the healthy direction.
23→17 client.data.mapper uses client.domain.model✕
- Connections
- 8 pairs of types, where a type in client.data.mapper uses a type in client.domain.model.
- The types involved
com.zaneschepke.wireguardautotunnel.client.data.mapper.AutoTunnelSettingsMapperKt→com.zaneschepke.wireguardautotunnel.client.domain.model.AutoTunnelSettingscom.zaneschepke.wireguardautotunnel.client.data.mapper.DnsSettingsMapperKt→com.zaneschepke.wireguardautotunnel.client.domain.model.DnsSettingscom.zaneschepke.wireguardautotunnel.client.data.mapper.LockdownMapperKt→com.zaneschepke.wireguardautotunnel.client.domain.model.LockdownSettingscom.zaneschepke.wireguardautotunnel.client.data.mapper.MonitoringSettingsMapperKt→com.zaneschepke.wireguardautotunnel.client.domain.model.MonitoringSettingscom.zaneschepke.wireguardautotunnel.client.data.mapper.ProxySettingsMapperKt→com.zaneschepke.wireguardautotunnel.client.domain.model.ProxySettingscom.zaneschepke.wireguardautotunnel.client.data.mapper.SettingsMapperKt→com.zaneschepke.wireguardautotunnel.client.domain.model.GeneralSettingscom.zaneschepke.wireguardautotunnel.client.data.mapper.TunnelConfigMapperKt→com.zaneschepke.wireguardautotunnel.client.domain.model.TunnelConfigcom.zaneschepke.wireguardautotunnel.client.data.mapper.TunnelGroupMapperKt→com.zaneschepke.wireguardautotunnel.client.domain.model.TunnelGroup
- Direction
- client.data.mapper uses client.domain.model, so a change to client.domain.model can break client.data.mapper, while a change to client.data.mapper can't break client.domain.model.
- Position
- Below the diagonal: client.data.mapper uses a module listed above it, which is the healthy direction.
24→1 client.domain.repository uses client.data.model✕
- Connections
- 3 pairs of types, where a type in client.domain.repository uses a type in client.data.model.
- The types involved
com.zaneschepke.wireguardautotunnel.client.domain.repository.GeneralSettingRepository→com.zaneschepke.wireguardautotunnel.client.data.model.AccentStylecom.zaneschepke.wireguardautotunnel.client.domain.repository.GeneralSettingRepository→com.zaneschepke.wireguardautotunnel.client.data.model.Themecom.zaneschepke.wireguardautotunnel.client.domain.repository.GeneralSettingRepository→com.zaneschepke.wireguardautotunnel.client.data.model.TrayIconAppearance
- Direction
- client.domain.repository uses client.data.model, so a change to client.data.model can break client.domain.repository, while a change to client.domain.repository can't break client.data.model.
- Position
- Below the diagonal: client.domain.repository uses a module listed above it, which is the healthy direction.
24→2 client.domain.repository uses client.domain.enums✕
- Connections
- 1 pair of types, where a type in client.domain.repository uses a type in client.domain.enums.
- The types involved
com.zaneschepke.wireguardautotunnel.client.domain.repository.GeneralSettingRepository→com.zaneschepke.wireguardautotunnel.client.domain.enums.TunnelMode
- Direction
- client.domain.repository uses client.domain.enums, so a change to client.domain.enums can break client.domain.repository, while a change to client.domain.repository can't break client.domain.enums.
- Position
- Below the diagonal: client.domain.repository uses a module listed above it, which is the healthy direction.
24→17 client.domain.repository uses client.domain.model✕
- Connections
- 9 pairs of types, where a type in client.domain.repository uses a type in client.domain.model.
- The types involved
com.zaneschepke.wireguardautotunnel.client.domain.repository.AutoTunnelSettingsRepository→com.zaneschepke.wireguardautotunnel.client.domain.model.AutoTunnelSettingscom.zaneschepke.wireguardautotunnel.client.domain.repository.ClientCacheRepository→com.zaneschepke.wireguardautotunnel.client.domain.model.WindowBoundscom.zaneschepke.wireguardautotunnel.client.domain.repository.DnsSettingsRepository→com.zaneschepke.wireguardautotunnel.client.domain.model.DnsSettingscom.zaneschepke.wireguardautotunnel.client.domain.repository.GeneralSettingRepository→com.zaneschepke.wireguardautotunnel.client.domain.model.GeneralSettingscom.zaneschepke.wireguardautotunnel.client.domain.repository.LockdownSettingsRepository→com.zaneschepke.wireguardautotunnel.client.domain.model.LockdownSettingscom.zaneschepke.wireguardautotunnel.client.domain.repository.MonitoringSettingsRepository→com.zaneschepke.wireguardautotunnel.client.domain.model.MonitoringSettingscom.zaneschepke.wireguardautotunnel.client.domain.repository.ProxySettingsRepository→com.zaneschepke.wireguardautotunnel.client.domain.model.ProxySettingscom.zaneschepke.wireguardautotunnel.client.domain.repository.TunnelGroupRepository→com.zaneschepke.wireguardautotunnel.client.domain.model.TunnelGroupcom.zaneschepke.wireguardautotunnel.client.domain.repository.TunnelRepository→com.zaneschepke.wireguardautotunnel.client.domain.model.TunnelConfig
- Direction
- client.domain.repository uses client.domain.model, so a change to client.domain.model can break client.domain.repository, while a change to client.domain.repository can't break client.domain.model.
- Position
- Below the diagonal: client.domain.repository uses a module listed above it, which is the healthy direction.
25→17 client.orchestration.TunnelCoordinator uses client.domain.model✕
- Connections
- 5 pairs of types, where a type in client.orchestration.TunnelCoordinator uses a type in client.domain.model.
- The types involved
com.zaneschepke.wireguardautotunnel.client.orchestration.TunnelCoordinator.RuntimeSettingsSnapshot→com.zaneschepke.wireguardautotunnel.client.domain.model.DnsSettingscom.zaneschepke.wireguardautotunnel.client.orchestration.TunnelCoordinator.RuntimeSettingsSnapshot→com.zaneschepke.wireguardautotunnel.client.domain.model.GeneralSettingscom.zaneschepke.wireguardautotunnel.client.orchestration.TunnelCoordinator.RuntimeSettingsSnapshot→com.zaneschepke.wireguardautotunnel.client.domain.model.LockdownSettingscom.zaneschepke.wireguardautotunnel.client.orchestration.TunnelCoordinator.RuntimeSettingsSnapshot→com.zaneschepke.wireguardautotunnel.client.domain.model.MonitoringSettingscom.zaneschepke.wireguardautotunnel.client.orchestration.TunnelCoordinator.RuntimeSettingsSnapshot→com.zaneschepke.wireguardautotunnel.client.domain.model.ProxySettings
- Direction
- client.orchestration.TunnelCoordinator uses client.domain.model, so a change to client.domain.model can break client.orchestration.TunnelCoordinator, while a change to client.orchestration.TunnelCoordinator can't break client.domain.model.
- Position
- Below the diagonal: client.orchestration.TunnelCoordinator uses a module listed above it, which is the healthy direction.
26→5 daemon.autotunnel uses daemon.tunnel✕
- Connections
- 1 pair of types, where a type in daemon.autotunnel uses a type in daemon.tunnel.
- The types involved
com.zaneschepke.wireguardautotunnel.daemon.autotunnel.AutoTunnelSupervisor→com.zaneschepke.wireguardautotunnel.daemon.tunnel.DesktopNetworkMonitor
- Direction
- daemon.autotunnel uses daemon.tunnel, so a change to daemon.tunnel can break daemon.autotunnel, while a change to daemon.autotunnel can't break daemon.tunnel.
- Position
- Below the diagonal: daemon.autotunnel uses a module listed above it, which is the healthy direction.
26→15 daemon.autotunnel uses core.ipc.dto✕
- Connections
- 3 pairs of types, where a type in daemon.autotunnel uses a type in core.ipc.dto.
- The types involved
com.zaneschepke.wireguardautotunnel.daemon.autotunnel.AutoTunnelSupervisor→com.zaneschepke.wireguardautotunnel.core.ipc.dto.AutoTunnelConfigDtocom.zaneschepke.wireguardautotunnel.daemon.autotunnel.AutoTunnelSupervisor→com.zaneschepke.wireguardautotunnel.core.ipc.dto.AutoTunnelStatusDtocom.zaneschepke.wireguardautotunnel.daemon.autotunnel.AutoTunnelSupervisor→com.zaneschepke.wireguardautotunnel.core.ipc.dto.AutoTunnelTunnelConfigDto
- Direction
- daemon.autotunnel uses core.ipc.dto, so a change to core.ipc.dto can break daemon.autotunnel, while a change to daemon.autotunnel can't break core.ipc.dto.
- Position
- Below the diagonal: daemon.autotunnel uses a module listed above it, which is the healthy direction.
26→21 daemon.autotunnel uses daemon.data✕
- Connections
- 1 pair of types, where a type in daemon.autotunnel uses a type in daemon.data.
- The types involved
com.zaneschepke.wireguardautotunnel.daemon.autotunnel.AutoTunnelSupervisor→com.zaneschepke.wireguardautotunnel.daemon.data.DaemonCacheRepository
- Direction
- daemon.autotunnel uses daemon.data, so a change to daemon.data can break daemon.autotunnel, while a change to daemon.autotunnel can't break daemon.data.
- Position
- Below the diagonal: daemon.autotunnel uses a module listed above it, which is the healthy direction.
27→15 daemon.dto uses core.ipc.dto✕
- Connections
- 5 pairs of types, where a type in daemon.dto uses a type in core.ipc.dto.
- The types involved
com.zaneschepke.wireguardautotunnel.daemon.dto.ExtensionsKt→com.zaneschepke.wireguardautotunnel.core.ipc.dto.BackendModecom.zaneschepke.wireguardautotunnel.daemon.dto.ExtensionsKt→com.zaneschepke.wireguardautotunnel.core.ipc.dto.BackendStatuscom.zaneschepke.wireguardautotunnel.daemon.dto.ExtensionsKt→com.zaneschepke.wireguardautotunnel.core.ipc.dto.ProxyConfigDtocom.zaneschepke.wireguardautotunnel.daemon.dto.ExtensionsKt→com.zaneschepke.wireguardautotunnel.core.ipc.dto.TunnelStatecom.zaneschepke.wireguardautotunnel.daemon.dto.ExtensionsKt→com.zaneschepke.wireguardautotunnel.core.ipc.dto.TunnelStatus
- Direction
- daemon.dto uses core.ipc.dto, so a change to core.ipc.dto can break daemon.dto, while a change to daemon.dto can't break core.ipc.dto.
- Position
- Below the diagonal: daemon.dto uses a module listed above it, which is the healthy direction.
27→21 daemon.dto uses daemon.data✕
- Connections
- 1 pair of types, where a type in daemon.dto uses a type in daemon.data.
- The types involved
com.zaneschepke.wireguardautotunnel.daemon.dto.ExtensionsKt→com.zaneschepke.wireguardautotunnel.daemon.data.DaemonCacheRepository
- Direction
- daemon.dto uses daemon.data, so a change to daemon.data can break daemon.dto, while a change to daemon.dto can't break daemon.data.
- Position
- Below the diagonal: daemon.dto uses a module listed above it, which is the healthy direction.
28→15 daemon.log uses core.ipc.dto✕
- Connections
- 2 pairs of types, where a type in daemon.log uses a type in core.ipc.dto.
- The types involved
com.zaneschepke.wireguardautotunnel.daemon.log.DaemonLogService→com.zaneschepke.wireguardautotunnel.core.ipc.dto.LogMessageDtocom.zaneschepke.wireguardautotunnel.daemon.log.NativeLogTailer→com.zaneschepke.wireguardautotunnel.core.ipc.dto.LogMessageDto
- Direction
- daemon.log uses core.ipc.dto, so a change to core.ipc.dto can break daemon.log, while a change to daemon.log can't break core.ipc.dto.
- Position
- Below the diagonal: daemon.log uses a module listed above it, which is the healthy direction.
28→20 daemon.log uses core.log✕
- Connections
- 1 pair of types, where a type in daemon.log uses a type in core.log.
- The types involved
com.zaneschepke.wireguardautotunnel.daemon.log.DaemonLogService→com.zaneschepke.wireguardautotunnel.core.log.LogRecorder
- Direction
- daemon.log uses core.log, so a change to core.log can break daemon.log, while a change to daemon.log can't break core.log.
- Position
- Below the diagonal: daemon.log uses a module listed above it, which is the healthy direction.
28→21 daemon.log uses daemon.data✕
- Connections
- 1 pair of types, where a type in daemon.log uses a type in daemon.data.
- The types involved
com.zaneschepke.wireguardautotunnel.daemon.log.DaemonLogService→com.zaneschepke.wireguardautotunnel.daemon.data.DaemonCacheRepository
- Direction
- daemon.log uses daemon.data, so a change to daemon.data can break daemon.log, while a change to daemon.log can't break daemon.data.
- Position
- Below the diagonal: daemon.log uses a module listed above it, which is the healthy direction.
29→1 desktop.ui.state uses client.data.model✕
- Connections
- 3 pairs of types, where a type in desktop.ui.state uses a type in client.data.model.
- The types involved
com.zaneschepke.wireguardautotunnel.desktop.ui.state.AppUiState→com.zaneschepke.wireguardautotunnel.client.data.model.AccentStylecom.zaneschepke.wireguardautotunnel.desktop.ui.state.AppUiState→com.zaneschepke.wireguardautotunnel.client.data.model.Themecom.zaneschepke.wireguardautotunnel.desktop.ui.state.AppUiState→com.zaneschepke.wireguardautotunnel.client.data.model.TrayIconAppearance
- Direction
- desktop.ui.state uses client.data.model, so a change to client.data.model can break desktop.ui.state, while a change to desktop.ui.state can't break client.data.model.
- Position
- Below the diagonal: desktop.ui.state uses a module listed above it, which is the healthy direction.
29→2 desktop.ui.state uses client.domain.enums✕
- Connections
- 4 pairs of types, where a type in desktop.ui.state uses a type in client.domain.enums.
- The types involved
com.zaneschepke.wireguardautotunnel.desktop.ui.state.AppUiState→com.zaneschepke.wireguardautotunnel.client.domain.enums.TunnelModecom.zaneschepke.wireguardautotunnel.desktop.ui.state.DnsUiState→com.zaneschepke.wireguardautotunnel.client.domain.enums.TunnelModecom.zaneschepke.wireguardautotunnel.desktop.ui.state.MonitoringUiState→com.zaneschepke.wireguardautotunnel.client.domain.enums.StatisticRefreshcom.zaneschepke.wireguardautotunnel.desktop.ui.state.SettingsUiState→com.zaneschepke.wireguardautotunnel.client.domain.enums.TunnelMode
- Direction
- desktop.ui.state uses client.domain.enums, so a change to client.domain.enums can break desktop.ui.state, while a change to desktop.ui.state can't break client.domain.enums.
- Position
- Below the diagonal: desktop.ui.state uses a module listed above it, which is the healthy direction.
29→7 desktop.ui.state uses desktop.update✕
- Connections
- 1 pair of types, where a type in desktop.ui.state uses a type in desktop.update.
- The types involved
com.zaneschepke.wireguardautotunnel.desktop.ui.state.SupportUiState→com.zaneschepke.wireguardautotunnel.desktop.update.UpdateState
- Direction
- desktop.ui.state uses desktop.update, so a change to desktop.update can break desktop.ui.state, while a change to desktop.ui.state can't break desktop.update.
- Position
- Below the diagonal: desktop.ui.state uses a module listed above it, which is the healthy direction.
29→15 desktop.ui.state uses core.ipc.dto✕
- Connections
- 4 pairs of types, where a type in desktop.ui.state uses a type in core.ipc.dto.
- The types involved
com.zaneschepke.wireguardautotunnel.desktop.ui.state.AppUiState→com.zaneschepke.wireguardautotunnel.core.ipc.dto.TunnelStatuscom.zaneschepke.wireguardautotunnel.desktop.ui.state.AutoTunnelUiState→com.zaneschepke.wireguardautotunnel.core.ipc.dto.NetworkStatusDtocom.zaneschepke.wireguardautotunnel.desktop.ui.state.LoggerUiState→com.zaneschepke.wireguardautotunnel.core.ipc.dto.LogMessageDtocom.zaneschepke.wireguardautotunnel.desktop.ui.state.TunnelUiItem→com.zaneschepke.wireguardautotunnel.core.ipc.dto.TunnelStatus
- Direction
- desktop.ui.state uses core.ipc.dto, so a change to core.ipc.dto can break desktop.ui.state, while a change to desktop.ui.state can't break core.ipc.dto.
- Position
- Below the diagonal: desktop.ui.state uses a module listed above it, which is the healthy direction.
29→17 desktop.ui.state uses client.domain.model✕
- Connections
- 17 pairs of types, where a type in desktop.ui.state uses a type in client.domain.model.
- The types involved
com.zaneschepke.wireguardautotunnel.desktop.ui.state.AutoTunnelUiState→com.zaneschepke.wireguardautotunnel.client.domain.model.AutoTunnelSettingscom.zaneschepke.wireguardautotunnel.desktop.ui.state.AutoTunnelUiState→com.zaneschepke.wireguardautotunnel.client.domain.model.TunnelConfigcom.zaneschepke.wireguardautotunnel.desktop.ui.state.DnsUiState→com.zaneschepke.wireguardautotunnel.client.domain.model.DnsSettingscom.zaneschepke.wireguardautotunnel.desktop.ui.state.GlobalConfigUiState→com.zaneschepke.wireguardautotunnel.client.domain.model.TunnelConfigcom.zaneschepke.wireguardautotunnel.desktop.ui.state.ProxyUiState→com.zaneschepke.wireguardautotunnel.client.domain.model.ProxySettingscom.zaneschepke.wireguardautotunnel.desktop.ui.state.SettingsUiState→com.zaneschepke.wireguardautotunnel.client.domain.model.AutoTunnelSettingscom.zaneschepke.wireguardautotunnel.desktop.ui.state.SettingsUiState→com.zaneschepke.wireguardautotunnel.client.domain.model.DnsSettingscom.zaneschepke.wireguardautotunnel.desktop.ui.state.SettingsUiState→com.zaneschepke.wireguardautotunnel.client.domain.model.GeneralSettingscom.zaneschepke.wireguardautotunnel.desktop.ui.state.SettingsUiState→com.zaneschepke.wireguardautotunnel.client.domain.model.LockdownSettingscom.zaneschepke.wireguardautotunnel.desktop.ui.state.SettingsUiState→com.zaneschepke.wireguardautotunnel.client.domain.model.MonitoringSettingscom.zaneschepke.wireguardautotunnel.desktop.ui.state.SettingsUiState→com.zaneschepke.wireguardautotunnel.client.domain.model.TunnelConfigcom.zaneschepke.wireguardautotunnel.desktop.ui.state.TunnelListRowsKt→com.zaneschepke.wireguardautotunnel.client.domain.model.TunnelConfigcom.zaneschepke.wireguardautotunnel.desktop.ui.state.TunnelListRowsKt→com.zaneschepke.wireguardautotunnel.client.domain.model.TunnelGroupcom.zaneschepke.wireguardautotunnel.desktop.ui.state.TunnelUiItem→com.zaneschepke.wireguardautotunnel.client.domain.model.TunnelConfigcom.zaneschepke.wireguardautotunnel.desktop.ui.state.TunnelUiState→com.zaneschepke.wireguardautotunnel.client.domain.model.TunnelConfigcom.zaneschepke.wireguardautotunnel.desktop.ui.state.TunnelsUiState→com.zaneschepke.wireguardautotunnel.client.domain.model.TunnelConfigcom.zaneschepke.wireguardautotunnel.desktop.ui.state.TunnelsUiState→com.zaneschepke.wireguardautotunnel.client.domain.model.TunnelGroup
- Direction
- desktop.ui.state uses client.domain.model, so a change to client.domain.model can break desktop.ui.state, while a change to desktop.ui.state can't break client.domain.model.
- Position
- Below the diagonal: desktop.ui.state uses a module listed above it, which is the healthy direction.
30→4 desktop.wifi uses core.wifi✕
- Connections
- 1 pair of types, where a type in desktop.wifi uses a type in core.wifi.
- The types involved
com.zaneschepke.wireguardautotunnel.desktop.wifi.MacWifiNameCoordinator→com.zaneschepke.wireguardautotunnel.core.wifi.WifiAuthorization
- Direction
- desktop.wifi uses core.wifi, so a change to core.wifi can break desktop.wifi, while a change to desktop.wifi can't break core.wifi.
- Position
- Below the diagonal: desktop.wifi uses a module listed above it, which is the healthy direction.
30→18 desktop.wifi uses client.service✕
- Connections
- 1 pair of types, where a type in desktop.wifi uses a type in client.service.
- The types involved
com.zaneschepke.wireguardautotunnel.desktop.wifi.MacWifiNameCoordinator→com.zaneschepke.wireguardautotunnel.client.service.DaemonService
- Direction
- desktop.wifi uses client.service, so a change to client.service can break desktop.wifi, while a change to desktop.wifi can't break client.service.
- Position
- Below the diagonal: desktop.wifi uses a module listed above it, which is the healthy direction.
31→1 client.data.repository uses client.data.model✕
- Connections
- 3 pairs of types, where a type in client.data.repository uses a type in client.data.model.
- The types involved
com.zaneschepke.wireguardautotunnel.client.data.repository.RoomSettingsRepository→com.zaneschepke.wireguardautotunnel.client.data.model.AccentStylecom.zaneschepke.wireguardautotunnel.client.data.repository.RoomSettingsRepository→com.zaneschepke.wireguardautotunnel.client.data.model.Themecom.zaneschepke.wireguardautotunnel.client.data.repository.RoomSettingsRepository→com.zaneschepke.wireguardautotunnel.client.data.model.TrayIconAppearance
- Direction
- client.data.repository uses client.data.model, so a change to client.data.model can break client.data.repository, while a change to client.data.repository can't break client.data.model.
- Position
- Below the diagonal: client.data.repository uses a module listed above it, which is the healthy direction.
31→2 client.data.repository uses client.domain.enums✕
- Connections
- 1 pair of types, where a type in client.data.repository uses a type in client.domain.enums.
- The types involved
com.zaneschepke.wireguardautotunnel.client.data.repository.RoomSettingsRepository→com.zaneschepke.wireguardautotunnel.client.domain.enums.TunnelMode
- Direction
- client.data.repository uses client.domain.enums, so a change to client.domain.enums can break client.data.repository, while a change to client.data.repository can't break client.domain.enums.
- Position
- Below the diagonal: client.data.repository uses a module listed above it, which is the healthy direction.
31→13 client.data.repository uses client.data.dao✕
- Connections
- 8 pairs of types, where a type in client.data.repository uses a type in client.data.dao.
- The types involved
com.zaneschepke.wireguardautotunnel.client.data.repository.RoomAutoTunnelSettingsRepository→com.zaneschepke.wireguardautotunnel.client.data.dao.AutoTunnelSettingsDaocom.zaneschepke.wireguardautotunnel.client.data.repository.RoomDnsSettingsRepository→com.zaneschepke.wireguardautotunnel.client.data.dao.DnsSettingsDaocom.zaneschepke.wireguardautotunnel.client.data.repository.RoomLockdownSettingsRepository→com.zaneschepke.wireguardautotunnel.client.data.dao.LockdownSettingsDaocom.zaneschepke.wireguardautotunnel.client.data.repository.RoomMonitoringSettingsRepository→com.zaneschepke.wireguardautotunnel.client.data.dao.MonitoringSettingsDaocom.zaneschepke.wireguardautotunnel.client.data.repository.RoomProxySettingsRepository→com.zaneschepke.wireguardautotunnel.client.data.dao.ProxySettingsDaocom.zaneschepke.wireguardautotunnel.client.data.repository.RoomSettingsRepository→com.zaneschepke.wireguardautotunnel.client.data.dao.GeneralSettingsDaocom.zaneschepke.wireguardautotunnel.client.data.repository.RoomTunnelGroupRepository→com.zaneschepke.wireguardautotunnel.client.data.dao.TunnelGroupDaocom.zaneschepke.wireguardautotunnel.client.data.repository.RoomTunnelRepository→com.zaneschepke.wireguardautotunnel.client.data.dao.TunnelConfigDao
- Direction
- client.data.repository uses client.data.dao, so a change to client.data.dao can break client.data.repository, while a change to client.data.repository can't break client.data.dao.
- Position
- Below the diagonal: client.data.repository uses a module listed above it, which is the healthy direction.
31→17 client.data.repository uses client.domain.model✕
- Connections
- 9 pairs of types, where a type in client.data.repository uses a type in client.domain.model.
- The types involved
com.zaneschepke.wireguardautotunnel.client.data.repository.PropertiesClientCacheRepository→com.zaneschepke.wireguardautotunnel.client.domain.model.WindowBoundscom.zaneschepke.wireguardautotunnel.client.data.repository.RoomAutoTunnelSettingsRepository→com.zaneschepke.wireguardautotunnel.client.domain.model.AutoTunnelSettingscom.zaneschepke.wireguardautotunnel.client.data.repository.RoomDnsSettingsRepository→com.zaneschepke.wireguardautotunnel.client.domain.model.DnsSettingscom.zaneschepke.wireguardautotunnel.client.data.repository.RoomLockdownSettingsRepository→com.zaneschepke.wireguardautotunnel.client.domain.model.LockdownSettingscom.zaneschepke.wireguardautotunnel.client.data.repository.RoomMonitoringSettingsRepository→com.zaneschepke.wireguardautotunnel.client.domain.model.MonitoringSettingscom.zaneschepke.wireguardautotunnel.client.data.repository.RoomProxySettingsRepository→com.zaneschepke.wireguardautotunnel.client.domain.model.ProxySettingscom.zaneschepke.wireguardautotunnel.client.data.repository.RoomSettingsRepository→com.zaneschepke.wireguardautotunnel.client.domain.model.GeneralSettingscom.zaneschepke.wireguardautotunnel.client.data.repository.RoomTunnelGroupRepository→com.zaneschepke.wireguardautotunnel.client.domain.model.TunnelGroupcom.zaneschepke.wireguardautotunnel.client.data.repository.RoomTunnelRepository→com.zaneschepke.wireguardautotunnel.client.domain.model.TunnelConfig
- Direction
- client.data.repository uses client.domain.model, so a change to client.domain.model can break client.data.repository, while a change to client.data.repository can't break client.domain.model.
- Position
- Below the diagonal: client.data.repository uses a module listed above it, which is the healthy direction.
31→24 client.data.repository uses client.domain.repository✕
- Connections
- 9 pairs of types, where a type in client.data.repository uses a type in client.domain.repository.
- The types involved
com.zaneschepke.wireguardautotunnel.client.data.repository.PropertiesClientCacheRepository→com.zaneschepke.wireguardautotunnel.client.domain.repository.ClientCacheRepositorycom.zaneschepke.wireguardautotunnel.client.data.repository.RoomAutoTunnelSettingsRepository→com.zaneschepke.wireguardautotunnel.client.domain.repository.AutoTunnelSettingsRepositorycom.zaneschepke.wireguardautotunnel.client.data.repository.RoomDnsSettingsRepository→com.zaneschepke.wireguardautotunnel.client.domain.repository.DnsSettingsRepositorycom.zaneschepke.wireguardautotunnel.client.data.repository.RoomLockdownSettingsRepository→com.zaneschepke.wireguardautotunnel.client.domain.repository.LockdownSettingsRepositorycom.zaneschepke.wireguardautotunnel.client.data.repository.RoomMonitoringSettingsRepository→com.zaneschepke.wireguardautotunnel.client.domain.repository.MonitoringSettingsRepositorycom.zaneschepke.wireguardautotunnel.client.data.repository.RoomProxySettingsRepository→com.zaneschepke.wireguardautotunnel.client.domain.repository.ProxySettingsRepositorycom.zaneschepke.wireguardautotunnel.client.data.repository.RoomSettingsRepository→com.zaneschepke.wireguardautotunnel.client.domain.repository.GeneralSettingRepositorycom.zaneschepke.wireguardautotunnel.client.data.repository.RoomTunnelGroupRepository→com.zaneschepke.wireguardautotunnel.client.domain.repository.TunnelGroupRepositorycom.zaneschepke.wireguardautotunnel.client.data.repository.RoomTunnelRepository→com.zaneschepke.wireguardautotunnel.client.domain.repository.TunnelRepository
- Direction
- client.data.repository uses client.domain.repository, so a change to client.domain.repository can break client.data.repository, while a change to client.data.repository can't break client.domain.repository.
- Position
- Below the diagonal: client.data.repository uses a module listed above it, which is the healthy direction.
32→10 client.data.service uses core.ipc.dto.request✕
- Connections
- 2 pairs of types, where a type in client.data.service uses a type in core.ipc.dto.request.
- The types involved
com.zaneschepke.wireguardautotunnel.client.data.service.UdsBackendService→com.zaneschepke.wireguardautotunnel.core.ipc.dto.request.BootstrapDnsModeRequestcom.zaneschepke.wireguardautotunnel.client.data.service.UdsTunnelService→com.zaneschepke.wireguardautotunnel.core.ipc.dto.request.StartTunnelRequest
- Direction
- client.data.service uses core.ipc.dto.request, so a change to core.ipc.dto.request can break client.data.service, while a change to client.data.service can't break core.ipc.dto.request.
- Position
- Below the diagonal: client.data.service uses a module listed above it, which is the healthy direction.
32→15 client.data.service uses core.ipc.dto✕
- Connections
- 5 pairs of types, where a type in client.data.service uses a type in core.ipc.dto.
- The types involved
com.zaneschepke.wireguardautotunnel.client.data.service.UdsBackendService→com.zaneschepke.wireguardautotunnel.core.ipc.dto.BackendStatuscom.zaneschepke.wireguardautotunnel.client.data.service.UdsBackendService→com.zaneschepke.wireguardautotunnel.core.ipc.dto.KillSwitchConfigDtocom.zaneschepke.wireguardautotunnel.client.data.service.UdsDaemonService→com.zaneschepke.wireguardautotunnel.core.ipc.dto.AutoTunnelConfigDtocom.zaneschepke.wireguardautotunnel.client.data.service.UdsDaemonService→com.zaneschepke.wireguardautotunnel.core.ipc.dto.AutoTunnelStatusDtocom.zaneschepke.wireguardautotunnel.client.data.service.UdsDaemonService→com.zaneschepke.wireguardautotunnel.core.ipc.dto.LogMessageDto
- Direction
- client.data.service uses core.ipc.dto, so a change to core.ipc.dto can break client.data.service, while a change to client.data.service can't break core.ipc.dto.
- Position
- Below the diagonal: client.data.service uses a module listed above it, which is the healthy direction.
32→18 client.data.service uses client.service✕
- Connections
- 5 pairs of types, where a type in client.data.service uses a type in client.service.
- The types involved
com.zaneschepke.wireguardautotunnel.client.data.service.DefaultTunnelImportService→com.zaneschepke.wireguardautotunnel.client.service.TunnelImportServicecom.zaneschepke.wireguardautotunnel.client.data.service.UdsBackendService→com.zaneschepke.wireguardautotunnel.client.service.BackendServicecom.zaneschepke.wireguardautotunnel.client.data.service.UdsBackendService→com.zaneschepke.wireguardautotunnel.client.service.DaemonServicecom.zaneschepke.wireguardautotunnel.client.data.service.UdsDaemonService→com.zaneschepke.wireguardautotunnel.client.service.DaemonServicecom.zaneschepke.wireguardautotunnel.client.data.service.UdsTunnelService→com.zaneschepke.wireguardautotunnel.client.service.TunnelService
- Direction
- client.data.service uses client.service, so a change to client.service can break client.data.service, while a change to client.data.service can't break client.service.
- Position
- Below the diagonal: client.data.service uses a module listed above it, which is the healthy direction.
32→24 client.data.service uses client.domain.repository✕
- Connections
- 4 pairs of types, where a type in client.data.service uses a type in client.domain.repository.
- The types involved
com.zaneschepke.wireguardautotunnel.client.data.service.DefaultTunnelImportService→com.zaneschepke.wireguardautotunnel.client.domain.repository.TunnelGroupRepositorycom.zaneschepke.wireguardautotunnel.client.data.service.DefaultTunnelImportService→com.zaneschepke.wireguardautotunnel.client.domain.repository.TunnelRepositorycom.zaneschepke.wireguardautotunnel.client.data.service.UdsBackendService→com.zaneschepke.wireguardautotunnel.client.domain.repository.LockdownSettingsRepositorycom.zaneschepke.wireguardautotunnel.client.data.service.UdsDaemonService→com.zaneschepke.wireguardautotunnel.client.domain.repository.LockdownSettingsRepository
- Direction
- client.data.service uses client.domain.repository, so a change to client.domain.repository can break client.data.service, while a change to client.data.service can't break client.domain.repository.
- Position
- Below the diagonal: client.data.service uses a module listed above it, which is the healthy direction.
33→2 client.orchestration uses client.domain.enums✕
- Connections
- 1 pair of types, where a type in client.orchestration uses a type in client.domain.enums.
- The types involved
com.zaneschepke.wireguardautotunnel.client.orchestration.TunnelBackendCoordinator→com.zaneschepke.wireguardautotunnel.client.domain.enums.TunnelMode
- Direction
- client.orchestration uses client.domain.enums, so a change to client.domain.enums can break client.orchestration, while a change to client.orchestration can't break client.domain.enums.
- Position
- Below the diagonal: client.orchestration uses a module listed above it, which is the healthy direction.
33→10 client.orchestration uses core.ipc.dto.request✕
- Connections
- 2 pairs of types, where a type in client.orchestration uses a type in core.ipc.dto.request.
- The types involved
com.zaneschepke.wireguardautotunnel.client.orchestration.DnsSettingsCoordinator→com.zaneschepke.wireguardautotunnel.core.ipc.dto.request.BootstrapDnsModeRequestcom.zaneschepke.wireguardautotunnel.client.orchestration.TunnelCoordinator→com.zaneschepke.wireguardautotunnel.core.ipc.dto.request.StartTunnelRequest
- Direction
- client.orchestration uses core.ipc.dto.request, so a change to core.ipc.dto.request can break client.orchestration, while a change to client.orchestration can't break core.ipc.dto.request.
- Position
- Below the diagonal: client.orchestration uses a module listed above it, which is the healthy direction.
33→15 client.orchestration uses core.ipc.dto✕
- Connections
- 4 pairs of types, where a type in client.orchestration uses a type in core.ipc.dto.
- The types involved
com.zaneschepke.wireguardautotunnel.client.orchestration.AutoTunnelCoordinator→com.zaneschepke.wireguardautotunnel.core.ipc.dto.AutoTunnelConfigDtocom.zaneschepke.wireguardautotunnel.client.orchestration.LogCoordinator→com.zaneschepke.wireguardautotunnel.core.ipc.dto.LogMessageDtocom.zaneschepke.wireguardautotunnel.client.orchestration.TunnelBackendCoordinator→com.zaneschepke.wireguardautotunnel.core.ipc.dto.KillSwitchConfigDtocom.zaneschepke.wireguardautotunnel.client.orchestration.TunnelCoordinator→com.zaneschepke.wireguardautotunnel.core.ipc.dto.KillSwitchConfigDto
- Direction
- client.orchestration uses core.ipc.dto, so a change to core.ipc.dto can break client.orchestration, while a change to client.orchestration can't break core.ipc.dto.
- Position
- Below the diagonal: client.orchestration uses a module listed above it, which is the healthy direction.
33→17 client.orchestration uses client.domain.model✕
- Connections
- 5 pairs of types, where a type in client.orchestration uses a type in client.domain.model.
- The types involved
com.zaneschepke.wireguardautotunnel.client.orchestration.AutoTunnelCoordinator→com.zaneschepke.wireguardautotunnel.client.domain.model.AutoTunnelSettingscom.zaneschepke.wireguardautotunnel.client.orchestration.AutoTunnelCoordinator→com.zaneschepke.wireguardautotunnel.client.domain.model.TunnelConfigcom.zaneschepke.wireguardautotunnel.client.orchestration.TunnelBackendCoordinator→com.zaneschepke.wireguardautotunnel.client.domain.model.LockdownSettingscom.zaneschepke.wireguardautotunnel.client.orchestration.TunnelCoordinator→com.zaneschepke.wireguardautotunnel.client.domain.model.LockdownSettingscom.zaneschepke.wireguardautotunnel.client.orchestration.TunnelCoordinator→com.zaneschepke.wireguardautotunnel.client.domain.model.TunnelConfig
- Direction
- client.orchestration uses client.domain.model, so a change to client.domain.model can break client.orchestration, while a change to client.orchestration can't break client.domain.model.
- Position
- Below the diagonal: client.orchestration uses a module listed above it, which is the healthy direction.
33→18 client.orchestration uses client.service✕
- Connections
- 7 pairs of types, where a type in client.orchestration uses a type in client.service.
- The types involved
com.zaneschepke.wireguardautotunnel.client.orchestration.AutoTunnelCoordinator→com.zaneschepke.wireguardautotunnel.client.service.DaemonServicecom.zaneschepke.wireguardautotunnel.client.orchestration.DnsSettingsCoordinator→com.zaneschepke.wireguardautotunnel.client.service.BackendServicecom.zaneschepke.wireguardautotunnel.client.orchestration.DnsSettingsCoordinator→com.zaneschepke.wireguardautotunnel.client.service.DaemonServicecom.zaneschepke.wireguardautotunnel.client.orchestration.LogCoordinator→com.zaneschepke.wireguardautotunnel.client.service.DaemonServicecom.zaneschepke.wireguardautotunnel.client.orchestration.TunnelBackendCoordinator→com.zaneschepke.wireguardautotunnel.client.service.BackendServicecom.zaneschepke.wireguardautotunnel.client.orchestration.TunnelCoordinator→com.zaneschepke.wireguardautotunnel.client.service.BackendServicecom.zaneschepke.wireguardautotunnel.client.orchestration.TunnelCoordinator→com.zaneschepke.wireguardautotunnel.client.service.TunnelService
- Direction
- client.orchestration uses client.service, so a change to client.service can break client.orchestration, while a change to client.orchestration can't break client.service.
- Position
- Below the diagonal: client.orchestration uses a module listed above it, which is the healthy direction.
33→20 client.orchestration uses core.log✕
- Connections
- 1 pair of types, where a type in client.orchestration uses a type in core.log.
- The types involved
com.zaneschepke.wireguardautotunnel.client.orchestration.LogCoordinator→com.zaneschepke.wireguardautotunnel.core.log.LogRecorder
- Direction
- client.orchestration uses core.log, so a change to core.log can break client.orchestration, while a change to client.orchestration can't break core.log.
- Position
- Below the diagonal: client.orchestration uses a module listed above it, which is the healthy direction.
33→24 client.orchestration uses client.domain.repository✕
- Connections
- 19 pairs of types, where a type in client.orchestration uses a type in client.domain.repository.
- The types involved
com.zaneschepke.wireguardautotunnel.client.orchestration.AutoTunnelCoordinator→com.zaneschepke.wireguardautotunnel.client.domain.repository.AutoTunnelSettingsRepositorycom.zaneschepke.wireguardautotunnel.client.orchestration.AutoTunnelCoordinator→com.zaneschepke.wireguardautotunnel.client.domain.repository.DnsSettingsRepositorycom.zaneschepke.wireguardautotunnel.client.orchestration.AutoTunnelCoordinator→com.zaneschepke.wireguardautotunnel.client.domain.repository.GeneralSettingRepositorycom.zaneschepke.wireguardautotunnel.client.orchestration.AutoTunnelCoordinator→com.zaneschepke.wireguardautotunnel.client.domain.repository.LockdownSettingsRepositorycom.zaneschepke.wireguardautotunnel.client.orchestration.AutoTunnelCoordinator→com.zaneschepke.wireguardautotunnel.client.domain.repository.MonitoringSettingsRepositorycom.zaneschepke.wireguardautotunnel.client.orchestration.AutoTunnelCoordinator→com.zaneschepke.wireguardautotunnel.client.domain.repository.ProxySettingsRepositorycom.zaneschepke.wireguardautotunnel.client.orchestration.AutoTunnelCoordinator→com.zaneschepke.wireguardautotunnel.client.domain.repository.TunnelRepositorycom.zaneschepke.wireguardautotunnel.client.orchestration.DnsSettingsCoordinator→com.zaneschepke.wireguardautotunnel.client.domain.repository.DnsSettingsRepositorycom.zaneschepke.wireguardautotunnel.client.orchestration.LogCoordinator→com.zaneschepke.wireguardautotunnel.client.domain.repository.MonitoringSettingsRepositorycom.zaneschepke.wireguardautotunnel.client.orchestration.TunnelBackendCoordinator→com.zaneschepke.wireguardautotunnel.client.domain.repository.GeneralSettingRepositorycom.zaneschepke.wireguardautotunnel.client.orchestration.TunnelBackendCoordinator→com.zaneschepke.wireguardautotunnel.client.domain.repository.LockdownSettingsRepositorycom.zaneschepke.wireguardautotunnel.client.orchestration.TunnelBackendCoordinator→com.zaneschepke.wireguardautotunnel.client.domain.repository.TunnelRepositorycom.zaneschepke.wireguardautotunnel.client.orchestration.TunnelCoordinator→com.zaneschepke.wireguardautotunnel.client.domain.repository.ClientCacheRepositorycom.zaneschepke.wireguardautotunnel.client.orchestration.TunnelCoordinator→com.zaneschepke.wireguardautotunnel.client.domain.repository.DnsSettingsRepositorycom.zaneschepke.wireguardautotunnel.client.orchestration.TunnelCoordinator→com.zaneschepke.wireguardautotunnel.client.domain.repository.GeneralSettingRepositorycom.zaneschepke.wireguardautotunnel.client.orchestration.TunnelCoordinator→com.zaneschepke.wireguardautotunnel.client.domain.repository.LockdownSettingsRepositorycom.zaneschepke.wireguardautotunnel.client.orchestration.TunnelCoordinator→com.zaneschepke.wireguardautotunnel.client.domain.repository.MonitoringSettingsRepositorycom.zaneschepke.wireguardautotunnel.client.orchestration.TunnelCoordinator→com.zaneschepke.wireguardautotunnel.client.domain.repository.ProxySettingsRepositorycom.zaneschepke.wireguardautotunnel.client.orchestration.TunnelCoordinator→com.zaneschepke.wireguardautotunnel.client.domain.repository.TunnelRepository
- Direction
- client.orchestration uses client.domain.repository, so a change to client.domain.repository can break client.orchestration, while a change to client.orchestration can't break client.domain.repository.
- Position
- Below the diagonal: client.orchestration uses a module listed above it, which is the healthy direction.
33→25 client.orchestration uses client.orchestration.TunnelCoordinator✕
- Connections
- 2 pairs of types, where a type in client.orchestration uses a type in client.orchestration.TunnelCoordinator.
- The types involved
com.zaneschepke.wireguardautotunnel.client.orchestration.AutoTunnelCoordinator→com.zaneschepke.wireguardautotunnel.client.orchestration.TunnelCoordinator.RuntimeSettingsSnapshotcom.zaneschepke.wireguardautotunnel.client.orchestration.TunnelCoordinator→com.zaneschepke.wireguardautotunnel.client.orchestration.TunnelCoordinator.RuntimeSettingsSnapshot
- Direction
- client.orchestration uses client.orchestration.TunnelCoordinator, so a change to client.orchestration.TunnelCoordinator can break client.orchestration, while a change to client.orchestration can't break client.orchestration.TunnelCoordinator.
- Position
- Below the diagonal: client.orchestration uses a module listed above it, which is the healthy direction.
34→5 daemon uses daemon.tunnel✕
- Connections
- 1 pair of types, where a type in daemon uses a type in daemon.tunnel.
- The types involved
com.zaneschepke.wireguardautotunnel.daemon.TunnelDaemon→com.zaneschepke.wireguardautotunnel.daemon.tunnel.DesktopNetworkMonitor
- Direction
- daemon uses daemon.tunnel, so a change to daemon.tunnel can break daemon, while a change to daemon can't break daemon.tunnel.
- Position
- Below the diagonal: daemon uses a module listed above it, which is the healthy direction.
34→21 daemon uses daemon.data✕
- Connections
- 1 pair of types, where a type in daemon uses a type in daemon.data.
- The types involved
com.zaneschepke.wireguardautotunnel.daemon.TunnelDaemon→com.zaneschepke.wireguardautotunnel.daemon.data.DaemonCacheRepository
- Direction
- daemon uses daemon.data, so a change to daemon.data can break daemon, while a change to daemon can't break daemon.data.
- Position
- Below the diagonal: daemon uses a module listed above it, which is the healthy direction.
34→26 daemon uses daemon.autotunnel✕
- Connections
- 1 pair of types, where a type in daemon uses a type in daemon.autotunnel.
- The types involved
com.zaneschepke.wireguardautotunnel.daemon.TunnelDaemon→com.zaneschepke.wireguardautotunnel.daemon.autotunnel.AutoTunnelSupervisor
- Direction
- daemon uses daemon.autotunnel, so a change to daemon.autotunnel can break daemon, while a change to daemon can't break daemon.autotunnel.
- Position
- Below the diagonal: daemon uses a module listed above it, which is the healthy direction.
34→28 daemon uses daemon.log✕
- Connections
- 1 pair of types, where a type in daemon uses a type in daemon.log.
- The types involved
com.zaneschepke.wireguardautotunnel.daemon.TunnelDaemon→com.zaneschepke.wireguardautotunnel.daemon.log.DaemonLogService
- Direction
- daemon uses daemon.log, so a change to daemon.log can break daemon, while a change to daemon can't break daemon.log.
- Position
- Below the diagonal: daemon uses a module listed above it, which is the healthy direction.
35→5 daemon.routes uses daemon.tunnel✕
- Connections
- 1 pair of types, where a type in daemon.routes uses a type in daemon.tunnel.
- The types involved
com.zaneschepke.wireguardautotunnel.daemon.routes.DaemonRoutesKt→com.zaneschepke.wireguardautotunnel.daemon.tunnel.DesktopNetworkMonitor
- Direction
- daemon.routes uses daemon.tunnel, so a change to daemon.tunnel can break daemon.routes, while a change to daemon.routes can't break daemon.tunnel.
- Position
- Below the diagonal: daemon.routes uses a module listed above it, which is the healthy direction.
35→21 daemon.routes uses daemon.data✕
- Connections
- 3 pairs of types, where a type in daemon.routes uses a type in daemon.data.
- The types involved
com.zaneschepke.wireguardautotunnel.daemon.routes.BackendRoutesKt→com.zaneschepke.wireguardautotunnel.daemon.data.DaemonCacheRepositorycom.zaneschepke.wireguardautotunnel.daemon.routes.DaemonRoutesKt→com.zaneschepke.wireguardautotunnel.daemon.data.DaemonCacheRepositorycom.zaneschepke.wireguardautotunnel.daemon.routes.TunnelRoutesKt→com.zaneschepke.wireguardautotunnel.daemon.data.DaemonCacheRepository
- Direction
- daemon.routes uses daemon.data, so a change to daemon.data can break daemon.routes, while a change to daemon.routes can't break daemon.data.
- Position
- Below the diagonal: daemon.routes uses a module listed above it, which is the healthy direction.
35→26 daemon.routes uses daemon.autotunnel✕
- Connections
- 2 pairs of types, where a type in daemon.routes uses a type in daemon.autotunnel.
- The types involved
com.zaneschepke.wireguardautotunnel.daemon.routes.DaemonRoutesKt→com.zaneschepke.wireguardautotunnel.daemon.autotunnel.AutoTunnelSupervisorcom.zaneschepke.wireguardautotunnel.daemon.routes.TunnelRoutesKt→com.zaneschepke.wireguardautotunnel.daemon.autotunnel.AutoTunnelSupervisor
- Direction
- daemon.routes uses daemon.autotunnel, so a change to daemon.autotunnel can break daemon.routes, while a change to daemon.routes can't break daemon.autotunnel.
- Position
- Below the diagonal: daemon.routes uses a module listed above it, which is the healthy direction.
35→28 daemon.routes uses daemon.log✕
- Connections
- 1 pair of types, where a type in daemon.routes uses a type in daemon.log.
- The types involved
com.zaneschepke.wireguardautotunnel.daemon.routes.DaemonRoutesKt→com.zaneschepke.wireguardautotunnel.daemon.log.DaemonLogService
- Direction
- daemon.routes uses daemon.log, so a change to daemon.log can break daemon.routes, while a change to daemon.routes can't break daemon.log.
- Position
- Below the diagonal: daemon.routes uses a module listed above it, which is the healthy direction.
36→11 desktop.ui.screens.tunnels.components uses desktop.ui.screens.tunnels✕
- Connections
- 2 pairs of types, where a type in desktop.ui.screens.tunnels.components uses a type in desktop.ui.screens.tunnels.
- The types involved
com.zaneschepke.wireguardautotunnel.desktop.ui.screens.tunnels.components.TunnelListKt→com.zaneschepke.wireguardautotunnel.desktop.ui.screens.tunnels.DeleteIntentcom.zaneschepke.wireguardautotunnel.desktop.ui.screens.tunnels.components.TunnelListKt→com.zaneschepke.wireguardautotunnel.desktop.ui.screens.tunnels.ExportIntent
- Direction
- desktop.ui.screens.tunnels.components uses desktop.ui.screens.tunnels, so a change to desktop.ui.screens.tunnels can break desktop.ui.screens.tunnels.components, while a change to desktop.ui.screens.tunnels.components can't break desktop.ui.screens.tunnels.
- Position
- Below the diagonal: desktop.ui.screens.tunnels.components uses a module listed above it, which is the healthy direction.
36→15 desktop.ui.screens.tunnels.components uses core.ipc.dto✕
- Connections
- 1 pair of types, where a type in desktop.ui.screens.tunnels.components uses a type in core.ipc.dto.
- The types involved
com.zaneschepke.wireguardautotunnel.desktop.ui.screens.tunnels.components.TunnelStatisticsSectionKt→com.zaneschepke.wireguardautotunnel.core.ipc.dto.TunnelStatus
- Direction
- desktop.ui.screens.tunnels.components uses core.ipc.dto, so a change to core.ipc.dto can break desktop.ui.screens.tunnels.components, while a change to desktop.ui.screens.tunnels.components can't break core.ipc.dto.
- Position
- Below the diagonal: desktop.ui.screens.tunnels.components uses a module listed above it, which is the healthy direction.
36→17 desktop.ui.screens.tunnels.components uses client.domain.model✕
- Connections
- 4 pairs of types, where a type in desktop.ui.screens.tunnels.components uses a type in client.domain.model.
- The types involved
com.zaneschepke.wireguardautotunnel.desktop.ui.screens.tunnels.components.MoveToGroupDialogKt→com.zaneschepke.wireguardautotunnel.client.domain.model.TunnelGroupcom.zaneschepke.wireguardautotunnel.desktop.ui.screens.tunnels.components.TunnelListKt→com.zaneschepke.wireguardautotunnel.client.domain.model.TunnelConfigcom.zaneschepke.wireguardautotunnel.desktop.ui.screens.tunnels.components.TunnelListKt→com.zaneschepke.wireguardautotunnel.client.domain.model.TunnelGroupcom.zaneschepke.wireguardautotunnel.desktop.ui.screens.tunnels.components.TunnelPickerListKt→com.zaneschepke.wireguardautotunnel.client.domain.model.TunnelConfig
- Direction
- desktop.ui.screens.tunnels.components uses client.domain.model, so a change to client.domain.model can break desktop.ui.screens.tunnels.components, while a change to desktop.ui.screens.tunnels.components can't break client.domain.model.
- Position
- Below the diagonal: desktop.ui.screens.tunnels.components uses a module listed above it, which is the healthy direction.
36→29 desktop.ui.screens.tunnels.components uses desktop.ui.state✕
- Connections
- 1 pair of types, where a type in desktop.ui.screens.tunnels.components uses a type in desktop.ui.state.
- The types involved
com.zaneschepke.wireguardautotunnel.desktop.ui.screens.tunnels.components.TunnelListKt→com.zaneschepke.wireguardautotunnel.desktop.ui.state.TunnelsUiState
- Direction
- desktop.ui.screens.tunnels.components uses desktop.ui.state, so a change to desktop.ui.state can break desktop.ui.screens.tunnels.components, while a change to desktop.ui.screens.tunnels.components can't break desktop.ui.state.
- Position
- Below the diagonal: desktop.ui.screens.tunnels.components uses a module listed above it, which is the healthy direction.
37→1 desktop.viewmodel uses client.data.model✕
- Connections
- 3 pairs of types, where a type in desktop.viewmodel uses a type in client.data.model.
- The types involved
com.zaneschepke.wireguardautotunnel.desktop.viewmodel.AppViewModel→com.zaneschepke.wireguardautotunnel.client.data.model.AccentStylecom.zaneschepke.wireguardautotunnel.desktop.viewmodel.AppViewModel→com.zaneschepke.wireguardautotunnel.client.data.model.Themecom.zaneschepke.wireguardautotunnel.desktop.viewmodel.AppViewModel→com.zaneschepke.wireguardautotunnel.client.data.model.TrayIconAppearance
- Direction
- desktop.viewmodel uses client.data.model, so a change to client.data.model can break desktop.viewmodel, while a change to desktop.viewmodel can't break client.data.model.
- Position
- Below the diagonal: desktop.viewmodel uses a module listed above it, which is the healthy direction.
37→2 desktop.viewmodel uses client.domain.enums✕
- Connections
- 7 pairs of types, where a type in desktop.viewmodel uses a type in client.domain.enums.
- The types involved
com.zaneschepke.wireguardautotunnel.desktop.viewmodel.DnsViewModel→com.zaneschepke.wireguardautotunnel.client.domain.enums.BootstrapDnsProtocolcom.zaneschepke.wireguardautotunnel.desktop.viewmodel.DnsViewModel→com.zaneschepke.wireguardautotunnel.client.domain.enums.SplitDnsSuffixTargetcom.zaneschepke.wireguardautotunnel.desktop.viewmodel.DnsViewModel→com.zaneschepke.wireguardautotunnel.client.domain.enums.TransitDnsPolicycom.zaneschepke.wireguardautotunnel.desktop.viewmodel.DnsViewModel→com.zaneschepke.wireguardautotunnel.client.domain.enums.TunnelDnsModecom.zaneschepke.wireguardautotunnel.desktop.viewmodel.DnsViewModel→com.zaneschepke.wireguardautotunnel.client.domain.enums.TunnelDnsProtocolcom.zaneschepke.wireguardautotunnel.desktop.viewmodel.MonitoringViewModel→com.zaneschepke.wireguardautotunnel.client.domain.enums.StatisticRefreshcom.zaneschepke.wireguardautotunnel.desktop.viewmodel.SettingsViewModel→com.zaneschepke.wireguardautotunnel.client.domain.enums.TunnelMode
- Direction
- desktop.viewmodel uses client.domain.enums, so a change to client.domain.enums can break desktop.viewmodel, while a change to desktop.viewmodel can't break client.domain.enums.
- Position
- Below the diagonal: desktop.viewmodel uses a module listed above it, which is the healthy direction.
37→7 desktop.viewmodel uses desktop.update✕
- Connections
- 2 pairs of types, where a type in desktop.viewmodel uses a type in desktop.update.
- The types involved
com.zaneschepke.wireguardautotunnel.desktop.viewmodel.AppViewModel→com.zaneschepke.wireguardautotunnel.desktop.update.AppUpdatercom.zaneschepke.wireguardautotunnel.desktop.viewmodel.SupportViewModel→com.zaneschepke.wireguardautotunnel.desktop.update.AppUpdater
- Direction
- desktop.viewmodel uses desktop.update, so a change to desktop.update can break desktop.viewmodel, while a change to desktop.viewmodel can't break desktop.update.
- Position
- Below the diagonal: desktop.viewmodel uses a module listed above it, which is the healthy direction.
37→11 desktop.viewmodel uses desktop.ui.screens.tunnels✕
- Connections
- 2 pairs of types, where a type in desktop.viewmodel uses a type in desktop.ui.screens.tunnels.
- The types involved
com.zaneschepke.wireguardautotunnel.desktop.viewmodel.TunnelsViewModel→com.zaneschepke.wireguardautotunnel.desktop.ui.screens.tunnels.DeleteIntentcom.zaneschepke.wireguardautotunnel.desktop.viewmodel.TunnelsViewModel→com.zaneschepke.wireguardautotunnel.desktop.ui.screens.tunnels.ExportIntent
- Direction
- desktop.viewmodel uses desktop.ui.screens.tunnels, so a change to desktop.ui.screens.tunnels can break desktop.viewmodel, while a change to desktop.viewmodel can't break desktop.ui.screens.tunnels.
- Position
- Below the diagonal: desktop.viewmodel uses a module listed above it, which is the healthy direction.
37→17 desktop.viewmodel uses client.domain.model✕
- Connections
- 4 pairs of types, where a type in desktop.viewmodel uses a type in client.domain.model.
- The types involved
com.zaneschepke.wireguardautotunnel.desktop.viewmodel.AutoTunnelViewModel→com.zaneschepke.wireguardautotunnel.client.domain.model.TunnelConfigcom.zaneschepke.wireguardautotunnel.desktop.viewmodel.GlobalConfigViewModel→com.zaneschepke.wireguardautotunnel.client.domain.model.TunnelConfigcom.zaneschepke.wireguardautotunnel.desktop.viewmodel.TunnelsViewModel→com.zaneschepke.wireguardautotunnel.client.domain.model.TunnelConfigcom.zaneschepke.wireguardautotunnel.desktop.viewmodel.TunnelsViewModel→com.zaneschepke.wireguardautotunnel.client.domain.model.TunnelGroup
- Direction
- desktop.viewmodel uses client.domain.model, so a change to client.domain.model can break desktop.viewmodel, while a change to desktop.viewmodel can't break client.domain.model.
- Position
- Below the diagonal: desktop.viewmodel uses a module listed above it, which is the healthy direction.
37→18 desktop.viewmodel uses client.service✕
- Connections
- 9 pairs of types, where a type in desktop.viewmodel uses a type in client.service.
- The types involved
com.zaneschepke.wireguardautotunnel.desktop.viewmodel.AppViewModel→com.zaneschepke.wireguardautotunnel.client.service.BackendServicecom.zaneschepke.wireguardautotunnel.desktop.viewmodel.AppViewModel→com.zaneschepke.wireguardautotunnel.client.service.DaemonServicecom.zaneschepke.wireguardautotunnel.desktop.viewmodel.AutoTunnelViewModel→com.zaneschepke.wireguardautotunnel.client.service.DaemonServicecom.zaneschepke.wireguardautotunnel.desktop.viewmodel.DnsViewModel→com.zaneschepke.wireguardautotunnel.client.service.BackendServicecom.zaneschepke.wireguardautotunnel.desktop.viewmodel.ProxyViewModel→com.zaneschepke.wireguardautotunnel.client.service.BackendServicecom.zaneschepke.wireguardautotunnel.desktop.viewmodel.SettingsViewModel→com.zaneschepke.wireguardautotunnel.client.service.DaemonServicecom.zaneschepke.wireguardautotunnel.desktop.viewmodel.TunnelViewModel→com.zaneschepke.wireguardautotunnel.client.service.BackendServicecom.zaneschepke.wireguardautotunnel.desktop.viewmodel.TunnelsViewModel→com.zaneschepke.wireguardautotunnel.client.service.BackendServicecom.zaneschepke.wireguardautotunnel.desktop.viewmodel.TunnelsViewModel→com.zaneschepke.wireguardautotunnel.client.service.TunnelImportService
- Direction
- desktop.viewmodel uses client.service, so a change to client.service can break desktop.viewmodel, while a change to desktop.viewmodel can't break client.service.
- Position
- Below the diagonal: desktop.viewmodel uses a module listed above it, which is the healthy direction.
37→24 desktop.viewmodel uses client.domain.repository✕
- Connections
- 22 pairs of types, where a type in desktop.viewmodel uses a type in client.domain.repository.
- The types involved
com.zaneschepke.wireguardautotunnel.desktop.viewmodel.AppViewModel→com.zaneschepke.wireguardautotunnel.client.domain.repository.AutoTunnelSettingsRepositorycom.zaneschepke.wireguardautotunnel.desktop.viewmodel.AppViewModel→com.zaneschepke.wireguardautotunnel.client.domain.repository.ClientCacheRepositorycom.zaneschepke.wireguardautotunnel.desktop.viewmodel.AppViewModel→com.zaneschepke.wireguardautotunnel.client.domain.repository.GeneralSettingRepositorycom.zaneschepke.wireguardautotunnel.desktop.viewmodel.AppViewModel→com.zaneschepke.wireguardautotunnel.client.domain.repository.TunnelRepositorycom.zaneschepke.wireguardautotunnel.desktop.viewmodel.AutoTunnelViewModel→com.zaneschepke.wireguardautotunnel.client.domain.repository.AutoTunnelSettingsRepositorycom.zaneschepke.wireguardautotunnel.desktop.viewmodel.AutoTunnelViewModel→com.zaneschepke.wireguardautotunnel.client.domain.repository.TunnelRepositorycom.zaneschepke.wireguardautotunnel.desktop.viewmodel.DnsViewModel→com.zaneschepke.wireguardautotunnel.client.domain.repository.DnsSettingsRepositorycom.zaneschepke.wireguardautotunnel.desktop.viewmodel.DnsViewModel→com.zaneschepke.wireguardautotunnel.client.domain.repository.GeneralSettingRepositorycom.zaneschepke.wireguardautotunnel.desktop.viewmodel.GlobalConfigViewModel→com.zaneschepke.wireguardautotunnel.client.domain.repository.DnsSettingsRepositorycom.zaneschepke.wireguardautotunnel.desktop.viewmodel.GlobalConfigViewModel→com.zaneschepke.wireguardautotunnel.client.domain.repository.GeneralSettingRepositorycom.zaneschepke.wireguardautotunnel.desktop.viewmodel.GlobalConfigViewModel→com.zaneschepke.wireguardautotunnel.client.domain.repository.TunnelRepositorycom.zaneschepke.wireguardautotunnel.desktop.viewmodel.MonitoringViewModel→com.zaneschepke.wireguardautotunnel.client.domain.repository.MonitoringSettingsRepositorycom.zaneschepke.wireguardautotunnel.desktop.viewmodel.ProxyViewModel→com.zaneschepke.wireguardautotunnel.client.domain.repository.ProxySettingsRepositorycom.zaneschepke.wireguardautotunnel.desktop.viewmodel.SettingsViewModel→com.zaneschepke.wireguardautotunnel.client.domain.repository.AutoTunnelSettingsRepositorycom.zaneschepke.wireguardautotunnel.desktop.viewmodel.SettingsViewModel→com.zaneschepke.wireguardautotunnel.client.domain.repository.DnsSettingsRepositorycom.zaneschepke.wireguardautotunnel.desktop.viewmodel.SettingsViewModel→com.zaneschepke.wireguardautotunnel.client.domain.repository.GeneralSettingRepositorycom.zaneschepke.wireguardautotunnel.desktop.viewmodel.SettingsViewModel→com.zaneschepke.wireguardautotunnel.client.domain.repository.LockdownSettingsRepositorycom.zaneschepke.wireguardautotunnel.desktop.viewmodel.SettingsViewModel→com.zaneschepke.wireguardautotunnel.client.domain.repository.MonitoringSettingsRepositorycom.zaneschepke.wireguardautotunnel.desktop.viewmodel.SettingsViewModel→com.zaneschepke.wireguardautotunnel.client.domain.repository.TunnelRepositorycom.zaneschepke.wireguardautotunnel.desktop.viewmodel.TunnelViewModel→com.zaneschepke.wireguardautotunnel.client.domain.repository.TunnelRepositorycom.zaneschepke.wireguardautotunnel.desktop.viewmodel.TunnelsViewModel→com.zaneschepke.wireguardautotunnel.client.domain.repository.TunnelGroupRepositorycom.zaneschepke.wireguardautotunnel.desktop.viewmodel.TunnelsViewModel→com.zaneschepke.wireguardautotunnel.client.domain.repository.TunnelRepository
- Direction
- desktop.viewmodel uses client.domain.repository, so a change to client.domain.repository can break desktop.viewmodel, while a change to desktop.viewmodel can't break client.domain.repository.
- Position
- Below the diagonal: desktop.viewmodel uses a module listed above it, which is the healthy direction.
37→30 desktop.viewmodel uses desktop.wifi✕
- Connections
- 1 pair of types, where a type in desktop.viewmodel uses a type in desktop.wifi.
- The types involved
com.zaneschepke.wireguardautotunnel.desktop.viewmodel.AppViewModel→com.zaneschepke.wireguardautotunnel.desktop.wifi.MacWifiNameCoordinator
- Direction
- desktop.viewmodel uses desktop.wifi, so a change to desktop.wifi can break desktop.viewmodel, while a change to desktop.viewmodel can't break desktop.wifi.
- Position
- Below the diagonal: desktop.viewmodel uses a module listed above it, which is the healthy direction.
37→33 desktop.viewmodel uses client.orchestration✕
- Connections
- 9 pairs of types, where a type in desktop.viewmodel uses a type in client.orchestration.
- The types involved
com.zaneschepke.wireguardautotunnel.desktop.viewmodel.AppViewModel→com.zaneschepke.wireguardautotunnel.client.orchestration.AutoTunnelCoordinatorcom.zaneschepke.wireguardautotunnel.desktop.viewmodel.AppViewModel→com.zaneschepke.wireguardautotunnel.client.orchestration.DnsSettingsCoordinatorcom.zaneschepke.wireguardautotunnel.desktop.viewmodel.AppViewModel→com.zaneschepke.wireguardautotunnel.client.orchestration.LogCoordinatorcom.zaneschepke.wireguardautotunnel.desktop.viewmodel.DnsViewModel→com.zaneschepke.wireguardautotunnel.client.orchestration.TunnelCoordinatorcom.zaneschepke.wireguardautotunnel.desktop.viewmodel.LoggerViewModel→com.zaneschepke.wireguardautotunnel.client.orchestration.LogCoordinatorcom.zaneschepke.wireguardautotunnel.desktop.viewmodel.ProxyViewModel→com.zaneschepke.wireguardautotunnel.client.orchestration.TunnelCoordinatorcom.zaneschepke.wireguardautotunnel.desktop.viewmodel.SettingsViewModel→com.zaneschepke.wireguardautotunnel.client.orchestration.TunnelBackendCoordinatorcom.zaneschepke.wireguardautotunnel.desktop.viewmodel.TunnelViewModel→com.zaneschepke.wireguardautotunnel.client.orchestration.TunnelCoordinatorcom.zaneschepke.wireguardautotunnel.desktop.viewmodel.TunnelsViewModel→com.zaneschepke.wireguardautotunnel.client.orchestration.TunnelCoordinator
- Direction
- desktop.viewmodel uses client.orchestration, so a change to client.orchestration can break desktop.viewmodel, while a change to desktop.viewmodel can't break client.orchestration.
- Position
- Below the diagonal: desktop.viewmodel uses a module listed above it, which is the healthy direction.
38→29 desktop uses desktop.ui.state✕
- Connections
- 1 pair of types, where a type in desktop uses a type in desktop.ui.state.
- The types involved
com.zaneschepke.wireguardautotunnel.desktop.AppKt→com.zaneschepke.wireguardautotunnel.desktop.ui.state.AppUiState
- Direction
- desktop uses desktop.ui.state, so a change to desktop.ui.state can break desktop, while a change to desktop can't break desktop.ui.state.
- Position
- Below the diagonal: desktop uses a module listed above it, which is the healthy direction.
38→37 desktop uses desktop.viewmodel✕
- Connections
- 1 pair of types, where a type in desktop uses a type in desktop.viewmodel.
- The types involved
com.zaneschepke.wireguardautotunnel.desktop.AppKt→com.zaneschepke.wireguardautotunnel.desktop.viewmodel.AppViewModel
- Direction
- desktop uses desktop.viewmodel, so a change to desktop.viewmodel can break desktop, while a change to desktop can't break desktop.viewmodel.
- Position
- Below the diagonal: desktop uses a module listed above it, which is the healthy direction.
39→6 desktop.ui.screens.autotunnel.preferred uses desktop.ui.navigation✕
- Connections
- 1 pair of types, where a type in desktop.ui.screens.autotunnel.preferred uses a type in desktop.ui.navigation.
- The types involved
com.zaneschepke.wireguardautotunnel.desktop.ui.screens.autotunnel.preferred.PreferredTunnelScreenKt→com.zaneschepke.wireguardautotunnel.desktop.ui.navigation.TunnelNetwork
- Direction
- desktop.ui.screens.autotunnel.preferred uses desktop.ui.navigation, so a change to desktop.ui.navigation can break desktop.ui.screens.autotunnel.preferred, while a change to desktop.ui.screens.autotunnel.preferred can't break desktop.ui.navigation.
- Position
- Below the diagonal: desktop.ui.screens.autotunnel.preferred uses a module listed above it, which is the healthy direction.
39→37 desktop.ui.screens.autotunnel.preferred uses desktop.viewmodel✕
- Connections
- 1 pair of types, where a type in desktop.ui.screens.autotunnel.preferred uses a type in desktop.viewmodel.
- The types involved
com.zaneschepke.wireguardautotunnel.desktop.ui.screens.autotunnel.preferred.PreferredTunnelScreenKt→com.zaneschepke.wireguardautotunnel.desktop.viewmodel.AutoTunnelViewModel
- Direction
- desktop.ui.screens.autotunnel.preferred uses desktop.viewmodel, so a change to desktop.viewmodel can break desktop.ui.screens.autotunnel.preferred, while a change to desktop.ui.screens.autotunnel.preferred can't break desktop.viewmodel.
- Position
- Below the diagonal: desktop.ui.screens.autotunnel.preferred uses a module listed above it, which is the healthy direction.
40→30 desktop.ui.screens.autotunnel.wifi uses desktop.wifi✕
- Connections
- 1 pair of types, where a type in desktop.ui.screens.autotunnel.wifi uses a type in desktop.wifi.
- The types involved
com.zaneschepke.wireguardautotunnel.desktop.ui.screens.autotunnel.wifi.MacWifiPermissionCardKt→com.zaneschepke.wireguardautotunnel.desktop.wifi.MacWifiNameCoordinator
- Direction
- desktop.ui.screens.autotunnel.wifi uses desktop.wifi, so a change to desktop.wifi can break desktop.ui.screens.autotunnel.wifi, while a change to desktop.ui.screens.autotunnel.wifi can't break desktop.wifi.
- Position
- Below the diagonal: desktop.ui.screens.autotunnel.wifi uses a module listed above it, which is the healthy direction.
40→37 desktop.ui.screens.autotunnel.wifi uses desktop.viewmodel✕
- Connections
- 1 pair of types, where a type in desktop.ui.screens.autotunnel.wifi uses a type in desktop.viewmodel.
- The types involved
com.zaneschepke.wireguardautotunnel.desktop.ui.screens.autotunnel.wifi.WifiSettingsScreenKt→com.zaneschepke.wireguardautotunnel.desktop.viewmodel.AutoTunnelViewModel
- Direction
- desktop.ui.screens.autotunnel.wifi uses desktop.viewmodel, so a change to desktop.viewmodel can break desktop.ui.screens.autotunnel.wifi, while a change to desktop.ui.screens.autotunnel.wifi can't break desktop.viewmodel.
- Position
- Below the diagonal: desktop.ui.screens.autotunnel.wifi uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Domain Modelling
At a glance — Accessibility
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 66 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 12 | Medium |
Roadmap
Top priorities: Adopt SLF4J (with a Logback or Log4j2 JSON encoder) and log at meaningful points in the modules you run; Set connect and read timeouts on every client (`RestTemplateBuilder.connectTimeout/readTimeout`, WebClient `responseTimeout`, `HttpRequest.Builder.timeout`, `HttpURLConnection.setReadTimeout`, Feign `connectTimeout`/`readTimeout` in configuration), and wrap calls to dependencies in resilience4j `@Retry`/`@CircuitBreaker`/`@TimeLimiter` (or Spring Retry); Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Adopt SLF4J (with a Logback or Log4j2 JSON encoder) and log at meaningful points in the modules you run. | +5.0 pts | Medium | Observability |
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.gradle.kts. | +2.2 pts | Low | ADR Quality |
| Set connect and read timeouts on every client (`RestTemplateBuilder.connectTimeout/readTimeout`, WebClient `responseTimeout`, `HttpRequest.Builder.timeout`, `HttpURLConnection.setReadTimeout`, Feign `connectTimeout`/`readTimeout` in configuration), and wrap calls to dependencies in resilience4j `@Retry`/`@CircuitBreaker`/`@TimeLimiter` (or Spring Retry). | +3.1 pts | Medium | Outbound HTTP resilience |
| 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. | +3.1 pts | Medium | Security & performance tooling |
| Resolve the 4 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. | +1.2 pts | Low | Supply-chain Provenance & Signing |
| 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. | +2.3 pts | Medium | Deployment & Rollback |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +2.0 pts | Medium | Architecture documentation |
| Resolve the 7 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (7). | +0.9 pts | Low | Static Analysis (SAST) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 1.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | 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.6 | Mixed | Static Analysis (SAST): High: REDACTED |
| composeApp/src/jvmMain/kotlin/com/zaneschepke/wireguardautotunnel/desktop/App.kt | 5.9 | Mixed | Cyclomatic Complexity: AppKt.App (cyclomatic 16) |
| REDACTED | 6.9 | Mixed | Dependency Vulnerabilities: Medium CVE: REDACTED |
| composeApp/src/jvmMain/kotlin/com/zaneschepke/wireguardautotunnel/desktop/viewmodel/TunnelsViewModel.kt | 7.0 | Mixed | Code Duplication: Edited copy of a member (10 corresponding lines) |
| composeApp/src/jvmMain/kotlin/com/zaneschepke/wireguardautotunnel/desktop/ui/screens/autotunnel/AutoTunnelScreen.kt | 7.1 | Mixed | Cognitive Complexity: AutoTunnelScreenKt.AutoTunnelScreen (cognitive 20) |
| composeApp/src/jvmMain/kotlin/com/zaneschepke/wireguardautotunnel/desktop/Main.kt | 7.2 | Mixed | Cyclomatic Complexity: MainKt.main (cyclomatic 41) |
| composeApp/src/jvmMain/kotlin/com/zaneschepke/wireguardautotunnel/desktop/ui/screens/settings/dns/DnsSettingsScreen.kt | 7.2 | Mixed | God Classes: MethodTooLong: DnsSettingsScreenKt.DnsSettingsScreen |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| composeApp/src/jvmMain/kotlin/com/zaneschepke/wireguardautotunnel/desktop/ui/screens/tunnels/components/TunnelList.kt | 7.4 | Mixed | Cyclomatic Complexity: TunnelListKt.TunnelList (cyclomatic 37) |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 63 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 63 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, 174 of 185 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.kt) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.kt) and this repository declares a JVM test suite (repository root, Gradle), but it was not re-run: no test result was produced. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- 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 (3 contributor(s) across 201 commit(s) sampled, automation and bot accounts excluded). One of them holds 99% of the history; the other 2 hold 0.5% 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 — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is a COLLECTOR gap, not an environment fault: no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `client/src/commonMain/kotlin/com/zaneschepke/wireguardautotunnel/client/data/model/EncryptedField.kt`, `composeApp/src/jvmMain/kotlin/com/zaneschepke/wireguardautotunnel/desktop/Main.kt` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- AX1 Captive dependencies — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository's container is Koin, whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AXB1 Runtime evidence locked — no reproducible boot — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Subject: 1 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates. The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. We then boot it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- DM8 Value-object opportunities — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check finds primitive parameters that travel together through several signatures of the domain (a missing value object). Its deterministic rule has not yet shown 95 % precision on adjudicated rows, so the clumps it finds are counted here and not published as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
- DM9 Scattered domain decisions — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Arm two tells a construction that PRODUCES a measurement from one that merely passes it along, and this repository's frontend does not compute that fact. A measurement built independently in two places would not appear above.
- DM9 Scattered domain decisions — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Some of this repository's production types come from a frontend that does not bind comparison operands to the members they read, which arm one needs, and those types were not walked for this dimension. The counts above speak for the languages that declare it.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Java was found, and this repository's Go, Kotlin is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby, Scala and Rust source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby, Scala or Rust was found, and this repository's Go, Kotlin is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- P1 CI/CD gates — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. A CI pipeline exists and the word "test" appears, but no explicit test-runner invocation (your stack's test command, or a test job) was matched — so either the gate runs tests through a step this pass could not recognise, or "test" is incidental here (a path, "latest", a reporter). Which of the two it is cannot be settled from this dimension's evidence; the coverage dimensions report whether a suite exists at all. You can widen what we reach: name the test runner explicitly in the pipeline step (your stack's test command, or a job named for the suite) so the gate is unambiguous to a reader and to this pass.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- 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 checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- 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 (REDACTED, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
- AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- 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".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
7 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was MainKt.main at 41. 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 26 — 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: composeApp/src/jvmMain/kotlin/com/zaneschepke/wireguardautotunnel/desktop/ui/navigation/Route.kt (Tab.fromRoute at 26). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 7 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with MainKt.main (cyclomatic 41), TunnelListKt.TunnelList (cyclomatic 37), WifiAgentMainKt.main (cyclomatic 24). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 7 together lifts Cyclomatic Complexity from 8.4 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
10 method(s) exceeded the cognitive complexity threshold of 15; the worst was TunnelListKt.TunnelList at 78.
What to do
- Bring the 3 bodies over 30 down to 30 or less in Cognitive Complexity — start with TunnelListKt.TunnelList (cognitive 78), WifiAgentMainKt.main (cognitive 47), MainKt.main (cognitive 43). — 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 Cognitive Complexity from 7.5 to about 8.5/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
D3 · God Classes
10 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 9 MethodTooLong finding(s) in God Classes — start with Main.kt, DnsSettingsScreen.kt, TunnelList.kt. — One of this dimension's main actionable groups (9 warning-level).
- Resolve the 1 FileTooLong finding(s) in God Classes — start with Main.kt. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
13 duplicated block group(s) detected. 2.6 % of the production lines (471 of 18,169) are in a reported copy. A further 10 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
What to do
- Resolve the 2 Edited copy of a member (18 corresponding lines) finding(s) in Code Duplication — start with REDACTED, AutoTunnelCoordinator.kt. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Edited copy of a member (10 corresponding lines) finding(s) in Code Duplication — start with TunnelsViewModel.kt, LinuxAccentColor.kt. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Edited copy of a member (6 corresponding lines) finding(s) in Code Duplication — start with SystemHomeDirectory.kt, SettingsViewModel.kt. — One of this dimension's main actionable groups (2 warning-level).
D5 · Coupling
8 production modules (Gradle+Go), 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 7 of the 8 (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 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
D6 · Cohesion (LCOM4)
1 of 28 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with TunnelsViewModel.kt. — One of this dimension's main actionable groups (1 warning-level).
D12 · Dependency Hygiene
1 outdated, 0 author-deprecated direct Go module(s), 0 pinning or checksum defect(s). Whether any of these modules is UNMAINTAINED is not graded — proxy.golang.org publishes no maintenance status, and release age does not stand in for one. Whether any is UNUSED is not graded either: that is a source question, not a registry one. Known CVEs in this module graph are D30's question, read from REDACTED and go.sum there.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets. 1 detection(s) were excluded as holding no minted credential in material that runs: a name, reference or comparison rather than a value, a readable phrase or pattern, a value that declares itself fake, or development, test, example, mock or demo material.
D14 · License Compliance
0 of 68 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 9 Maven/Gradle manifest(s) declare with a version resolvable from the manifest itself — the same declaration-site closure this analysis reads for dependency currency. The JVM has no lockfile a checkout is guaranteed to carry, so this is deliberately NOT the transitive closure. A further 4 coordinate(s) are not published to Maven Central — another repository (Google's Maven hosts androidx), a SNAPSHOT, or a private artifact — so their licences are not readable from here and they are outside this verdict.
D15 · Churn × Complexity Hotspots
Top hotspots: composeApp/src/jvmMain/kotlin/com/zaneschepke/wireguardautotunnel/desktop/Main.kt (11×41=451); composeApp/src/jvmMain/kotlin/com/zaneschepke/wireguardautotunnel/desktop/ui/screens/tunnels/components/TunnelList.kt (6×37=222); composeApp/src/jvmMain/kotlin/com/zaneschepke/wireguardautotunnel/desktop/App.kt (10×16=160) Repeated repair below the complexity floor: daemon/src/main/kotlin/com/zaneschepke/wireguardautotunnel/daemon/autotunnel/AutoTunnelSupervisor.kt (5 of 9 changes were fixes); composeApp/src/jvmMain/kotlin/com/zaneschepke/wireguardautotunnel/desktop/ui/screens/autotunnel/preferred/PreferredTunnelScreen.kt (4 of 7 changes were fixes); shared/src/main/java/com/zaneschepke/wireguardautotunnel/core/ipc/IpcKeyFileValidator.kt (4 of 5 changes were fixes)
What to do
- Resolve the 8 Repeated repair finding(s) in Churn × Complexity Hotspots — start with AutoTunnelSupervisor.kt, PreferredTunnelScreen.kt, IpcKeyFileValidator.kt. — One of this dimension's main actionable groups (8 warning-level).
- Resolve the 5 Hotspot finding(s) in Churn × Complexity Hotspots — start with Main.kt, TunnelList.kt, App.kt. — One of this dimension's main actionable groups (5 warning-level).
D17 · Explicit Debt
2 deducted task-comment markers across 18169 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 2 TodoComment finding(s) in Explicit Debt — start with PermissionsHelper.kt, DaemonApplicationProvider.kt. — One of this dimension's main actionable groups (2 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 2 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.gradle.kts. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
1 of 9 build units (Go, Gradle) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with build.gradle.kts. — 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)
66 finding(s): 0 critical, 64 high, 1 medium, 1 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 180) — 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 9 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 10 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED, REDACTED. — One of this dimension's main actionable groups (10 issue-level).
- Resolve the 7 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (7). — One of this dimension's main actionable groups (7 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
2 finding(s): 0 critical, 0 high, 2 medium, 0 low.
What to do
- Resolve the 2 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 110 of the 276 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: App.kt↔Main.kt 60%
What to do
- Resolve the 1 Change coupling finding(s) in Change Coupling — start with App.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 4 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (4 warning-level).
- 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).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 3 platform declaration(s) and 74 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AC1 · Text alternatives
AC2 · Forms & labels
AC3 · Page structure
AC5 · ARIA correctness
AC6 · Visual & motion safety
- `.copy-message` moves (`transition: opacity 0.2s ease, transform 0.2s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — packaging/apt/site.css:193
What to do
- Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
- `GeneralSettingsDao` declares 17 abstract methods: `get`, `upsert`, `getFlow`, `updateTheme`, `updateLocale`, `updateRestoreTunnelOnBoot`, `updateLaunchAtLogin`, `updateAlreadyDonated`, `updateSystemColors`, `updateCustomSeedColor`, `updateAccentStyle`, `updateTrayIconAppearance`, `updateTunnelMode`, `updateSeamlessRecovery`, `updateSeamlessRecoveryBounceDelay`, `updateGlobalAmneziaEnabled`, `updateLastNotifiedUpdateVersion`. Counted over its public functions with no body, once per name; default-bodied functions and properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — client/src/commonMain/kotlin/com/zaneschepke/wireguardautotunnel/client/data/dao/GeneralSettingsDao.kt:10
- `TunnelConfigDao` declares 18 abstract methods: `upsert`, `updateAll`, `saveAll`, `getById`, `getByName`, `getAll`, `deleteById`, `deleteByIds`, `clearEntryRefsTo`, `deleteByName`, `count`, `getAllFlow`, `getUserTunnelsFlow`, `getGlobalTunnelFlow`, `setDdnsTunnel`, `resetPrimaryTunnel`, `resetEthernetTunnel`, `findPrimary`. Counted over its public functions with no body, once per name; default-bodied functions and properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — client/src/commonMain/kotlin/com/zaneschepke/wireguardautotunnel/client/data/dao/TunnelConfigDao.kt:13
- `GeneralSettingRepository` declares 16 abstract methods: `upsert`, `get`, `updateTheme`, `updateLocale`, `updateAlreadyDonated`, `updateRestoreTunnelOnBoot`, `updateLaunchAtLogin`, `updateSystemColors`, `updateCustomSeedColor`, `updateAccentStyle`, `updateTrayIconAppearance`, `updateTunnelMode`, `updateSeamlessRecovery`, `updateSeamlessRecoveryBounceDelay`, `updateGlobalAmneziaEnabled`, `updateLastNotifiedUpdateVersion`. Counted over its public functions with no body, once per name; default-bodied functions and properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — client/src/commonMain/kotlin/com/zaneschepke/wireguardautotunnel/client/domain/repository/GeneralSettingRepository.kt:10
What to do
- Split fat interfaces into focused role-interfaces so clients depend only on what they use.
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
- `TunnelsViewModel.onDelete` saves `TunnelRepository`, `TunnelGroupRepository` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event. — composeApp/src/jvmMain/kotlin/com/zaneschepke/wireguardautotunnel/desktop/viewmodel/TunnelsViewModel.kt:262
What to do
- Mutate one aggregate per operation and let the others follow from a domain event — the second aggregate reaching consistency a moment later is the design, not a compromise.
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`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `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. — client/src/commonMain/kotlin/com/zaneschepke/wireguardautotunnel/client/data/entity/DnsSettings.kt:8
- `GeneralSettings`'s public constructor takes `theme`, `locale`, `accentStyle`, `trayIconAppearance`, … as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `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. — client/src/commonMain/kotlin/com/zaneschepke/wireguardautotunnel/client/data/entity/GeneralSettings.kt:8
- `ProxySettings`'s public constructor takes `socks5ProxyBindAddress`, `httpProxyBindAddress` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `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. — client/src/commonMain/kotlin/com/zaneschepke/wireguardautotunnel/client/data/entity/ProxySettings.kt:11
- `TunnelConfig`'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`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `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. — client/src/commonMain/kotlin/com/zaneschepke/wireguardautotunnel/client/data/entity/TunnelConfig.kt:31
- `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`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `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. — client/src/commonMain/kotlin/com/zaneschepke/wireguardautotunnel/client/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
- `TunnelConfig.groupId` is a raw `Long` — give it a strongly-typed id: a dedicated single-field type wrapping the `Long`, in whatever form your language spells that. — client/src/commonMain/kotlin/com/zaneschepke/wireguardautotunnel/client/data/entity/TunnelConfig.kt:52
- `TunnelConfig.entryTunnelId` is a raw `Long` — give it a strongly-typed id: a dedicated single-field type wrapping the `Long`, in whatever form your language spells that. — client/src/commonMain/kotlin/com/zaneschepke/wireguardautotunnel/client/data/entity/TunnelConfig.kt:53
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 9 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — client/src/commonMain/kotlin/com/zaneschepke/wireguardautotunnel/client/data/entity/AutoTunnelSettings.kt:10
- `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. — client/src/commonMain/kotlin/com/zaneschepke/wireguardautotunnel/client/data/entity/DnsSettings.kt:8
- `GeneralSettings` is an aggregate/entity with 15 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — client/src/commonMain/kotlin/com/zaneschepke/wireguardautotunnel/client/data/entity/GeneralSettings.kt:8
- `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. — client/src/commonMain/kotlin/com/zaneschepke/wireguardautotunnel/client/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. — client/src/commonMain/kotlin/com/zaneschepke/wireguardautotunnel/client/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. — client/src/commonMain/kotlin/com/zaneschepke/wireguardautotunnel/client/data/entity/ProxySettings.kt:11
- `TunnelConfig` 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. — client/src/commonMain/kotlin/com/zaneschepke/wireguardautotunnel/client/data/entity/TunnelConfig.kt:31
- `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. — client/src/commonMain/kotlin/com/zaneschepke/wireguardautotunnel/client/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
DM9 · Scattered domain decisions
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- 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.
P2 · Observability
- No logging call was found in the 266 JVM production file(s) this check read across 7 module(s). Each was searched for its ecosystem's logging libraries (JVM: SLF4J, Log4j2, java.util.logging, Logback, kotlin-logging, scala-logging) and for a call on a receiver named `log`/`logger` (or ending in `Logger`/`_logger`) with a level verb. It cannot see logging through a repo-local wrapper named otherwise, or in source it did not read — this is 'no logging found by this walk', not a verdict that nothing here logs. If it is right, production issues will be hard to diagnose.
What to do
- Adopt SLF4J (with a Logback or Log4j2 JSON encoder) and log at meaningful points in the modules you run.
- Add a health-check endpoint (Spring Boot Actuator's /actuator/health, or a /health route) so orchestrators and load balancers can probe liveness/readiness.
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 12 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
- `REDACTED` schedules updates, but no `package-ecosystem` entry covers `gomod`, `gitsubmodule`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entries to the `updates:` list. — REDACTED:2
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 `gomod`, `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
What to do
- Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
P6 · Release Hygiene
P7 · Outbound HTTP resilience
- `HttpClient(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — client/src/commonMain/kotlin/com/zaneschepke/wireguardautotunnel/client/di/serviceModule.kt:51
What to do
- Set connect and read timeouts on every client (`RestTemplateBuilder.connectTimeout/readTimeout`, WebClient `responseTimeout`, `HttpRequest.Builder.timeout`, `HttpURLConnection.setReadTimeout`, Feign `connectTimeout`/`readTimeout` in configuration), and wrap calls to dependencies in resilience4j `@Retry`/`@CircuitBreaker`/`@TimeLimiter` (or Spring Retry).
PF3 · Async & latency hygiene
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
- The JDK pipes both `stdout` and `stderr` of a child started this way — no `redirectErrorStream`, `redirectError`, `redirectOutput` or `inheritIO` is set — and here `process.inputStream` (stdout) is read while the child's end is awaited, but nothing in this scope ever reads `process.errorStream` (stderr). The JDK's own `Process` documentation warns that failing to read a child's output promptly "may cause the process to block, or even deadlock": once the child writes more than the pipe holds to stderr (measured on OpenJDK 25 / Linux: 60,000 bytes finishes, 70,000 hangs forever), it blocks on the write, never exits, and the `waitFor` or end of stream this code waits on never comes. Nothing fails loudly: the thread hangs and the stuck child holds its resources until something kills it. Read both streams (a coroutine or thread per stream), merge them with `redirectErrorStream(true)` before `start()`, or discard the unwanted one with `redirectError(ProcessBuilder.Redirect.DISCARD)` (or `redirectOutput`). (×2) — shared/src/main/java/com/zaneschepke/wireguardautotunnel/core/ipc/IPC.kt:100, shared/src/main/java/com/zaneschepke/wireguardautotunnel/core/helper/PermissionsHelper.kt:375
- The JDK pipes both `stdout` and `stderr` of a child started this way — no `redirectErrorStream`, `redirectError`, `redirectOutput` or `inheritIO` is set — and here `process.errorStream` (stderr) is read while the child's end is awaited, but nothing in this scope ever reads `process.inputStream` (stdout). The JDK's own `Process` documentation warns that failing to read a child's output promptly "may cause the process to block, or even deadlock": once the child writes more than the pipe holds to stdout (measured on OpenJDK 25 / Linux: 60,000 bytes finishes, 70,000 hangs forever), it blocks on the write, never exits, and the `waitFor` or end of stream this code waits on never comes. Nothing fails loudly: the thread hangs and the stuck child holds its resources until something kills it. Read both streams (a coroutine or thread per stream), merge them with `redirectErrorStream(true)` before `start()`, or discard the unwanted one with `redirectError(ProcessBuilder.Redirect.DISCARD)` (or `redirectOutput`). (×3) — shared/src/main/java/com/zaneschepke/wireguardautotunnel/core/helper/PermissionsHelper.kt:101, shared/src/main/java/com/zaneschepke/wireguardautotunnel/core/helper/PermissionsHelper.kt:155, shared/src/main/java/com/zaneschepke/wireguardautotunnel/core/helper/PermissionsHelper.kt:328
What to do
- Each finding names the span that makes the branch dead and the span it is dead because of. Confirm from the two, then delete the dead arm or fix the predicate that was meant to be reachable.
X16 · Unfloored truncation loop
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X2 · Cancellation propagation
X21 · Side-effecting pattern guard
X25 · Inert configuration knob
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
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. — shared/src/main/java/com/zaneschepke/wireguardautotunnel/core/log/LogRecorder.kt:178
What to do
- Swallowed exception (empty catch)
X5 · Nullable reference types
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC1 · Text alternatives | 1.1.1, 1.2.2, 1.2.5 | Partial signal |
| AC2 · Forms & labels | 1.3.1, 3.3.2, 4.1.2 | Partial signal |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC5 · ARIA correctness | 4.1.2 | Partial signal |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 86.4 | Strong | Solid. |
| Architecture | 92.8 | Exemplary | Solid. |
| Maturity | 54.7 | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 39.5 | Weak — gated by P2, P3, P7 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 44.2 | Weak — gated by D29, D36, C1 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 57.1 | Adequate — gated by DM2, DM4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Accessibility | 70.5 | Adequate — gated by AC6 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100.0 | Exemplary | Strongest area. |
Unscored — 2 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 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.
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 59 check(s) not relevant to this codebase
- AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
- 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 Go request handler (a net/http, Gin, Echo, Fiber or fasthttp handler, or a gRPC service method) is declared as a method or function, and no handler function literal writes a value captured from outside it, so no state is shared between request goroutines. 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
- 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
- AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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 — ~68 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 does not read html yet; not measured.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .go, .kt, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — symbol resolution incomplete — navigability not assessed
- 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) — 2 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- 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)
- 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, Scala, Rust and Java, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- M4 Documentation accuracy — Not applicable: the 2 current-state document(s) make no claim of a kind M4 checks. 5 claim(s) of kinds M4 does not check were not checked (path 4, command argument 1); M4 checks only links and versions and artefact counts.
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a pom.xml, Gradle or sbt build, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Kotlin was read, and it logs through none that an assembled message defeats: Android's `Log` and Timber, java.util.logging and log4j-api-kotlin take one finished message (as log4net does in C#), or it makes no call through a named logger at all. Calls made through SLF4J, log4j 2 or kotlin-logging (`LoggerFactory.getLogger`, `KotlinLogging.logger {}`) would be judged.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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 — 64 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
Serious — 102 finding(s)
- MethodTooLong: MainKt.main composeApp/src/jvmMain/kotlin/com/zaneschepke/wireguardautotunnel/desktop/Main.kt:172
- MethodTooLong: DnsSettingsScreenKt.DnsSettingsScreen composeApp/src/jvmMain/kotlin/com/zaneschepke/wireguardautotunnel/desktop/ui/screens/settings/dns/DnsSettingsScreen.kt:79
- MethodTooLong: TunnelListKt.TunnelList composeApp/src/jvmMain/kotlin/com/zaneschepke/wireguardautotunnel/desktop/ui/screens/tunnels/components/TunnelList.kt:87
- MethodTooLong: AppKt.App composeApp/src/jvmMain/kotlin/com/zaneschepke/wireguardautotunnel/desktop/App.kt:103
- MethodTooLong: SupportScreenKt.SupportScreen composeApp/src/jvmMain/kotlin/com/zaneschepke/wireguardautotunnel/desktop/ui/screens/support/SupportScreen.kt:112
- MethodTooLong: TunnelsScreenKt.TunnelsScreen composeApp/src/jvmMain/kotlin/com/zaneschepke/wireguardautotunnel/desktop/ui/screens/tunnels/TunnelsScreen.kt:70
- MethodTooLong: AutoTunnelScreenKt.AutoTunnelScreen composeApp/src/jvmMain/kotlin/com/zaneschepke/wireguardautotunnel/desktop/ui/screens/autotunnel/AutoTunnelScreen.kt:76
- MethodTooLong: SettingsScreenKt.SettingsScreen composeApp/src/jvmMain/kotlin/com/zaneschepke/wireguardautotunnel/desktop/ui/screens/settings/SettingsScreen.kt:79
- MethodTooLong: TunnelSettingsScreenKt.TunnelSettingsScreen composeApp/src/jvmMain/kotlin/com/zaneschepke/wireguardautotunnel/desktop/ui/screens/tunnels/tunnel/TunnelSettingsScreen.kt:62
- Repeated repair: daemon/src/main/kotlin/com/zaneschepke/wireguardautotunnel/daemon/autotunnel/AutoTunnelSupervisor.kt daemon/src/main/kotlin/com/zaneschepke/wireguardautotunnel/daemon/autotunnel/AutoTunnelSupervisor.kt:109
- Repeated repair: composeApp/src/jvmMain/kotlin/com/zaneschepke/wireguardautotunnel/desktop/ui/screens/autotunnel/preferred/PreferredTunnelScreen.kt composeApp/src/jvmMain/kotlin/com/zaneschepke/wireguardautotunnel/desktop/ui/screens/autotunnel/preferred/PreferredTunnelScreen.kt:51
- Repeated repair: shared/src/main/java/com/zaneschepke/wireguardautotunnel/core/ipc/IpcKeyFileValidator.kt shared/src/main/java/com/zaneschepke/wireguardautotunnel/core/ipc/IpcKeyFileValidator.kt:34
- Repeated repair: composeApp/src/jvmMain/kotlin/com/zaneschepke/wireguardautotunnel/desktop/ui/screens/autotunnel/wifi/WifiSettingsScreen.kt composeApp/src/jvmMain/kotlin/com/zaneschepke/wireguardautotunnel/desktop/ui/screens/autotunnel/wifi/WifiSettingsScreen.kt:58
- Repeated repair: composeApp/src/jvmMain/kotlin/com/zaneschepke/wireguardautotunnel/desktop/wifi/MacWifiNameCoordinator.kt composeApp/src/jvmMain/kotlin/com/zaneschepke/wireguardautotunnel/desktop/wifi/MacWifiNameCoordinator.kt:38
- Repeated repair: shared/src/main/java/com/zaneschepke/wireguardautotunnel/core/helper/WindowsSid.kt shared/src/main/java/com/zaneschepke/wireguardautotunnel/core/helper/WindowsSid.kt:24
- Repeated repair: shared/src/main/java/com/zaneschepke/wireguardautotunnel/core/ipc/IPC.kt shared/src/main/java/com/zaneschepke/wireguardautotunnel/core/ipc/IPC.kt:26
- Repeated repair: shared/src/main/java/com/zaneschepke/wireguardautotunnel/core/helper/SystemHomeDirectory.kt shared/src/main/java/com/zaneschepke/wireguardautotunnel/core/helper/SystemHomeDirectory.kt:33
- Anemic entity: AutoTunnelSettings client/src/commonMain/kotlin/com/zaneschepke/wireguardautotunnel/client/data/entity/AutoTunnelSettings.kt:10
- Anemic entity: DnsSettings client/src/commonMain/kotlin/com/zaneschepke/wireguardautotunnel/client/data/entity/DnsSettings.kt:8
- Anemic entity: GeneralSettings client/src/commonMain/kotlin/com/zaneschepke/wireguardautotunnel/client/data/entity/GeneralSettings.kt:8
- Anemic entity: LockdownSettings client/src/commonMain/kotlin/com/zaneschepke/wireguardautotunnel/client/data/entity/LockdownSettings.kt:8
- Anemic entity: MonitoringSettings client/src/commonMain/kotlin/com/zaneschepke/wireguardautotunnel/client/data/entity/MonitoringSettings.kt:8
- Anemic entity: ProxySettings client/src/commonMain/kotlin/com/zaneschepke/wireguardautotunnel/client/data/entity/ProxySettings.kt:11
- Anemic entity: TunnelConfig client/src/commonMain/kotlin/com/zaneschepke/wireguardautotunnel/client/data/entity/TunnelConfig.kt:31
- Anemic entity: TunnelGroup client/src/commonMain/kotlin/com/zaneschepke/wireguardautotunnel/client/data/entity/TunnelGroup.kt:9
- Hotspot: composeApp/src/jvmMain/kotlin/com/zaneschepke/wireguardautotunnel/desktop/Main.kt composeApp/src/jvmMain/kotlin/com/zaneschepke/wireguardautotunnel/desktop/Main.kt:172
- Hotspot: composeApp/src/jvmMain/kotlin/com/zaneschepke/wireguardautotunnel/desktop/ui/screens/tunnels/components/TunnelList.kt composeApp/src/jvmMain/kotlin/com/zaneschepke/wireguardautotunnel/desktop/ui/screens/tunnels/components/TunnelList.kt:87
- Hotspot: composeApp/src/jvmMain/kotlin/com/zaneschepke/wireguardautotunnel/desktop/App.kt composeApp/src/jvmMain/kotlin/com/zaneschepke/wireguardautotunnel/desktop/App.kt:103
- Hotspot: composeApp/src/jvmMain/kotlin/com/zaneschepke/wireguardautotunnel/desktop/ui/screens/tunnels/TunnelsScreen.kt composeApp/src/jvmMain/kotlin/com/zaneschepke/wireguardautotunnel/desktop/ui/screens/tunnels/TunnelsScreen.kt:70
- Hotspot: composeApp/src/jvmMain/kotlin/com/zaneschepke/wireguardautotunnel/desktop/ui/screens/support/SupportScreen.kt composeApp/src/jvmMain/kotlin/com/zaneschepke/wireguardautotunnel/desktop/ui/screens/support/SupportScreen.kt:112
- Constructible in an invalid state: DnsSettings client/src/commonMain/kotlin/com/zaneschepke/wireguardautotunnel/client/data/entity/DnsSettings.kt:8
- Constructible in an invalid state: GeneralSettings client/src/commonMain/kotlin/com/zaneschepke/wireguardautotunnel/client/data/entity/GeneralSettings.kt:8
- Constructible in an invalid state: ProxySettings client/src/commonMain/kotlin/com/zaneschepke/wireguardautotunnel/client/data/entity/ProxySettings.kt:11
- Constructible in an invalid state: TunnelConfig client/src/commonMain/kotlin/com/zaneschepke/wireguardautotunnel/client/data/entity/TunnelConfig.kt:31
- Constructible in an invalid state: TunnelGroup client/src/commonMain/kotlin/com/zaneschepke/wireguardautotunnel/client/data/entity/TunnelGroup.kt:9
- Redirected process stream is never drained (deadlock) shared/src/main/java/com/zaneschepke/wireguardautotunnel/core/ipc/IPC.kt:100
- Redirected process stream is never drained (deadlock) shared/src/main/java/com/zaneschepke/wireguardautotunnel/core/helper/PermissionsHelper.kt:101
- Redirected process stream is never drained (deadlock) shared/src/main/java/com/zaneschepke/wireguardautotunnel/core/helper/PermissionsHelper.kt:155
- Redirected process stream is never drained (deadlock) shared/src/main/java/com/zaneschepke/wireguardautotunnel/core/helper/PermissionsHelper.kt:328
- Redirected process stream is never drained (deadlock) shared/src/main/java/com/zaneschepke/wireguardautotunnel/core/helper/PermissionsHelper.kt:375
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- TodoComment shared/src/main/java/com/zaneschepke/wireguardautotunnel/core/helper/PermissionsHelper.kt:369
- TodoComment daemon/src/main/kotlin/com/zaneschepke/wireguardautotunnel/daemon/tunnel/DaemonApplicationProvider.kt:11
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Edited copy of a member (18 corresponding lines) REDACTED:43
- Edited copy of a member (18 corresponding lines) client/src/commonMain/kotlin/com/zaneschepke/wireguardautotunnel/client/orchestration/AutoTunnelCoordinator.kt:124
- Edited copy of a member (10 corresponding lines) composeApp/src/jvmMain/kotlin/com/zaneschepke/wireguardautotunnel/desktop/viewmodel/TunnelsViewModel.kt:336
- Edited copy of a member (10 corresponding lines) composeApp/src/jvmMain/kotlin/com/zaneschepke/wireguardautotunnel/desktop/util/LinuxAccentColor.kt:20
- Edited copy of a member (6 corresponding lines) shared/src/main/java/com/zaneschepke/wireguardautotunnel/core/helper/SystemHomeDirectory.kt:43
- Edited copy of a member (6 corresponding lines) composeApp/src/jvmMain/kotlin/com/zaneschepke/wireguardautotunnel/desktop/viewmodel/SettingsViewModel.kt:91
- Duplicated block (11 lines × 2) composeApp/src/jvmMain/kotlin/com/zaneschepke/wireguardautotunnel/desktop/ui/screens/autotunnel/AutoTunnelScreen.kt:81
- Duplicated block (11 lines × 2) composeApp/src/jvmMain/kotlin/com/zaneschepke/wireguardautotunnel/desktop/ui/screens/settings/dns/DnsSettingsScreen.kt:123
- Animation without a prefers-reduced-motion guard packaging/apt/site.css:193
- MainKt.main (cyclomatic 41) composeApp/src/jvmMain/kotlin/com/zaneschepke/wireguardautotunnel/desktop/Main.kt:172
- TunnelListKt.TunnelList (cyclomatic 37) composeApp/src/jvmMain/kotlin/com/zaneschepke/wireguardautotunnel/desktop/ui/screens/tunnels/components/TunnelList.kt:87
- WifiAgentMainKt.main (cyclomatic 24) wifi-agent/src/main/kotlin/com/zaneschepke/wireguardautotunnel/wifi/WifiAgentMain.kt:57
- SupportScreenKt.SupportScreen (cyclomatic 19) composeApp/src/jvmMain/kotlin/com/zaneschepke/wireguardautotunnel/desktop/ui/screens/support/SupportScreen.kt:112
- TunnelsScreenKt.TunnelsScreen (cyclomatic 17) composeApp/src/jvmMain/kotlin/com/zaneschepke/wireguardautotunnel/desktop/ui/screens/tunnels/TunnelsScreen.kt:70
- DnsViewModel.save (cyclomatic 17) composeApp/src/jvmMain/kotlin/com/zaneschepke/wireguardautotunnel/desktop/viewmodel/DnsViewModel.kt:123
- AppKt.App (cyclomatic 16) composeApp/src/jvmMain/kotlin/com/zaneschepke/wireguardautotunnel/desktop/App.kt:103
- TunnelListKt.TunnelList (cognitive 78) composeApp/src/jvmMain/kotlin/com/zaneschepke/wireguardautotunnel/desktop/ui/screens/tunnels/components/TunnelList.kt:87
- WifiAgentMainKt.main (cognitive 47) wifi-agent/src/main/kotlin/com/zaneschepke/wireguardautotunnel/wifi/WifiAgentMain.kt:57
- MainKt.main (cognitive 43) composeApp/src/jvmMain/kotlin/com/zaneschepke/wireguardautotunnel/desktop/Main.kt:172
- SupportScreenKt.SupportScreen (cognitive 21) composeApp/src/jvmMain/kotlin/com/zaneschepke/wireguardautotunnel/desktop/ui/screens/support/SupportScreen.kt:112
- AutoTunnelScreenKt.AutoTunnelScreen (cognitive 20) composeApp/src/jvmMain/kotlin/com/zaneschepke/wireguardautotunnel/desktop/ui/screens/autotunnel/AutoTunnelScreen.kt:76
- PreferredTunnelScreenKt.PreferredTunnelScreen (cognitive 20) composeApp/src/jvmMain/kotlin/com/zaneschepke/wireguardautotunnel/desktop/ui/screens/autotunnel/preferred/PreferredTunnelScreen.kt:51
- AppKt.App (cognitive 18) composeApp/src/jvmMain/kotlin/com/zaneschepke/wireguardautotunnel/desktop/App.kt:103
- DnsViewModel.save (cognitive 18) composeApp/src/jvmMain/kotlin/com/zaneschepke/wireguardautotunnel/desktop/viewmodel/DnsViewModel.kt:123
- TunnelsScreenKt.TunnelsScreen (cognitive 17) composeApp/src/jvmMain/kotlin/com/zaneschepke/wireguardautotunnel/desktop/ui/screens/tunnels/TunnelsScreen.kt:70
- WifiAgentMainKt.watchUnderlay (cognitive 17) wifi-agent/src/main/kotlin/com/zaneschepke/wireguardautotunnel/wifi/WifiAgentMain.kt:282
- REDACTED
- FileTooLong: desktop/Main.kt composeApp/src/jvmMain/kotlin/com/zaneschepke/wireguardautotunnel/desktop/Main.kt
- Change coupling: App.kt ↔ Main.kt composeApp/src/jvmMain/kotlin/com/zaneschepke/wireguardautotunnel/desktop/App.kt:1
- REDACTED
- REDACTED
- Members sharing a duplicated core (13 members, 50+ identical tokens) composeApp/src/jvmMain/kotlin/com/zaneschepke/wireguardautotunnel/desktop/ui/screens/autotunnel/AutoTunnelScreen.kt:76
- Edited copy of a member (21 corresponding lines) daemon/src/main/kotlin/com/zaneschepke/wireguardautotunnel/daemon/dto/Extensions.kt:68
- Edited copy of a member (11 corresponding lines) composeApp/src/jvmMain/kotlin/com/zaneschepke/wireguardautotunnel/desktop/viewmodel/AutoTunnelViewModel.kt:122
- Edited copy of a member (14 corresponding lines) composeApp/src/jvmMain/kotlin/com/zaneschepke/wireguardautotunnel/desktop/viewmodel/AutoTunnelViewModel.kt:95
- Duplicated block (15–19 lines × 2) client/src/commonMain/kotlin/com/zaneschepke/wireguardautotunnel/client/di/serviceModule.kt:101
- Duplicated block (16 lines × 2) composeApp/src/jvmMain/kotlin/com/zaneschepke/wireguardautotunnel/desktop/ui/screens/settings/dns/DnsSettingsScreen.kt:89
- Duplicated block (14–16 lines × 2) composeApp/src/jvmMain/kotlin/com/zaneschepke/wireguardautotunnel/desktop/ui/screens/tunnels/tunnel/EntryTunnelScreen.kt:37
- Duplicated block (11–13 lines × 6) composeApp/src/jvmMain/kotlin/com/zaneschepke/wireguardautotunnel/desktop/ui/screens/autotunnel/AutoTunnelScreen.kt:79
- Duplicated block (11–13 lines × 4) composeApp/src/jvmMain/kotlin/com/zaneschepke/wireguardautotunnel/desktop/ui/screens/settings/globals/GlobalConfigScreen.kt:33
- Duplicated block (11–13 lines × 2) composeApp/src/jvmMain/kotlin/com/zaneschepke/wireguardautotunnel/desktop/ui/screens/settings/SettingsScreen.kt:83
- Duplicated block (13 lines × 2) composeApp/src/jvmMain/kotlin/com/zaneschepke/wireguardautotunnel/desktop/ui/screens/settings/appearance/display/DisplayScreen.kt:72
- Duplicated block (12 lines × 3) composeApp/src/jvmMain/kotlin/com/zaneschepke/wireguardautotunnel/desktop/ui/screens/settings/dns/DnsSettingsScreen.kt:88
- Duplicated block (11–12 lines × 2) composeApp/src/jvmMain/kotlin/com/zaneschepke/wireguardautotunnel/desktop/ui/screens/settings/lockdown/LockdownSettingsScreen.kt:55
- Duplicated block (11 lines × 10) composeApp/src/jvmMain/kotlin/com/zaneschepke/wireguardautotunnel/desktop/ui/screens/autotunnel/AutoTunnelScreen.kt:79
- Duplicated block (5 lines × 3) client/src/commonMain/kotlin/com/zaneschepke/wireguardautotunnel/client/data/repository/RoomDnsSettingsRepository.kt:14
- Off the main sequence: :keyring
- Low cohesion: TunnelsViewModel (LCOM4 9) composeApp/src/jvmMain/kotlin/com/zaneschepke/wireguardautotunnel/desktop/viewmodel/TunnelsViewModel.kt:43
- One operation mutates 2 aggregates: TunnelsViewModel.onDelete composeApp/src/jvmMain/kotlin/com/zaneschepke/wireguardautotunnel/desktop/viewmodel/TunnelsViewModel.kt:262
- No structured logging
- Outbound HTTP without resilience client/src/commonMain/kotlin/com/zaneschepke/wireguardautotunnel/client/di/serviceModule.kt:51
- Swallowed exception (empty catch) shared/src/main/java/com/zaneschepke/wireguardautotunnel/core/log/LogRecorder.kt:178
Minor — 17 finding(s)
- Fat interface: GeneralSettingsDao (17 abstract methods) client/src/commonMain/kotlin/com/zaneschepke/wireguardautotunnel/client/data/dao/GeneralSettingsDao.kt:10
- Fat interface: TunnelConfigDao (18 abstract methods) client/src/commonMain/kotlin/com/zaneschepke/wireguardautotunnel/client/data/dao/TunnelConfigDao.kt:13
- Fat interface: GeneralSettingRepository (16 abstract methods) client/src/commonMain/kotlin/com/zaneschepke/wireguardautotunnel/client/domain/repository/GeneralSettingRepository.kt:10
- Primitive id on a domain type: TunnelConfig.groupId client/src/commonMain/kotlin/com/zaneschepke/wireguardautotunnel/client/data/entity/TunnelConfig.kt:52
- Primitive id on a domain type: TunnelConfig.entryTunnelId client/src/commonMain/kotlin/com/zaneschepke/wireguardautotunnel/client/data/entity/TunnelConfig.kt:53
- Silent fallback default in catch shared/src/main/java/com/zaneschepke/wireguardautotunnel/core/helper/PermissionsHelper.kt:443
- Silent fallback default in catch shared/src/main/java/com/zaneschepke/wireguardautotunnel/core/ipc/IPC.kt:104
- No ADRs found wifi-agent/build.gradle.kts:28
- Projects may be oversized for their cohesion composeApp/build.gradle.kts:1
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- No SAST
- Dependabot does not watch gomod/gitsubmodule REDACTED:2
- Duplicated predicate client/src/commonMain/kotlin/com/zaneschepke/wireguardautotunnel/client/data/repository/PropertiesClientCacheRepository.kt:26
Minor — 2 finding(s)
- Outdated: github.com/zalando/go-keyring
- Off the main sequence: :shared
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=0 --max-count=200" --report-format json --report-path /tmp/watchdog-gitleaks-66e28258f6e647a1ab11ce38ba92f27e/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=200 --max-count=1" --report-format json --report-path /tmp/watchdog-gitleaks-66e28258f6e647a1ab11ce38ba92f27e/history-1.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history-1.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-66e28258f6e647a1ab11ce38ba92f27e/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 66 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-d3da17e3102d41c49f9e11cd17f62e48 | 2 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 2 file(s) — `client/src/commonMain/kotlin/com/zaneschepke/wireguardautotunnel/client/data/model/EncryptedField.kt`, `composeApp/src/jvmMain/kotlin/com/zaneschepke/wireguardautotunnel/desktop/Main.kt` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-d3da17e3102d41c49f9e11cd17f62e48 | 0 | artifacts/raw/osv-scanner.json |