Executive summary
erebe/wstunnel falls short of our standard for production, in part because we found no access checks on the code's endpoints or handlers. It scores 53 out of 100 and is rated Adequate, and all 34 of its critical findings are security problems.
Security and Compliance, at 39, is the weakest lens and counts most in the score. The best first step is adding access checks, worth about 12 points. Recording design decisions comes next, worth about 4 points. Raising Security and Compliance to 70 would lift the score to about 64.
Sixteen pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Eleven passwords or keys in the code's history and three in the code are open to anyone who can read the repository, and two secrets can leak from the build pipeline. Pinning each tool to an exact version, replacing each exposed password or key and limiting each secret to its own step would close these risks. The pipeline step that installs packages without pinning their versions needs the packages it installs pinned to exact versions. The unsafe setting in infrastructure or container files needs changing to safe values.
The product code is 10,699 lines, about €10,000 to rebuild.
If Security and Compliance rose from 39 to 70, the lowest score rated Strong, the score would rise from 53 to about 64.
New since the last survey: 9 findings
- Dependency Hygiene · Yanked release: tokio
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Access Controls · No authorization wstunnel/src/tunnel/server/server.rs
Fixed since the last survey: 2 findings
- Supply-chain Provenance & Signing REDACTED
- Access Controls · No authorization wstunnel/src/protocols/http_proxy/server.rs
Rebuild cost: about €10,000 · Estimate
| Cost to rebuild | €3,500 to €17,000, for 58 to 182 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 53. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 10,699 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 protocols.http_proxy.server | 2 protocols.unix_sock.server | 3 somark | 4 tunnel.downstream_listeners | 5 tunnel.transport.io | 6 protocols.dns.resolver | 7 tunnel.downstream_listeners.http_proxy | 8 tunnel.downstream_listeners.unix_sock | 9 tunnel.transport.jwt | 10 tunnel.transport.types | 11 tunnel.transport.webtransport.endpoint | 12 tunnel.transport.webtransport.udp | 13 tunnel.transport.webtransport.utils | 14 protocols.tcp.server | 15 protocols.udp.server | 16 tunnel | 17 tunnel.client.config | 18 tunnel.transport.webtransport | 19 config | 20 protocols.socks5.tcp_server | 21 restrictions.types | 22 tunnel.client.connection_pool.manager | 23 tunnel.tls_reloader | 24 tunnel.upstream_connectors | 25 wstunnel | 26 restrictions.config_reloader | 27 tunnel.client.client | 28 tunnel.downstream_listeners.socks5 | 29 tunnel.server.server | 30 tunnel.server.utils | 31 tunnel.upstream_connectors.socks5 | 32 tunnel.upstream_connectors.tcp | 33 tunnel.upstream_connectors.udp | 34 protocols.tls.server | 35 tunnel.server.handler_http2 | 36 tunnel.server.handler_websocket | 37 tunnel.server.handler_webtransport | 38 tunnel.transport.http2 | 39 tunnel.transport.websocket | 40 tunnel.transport.webtransport.client |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 protocols.http_proxy.server | ||||||||||||||||||||||||||||||||||||||||
| 2 protocols.unix_sock.server | ||||||||||||||||||||||||||||||||||||||||
| 3 somark | ||||||||||||||||||||||||||||||||||||||||
| 4 tunnel.downstream_listeners | ||||||||||||||||||||||||||||||||||||||||
| 5 tunnel.transport.io | ||||||||||||||||||||||||||||||||||||||||
| 6 protocols.dns.resolver | 2 | |||||||||||||||||||||||||||||||||||||||
| 7 tunnel.downstream_listeners.http_proxy | 1 | |||||||||||||||||||||||||||||||||||||||
| 8 tunnel.downstream_listeners.unix_sock | 1 | |||||||||||||||||||||||||||||||||||||||
| 9 tunnel.transport.jwt | 3 | |||||||||||||||||||||||||||||||||||||||
| 10 tunnel.transport.types | 1 | |||||||||||||||||||||||||||||||||||||||
| 11 tunnel.transport.webtransport.endpoint | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 12 tunnel.transport.webtransport.udp | 2 | |||||||||||||||||||||||||||||||||||||||
| 13 tunnel.transport.webtransport.utils | 1 | |||||||||||||||||||||||||||||||||||||||
| 14 protocols.tcp.server | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 15 protocols.udp.server | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 16 tunnel | 1 | |||||||||||||||||||||||||||||||||||||||
| 17 tunnel.client.config | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 18 tunnel.transport.webtransport | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 19 config | 1 | |||||||||||||||||||||||||||||||||||||||
| 20 protocols.socks5.tcp_server | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 21 restrictions.types | 5 | |||||||||||||||||||||||||||||||||||||||
| 22 tunnel.client.connection_pool.manager | 1 | |||||||||||||||||||||||||||||||||||||||
| 23 tunnel.tls_reloader | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 24 tunnel.upstream_connectors | 1 | |||||||||||||||||||||||||||||||||||||||
| 25 wstunnel | 2 | |||||||||||||||||||||||||||||||||||||||
| 26 restrictions.config_reloader | 1 | |||||||||||||||||||||||||||||||||||||||
| 27 tunnel.client.client | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 28 tunnel.downstream_listeners.socks5 | 1 | |||||||||||||||||||||||||||||||||||||||
| 29 tunnel.server.server | 1 | 1 | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||
| 30 tunnel.server.utils | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 31 tunnel.upstream_connectors.socks5 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 32 tunnel.upstream_connectors.tcp | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 33 tunnel.upstream_connectors.udp | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 34 protocols.tls.server | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 35 tunnel.server.handler_http2 | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 36 tunnel.server.handler_websocket | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 37 tunnel.server.handler_webtransport | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 38 tunnel.transport.http2 | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 39 tunnel.transport.websocket | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 40 tunnel.transport.webtransport.client | 1 | 1 | 1 |
6→3 protocols.dns.resolver uses somark✕
- Connections
- 2 pairs of types, where a type in protocols.dns.resolver uses a type in somark.
- The types involved
wstunnel.protocols.dns.resolver.DnsResolver→wstunnel.somark.SoMarkwstunnel.protocols.dns.resolver.TokioRuntimeProviderWithSoMark→wstunnel.somark.SoMark
- Direction
- protocols.dns.resolver uses somark, so a change to somark can break protocols.dns.resolver, while a change to protocols.dns.resolver can't break somark.
- Position
- Below the diagonal: protocols.dns.resolver uses a module listed above it, which is the healthy direction.
7→1 tunnel.downstream_listeners.http_proxy uses protocols.http_proxy.server✕
- Connections
- 1 pair of types, where a type in tunnel.downstream_listeners.http_proxy uses a type in protocols.http_proxy.server.
- The types involved
wstunnel.tunnel.downstream_listeners.http_proxy.HttpProxyDownstreamListener→wstunnel.protocols.http_proxy.server.HttpProxyListener
- Direction
- tunnel.downstream_listeners.http_proxy uses protocols.http_proxy.server, so a change to protocols.http_proxy.server can break tunnel.downstream_listeners.http_proxy, while a change to tunnel.downstream_listeners.http_proxy can't break protocols.http_proxy.server.
- Position
- Below the diagonal: tunnel.downstream_listeners.http_proxy uses a module listed above it, which is the healthy direction.
8→2 tunnel.downstream_listeners.unix_sock uses protocols.unix_sock.server✕
- Connections
- 1 pair of types, where a type in tunnel.downstream_listeners.unix_sock uses a type in protocols.unix_sock.server.
- The types involved
wstunnel.tunnel.downstream_listeners.unix_sock.UnixDownstreamListener→wstunnel.protocols.unix_sock.server.UnixSockListener
- Direction
- tunnel.downstream_listeners.unix_sock uses protocols.unix_sock.server, so a change to protocols.unix_sock.server can break tunnel.downstream_listeners.unix_sock, while a change to tunnel.downstream_listeners.unix_sock can't break protocols.unix_sock.server.
- Position
- Below the diagonal: tunnel.downstream_listeners.unix_sock uses a module listed above it, which is the healthy direction.
9→16 tunnel.transport.jwt uses tunnel part of a loop✕
- Connections
- 3 pairs of types, where a type in tunnel.transport.jwt uses a type in tunnel.
- The types involved
wstunnel.tunnel.transport.jwt.JwtTunnelConfig→wstunnel.tunnel.LocalProtocolwstunnel.tunnel.transport.jwt.JwtTunnelConfig→wstunnel.tunnel.RemoteAddrwstunnel.tunnel.transport.jwt.jwt$module→wstunnel.tunnel.RemoteAddr
- Direction
- tunnel.transport.jwt uses tunnel, so a change to tunnel can break tunnel.transport.jwt, while a change to tunnel.transport.jwt can't break tunnel.
- 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.
10→17 tunnel.transport.types uses tunnel.client.config part of a loop✕
- Connections
- 1 pair of types, where a type in tunnel.transport.types uses a type in tunnel.client.config.
- The types involved
wstunnel.tunnel.transport.types.TransportAddr→wstunnel.tunnel.client.config.TlsClientConfig
- Direction
- tunnel.transport.types uses tunnel.client.config, so a change to tunnel.client.config can break tunnel.transport.types, while a change to tunnel.transport.types can't break tunnel.client.config.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→3 tunnel.transport.webtransport.endpoint uses somark✕
- Connections
- 1 pair of types, where a type in tunnel.transport.webtransport.endpoint uses a type in somark.
- The types involved
wstunnel.tunnel.transport.webtransport.endpoint.WebTransportEndpoint→wstunnel.somark.SoMark
- Direction
- tunnel.transport.webtransport.endpoint uses somark, so a change to somark can break tunnel.transport.webtransport.endpoint, while a change to tunnel.transport.webtransport.endpoint can't break somark.
- Position
- Below the diagonal: tunnel.transport.webtransport.endpoint uses a module listed above it, which is the healthy direction.
11→17 tunnel.transport.webtransport.endpoint uses tunnel.client.config part of a loop✕
- Connections
- 1 pair of types, where a type in tunnel.transport.webtransport.endpoint uses a type in tunnel.client.config.
- The types involved
wstunnel.tunnel.transport.webtransport.endpoint.WebTransportEndpoint→wstunnel.tunnel.client.config.ClientConfig
- Direction
- tunnel.transport.webtransport.endpoint uses tunnel.client.config, so a change to tunnel.client.config can break tunnel.transport.webtransport.endpoint, while a change to tunnel.transport.webtransport.endpoint can't break tunnel.client.config.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→5 tunnel.transport.webtransport.udp uses tunnel.transport.io✕
- Connections
- 2 pairs of types, where a type in tunnel.transport.webtransport.udp uses a type in tunnel.transport.io.
- The types involved
wstunnel.tunnel.transport.webtransport.udp.WebTransportUdpRead→wstunnel.tunnel.transport.io.TransportReadwstunnel.tunnel.transport.webtransport.udp.WebTransportUdpWrite→wstunnel.tunnel.transport.io.TransportWrite
- Direction
- tunnel.transport.webtransport.udp uses tunnel.transport.io, so a change to tunnel.transport.io can break tunnel.transport.webtransport.udp, while a change to tunnel.transport.webtransport.udp can't break tunnel.transport.io.
- Position
- Below the diagonal: tunnel.transport.webtransport.udp uses a module listed above it, which is the healthy direction.
13→3 tunnel.transport.webtransport.utils uses somark✕
- Connections
- 1 pair of types, where a type in tunnel.transport.webtransport.utils uses a type in somark.
- The types involved
wstunnel.tunnel.transport.webtransport.utils.utils$module→wstunnel.somark.SoMark
- Direction
- tunnel.transport.webtransport.utils uses somark, so a change to somark can break tunnel.transport.webtransport.utils, while a change to tunnel.transport.webtransport.utils can't break somark.
- Position
- Below the diagonal: tunnel.transport.webtransport.utils uses a module listed above it, which is the healthy direction.
14→3 protocols.tcp.server uses somark✕
- Connections
- 1 pair of types, where a type in protocols.tcp.server uses a type in somark.
- The types involved
wstunnel.protocols.tcp.server.server$module→wstunnel.somark.SoMark
- Direction
- protocols.tcp.server uses somark, so a change to somark can break protocols.tcp.server, while a change to protocols.tcp.server can't break somark.
- Position
- Below the diagonal: protocols.tcp.server uses a module listed above it, which is the healthy direction.
14→6 protocols.tcp.server uses protocols.dns.resolver✕
- Connections
- 1 pair of types, where a type in protocols.tcp.server uses a type in protocols.dns.resolver.
- The types involved
wstunnel.protocols.tcp.server.server$module→wstunnel.protocols.dns.resolver.DnsResolver
- Direction
- protocols.tcp.server uses protocols.dns.resolver, so a change to protocols.dns.resolver can break protocols.tcp.server, while a change to protocols.tcp.server can't break protocols.dns.resolver.
- Position
- Below the diagonal: protocols.tcp.server uses a module listed above it, which is the healthy direction.
15→3 protocols.udp.server uses somark✕
- Connections
- 1 pair of types, where a type in protocols.udp.server uses a type in somark.
- The types involved
wstunnel.protocols.udp.server.server$module→wstunnel.somark.SoMark
- Direction
- protocols.udp.server uses somark, so a change to somark can break protocols.udp.server, while a change to protocols.udp.server can't break somark.
- Position
- Below the diagonal: protocols.udp.server uses a module listed above it, which is the healthy direction.
15→4 protocols.udp.server uses tunnel.downstream_listeners✕
- Connections
- 1 pair of types, where a type in protocols.udp.server uses a type in tunnel.downstream_listeners.
- The types involved
wstunnel.protocols.udp.server.UdpStreamWriter→wstunnel.tunnel.downstream_listeners.DownstreamWrite
- Direction
- protocols.udp.server uses tunnel.downstream_listeners, so a change to tunnel.downstream_listeners can break protocols.udp.server, while a change to protocols.udp.server can't break tunnel.downstream_listeners.
- Position
- Below the diagonal: protocols.udp.server uses a module listed above it, which is the healthy direction.
15→6 protocols.udp.server uses protocols.dns.resolver✕
- Connections
- 1 pair of types, where a type in protocols.udp.server uses a type in protocols.dns.resolver.
- The types involved
wstunnel.protocols.udp.server.server$module→wstunnel.protocols.dns.resolver.DnsResolver
- Direction
- protocols.udp.server uses protocols.dns.resolver, so a change to protocols.dns.resolver can break protocols.udp.server, while a change to protocols.udp.server can't break protocols.dns.resolver.
- Position
- Below the diagonal: protocols.udp.server uses a module listed above it, which is the healthy direction.
16→9 tunnel uses tunnel.transport.jwt✕
- Connections
- 1 pair of types, where a type in tunnel uses a type in tunnel.transport.jwt.
- The types involved
wstunnel.tunnel.RemoteAddr→wstunnel.tunnel.transport.jwt.JwtTunnelConfig
- Direction
- tunnel uses tunnel.transport.jwt, so a change to tunnel.transport.jwt can break tunnel, while a change to tunnel can't break tunnel.transport.jwt.
- Position
- Below the diagonal: tunnel uses a module listed above it, which is the healthy direction.
17→3 tunnel.client.config uses somark✕
- Connections
- 1 pair of types, where a type in tunnel.client.config uses a type in somark.
- The types involved
wstunnel.tunnel.client.config.ClientConfig→wstunnel.somark.SoMark
- Direction
- tunnel.client.config uses somark, so a change to somark can break tunnel.client.config, while a change to tunnel.client.config can't break somark.
- Position
- Below the diagonal: tunnel.client.config uses a module listed above it, which is the healthy direction.
17→6 tunnel.client.config uses protocols.dns.resolver✕
- Connections
- 1 pair of types, where a type in tunnel.client.config uses a type in protocols.dns.resolver.
- The types involved
wstunnel.tunnel.client.config.ClientConfig→wstunnel.protocols.dns.resolver.DnsResolver
- Direction
- tunnel.client.config uses protocols.dns.resolver, so a change to protocols.dns.resolver can break tunnel.client.config, while a change to tunnel.client.config can't break protocols.dns.resolver.
- Position
- Below the diagonal: tunnel.client.config uses a module listed above it, which is the healthy direction.
17→10 tunnel.client.config uses tunnel.transport.types✕
- Connections
- 1 pair of types, where a type in tunnel.client.config uses a type in tunnel.transport.types.
- The types involved
wstunnel.tunnel.client.config.ClientConfig→wstunnel.tunnel.transport.types.TransportAddr
- Direction
- tunnel.client.config uses tunnel.transport.types, so a change to tunnel.transport.types can break tunnel.client.config, while a change to tunnel.client.config can't break tunnel.transport.types.
- Position
- Below the diagonal: tunnel.client.config uses a module listed above it, which is the healthy direction.
17→11 tunnel.client.config uses tunnel.transport.webtransport.endpoint✕
- Connections
- 1 pair of types, where a type in tunnel.client.config uses a type in tunnel.transport.webtransport.endpoint.
- The types involved
wstunnel.tunnel.client.config.ClientConfig→wstunnel.tunnel.transport.webtransport.endpoint.WebTransportEndpoint
- Direction
- tunnel.client.config uses tunnel.transport.webtransport.endpoint, so a change to tunnel.transport.webtransport.endpoint can break tunnel.client.config, while a change to tunnel.client.config can't break tunnel.transport.webtransport.endpoint.
- Position
- Below the diagonal: tunnel.client.config uses a module listed above it, which is the healthy direction.
18→5 tunnel.transport.webtransport uses tunnel.transport.io✕
- Connections
- 2 pairs of types, where a type in tunnel.transport.webtransport uses a type in tunnel.transport.io.
- The types involved
wstunnel.tunnel.transport.webtransport.WebTransportRead→wstunnel.tunnel.transport.io.TransportReadwstunnel.tunnel.transport.webtransport.WebTransportWrite→wstunnel.tunnel.transport.io.TransportWrite
- Direction
- tunnel.transport.webtransport uses tunnel.transport.io, so a change to tunnel.transport.io can break tunnel.transport.webtransport, while a change to tunnel.transport.webtransport can't break tunnel.transport.io.
- Position
- Below the diagonal: tunnel.transport.webtransport uses a module listed above it, which is the healthy direction.
18→12 tunnel.transport.webtransport uses tunnel.transport.webtransport.udp✕
- Connections
- 2 pairs of types, where a type in tunnel.transport.webtransport uses a type in tunnel.transport.webtransport.udp.
- The types involved
wstunnel.tunnel.transport.webtransport.WebTransportRead→wstunnel.tunnel.transport.webtransport.udp.WebTransportUdpReadwstunnel.tunnel.transport.webtransport.WebTransportWrite→wstunnel.tunnel.transport.webtransport.udp.WebTransportUdpWrite
- Direction
- tunnel.transport.webtransport uses tunnel.transport.webtransport.udp, so a change to tunnel.transport.webtransport.udp can break tunnel.transport.webtransport, while a change to tunnel.transport.webtransport can't break tunnel.transport.webtransport.udp.
- Position
- Below the diagonal: tunnel.transport.webtransport uses a module listed above it, which is the healthy direction.
19→16 config uses tunnel✕
- Connections
- 1 pair of types, where a type in config uses a type in tunnel.
- The types involved
wstunnel.config.LocalToRemote→wstunnel.tunnel.LocalProtocol
- Direction
- config uses tunnel, so a change to tunnel can break config, while a change to config can't break tunnel.
- Position
- Below the diagonal: config uses a module listed above it, which is the healthy direction.
20→4 protocols.socks5.tcp_server uses tunnel.downstream_listeners✕
- Connections
- 1 pair of types, where a type in protocols.socks5.tcp_server uses a type in tunnel.downstream_listeners.
- The types involved
wstunnel.protocols.socks5.tcp_server.Socks5WriteHalf→wstunnel.tunnel.downstream_listeners.DownstreamWrite
- Direction
- protocols.socks5.tcp_server uses tunnel.downstream_listeners, so a change to tunnel.downstream_listeners can break protocols.socks5.tcp_server, while a change to protocols.socks5.tcp_server can't break tunnel.downstream_listeners.
- Position
- Below the diagonal: protocols.socks5.tcp_server uses a module listed above it, which is the healthy direction.
20→16 protocols.socks5.tcp_server uses tunnel✕
- Connections
- 1 pair of types, where a type in protocols.socks5.tcp_server uses a type in tunnel.
- The types involved
wstunnel.protocols.socks5.tcp_server.Socks5Stream→wstunnel.tunnel.LocalProtocol
- Direction
- protocols.socks5.tcp_server uses tunnel, so a change to tunnel can break protocols.socks5.tcp_server, while a change to protocols.socks5.tcp_server can't break tunnel.
- Position
- Below the diagonal: protocols.socks5.tcp_server uses a module listed above it, which is the healthy direction.
21→16 restrictions.types uses tunnel✕
- Connections
- 5 pairs of types, where a type in restrictions.types uses a type in tunnel.
- The types involved
wstunnel.restrictions.types.AllowConfig→wstunnel.tunnel.RemoteAddrwstunnel.restrictions.types.AllowReverseTunnelConfig→wstunnel.tunnel.RemoteAddrwstunnel.restrictions.types.AllowTunnelConfig→wstunnel.tunnel.RemoteAddrwstunnel.restrictions.types.ReverseTunnelProtocol→wstunnel.tunnel.LocalProtocolwstunnel.restrictions.types.TunnelProtocol→wstunnel.tunnel.LocalProtocol
- Direction
- restrictions.types uses tunnel, so a change to tunnel can break restrictions.types, while a change to restrictions.types can't break tunnel.
- Position
- Below the diagonal: restrictions.types uses a module listed above it, which is the healthy direction.
22→17 tunnel.client.connection_pool.manager uses tunnel.client.config✕
- Connections
- 1 pair of types, where a type in tunnel.client.connection_pool.manager uses a type in tunnel.client.config.
- The types involved
wstunnel.tunnel.client.connection_pool.manager.L4StreamManager→wstunnel.tunnel.client.config.ClientConfig
- Direction
- tunnel.client.connection_pool.manager uses tunnel.client.config, so a change to tunnel.client.config can break tunnel.client.connection_pool.manager, while a change to tunnel.client.connection_pool.manager can't break tunnel.client.config.
- Position
- Below the diagonal: tunnel.client.connection_pool.manager uses a module listed above it, which is the healthy direction.
23→17 tunnel.tls_reloader uses tunnel.client.config✕
- Connections
- 2 pairs of types, where a type in tunnel.tls_reloader uses a type in tunnel.client.config.
- The types involved
wstunnel.tunnel.tls_reloader.TlsReloader→wstunnel.tunnel.client.config.ClientConfigwstunnel.tunnel.tls_reloader.TlsReloaderClientState→wstunnel.tunnel.client.config.ClientConfig
- Direction
- tunnel.tls_reloader uses tunnel.client.config, so a change to tunnel.client.config can break tunnel.tls_reloader, while a change to tunnel.tls_reloader can't break tunnel.client.config.
- Position
- Below the diagonal: tunnel.tls_reloader uses a module listed above it, which is the healthy direction.
23→29 tunnel.tls_reloader uses tunnel.server.server part of a loop✕
- Connections
- 2 pairs of types, where a type in tunnel.tls_reloader uses a type in tunnel.server.server.
- The types involved
wstunnel.tunnel.tls_reloader.TlsReloader→wstunnel.tunnel.server.server.ServerConfigwstunnel.tunnel.tls_reloader.TlsReloaderServerState→wstunnel.tunnel.server.server.ServerConfig
- Direction
- tunnel.tls_reloader uses tunnel.server.server, so a change to tunnel.server.server can break tunnel.tls_reloader, while a change to tunnel.tls_reloader can't break tunnel.server.server.
- 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.
24→16 tunnel.upstream_connectors uses tunnel✕
- Connections
- 1 pair of types, where a type in tunnel.upstream_connectors uses a type in tunnel.
- The types involved
wstunnel.tunnel.upstream_connectors.UpstreamConnector→wstunnel.tunnel.RemoteAddr
- Direction
- tunnel.upstream_connectors uses tunnel, so a change to tunnel can break tunnel.upstream_connectors, while a change to tunnel.upstream_connectors can't break tunnel.
- Position
- Below the diagonal: tunnel.upstream_connectors uses a module listed above it, which is the healthy direction.
25→19 wstunnel uses config✕
- Connections
- 2 pairs of types, where a type in wstunnel uses a type in config.
- The types involved
wstunnel.wstunnel$module→wstunnel.config.ClientCreationRequestwstunnel.wstunnel$module→wstunnel.config.ServerCreationRequest
- Direction
- wstunnel uses config, so a change to config can break wstunnel, while a change to wstunnel can't break config.
- Position
- Below the diagonal: wstunnel uses a module listed above it, which is the healthy direction.
26→21 restrictions.config_reloader uses restrictions.types✕
- Connections
- 1 pair of types, where a type in restrictions.config_reloader uses a type in restrictions.types.
- The types involved
wstunnel.restrictions.config_reloader.RestrictionsRulesReloader→wstunnel.restrictions.types.RestrictionsRules
- Direction
- restrictions.config_reloader uses restrictions.types, so a change to restrictions.types can break restrictions.config_reloader, while a change to restrictions.config_reloader can't break restrictions.types.
- Position
- Below the diagonal: restrictions.config_reloader uses a module listed above it, which is the healthy direction.
27→16 tunnel.client.client uses tunnel✕
- Connections
- 1 pair of types, where a type in tunnel.client.client uses a type in tunnel.
- The types involved
wstunnel.tunnel.client.client.Client→wstunnel.tunnel.RemoteAddr
- Direction
- tunnel.client.client uses tunnel, so a change to tunnel can break tunnel.client.client, while a change to tunnel.client.client can't break tunnel.
- Position
- Below the diagonal: tunnel.client.client uses a module listed above it, which is the healthy direction.
27→17 tunnel.client.client uses tunnel.client.config✕
- Connections
- 1 pair of types, where a type in tunnel.client.client uses a type in tunnel.client.config.
- The types involved
wstunnel.tunnel.client.client.Client→wstunnel.tunnel.client.config.ClientConfig
- Direction
- tunnel.client.client uses tunnel.client.config, so a change to tunnel.client.config can break tunnel.client.client, while a change to tunnel.client.client can't break tunnel.client.config.
- Position
- Below the diagonal: tunnel.client.client uses a module listed above it, which is the healthy direction.
27→23 tunnel.client.client uses tunnel.tls_reloader✕
- Connections
- 1 pair of types, where a type in tunnel.client.client uses a type in tunnel.tls_reloader.
- The types involved
wstunnel.tunnel.client.client.Client→wstunnel.tunnel.tls_reloader.TlsReloader
- Direction
- tunnel.client.client uses tunnel.tls_reloader, so a change to tunnel.tls_reloader can break tunnel.client.client, while a change to tunnel.client.client can't break tunnel.tls_reloader.
- Position
- Below the diagonal: tunnel.client.client uses a module listed above it, which is the healthy direction.
28→20 tunnel.downstream_listeners.socks5 uses protocols.socks5.tcp_server✕
- Connections
- 1 pair of types, where a type in tunnel.downstream_listeners.socks5 uses a type in protocols.socks5.tcp_server.
- The types involved
wstunnel.tunnel.downstream_listeners.socks5.Socks5DownstreamListener→wstunnel.protocols.socks5.tcp_server.Socks5Listener
- Direction
- tunnel.downstream_listeners.socks5 uses protocols.socks5.tcp_server, so a change to protocols.socks5.tcp_server can break tunnel.downstream_listeners.socks5, while a change to tunnel.downstream_listeners.socks5 can't break protocols.socks5.tcp_server.
- Position
- Below the diagonal: tunnel.downstream_listeners.socks5 uses a module listed above it, which is the healthy direction.
29→3 tunnel.server.server uses somark✕
- Connections
- 1 pair of types, where a type in tunnel.server.server uses a type in somark.
- The types involved
wstunnel.tunnel.server.server.ServerConfig→wstunnel.somark.SoMark
- Direction
- tunnel.server.server uses somark, so a change to somark can break tunnel.server.server, while a change to tunnel.server.server can't break somark.
- Position
- Below the diagonal: tunnel.server.server uses a module listed above it, which is the healthy direction.
29→6 tunnel.server.server uses protocols.dns.resolver✕
- Connections
- 1 pair of types, where a type in tunnel.server.server uses a type in protocols.dns.resolver.
- The types involved
wstunnel.tunnel.server.server.ServerConfig→wstunnel.protocols.dns.resolver.DnsResolver
- Direction
- tunnel.server.server uses protocols.dns.resolver, so a change to protocols.dns.resolver can break tunnel.server.server, while a change to tunnel.server.server can't break protocols.dns.resolver.
- Position
- Below the diagonal: tunnel.server.server uses a module listed above it, which is the healthy direction.
29→16 tunnel.server.server uses tunnel✕
- Connections
- 1 pair of types, where a type in tunnel.server.server uses a type in tunnel.
- The types involved
wstunnel.tunnel.server.server.Server→wstunnel.tunnel.RemoteAddr
- Direction
- tunnel.server.server uses tunnel, so a change to tunnel can break tunnel.server.server, while a change to tunnel.server.server can't break tunnel.
- Position
- Below the diagonal: tunnel.server.server uses a module listed above it, which is the healthy direction.
29→21 tunnel.server.server uses restrictions.types✕
- Connections
- 2 pairs of types, where a type in tunnel.server.server uses a type in restrictions.types.
- The types involved
wstunnel.tunnel.server.server.Server→wstunnel.restrictions.types.RestrictionConfigwstunnel.tunnel.server.server.Server→wstunnel.restrictions.types.RestrictionsRules
- Direction
- tunnel.server.server uses restrictions.types, so a change to restrictions.types can break tunnel.server.server, while a change to tunnel.server.server can't break restrictions.types.
- Position
- Below the diagonal: tunnel.server.server uses a module listed above it, which is the healthy direction.
29→23 tunnel.server.server uses tunnel.tls_reloader✕
- Connections
- 1 pair of types, where a type in tunnel.server.server uses a type in tunnel.tls_reloader.
- The types involved
wstunnel.tunnel.server.server.TlsContext→wstunnel.tunnel.tls_reloader.TlsReloader
- Direction
- tunnel.server.server uses tunnel.tls_reloader, so a change to tunnel.tls_reloader can break tunnel.server.server, while a change to tunnel.server.server can't break tunnel.tls_reloader.
- Position
- Below the diagonal: tunnel.server.server uses a module listed above it, which is the healthy direction.
30→16 tunnel.server.utils uses tunnel✕
- Connections
- 1 pair of types, where a type in tunnel.server.utils uses a type in tunnel.
- The types involved
wstunnel.tunnel.server.utils.utils$module→wstunnel.tunnel.RemoteAddr
- Direction
- tunnel.server.utils uses tunnel, so a change to tunnel can break tunnel.server.utils, while a change to tunnel.server.utils can't break tunnel.
- Position
- Below the diagonal: tunnel.server.utils uses a module listed above it, which is the healthy direction.
30→21 tunnel.server.utils uses restrictions.types✕
- Connections
- 2 pairs of types, where a type in tunnel.server.utils uses a type in restrictions.types.
- The types involved
wstunnel.tunnel.server.utils.utils$module→wstunnel.restrictions.types.RestrictionConfigwstunnel.tunnel.server.utils.utils$module→wstunnel.restrictions.types.RestrictionsRules
- Direction
- tunnel.server.utils uses restrictions.types, so a change to restrictions.types can break tunnel.server.utils, while a change to tunnel.server.utils can't break restrictions.types.
- Position
- Below the diagonal: tunnel.server.utils uses a module listed above it, which is the healthy direction.
31→3 tunnel.upstream_connectors.socks5 uses somark✕
- Connections
- 1 pair of types, where a type in tunnel.upstream_connectors.socks5 uses a type in somark.
- The types involved
wstunnel.tunnel.upstream_connectors.socks5.Socks5UpstreamConnector→wstunnel.somark.SoMark
- Direction
- tunnel.upstream_connectors.socks5 uses somark, so a change to somark can break tunnel.upstream_connectors.socks5, while a change to tunnel.upstream_connectors.socks5 can't break somark.
- Position
- Below the diagonal: tunnel.upstream_connectors.socks5 uses a module listed above it, which is the healthy direction.
31→6 tunnel.upstream_connectors.socks5 uses protocols.dns.resolver✕
- Connections
- 1 pair of types, where a type in tunnel.upstream_connectors.socks5 uses a type in protocols.dns.resolver.
- The types involved
wstunnel.tunnel.upstream_connectors.socks5.Socks5UpstreamConnector→wstunnel.protocols.dns.resolver.DnsResolver
- Direction
- tunnel.upstream_connectors.socks5 uses protocols.dns.resolver, so a change to protocols.dns.resolver can break tunnel.upstream_connectors.socks5, while a change to tunnel.upstream_connectors.socks5 can't break protocols.dns.resolver.
- Position
- Below the diagonal: tunnel.upstream_connectors.socks5 uses a module listed above it, which is the healthy direction.
31→16 tunnel.upstream_connectors.socks5 uses tunnel✕
- Connections
- 1 pair of types, where a type in tunnel.upstream_connectors.socks5 uses a type in tunnel.
- The types involved
wstunnel.tunnel.upstream_connectors.socks5.Socks5UpstreamConnector→wstunnel.tunnel.RemoteAddr
- Direction
- tunnel.upstream_connectors.socks5 uses tunnel, so a change to tunnel can break tunnel.upstream_connectors.socks5, while a change to tunnel.upstream_connectors.socks5 can't break tunnel.
- Position
- Below the diagonal: tunnel.upstream_connectors.socks5 uses a module listed above it, which is the healthy direction.
31→24 tunnel.upstream_connectors.socks5 uses tunnel.upstream_connectors✕
- Connections
- 1 pair of types, where a type in tunnel.upstream_connectors.socks5 uses a type in tunnel.upstream_connectors.
- The types involved
wstunnel.tunnel.upstream_connectors.socks5.Socks5UpstreamConnector→wstunnel.tunnel.upstream_connectors.UpstreamConnector
- Direction
- tunnel.upstream_connectors.socks5 uses tunnel.upstream_connectors, so a change to tunnel.upstream_connectors can break tunnel.upstream_connectors.socks5, while a change to tunnel.upstream_connectors.socks5 can't break tunnel.upstream_connectors.
- Position
- Below the diagonal: tunnel.upstream_connectors.socks5 uses a module listed above it, which is the healthy direction.
32→3 tunnel.upstream_connectors.tcp uses somark✕
- Connections
- 1 pair of types, where a type in tunnel.upstream_connectors.tcp uses a type in somark.
- The types involved
wstunnel.tunnel.upstream_connectors.tcp.TcpUpstreamConnector→wstunnel.somark.SoMark
- Direction
- tunnel.upstream_connectors.tcp uses somark, so a change to somark can break tunnel.upstream_connectors.tcp, while a change to tunnel.upstream_connectors.tcp can't break somark.
- Position
- Below the diagonal: tunnel.upstream_connectors.tcp uses a module listed above it, which is the healthy direction.
32→6 tunnel.upstream_connectors.tcp uses protocols.dns.resolver✕
- Connections
- 1 pair of types, where a type in tunnel.upstream_connectors.tcp uses a type in protocols.dns.resolver.
- The types involved
wstunnel.tunnel.upstream_connectors.tcp.TcpUpstreamConnector→wstunnel.protocols.dns.resolver.DnsResolver
- Direction
- tunnel.upstream_connectors.tcp uses protocols.dns.resolver, so a change to protocols.dns.resolver can break tunnel.upstream_connectors.tcp, while a change to tunnel.upstream_connectors.tcp can't break protocols.dns.resolver.
- Position
- Below the diagonal: tunnel.upstream_connectors.tcp uses a module listed above it, which is the healthy direction.
32→16 tunnel.upstream_connectors.tcp uses tunnel✕
- Connections
- 1 pair of types, where a type in tunnel.upstream_connectors.tcp uses a type in tunnel.
- The types involved
wstunnel.tunnel.upstream_connectors.tcp.TcpUpstreamConnector→wstunnel.tunnel.RemoteAddr
- Direction
- tunnel.upstream_connectors.tcp uses tunnel, so a change to tunnel can break tunnel.upstream_connectors.tcp, while a change to tunnel.upstream_connectors.tcp can't break tunnel.
- Position
- Below the diagonal: tunnel.upstream_connectors.tcp uses a module listed above it, which is the healthy direction.
32→24 tunnel.upstream_connectors.tcp uses tunnel.upstream_connectors✕
- Connections
- 1 pair of types, where a type in tunnel.upstream_connectors.tcp uses a type in tunnel.upstream_connectors.
- The types involved
wstunnel.tunnel.upstream_connectors.tcp.TcpUpstreamConnector→wstunnel.tunnel.upstream_connectors.UpstreamConnector
- Direction
- tunnel.upstream_connectors.tcp uses tunnel.upstream_connectors, so a change to tunnel.upstream_connectors can break tunnel.upstream_connectors.tcp, while a change to tunnel.upstream_connectors.tcp can't break tunnel.upstream_connectors.
- Position
- Below the diagonal: tunnel.upstream_connectors.tcp uses a module listed above it, which is the healthy direction.
33→3 tunnel.upstream_connectors.udp uses somark✕
- Connections
- 1 pair of types, where a type in tunnel.upstream_connectors.udp uses a type in somark.
- The types involved
wstunnel.tunnel.upstream_connectors.udp.UdpUpstreamConnector→wstunnel.somark.SoMark
- Direction
- tunnel.upstream_connectors.udp uses somark, so a change to somark can break tunnel.upstream_connectors.udp, while a change to tunnel.upstream_connectors.udp can't break somark.
- Position
- Below the diagonal: tunnel.upstream_connectors.udp uses a module listed above it, which is the healthy direction.
33→6 tunnel.upstream_connectors.udp uses protocols.dns.resolver✕
- Connections
- 1 pair of types, where a type in tunnel.upstream_connectors.udp uses a type in protocols.dns.resolver.
- The types involved
wstunnel.tunnel.upstream_connectors.udp.UdpUpstreamConnector→wstunnel.protocols.dns.resolver.DnsResolver
- Direction
- tunnel.upstream_connectors.udp uses protocols.dns.resolver, so a change to protocols.dns.resolver can break tunnel.upstream_connectors.udp, while a change to tunnel.upstream_connectors.udp can't break protocols.dns.resolver.
- Position
- Below the diagonal: tunnel.upstream_connectors.udp uses a module listed above it, which is the healthy direction.
33→16 tunnel.upstream_connectors.udp uses tunnel✕
- Connections
- 1 pair of types, where a type in tunnel.upstream_connectors.udp uses a type in tunnel.
- The types involved
wstunnel.tunnel.upstream_connectors.udp.UdpUpstreamConnector→wstunnel.tunnel.RemoteAddr
- Direction
- tunnel.upstream_connectors.udp uses tunnel, so a change to tunnel can break tunnel.upstream_connectors.udp, while a change to tunnel.upstream_connectors.udp can't break tunnel.
- Position
- Below the diagonal: tunnel.upstream_connectors.udp uses a module listed above it, which is the healthy direction.
33→24 tunnel.upstream_connectors.udp uses tunnel.upstream_connectors✕
- Connections
- 1 pair of types, where a type in tunnel.upstream_connectors.udp uses a type in tunnel.upstream_connectors.
- The types involved
wstunnel.tunnel.upstream_connectors.udp.UdpUpstreamConnector→wstunnel.tunnel.upstream_connectors.UpstreamConnector
- Direction
- tunnel.upstream_connectors.udp uses tunnel.upstream_connectors, so a change to tunnel.upstream_connectors can break tunnel.upstream_connectors.udp, while a change to tunnel.upstream_connectors.udp can't break tunnel.upstream_connectors.
- Position
- Below the diagonal: tunnel.upstream_connectors.udp uses a module listed above it, which is the healthy direction.
34→17 protocols.tls.server uses tunnel.client.config✕
- Connections
- 1 pair of types, where a type in protocols.tls.server uses a type in tunnel.client.config.
- The types involved
wstunnel.protocols.tls.server.server$module→wstunnel.tunnel.client.config.ClientConfig
- Direction
- protocols.tls.server uses tunnel.client.config, so a change to tunnel.client.config can break protocols.tls.server, while a change to protocols.tls.server can't break tunnel.client.config.
- Position
- Below the diagonal: protocols.tls.server uses a module listed above it, which is the healthy direction.
34→29 protocols.tls.server uses tunnel.server.server✕
- Connections
- 1 pair of types, where a type in protocols.tls.server uses a type in tunnel.server.server.
- The types involved
wstunnel.protocols.tls.server.server$module→wstunnel.tunnel.server.server.TlsServerConfig
- Direction
- protocols.tls.server uses tunnel.server.server, so a change to tunnel.server.server can break protocols.tls.server, while a change to protocols.tls.server can't break tunnel.server.server.
- Position
- Below the diagonal: protocols.tls.server uses a module listed above it, which is the healthy direction.
35→21 tunnel.server.handler_http2 uses restrictions.types✕
- Connections
- 1 pair of types, where a type in tunnel.server.handler_http2 uses a type in restrictions.types.
- The types involved
wstunnel.tunnel.server.handler_http2.handler_http2$module→wstunnel.restrictions.types.RestrictionsRules
- Direction
- tunnel.server.handler_http2 uses restrictions.types, so a change to restrictions.types can break tunnel.server.handler_http2, while a change to tunnel.server.handler_http2 can't break restrictions.types.
- Position
- Below the diagonal: tunnel.server.handler_http2 uses a module listed above it, which is the healthy direction.
35→29 tunnel.server.handler_http2 uses tunnel.server.server✕
- Connections
- 1 pair of types, where a type in tunnel.server.handler_http2 uses a type in tunnel.server.server.
- The types involved
wstunnel.tunnel.server.handler_http2.handler_http2$module→wstunnel.tunnel.server.server.Server
- Direction
- tunnel.server.handler_http2 uses tunnel.server.server, so a change to tunnel.server.server can break tunnel.server.handler_http2, while a change to tunnel.server.handler_http2 can't break tunnel.server.server.
- Position
- Below the diagonal: tunnel.server.handler_http2 uses a module listed above it, which is the healthy direction.
36→21 tunnel.server.handler_websocket uses restrictions.types✕
- Connections
- 1 pair of types, where a type in tunnel.server.handler_websocket uses a type in restrictions.types.
- The types involved
wstunnel.tunnel.server.handler_websocket.handler_websocket$module→wstunnel.restrictions.types.RestrictionsRules
- Direction
- tunnel.server.handler_websocket uses restrictions.types, so a change to restrictions.types can break tunnel.server.handler_websocket, while a change to tunnel.server.handler_websocket can't break restrictions.types.
- Position
- Below the diagonal: tunnel.server.handler_websocket uses a module listed above it, which is the healthy direction.
36→29 tunnel.server.handler_websocket uses tunnel.server.server✕
- Connections
- 1 pair of types, where a type in tunnel.server.handler_websocket uses a type in tunnel.server.server.
- The types involved
wstunnel.tunnel.server.handler_websocket.handler_websocket$module→wstunnel.tunnel.server.server.Server
- Direction
- tunnel.server.handler_websocket uses tunnel.server.server, so a change to tunnel.server.server can break tunnel.server.handler_websocket, while a change to tunnel.server.handler_websocket can't break tunnel.server.server.
- Position
- Below the diagonal: tunnel.server.handler_websocket uses a module listed above it, which is the healthy direction.
37→21 tunnel.server.handler_webtransport uses restrictions.types✕
- Connections
- 1 pair of types, where a type in tunnel.server.handler_webtransport uses a type in restrictions.types.
- The types involved
wstunnel.tunnel.server.handler_webtransport.handler_webtransport$module→wstunnel.restrictions.types.RestrictionsRules
- Direction
- tunnel.server.handler_webtransport uses restrictions.types, so a change to restrictions.types can break tunnel.server.handler_webtransport, while a change to tunnel.server.handler_webtransport can't break restrictions.types.
- Position
- Below the diagonal: tunnel.server.handler_webtransport uses a module listed above it, which is the healthy direction.
37→29 tunnel.server.handler_webtransport uses tunnel.server.server✕
- Connections
- 2 pairs of types, where a type in tunnel.server.handler_webtransport uses a type in tunnel.server.server.
- The types involved
wstunnel.tunnel.server.handler_webtransport.handler_webtransport$module→wstunnel.tunnel.server.server.Serverwstunnel.tunnel.server.handler_webtransport.handler_webtransport$module→wstunnel.tunnel.server.server.TlsServerConfig
- Direction
- tunnel.server.handler_webtransport uses tunnel.server.server, so a change to tunnel.server.server can break tunnel.server.handler_webtransport, while a change to tunnel.server.handler_webtransport can't break tunnel.server.server.
- Position
- Below the diagonal: tunnel.server.handler_webtransport uses a module listed above it, which is the healthy direction.
38→5 tunnel.transport.http2 uses tunnel.transport.io✕
- Connections
- 2 pairs of types, where a type in tunnel.transport.http2 uses a type in tunnel.transport.io.
- The types involved
wstunnel.tunnel.transport.http2.Http2TransportRead→wstunnel.tunnel.transport.io.TransportReadwstunnel.tunnel.transport.http2.Http2TransportWrite→wstunnel.tunnel.transport.io.TransportWrite
- Direction
- tunnel.transport.http2 uses tunnel.transport.io, so a change to tunnel.transport.io can break tunnel.transport.http2, while a change to tunnel.transport.http2 can't break tunnel.transport.io.
- Position
- Below the diagonal: tunnel.transport.http2 uses a module listed above it, which is the healthy direction.
38→16 tunnel.transport.http2 uses tunnel✕
- Connections
- 1 pair of types, where a type in tunnel.transport.http2 uses a type in tunnel.
- The types involved
wstunnel.tunnel.transport.http2.http2$module→wstunnel.tunnel.RemoteAddr
- Direction
- tunnel.transport.http2 uses tunnel, so a change to tunnel can break tunnel.transport.http2, while a change to tunnel.transport.http2 can't break tunnel.
- Position
- Below the diagonal: tunnel.transport.http2 uses a module listed above it, which is the healthy direction.
38→27 tunnel.transport.http2 uses tunnel.client.client✕
- Connections
- 1 pair of types, where a type in tunnel.transport.http2 uses a type in tunnel.client.client.
- The types involved
wstunnel.tunnel.transport.http2.http2$module→wstunnel.tunnel.client.client.Client
- Direction
- tunnel.transport.http2 uses tunnel.client.client, so a change to tunnel.client.client can break tunnel.transport.http2, while a change to tunnel.transport.http2 can't break tunnel.client.client.
- Position
- Below the diagonal: tunnel.transport.http2 uses a module listed above it, which is the healthy direction.
39→5 tunnel.transport.websocket uses tunnel.transport.io✕
- Connections
- 2 pairs of types, where a type in tunnel.transport.websocket uses a type in tunnel.transport.io.
- The types involved
wstunnel.tunnel.transport.websocket.WebsocketTransportRead→wstunnel.tunnel.transport.io.TransportReadwstunnel.tunnel.transport.websocket.WebsocketTransportWrite→wstunnel.tunnel.transport.io.TransportWrite
- Direction
- tunnel.transport.websocket uses tunnel.transport.io, so a change to tunnel.transport.io can break tunnel.transport.websocket, while a change to tunnel.transport.websocket can't break tunnel.transport.io.
- Position
- Below the diagonal: tunnel.transport.websocket uses a module listed above it, which is the healthy direction.
39→16 tunnel.transport.websocket uses tunnel✕
- Connections
- 1 pair of types, where a type in tunnel.transport.websocket uses a type in tunnel.
- The types involved
wstunnel.tunnel.transport.websocket.websocket$module→wstunnel.tunnel.RemoteAddr
- Direction
- tunnel.transport.websocket uses tunnel, so a change to tunnel can break tunnel.transport.websocket, while a change to tunnel.transport.websocket can't break tunnel.
- Position
- Below the diagonal: tunnel.transport.websocket uses a module listed above it, which is the healthy direction.
39→27 tunnel.transport.websocket uses tunnel.client.client✕
- Connections
- 1 pair of types, where a type in tunnel.transport.websocket uses a type in tunnel.client.client.
- The types involved
wstunnel.tunnel.transport.websocket.websocket$module→wstunnel.tunnel.client.client.Client
- Direction
- tunnel.transport.websocket uses tunnel.client.client, so a change to tunnel.client.client can break tunnel.transport.websocket, while a change to tunnel.transport.websocket can't break tunnel.client.client.
- Position
- Below the diagonal: tunnel.transport.websocket uses a module listed above it, which is the healthy direction.
40→16 tunnel.transport.webtransport.client uses tunnel✕
- Connections
- 1 pair of types, where a type in tunnel.transport.webtransport.client uses a type in tunnel.
- The types involved
wstunnel.tunnel.transport.webtransport.client.client$module→wstunnel.tunnel.RemoteAddr
- Direction
- tunnel.transport.webtransport.client uses tunnel, so a change to tunnel can break tunnel.transport.webtransport.client, while a change to tunnel.transport.webtransport.client can't break tunnel.
- Position
- Below the diagonal: tunnel.transport.webtransport.client uses a module listed above it, which is the healthy direction.
40→17 tunnel.transport.webtransport.client uses tunnel.client.config✕
- Connections
- 1 pair of types, where a type in tunnel.transport.webtransport.client uses a type in tunnel.client.config.
- The types involved
wstunnel.tunnel.transport.webtransport.client.client$module→wstunnel.tunnel.client.config.ClientConfig
- Direction
- tunnel.transport.webtransport.client uses tunnel.client.config, so a change to tunnel.client.config can break tunnel.transport.webtransport.client, while a change to tunnel.transport.webtransport.client can't break tunnel.client.config.
- Position
- Below the diagonal: tunnel.transport.webtransport.client uses a module listed above it, which is the healthy direction.
40→27 tunnel.transport.webtransport.client uses tunnel.client.client✕
- Connections
- 1 pair of types, where a type in tunnel.transport.webtransport.client uses a type in tunnel.client.client.
- The types involved
wstunnel.tunnel.transport.webtransport.client.client$module→wstunnel.tunnel.client.client.Client
- Direction
- tunnel.transport.webtransport.client uses tunnel.client.client, so a change to tunnel.client.client can break tunnel.transport.webtransport.client, while a change to tunnel.transport.webtransport.client can't break tunnel.client.client.
- Position
- Below the diagonal: tunnel.transport.webtransport.client uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 25 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 16 | Medium |
| A07:2025 — Authentication Failures | 15 | High / Critical |
| A02:2025 — Security Misconfiguration | 6 | High / Critical |
Roadmap
First, secure the application by implementing a global authentication guard with explicit public opt-outs and defining clear role-based permissions. Next, immediately address all secret management issues by removing leaked credentials from the codebase and purging sensitive keys like REDACTED from version history. Finally, establish a formal process for documenting significant design decisions by creating structured ADRs in a dedicated folder to ensure architectural clarity and traceability.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Protect endpoints by default-deny: a global authentication guard or middleware with explicit public opt-outs, or a guard on every route, plus named role/permission rules for what an authenticated caller may do. | +11.6 pts | Medium | Access Controls |
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +3.8 pts | Low | ADR Quality |
| Resolve the 3 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED, REDACTED, REDACTED. | +3.2 pts | Low | REDACTED Scanning |
| Resolve the 11 REDACTED finding(s) in Secrets (history) — start with REDACTED (2), REDACTED (2), REDACTED (2). | +6.1 pts | Medium | Secrets (history) |
| Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. | +1.9 pts | Low | Supply-chain Provenance & Signing |
| 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. | +3.3 pts | Medium | Architecture documentation |
| Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. | +1.3 pts | Low | Static Analysis (SAST) |
| Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. | +1.3 pts | Low | Static Analysis (SAST) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.6 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 4.4 | Mixed | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 4.4 | Mixed | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 4.4 | Mixed | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 5.8 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 5.8 | Mixed | Dependency Vulnerabilities: Medium CVE: REDACTED |
| wstunnel/src/protocols/socks5/tcp_server.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| wstunnel/src/tunnel/server/server.rs | 7.0 | Mixed | Cyclomatic Complexity: Server::serve (cyclomatic 18) |
| wstunnel/src/lib.rs | 7.1 | Mixed | Cyclomatic Complexity: wstunnel::create_client_tunnels (cyclomatic 37) |
| wstunnel/src/protocols/socks5/udp_server.rs | 7.2 | Mixed | Code Duplication: Edited copy of a member (42 corresponding lines) |
| REDACTED | 7.2 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 7.2 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 7.2 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 7.2 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 7.2 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 7.2 | Mixed | Secrets (history): REDACTED: REDACTED |
| wstunnel/src/protocols/tcp/server.rs | 7.4 | Mixed | Code Duplication: Duplicated block (14 lines × 2) |
| wstunnel/src/tunnel/downstream_listeners/tcp.rs | 7.8 | Mixed | Code Duplication: Duplicated block (14 lines × 2) |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 53 of 53 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
What we checked — 53 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, 135 of 153 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Watchdog duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
| LLM (sampled · advisory) | Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement | — | ◐ LLM · sampled · advisory |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.rs) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage read, produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (34 contributor(s) across 922 commit(s) sampled, automation and bot accounts excluded). One of them holds 94% of the history; the other 33 hold 0.2% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D24 Comment Value — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D27 Navigability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- D44 Platform End-of-Life — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a REDACTED) is simply not read here yet.
- AX6 Interface segregation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AXR1 Runtime accessibility — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via REDACTED (REDACTED). docker build failed (exit 1) — 6 | 7 | RUN rustup component add rustfmt clippy && apt-get update && apt-get install cmake libclang-dev -y -------------------- ERROR: failed to solve: rust:1.97-trixie: failed to resolve source metadata for docker.io/library/rust:1.97-trixie: failed to do request: Head "https://registry-1.docker.io/v2/library/rust/manifests/1.97-trixie": Forbidden; runtime evidence skipped.
- GD1 Unfinished & placeholder code — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Go, Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's Go, Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- X12 Unreachable branch — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X13 Undrained process stream — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X16 Unfloored truncation loop — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X17 Uncapped recursion over a caller-supplied document — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X18 Disposal-pattern correctness — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X19 Unrestored process-global state — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X22 Contradicted release guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Java, TypeScript/JavaScript, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded, and this repository's Go, Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X23 Unguarded diagnostic materialisation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X24 Document value interpolated into markup unescaped — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X25 Inert configuration knob — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart and Ruby source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart or Ruby was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X4 Structured logging — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 82 further occurrence(s) are not listed individually; the score already reflects all 122.
- X5 Nullable reference types — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax and MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, and Kotlin source only, and no C# was loaded, no TypeScript was found, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D11 Test Reliability: Flakiness is inferred from history/markers — Watchdog runs the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 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.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- 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: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
4 function(s) exceeded the cyclomatic complexity threshold of 15; the worst was wstunnel::create_client_tunnels at 37.
What to do
- Bring the 4 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with wstunnel::create_client_tunnels (cyclomatic 37), wstunnel::protocols::socks5::tcp_server::run_server (cyclomatic 21), Server::serve (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 8.7 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
5 function(s) exceeded the cognitive complexity threshold of 15; the worst was wstunnel::create_client_tunnels at 48.
What to do
- Bring the 5 bodies over 15 down to 15 or less in Cognitive Complexity — start with wstunnel::create_client_tunnels (cognitive 48), Server::serve (cognitive 41), wstunnel::protocols::socks5::tcp_server::run_server (cognitive 35). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 5 together lifts Cognitive Complexity from 8.4 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
4 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 2 FunctionTooLong finding(s) in God Classes — start with lib.rs (2). — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 MethodTooLong finding(s) in God Classes — start with server.rs (2). — One of this dimension's main actionable groups (2 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
17 duplicated block group(s) detected. One further row reports members as variants of one another; it aggregates block groups already counted above and is not itself counted.
What to do
- Resolve the 3 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with udp_server.rs, server.rs, types.rs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 Duplicated block (14 lines × 2) finding(s) in Code Duplication — start with server.rs, tcp.rs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with server.rs, websocket.rs. — One of this dimension's main actionable groups (2 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
2 production modules (Cargo), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 1 module(s) off the main sequence.
What to do
- Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
1 of 24 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with l4_stream.rs. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D9 · Test Distribution
30 test methods: 30 unit, 0 integration, 0 BDD, 0 e2e. The Rust suite contributes 30 `#[test]` function(s) across 8 file(s) declaring at least one; its unit/integration split is Cargo's own — 0 of those file(s) are integration-test targets under a crate's tests/ directory, and the rest are #[test] functions compiled into the crate they test.
D11 · Test Reliability
0 flaky across 1 measured tier(s). Rust (repository root, 8 test files): measured (0 flaky).
D12 · Dependency Hygiene
3 outdated, 1 yanked direct Cargo dependencies. Only DIRECT edges are graded: a transitive crate cannot be moved past what its parent's requirement admits, so reporting one would be advice its owner cannot take. A newer release is reported only where this repository's OWN requirement already admits it, so the remedy is `cargo update` and never a manifest edit — which means a release outside the declared range is deliberately NOT charged, because a written-down constraint is a decision rather than a defect. Note that a bare requirement is a CARET, and for a 0.x crate its ceiling is the minor. Whether any crate is UNMAINTAINED is not graded — crates.io publishes no maintenance status, and release age does not stand in for one. Known CVEs in this dependency graph are D30's question, read from REDACTED there.
What to do
- Resolve the 1 Yanked release finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D13 · REDACTED Scanning
3 secret(s) detected.
What to do
- Resolve the 3 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 issue-level).
- Enforce REDACTED Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D14 · License Compliance
0 of 388 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository's REDACTED closed over its manifests' `[dependencies]` and `[build-dependencies]`. Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository.
D15 · Churn × Complexity Hotspots
Top hotspots: wstunnel/src/lib.rs (5×37=185); wstunnel/src/protocols/socks5/tcp_server.rs (6×21=126); wstunnel/src/tunnel/server/server.rs (5×18=90)
What to do
- Resolve the 3 Hotspot finding(s) in Churn × Complexity Hotspots — start with lib.rs, tcp_server.rs, server.rs. — One of this dimension's main actionable groups (3 warning-level).
D17 · Explicit Debt
2 deducted task-comment markers across 10699 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 2 TodoComment finding(s) in Explicit Debt — start with utils.rs, tcp_server.rs. — One of this dimension's main actionable groups (2 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 3 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
1 of 3 build units (Cargo) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
11 finding(s): 0 critical, 11 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 11 REDACTED finding(s) in Secrets (history) — start with REDACTED (2), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (11 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)
25 finding(s): 0 critical, 19 high, 6 medium, 0 low. 16 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. Separately, one or more rules could not re-parse an embedded snippet in 1 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 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 16 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (16 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
9 finding(s): 0 critical, 0 high, 9 medium, 0 low.
What to do
- Resolve the 4 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (4). — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 3 Medium advisory (unmaintained) finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 Medium vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
D31 · IaC & Container Security
6 finding(s): 0 critical, 1 high, 4 medium, 1 low.
What to do
- Resolve the 1 High IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 4 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (4). — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 1 Low IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 41 of the 70 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D37 · Vulnerability-disclosure Policy
A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
Frontend & cross-cutting dimensions
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX4 · Dependency direction
AX9 · CQS / query purity
C2 · Access Controls
- This repository serves requests — a server (.serve_connection) (wstunnel/src/tunnel/server/server.rs:515) — and no route guard, auth-gate middleware, global guard or imperative check that refuses a caller (401/403, an Unauthorized/Forbidden error) was found: its endpoints may be unprotected. — wstunnel/src/tunnel/server/server.rs:515
What to do
- Protect endpoints by default-deny: a global authentication guard or middleware with explicit public opt-outs, or a guard on every route, plus named role/permission rules for what an authenticated caller may do.
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Add a README to the 2 of 2 project(s) that lack one — worth up to 2 pts.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
- Only 2/3 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `.`.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
- Consider OpenTelemetry tracing/metrics (opentelemetry with tracing-opentelemetry) and a health-check endpoint (a /health route on your axum/actix router) for operability.
P3 · Security & performance tooling
What to do
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
What to do
- Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
P6 · Release Hygiene
PF3 · Async & latency hygiene
S1 · Web-Security Posture
- None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is set on a response this repository's Rust server sends — defense in depth, even when a proxy could set them. (−2.0 on this card.) The server: `.serve_connection(` (wstunnel/src/tunnel/server/server.rs:515).
What to do
- Set security response headers on what the server sends — actix-web's `DefaultHeaders::new().add((header::X_CONTENT_TYPE_OPTIONS, "nosniff"))`, tower-http's `SetResponseHeaderLayer::overriding(…)` on an axum router, or keep Rocket's default `Shield` — with `Content-Security-Policy`, `X-Content-Type-Options` and a frame policy on every response.
X1 · Async correctness
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X21 · Side-effecting pattern guard
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
X30 · Support guard that admits what it rejects
X4 · Structured logging
- `warn!` at line 91 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — wstunnel-cli/src/main.rs:91
- `info!` at line 232 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — wstunnel/src/lib.rs:232
- `error!` at line 276 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — wstunnel/src/lib.rs:276
- `error!` at line 299 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — wstunnel/src/lib.rs:299
- `error!` at line 318 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — wstunnel/src/lib.rs:318
- `error!` at line 342 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — wstunnel/src/lib.rs:342
- `info!` at line 348 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — wstunnel/src/lib.rs:348
- `error!` at line 366 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — wstunnel/src/lib.rs:366
- `error!` at line 391 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — wstunnel/src/lib.rs:391
- `error!` at line 402 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — wstunnel/src/lib.rs:402
- `error!` at line 412 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — wstunnel/src/lib.rs:412
- `error!` at line 427 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — wstunnel/src/lib.rs:427
- `error!` at line 439 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — wstunnel/src/lib.rs:439
- `error!` at line 447 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — wstunnel/src/lib.rs:447
- `error!` at line 461 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — wstunnel/src/lib.rs:461
- `error!` at line 469 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — wstunnel/src/lib.rs:469
- `info!` at line 588 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — wstunnel/src/lib.rs:588
- `warn!` at line 63 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — wstunnel/src/tunnel/ca_reloader.rs:63
- `warn!` at line 67 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — wstunnel/src/tunnel/ca_reloader.rs:67
- `warn!` at line 71 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — wstunnel/src/tunnel/tls_reloader.rs:71
- `warn!` at line 76 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — wstunnel/src/tunnel/tls_reloader.rs:76
- `warn!` at line 261 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — wstunnel/src/tunnel/tls_reloader.rs:261
- `error!` at line 269 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — wstunnel/src/tunnel/tls_reloader.rs:269
- `error!` at line 301 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — wstunnel/src/tunnel/tls_reloader.rs:301
- `error!` at line 334 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — wstunnel/src/tunnel/tls_reloader.rs:334
- `warn!` at line 162 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — wstunnel/src/tunnel/transport/io.rs:162
- `warn!` at line 183 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — wstunnel/src/tunnel/transport/io.rs:183
- `warn!` at line 190 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — wstunnel/src/tunnel/transport/io.rs:190
- `debug!` at line 222 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — wstunnel/src/tunnel/transport/io.rs:222
- `error!` at line 223 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — wstunnel/src/tunnel/transport/io.rs:223
- `error!` at line 29 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — wstunnel/src/tunnel/transport/mod.rs:29
- `trace!` at line 92 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — wstunnel/src/tunnel/transport/websocket.rs:92
- `trace!` at line 201 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — wstunnel/src/tunnel/transport/websocket.rs:201
- `warn!` at line 26 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — wstunnel/src/tunnel/server/handler_websocket.rs:26
- `warn!` at line 42 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — wstunnel/src/tunnel/server/handler_websocket.rs:42
- `error!` at line 54 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — wstunnel/src/tunnel/server/handler_websocket.rs:54
- `error!` at line 59 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — wstunnel/src/tunnel/server/handler_websocket.rs:59
- `info!` at line 47 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — wstunnel/src/tunnel/server/handler_webtransport.rs:47
- `error!` at line 55 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — wstunnel/src/tunnel/server/handler_webtransport.rs:55
- `warn!` at line 73 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — wstunnel/src/tunnel/server/handler_webtransport.rs:73
What to do
- Interpolated log message defeats structured logging
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 71% | Adequate — gated by X4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 88% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 59% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 61% | Adequate — gated by D13 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 39% | Weak — gated by D28, D36, C2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 1 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 65 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: this repository's Go imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one.
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No Go request handler (a net/http, Gin, Echo, Fiber or fasthttp handler, or a gRPC service method) is declared as a method or function, and no handler function literal writes a value captured from outside it, so no state is shared between request goroutines. Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — docker build failed (exit 1) — 6 | 7 | RUN rustup component add rustfmt clippy && apt-get update && apt-get install cmake libclang-dev -y -------------------- ERROR: failed to solve: rust:1.97-trixie: failed to resolve source metadata for docker.io/library/rust:1.97-trixie: failed to do request: Head "https://registry-1.docker.io/v2/library/rust/manifests/1.97-trixie": Forbidden; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no data at rest for these controls to protect.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~0 lines of test source are present (.rs) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — Naming consistency is measured on C# only; Go, Rust not measured.
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed Rust surface was not measured.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ projects each declaring an entity of their own. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C# and Visual Basic comments only — this repository's production source is .go, .rs, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.rs), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- 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.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — applicable but not scored (1 of 2 signals for this style — below the bar we score at): 1 value object(s)
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the Go, Rust source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `#[bench]`, criterion's `bench_function`/`bench_with_input`, `#[divan::bench]` or `#[library_benchmark]` in any `.rs` file, or criterion, divan, iai or a `[[bench]]` target in a Cargo.toml, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not applicable: allocation awareness is rated where code engineers for it — at least 400 production lines that ship benchmarks or already use allocation-aware idioms (8 or more). This repository's Go code has 3 production line(s), 0 such use(s) and no benchmarks, so there is no allocation work to rate. The card is reward-only: its absence costs nothing.
- X12 Unreachable branch — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X13 Undrained process stream — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X16 Unfloored truncation loop — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X17 Uncapped recursion over a caller-supplied document — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X18 Disposal-pattern correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X19 Unrestored process-global state — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X2 Cancellation propagation — no C# was loaded; this repository's Rust was read, and no request in it can be cancelled by a caller — a Rust request takes no token: a future is cancelled by dropping it, from outside the call (select!, a timeout, an aborted task), and reqwest, hyper and tonic take none
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X22 Contradicted release guard — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X23 Unguarded diagnostic materialisation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X24 Document value interpolated into markup unescaped — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X25 Inert configuration knob — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 34 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
Serious — 62 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Hotspot: wstunnel/src/lib.rs wstunnel/src/lib.rs:237
- Hotspot: wstunnel/src/protocols/socks5/tcp_server.rs wstunnel/src/protocols/socks5/tcp_server.rs:150
- Hotspot: wstunnel/src/tunnel/server/server.rs wstunnel/src/tunnel/server/server.rs:353
- wstunnel::create_client_tunnels (cognitive 48) wstunnel/src/lib.rs:237
- wstunnel::protocols::socks5::tcp_server::run_server (cognitive 35) wstunnel/src/protocols/socks5/tcp_server.rs:150
- wstunnel::create_client (cognitive 21) wstunnel/src/lib.rs:58
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (8 lines × 2) wstunnel/src/protocols/socks5/udp_server.rs:182
- Duplicated block (8 lines × 2) wstunnel/src/protocols/tcp/server.rs:65
- Duplicated block (8 lines × 2) wstunnel/src/tunnel/transport/types.rs:150
- wstunnel::create_client_tunnels (cyclomatic 37) wstunnel/src/lib.rs:237
- wstunnel::protocols::socks5::tcp_server::run_server (cyclomatic 21) wstunnel/src/protocols/socks5/tcp_server.rs:150
- Server::serve (cyclomatic 18) wstunnel/src/tunnel/server/server.rs:353
- Server::exec_tunnel (cyclomatic 16) wstunnel/src/tunnel/server/server.rs:163
- TodoComment wstunnel/src/tunnel/transport/webtransport/utils.rs:32
- TodoComment wstunnel/src/protocols/socks5/tcp_server.rs:74
- REDACTED
- REDACTED
- FunctionTooLong: wstunnel::create_client_tunnels wstunnel/src/lib.rs:237
- FunctionTooLong: wstunnel::create_client wstunnel/src/lib.rs:58
- MethodTooLong: Server.serve wstunnel/src/tunnel/server/server.rs:353
- MethodTooLong: Server.exec_tunnel wstunnel/src/tunnel/server/server.rs:163
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (14 lines × 2) wstunnel/src/protocols/tcp/server.rs:96
- Duplicated block (14 lines × 2) wstunnel/src/tunnel/downstream_listeners/tcp.rs:46
- Duplicated block (11 lines × 2) wstunnel/src/tunnel/server/server.rs:298
- Duplicated block (11 lines × 2) wstunnel/src/tunnel/transport/websocket.rs:225
- No authorization wstunnel/src/tunnel/server/server.rs:515
- Yanked release: tokio
- Server::serve (cognitive 41) wstunnel/src/tunnel/server/server.rs:353
- ReverseTunnelServer::run_listening_server (cognitive 33) wstunnel/src/tunnel/server/reverse_tunnel.rs:63
- REDACTED
- Edited copy of a member (42 corresponding lines) wstunnel/src/protocols/socks5/udp_server.rs:40
- Duplicated block (38 lines × 2) wstunnel/src/protocols/socks5/udp_server.rs:45
- Duplicated block (16 lines × 2) wstunnel/src/tunnel/server/server.rs:363
- Duplicated block (15 lines × 2) wstunnel/src/tunnel/downstream_listeners/tproxy.rs:92
- Duplicated block (13 lines × 3) wstunnel/src/tunnel/downstream_listeners/tcp.rs:49
- Duplicated block (11–12 lines × 2) wstunnel/src/lib.rs:260
- Duplicated block (12 lines × 2) wstunnel/src/protocols/socks5/udp_server.rs:86
- Duplicated block (10 lines × 4) wstunnel/src/tunnel/server/server.rs:233
- Duplicated block (6 lines × 2) wstunnel/src/protocols/tcp/server.rs:59
- Duplicated block (9 lines × 2) wstunnel/src/config.rs:618
- Duplicated block (8 lines × 4) wstunnel/src/config.rs:605
- Off the main sequence: wstunnel
- Low cohesion: L4Stream (LCOM4 6) wstunnel/src/tunnel/client/connection_pool/l4_stream.rs:12
Minor — 54 finding(s)
- Interpolated log message defeats structured logging wstunnel-cli/src/main.rs:91
- Interpolated log message defeats structured logging wstunnel/src/lib.rs:232
- Interpolated log message defeats structured logging wstunnel/src/lib.rs:276
- Interpolated log message defeats structured logging wstunnel/src/lib.rs:299
- Interpolated log message defeats structured logging wstunnel/src/lib.rs:318
- Interpolated log message defeats structured logging wstunnel/src/lib.rs:342
- Interpolated log message defeats structured logging wstunnel/src/lib.rs:348
- Interpolated log message defeats structured logging wstunnel/src/lib.rs:366
- Interpolated log message defeats structured logging wstunnel/src/lib.rs:391
- Interpolated log message defeats structured logging wstunnel/src/lib.rs:402
- Interpolated log message defeats structured logging wstunnel/src/lib.rs:412
- Interpolated log message defeats structured logging wstunnel/src/lib.rs:427
- Interpolated log message defeats structured logging wstunnel/src/lib.rs:439
- Interpolated log message defeats structured logging wstunnel/src/lib.rs:447
- Interpolated log message defeats structured logging wstunnel/src/lib.rs:461
- Interpolated log message defeats structured logging wstunnel/src/lib.rs:469
- Interpolated log message defeats structured logging wstunnel/src/lib.rs:588
- Interpolated log message defeats structured logging wstunnel/src/tunnel/ca_reloader.rs:63
- Interpolated log message defeats structured logging wstunnel/src/tunnel/ca_reloader.rs:67
- Interpolated log message defeats structured logging wstunnel/src/tunnel/tls_reloader.rs:71
- Interpolated log message defeats structured logging wstunnel/src/tunnel/tls_reloader.rs:76
- Interpolated log message defeats structured logging wstunnel/src/tunnel/tls_reloader.rs:261
- Interpolated log message defeats structured logging wstunnel/src/tunnel/tls_reloader.rs:269
- Interpolated log message defeats structured logging wstunnel/src/tunnel/tls_reloader.rs:301
- Interpolated log message defeats structured logging wstunnel/src/tunnel/tls_reloader.rs:334
- No ADRs found
- Projects may be oversized for their cohesion
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- Logging is not universal
- No release approval gate
- No security response headers detected
- Duplicated predicate wstunnel/src/protocols/socks5/udp_server.rs:184
Minor — 3 finding(s)
- Outdated: notify
- Outdated: uuid
- Outdated: web-transport-quinn
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-58627130fb494b079dd6e4113be5c94b/history.json --exit-code 0 --source . | 13 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-58627130fb494b079dd6e4113be5c94b/tree.json --exit-code 0 --source . | 3 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 25 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 9 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 6 | artifacts/raw/trivy-config.json |
| 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 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |