Executive summary
OutlineFoundation/outline-apps is rated At risk because critical security findings are open, most of them in the packages it uses. Its score is held back because three passwords or keys sit in the current code and it has uses of packages that aren't listed. It scores 56.4 out of 100, which the At risk rating leaves unchanged.
Production Readiness, at 45.4, is the weakest lens and counts most in the score. The best first step is replacing the three exposed passwords or keys and switching the old ones off, worth about 10.1 points. Tidying the declared packages comes next, worth about 7.3 points. Raising Production Readiness to 70 would lift the score to about 64.8.
105 known security holes in the packages the code depends on can be used by attackers. Five passwords or keys in the code's history and three in the code are open to anyone who can read the repository, and one automatic update takes new releases before a bad one can be spotted. Updating the vulnerable packages, replacing each exposed password or key and setting a waiting period for automatic updates would close these risks. The pipeline step that installs packages without pinning their versions needs the packages it installs pinned to exact versions. The six uses of packages that aren't listed need adding to the project's list of dependencies.
The product code is 41,576 lines, about €59,000 to rebuild.
If Production Readiness rose from 45.4 to 70, the lowest score rated Strong, the score would rise from 56.4 to about 64.8.
Rebuild cost: about €59,000 · Estimate
| Cost to rebuild | €19,000 to €98,000, for 324 to 1,029 hours of work, about 0.4 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 56. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Medium: 41,576 lines of product code |
| Comment lines | The estimate prices 41,300 lines. Comment lines count towards the size of 41,576 lines but aren't priced as work. |
| 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.web.app.clipboard | 2 client.web.app.environment | 3 client.web.app.method_channel | 4 client.web.app.outline_server_repository.vpn | 5 client.web.app.vpn_installer | 6 client.web.model.server | 7 client.web.shared.error_reporter | 8 infrastructure.custom_error | 9 infrastructure.i18n | 10 server_manager.electron.digitalocean_oauth | 11 server_manager.model.location | 12 client.electron.go_vpn_tunnel | 13 client.web.app.main_electron | 14 client.web.app.platform | 15 client.web.model.events | 16 client.web.views.servers_view.server_list_item | 17 infrastructure.path_api | 18 localhost/client/go/outline/tun2socks | 19 server_manager.cloud.digitalocean_api | 20 server_manager.model.server | 21 server_manager.www.ui_components.outline-server-view | 22 client.capacitor.src | 23 client.web.app.app | 24 client.web.app.main_cordova | 25 client.web.app.outline_server_repository | 26 localhost/client/go/outline/vpn | 27 server_manager.model.digitalocean | 28 server_manager.model.gcp | 29 server_manager.www.shadowbox_server | 30 client.web.app | 31 localhost/client/go/outline | 32 server_manager.www.app | 33 server_manager.www.digitalocean_account | 34 server_manager.www.gcp_account | 35 server_manager.www.gcp_server | 36 server_manager.www | 37 server_manager.www.cloud_accounts | 38 server_manager.www.digitalocean_server | 39 server_manager.www.outline-gcp-create-server-app | 40 server_manager.www.ui_components.app-root |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 client.web.app.clipboard | ||||||||||||||||||||||||||||||||||||||||
| 2 client.web.app.environment | ||||||||||||||||||||||||||||||||||||||||
| 3 client.web.app.method_channel | ||||||||||||||||||||||||||||||||||||||||
| 4 client.web.app.outline_server_repository.vpn | ||||||||||||||||||||||||||||||||||||||||
| 5 client.web.app.vpn_installer | ||||||||||||||||||||||||||||||||||||||||
| 6 client.web.model.server | ||||||||||||||||||||||||||||||||||||||||
| 7 client.web.shared.error_reporter | ||||||||||||||||||||||||||||||||||||||||
| 8 infrastructure.custom_error | ||||||||||||||||||||||||||||||||||||||||
| 9 infrastructure.i18n | ||||||||||||||||||||||||||||||||||||||||
| 10 server_manager.electron.digitalocean_oauth | ||||||||||||||||||||||||||||||||||||||||
| 11 server_manager.model.location | ||||||||||||||||||||||||||||||||||||||||
| 12 client.electron.go_vpn_tunnel | 1 | |||||||||||||||||||||||||||||||||||||||
| 13 client.web.app.main_electron | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 14 client.web.app.platform | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 15 client.web.model.events | 4 | |||||||||||||||||||||||||||||||||||||||
| 16 client.web.views.servers_view.server_list_item | 1 | |||||||||||||||||||||||||||||||||||||||
| 17 infrastructure.path_api | 1 | |||||||||||||||||||||||||||||||||||||||
| 18 localhost/client/go/outline/tun2socks | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 19 server_manager.cloud.digitalocean_api | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 20 server_manager.model.server | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 21 server_manager.www.ui_components.outline-server-view | 1 | |||||||||||||||||||||||||||||||||||||||
| 22 client.capacitor.src | 1 | 1 | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 23 client.web.app.app | 1 | 1 | 1 | 2 | 1 | 1 | 8 | 1 | ||||||||||||||||||||||||||||||||
| 24 client.web.app.main_cordova | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 25 client.web.app.outline_server_repository | 2 | 3 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 26 localhost/client/go/outline/vpn | 1 | |||||||||||||||||||||||||||||||||||||||
| 27 server_manager.model.digitalocean | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 28 server_manager.model.gcp | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 29 server_manager.www.shadowbox_server | 1 | 3 | ||||||||||||||||||||||||||||||||||||||
| 30 client.web.app | 1 | 1 | 2 | 2 | 1 | 2 | 2 | |||||||||||||||||||||||||||||||||
| 31 localhost/client/go/outline | 1 | |||||||||||||||||||||||||||||||||||||||
| 32 server_manager.www.app | 1 | 1 | 1 | 4 | 1 | 2 | ||||||||||||||||||||||||||||||||||
| 33 server_manager.www.digitalocean_account | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 34 server_manager.www.gcp_account | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 35 server_manager.www.gcp_server | 3 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 36 server_manager.www | 1 | 1 | 2 | 4 | 3 | 1 | 1 | 1 | 2 | |||||||||||||||||||||||||||||||
| 37 server_manager.www.cloud_accounts | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 38 server_manager.www.digitalocean_server | 2 | 2 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 39 server_manager.www.outline-gcp-create-server-app | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 40 server_manager.www.ui_components.app-root | 1 | 1 |
12→4 client.electron.go_vpn_tunnel uses client.web.app.outline_server_repository.vpn✕
- Connections
- 1 pair of types, where a type in client.electron.go_vpn_tunnel uses a type in client.web.app.outline_server_repository.vpn.
- The types involved
client.electron.go_vpn_tunnel.GoVpnTunnel→client.web.app.outline_server_repository.vpn.TunnelStatus
- Direction
- client.electron.go_vpn_tunnel uses client.web.app.outline_server_repository.vpn, so a change to client.web.app.outline_server_repository.vpn can break client.electron.go_vpn_tunnel, while a change to client.electron.go_vpn_tunnel can't break client.web.app.outline_server_repository.vpn.
- Position
- Below the diagonal: client.electron.go_vpn_tunnel uses a module listed above it, which is the healthy direction.
13→1 client.web.app.main_electron uses client.web.app.clipboard✕
- Connections
- 1 pair of types, where a type in client.web.app.main_electron uses a type in client.web.app.clipboard.
- The types involved
client.web.app.main_electron.ElectronClipboard→client.web.app.clipboard.AbstractClipboard
- Direction
- client.web.app.main_electron uses client.web.app.clipboard, so a change to client.web.app.clipboard can break client.web.app.main_electron, while a change to client.web.app.main_electron can't break client.web.app.clipboard.
- Position
- Below the diagonal: client.web.app.main_electron uses a module listed above it, which is the healthy direction.
13→3 client.web.app.main_electron uses client.web.app.method_channel✕
- Connections
- 1 pair of types, where a type in client.web.app.main_electron uses a type in client.web.app.method_channel.
- The types involved
client.web.app.main_electron.ElectronMethodChannel→client.web.app.method_channel.MethodChannel
- Direction
- client.web.app.main_electron uses client.web.app.method_channel, so a change to client.web.app.method_channel can break client.web.app.main_electron, while a change to client.web.app.main_electron can't break client.web.app.method_channel.
- Position
- Below the diagonal: client.web.app.main_electron uses a module listed above it, which is the healthy direction.
13→5 client.web.app.main_electron uses client.web.app.vpn_installer✕
- Connections
- 1 pair of types, where a type in client.web.app.main_electron uses a type in client.web.app.vpn_installer.
- The types involved
client.web.app.main_electron.ElectronVpnInstaller→client.web.app.vpn_installer.VpnInstaller
- Direction
- client.web.app.main_electron uses client.web.app.vpn_installer, so a change to client.web.app.vpn_installer can break client.web.app.main_electron, while a change to client.web.app.main_electron can't break client.web.app.vpn_installer.
- Position
- Below the diagonal: client.web.app.main_electron uses a module listed above it, which is the healthy direction.
13→7 client.web.app.main_electron uses client.web.shared.error_reporter✕
- Connections
- 1 pair of types, where a type in client.web.app.main_electron uses a type in client.web.shared.error_reporter.
- The types involved
client.web.app.main_electron.ElectronErrorReporter→client.web.shared.error_reporter.OutlineErrorReporter
- Direction
- client.web.app.main_electron uses client.web.shared.error_reporter, so a change to client.web.shared.error_reporter can break client.web.app.main_electron, while a change to client.web.app.main_electron can't break client.web.shared.error_reporter.
- Position
- Below the diagonal: client.web.app.main_electron uses a module listed above it, which is the healthy direction.
14→1 client.web.app.platform uses client.web.app.clipboard✕
- Connections
- 1 pair of types, where a type in client.web.app.platform uses a type in client.web.app.clipboard.
- The types involved
client.web.app.platform.OutlinePlatform→client.web.app.clipboard.Clipboard
- Direction
- client.web.app.platform uses client.web.app.clipboard, so a change to client.web.app.clipboard can break client.web.app.platform, while a change to client.web.app.platform can't break client.web.app.clipboard.
- Position
- Below the diagonal: client.web.app.platform uses a module listed above it, which is the healthy direction.
14→2 client.web.app.platform uses client.web.app.environment✕
- Connections
- 1 pair of types, where a type in client.web.app.platform uses a type in client.web.app.environment.
- The types involved
client.web.app.platform.OutlinePlatform→client.web.app.environment.EnvironmentVariables
- Direction
- client.web.app.platform uses client.web.app.environment, so a change to client.web.app.environment can break client.web.app.platform, while a change to client.web.app.platform can't break client.web.app.environment.
- Position
- Below the diagonal: client.web.app.platform uses a module listed above it, which is the healthy direction.
14→5 client.web.app.platform uses client.web.app.vpn_installer✕
- Connections
- 1 pair of types, where a type in client.web.app.platform uses a type in client.web.app.vpn_installer.
- The types involved
client.web.app.platform.OutlinePlatform→client.web.app.vpn_installer.VpnInstaller
- Direction
- client.web.app.platform uses client.web.app.vpn_installer, so a change to client.web.app.vpn_installer can break client.web.app.platform, while a change to client.web.app.platform can't break client.web.app.vpn_installer.
- Position
- Below the diagonal: client.web.app.platform uses a module listed above it, which is the healthy direction.
14→7 client.web.app.platform uses client.web.shared.error_reporter✕
- Connections
- 1 pair of types, where a type in client.web.app.platform uses a type in client.web.shared.error_reporter.
- The types involved
client.web.app.platform.OutlinePlatform→client.web.shared.error_reporter.OutlineErrorReporter
- Direction
- client.web.app.platform uses client.web.shared.error_reporter, so a change to client.web.shared.error_reporter can break client.web.app.platform, while a change to client.web.app.platform can't break client.web.shared.error_reporter.
- Position
- Below the diagonal: client.web.app.platform uses a module listed above it, which is the healthy direction.
15→6 client.web.model.events uses client.web.model.server✕
- Connections
- 4 pairs of types, where a type in client.web.model.events uses a type in client.web.model.server.
- The types involved
client.web.model.events.ServerAdded→client.web.model.server.Serverclient.web.model.events.ServerForgetUndone→client.web.model.server.Serverclient.web.model.events.ServerForgotten→client.web.model.server.Serverclient.web.model.events.ServerRenamed→client.web.model.server.Server
- Direction
- client.web.model.events uses client.web.model.server, so a change to client.web.model.server can break client.web.model.events, while a change to client.web.model.events can't break client.web.model.server.
- Position
- Below the diagonal: client.web.model.events uses a module listed above it, which is the healthy direction.
16→9 client.web.views.servers_view.server_list_item uses infrastructure.i18n✕
- Connections
- 1 pair of types, where a type in client.web.views.servers_view.server_list_item uses a type in infrastructure.i18n.
- The types involved
client.web.views.servers_view.server_list_item.ServerListItemElement→infrastructure.i18n.Localizer
- Direction
- client.web.views.servers_view.server_list_item uses infrastructure.i18n, so a change to infrastructure.i18n can break client.web.views.servers_view.server_list_item, while a change to client.web.views.servers_view.server_list_item can't break infrastructure.i18n.
- Position
- Below the diagonal: client.web.views.servers_view.server_list_item uses a module listed above it, which is the healthy direction.
17→8 infrastructure.path_api uses infrastructure.custom_error✕
- Connections
- 1 pair of types, where a type in infrastructure.path_api uses a type in infrastructure.custom_error.
- The types involved
infrastructure.path_api.ServerApiError→infrastructure.custom_error.CustomError
- Direction
- infrastructure.path_api uses infrastructure.custom_error, so a change to infrastructure.custom_error can break infrastructure.path_api, while a change to infrastructure.path_api can't break infrastructure.custom_error.
- Position
- Below the diagonal: infrastructure.path_api uses a module listed above it, which is the healthy direction.
18→26 localhost/client/go/outline/tun2socks uses localhost/client/go/outline/vpn part of a loop✕
- Connections
- 1 pair of types, where a type in localhost/client/go/outline/tun2socks uses a type in localhost/client/go/outline/vpn.
- The types involved
localhost/client/go/outline/tun2socks.RemoteDevice→localhost/client/go/outline/vpn.RemoteDevice
- Direction
- localhost/client/go/outline/tun2socks uses localhost/client/go/outline/vpn, so a change to localhost/client/go/outline/vpn can break localhost/client/go/outline/tun2socks, while a change to localhost/client/go/outline/tun2socks can't break localhost/client/go/outline/vpn.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→31 localhost/client/go/outline/tun2socks uses localhost/client/go/outline part of a loop✕
- Connections
- 2 pairs of types, where a type in localhost/client/go/outline/tun2socks uses a type in localhost/client/go/outline.
- The types involved
localhost/client/go/outline/tun2socks.RemoteDevice→localhost/client/go/outline.Clientlocalhost/client/go/outline/tun2socks.tun2socks→localhost/client/go/outline.Client
- Direction
- localhost/client/go/outline/tun2socks uses localhost/client/go/outline, so a change to localhost/client/go/outline can break localhost/client/go/outline/tun2socks, while a change to localhost/client/go/outline/tun2socks can't break localhost/client/go/outline.
- 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.
19→8 server_manager.cloud.digitalocean_api uses infrastructure.custom_error✕
- Connections
- 1 pair of types, where a type in server_manager.cloud.digitalocean_api uses a type in infrastructure.custom_error.
- The types involved
server_manager.cloud.digitalocean_api.XhrError→infrastructure.custom_error.CustomError
- Direction
- server_manager.cloud.digitalocean_api uses infrastructure.custom_error, so a change to infrastructure.custom_error can break server_manager.cloud.digitalocean_api, while a change to server_manager.cloud.digitalocean_api can't break infrastructure.custom_error.
- Position
- Below the diagonal: server_manager.cloud.digitalocean_api uses a module listed above it, which is the healthy direction.
19→10 server_manager.cloud.digitalocean_api uses server_manager.electron.digitalocean_oauth✕
- Connections
- 2 pairs of types, where a type in server_manager.cloud.digitalocean_api uses a type in server_manager.electron.digitalocean_oauth.
- The types involved
server_manager.cloud.digitalocean_api.DigitalOceanSession→server_manager.electron.digitalocean_oauth.Accountserver_manager.cloud.digitalocean_api.RestApiSession→server_manager.electron.digitalocean_oauth.Account
- Direction
- server_manager.cloud.digitalocean_api uses server_manager.electron.digitalocean_oauth, so a change to server_manager.electron.digitalocean_oauth can break server_manager.cloud.digitalocean_api, while a change to server_manager.cloud.digitalocean_api can't break server_manager.electron.digitalocean_oauth.
- Position
- Below the diagonal: server_manager.cloud.digitalocean_api uses a module listed above it, which is the healthy direction.
20→8 server_manager.model.server uses infrastructure.custom_error✕
- Connections
- 2 pairs of types, where a type in server_manager.model.server uses a type in infrastructure.custom_error.
- The types involved
server_manager.model.server.ServerInstallCanceledError→infrastructure.custom_error.CustomErrorserver_manager.model.server.ServerInstallFailedError→infrastructure.custom_error.CustomError
- Direction
- server_manager.model.server uses infrastructure.custom_error, so a change to infrastructure.custom_error can break server_manager.model.server, while a change to server_manager.model.server can't break infrastructure.custom_error.
- Position
- Below the diagonal: server_manager.model.server uses a module listed above it, which is the healthy direction.
20→11 server_manager.model.server uses server_manager.model.location✕
- Connections
- 1 pair of types, where a type in server_manager.model.server uses a type in server_manager.model.location.
- The types involved
server_manager.model.server.ManagedServerHost→server_manager.model.location.CloudLocation
- Direction
- server_manager.model.server uses server_manager.model.location, so a change to server_manager.model.location can break server_manager.model.server, while a change to server_manager.model.server can't break server_manager.model.location.
- Position
- Below the diagonal: server_manager.model.server uses a module listed above it, which is the healthy direction.
21→11 server_manager.www.ui_components.outline-server-view uses server_manager.model.location✕
- Connections
- 1 pair of types, where a type in server_manager.www.ui_components.outline-server-view uses a type in server_manager.model.location.
- The types involved
server_manager.www.ui_components.outline-server-view.ServerView→server_manager.model.location.CloudLocation
- Direction
- server_manager.www.ui_components.outline-server-view uses server_manager.model.location, so a change to server_manager.model.location can break server_manager.www.ui_components.outline-server-view, while a change to server_manager.www.ui_components.outline-server-view can't break server_manager.model.location.
- Position
- Below the diagonal: server_manager.www.ui_components.outline-server-view uses a module listed above it, which is the healthy direction.
22→1 client.capacitor.src uses client.web.app.clipboard✕
- Connections
- 1 pair of types, where a type in client.capacitor.src uses a type in client.web.app.clipboard.
- The types involved
client.capacitor.src.CapacitorClipboard→client.web.app.clipboard.AbstractClipboard
- Direction
- client.capacitor.src uses client.web.app.clipboard, so a change to client.web.app.clipboard can break client.capacitor.src, while a change to client.capacitor.src can't break client.web.app.clipboard.
- Position
- Below the diagonal: client.capacitor.src uses a module listed above it, which is the healthy direction.
22→2 client.capacitor.src uses client.web.app.environment✕
- Connections
- 1 pair of types, where a type in client.capacitor.src uses a type in client.web.app.environment.
- The types involved
client.capacitor.src.CapacitorPlatform→client.web.app.environment.EnvironmentVariables
- Direction
- client.capacitor.src uses client.web.app.environment, so a change to client.web.app.environment can break client.capacitor.src, while a change to client.capacitor.src can't break client.web.app.environment.
- Position
- Below the diagonal: client.capacitor.src uses a module listed above it, which is the healthy direction.
22→3 client.capacitor.src uses client.web.app.method_channel✕
- Connections
- 1 pair of types, where a type in client.capacitor.src uses a type in client.web.app.method_channel.
- The types involved
client.capacitor.src.CapacitorMethodChannel→client.web.app.method_channel.MethodChannel
- Direction
- client.capacitor.src uses client.web.app.method_channel, so a change to client.web.app.method_channel can break client.capacitor.src, while a change to client.capacitor.src can't break client.web.app.method_channel.
- Position
- Below the diagonal: client.capacitor.src uses a module listed above it, which is the healthy direction.
22→4 client.capacitor.src uses client.web.app.outline_server_repository.vpn✕
- Connections
- 1 pair of types, where a type in client.capacitor.src uses a type in client.web.app.outline_server_repository.vpn.
- The types involved
client.capacitor.src.CapacitorVpnApi→client.web.app.outline_server_repository.vpn.StartRequestJson
- Direction
- client.capacitor.src uses client.web.app.outline_server_repository.vpn, so a change to client.web.app.outline_server_repository.vpn can break client.capacitor.src, while a change to client.capacitor.src can't break client.web.app.outline_server_repository.vpn.
- Position
- Below the diagonal: client.capacitor.src uses a module listed above it, which is the healthy direction.
22→5 client.capacitor.src uses client.web.app.vpn_installer✕
- Connections
- 1 pair of types, where a type in client.capacitor.src uses a type in client.web.app.vpn_installer.
- The types involved
client.capacitor.src.CapacitorPlatform→client.web.app.vpn_installer.VpnInstaller
- Direction
- client.capacitor.src uses client.web.app.vpn_installer, so a change to client.web.app.vpn_installer can break client.capacitor.src, while a change to client.capacitor.src can't break client.web.app.vpn_installer.
- Position
- Below the diagonal: client.capacitor.src uses a module listed above it, which is the healthy direction.
22→7 client.capacitor.src uses client.web.shared.error_reporter✕
- Connections
- 1 pair of types, where a type in client.capacitor.src uses a type in client.web.shared.error_reporter.
- The types involved
client.capacitor.src.CapacitorErrorReporter→client.web.shared.error_reporter.SentryErrorReporter
- Direction
- client.capacitor.src uses client.web.shared.error_reporter, so a change to client.web.shared.error_reporter can break client.capacitor.src, while a change to client.capacitor.src can't break client.web.shared.error_reporter.
- Position
- Below the diagonal: client.capacitor.src uses a module listed above it, which is the healthy direction.
22→14 client.capacitor.src uses client.web.app.platform✕
- Connections
- 1 pair of types, where a type in client.capacitor.src uses a type in client.web.app.platform.
- The types involved
client.capacitor.src.CapacitorPlatform→client.web.app.platform.OutlinePlatform
- Direction
- client.capacitor.src uses client.web.app.platform, so a change to client.web.app.platform can break client.capacitor.src, while a change to client.capacitor.src can't break client.web.app.platform.
- Position
- Below the diagonal: client.capacitor.src uses a module listed above it, which is the healthy direction.
23→1 client.web.app.app uses client.web.app.clipboard✕
- Connections
- 1 pair of types, where a type in client.web.app.app uses a type in client.web.app.clipboard.
- The types involved
client.web.app.app.App→client.web.app.clipboard.Clipboard
- Direction
- client.web.app.app uses client.web.app.clipboard, so a change to client.web.app.clipboard can break client.web.app.app, while a change to client.web.app.app can't break client.web.app.clipboard.
- Position
- Below the diagonal: client.web.app.app uses a module listed above it, which is the healthy direction.
23→2 client.web.app.app uses client.web.app.environment✕
- Connections
- 1 pair of types, where a type in client.web.app.app uses a type in client.web.app.environment.
- The types involved
client.web.app.app.App→client.web.app.environment.EnvironmentVariables
- Direction
- client.web.app.app uses client.web.app.environment, so a change to client.web.app.environment can break client.web.app.app, while a change to client.web.app.app can't break client.web.app.environment.
- Position
- Below the diagonal: client.web.app.app uses a module listed above it, which is the healthy direction.
23→5 client.web.app.app uses client.web.app.vpn_installer✕
- Connections
- 1 pair of types, where a type in client.web.app.app uses a type in client.web.app.vpn_installer.
- The types involved
client.web.app.app.App→client.web.app.vpn_installer.VpnInstaller
- Direction
- client.web.app.app uses client.web.app.vpn_installer, so a change to client.web.app.vpn_installer can break client.web.app.app, while a change to client.web.app.app can't break client.web.app.vpn_installer.
- Position
- Below the diagonal: client.web.app.app uses a module listed above it, which is the healthy direction.
23→6 client.web.app.app uses client.web.model.server✕
- Connections
- 2 pairs of types, where a type in client.web.app.app uses a type in client.web.model.server.
- The types involved
client.web.app.app.App→client.web.model.server.Serverclient.web.app.app.App→client.web.model.server.ServerRepository
- Direction
- client.web.app.app uses client.web.model.server, so a change to client.web.model.server can break client.web.app.app, while a change to client.web.app.app can't break client.web.model.server.
- Position
- Below the diagonal: client.web.app.app uses a module listed above it, which is the healthy direction.
23→7 client.web.app.app uses client.web.shared.error_reporter✕
- Connections
- 1 pair of types, where a type in client.web.app.app uses a type in client.web.shared.error_reporter.
- The types involved
client.web.app.app.App→client.web.shared.error_reporter.OutlineErrorReporter
- Direction
- client.web.app.app uses client.web.shared.error_reporter, so a change to client.web.shared.error_reporter can break client.web.app.app, while a change to client.web.app.app can't break client.web.shared.error_reporter.
- Position
- Below the diagonal: client.web.app.app uses a module listed above it, which is the healthy direction.
23→9 client.web.app.app uses infrastructure.i18n✕
- Connections
- 1 pair of types, where a type in client.web.app.app uses a type in infrastructure.i18n.
- The types involved
client.web.app.app.App→infrastructure.i18n.Localizer
- Direction
- client.web.app.app uses infrastructure.i18n, so a change to infrastructure.i18n can break client.web.app.app, while a change to client.web.app.app can't break infrastructure.i18n.
- Position
- Below the diagonal: client.web.app.app uses a module listed above it, which is the healthy direction.
23→15 client.web.app.app uses client.web.model.events✕
- Connections
- 8 pairs of types, where a type in client.web.app.app uses a type in client.web.model.events.
- The types involved
client.web.app.app.App→client.web.model.events.EventQueueclient.web.app.app.App→client.web.model.events.ServerAddedclient.web.app.app.App→client.web.model.events.ServerConnectedclient.web.app.app.App→client.web.model.events.ServerDisconnectedclient.web.app.app.App→client.web.model.events.ServerForgetUndoneclient.web.app.app.App→client.web.model.events.ServerForgottenclient.web.app.app.App→client.web.model.events.ServerReconnectingclient.web.app.app.App→client.web.model.events.ServerRenamed
- Direction
- client.web.app.app uses client.web.model.events, so a change to client.web.model.events can break client.web.app.app, while a change to client.web.app.app can't break client.web.model.events.
- Position
- Below the diagonal: client.web.app.app uses a module listed above it, which is the healthy direction.
23→16 client.web.app.app uses client.web.views.servers_view.server_list_item✕
- Connections
- 1 pair of types, where a type in client.web.app.app uses a type in client.web.views.servers_view.server_list_item.
- The types involved
client.web.app.app.App→client.web.views.servers_view.server_list_item.ServerListItem
- Direction
- client.web.app.app uses client.web.views.servers_view.server_list_item, so a change to client.web.views.servers_view.server_list_item can break client.web.app.app, while a change to client.web.app.app can't break client.web.views.servers_view.server_list_item.
- Position
- Below the diagonal: client.web.app.app uses a module listed above it, which is the healthy direction.
24→1 client.web.app.main_cordova uses client.web.app.clipboard✕
- Connections
- 1 pair of types, where a type in client.web.app.main_cordova uses a type in client.web.app.clipboard.
- The types involved
client.web.app.main_cordova.CordovaClipboard→client.web.app.clipboard.AbstractClipboard
- Direction
- client.web.app.main_cordova uses client.web.app.clipboard, so a change to client.web.app.clipboard can break client.web.app.main_cordova, while a change to client.web.app.main_cordova can't break client.web.app.clipboard.
- Position
- Below the diagonal: client.web.app.main_cordova uses a module listed above it, which is the healthy direction.
24→2 client.web.app.main_cordova uses client.web.app.environment✕
- Connections
- 1 pair of types, where a type in client.web.app.main_cordova uses a type in client.web.app.environment.
- The types involved
client.web.app.main_cordova.CordovaPlatform→client.web.app.environment.EnvironmentVariables
- Direction
- client.web.app.main_cordova uses client.web.app.environment, so a change to client.web.app.environment can break client.web.app.main_cordova, while a change to client.web.app.main_cordova can't break client.web.app.environment.
- Position
- Below the diagonal: client.web.app.main_cordova uses a module listed above it, which is the healthy direction.
24→3 client.web.app.main_cordova uses client.web.app.method_channel✕
- Connections
- 1 pair of types, where a type in client.web.app.main_cordova uses a type in client.web.app.method_channel.
- The types involved
client.web.app.main_cordova.CordovaMethodChannel→client.web.app.method_channel.MethodChannel
- Direction
- client.web.app.main_cordova uses client.web.app.method_channel, so a change to client.web.app.method_channel can break client.web.app.main_cordova, while a change to client.web.app.main_cordova can't break client.web.app.method_channel.
- Position
- Below the diagonal: client.web.app.main_cordova uses a module listed above it, which is the healthy direction.
24→5 client.web.app.main_cordova uses client.web.app.vpn_installer✕
- Connections
- 1 pair of types, where a type in client.web.app.main_cordova uses a type in client.web.app.vpn_installer.
- The types involved
client.web.app.main_cordova.CordovaPlatform→client.web.app.vpn_installer.VpnInstaller
- Direction
- client.web.app.main_cordova uses client.web.app.vpn_installer, so a change to client.web.app.vpn_installer can break client.web.app.main_cordova, while a change to client.web.app.main_cordova can't break client.web.app.vpn_installer.
- Position
- Below the diagonal: client.web.app.main_cordova uses a module listed above it, which is the healthy direction.
24→7 client.web.app.main_cordova uses client.web.shared.error_reporter✕
- Connections
- 1 pair of types, where a type in client.web.app.main_cordova uses a type in client.web.shared.error_reporter.
- The types involved
client.web.app.main_cordova.CordovaErrorReporter→client.web.shared.error_reporter.SentryErrorReporter
- Direction
- client.web.app.main_cordova uses client.web.shared.error_reporter, so a change to client.web.shared.error_reporter can break client.web.app.main_cordova, while a change to client.web.app.main_cordova can't break client.web.shared.error_reporter.
- Position
- Below the diagonal: client.web.app.main_cordova uses a module listed above it, which is the healthy direction.
24→14 client.web.app.main_cordova uses client.web.app.platform✕
- Connections
- 1 pair of types, where a type in client.web.app.main_cordova uses a type in client.web.app.platform.
- The types involved
client.web.app.main_cordova.CordovaPlatform→client.web.app.platform.OutlinePlatform
- Direction
- client.web.app.main_cordova uses client.web.app.platform, so a change to client.web.app.platform can break client.web.app.main_cordova, while a change to client.web.app.main_cordova can't break client.web.app.platform.
- Position
- Below the diagonal: client.web.app.main_cordova uses a module listed above it, which is the healthy direction.
25→4 client.web.app.outline_server_repository uses client.web.app.outline_server_repository.vpn✕
- Connections
- 2 pairs of types, where a type in client.web.app.outline_server_repository uses a type in client.web.app.outline_server_repository.vpn.
- The types involved
client.web.app.outline_server_repository.OutlineServerRepository→client.web.app.outline_server_repository.vpn.VpnApiclient.web.app.outline_server_repository.server→client.web.app.outline_server_repository.vpn.VpnApi
- Direction
- client.web.app.outline_server_repository uses client.web.app.outline_server_repository.vpn, so a change to client.web.app.outline_server_repository.vpn can break client.web.app.outline_server_repository, while a change to client.web.app.outline_server_repository can't break client.web.app.outline_server_repository.vpn.
- Position
- Below the diagonal: client.web.app.outline_server_repository uses a module listed above it, which is the healthy direction.
25→6 client.web.app.outline_server_repository uses client.web.model.server✕
- Connections
- 3 pairs of types, where a type in client.web.app.outline_server_repository uses a type in client.web.model.server.
- The types involved
client.web.app.outline_server_repository.OutlineServerRepository→client.web.model.server.Serverclient.web.app.outline_server_repository.OutlineServerRepository→client.web.model.server.ServerRepositoryclient.web.app.outline_server_repository.server→client.web.model.server.Server
- Direction
- client.web.app.outline_server_repository uses client.web.model.server, so a change to client.web.model.server can break client.web.app.outline_server_repository, while a change to client.web.app.outline_server_repository can't break client.web.model.server.
- Position
- Below the diagonal: client.web.app.outline_server_repository uses a module listed above it, which is the healthy direction.
25→9 client.web.app.outline_server_repository uses infrastructure.i18n✕
- Connections
- 2 pairs of types, where a type in client.web.app.outline_server_repository uses a type in infrastructure.i18n.
- The types involved
client.web.app.outline_server_repository.OutlineServerRepository→infrastructure.i18n.Localizerclient.web.app.outline_server_repository.server→infrastructure.i18n.Localizer
- Direction
- client.web.app.outline_server_repository uses infrastructure.i18n, so a change to infrastructure.i18n can break client.web.app.outline_server_repository, while a change to client.web.app.outline_server_repository can't break infrastructure.i18n.
- Position
- Below the diagonal: client.web.app.outline_server_repository uses a module listed above it, which is the healthy direction.
25→15 client.web.app.outline_server_repository uses client.web.model.events✕
- Connections
- 1 pair of types, where a type in client.web.app.outline_server_repository uses a type in client.web.model.events.
- The types involved
client.web.app.outline_server_repository.OutlineServerRepository→client.web.model.events.EventQueue
- Direction
- client.web.app.outline_server_repository uses client.web.model.events, so a change to client.web.model.events can break client.web.app.outline_server_repository, while a change to client.web.app.outline_server_repository can't break client.web.model.events.
- Position
- Below the diagonal: client.web.app.outline_server_repository uses a module listed above it, which is the healthy direction.
26→18 localhost/client/go/outline/vpn uses localhost/client/go/outline/tun2socks✕
- Connections
- 1 pair of types, where a type in localhost/client/go/outline/vpn uses a type in localhost/client/go/outline/tun2socks.
- The types involved
localhost/client/go/outline/vpn.RemoteDevice→localhost/client/go/outline/tun2socks.TunWriter
- Direction
- localhost/client/go/outline/vpn uses localhost/client/go/outline/tun2socks, so a change to localhost/client/go/outline/tun2socks can break localhost/client/go/outline/vpn, while a change to localhost/client/go/outline/vpn can't break localhost/client/go/outline/tun2socks.
- Position
- Below the diagonal: localhost/client/go/outline/vpn uses a module listed above it, which is the healthy direction.
27→11 server_manager.model.digitalocean uses server_manager.model.location✕
- Connections
- 1 pair of types, where a type in server_manager.model.digitalocean uses a type in server_manager.model.location.
- The types involved
server_manager.model.digitalocean.Region→server_manager.model.location.GeoLocation
- Direction
- server_manager.model.digitalocean uses server_manager.model.location, so a change to server_manager.model.location can break server_manager.model.digitalocean, while a change to server_manager.model.digitalocean can't break server_manager.model.location.
- Position
- Below the diagonal: server_manager.model.digitalocean uses a module listed above it, which is the healthy direction.
27→20 server_manager.model.digitalocean uses server_manager.model.server✕
- Connections
- 1 pair of types, where a type in server_manager.model.digitalocean uses a type in server_manager.model.server.
- The types involved
server_manager.model.digitalocean.Account→server_manager.model.server.ManagedServer
- Direction
- server_manager.model.digitalocean uses server_manager.model.server, so a change to server_manager.model.server can break server_manager.model.digitalocean, while a change to server_manager.model.digitalocean can't break server_manager.model.server.
- Position
- Below the diagonal: server_manager.model.digitalocean uses a module listed above it, which is the healthy direction.
28→11 server_manager.model.gcp uses server_manager.model.location✕
- Connections
- 1 pair of types, where a type in server_manager.model.gcp uses a type in server_manager.model.location.
- The types involved
server_manager.model.gcp.Zone→server_manager.model.location.GeoLocation
- Direction
- server_manager.model.gcp uses server_manager.model.location, so a change to server_manager.model.location can break server_manager.model.gcp, while a change to server_manager.model.gcp can't break server_manager.model.location.
- Position
- Below the diagonal: server_manager.model.gcp uses a module listed above it, which is the healthy direction.
28→20 server_manager.model.gcp uses server_manager.model.server✕
- Connections
- 1 pair of types, where a type in server_manager.model.gcp uses a type in server_manager.model.server.
- The types involved
server_manager.model.gcp.Account→server_manager.model.server.ManagedServer
- Direction
- server_manager.model.gcp uses server_manager.model.server, so a change to server_manager.model.server can break server_manager.model.gcp, while a change to server_manager.model.gcp can't break server_manager.model.server.
- Position
- Below the diagonal: server_manager.model.gcp uses a module listed above it, which is the healthy direction.
29→17 server_manager.www.shadowbox_server uses infrastructure.path_api✕
- Connections
- 1 pair of types, where a type in server_manager.www.shadowbox_server uses a type in infrastructure.path_api.
- The types involved
server_manager.www.shadowbox_server.ShadowboxServer→infrastructure.path_api.PathApiClient
- Direction
- server_manager.www.shadowbox_server uses infrastructure.path_api, so a change to infrastructure.path_api can break server_manager.www.shadowbox_server, while a change to server_manager.www.shadowbox_server can't break infrastructure.path_api.
- Position
- Below the diagonal: server_manager.www.shadowbox_server uses a module listed above it, which is the healthy direction.
29→20 server_manager.www.shadowbox_server uses server_manager.model.server✕
- Connections
- 3 pairs of types, where a type in server_manager.www.shadowbox_server uses a type in server_manager.model.server.
- The types involved
server_manager.www.shadowbox_server.ServerConfigJson→server_manager.model.server.Dataserver_manager.www.shadowbox_server.ShadowboxServer→server_manager.model.server.AccessKeyserver_manager.www.shadowbox_server.ShadowboxServer→server_manager.model.server.Data
- Direction
- server_manager.www.shadowbox_server uses server_manager.model.server, so a change to server_manager.model.server can break server_manager.www.shadowbox_server, while a change to server_manager.www.shadowbox_server can't break server_manager.model.server.
- Position
- Below the diagonal: server_manager.www.shadowbox_server uses a module listed above it, which is the healthy direction.
30→3 client.web.app uses client.web.app.method_channel✕
- Connections
- 1 pair of types, where a type in client.web.app uses a type in client.web.app.method_channel.
- The types involved
client.web.app.method_channel→client.web.app.method_channel.MethodChannel
- Direction
- client.web.app uses client.web.app.method_channel, so a change to client.web.app.method_channel can break client.web.app, while a change to client.web.app can't break client.web.app.method_channel.
- Position
- Below the diagonal: client.web.app uses a module listed above it, which is the healthy direction.
30→4 client.web.app uses client.web.app.outline_server_repository.vpn✕
- Connections
- 1 pair of types, where a type in client.web.app uses a type in client.web.app.outline_server_repository.vpn.
- The types involved
client.web.app.index→client.web.app.outline_server_repository.vpn.VpnApi
- Direction
- client.web.app uses client.web.app.outline_server_repository.vpn, so a change to client.web.app.outline_server_repository.vpn can break client.web.app, while a change to client.web.app can't break client.web.app.outline_server_repository.vpn.
- Position
- Below the diagonal: client.web.app uses a module listed above it, which is the healthy direction.
30→6 client.web.app uses client.web.model.server✕
- Connections
- 2 pairs of types, where a type in client.web.app uses a type in client.web.model.server.
- The types involved
client.web.app.index→client.web.model.server.ServerRepositoryclient.web.app.main→client.web.model.server.ServerRepository
- Direction
- client.web.app uses client.web.model.server, so a change to client.web.model.server can break client.web.app, while a change to client.web.app can't break client.web.model.server.
- Position
- Below the diagonal: client.web.app uses a module listed above it, which is the healthy direction.
30→9 client.web.app uses infrastructure.i18n✕
- Connections
- 2 pairs of types, where a type in client.web.app uses a type in infrastructure.i18n.
- The types involved
client.web.app.index→infrastructure.i18n.Localizerclient.web.app.main→infrastructure.i18n.Localizer
- Direction
- client.web.app uses infrastructure.i18n, so a change to infrastructure.i18n can break client.web.app, while a change to client.web.app can't break infrastructure.i18n.
- Position
- Below the diagonal: client.web.app uses a module listed above it, which is the healthy direction.
30→14 client.web.app uses client.web.app.platform✕
- Connections
- 1 pair of types, where a type in client.web.app uses a type in client.web.app.platform.
- The types involved
client.web.app.main→client.web.app.platform.OutlinePlatform
- Direction
- client.web.app uses client.web.app.platform, so a change to client.web.app.platform can break client.web.app, while a change to client.web.app can't break client.web.app.platform.
- Position
- Below the diagonal: client.web.app uses a module listed above it, which is the healthy direction.
30→15 client.web.app uses client.web.model.events✕
- Connections
- 2 pairs of types, where a type in client.web.app uses a type in client.web.model.events.
- The types involved
client.web.app.index→client.web.model.events.EventQueueclient.web.app.main→client.web.model.events.EventQueue
- Direction
- client.web.app uses client.web.model.events, so a change to client.web.model.events can break client.web.app, while a change to client.web.app can't break client.web.model.events.
- Position
- Below the diagonal: client.web.app uses a module listed above it, which is the healthy direction.
30→25 client.web.app uses client.web.app.outline_server_repository✕
- Connections
- 2 pairs of types, where a type in client.web.app uses a type in client.web.app.outline_server_repository.
- The types involved
client.web.app.index→client.web.app.outline_server_repository.OutlineServerRepositoryclient.web.app.index→client.web.app.outline_server_repository.ServersStorageV0Config
- Direction
- client.web.app uses client.web.app.outline_server_repository, so a change to client.web.app.outline_server_repository can break client.web.app, while a change to client.web.app can't break client.web.app.outline_server_repository.
- Position
- Below the diagonal: client.web.app uses a module listed above it, which is the healthy direction.
31→26 localhost/client/go/outline uses localhost/client/go/outline/vpn✕
- Connections
- 1 pair of types, where a type in localhost/client/go/outline uses a type in localhost/client/go/outline/vpn.
- The types involved
localhost/client/go/outline.establishVpnRequestJSON→localhost/client/go/outline/vpn.Config
- Direction
- localhost/client/go/outline uses localhost/client/go/outline/vpn, so a change to localhost/client/go/outline/vpn can break localhost/client/go/outline, while a change to localhost/client/go/outline can't break localhost/client/go/outline/vpn.
- Position
- Below the diagonal: localhost/client/go/outline uses a module listed above it, which is the healthy direction.
32→6 server_manager.www.app uses client.web.model.server✕
- Connections
- 1 pair of types, where a type in server_manager.www.app uses a type in client.web.model.server.
- The types involved
server_manager.www.app.App→client.web.model.server.Server
- Direction
- server_manager.www.app uses client.web.model.server, so a change to client.web.model.server can break server_manager.www.app, while a change to server_manager.www.app can't break client.web.model.server.
- Position
- Below the diagonal: server_manager.www.app uses a module listed above it, which is the healthy direction.
32→10 server_manager.www.app uses server_manager.electron.digitalocean_oauth✕
- Connections
- 1 pair of types, where a type in server_manager.www.app uses a type in server_manager.electron.digitalocean_oauth.
- The types involved
server_manager.www.app.App→server_manager.electron.digitalocean_oauth.Account
- Direction
- server_manager.www.app uses server_manager.electron.digitalocean_oauth, so a change to server_manager.electron.digitalocean_oauth can break server_manager.www.app, while a change to server_manager.www.app can't break server_manager.electron.digitalocean_oauth.
- Position
- Below the diagonal: server_manager.www.app uses a module listed above it, which is the healthy direction.
32→11 server_manager.www.app uses server_manager.model.location✕
- Connections
- 1 pair of types, where a type in server_manager.www.app uses a type in server_manager.model.location.
- The types involved
server_manager.www.app.App→server_manager.model.location.CloudLocation
- Direction
- server_manager.www.app uses server_manager.model.location, so a change to server_manager.model.location can break server_manager.www.app, while a change to server_manager.www.app can't break server_manager.model.location.
- Position
- Below the diagonal: server_manager.www.app uses a module listed above it, which is the healthy direction.
32→20 server_manager.www.app uses server_manager.model.server✕
- Connections
- 4 pairs of types, where a type in server_manager.www.app uses a type in server_manager.model.server.
- The types involved
server_manager.www.app.App→server_manager.model.server.AccessKeyMetricsserver_manager.www.app.App→server_manager.model.server.Dataserver_manager.www.app.App→server_manager.model.server.ManagedServerserver_manager.www.app.App→server_manager.model.server.ManualServerRepository
- Direction
- server_manager.www.app uses server_manager.model.server, so a change to server_manager.model.server can break server_manager.www.app, while a change to server_manager.www.app can't break server_manager.model.server.
- Position
- Below the diagonal: server_manager.www.app uses a module listed above it, which is the healthy direction.
32→21 server_manager.www.app uses server_manager.www.ui_components.outline-server-view✕
- Connections
- 1 pair of types, where a type in server_manager.www.app uses a type in server_manager.www.ui_components.outline-server-view.
- The types involved
server_manager.www.app.App→server_manager.www.ui_components.outline-server-view.ServerView
- Direction
- server_manager.www.app uses server_manager.www.ui_components.outline-server-view, so a change to server_manager.www.ui_components.outline-server-view can break server_manager.www.app, while a change to server_manager.www.app can't break server_manager.www.ui_components.outline-server-view.
- Position
- Below the diagonal: server_manager.www.app uses a module listed above it, which is the healthy direction.
32→27 server_manager.www.app uses server_manager.model.digitalocean✕
- Connections
- 2 pairs of types, where a type in server_manager.www.app uses a type in server_manager.model.digitalocean.
- The types involved
server_manager.www.app.App→server_manager.model.digitalocean.Regionserver_manager.www.app.App→server_manager.model.digitalocean.Status
- Direction
- server_manager.www.app uses server_manager.model.digitalocean, so a change to server_manager.model.digitalocean can break server_manager.www.app, while a change to server_manager.www.app can't break server_manager.model.digitalocean.
- Position
- Below the diagonal: server_manager.www.app uses a module listed above it, which is the healthy direction.
33→19 server_manager.www.digitalocean_account uses server_manager.cloud.digitalocean_api✕
- Connections
- 1 pair of types, where a type in server_manager.www.digitalocean_account uses a type in server_manager.cloud.digitalocean_api.
- The types involved
server_manager.www.digitalocean_account.DigitalOceanAccount→server_manager.cloud.digitalocean_api.DigitalOceanSession
- Direction
- server_manager.www.digitalocean_account uses server_manager.cloud.digitalocean_api, so a change to server_manager.cloud.digitalocean_api can break server_manager.www.digitalocean_account, while a change to server_manager.www.digitalocean_account can't break server_manager.cloud.digitalocean_api.
- Position
- Below the diagonal: server_manager.www.digitalocean_account uses a module listed above it, which is the healthy direction.
33→20 server_manager.www.digitalocean_account uses server_manager.model.server✕
- Connections
- 1 pair of types, where a type in server_manager.www.digitalocean_account uses a type in server_manager.model.server.
- The types involved
server_manager.www.digitalocean_account.DigitalOceanAccount→server_manager.model.server.ManagedServer
- Direction
- server_manager.www.digitalocean_account uses server_manager.model.server, so a change to server_manager.model.server can break server_manager.www.digitalocean_account, while a change to server_manager.www.digitalocean_account can't break server_manager.model.server.
- Position
- Below the diagonal: server_manager.www.digitalocean_account uses a module listed above it, which is the healthy direction.
33→27 server_manager.www.digitalocean_account uses server_manager.model.digitalocean✕
- Connections
- 2 pairs of types, where a type in server_manager.www.digitalocean_account uses a type in server_manager.model.digitalocean.
- The types involved
server_manager.www.digitalocean_account.DigitalOceanAccount→server_manager.model.digitalocean.Regionserver_manager.www.digitalocean_account.DigitalOceanAccount→server_manager.model.digitalocean.Status
- Direction
- server_manager.www.digitalocean_account uses server_manager.model.digitalocean, so a change to server_manager.model.digitalocean can break server_manager.www.digitalocean_account, while a change to server_manager.www.digitalocean_account can't break server_manager.model.digitalocean.
- Position
- Below the diagonal: server_manager.www.digitalocean_account uses a module listed above it, which is the healthy direction.
34→20 server_manager.www.gcp_account uses server_manager.model.server✕
- Connections
- 1 pair of types, where a type in server_manager.www.gcp_account uses a type in server_manager.model.server.
- The types involved
server_manager.www.gcp_account.GcpAccount→server_manager.model.server.ManagedServer
- Direction
- server_manager.www.gcp_account uses server_manager.model.server, so a change to server_manager.model.server can break server_manager.www.gcp_account, while a change to server_manager.www.gcp_account can't break server_manager.model.server.
- Position
- Below the diagonal: server_manager.www.gcp_account uses a module listed above it, which is the healthy direction.
34→28 server_manager.www.gcp_account uses server_manager.model.gcp✕
- Connections
- 1 pair of types, where a type in server_manager.www.gcp_account uses a type in server_manager.model.gcp.
- The types involved
server_manager.www.gcp_account.GcpAccount→server_manager.model.gcp.Zone
- Direction
- server_manager.www.gcp_account uses server_manager.model.gcp, so a change to server_manager.model.gcp can break server_manager.www.gcp_account, while a change to server_manager.www.gcp_account can't break server_manager.model.gcp.
- Position
- Below the diagonal: server_manager.www.gcp_account uses a module listed above it, which is the healthy direction.
35→20 server_manager.www.gcp_server uses server_manager.model.server✕
- Connections
- 3 pairs of types, where a type in server_manager.www.gcp_server uses a type in server_manager.model.server.
- The types involved
server_manager.www.gcp_server.GcpHost→server_manager.model.server.DataAmountserver_manager.www.gcp_server.GcpHost→server_manager.model.server.MonetaryCostserver_manager.www.gcp_server.GcpServer→server_manager.model.server.ManagedServerHost
- Direction
- server_manager.www.gcp_server uses server_manager.model.server, so a change to server_manager.model.server can break server_manager.www.gcp_server, while a change to server_manager.www.gcp_server can't break server_manager.model.server.
- Position
- Below the diagonal: server_manager.www.gcp_server uses a module listed above it, which is the healthy direction.
35→28 server_manager.www.gcp_server uses server_manager.model.gcp✕
- Connections
- 1 pair of types, where a type in server_manager.www.gcp_server uses a type in server_manager.model.gcp.
- The types involved
server_manager.www.gcp_server.GcpHost→server_manager.model.gcp.Zone
- Direction
- server_manager.www.gcp_server uses server_manager.model.gcp, so a change to server_manager.model.gcp can break server_manager.www.gcp_server, while a change to server_manager.www.gcp_server can't break server_manager.model.gcp.
- Position
- Below the diagonal: server_manager.www.gcp_server uses a module listed above it, which is the healthy direction.
35→29 server_manager.www.gcp_server uses server_manager.www.shadowbox_server✕
- Connections
- 1 pair of types, where a type in server_manager.www.gcp_server uses a type in server_manager.www.shadowbox_server.
- The types involved
server_manager.www.gcp_server.GcpServer→server_manager.www.shadowbox_server.ShadowboxServer
- Direction
- server_manager.www.gcp_server uses server_manager.www.shadowbox_server, so a change to server_manager.www.shadowbox_server can break server_manager.www.gcp_server, while a change to server_manager.www.gcp_server can't break server_manager.www.shadowbox_server.
- Position
- Below the diagonal: server_manager.www.gcp_server uses a module listed above it, which is the healthy direction.
36→6 server_manager.www uses client.web.model.server✕
- Connections
- 1 pair of types, where a type in server_manager.www uses a type in client.web.model.server.
- The types involved
server_manager.www.app→client.web.model.server.Server
- Direction
- server_manager.www uses client.web.model.server, so a change to client.web.model.server can break server_manager.www, while a change to server_manager.www can't break client.web.model.server.
- Position
- Below the diagonal: server_manager.www uses a module listed above it, which is the healthy direction.
36→9 server_manager.www uses infrastructure.i18n✕
- Connections
- 1 pair of types, where a type in server_manager.www uses a type in infrastructure.i18n.
- The types involved
server_manager.www.main→infrastructure.i18n.LanguageCode
- Direction
- server_manager.www uses infrastructure.i18n, so a change to infrastructure.i18n can break server_manager.www, while a change to server_manager.www can't break infrastructure.i18n.
- Position
- Below the diagonal: server_manager.www uses a module listed above it, which is the healthy direction.
36→11 server_manager.www uses server_manager.model.location✕
- Connections
- 2 pairs of types, where a type in server_manager.www uses a type in server_manager.model.location.
- The types involved
server_manager.www.location_formatting→server_manager.model.location.CloudLocationserver_manager.www.location_formatting→server_manager.model.location.GeoLocation
- Direction
- server_manager.www uses server_manager.model.location, so a change to server_manager.model.location can break server_manager.www, while a change to server_manager.www can't break server_manager.model.location.
- Position
- Below the diagonal: server_manager.www uses a module listed above it, which is the healthy direction.
36→17 server_manager.www uses infrastructure.path_api✕
- Connections
- 4 pairs of types, where a type in server_manager.www uses a type in infrastructure.path_api.
- The types involved
server_manager.www.browser_main→infrastructure.path_api.HttpRequestserver_manager.www.fetcher→infrastructure.path_api.HttpRequestserver_manager.www.fetcher→infrastructure.path_api.HttpResponseserver_manager.www.fetcher→infrastructure.path_api.PathApiClient
- Direction
- server_manager.www uses infrastructure.path_api, so a change to infrastructure.path_api can break server_manager.www, while a change to server_manager.www can't break infrastructure.path_api.
- Position
- Below the diagonal: server_manager.www uses a module listed above it, which is the healthy direction.
36→20 server_manager.www uses server_manager.model.server✕
- Connections
- 3 pairs of types, where a type in server_manager.www uses a type in server_manager.model.server.
- The types involved
server_manager.www.app→server_manager.model.server.Dataserver_manager.www.management_urls→server_manager.model.server.ManualServerConfigserver_manager.www.shadowbox_server→server_manager.model.server.AccessKey
- Direction
- server_manager.www uses server_manager.model.server, so a change to server_manager.model.server can break server_manager.www, while a change to server_manager.www can't break server_manager.model.server.
- Position
- Below the diagonal: server_manager.www uses a module listed above it, which is the healthy direction.
36→21 server_manager.www uses server_manager.www.ui_components.outline-server-view✕
- Connections
- 1 pair of types, where a type in server_manager.www uses a type in server_manager.www.ui_components.outline-server-view.
- The types involved
server_manager.www.app→server_manager.www.ui_components.outline-server-view.ServerView
- Direction
- server_manager.www uses server_manager.www.ui_components.outline-server-view, so a change to server_manager.www.ui_components.outline-server-view can break server_manager.www, while a change to server_manager.www can't break server_manager.www.ui_components.outline-server-view.
- Position
- Below the diagonal: server_manager.www uses a module listed above it, which is the healthy direction.
36→28 server_manager.www uses server_manager.model.gcp✕
- Connections
- 1 pair of types, where a type in server_manager.www uses a type in server_manager.model.gcp.
- The types involved
server_manager.www.gcp_account→server_manager.model.gcp.Zone
- Direction
- server_manager.www uses server_manager.model.gcp, so a change to server_manager.model.gcp can break server_manager.www, while a change to server_manager.www can't break server_manager.model.gcp.
- Position
- Below the diagonal: server_manager.www uses a module listed above it, which is the healthy direction.
36→29 server_manager.www uses server_manager.www.shadowbox_server✕
- Connections
- 1 pair of types, where a type in server_manager.www uses a type in server_manager.www.shadowbox_server.
- The types involved
server_manager.www.shadowbox_server→server_manager.www.shadowbox_server.AccessKeyJson
- Direction
- server_manager.www uses server_manager.www.shadowbox_server, so a change to server_manager.www.shadowbox_server can break server_manager.www, while a change to server_manager.www can't break server_manager.www.shadowbox_server.
- Position
- Below the diagonal: server_manager.www uses a module listed above it, which is the healthy direction.
36→35 server_manager.www uses server_manager.www.gcp_server✕
- Connections
- 2 pairs of types, where a type in server_manager.www uses a type in server_manager.www.gcp_server.
- The types involved
server_manager.www.digitalocean_server→server_manager.www.gcp_server.InstallStateserver_manager.www.gcp_server→server_manager.www.gcp_server.InstallState
- Direction
- server_manager.www uses server_manager.www.gcp_server, so a change to server_manager.www.gcp_server can break server_manager.www, while a change to server_manager.www can't break server_manager.www.gcp_server.
- Position
- Below the diagonal: server_manager.www uses a module listed above it, which is the healthy direction.
37→10 server_manager.www.cloud_accounts uses server_manager.electron.digitalocean_oauth✕
- Connections
- 1 pair of types, where a type in server_manager.www.cloud_accounts uses a type in server_manager.electron.digitalocean_oauth.
- The types involved
server_manager.www.cloud_accounts.CloudAccounts→server_manager.electron.digitalocean_oauth.Account
- Direction
- server_manager.www.cloud_accounts uses server_manager.electron.digitalocean_oauth, so a change to server_manager.electron.digitalocean_oauth can break server_manager.www.cloud_accounts, while a change to server_manager.www.cloud_accounts can't break server_manager.electron.digitalocean_oauth.
- Position
- Below the diagonal: server_manager.www.cloud_accounts uses a module listed above it, which is the healthy direction.
37→33 server_manager.www.cloud_accounts uses server_manager.www.digitalocean_account✕
- Connections
- 1 pair of types, where a type in server_manager.www.cloud_accounts uses a type in server_manager.www.digitalocean_account.
- The types involved
server_manager.www.cloud_accounts.CloudAccounts→server_manager.www.digitalocean_account.DigitalOceanAccount
- Direction
- server_manager.www.cloud_accounts uses server_manager.www.digitalocean_account, so a change to server_manager.www.digitalocean_account can break server_manager.www.cloud_accounts, while a change to server_manager.www.cloud_accounts can't break server_manager.www.digitalocean_account.
- Position
- Below the diagonal: server_manager.www.cloud_accounts uses a module listed above it, which is the healthy direction.
37→34 server_manager.www.cloud_accounts uses server_manager.www.gcp_account✕
- Connections
- 1 pair of types, where a type in server_manager.www.cloud_accounts uses a type in server_manager.www.gcp_account.
- The types involved
server_manager.www.cloud_accounts.CloudAccounts→server_manager.www.gcp_account.GcpAccount
- Direction
- server_manager.www.cloud_accounts uses server_manager.www.gcp_account, so a change to server_manager.www.gcp_account can break server_manager.www.cloud_accounts, while a change to server_manager.www.cloud_accounts can't break server_manager.www.gcp_account.
- Position
- Below the diagonal: server_manager.www.cloud_accounts uses a module listed above it, which is the healthy direction.
38→19 server_manager.www.digitalocean_server uses server_manager.cloud.digitalocean_api✕
- Connections
- 2 pairs of types, where a type in server_manager.www.digitalocean_server uses a type in server_manager.cloud.digitalocean_api.
- The types involved
server_manager.www.digitalocean_server.DigitalOceanHost→server_manager.cloud.digitalocean_api.DigitalOceanSessionserver_manager.www.digitalocean_server.DigitalOceanServer→server_manager.cloud.digitalocean_api.DigitalOceanSession
- Direction
- server_manager.www.digitalocean_server uses server_manager.cloud.digitalocean_api, so a change to server_manager.cloud.digitalocean_api can break server_manager.www.digitalocean_server, while a change to server_manager.www.digitalocean_server can't break server_manager.cloud.digitalocean_api.
- Position
- Below the diagonal: server_manager.www.digitalocean_server uses a module listed above it, which is the healthy direction.
38→20 server_manager.www.digitalocean_server uses server_manager.model.server✕
- Connections
- 2 pairs of types, where a type in server_manager.www.digitalocean_server uses a type in server_manager.model.server.
- The types involved
server_manager.www.digitalocean_server.DigitalOceanHost→server_manager.model.server.DataAmountserver_manager.www.digitalocean_server.DigitalOceanHost→server_manager.model.server.MonetaryCost
- Direction
- server_manager.www.digitalocean_server uses server_manager.model.server, so a change to server_manager.model.server can break server_manager.www.digitalocean_server, while a change to server_manager.www.digitalocean_server can't break server_manager.model.server.
- Position
- Below the diagonal: server_manager.www.digitalocean_server uses a module listed above it, which is the healthy direction.
38→27 server_manager.www.digitalocean_server uses server_manager.model.digitalocean✕
- Connections
- 1 pair of types, where a type in server_manager.www.digitalocean_server uses a type in server_manager.model.digitalocean.
- The types involved
server_manager.www.digitalocean_server.DigitalOceanHost→server_manager.model.digitalocean.Region
- Direction
- server_manager.www.digitalocean_server uses server_manager.model.digitalocean, so a change to server_manager.model.digitalocean can break server_manager.www.digitalocean_server, while a change to server_manager.www.digitalocean_server can't break server_manager.model.digitalocean.
- Position
- Below the diagonal: server_manager.www.digitalocean_server uses a module listed above it, which is the healthy direction.
38→29 server_manager.www.digitalocean_server uses server_manager.www.shadowbox_server✕
- Connections
- 1 pair of types, where a type in server_manager.www.digitalocean_server uses a type in server_manager.www.shadowbox_server.
- The types involved
server_manager.www.digitalocean_server.DigitalOceanServer→server_manager.www.shadowbox_server.ShadowboxServer
- Direction
- server_manager.www.digitalocean_server uses server_manager.www.shadowbox_server, so a change to server_manager.www.shadowbox_server can break server_manager.www.digitalocean_server, while a change to server_manager.www.digitalocean_server can't break server_manager.www.shadowbox_server.
- Position
- Below the diagonal: server_manager.www.digitalocean_server uses a module listed above it, which is the healthy direction.
38→35 server_manager.www.digitalocean_server uses server_manager.www.gcp_server✕
- Connections
- 1 pair of types, where a type in server_manager.www.digitalocean_server uses a type in server_manager.www.gcp_server.
- The types involved
server_manager.www.digitalocean_server.DigitalOceanServer→server_manager.www.gcp_server.InstallState
- Direction
- server_manager.www.digitalocean_server uses server_manager.www.gcp_server, so a change to server_manager.www.gcp_server can break server_manager.www.digitalocean_server, while a change to server_manager.www.digitalocean_server can't break server_manager.www.gcp_server.
- Position
- Below the diagonal: server_manager.www.digitalocean_server uses a module listed above it, which is the healthy direction.
39→10 server_manager.www.outline-gcp-create-server-app uses server_manager.electron.digitalocean_oauth✕
- Connections
- 1 pair of types, where a type in server_manager.www.outline-gcp-create-server-app uses a type in server_manager.electron.digitalocean_oauth.
- The types involved
server_manager.www.outline-gcp-create-server-app.GcpCreateServerApp→server_manager.electron.digitalocean_oauth.Account
- Direction
- server_manager.www.outline-gcp-create-server-app uses server_manager.electron.digitalocean_oauth, so a change to server_manager.electron.digitalocean_oauth can break server_manager.www.outline-gcp-create-server-app, while a change to server_manager.www.outline-gcp-create-server-app can't break server_manager.electron.digitalocean_oauth.
- Position
- Below the diagonal: server_manager.www.outline-gcp-create-server-app uses a module listed above it, which is the healthy direction.
39→11 server_manager.www.outline-gcp-create-server-app uses server_manager.model.location✕
- Connections
- 1 pair of types, where a type in server_manager.www.outline-gcp-create-server-app uses a type in server_manager.model.location.
- The types involved
server_manager.www.outline-gcp-create-server-app.GcpCreateServerApp→server_manager.model.location.CloudLocation
- Direction
- server_manager.www.outline-gcp-create-server-app uses server_manager.model.location, so a change to server_manager.model.location can break server_manager.www.outline-gcp-create-server-app, while a change to server_manager.www.outline-gcp-create-server-app can't break server_manager.model.location.
- Position
- Below the diagonal: server_manager.www.outline-gcp-create-server-app uses a module listed above it, which is the healthy direction.
39→34 server_manager.www.outline-gcp-create-server-app uses server_manager.www.gcp_account✕
- Connections
- 1 pair of types, where a type in server_manager.www.outline-gcp-create-server-app uses a type in server_manager.www.gcp_account.
- The types involved
server_manager.www.outline-gcp-create-server-app.GcpCreateServerApp→server_manager.www.gcp_account.GcpAccount
- Direction
- server_manager.www.outline-gcp-create-server-app uses server_manager.www.gcp_account, so a change to server_manager.www.gcp_account can break server_manager.www.outline-gcp-create-server-app, while a change to server_manager.www.outline-gcp-create-server-app can't break server_manager.www.gcp_account.
- Position
- Below the diagonal: server_manager.www.outline-gcp-create-server-app uses a module listed above it, which is the healthy direction.
40→21 server_manager.www.ui_components.app-root uses server_manager.www.ui_components.outline-server-view✕
- Connections
- 1 pair of types, where a type in server_manager.www.ui_components.app-root uses a type in server_manager.www.ui_components.outline-server-view.
- The types involved
server_manager.www.ui_components.app-root.AppRoot→server_manager.www.ui_components.outline-server-view.ServerView
- Direction
- server_manager.www.ui_components.app-root uses server_manager.www.ui_components.outline-server-view, so a change to server_manager.www.ui_components.outline-server-view can break server_manager.www.ui_components.app-root, while a change to server_manager.www.ui_components.app-root can't break server_manager.www.ui_components.outline-server-view.
- Position
- Below the diagonal: server_manager.www.ui_components.app-root uses a module listed above it, which is the healthy direction.
40→39 server_manager.www.ui_components.app-root uses server_manager.www.outline-gcp-create-server-app✕
- Connections
- 1 pair of types, where a type in server_manager.www.ui_components.app-root uses a type in server_manager.www.outline-gcp-create-server-app.
- The types involved
server_manager.www.ui_components.app-root.AppRoot→server_manager.www.outline-gcp-create-server-app.GcpCreateServerApp
- Direction
- server_manager.www.ui_components.app-root uses server_manager.www.outline-gcp-create-server-app, so a change to server_manager.www.outline-gcp-create-server-app can break server_manager.www.ui_components.app-root, while a change to server_manager.www.ui_components.app-root can't break server_manager.www.outline-gcp-create-server-app.
- Position
- Below the diagonal: server_manager.www.ui_components.app-root uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Domain Modelling
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 170 | High / Critical |
| A05:2025 — Injection | 11 | High / Critical |
| A07:2025 — Authentication Failures | 9 | High / Critical |
Roadmap
Top priorities: Resolve the 3 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2), REDACTED; Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies; Fix the listed violations: import through public entries (package exports / slice index), never reach into another layer or package's internals.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 3 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2), REDACTED. | +10.1 pts | Low | REDACTED Scanning |
| Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies. | +7.3 pts | Medium | Dependency Hygiene |
| Resolve the 5 No assertions finding(s) in Test Quality — start with fetch.spec.ts (2), value_stream.spec.ts (2), outline_server_repository.spec.ts. | +2.0 pts | Low | Test Quality |
| Fix the listed violations: import through public entries (package exports / slice index), never reach into another layer or package's internals. | +2.6 pts | Medium | Import Boundaries |
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with OutlineService.csproj. | +1.2 pts | Low | ADR Quality |
| Resolve the 1 EmptyCatchBlock finding(s) in Explicit Debt — start with OutlineService.cs. | +0.8 pts | Low | Explicit Debt |
| Enable Dependabot/Renovate or a dependency-review gate. | +1.6 pts | Medium | Security & performance tooling |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +1.6 pts | Medium | Release Hygiene |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 1.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| client/electron/windows/OutlineService/OutlineService/OutlineService.cs | 2.7 | Slop | Explicit Debt: EmptyCatchBlock |
| REDACTED | 3.0 | Slop | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 5.0 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| client/web/app/app.ts | 5.6 | Mixed | Cyclomatic Complexity: App.showLocalizedError (cyclomatic 25) |
| server_manager/www/ui_components/app-root.ts | 5.6 | Mixed | God Classes: MethodTooLong: AppRoot.template |
| server_manager/www/ui_components/outline-server-view.ts | 5.7 | Mixed | God Classes: MethodTooLong: ServerView.template |
| REDACTED | 5.8 | Mixed | Secrets (history): High secret: REDACTED |
| REDACTED | 6.4 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| client/electron/index.ts | 6.5 | Mixed | Cognitive Complexity: index.main (cognitive 16) |
| client/capacitor/plugins/capacitor-plugin-outline/ios/Sources/CapacitorPluginOutline/CapacitorPluginOutline.swift | 7.1 | Mixed | Code Duplication: Edited copy of a member (92 corresponding lines) |
| client/web/ui_components/app-root.js | 7.2 | Mixed | God Classes: MethodTooLong: AppRoot.template |
| REDACTED | 7.2 | Mixed | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 7.2 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 7.2 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.2 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 7.2 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
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 55 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 — 55 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, 497 of 515 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
- D10 Test 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. The 171 test(s) behind this row are the ones the JavaScript/TypeScript census could read, and this repository also carries at least 18 test source file(s) (.go) that it cannot: it reads JavaScript/TypeScript test declarations off disk, so a JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
- 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 reliability NOT SCORED: this repository's production source includes .ts, and the built-in reliability runner cannot re-run the .ts test suite(s) — so reliability was not measured for the repository as a whole. The Go (localhost): measured (0 flaky) suite(s) did re-run, and came back with 0 flaky across 1 measured tier(s) — but that is a figure for one half of the product, and we do not publish a partial one as if it were complete. This is OUR limitation, not a defect in the repo — test reliability is excluded from the score rather than counted.
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `dotnet list package` did not return usable output (restore or query failed); no outdated/vulnerable/deprecated data to assess. The tool said: `dotnet list package` exited 1 with no output.
- D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares REDACTED, but the licence verdict published here was taken over its NuGet package dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares a Go module (REDACTED/go.sum), but the licence verdict published here was taken over its NuGet package dependencies. Nothing was read about its Go dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- D17 Explicit Debt — 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. The 4 deducted marker(s) and the 0.5/KLoC density on this row were taken over this repository's .NET projects ALONE: .ts (25,133 lines, 70% of production source) went unread, because every marker collector on this path is reached through a C# workspace. A read-only sweep of that source finds at least 101 task marker(s) (TODO/FIXME/HACK/XXX) across 41 file(s) that this score does not count — a floor, since only line comments are read there and D17's other eight marker kinds (suppressions, NoWarn, editorconfig severities, empty catches, commented-out code, Obsolete, dead code, preprocessor branches) need a compiler we do not have for that language. The debt in that source is UNMEASURED — its absence from the score above is a gap in this analyzer's language coverage, not a finding that the code carries none.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D21 Naming Consistency — 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. 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 — 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. D22's deterministic call-shape rules are gated per language (docs/plans/deterministic-engine.md, P5; C# and each NeutralApiArms arm pass): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D24 Comment Value — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- D30 Dependency Vulnerabilities — measured, with a gap in what it reached — 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. `dotnet list package --vulnerable` could not read this solution's dependency graph — it reported an error for at least one project and returned no package data at all (typically a REDACTED / non-PackageReference project, which the command cannot read). An unreadable dependency graph is not a clean one; migrate the project(s) to PackageReference to enable this scan. 2 of 3 declared ecosystem(s) (npm,osv) WERE scanned and every vulnerability they reported is included in this result; nuget was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that nuget is free of known-vulnerable dependencies.
- D34 Knowledge Freshness — 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. File-level freshness contradicts repo activity: 35 commits in the last 90 days, yet 126 of 154 significant files carry no living knowledge. Those two readings cannot both be true, so the per-file recency signal is treated as unreliable here and freshness is not scored for this run.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Boot via AndroidApp (client/capacitor/android/app). the Android app did not build — `./gradlew :app:assembleDebug` exited 1: Where: Script 'client/capacitor/android/app/capacitor.build.gradle' line: 10 * What went wrong: A problem occurred evaluating script. > Could not…; runtime evidence skipped (launch chosen because client/capacitor/android/app/build.gradle applies the Android application plugin and client/capacitor/android/gradlew builds it).
- 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.
- 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's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- M4 Documentation accuracy — 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. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- 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.
- R11 Import Boundaries — 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. 3 further occurrence(s) are not listed individually; the score already reflects all 43.
- R4 Test Coverage — 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. 29 further occurrence(s) are not listed individually; the score already reflects all 69.
- R8 Dependency Hygiene — 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. 22 further occurrence(s) are not listed individually; the score already reflects all 62.
- X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X13 Undrained process stream — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X14 Bypassable address classification — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X16 Unfloored truncation loop — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X18 Disposal-pattern correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X27 Collection changed while being enumerated — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X28 Index access outside its own emptiness guard — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X3 Exception handling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D13 REDACTED Scanning: REDACTED 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.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- 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.
- D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
- D22 Internal API Consistency: API consistency compares the call shapes of members that play the same role on the exposed C# surface: whether the API suits its callers is not measured, and surfaces in other languages are not measured.
- D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- 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.
- 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.
- 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.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- 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
4 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was App.showLocalizedError at 25.
What to do
- Bring the 4 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with App.showLocalizedError (cyclomatic 25), configregistry.parseIPTableStreamDialer (cyclomatic 23), platform_error.convertRawErrorObjectToError (cyclomatic 18). — 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 4 together lifts Cyclomatic Complexity from 9.1 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
12 method(s) exceeded the cognitive complexity threshold of 15; the worst was configregistry.parseIPTableStreamDialer at 43.
What to do
- Bring the 1 body over 30 down to 30 or less in Cognitive Complexity — start with configregistry.parseIPTableStreamDialer (cognitive 43). — Refactoring it lifts Cognitive Complexity from 7.9 to about 8.3/10.
D3 · God Classes
25 god class(es) detected.
What to do
- Resolve the 10 MethodTooLong finding(s) in God Classes — start with app-root.ts (2), app-root.js (2), outline-server-view.ts (2). — One of this dimension's main actionable groups (10 warning-level).
- Resolve the 6 ClassTooLong finding(s) in God Classes — start with REDACTED (2), app-root.ts, outline-server-view.ts. — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 5 FileTooLong finding(s) in God Classes — start with REDACTED (2), app-root.ts, outline-server-view.ts. — One of this dimension's main actionable groups (5 warning-level).
D4 · Code Duplication
6 duplicated block group(s) detected. 1.3 % of the production lines (543 of 40,965) 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. Measured on part of this repository only: .ts (70% of production source) was not exposed to THIS dimension's token comparison and is not in this count; duplication there is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream.
What to do
- Resolve the 2 Edited copy of a member (5 corresponding lines) finding(s) in Code Duplication — start with config_dial_endpoint.go, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Edited copy of a member (92 corresponding lines) finding(s) in Code Duplication — start with CapacitorPluginOutline.swift. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Edited copy of a member (24 corresponding lines) finding(s) in Code Duplication — start with CapacitorPluginOutline.swift. — One of this dimension's main actionable groups (1 warning-level).
D5 · Coupling
17 production modules (Gradle+npm+Go+SwiftPM), 0 dependency cycle(s), 1 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; 4 module(s) off the main sequence, with abstractness counted on 14 of the 17 (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 4 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 1 Unstable project CapacitorPluginOutline finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
D6 · Cohesion (LCOM4)
2 of 63 classes have LCOM4 above 3.
What to do
- Resolve the 2 Low cohesion finding(s) in Cohesion (LCOM4) — start with app-root.ts, outline-server-view.ts. — One of this dimension's main actionable groups (2 warning-level).
D10 · Test Quality
0 skipped, 5 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 171 tests. Measured on the JavaScript/TypeScript suite only — at least 18 test source file(s) (.go) went unread, so its test quality is unmeasured and is not in these counts.
What to do
- Resolve the 5 No assertions finding(s) in Test Quality — start with fetch.spec.ts (2), value_stream.spec.ts (2), outline_server_repository.spec.ts. — One of this dimension's main actionable groups (5 warning-level).
D13 · REDACTED Scanning
3 secret(s) detected. 2 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.
What to do
- Resolve the 3 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 issue-level).
D14 · License Compliance
0 of 0 packages use a banned license. The depth of this set was not established for this repository: the graded packages are what this pass resolved, and no lockfile was read, so it is not certified to be the full transitive closure. ★ COVERAGE OF THIS VERDICT: it grades this repository's NuGet package dependencies and nothing else. The repository also declares REDACTED and a Go module (REDACTED/go.sum), and the licences of those dependency graphs were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D16 · Bus Factor
8 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is client/src/cordova/apple/OutlineAppleLib/Sources/OutlineTunnel/OutlineVpn.swift. Counted over 153 of the 245 production source files in this repository: 91 are under the ~2,400-byte size floor this dimension measures over, and the remaining 1 have no attributable history left to measure.
D17 · Explicit Debt
4 deducted debt markers + 1 dead symbols across 1084 LoC in the .NET projects (0.5/KLoC) → score 9.0. Measured on the .NET source only: .ts (70% of production source) was not read, and carries at least 101 uncounted task marker(s) in 41 file(s).
What to do
- Resolve the 1 EmptyCatchBlock finding(s) in Explicit Debt — start with OutlineService.cs. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 3 TodoComment finding(s) in Explicit Debt — start with OutlineService.cs (3). — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 Dead code finding(s) in Explicit Debt — start with OutlineService.cs. — One of this dimension's main actionable groups (1 warning-level).
D19 · Documentation Quality
1 of 2 documentation facets pass in full; short on: F2 example. 14 document(s) read across 8 unit(s).
What to do
- Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md. — One of this dimension's main actionable groups (1 recommendation-level).
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 OutlineService.csproj. — One of this dimension's main actionable groups (1 recommendation-level).
D21 · Naming Consistency
3 naming inconsistencies among 217 declarations measured against a convention their peers follow.
What to do
- Resolve the 1 `handleOpenURL` spells `URL` where 45 names in the project spell it… finding(s) in Naming Consistency — start with main.cordova.ts. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 `messageID` spells `ID` where 166 names in the project spell it `Id` finding(s) in Naming Consistency — start with localize.ts. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 `establishVpnRequestJSON` spells `Vpn` where 15 names in the project… finding(s) in Naming Consistency — start with vpn_linux.go. — One of this dimension's main actionable groups (1 recommendation-level).
D22 · Internal API Consistency
0 API inconsistencies among 8 exposed members measured against a convention their peers follow.
D24 · Comment Value
14 of 643 judged comments only repeat the code they sit on (2.2 %). 24 comment(s) in another language or script were not judged.
What to do
- Resolve the 14 redundant comment finding(s) in Comment Value — start with AssemblyInfo.cs (4), server.ts (4), index.ts. — One of this dimension's main actionable groups (14 recommendation-level).
D27 · Navigability
22 % of calls cross a namespace and 8 % go through an interface, but 65 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
5 finding(s): 0 critical, 5 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 3 REDACTED finding(s) in Secrets (history) — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 2 High secret finding(s) in Secrets (history) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
11 finding(s): 0 critical, 2 high, 8 medium, 1 low. semgrep hit a parse error in 19 file(s) — `client/capacitor/android/gradlew` (line 74, line 180), `client/src/cordova/android/OutlineAndroidLib/gradlew` (line 177), `server_manager/install_scripts/install_server.sh` (line 226, line 227, lines 552–557), `third_party/tap-windows6/src/adapter.c` (line 47, line 49, line 65, …), `third_party/tap-windows6/src/adapter.h`, … (+14 more) — 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 2 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 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (4 warning-level).
D30 · Dependency Vulnerabilities
160 finding(s): 14 critical, 91 high, 42 medium, 13 low. Partial dependency scan: 2 of 3 declared ecosystem(s) were scanned (npm,osv), and the findings above are real and complete for them. nuget was not scanned (nuget: `dotnet list package --vulnerable` could not read this solution's dependency graph — it reported an error for at least one project and returned no package data at all (typically a REDACTED / non-PackageReference project, which the command cannot read). An unreadable dependency graph is not a clean one; migrate the project(s) to PackageReference to enable this scan), so this is not the whole dependency surface and the result is reported at reduced confidence.
What to do
- Resolve the 90 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (85), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (90 issue-level).
- Resolve the 14 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (13), REDACTED. — One of this dimension's main actionable groups (14 issue-level).
- Resolve the 1 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D35 · Change Coupling
Strongest change-coupling: index.ts↔vpn.fake.ts 80%; index.ts↔vpn.fake.ts 60%; index.ts↔main.electron.ts 56%
What to do
- Resolve the 3 Change coupling finding(s) in Change Coupling — start with index.ts, Package.swift, REDACTED. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 Change-coupling hub finding(s) in Change Coupling — start with vpn.fake.ts. — One of this dimension's main actionable groups (1 warning-level).
D36 · Supply-chain Provenance & Signing
2/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 5 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 9 platform declaration(s) and 10 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX5 · Architecture & structure
AX6 · Interface segregation
- `Server` declares 25 required operations: `getId`, `getName`, `getVersion`, `setName`, `getAccessKey`, `listAccessKeys`, `getServerMetrics`, `addAccessKey`, `renameAccessKey`, `removeAccessKey`, `setDefaultDataLimit`, `getDefaultDataLimit`, `removeDefaultDataLimit`, `setAccessKeyDataLimit`, `removeAccessKeyDataLimit`, `getMetricsEnabled`, `setMetricsEnabled`, `getMetricsId`, `isHealthy`, `getCreatedDate`, `getHostnameForAccessKeys`, `setHostnameForAccessKeys`, `getManagementApiUrl`, `getPortForNewAccessKeys`, `setPortForNewAccessKeys`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data 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. — server_manager/model/server.ts:19
What to do
- Split fat interfaces into focused role-interfaces so clients depend only on what they use.
AX9 · CQS / query purity
DM9 · Scattered domain decisions
GD1 · Unfinished & placeholder code
M1 · Documentation (README)
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
- client/src/cordova/android/README.md links to `client/src/cordova/android/OutlineAndroidLib/build.gradle`, but `client/src/cordova/android/client/src/cordova/android/OutlineAndroidLib/build.gradle` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — client/src/cordova/android/README.md:24
What to do
- Reconcile the README with reality: client/src/cordova/android/README.md links to `client/src/cordova/android/OutlineAndroidLib/build.gradle`, but `client/src/cordova/android/client/src/cordova/android/OutlineAndroidLib/build.gradle` does not exist.
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
- Only 8/12 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `client`, `client/capacitor/ios/App`, `infrastructure`, `server_manager`.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
- Add a health-check endpoint (@godaddy/terminus or a /health route) so orchestrators and load balancers can probe liveness/readiness.
P3 · Security & performance tooling
- `REDACTED` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — REDACTED:3
What to do
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
PF3 · Async & latency hygiene
R1 · Type Safety
R10 · Code Duplication
- 6 of the duplicated blocks reported below have copies in at least two of the sibling directories capacitor, electron, go, src, web under client/. That concentration is one structural fact, not 6 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 6 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — client/capacitor/src/index.ts:165
- server_manager/www/digitalocean_server.ts:45 · server_manager/www/gcp_server.ts:29 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — server_manager/www/digitalocean_server.ts:45
- server_manager/www/views/server_view/server_metrics_row/bandwidth.ts:288 · server_manager/www/views/server_view/server_metrics_row/tunnel_time.ts:121 — the two spans are one implementation copied and then locally edited — 89 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — server_manager/www/views/server_view/server_metrics_row/bandwidth.ts:288
- client/capacitor/src/index.ts:165 · client/web/app/main.cordova.ts:104 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — client/capacitor/src/index.ts:165
- client/capacitor/build.action.mjs:60 · client/src/cordova/build.action.mjs:70 — the two spans are one implementation copied and then locally edited — 73 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — client/capacitor/build.action.mjs:60
- REDACTED:733 · REDACTED:759 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:733
- server_manager/www/cloud_accounts.ts:47 · server_manager/www/testing/models.ts:378 — the two spans are one implementation copied and then locally edited — 101 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — server_manager/www/cloud_accounts.ts:47
- REDACTED:1394 · REDACTED:1417 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:1394
- server_manager/cloud/gcp_api.ts:362 · server_manager/cloud/gcp_api.ts:452 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — server_manager/cloud/gcp_api.ts:362
- REDACTED:689 · REDACTED:717 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — REDACTED:689
- server_manager/www/views/server_view/access_key_data_table/access_key_controls/index.ts:121 · server_manager/www/views/server_view/access_key_data_table/access_key_controls/index.ts:141 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — server_manager/www/views/server_view/access_key_data_table/access_key_controls/index.ts:121
- client/src/cordova/setup.action.mjs:136 · client/src/cordova/setup.action.mjs:173 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — client/src/cordova/setup.action.mjs:136
- server_manager/electron/digitalocean_oauth.ts:244 · REDACTED:155 — the two spans are one implementation copied and then locally edited — 58 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — server_manager/electron/digitalocean_oauth.ts:244
- REDACTED:1355 · REDACTED:1376 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:1355
- client/capacitor/web_bundle.mjs:54 · client/web/build.action.mjs:39 — the two spans are one implementation copied and then locally edited — 67 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — client/capacitor/web_bundle.mjs:54
- server_manager/cloud/gcp_api.ts:310 · server_manager/cloud/gcp_api.ts:335 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — server_manager/cloud/gcp_api.ts:310
- REDACTED:1103 · REDACTED:1117 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:1103
- server_manager/www/manual_server.ts:43 · server_manager/www/testing/models.ts:325 — the two spans are one implementation copied and then locally edited — 68 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — server_manager/www/manual_server.ts:43
- infrastructure/i18n.ts:61 · infrastructure/i18n.ts:81 — the two spans are one implementation copied and then locally edited — 51 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — infrastructure/i18n.ts:61
- client/src/cordova/build.action.mjs:48 · client/src/cordova/setup.action.mjs:46 — the two spans are one implementation copied and then locally edited — 66 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — client/src/cordova/build.action.mjs:48
- client/web/webpack_css_rtl_loader.cjs:18 · server_manager/css-in-js-rtl-loader.js:19 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — client/web/webpack_css_rtl_loader.cjs:18
- server_manager/www/digitalocean_server.ts:110 · server_manager/www/gcp_server.ts:166 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — server_manager/www/digitalocean_server.ts:110
- client/web/app/app.ts:318 · client/web/app/app.ts:330 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — client/web/app/app.ts:318
- client/capacitor/web_build.action.mjs:17 · client/go/build.action.mjs:17 — the two spans are one implementation copied and then locally edited — 58 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — client/capacitor/web_build.action.mjs:17
- server_manager/install_scripts/build_do_install_script_ts.node.js:15 · server_manager/install_scripts/build_gcp_install_script_ts.node.js:15 — the two spans are one implementation copied and then locally edited — 55 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — server_manager/install_scripts/build_do_install_script_ts.node.js:15
- server_manager/www/shadowbox_server.ts:164 · server_manager/www/shadowbox_server.ts:193 — the two spans are one implementation copied and then locally edited — 61 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — server_manager/www/shadowbox_server.ts:164
- client/electron/start.action.mjs:52 · REDACTED:126 — the two spans are one implementation copied and then locally edited — 50 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — client/electron/start.action.mjs:52
- client/web/views/root_view/connection_confirm_dialog/index.ts:25 · client/web/views/servers_view/server_list_item/server_card/server_info_dialog/index.ts:23 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — client/web/views/root_view/connection_confirm_dialog/index.ts:25
- server_manager/www/ui_components/outline-share-dialog.ts:170 · server_manager/www/ui_components/outline-share-dialog.ts:178 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — server_manager/www/ui_components/outline-share-dialog.ts:170
- client/capacitor/start.action.mjs:40 · client/web/start.action.mjs:33 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — client/capacitor/start.action.mjs:40
- client/web/views/servers_view/server_list_item/server_card/index.ts:36 · client/web/views/servers_view/server_list_item/server_card/legacy.ts:337 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — client/web/views/servers_view/server_list_item/server_card/index.ts:36
- server_manager/www/views/server_view/server_metrics_row/bandwidth.ts:37 · server_manager/www/views/server_view/server_metrics_row/tunnel_time.ts:35 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — server_manager/www/views/server_view/server_metrics_row/bandwidth.ts:37
What to do
- Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
R11 · Import Boundaries
- client/capacitor/src/polyfills.ts:36 imports @polymer/polymer/lib/utils/settings.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — client/capacitor/src/polyfills.ts:36
- client/web/app/main.cordova.ts:21 imports @polymer/polymer/lib/utils/settings.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — client/web/app/main.cordova.ts:21
- client/web/ui_components/app-root.js:20 imports @polymer/polymer/lib/legacy/polymer.dom.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — client/web/ui_components/app-root.js:20
- client/web/ui_components/app-root.js:69 imports @polymer/polymer/lib/legacy/class.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — client/web/ui_components/app-root.js:69
- client/web/ui_components/app-root.js:70 imports @polymer/polymer/lib/utils/html-tag.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — client/web/ui_components/app-root.js:70
- server_manager/www/ui_components/app-root.ts:53 imports @polymer/polymer/lib/legacy/class, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — server_manager/www/ui_components/app-root.ts:53
- server_manager/www/ui_components/app-root.ts:55 imports @polymer/polymer/lib/utils/html-tag, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — server_manager/www/ui_components/app-root.ts:55
- server_manager/www/ui_components/cloud-install-styles.ts:17 imports @polymer/polymer/lib/utils/html-tag, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — server_manager/www/ui_components/cloud-install-styles.ts:17
- server_manager/www/ui_components/outline-about-dialog.ts:20 imports @polymer/polymer/lib/legacy/polymer-fn, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — server_manager/www/ui_components/outline-about-dialog.ts:20
- server_manager/www/ui_components/outline-about-dialog.ts:21 imports @polymer/polymer/lib/utils/html-tag, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — server_manager/www/ui_components/outline-about-dialog.ts:21
- server_manager/www/ui_components/outline-cloud-instructions-view.ts:20 imports @polymer/polymer/lib/legacy/polymer-fn, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — server_manager/www/ui_components/outline-cloud-instructions-view.ts:20
- server_manager/www/ui_components/outline-cloud-instructions-view.ts:21 imports @polymer/polymer/lib/utils/html-tag, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — server_manager/www/ui_components/outline-cloud-instructions-view.ts:21
- server_manager/www/ui_components/outline-do-oauth-step.ts:22 imports @polymer/polymer/lib/legacy/polymer-fn, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — server_manager/www/ui_components/outline-do-oauth-step.ts:22
- server_manager/www/ui_components/outline-do-oauth-step.ts:23 imports @polymer/polymer/lib/utils/html-tag, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — server_manager/www/ui_components/outline-do-oauth-step.ts:23
- server_manager/www/ui_components/outline-feedback-dialog.ts:26 imports @polymer/polymer/lib/legacy/polymer-fn, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — server_manager/www/ui_components/outline-feedback-dialog.ts:26
- server_manager/www/ui_components/outline-feedback-dialog.ts:27 imports @polymer/polymer/lib/utils/html-tag, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — server_manager/www/ui_components/outline-feedback-dialog.ts:27
- server_manager/www/ui_components/outline-help-bubble.ts:19 imports @polymer/polymer/lib/legacy/polymer-fn, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — server_manager/www/ui_components/outline-help-bubble.ts:19
- server_manager/www/ui_components/outline-help-bubble.ts:20 imports @polymer/polymer/lib/utils/html-tag, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — server_manager/www/ui_components/outline-help-bubble.ts:20
- server_manager/www/ui_components/outline-iconset.ts:18 imports @polymer/polymer/lib/utils/html-tag, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — server_manager/www/ui_components/outline-iconset.ts:18
- server_manager/www/ui_components/outline-intro-step.ts:22 imports @polymer/polymer/lib/legacy/polymer-fn, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — server_manager/www/ui_components/outline-intro-step.ts:22
- server_manager/www/ui_components/outline-intro-step.ts:23 imports @polymer/polymer/lib/utils/html-tag, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — server_manager/www/ui_components/outline-intro-step.ts:23
- server_manager/www/ui_components/outline-manual-server-entry.ts:31 imports @polymer/polymer/lib/legacy/polymer-fn, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — server_manager/www/ui_components/outline-manual-server-entry.ts:31
- server_manager/www/ui_components/outline-manual-server-entry.ts:32 imports @polymer/polymer/lib/utils/html-tag, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — server_manager/www/ui_components/outline-manual-server-entry.ts:32
- server_manager/www/ui_components/outline-metrics-option-dialog.ts:21 imports @polymer/polymer/lib/legacy/polymer-fn, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — server_manager/www/ui_components/outline-metrics-option-dialog.ts:21
- server_manager/www/ui_components/outline-metrics-option-dialog.ts:22 imports @polymer/polymer/lib/utils/html-tag, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — server_manager/www/ui_components/outline-metrics-option-dialog.ts:22
- server_manager/www/ui_components/outline-modal-dialog.ts:18 imports @polymer/polymer/lib/legacy/polymer-fn, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — server_manager/www/ui_components/outline-modal-dialog.ts:18
- server_manager/www/ui_components/outline-modal-dialog.ts:19 imports @polymer/polymer/lib/utils/html-tag, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — server_manager/www/ui_components/outline-modal-dialog.ts:19
- server_manager/www/ui_components/outline-progress-spinner.ts:18 imports @polymer/polymer/lib/legacy/polymer-fn, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — server_manager/www/ui_components/outline-progress-spinner.ts:18
- server_manager/www/ui_components/outline-progress-spinner.ts:19 imports @polymer/polymer/lib/utils/html-tag, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — server_manager/www/ui_components/outline-progress-spinner.ts:19
- server_manager/www/ui_components/outline-server-settings-styles.ts:17 imports @polymer/polymer/lib/utils/html-tag, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — server_manager/www/ui_components/outline-server-settings-styles.ts:17
- server_manager/www/ui_components/outline-server-settings.ts:26 imports @polymer/polymer/lib/legacy/polymer-fn, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — server_manager/www/ui_components/outline-server-settings.ts:26
- server_manager/www/ui_components/outline-server-settings.ts:27 imports @polymer/polymer/lib/utils/html-tag, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — server_manager/www/ui_components/outline-server-settings.ts:27
- server_manager/www/ui_components/outline-server-view.ts:44 imports @polymer/polymer/lib/mixins/dir-mixin, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — server_manager/www/ui_components/outline-server-view.ts:44
- server_manager/www/ui_components/outline-share-dialog.ts:19 imports @polymer/polymer/lib/legacy/polymer-fn, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — server_manager/www/ui_components/outline-share-dialog.ts:19
- server_manager/www/ui_components/outline-share-dialog.ts:20 imports @polymer/polymer/lib/utils/html-tag, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — server_manager/www/ui_components/outline-share-dialog.ts:20
- server_manager/www/ui_components/outline-step-view.ts:18 imports @polymer/polymer/lib/legacy/polymer-fn, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — server_manager/www/ui_components/outline-step-view.ts:18
- server_manager/www/ui_components/outline-step-view.ts:19 imports @polymer/polymer/lib/utils/html-tag, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — server_manager/www/ui_components/outline-step-view.ts:19
- server_manager/www/ui_components/outline-survey-dialog.ts:23 imports @polymer/polymer/lib/mixins/dir-mixin, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — server_manager/www/ui_components/outline-survey-dialog.ts:23
- server_manager/www/ui_components/outline-survey-dialog.ts:24 imports @polymer/polymer/lib/utils/html-tag, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — server_manager/www/ui_components/outline-survey-dialog.ts:24
- server_manager/www/ui_components/outline-tos-view.ts:16 imports @polymer/polymer/lib/legacy/polymer-fn, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — server_manager/www/ui_components/outline-tos-view.ts:16
What to do
- Fix the listed violations: import through public entries (package exports / slice index), never reach into another layer or package's internals.
R2 · Cyclomatic Complexity
- showLocalizedError has cyclomatic complexity 25 and cognitive complexity 27; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — client/web/app/app.ts:260
- convertRawErrorObjectToError has cyclomatic complexity 18 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — client/web/model/platform_error.ts:55
- main has cyclomatic complexity 14 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — client/capacitor/build.action.mjs:37
- toErrorCode has cyclomatic complexity 13 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — client/web/model/errors.ts:175
- main has cyclomatic complexity 13 and cognitive complexity 9; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — client/src/cordova/build.action.mjs:37
- deserializeError has cyclomatic complexity 12 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — client/web/model/platform_error.ts:243
- (anonymous) has cyclomatic complexity 11 and cognitive complexity 10; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — client/capacitor/src/index.ts:210
R3 · Large Files
- REDACTED has 1502 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
- server_manager/www/ui_components/app-root.ts has 1140 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — server_manager/www/ui_components/app-root.ts:1
- server_manager/www/ui_components/outline-server-view.ts has 881 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — server_manager/www/ui_components/outline-server-view.ts:1
- client/web/app/app.ts has 812 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — client/web/app/app.ts:1
- server_manager/cloud/gcp_api.ts has 794 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — server_manager/cloud/gcp_api.ts:1
- client/web/ui_components/app-root.js has 793 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — client/web/ui_components/app-root.js:1
- client/electron/index.ts has 562 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — client/electron/index.ts:1
- server_manager/www/ui_components/outline-server-settings.ts has 528 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — server_manager/www/ui_components/outline-server-settings.ts:1
- server_manager/www/ui_components/outline-manual-server-entry.ts has 522 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — server_manager/www/ui_components/outline-manual-server-entry.ts:1
- client/web/views/servers_view/server_list_item/server_card/index.ts has 455 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — client/web/views/servers_view/server_list_item/server_card/index.ts:1
- server_manager/www/ui_components/outline-intro-step.ts has 445 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — server_manager/www/ui_components/outline-intro-step.ts:1
- server_manager/www/outline-gcp-create-server-app.ts has 441 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — server_manager/www/outline-gcp-create-server-app.ts:1
- server_manager/www/views/server_view/server_metrics_row/bandwidth.ts has 439 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — server_manager/www/views/server_view/server_metrics_row/bandwidth.ts:1
What to do
- Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
R4 · Test Coverage
- No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×40) — client/electron/index.ts:1, client/electron/go_vpn_tunnel.ts:1, REDACTED:1, …
What to do
- Add tests that import the unreached modules (directly or through their public entry).
R5 · Dependency Freshness
R6 · Tooling
R7 · Dead Code
- 5 file(s) (~201 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package.
- 16 file(s) (~917 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — infrastructure
- 113 file(s) (~20533 LoC) were excluded from dead-code analysis. This package's entry point(s) resolved, but the walk stopped one hop in: server_manager/www/digitalocean_account.ts imports '../install_scripts/do_install_script', which is not in the scanned tree. That is usually a generated or build-output module, so reachability cannot see past it and no dead-code claim is made about this package. Nothing is necessarily wrong here. — server_manager
- Unreachable from the 117 application, 18 tooling and 56 test entry point(s) detected in this repo. Gate removals on `npm run build` — an undetected custom entry would make these reachable.
- no import path from any entry point (117 application, 18 tooling, 56 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make (×13) — client/electron/index.ts, REDACTED, client/src/cordova/build.action.mjs, …
- no import path from any entry point (117 application, 18 tooling, 56 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (client/electron/index.ts, client/electron/vpn_service.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — client/electron/go_plugin.ts
- no import path from any entry point (117 application, 18 tooling, 56 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (client/electron/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×3) — client/electron/vpn_service.ts, client/electron/tunnel_store.ts, client/electron/connectivity.ts
- no import path from any entry point (117 application, 18 tooling, 56 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (client/electron/build_main.action.mjs) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — client/electron/webpack_electron_main.mjs
- Nothing imports this binding — it is safe to review for removal. (×10) — client/web/model/errors.ts:175, client/web/views/appearance_view/index.ts:30, client/web/views/licenses_view/index.ts:25, …
- No runtime consumer imports this binding — the only demand on it comes from a type-position import of its module, which asks for the module's type surface rather than for this name. If the value is genuinely unneeded, remove it; if a consumer needs only its TYPE, export that type (e.g. `export type X = typeof x`) and drop the value. A value export — a const, a function, a class — cannot itself be rewritten as `export type`. (×4) — client/web/views/root_view/dns_config_dialog/index.ts:40, client/web/views/root_view/error_details_dialog/index.ts:18, client/web/views/root_view/root_header/index.ts:19, …
- Nothing ultimately consumes this binding: its only referrer is the re-export in client/web/views/servers_view/server_list_item/server_card/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in client/web/views/servers_view/server_list_item/server_card/index.ts in the same commit, or the barrel will import a name that no longer exists. (×2) — client/web/views/servers_view/server_list_item/server_card/legacy.ts:277, client/web/views/servers_view/server_list_item/server_card/legacy.ts:338
- Nothing in its class reads or assigns this private field (for a constructor parameter property: it is stored and never read), and no string key or test reaches it by name. Remove it, or use it where it was meant to take effect. — client/web/app/app.ts:99
What to do
- Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
R8 · Dependency Hygiene
- Imported but not declared in any reachable REDACTED — installs work only by hoisting accident. (×6) — .storybook/preview.js:17, list.action.mjs:19, client/web/views/contact_view/index.ts:17, …
- Declared in the root REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×2) — REDACTED:41, REDACTED:51
- Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×28) — REDACTED:11, REDACTED:12, REDACTED:13, …
- Declared in client/capacitor/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. — client/capacitor/package.json:36
- Declared in infrastructure/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×3) — infrastructure/package.json:19, infrastructure/package.json:12, infrastructure/package.json:20
What to do
- Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports
- server_manager/www/outline-gcp-create-server-app.ts → server_manager/www/ui_components/app-root.ts → server_manager/www/outline-gcp-create-server-app.ts — server_manager/www/outline-gcp-create-server-app.ts:29
- server_manager/www/views/server_view/access_key_data_table/access_key_controls/index.ts → server_manager/www/views/server_view/access_key_data_table/index.ts → server_manager/www/views/server_view/access_key_data_table/access_key_controls/index.ts — server_manager/www/views/server_view/access_key_data_table/access_key_controls/index.ts:27
What to do
- Break each cycle by extracting the shared piece into a module both sides can import.
X24 · Document value interpolated into markup unescaped
- `this.text` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — server_manager/www/views/server_view/icon_tooltip/index.ts:76
What to do
- Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 78.4 | Strong | Solid. |
| Architecture | 60.5 | Adequate — gated by R11 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 74.6 | Strong | Solid. |
| Readiness | 45.4 | Weak — gated by D13, R8 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 61.5 | Adequate | Acceptable, with room to improve. |
| Performance | 100.0 | Exemplary | Strongest area. |
Unscored — 4 check(s) recorded observations but carry no score
- P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
- SC1 Supply-chain hygiene — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X10 Duplicated predicate — 3 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 — 2 control(s) we could not find positive evidence for
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 76 check(s) not relevant to this codebase
- AC1 Text alternatives — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
- AC2 Forms & labels — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
- AC3 Page structure — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
- AC4 Keyboard semantics — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
- AC5 ARIA correctness — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
- AC6 Visual & motion safety — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
- AX1 Captive dependencies — no DI registrations detected
- AX2 Stateful singletons — no singleton implementations detected
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — the Android app did not build — `./gradlew :app:assembleDebug` exited 1: Where: Script 'client/capacitor/android/app/capacitor.build.gradle' line: 10 * What went wrong: A problem occurred evaluating script. > Could not…; runtime evidence skipped (launch chosen because client/capacitor/android/app/build.gradle applies the Android application plugin and client/capacitor/android/gradlew builds it) This is a statement about this run, not a statement about your application: nothing here says the app is inaccessible, only that it was never run.
- C1 Data Protection — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C2 Access Controls — No access-control surface detected in the analyzed source — no web/app surface to authorize (no HTTP API or web-UI project) and no authorization code at all (no [Authorize]/policies, no imperative guard methods). Access control is therefore N/A here — this is a library/CLI, which is authorized by its CALLER, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C4 Data Retention — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C5 Data-Subject Rights — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- D11 Test Reliability — Test reliability not scored — polyglot repository, one half has no runner
- D12 Dependency Hygiene — Dependency hygiene not measured
- D18 Solution Shape — D18 scores the shape of a C#/VB .NET solution, but this repository's production source is mostly .cpp, .go, .java, .kt, .m, .swift, .ts, which the C#/VB workspace does not load — the projects that loaded are an immaterial minority, so solution shape was not assessed for this repository. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
- D23 Boundary Type-Coupling — single shared-core project — no cross-context coupling to assess
- D25 ADR Conformance — no ADRs to check
- D26 Project Cohesion — This repository is one project, `OutlineService` (1084 LoC, 3 public types across 1 namespaces), within the size bounds. Not scored: a single unit of this size gives project cohesion nothing to grade.
- 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) — 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.
- D34 Knowledge Freshness — knowledge concentrated in recent work — freshness signal contradicted by repo activity
- 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 dependency cycles — architectural integrity not assessed
- D8 Code Coverage — Coverage NOT MEASURED: this repository did not build in our analyzer environment (a C#/MSBuild compiler error), so no coverage could be collected. It is excluded from the score rather than counted as a near-zero defect. We did not read WHERE the failing diagnostic is, so this does not claim the fault is in your test code — a repository written for an older SDK band can compile for you and not for us. Run `dotnet build` on this commit; if it succeeds, the gap is ours. Committing the Cobertura/OpenCover/lcov report your CI already produces also lets us measure real coverage without building anything.
- DM1 Aggregate boundaries — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
- DM10 One transaction, one aggregate — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
- DM2 Strongly-typed ids — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
- DM3 Integration-event coupling — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
- DM4 Rich vs anemic model — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
- DM5 Encapsulated state — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
- DM6 Domain ↔ infrastructure boundary — this TypeScript/JavaScript repository maps no type to a persistence framework (TypeORM/Prisma/MikroORM/Sequelize/Mongoose), so DM6's domain↔infrastructure fusion read has no population to be taken over
- DM7 Repository granularity — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and this analysis resolves a call's owner only where the receiver's type is written down in the source. Reported as guidance rather than measured
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- IC1 Incompleteness & stubs — IC1 reached only 3% of this repository's production lines — typescript (26,207 lines), javascript (4,626 lines), go (4,374 lines), swift (2,550 lines), java (1,573 lines), kotlin (551 lines), objectivec (338 lines), cpp (163 lines), c (110 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- P7 Outbound HTTP resilience — not applicable — this isn't a service/API/worker
- P8 Schema migrations — no EF Core usage detected
- 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 — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
- 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 — No web surface detected in the analyzed source — no HTTP API or web-UI project (no controllers/minimal-API endpoints, no Razor/Blazor views) and no web middleware (HTTPS redirection, HSTS, security headers, cookies). Transport security, security headers, secure cookies, CSRF/input-validation and middleware-order controls are therefore N/A here — this is a library/CLI/worker, not a web app. Crypto hygiene was still checked and found nothing to flag. If this codebase becomes web-facing, the dimension reactivates automatically.
- X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X12 Unreachable branch — X12 reached only 3% of this repository's production lines — typescript (26,207 lines), javascript (4,626 lines), go (4,374 lines), swift (2,550 lines), java (1,573 lines), kotlin (551 lines), objectivec (338 lines), cpp (163 lines), c (110 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X13 Undrained process stream — X13 reached only 3% of this repository's production lines — typescript (26,207 lines), javascript (4,626 lines), go (4,374 lines), swift (2,550 lines), java (1,573 lines), kotlin (551 lines), objectivec (338 lines), cpp (163 lines), c (110 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X14 Bypassable address classification — X14 reached only 3% of this repository's production lines — typescript (26,207 lines), javascript (4,626 lines), go (4,374 lines), swift (2,550 lines), java (1,573 lines), kotlin (551 lines), objectivec (338 lines), cpp (163 lines), c (110 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- 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
- X16 Unfloored truncation loop — X16 reached only 3% of this repository's production lines — typescript (26,207 lines), javascript (4,626 lines), go (4,374 lines), swift (2,550 lines), java (1,573 lines), kotlin (551 lines), objectivec (338 lines), cpp (163 lines), c (110 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X18 Disposal-pattern correctness — X18 reached only 3% of this repository's production lines — typescript (26,207 lines), javascript (4,626 lines), go (4,374 lines), swift (2,550 lines), java (1,573 lines), kotlin (551 lines), objectivec (338 lines), cpp (163 lines), c (110 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — no async method does work a token could cancel
- 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
- X21 Side-effecting pattern 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
- X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X27 Collection changed while being enumerated — X27 reached only 3% of this repository's production lines — typescript (26,207 lines), javascript (4,626 lines), go (4,374 lines), swift (2,550 lines), java (1,573 lines), kotlin (551 lines), objectivec (338 lines), cpp (163 lines), c (110 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X28 Index access outside its own emptiness guard — X28 reached only 3% of this repository's production lines — typescript (26,207 lines), javascript (4,626 lines), go (4,374 lines), swift (2,550 lines), java (1,573 lines), kotlin (551 lines), objectivec (338 lines), cpp (163 lines), c (110 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- 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
- X3 Exception handling — X3 reached only 3% of this repository's production lines — typescript (26,207 lines), javascript (4,626 lines), go (4,374 lines), swift (2,550 lines), java (1,573 lines), kotlin (551 lines), objectivec (338 lines), cpp (163 lines), c (110 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- 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 — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X4 Structured logging — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X5 Nullable reference types — no NRT-eligible projects
- 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 — 124 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
- Import cycle (2 files) server_manager/www/outline-gcp-create-server-app.ts:29
- Import cycle (2 files) server_manager/www/views/server_view/access_key_data_table/access_key_controls/index.ts:27
- EmptyCatchBlock client/electron/windows/OutlineService/OutlineService/OutlineService.cs:485
- REDACTED
- REDACTED
- REDACTED
- Unlisted import '@material/web' .storybook/preview.js:17
- Unlisted import 'globby' list.action.mjs:19
- Unlisted import '@material/mwc-list' client/web/views/contact_view/index.ts:17
- Unlisted import '@polymer/iron-iconset-svg' server_manager/www/ui_components/outline-iconset.ts:17
- Unlisted import '@polymer/neon-animation' server_manager/www/ui_components/outline-survey-dialog.ts:16
- Unlisted import '@polymer/paper-menu-button' server_manager/www/ui_components/app-root.ts:28
Serious — 322 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Boundary violation [package:third-party-deep-import] client/capacitor/src/polyfills.ts:36
- Boundary violation [package:third-party-deep-import] client/web/app/main.cordova.ts:21
- Boundary violation [package:third-party-deep-import] client/web/ui_components/app-root.js:20
- Boundary violation [package:third-party-deep-import] client/web/ui_components/app-root.js:69
- Boundary violation [package:third-party-deep-import] client/web/ui_components/app-root.js:70
- Boundary violation [package:third-party-deep-import] server_manager/www/ui_components/app-root.ts:53
- Boundary violation [package:third-party-deep-import] server_manager/www/ui_components/app-root.ts:55
- Boundary violation [package:third-party-deep-import] server_manager/www/ui_components/cloud-install-styles.ts:17
- Boundary violation [package:third-party-deep-import] server_manager/www/ui_components/outline-about-dialog.ts:20
- Boundary violation [package:third-party-deep-import] server_manager/www/ui_components/outline-about-dialog.ts:21
- Boundary violation [package:third-party-deep-import] server_manager/www/ui_components/outline-cloud-instructions-view.ts:20
- Boundary violation [package:third-party-deep-import] server_manager/www/ui_components/outline-cloud-instructions-view.ts:21
- Boundary violation [package:third-party-deep-import] server_manager/www/ui_components/outline-do-oauth-step.ts:22
- Boundary violation [package:third-party-deep-import] server_manager/www/ui_components/outline-do-oauth-step.ts:23
- Boundary violation [package:third-party-deep-import] server_manager/www/ui_components/outline-feedback-dialog.ts:26
- Boundary violation [package:third-party-deep-import] server_manager/www/ui_components/outline-feedback-dialog.ts:27
- Boundary violation [package:third-party-deep-import] server_manager/www/ui_components/outline-help-bubble.ts:19
- Boundary violation [package:third-party-deep-import] server_manager/www/ui_components/outline-help-bubble.ts:20
- Boundary violation [package:third-party-deep-import] server_manager/www/ui_components/outline-iconset.ts:18
- Boundary violation [package:third-party-deep-import] server_manager/www/ui_components/outline-intro-step.ts:22
- Boundary violation [package:third-party-deep-import] server_manager/www/ui_components/outline-intro-step.ts:23
- Boundary violation [package:third-party-deep-import] server_manager/www/ui_components/outline-manual-server-entry.ts:31
- Boundary violation [package:third-party-deep-import] server_manager/www/ui_components/outline-manual-server-entry.ts:32
- Boundary violation [package:third-party-deep-import] server_manager/www/ui_components/outline-metrics-option-dialog.ts:21
- Boundary violation [package:third-party-deep-import] server_manager/www/ui_components/outline-metrics-option-dialog.ts:22
- No test reaches this file client/electron/index.ts:1
- No test reaches this file client/electron/go_vpn_tunnel.ts:1
- No test reaches this file REDACTED:1
- No test reaches this file client/electron/routing_service.ts:1
- No test reaches this file server_manager/electron/index.ts:1
- No test reaches this file client/capacitor/src/index.ts:1
- No test reaches this file server_manager/electron/digitalocean_oauth.ts:1
- No test reaches this file client/capacitor/build.action.mjs:1
- No test reaches this file client/src/cordova/build.action.mjs:1
- No test reaches this file client/src/cordova/setup.action.mjs:1
- No test reaches this file client/electron/go_plugin.ts:1
- No test reaches this file REDACTED:1
- No test reaches this file client/web/app/main.ts:1
- No test reaches this file client/electron/process.ts:1
- No test reaches this file client/web/app/main.electron.ts:1
- No test reaches this file client/web/app/main.cordova.ts:1
- No test reaches this file server_manager/www/main.ts:1
- No test reaches this file REDACTED:1
- No test reaches this file client/electron/vpn_service.ts:1
- No test reaches this file client/electron/build.action.mjs:1
- No test reaches this file client/capacitor/src/browser_method_channel.ts:1
- No test reaches this file server_manager/base.webpack.js:1
- No test reaches this file server_manager/www/manual_server.ts:1
- No test reaches this file REDACTED:1
- No test reaches this file client/capacitor/src/capacitor_url_interceptor.ts:1
- MethodTooLong: AppRoot.template server_manager/www/ui_components/app-root.ts:102
- MethodTooLong: AppRoot.template client/web/ui_components/app-root.js:81
- MethodTooLong: ServerView.template server_manager/www/ui_components/outline-server-view.ts:81
- MethodTooLong: ServerView.managementViewTemplate server_manager/www/ui_components/outline-server-view.ts:410
- MethodTooLong: AppRoot.properties client/web/ui_components/app-root.js:421
- MethodTooLong: App.constructor REDACTED:163
- MethodTooLong: AppRoot.expandedServersTemplate server_manager/www/ui_components/app-root.ts:507
- MethodTooLong: OutlineRegionPicker.styles server_manager/www/ui_components/outline-region-picker-step.ts:49
- MethodTooLong: App.constructor client/web/app/app.ts:95
- MethodTooLong: ServerMetricsBandwidthRow.render server_manager/www/views/server_view/server_metrics_row/bandwidth.ts:288
- ClassTooLong: App REDACTED:157
- ClassTooLong: AppRoot server_manager/www/ui_components/app-root.ts:101
- ClassTooLong: ServerView server_manager/www/ui_components/outline-server-view.ts:80
- ClassTooLong: AppRoot client/web/ui_components/app-root.js:77
- ClassTooLong: App client/web/app/app.ts:84
- ClassTooLong: OutlineService client/electron/windows/OutlineService/OutlineService/OutlineService.cs
- No assertions: throws on pin mismatch (remote) server_manager/electron/fetch.spec.ts:25
- No assertions: throws on pin mismatch (local) server_manager/electron/fetch.spec.ts:54
- No assertions: close can safely be called twice infrastructure/value_stream.spec.ts:48
- No assertions: the last update in a burst is received infrastructure/value_stream.spec.ts:78
- No assertions: add throws on invalid access keys client/web/app/outline_server_repository/outline_server_repository.spec.ts:162
- FileTooLong: REDACTED REDACTED
- FileTooLong: ui_components/app-root.ts server_manager/www/ui_components/app-root.ts
- FileTooLong: ui_components/outline-server-view.ts server_manager/www/ui_components/outline-server-view.ts
- FileTooLong: ui_components/app-root.js client/web/ui_components/app-root.js
- FileTooLong: app/app.ts client/web/app/app.ts
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Off the main sequence: OutlineError
- Off the main sequence: OutlineSentryLogger
- Off the main sequence: OutlineTunnel
- Off the main sequence: @outline/infrastructure
- TodoComment client/electron/windows/OutlineService/OutlineService/OutlineService.cs:393
- TodoComment client/electron/windows/OutlineService/OutlineService/OutlineService.cs:619
- TodoComment client/electron/windows/OutlineService/OutlineService/OutlineService.cs:957
- TooManyMethods: AppRoot server_manager/www/ui_components/app-root.ts:101
- TooManyMethods: App REDACTED:157
- TooManyMethods: App client/web/app/app.ts:84
- Change coupling: index.ts ↔ main.electron.ts client/electron/index.ts:1
- Change coupling: Package.swift ↔ PacketTunnelProvider.swift client/src/cordova/apple/OutlineAppleLib/Package.swift:1
- Change coupling: REDACTED ↔ index.ts client/web/app/app.ts:1
- Duplicated block (18 lines × 2 locations) server_manager/cloud/gcp_api.ts:362
- Duplicated block (18 lines × 2 locations) REDACTED:689
- Duplicated block (18 lines × 2 locations) server_manager/www/views/server_view/access_key_data_table/access_key_controls/index.ts:121
- Duplicated block with local edits (8 matched lines × 2 locations) client/capacitor/web_build.action.mjs:17
- Duplicated block with local edits (8 matched lines × 2 locations) server_manager/install_scripts/build_do_install_script_ts.node.js:15
- Duplicated block with local edits (8 matched lines × 2 locations) server_manager/www/shadowbox_server.ts:164
- Unused dependency 'chalk' REDACTED:41
- Unused dependency 'chalk' REDACTED:74
- Unused dependency 'chalk' infrastructure/package.json:19
- REDACTED
- REDACTED
- Edited copy of a member (5 corresponding lines) client/go/outline/configregistry/config_dial_endpoint.go:35
- Edited copy of a member (5 corresponding lines) REDACTED:43
- Low cohesion: AppRoot (LCOM4 12) server_manager/www/ui_components/app-root.ts:101
- Low cohesion: ServerView (LCOM4 10) server_manager/www/ui_components/outline-server-view.ts:80
- Duplicated block (11 lines × 2 locations) client/web/webpack_css_rtl_loader.cjs:18
- Duplicated block (11 lines × 2 locations) server_manager/www/digitalocean_server.ts:110
- Duplicated block (7 lines × 2 locations) client/web/views/root_view/connection_confirm_dialog/index.ts:25
- Duplicated block (7 lines × 2 locations) server_manager/www/ui_components/outline-share-dialog.ts:170
- Duplicated block (6 lines × 2 locations) client/capacitor/start.action.mjs:40
- Duplicated block (6 lines × 2 locations) client/web/views/servers_view/server_list_item/server_card/index.ts:36
- Unused dependency 'node-fetch' REDACTED:107
- Unused dependency 'node-fetch' infrastructure/package.json:20
- App.showLocalizedError (cyclomatic 25) client/web/app/app.ts:260
- configregistry.parseIPTableStreamDialer (cyclomatic 23) client/go/outline/configregistry/config_iptable.go:38
- platform_error.convertRawErrorObjectToError (cyclomatic 18) client/web/model/platform_error.ts:55
- VpnTunnelService.startTunnel (cyclomatic 16) client/src/cordova/android/OutlineAndroidLib/outline/src/main/java/org/outline/vpn/VpnTunnelService.java:210
- Dead code: MIB_IPFORWARDTABLE client/electron/windows/OutlineService/OutlineService/OutlineService.cs:141
- configregistry.parseIPTableStreamDialer (cognitive 43) client/go/outline/configregistry/config_iptable.go:38
- App.showLocalizedError (cognitive 27) client/web/app/app.ts:260
- VpnTunnelService.startTunnel (cognitive 23) client/src/cordova/android/OutlineAndroidLib/outline/src/main/java/org/outline/vpn/VpnTunnelService.java:210
- outline.doParseTunnelConfig (cognitive 22) client/go/outline/parse.go:78
- ClientConfig.new (cognitive 19) client/go/outline/client.go:113
- reporting.NewHTTPReporterConfigParser (cognitive 18) client/go/outline/reporting/config.go:49
- App.ensureActiveDigitalOceanAccount (cognitive 17) REDACTED:607
- TypeParser.Parse (cognitive 17) client/go/configyaml/parse.go:90
- platform_error.convertRawErrorObjectToError (cognitive 16) client/web/model/platform_error.ts:55
- index.main (cognitive 16) client/electron/index.ts:453
- OutlineSentryLogger.addVpnExtensionLogsToSentry (cognitive 16) client/src/cordova/apple/OutlineAppleLib/Sources/OutlineSentryLogger/OutlineSentryLogger.swift:67
- OutlineVpn.start (cognitive 16) client/src/cordova/apple/OutlineAppleLib/Sources/OutlineTunnel/OutlineVpn.swift:53
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- FunctionTooLong: legacy.getSharedComponents client/web/views/servers_view/server_list_item/server_card/legacy.ts:145
- Change-coupling hub: vpn.fake.ts → index.ts, main.electron.ts, index.ts client/web/app/outline_server_repository/vpn.fake.ts
- REDACTED
- Edited copy of a member (92 corresponding lines) client/capacitor/plugins/capacitor-plugin-outline/ios/Sources/CapacitorPluginOutline/CapacitorPluginOutline.swift:346
- Edited copy of a member (24 corresponding lines) client/capacitor/plugins/capacitor-plugin-outline/ios/Sources/CapacitorPluginOutline/CapacitorPluginOutline.swift:230
- Edited copy of a member (38 corresponding lines) client/capacitor/plugins/capacitor-plugin-outline/ios/Sources/CapacitorPluginOutline/CapacitorPluginOutline.swift:277
- Edited copy of a member (28 corresponding lines) client/go/outline/tun2socks/relay.go:34
- Edited copy of a member (18 corresponding lines) client/go/outline/configregistry/config_shadowsocks.go:102
- Edited copy of a member (20 corresponding lines) client/capacitor/plugins/capacitor-plugin-outline/android/src/main/java/org/outline/CapacitorPluginOutline.kt:158
- Edited copy of a member (11 corresponding lines) client/go/outline/dialer_linux.go:26
- Edited copy of a member (15 corresponding lines) client/capacitor/plugins/capacitor-plugin-outline/android/src/main/java/org/outline/CapacitorPluginOutline.kt:244
- Duplicated block (16 lines × 2) client/go/outline/configregistry/config_shadowsocks.go:68
- Duplicated block (10 lines × 2) client/go/outline/configregistry/config_shadowsocks.go:224
- Duplicated block (5 lines × 3) client/go/outline/configregistry/config_iptable.go:147
- Duplicated block (19–27 lines × 2) client/capacitor/plugins/capacitor-plugin-outline/ios/Sources/CapacitorPluginOutline/CapacitorPluginOutline.swift:364
- Duplicated block (16–17 lines × 2) client/capacitor/plugins/capacitor-plugin-outline/ios/Sources/CapacitorPluginOutline/CapacitorPluginOutline.swift:346
- Duplicated block (13 lines × 2) client/capacitor/plugins/capacitor-plugin-outline/ios/Sources/CapacitorPluginOutline/CapacitorPluginOutline.swift:238
- Unstable project CapacitorPluginOutline
- Coverage not measured — test suite did not build
- Coverage collected but not gated
- Duplication concentrated across 5 sibling directories (6 clone groups) client/capacitor/src/index.ts:165
- Duplicated block (35 lines × 2 locations) server_manager/www/digitalocean_server.ts:45
- Duplicated block with local edits (30 matched lines × 2 locations) server_manager/www/views/server_view/server_metrics_row/bandwidth.ts:288
- Duplicated block (26 lines × 2 locations) client/capacitor/src/index.ts:165
- Duplicated block with local edits (22 matched lines × 2 locations) client/capacitor/build.action.mjs:60
- Duplicated block (22 lines × 2 locations) REDACTED:733
- Duplicated block with local edits (21 matched lines × 2 locations) server_manager/www/cloud_accounts.ts:47
- Duplicated block (19 lines × 2 locations) REDACTED:1394
- Duplicated block (17 lines × 2 locations) client/src/cordova/setup.action.mjs:136
- Duplicated block with local edits (16 matched lines × 2 locations) server_manager/electron/digitalocean_oauth.ts:244
- Duplicated block (16 lines × 2 locations) REDACTED:1355
- Duplicated block with local edits (15 matched lines × 2 locations) client/capacitor/web_bundle.mjs:54
- Duplicated block (15 lines × 2 locations) server_manager/cloud/gcp_api.ts:310
- Duplicated block (13 lines × 2 locations) REDACTED:1103
- Duplicated block with local edits (13 matched lines × 2 locations) server_manager/www/manual_server.ts:43
- Duplicated block with local edits (12 matched lines × 2 locations) infrastructure/i18n.ts:61
- Duplicated block with local edits (11 matched lines × 2 locations) client/src/cordova/build.action.mjs:48
- Duplicated block (9 lines × 2 locations) client/web/app/app.ts:318
- Duplicated block with local edits (7 matched lines × 2 locations) client/electron/start.action.mjs:52
- Duplicated block (5 lines × 2 locations) server_manager/www/views/server_view/server_metrics_row/bandwidth.ts:37
- Complex function showLocalizedError (cyclomatic 25, cognitive 27) client/web/app/app.ts:260
- Complex function convertRawErrorObjectToError (cyclomatic 18, cognitive 16) client/web/model/platform_error.ts:55
- Complex function main (cyclomatic 14, cognitive 13) client/capacitor/build.action.mjs:37
- Complex function toErrorCode (cyclomatic 13, cognitive 12) client/web/model/errors.ts:175
- Complex function main (cyclomatic 13, cognitive 9) client/src/cordova/build.action.mjs:37
- Complex function deserializeError (cyclomatic 12, cognitive 13) client/web/model/platform_error.ts:243
- Complex function (anonymous) (cyclomatic 11, cognitive 10) client/capacitor/src/index.ts:210
- REDACTED: 1502 lines of code REDACTED:1
- server_manager/www/ui_components/app-root.ts: 1140 lines of code server_manager/www/ui_components/app-root.ts:1
- server_manager/www/ui_components/outline-server-view.ts: 881 lines of code server_manager/www/ui_components/outline-server-view.ts:1
- client/web/app/app.ts: 812 lines of code client/web/app/app.ts:1
- server_manager/cloud/gcp_api.ts: 794 lines of code server_manager/cloud/gcp_api.ts:1
- client/web/ui_components/app-root.js: 793 lines of code client/web/ui_components/app-root.js:1
- client/electron/index.ts: 562 lines of code client/electron/index.ts:1
- server_manager/www/ui_components/outline-server-settings.ts: 528 lines of code server_manager/www/ui_components/outline-server-settings.ts:1
- server_manager/www/ui_components/outline-manual-server-entry.ts: 522 lines of code server_manager/www/ui_components/outline-manual-server-entry.ts:1
- client/web/views/servers_view/server_list_item/server_card/index.ts: 455 lines of code client/web/views/servers_view/server_list_item/server_card/index.ts:1
- server_manager/www/ui_components/outline-intro-step.ts: 445 lines of code server_manager/www/ui_components/outline-intro-step.ts:1
- server_manager/www/outline-gcp-create-server-app.ts: 441 lines of code server_manager/www/outline-gcp-create-server-app.ts:1
- server_manager/www/views/server_view/server_metrics_row/bandwidth.ts: 439 lines of code server_manager/www/views/server_view/server_metrics_row/bandwidth.ts:1
- Dead file (~629 LoC) client/electron/index.ts
- Dead file (~360 LoC) REDACTED
- Dead file (~239 LoC) client/src/cordova/build.action.mjs
- Dead file (~199 LoC) client/src/cordova/setup.action.mjs
- Dead file (~195 LoC) client/electron/go_plugin.ts
- Dead file (~140 LoC) REDACTED
- Dead file (~135 LoC) client/electron/vpn_service.ts
- Dead file (~132 LoC) client/electron/build.action.mjs
- Dead file (~93 LoC) client/src/cordova/test.action.mjs
- Dead file (~87 LoC) client/electron/tunnel_store.ts
- Dead file (~81 LoC) client/electron/build_main.action.mjs
- Dead file (~78 LoC) client/electron/webpack_electron_main.mjs
- Dead file (~72 LoC) client/electron/hooks/after_pack.cjs
- Dead file (~59 LoC) client/electron/start.action.mjs
- Dead file (~45 LoC) client/electron/windows/sign_windows_executable.action.mjs
- Dead file (~44 LoC) client/electron/connectivity.ts
- Dead file (~39 LoC) client/go/build.action.mjs
- Dead file (~38 LoC) client/electron/windows/electron_builder_signing_plugin.cjs
- Unused dependency 'storybook-dark-mode' REDACTED:51
- Unused dependency '@material/mwc-formfield' REDACTED:11
- Unused dependency '@material/mwc-icon-button' REDACTED:12
- Unused dependency '@material/mwc-menu' REDACTED:13
- Unused dependency '@material/mwc-radio' REDACTED:14
- Unused dependency '@polymer/decorators' REDACTED:23
- Unused dependency '@polymer/font-roboto' REDACTED:24
- Unused dependency '@polymer/paper-behaviors' REDACTED:28
- Unused dependency '@polymer/paper-ripple' REDACTED:38
- Unused dependency '@polymer/paper-styles' REDACTED:39
- Unused dependency 'copy-dir' REDACTED:75
- Unused dependency 'cordova-android' REDACTED:77
- Unused dependency 'cordova-browser' REDACTED:78
- Unused dependency 'cordova-ios' REDACTED:79
- Unused dependency 'cordova-plugin-clipboard' REDACTED:81
- Unused dependency 'cordova-plugin-splashscreen' REDACTED:46
- Unused dependency 'cordova-plugin-statusbar' REDACTED:47
- Unused dependency 'cordova-webintent' REDACTED:83
- Unused dependency 'deepmerge' REDACTED:85
- Unused dependency 'esm' REDACTED:93
- Unused dependency 'i18n-strings-files' REDACTED:97
- Unused dependency 'istanbul' REDACTED:99
- Unused dependency 'node-gyp' REDACTED:108
- Unused dependency 'pretty-quick' REDACTED:113
- Unused dependency 'replace-in-file' REDACTED:116
- Unused dependency 'socks' REDACTED:54
- Unused dependency 'xmlbuilder2' REDACTED:128
- Unused dependency '@capacitor/ios' client/capacitor/package.json:36
- Unused dependency 'https-browserify' infrastructure/package.json:12
- NuGet dependencies are not locked REDACTED:3
- JavaScript dependencies are not locked client/capacitor/plugins/capacitor-plugin-outline/package.json:27
- Untrusted text written into markup unescaped server_manager/www/views/server_view/icon_tooltip/index.ts:76
Minor — 68 finding(s)
- redundant comment client/electron/index.ts:146
- redundant comment client/electron/windows/OutlineService/OutlineService/Program.cs:70
- redundant comment client/electron/windows/OutlineService/OutlineService/Properties/AssemblyInfo.cs:19
- redundant comment client/electron/windows/OutlineService/OutlineService/Properties/AssemblyInfo.cs:31
- redundant comment client/electron/windows/OutlineService/OutlineService/Properties/AssemblyInfo.cs:36
- redundant comment client/electron/windows/OutlineService/OutlineService/Properties/AssemblyInfo.cs:39
- redundant comment client/web/app/outline_server_repository/outline_server_repository.spec.ts:311
- redundant comment server_manager/model/server.ts:48
- redundant comment server_manager/model/server.ts:51
- redundant comment server_manager/model/server.ts:103
- redundant comment server_manager/model/server.ts:142
- redundant comment server_manager/www/app.spec.ts:284
- redundant comment server_manager/www/gcp_account.ts:146
- redundant comment server_manager/www/shadowbox_server.ts:106
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated predicate client/capacitor/build.action.mjs:68
- Duplicated predicate server_manager/www/digitalocean_server.ts:81
- Duplicated predicate client/capacitor/plugins/capacitor-plugin-outline/ios/Sources/CapacitorPluginOutline/CapacitorPluginOutline.swift:102
- Silent fallback default in catch client/capacitor/src/index.ts:56
- Silent fallback default in catch server_manager/www/shadowbox_server.ts:354
- Fat interface: Server (25 required operations) server_manager/model/server.ts:19
- Off-boarding risk: anonymized user #1
- Further sole-owners (lower concentration)
- Documentation: no build, run or usage example client/src/cordova/plugin/README.md:1
- No ADRs found client/electron/windows/OutlineService/OutlineService/OutlineService.csproj:8
- `handleOpenURL` spells `URL` where 45 names in the project spell it `Url` client/web/app/main.cordova.ts:151
- `messageID` spells `ID` where 166 names in the project spell it `Id` client/web/testing/localize.ts:22
- `establishVpnRequestJSON` spells `Vpn` where 15 names in the project spell it `VPN` client/go/outline/vpn_linux.go:32
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- README/code drift client/src/cordova/android/README.md:24
- Logging is not universal
- No dependency-update automation REDACTED:3
- No changelog
- Unused export 'toErrorCode' client/web/model/errors.ts:175
- Unused export 'AppearanceView' client/web/views/appearance_view/index.ts:30
- Unused export 'LicensesView' client/web/views/licenses_view/index.ts:25
- Unused export 'BasicAccessConfirmDialog' client/web/views/root_view/connection_confirm_dialog/index.ts:199
- Unused export 'ProxylessConfirmDialog' client/web/views/root_view/connection_confirm_dialog/index.ts:216
- Unused export 'SplitConfirmDialog' client/web/views/root_view/connection_confirm_dialog/index.ts:231
- Unused export 'DnsConfigDialog' client/web/views/root_view/dns_config_dialog/index.ts:40
- Unused export 'ErrorDetailsDialog' client/web/views/root_view/error_details_dialog/index.ts:18
- Unused export 'RootHeader' client/web/views/root_view/root_header/index.ts:19
- Unused export 'RootNavigation' client/web/views/root_view/root_navigation/index.ts:22
- Unused export 'ServerList' client/web/views/servers_view/index.ts:37
- Unused export 'ServerRowCard' client/web/views/servers_view/server_list_item/server_card/legacy.ts:277
- Unused export 'ServerHeroCard' client/web/views/servers_view/server_list_item/server_card/legacy.ts:338
- Unused export 'ServerProxylessInfoDialog' client/web/views/servers_view/server_list_item/server_card/server_info_dialog/index.ts:110
- Unused export 'ServerSplitTunnelingInfoDialog' client/web/views/servers_view/server_list_item/server_card/server_info_dialog/index.ts:120
- Unused export 'ServerCompleteProtectionInfoDialog' client/web/views/servers_view/server_list_item/server_card/server_info_dialog/index.ts:130
- Unused private field 'debugMode' client/web/app/app.ts:99
Minor — 1 finding(s)
- doc comments repeat the names server_manager/cloud/gcp_api.ts:111
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-89b54ec0782744c7b371c422f2393865/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=800" --report-format json --report-path /tmp/watchdog-gitleaks-89b54ec0782744c7b371c422f2393865/history-1.json --exit-code 0 --source . | 2 | artifacts/raw/gitleaks-history-1.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=1000 --max-count=883" --report-format json --report-path /tmp/watchdog-gitleaks-89b54ec0782744c7b371c422f2393865/history-2.json --exit-code 0 --source . | 2 | artifacts/raw/gitleaks-history-2.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-89b54ec0782744c7b371c422f2393865/tree.json --exit-code 0 --source . | 2 | 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 . | 11 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | nuget | — | nuget: not applicable — nuget: `dotnet list package --vulnerable` could not read this solution's dependency graph — it reported an error for at least one project and returned no package data at all (typically a REDACTED / non-PackageReference project, which the command cannot read). An unreadable dependency graph is not a clean one; migrate the project(s) to PackageReference to enable this scan | 0 | — |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 160 | artifacts/raw/trivy-fs.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. | 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 | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |