Executive summary
n0-computer/iroh falls short of our standard for production, in part because we found no access checks on the code's endpoints or handlers. It scores 57 out of 100 and is rated Adequate, and 26 of its 29 critical findings are security problems in the build pipeline and in its servers and containers.
Security and Compliance, at 38, is the weakest lens and counts most in the score. The best first step is adding access checks, worth about 15 points. Raising Security and Compliance to 70 would lift the score to about 71.
Eleven pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Five secrets can leak from the build pipeline, and five settings leave the servers or containers unsafe. Pinning each tool to an exact version, limiting each secret to its own step and correcting the unsafe settings would close these risks. Correcting the flagged pipeline settings would fix the weakness in the build pipeline's configuration, and the four pipeline steps that run downloads without checking them need each download checked against a known checksum first. The two tests the project itself marks as unreliable need fixing or deleting.
The product code is 46,205 lines, about €54,000 to rebuild.
If Security and Compliance rose from 38 to 70, the lowest score rated Strong, the score would rise from 57 to about 71.
New since the last survey: 7 findings
- Cognitive Complexity · RelayTransport::poll_recv (cognitive 17) iroh/src/socket/transports/relay.rs
- Static Analysis (SAST) · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Access Controls · No authorization iroh-relay/src/server.rs
- Outbound HTTP resilience · Outbound HTTP without resilience iroh/src/util.rs
Fixed since the last survey: 2 findings
- Code Duplication · Duplicated block (8 lines × 2) iroh-dns-server/src/http.rs
- Access Controls · No authorization iroh-dns-server/src/http.rs
Rebuild cost: about €54,000 · Estimate
| Cost to rebuild | €18,000 to €91,000, for 301 to 956 hours of work, about 0.4 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 57. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Medium: 46,205 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 iroh.address_lookup.metrics | 2 iroh_base.key | 3 iroh_base.relay_url | 4 iroh_relay.protos.relay | 5 iroh.tls | 6 iroh_dns.dns | 7 iroh_dns.pkarr | 8 iroh_relay.client.conn | 9 iroh_relay.relay_map | 10 iroh_dns.endpoint_info | 11 iroh_relay.client | 12 iroh_base.endpoint_addr | 13 iroh.socket.remote_map.remote_state.path_watcher | 14 iroh.net_report.reportgen | 15 iroh.socket.remote_map.remote_state | 16 iroh.net_report.options.imp | 17 iroh.net_report.report | 18 iroh.socket.remote_map | 19 iroh.net_report | 20 iroh.socket.transports.ip | 21 iroh.socket | 22 iroh.socket.transports.relay.actor | 23 iroh_relay.server.clients | 24 iroh.socket.transports.relay | 25 iroh.socket.transports | 26 iroh.endpoint.quic | 27 iroh_dns_server.store.signed_packets | 28 iroh.endpoint.connection | 29 iroh_dns_server.store | 30 iroh.endpoint | 31 iroh.address_lookup | 32 iroh_dns_server.http | 33 iroh_relay.server.http_server | 34 iroh.address_lookup.pkarr | 35 iroh_dns_server.server | 36 iroh_dns_server.dns | 37 iroh_relay.server | 38 iroh_relay.main | 39 iroh_relay.server.streams | 40 iroh_relay.server.client |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 iroh.address_lookup.metrics | ||||||||||||||||||||||||||||||||||||||||
| 2 iroh_base.key | ||||||||||||||||||||||||||||||||||||||||
| 3 iroh_base.relay_url | ||||||||||||||||||||||||||||||||||||||||
| 4 iroh_relay.protos.relay | ||||||||||||||||||||||||||||||||||||||||
| 5 iroh.tls | 1 | |||||||||||||||||||||||||||||||||||||||
| 6 iroh_dns.dns | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 7 iroh_dns.pkarr | 3 | |||||||||||||||||||||||||||||||||||||||
| 8 iroh_relay.client.conn | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 9 iroh_relay.relay_map | 2 | |||||||||||||||||||||||||||||||||||||||
| 10 iroh_dns.endpoint_info | 1 | 2 | 1 | 4 | 1 | |||||||||||||||||||||||||||||||||||
| 11 iroh_relay.client | 1 | 1 | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 12 iroh_base.endpoint_addr | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 13 iroh.socket.remote_map.remote_state.path_watcher | 2 | 4 | 7 | 1 | ||||||||||||||||||||||||||||||||||||
| 14 iroh.net_report.reportgen | 3 | 2 | 4 | 1 | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 15 iroh.socket.remote_map.remote_state | 3 | 2 | 13 | 8 | 3 | |||||||||||||||||||||||||||||||||||
| 16 iroh.net_report.options.imp | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 17 iroh.net_report.report | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 18 iroh.socket.remote_map | 1 | 1 | 2 | 5 | 1 | 2 | ||||||||||||||||||||||||||||||||||
| 19 iroh.net_report | 1 | 2 | 2 | 4 | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||
| 20 iroh.socket.transports.ip | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 21 iroh.socket | 1 | 2 | 1 | 2 | 1 | 3 | 2 | 1 | 1 | 2 | 1 | 1 | 1 | 2 | 1 | 7 | 3 | 1 | 2 | 1 | ||||||||||||||||||||
| 22 iroh.socket.transports.relay.actor | 2 | 6 | 3 | 2 | 1 | 2 | 1 | 1 | 1 | 4 | 1 | |||||||||||||||||||||||||||||
| 23 iroh_relay.server.clients | 1 | 1 | 1 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||
| 24 iroh.socket.transports.relay | 1 | 1 | 1 | 3 | 4 | |||||||||||||||||||||||||||||||||||
| 25 iroh.socket.transports | 3 | 1 | 3 | 3 | 3 | |||||||||||||||||||||||||||||||||||
| 26 iroh.endpoint.quic | 2 | |||||||||||||||||||||||||||||||||||||||
| 27 iroh_dns_server.store.signed_packets | 2 | 3 | 3 | 2 | ||||||||||||||||||||||||||||||||||||
| 28 iroh.endpoint.connection | 6 | 2 | 1 | 6 | ||||||||||||||||||||||||||||||||||||
| 29 iroh_dns_server.store | 2 | 4 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 30 iroh.endpoint | 2 | 2 | 1 | 2 | 3 | 1 | 1 | 1 | 1 | 2 | 3 | 1 | ||||||||||||||||||||||||||||
| 31 iroh.address_lookup | 2 | 7 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 32 iroh_dns_server.http | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 33 iroh_relay.server.http_server | 3 | 3 | 1 | 2 | 1 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||
| 34 iroh.address_lookup.pkarr | 3 | 4 | 1 | 4 | 1 | 2 | 4 | |||||||||||||||||||||||||||||||||
| 35 iroh_dns_server.server | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 36 iroh_dns_server.dns | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 37 iroh_relay.server | 1 | 1 | 1 | 1 | 2 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||
| 38 iroh_relay.main | 2 | 2 | 2 | 12 | ||||||||||||||||||||||||||||||||||||
| 39 iroh_relay.server.streams | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 40 iroh_relay.server.client | 2 | 5 | 1 | 1 | 1 | 2 | 1 | 3 | 2 |
5→2 iroh.tls uses iroh_base.key✕
- Connections
- 1 pair of types, where a type in iroh.tls uses a type in iroh_base.key.
- The types involved
iroh.tls.TlsConfig→iroh_base.key.SecretKey
- Direction
- iroh.tls uses iroh_base.key, so a change to iroh_base.key can break iroh.tls, while a change to iroh.tls can't break iroh_base.key.
- Position
- Below the diagonal: iroh.tls uses a module listed above it, which is the healthy direction.
6→30 iroh_dns.dns uses iroh.endpoint part of a loop✕
- Connections
- 2 pairs of types, where a type in iroh_dns.dns uses a type in iroh.endpoint.
- The types involved
iroh_dns.dns.Builder→iroh.endpoint.Builderiroh_dns.dns.DnsResolver→iroh.endpoint.Builder
- Direction
- iroh_dns.dns uses iroh.endpoint, so a change to iroh.endpoint can break iroh_dns.dns, while a change to iroh_dns.dns can't break iroh.endpoint.
- 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.
6→31 iroh_dns.dns uses iroh.address_lookup part of a loop✕
- Connections
- 2 pairs of types, where a type in iroh_dns.dns uses a type in iroh.address_lookup.
- The types involved
iroh_dns.dns.LookupIter→iroh.address_lookup.Itemiroh_dns.dns.dns$module→iroh.address_lookup.Error
- Direction
- iroh_dns.dns uses iroh.address_lookup, so a change to iroh.address_lookup can break iroh_dns.dns, while a change to iroh_dns.dns can't break iroh.address_lookup.
- 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.
7→2 iroh_dns.pkarr uses iroh_base.key✕
- Connections
- 3 pairs of types, where a type in iroh_dns.pkarr uses a type in iroh_base.key.
- The types involved
iroh_dns.pkarr.SignedPacket→iroh_base.key.PublicKeyiroh_dns.pkarr.SignedPacket→iroh_base.key.SecretKeyiroh_dns.pkarr.SignedPacket→iroh_base.key.Signature
- Direction
- iroh_dns.pkarr uses iroh_base.key, so a change to iroh_base.key can break iroh_dns.pkarr, while a change to iroh_dns.pkarr can't break iroh_base.key.
- Position
- Below the diagonal: iroh_dns.pkarr uses a module listed above it, which is the healthy direction.
8→2 iroh_relay.client.conn uses iroh_base.key✕
- Connections
- 1 pair of types, where a type in iroh_relay.client.conn uses a type in iroh_base.key.
- The types involved
iroh_relay.client.conn.Conn→iroh_base.key.SecretKey
- Direction
- iroh_relay.client.conn uses iroh_base.key, so a change to iroh_base.key can break iroh_relay.client.conn, while a change to iroh_relay.client.conn can't break iroh_base.key.
- Position
- Below the diagonal: iroh_relay.client.conn uses a module listed above it, which is the healthy direction.
8→4 iroh_relay.client.conn uses iroh_relay.protos.relay✕
- Connections
- 1 pair of types, where a type in iroh_relay.client.conn uses a type in iroh_relay.protos.relay.
- The types involved
iroh_relay.client.conn.Conn→iroh_relay.protos.relay.ClientToRelayMsg
- Direction
- iroh_relay.client.conn uses iroh_relay.protos.relay, so a change to iroh_relay.protos.relay can break iroh_relay.client.conn, while a change to iroh_relay.client.conn can't break iroh_relay.protos.relay.
- Position
- Below the diagonal: iroh_relay.client.conn uses a module listed above it, which is the healthy direction.
9→3 iroh_relay.relay_map uses iroh_base.relay_url✕
- Connections
- 2 pairs of types, where a type in iroh_relay.relay_map uses a type in iroh_base.relay_url.
- The types involved
iroh_relay.relay_map.RelayConfig→iroh_base.relay_url.RelayUrliroh_relay.relay_map.RelayMap→iroh_base.relay_url.RelayUrl
- Direction
- iroh_relay.relay_map uses iroh_base.relay_url, so a change to iroh_base.relay_url can break iroh_relay.relay_map, while a change to iroh_relay.relay_map can't break iroh_base.relay_url.
- Position
- Below the diagonal: iroh_relay.relay_map uses a module listed above it, which is the healthy direction.
10→2 iroh_dns.endpoint_info uses iroh_base.key✕
- Connections
- 1 pair of types, where a type in iroh_dns.endpoint_info uses a type in iroh_base.key.
- The types involved
iroh_dns.endpoint_info.EndpointInfo→iroh_base.key.SecretKey
- Direction
- iroh_dns.endpoint_info uses iroh_base.key, so a change to iroh_base.key can break iroh_dns.endpoint_info, while a change to iroh_dns.endpoint_info can't break iroh_base.key.
- Position
- Below the diagonal: iroh_dns.endpoint_info uses a module listed above it, which is the healthy direction.
10→3 iroh_dns.endpoint_info uses iroh_base.relay_url✕
- Connections
- 2 pairs of types, where a type in iroh_dns.endpoint_info uses a type in iroh_base.relay_url.
- The types involved
iroh_dns.endpoint_info.EndpointData→iroh_base.relay_url.RelayUrliroh_dns.endpoint_info.EndpointInfo→iroh_base.relay_url.RelayUrl
- Direction
- iroh_dns.endpoint_info uses iroh_base.relay_url, so a change to iroh_base.relay_url can break iroh_dns.endpoint_info, while a change to iroh_dns.endpoint_info can't break iroh_base.relay_url.
- Position
- Below the diagonal: iroh_dns.endpoint_info uses a module listed above it, which is the healthy direction.
10→7 iroh_dns.endpoint_info uses iroh_dns.pkarr✕
- Connections
- 1 pair of types, where a type in iroh_dns.endpoint_info uses a type in iroh_dns.pkarr.
- The types involved
iroh_dns.endpoint_info.EndpointInfo→iroh_dns.pkarr.SignedPacket
- Direction
- iroh_dns.endpoint_info uses iroh_dns.pkarr, so a change to iroh_dns.pkarr can break iroh_dns.endpoint_info, while a change to iroh_dns.endpoint_info can't break iroh_dns.pkarr.
- Position
- Below the diagonal: iroh_dns.endpoint_info uses a module listed above it, which is the healthy direction.
10→12 iroh_dns.endpoint_info uses iroh_base.endpoint_addr part of a loop✕
- Connections
- 4 pairs of types, where a type in iroh_dns.endpoint_info uses a type in iroh_base.endpoint_addr.
- The types involved
iroh_dns.endpoint_info.AddrFilter→iroh_base.endpoint_addr.TransportAddriroh_dns.endpoint_info.EndpointData→iroh_base.endpoint_addr.EndpointAddriroh_dns.endpoint_info.EndpointData→iroh_base.endpoint_addr.TransportAddriroh_dns.endpoint_info.EndpointInfo→iroh_base.endpoint_addr.EndpointAddr
- Direction
- iroh_dns.endpoint_info uses iroh_base.endpoint_addr, so a change to iroh_base.endpoint_addr can break iroh_dns.endpoint_info, while a change to iroh_dns.endpoint_info can't break iroh_base.endpoint_addr.
- 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→31 iroh_dns.endpoint_info uses iroh.address_lookup part of a loop✕
- Connections
- 1 pair of types, where a type in iroh_dns.endpoint_info uses a type in iroh.address_lookup.
- The types involved
iroh_dns.endpoint_info.EndpointInfo→iroh.address_lookup.Item
- Direction
- iroh_dns.endpoint_info uses iroh.address_lookup, so a change to iroh.address_lookup can break iroh_dns.endpoint_info, while a change to iroh_dns.endpoint_info can't break iroh.address_lookup.
- 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→2 iroh_relay.client uses iroh_base.key✕
- Connections
- 1 pair of types, where a type in iroh_relay.client uses a type in iroh_base.key.
- The types involved
iroh_relay.client.ClientBuilder→iroh_base.key.SecretKey
- Direction
- iroh_relay.client uses iroh_base.key, so a change to iroh_base.key can break iroh_relay.client, while a change to iroh_relay.client can't break iroh_base.key.
- Position
- Below the diagonal: iroh_relay.client uses a module listed above it, which is the healthy direction.
11→3 iroh_relay.client uses iroh_base.relay_url✕
- Connections
- 1 pair of types, where a type in iroh_relay.client uses a type in iroh_base.relay_url.
- The types involved
iroh_relay.client.ClientBuilder→iroh_base.relay_url.RelayUrl
- Direction
- iroh_relay.client uses iroh_base.relay_url, so a change to iroh_base.relay_url can break iroh_relay.client, while a change to iroh_relay.client can't break iroh_base.relay_url.
- Position
- Below the diagonal: iroh_relay.client uses a module listed above it, which is the healthy direction.
11→4 iroh_relay.client uses iroh_relay.protos.relay✕
- Connections
- 2 pairs of types, where a type in iroh_relay.client uses a type in iroh_relay.protos.relay.
- The types involved
iroh_relay.client.Client→iroh_relay.protos.relay.ClientToRelayMsgiroh_relay.client.ClientSink→iroh_relay.protos.relay.ClientToRelayMsg
- Direction
- iroh_relay.client uses iroh_relay.protos.relay, so a change to iroh_relay.protos.relay can break iroh_relay.client, while a change to iroh_relay.client can't break iroh_relay.protos.relay.
- Position
- Below the diagonal: iroh_relay.client uses a module listed above it, which is the healthy direction.
11→6 iroh_relay.client uses iroh_dns.dns✕
- Connections
- 1 pair of types, where a type in iroh_relay.client uses a type in iroh_dns.dns.
- The types involved
iroh_relay.client.ClientBuilder→iroh_dns.dns.DnsResolver
- Direction
- iroh_relay.client uses iroh_dns.dns, so a change to iroh_dns.dns can break iroh_relay.client, while a change to iroh_relay.client can't break iroh_dns.dns.
- Position
- Below the diagonal: iroh_relay.client uses a module listed above it, which is the healthy direction.
11→8 iroh_relay.client uses iroh_relay.client.conn✕
- Connections
- 1 pair of types, where a type in iroh_relay.client uses a type in iroh_relay.client.conn.
- The types involved
iroh_relay.client.Client→iroh_relay.client.conn.Conn
- Direction
- iroh_relay.client uses iroh_relay.client.conn, so a change to iroh_relay.client.conn can break iroh_relay.client, while a change to iroh_relay.client can't break iroh_relay.client.conn.
- Position
- Below the diagonal: iroh_relay.client uses a module listed above it, which is the healthy direction.
12→2 iroh_base.endpoint_addr uses iroh_base.key✕
- Connections
- 1 pair of types, where a type in iroh_base.endpoint_addr uses a type in iroh_base.key.
- The types involved
iroh_base.endpoint_addr.EndpointAddr→iroh_base.key.PublicKey
- Direction
- iroh_base.endpoint_addr uses iroh_base.key, so a change to iroh_base.key can break iroh_base.endpoint_addr, while a change to iroh_base.endpoint_addr can't break iroh_base.key.
- Position
- Below the diagonal: iroh_base.endpoint_addr uses a module listed above it, which is the healthy direction.
12→3 iroh_base.endpoint_addr uses iroh_base.relay_url✕
- Connections
- 1 pair of types, where a type in iroh_base.endpoint_addr uses a type in iroh_base.relay_url.
- The types involved
iroh_base.endpoint_addr.EndpointAddr→iroh_base.relay_url.RelayUrl
- Direction
- iroh_base.endpoint_addr uses iroh_base.relay_url, so a change to iroh_base.relay_url can break iroh_base.endpoint_addr, while a change to iroh_base.endpoint_addr can't break iroh_base.relay_url.
- Position
- Below the diagonal: iroh_base.endpoint_addr uses a module listed above it, which is the healthy direction.
12→10 iroh_base.endpoint_addr uses iroh_dns.endpoint_info✕
- Connections
- 1 pair of types, where a type in iroh_base.endpoint_addr uses a type in iroh_dns.endpoint_info.
- The types involved
iroh_base.endpoint_addr.EndpointAddr→iroh_dns.endpoint_info.EndpointInfo
- Direction
- iroh_base.endpoint_addr uses iroh_dns.endpoint_info, so a change to iroh_dns.endpoint_info can break iroh_base.endpoint_addr, while a change to iroh_base.endpoint_addr can't break iroh_dns.endpoint_info.
- Position
- Below the diagonal: iroh_base.endpoint_addr uses a module listed above it, which is the healthy direction.
12→25 iroh_base.endpoint_addr uses iroh.socket.transports part of a loop✕
- Connections
- 1 pair of types, where a type in iroh_base.endpoint_addr uses a type in iroh.socket.transports.
- The types involved
iroh_base.endpoint_addr.TransportAddr→iroh.socket.transports.Addr
- Direction
- iroh_base.endpoint_addr uses iroh.socket.transports, so a change to iroh.socket.transports can break iroh_base.endpoint_addr, while a change to iroh_base.endpoint_addr can't break iroh.socket.transports.
- 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→28 iroh_base.endpoint_addr uses iroh.endpoint.connection part of a loop✕
- Connections
- 1 pair of types, where a type in iroh_base.endpoint_addr uses a type in iroh.endpoint.connection.
- The types involved
iroh_base.endpoint_addr.TransportAddr→iroh.endpoint.connection.IncomingAddr
- Direction
- iroh_base.endpoint_addr uses iroh.endpoint.connection, so a change to iroh.endpoint.connection can break iroh_base.endpoint_addr, while a change to iroh_base.endpoint_addr can't break iroh.endpoint.connection.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→12 iroh.socket.remote_map.remote_state.path_watcher uses iroh_base.endpoint_addr✕
- Connections
- 2 pairs of types, where a type in iroh.socket.remote_map.remote_state.path_watcher uses a type in iroh_base.endpoint_addr.
- The types involved
iroh.socket.remote_map.remote_state.path_watcher.Path→iroh_base.endpoint_addr.TransportAddriroh.socket.remote_map.remote_state.path_watcher.PathData→iroh_base.endpoint_addr.TransportAddr
- Direction
- iroh.socket.remote_map.remote_state.path_watcher uses iroh_base.endpoint_addr, so a change to iroh_base.endpoint_addr can break iroh.socket.remote_map.remote_state.path_watcher, while a change to iroh.socket.remote_map.remote_state.path_watcher can't break iroh_base.endpoint_addr.
- Position
- Below the diagonal: iroh.socket.remote_map.remote_state.path_watcher uses a module listed above it, which is the healthy direction.
13→25 iroh.socket.remote_map.remote_state.path_watcher uses iroh.socket.transports part of a loop✕
- Connections
- 4 pairs of types, where a type in iroh.socket.remote_map.remote_state.path_watcher uses a type in iroh.socket.transports.
- The types involved
iroh.socket.remote_map.remote_state.path_watcher.Path→iroh.socket.transports.LocalTransportAddriroh.socket.remote_map.remote_state.path_watcher.PathData→iroh.socket.transports.LocalTransportAddriroh.socket.remote_map.remote_state.path_watcher.PathStateSender→iroh.socket.transports.FourTupleiroh.socket.remote_map.remote_state.path_watcher.PathStateSender→iroh.socket.transports.Sender
- Direction
- iroh.socket.remote_map.remote_state.path_watcher uses iroh.socket.transports, so a change to iroh.socket.transports can break iroh.socket.remote_map.remote_state.path_watcher, while a change to iroh.socket.remote_map.remote_state.path_watcher can't break iroh.socket.transports.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→28 iroh.socket.remote_map.remote_state.path_watcher uses iroh.endpoint.connection part of a loop✕
- Connections
- 7 pairs of types, where a type in iroh.socket.remote_map.remote_state.path_watcher uses a type in iroh.endpoint.connection.
- The types involved
iroh.socket.remote_map.remote_state.path_watcher.Path→iroh.endpoint.connection.Connectioniroh.socket.remote_map.remote_state.path_watcher.PathData→iroh.endpoint.connection.Connectioniroh.socket.remote_map.remote_state.path_watcher.PathList→iroh.endpoint.connection.Connectioniroh.socket.remote_map.remote_state.path_watcher.PathListIter→iroh.endpoint.connection.Connectioniroh.socket.remote_map.remote_state.path_watcher.PathListStream→iroh.endpoint.connection.Connectioniroh.socket.remote_map.remote_state.path_watcher.PathStateReceiver→iroh.endpoint.connection.Connectioniroh.socket.remote_map.remote_state.path_watcher.PathStateSender→iroh.endpoint.connection.Connection
- Direction
- iroh.socket.remote_map.remote_state.path_watcher uses iroh.endpoint.connection, so a change to iroh.endpoint.connection can break iroh.socket.remote_map.remote_state.path_watcher, while a change to iroh.socket.remote_map.remote_state.path_watcher can't break iroh.endpoint.connection.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→31 iroh.socket.remote_map.remote_state.path_watcher uses iroh.address_lookup part of a loop✕
- Connections
- 1 pair of types, where a type in iroh.socket.remote_map.remote_state.path_watcher uses a type in iroh.address_lookup.
- The types involved
iroh.socket.remote_map.remote_state.path_watcher.PathListIter→iroh.address_lookup.Item
- Direction
- iroh.socket.remote_map.remote_state.path_watcher uses iroh.address_lookup, so a change to iroh.address_lookup can break iroh.socket.remote_map.remote_state.path_watcher, while a change to iroh.socket.remote_map.remote_state.path_watcher can't break iroh.address_lookup.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→3 iroh.net_report.reportgen uses iroh_base.relay_url✕
- Connections
- 3 pairs of types, where a type in iroh.net_report.reportgen uses a type in iroh_base.relay_url.
- The types involved
iroh.net_report.reportgen.HttpsProbeReport→iroh_base.relay_url.RelayUrliroh.net_report.reportgen.QadProbeReport→iroh_base.relay_url.RelayUrliroh.net_report.reportgen.reportgen$module→iroh_base.relay_url.RelayUrl
- Direction
- iroh.net_report.reportgen uses iroh_base.relay_url, so a change to iroh_base.relay_url can break iroh.net_report.reportgen, while a change to iroh.net_report.reportgen can't break iroh_base.relay_url.
- Position
- Below the diagonal: iroh.net_report.reportgen uses a module listed above it, which is the healthy direction.
14→6 iroh.net_report.reportgen uses iroh_dns.dns✕
- Connections
- 2 pairs of types, where a type in iroh.net_report.reportgen uses a type in iroh_dns.dns.
- The types involved
iroh.net_report.reportgen.SocketState→iroh_dns.dns.DnsResolveriroh.net_report.reportgen.reportgen$module→iroh_dns.dns.DnsResolver
- Direction
- iroh.net_report.reportgen uses iroh_dns.dns, so a change to iroh_dns.dns can break iroh.net_report.reportgen, while a change to iroh.net_report.reportgen can't break iroh_dns.dns.
- Position
- Below the diagonal: iroh.net_report.reportgen uses a module listed above it, which is the healthy direction.
14→9 iroh.net_report.reportgen uses iroh_relay.relay_map✕
- Connections
- 4 pairs of types, where a type in iroh.net_report.reportgen uses a type in iroh_relay.relay_map.
- The types involved
iroh.net_report.reportgen.Actor→iroh_relay.relay_map.RelayMapiroh.net_report.reportgen.Client→iroh_relay.relay_map.RelayMapiroh.net_report.reportgen.reportgen$module→iroh_relay.relay_map.RelayConfigiroh.net_report.reportgen.reportgen$module→iroh_relay.relay_map.RelayMap
- Direction
- iroh.net_report.reportgen uses iroh_relay.relay_map, so a change to iroh_relay.relay_map can break iroh.net_report.reportgen, while a change to iroh.net_report.reportgen can't break iroh_relay.relay_map.
- Position
- Below the diagonal: iroh.net_report.reportgen uses a module listed above it, which is the healthy direction.
14→13 iroh.net_report.reportgen uses iroh.socket.remote_map.remote_state.path_watcher✕
- Connections
- 1 pair of types, where a type in iroh.net_report.reportgen uses a type in iroh.socket.remote_map.remote_state.path_watcher.
- The types involved
iroh.net_report.reportgen.IfStateDetails→iroh.socket.remote_map.remote_state.path_watcher.State
- Direction
- iroh.net_report.reportgen uses iroh.socket.remote_map.remote_state.path_watcher, so a change to iroh.socket.remote_map.remote_state.path_watcher can break iroh.net_report.reportgen, while a change to iroh.net_report.reportgen can't break iroh.socket.remote_map.remote_state.path_watcher.
- Position
- Below the diagonal: iroh.net_report.reportgen uses a module listed above it, which is the healthy direction.
14→17 iroh.net_report.reportgen uses iroh.net_report.report part of a loop✕
- Connections
- 2 pairs of types, where a type in iroh.net_report.reportgen uses a type in iroh.net_report.report.
- The types involved
iroh.net_report.reportgen.Actor→iroh.net_report.report.Reportiroh.net_report.reportgen.Client→iroh.net_report.report.Report
- Direction
- iroh.net_report.reportgen uses iroh.net_report.report, so a change to iroh.net_report.report can break iroh.net_report.reportgen, while a change to iroh.net_report.reportgen can't break iroh.net_report.report.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→25 iroh.net_report.reportgen uses iroh.socket.transports part of a loop✕
- Connections
- 1 pair of types, where a type in iroh.net_report.reportgen uses a type in iroh.socket.transports.
- The types involved
iroh.net_report.reportgen.Actor→iroh.socket.transports.Sender
- Direction
- iroh.net_report.reportgen uses iroh.socket.transports, so a change to iroh.socket.transports can break iroh.net_report.reportgen, while a change to iroh.net_report.reportgen can't break iroh.socket.transports.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→30 iroh.net_report.reportgen uses iroh.endpoint part of a loop✕
- Connections
- 1 pair of types, where a type in iroh.net_report.reportgen uses a type in iroh.endpoint.
- The types involved
iroh.net_report.reportgen.QuicConfig→iroh.endpoint.Endpoint
- Direction
- iroh.net_report.reportgen uses iroh.endpoint, so a change to iroh.endpoint can break iroh.net_report.reportgen, while a change to iroh.net_report.reportgen can't break iroh.endpoint.
- 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.
15→13 iroh.socket.remote_map.remote_state uses iroh.socket.remote_map.remote_state.path_watcher✕
- Connections
- 3 pairs of types, where a type in iroh.socket.remote_map.remote_state uses a type in iroh.socket.remote_map.remote_state.path_watcher.
- The types involved
iroh.socket.remote_map.remote_state.ConnectionState→iroh.socket.remote_map.remote_state.path_watcher.PathStateSenderiroh.socket.remote_map.remote_state.RemoteStateActor→iroh.socket.remote_map.remote_state.path_watcher.Stateiroh.socket.remote_map.remote_state.State→iroh.socket.remote_map.remote_state.path_watcher.Path
- Direction
- iroh.socket.remote_map.remote_state uses iroh.socket.remote_map.remote_state.path_watcher, so a change to iroh.socket.remote_map.remote_state.path_watcher can break iroh.socket.remote_map.remote_state, while a change to iroh.socket.remote_map.remote_state can't break iroh.socket.remote_map.remote_state.path_watcher.
- Position
- Below the diagonal: iroh.socket.remote_map.remote_state uses a module listed above it, which is the healthy direction.
15→18 iroh.socket.remote_map.remote_state uses iroh.socket.remote_map part of a loop✕
- Connections
- 2 pairs of types, where a type in iroh.socket.remote_map.remote_state uses a type in iroh.socket.remote_map.
- The types involved
iroh.socket.remote_map.remote_state.RemoteStateActor→iroh.socket.remote_map.MappedAddrsiroh.socket.remote_map.remote_state.State→iroh.socket.remote_map.MappedAddrs
- Direction
- iroh.socket.remote_map.remote_state uses iroh.socket.remote_map, so a change to iroh.socket.remote_map can break iroh.socket.remote_map.remote_state, while a change to iroh.socket.remote_map.remote_state can't break iroh.socket.remote_map.
- 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.
15→25 iroh.socket.remote_map.remote_state uses iroh.socket.transports part of a loop✕
- Connections
- 13 pairs of types, where a type in iroh.socket.remote_map.remote_state uses a type in iroh.socket.transports.
- The types involved
iroh.socket.remote_map.remote_state.ConnectionState→iroh.socket.transports.FourTupleiroh.socket.remote_map.remote_state.PathSelection→iroh.socket.transports.FourTupleiroh.socket.remote_map.remote_state.PathSelectionContext→iroh.socket.transports.FourTupleiroh.socket.remote_map.remote_state.PathSelectionData→iroh.socket.transports.FourTupleiroh.socket.remote_map.remote_state.RemoteStateActor→iroh.socket.transports.FourTupleiroh.socket.remote_map.remote_state.RemoteStateActor→iroh.socket.transports.Senderiroh.socket.remote_map.remote_state.State→iroh.socket.transports.FourTupleiroh.socket.remote_map.remote_state.State→iroh.socket.transports.OwnedTransmitiroh.socket.remote_map.remote_state.State→iroh.socket.transports.Senderiroh.socket.remote_map.remote_state.State→iroh.socket.transports.TransportsSenderiroh.socket.remote_map.remote_state.remote_state$module→iroh.socket.transports.FourTupleiroh.socket.remote_map.remote_state.remote_state$module→iroh.socket.transports.OwnedTransmitiroh.socket.remote_map.remote_state.remote_state$module→iroh.socket.transports.TransportsSender
- Direction
- iroh.socket.remote_map.remote_state uses iroh.socket.transports, so a change to iroh.socket.transports can break iroh.socket.remote_map.remote_state, while a change to iroh.socket.remote_map.remote_state can't break iroh.socket.transports.
- 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.
15→28 iroh.socket.remote_map.remote_state uses iroh.endpoint.connection part of a loop✕
- Connections
- 8 pairs of types, where a type in iroh.socket.remote_map.remote_state uses a type in iroh.endpoint.connection.
- The types involved
iroh.socket.remote_map.remote_state.ConnectionState→iroh.endpoint.connection.Connectioniroh.socket.remote_map.remote_state.ConnectionState→iroh.endpoint.connection.WeakConnectionHandleiroh.socket.remote_map.remote_state.OnClosed→iroh.endpoint.connection.Connectioniroh.socket.remote_map.remote_state.PathSelectionData→iroh.endpoint.connection.Connectioniroh.socket.remote_map.remote_state.RemoteStateActor→iroh.endpoint.connection.Connectioniroh.socket.remote_map.remote_state.State→iroh.endpoint.connection.Connectioniroh.socket.remote_map.remote_state.State→iroh.endpoint.connection.ConnectionStateiroh.socket.remote_map.remote_state.remote_state$module→iroh.endpoint.connection.Connection
- Direction
- iroh.socket.remote_map.remote_state uses iroh.endpoint.connection, so a change to iroh.endpoint.connection can break iroh.socket.remote_map.remote_state, while a change to iroh.socket.remote_map.remote_state can't break iroh.endpoint.connection.
- 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.
15→31 iroh.socket.remote_map.remote_state uses iroh.address_lookup part of a loop✕
- Connections
- 3 pairs of types, where a type in iroh.socket.remote_map.remote_state uses a type in iroh.address_lookup.
- The types involved
iroh.socket.remote_map.remote_state.RemoteStateActor→iroh.address_lookup.AddressLookupServicesiroh.socket.remote_map.remote_state.State→iroh.address_lookup.AddressLookupServicesiroh.socket.remote_map.remote_state.remote_state$module→iroh.address_lookup.Item
- Direction
- iroh.socket.remote_map.remote_state uses iroh.address_lookup, so a change to iroh.address_lookup can break iroh.socket.remote_map.remote_state, while a change to iroh.socket.remote_map.remote_state can't break iroh.address_lookup.
- 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.
16→14 iroh.net_report.options.imp uses iroh.net_report.reportgen✕
- Connections
- 1 pair of types, where a type in iroh.net_report.options.imp uses a type in iroh.net_report.reportgen.
- The types involved
iroh.net_report.options.imp.Options→iroh.net_report.reportgen.QuicConfig
- Direction
- iroh.net_report.options.imp uses iroh.net_report.reportgen, so a change to iroh.net_report.reportgen can break iroh.net_report.options.imp, while a change to iroh.net_report.options.imp can't break iroh.net_report.reportgen.
- Position
- Below the diagonal: iroh.net_report.options.imp uses a module listed above it, which is the healthy direction.
16→19 iroh.net_report.options.imp uses iroh.net_report part of a loop✕
- Connections
- 1 pair of types, where a type in iroh.net_report.options.imp uses a type in iroh.net_report.
- The types involved
iroh.net_report.options.imp.Options→iroh.net_report.NetReportConfig
- Direction
- iroh.net_report.options.imp uses iroh.net_report, so a change to iroh.net_report can break iroh.net_report.options.imp, while a change to iroh.net_report.options.imp can't break iroh.net_report.
- 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.
17→3 iroh.net_report.report uses iroh_base.relay_url✕
- Connections
- 2 pairs of types, where a type in iroh.net_report.report uses a type in iroh_base.relay_url.
- The types involved
iroh.net_report.report.RelayLatencies→iroh_base.relay_url.RelayUrliroh.net_report.report.Report→iroh_base.relay_url.RelayUrl
- Direction
- iroh.net_report.report uses iroh_base.relay_url, so a change to iroh_base.relay_url can break iroh.net_report.report, while a change to iroh.net_report.report can't break iroh_base.relay_url.
- Position
- Below the diagonal: iroh.net_report.report uses a module listed above it, which is the healthy direction.
17→14 iroh.net_report.report uses iroh.net_report.reportgen✕
- Connections
- 1 pair of types, where a type in iroh.net_report.report uses a type in iroh.net_report.reportgen.
- The types involved
iroh.net_report.report.Report→iroh.net_report.reportgen.ProbeReport
- Direction
- iroh.net_report.report uses iroh.net_report.reportgen, so a change to iroh.net_report.reportgen can break iroh.net_report.report, while a change to iroh.net_report.report can't break iroh.net_report.reportgen.
- Position
- Below the diagonal: iroh.net_report.report uses a module listed above it, which is the healthy direction.
18→2 iroh.socket.remote_map uses iroh_base.key✕
- Connections
- 1 pair of types, where a type in iroh.socket.remote_map uses a type in iroh_base.key.
- The types involved
iroh.socket.remote_map.RemoteMap→iroh_base.key.PublicKey
- Direction
- iroh.socket.remote_map uses iroh_base.key, so a change to iroh_base.key can break iroh.socket.remote_map, while a change to iroh.socket.remote_map can't break iroh_base.key.
- Position
- Below the diagonal: iroh.socket.remote_map uses a module listed above it, which is the healthy direction.
18→12 iroh.socket.remote_map uses iroh_base.endpoint_addr✕
- Connections
- 1 pair of types, where a type in iroh.socket.remote_map uses a type in iroh_base.endpoint_addr.
- The types involved
iroh.socket.remote_map.RemoteMap→iroh_base.endpoint_addr.EndpointAddr
- Direction
- iroh.socket.remote_map uses iroh_base.endpoint_addr, so a change to iroh_base.endpoint_addr can break iroh.socket.remote_map, while a change to iroh.socket.remote_map can't break iroh_base.endpoint_addr.
- Position
- Below the diagonal: iroh.socket.remote_map uses a module listed above it, which is the healthy direction.
18→15 iroh.socket.remote_map uses iroh.socket.remote_map.remote_state✕
- Connections
- 2 pairs of types, where a type in iroh.socket.remote_map uses a type in iroh.socket.remote_map.remote_state.
- The types involved
iroh.socket.remote_map.RemoteMap→iroh.socket.remote_map.remote_state.RemoteStateMessageiroh.socket.remote_map.Tasks→iroh.socket.remote_map.remote_state.RemoteStateMessage
- Direction
- iroh.socket.remote_map uses iroh.socket.remote_map.remote_state, so a change to iroh.socket.remote_map.remote_state can break iroh.socket.remote_map, while a change to iroh.socket.remote_map can't break iroh.socket.remote_map.remote_state.
- Position
- Below the diagonal: iroh.socket.remote_map uses a module listed above it, which is the healthy direction.
18→25 iroh.socket.remote_map uses iroh.socket.transports part of a loop✕
- Connections
- 5 pairs of types, where a type in iroh.socket.remote_map uses a type in iroh.socket.transports.
- The types involved
iroh.socket.remote_map.MappedAddrs→iroh.socket.transports.Addriroh.socket.remote_map.MappedAddrs→iroh.socket.transports.FourTupleiroh.socket.remote_map.RemoteMap→iroh.socket.transports.Senderiroh.socket.remote_map.Tasks→iroh.socket.transports.Senderiroh.socket.remote_map.remote_map$module→iroh.socket.transports.Addr
- Direction
- iroh.socket.remote_map uses iroh.socket.transports, so a change to iroh.socket.transports can break iroh.socket.remote_map, while a change to iroh.socket.remote_map can't break iroh.socket.transports.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→28 iroh.socket.remote_map uses iroh.endpoint.connection part of a loop✕
- Connections
- 1 pair of types, where a type in iroh.socket.remote_map uses a type in iroh.endpoint.connection.
- The types involved
iroh.socket.remote_map.RemoteMap→iroh.endpoint.connection.Connection
- Direction
- iroh.socket.remote_map uses iroh.endpoint.connection, so a change to iroh.endpoint.connection can break iroh.socket.remote_map, while a change to iroh.socket.remote_map can't break iroh.endpoint.connection.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→31 iroh.socket.remote_map uses iroh.address_lookup part of a loop✕
- Connections
- 2 pairs of types, where a type in iroh.socket.remote_map uses a type in iroh.address_lookup.
- The types involved
iroh.socket.remote_map.RemoteMap→iroh.address_lookup.AddressLookupServicesiroh.socket.remote_map.Tasks→iroh.address_lookup.AddressLookupServices
- Direction
- iroh.socket.remote_map uses iroh.address_lookup, so a change to iroh.address_lookup can break iroh.socket.remote_map, while a change to iroh.socket.remote_map can't break iroh.address_lookup.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→1 iroh.net_report uses iroh.address_lookup.metrics✕
- Connections
- 1 pair of types, where a type in iroh.net_report uses a type in iroh.address_lookup.metrics.
- The types involved
iroh.net_report.Client→iroh.address_lookup.metrics.Metrics
- Direction
- iroh.net_report uses iroh.address_lookup.metrics, so a change to iroh.address_lookup.metrics can break iroh.net_report, while a change to iroh.net_report can't break iroh.address_lookup.metrics.
- Position
- Below the diagonal: iroh.net_report uses a module listed above it, which is the healthy direction.
19→6 iroh.net_report uses iroh_dns.dns✕
- Connections
- 2 pairs of types, where a type in iroh.net_report uses a type in iroh_dns.dns.
- The types involved
iroh.net_report.Client→iroh_dns.dns.DnsResolveriroh.net_report.net_report$module→iroh_dns.dns.DnsResolver
- Direction
- iroh.net_report uses iroh_dns.dns, so a change to iroh_dns.dns can break iroh.net_report, while a change to iroh.net_report can't break iroh_dns.dns.
- Position
- Below the diagonal: iroh.net_report uses a module listed above it, which is the healthy direction.
19→9 iroh.net_report uses iroh_relay.relay_map✕
- Connections
- 2 pairs of types, where a type in iroh.net_report uses a type in iroh_relay.relay_map.
- The types involved
iroh.net_report.Client→iroh_relay.relay_map.RelayMapiroh.net_report.net_report$module→iroh_relay.relay_map.RelayConfig
- Direction
- iroh.net_report uses iroh_relay.relay_map, so a change to iroh_relay.relay_map can break iroh.net_report, while a change to iroh.net_report can't break iroh_relay.relay_map.
- Position
- Below the diagonal: iroh.net_report uses a module listed above it, which is the healthy direction.
19→14 iroh.net_report uses iroh.net_report.reportgen✕
- Connections
- 4 pairs of types, where a type in iroh.net_report uses a type in iroh.net_report.reportgen.
- The types involved
iroh.net_report.Client→iroh.net_report.reportgen.IfStateDetailsiroh.net_report.Client→iroh.net_report.reportgen.ProbeReportiroh.net_report.Client→iroh.net_report.reportgen.SocketStateiroh.net_report.QadConns→iroh.net_report.reportgen.ProbeReport
- Direction
- iroh.net_report uses iroh.net_report.reportgen, so a change to iroh.net_report.reportgen can break iroh.net_report, while a change to iroh.net_report can't break iroh.net_report.reportgen.
- Position
- Below the diagonal: iroh.net_report uses a module listed above it, which is the healthy direction.
19→16 iroh.net_report uses iroh.net_report.options.imp✕
- Connections
- 1 pair of types, where a type in iroh.net_report uses a type in iroh.net_report.options.imp.
- The types involved
iroh.net_report.Client→iroh.net_report.options.imp.Options
- Direction
- iroh.net_report uses iroh.net_report.options.imp, so a change to iroh.net_report.options.imp can break iroh.net_report, while a change to iroh.net_report can't break iroh.net_report.options.imp.
- Position
- Below the diagonal: iroh.net_report uses a module listed above it, which is the healthy direction.
19→17 iroh.net_report uses iroh.net_report.report✕
- Connections
- 2 pairs of types, where a type in iroh.net_report uses a type in iroh.net_report.report.
- The types involved
iroh.net_report.Client→iroh.net_report.report.Reportiroh.net_report.Reports→iroh.net_report.report.Report
- Direction
- iroh.net_report uses iroh.net_report.report, so a change to iroh.net_report.report can break iroh.net_report, while a change to iroh.net_report can't break iroh.net_report.report.
- Position
- Below the diagonal: iroh.net_report uses a module listed above it, which is the healthy direction.
19→28 iroh.net_report uses iroh.endpoint.connection part of a loop✕
- Connections
- 1 pair of types, where a type in iroh.net_report uses a type in iroh.endpoint.connection.
- The types involved
iroh.net_report.QadConn→iroh.endpoint.connection.Connection
- Direction
- iroh.net_report uses iroh.endpoint.connection, so a change to iroh.endpoint.connection can break iroh.net_report, while a change to iroh.net_report can't break iroh.endpoint.connection.
- 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.
20→17 iroh.socket.transports.ip uses iroh.net_report.report✕
- Connections
- 1 pair of types, where a type in iroh.socket.transports.ip uses a type in iroh.net_report.report.
- The types involved
iroh.socket.transports.ip.IpNetworkChangeSender→iroh.net_report.report.Report
- Direction
- iroh.socket.transports.ip uses iroh.net_report.report, so a change to iroh.net_report.report can break iroh.socket.transports.ip, while a change to iroh.socket.transports.ip can't break iroh.net_report.report.
- Position
- Below the diagonal: iroh.socket.transports.ip uses a module listed above it, which is the healthy direction.
20→25 iroh.socket.transports.ip uses iroh.socket.transports part of a loop✕
- Connections
- 1 pair of types, where a type in iroh.socket.transports.ip uses a type in iroh.socket.transports.
- The types involved
iroh.socket.transports.ip.IpSender→iroh.socket.transports.Transmit
- Direction
- iroh.socket.transports.ip uses iroh.socket.transports, so a change to iroh.socket.transports can break iroh.socket.transports.ip, while a change to iroh.socket.transports.ip can't break iroh.socket.transports.
- 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.
21→2 iroh.socket uses iroh_base.key✕
- Connections
- 1 pair of types, where a type in iroh.socket uses a type in iroh_base.key.
- The types involved
iroh.socket.Options→iroh_base.key.SecretKey
- Direction
- iroh.socket uses iroh_base.key, so a change to iroh_base.key can break iroh.socket, while a change to iroh.socket can't break iroh_base.key.
- Position
- Below the diagonal: iroh.socket uses a module listed above it, which is the healthy direction.
21→3 iroh.socket uses iroh_base.relay_url✕
- Connections
- 2 pairs of types, where a type in iroh.socket uses a type in iroh_base.relay_url.
- The types involved
iroh.socket.EndpointInner→iroh_base.relay_url.RelayUrliroh.socket.Socket→iroh_base.relay_url.RelayUrl
- Direction
- iroh.socket uses iroh_base.relay_url, so a change to iroh_base.relay_url can break iroh.socket, while a change to iroh.socket can't break iroh_base.relay_url.
- Position
- Below the diagonal: iroh.socket uses a module listed above it, which is the healthy direction.
21→5 iroh.socket uses iroh.tls✕
- Connections
- 1 pair of types, where a type in iroh.socket uses a type in iroh.tls.
- The types involved
iroh.socket.StaticConfig→iroh.tls.TlsConfig
- Direction
- iroh.socket uses iroh.tls, so a change to iroh.tls can break iroh.socket, while a change to iroh.socket can't break iroh.tls.
- Position
- Below the diagonal: iroh.socket uses a module listed above it, which is the healthy direction.
21→6 iroh.socket uses iroh_dns.dns✕
- Connections
- 2 pairs of types, where a type in iroh.socket uses a type in iroh_dns.dns.
- The types involved
iroh.socket.Options→iroh_dns.dns.DnsResolveriroh.socket.Socket→iroh_dns.dns.DnsResolver
- Direction
- iroh.socket uses iroh_dns.dns, so a change to iroh_dns.dns can break iroh.socket, while a change to iroh.socket can't break iroh_dns.dns.
- Position
- Below the diagonal: iroh.socket uses a module listed above it, which is the healthy direction.
21→8 iroh.socket uses iroh_relay.client.conn✕
- Connections
- 1 pair of types, where a type in iroh.socket uses a type in iroh_relay.client.conn.
- The types involved
iroh.socket.RemoteStateActorStoppedError→iroh_relay.client.conn.SendError
- Direction
- iroh.socket uses iroh_relay.client.conn, so a change to iroh_relay.client.conn can break iroh.socket, while a change to iroh.socket can't break iroh_relay.client.conn.
- Position
- Below the diagonal: iroh.socket uses a module listed above it, which is the healthy direction.
21→9 iroh.socket uses iroh_relay.relay_map✕
- Connections
- 3 pairs of types, where a type in iroh.socket uses a type in iroh_relay.relay_map.
- The types involved
iroh.socket.DirectAddrUpdateState→iroh_relay.relay_map.RelayMapiroh.socket.EndpointInner→iroh_relay.relay_map.RelayConfigiroh.socket.Socket→iroh_relay.relay_map.RelayMap
- Direction
- iroh.socket uses iroh_relay.relay_map, so a change to iroh_relay.relay_map can break iroh.socket, while a change to iroh.socket can't break iroh_relay.relay_map.
- Position
- Below the diagonal: iroh.socket uses a module listed above it, which is the healthy direction.
21→10 iroh.socket uses iroh_dns.endpoint_info✕
- Connections
- 2 pairs of types, where a type in iroh.socket uses a type in iroh_dns.endpoint_info.
- The types involved
iroh.socket.Options→iroh_dns.endpoint_info.UserDatairoh.socket.Socket→iroh_dns.endpoint_info.UserData
- Direction
- iroh.socket uses iroh_dns.endpoint_info, so a change to iroh_dns.endpoint_info can break iroh.socket, while a change to iroh.socket can't break iroh_dns.endpoint_info.
- Position
- Below the diagonal: iroh.socket uses a module listed above it, which is the healthy direction.
21→12 iroh.socket uses iroh_base.endpoint_addr✕
- Connections
- 1 pair of types, where a type in iroh.socket uses a type in iroh_base.endpoint_addr.
- The types involved
iroh.socket.EndpointInner→iroh_base.endpoint_addr.EndpointAddr
- Direction
- iroh.socket uses iroh_base.endpoint_addr, so a change to iroh_base.endpoint_addr can break iroh.socket, while a change to iroh.socket can't break iroh_base.endpoint_addr.
- Position
- Below the diagonal: iroh.socket uses a module listed above it, which is the healthy direction.
21→13 iroh.socket uses iroh.socket.remote_map.remote_state.path_watcher✕
- Connections
- 1 pair of types, where a type in iroh.socket uses a type in iroh.socket.remote_map.remote_state.path_watcher.
- The types involved
iroh.socket.socket$module→iroh.socket.remote_map.remote_state.path_watcher.State
- Direction
- iroh.socket uses iroh.socket.remote_map.remote_state.path_watcher, so a change to iroh.socket.remote_map.remote_state.path_watcher can break iroh.socket, while a change to iroh.socket can't break iroh.socket.remote_map.remote_state.path_watcher.
- Position
- Below the diagonal: iroh.socket uses a module listed above it, which is the healthy direction.
21→14 iroh.socket uses iroh.net_report.reportgen✕
- Connections
- 2 pairs of types, where a type in iroh.socket uses a type in iroh.net_report.reportgen.
- The types involved
iroh.socket.DirectAddrUpdateState→iroh.net_report.reportgen.Clientiroh.socket.DirectAddrUpdateState→iroh.net_report.reportgen.IfStateDetails
- Direction
- iroh.socket uses iroh.net_report.reportgen, so a change to iroh.net_report.reportgen can break iroh.socket, while a change to iroh.socket can't break iroh.net_report.reportgen.
- Position
- Below the diagonal: iroh.socket uses a module listed above it, which is the healthy direction.
21→15 iroh.socket uses iroh.socket.remote_map.remote_state✕
- Connections
- 1 pair of types, where a type in iroh.socket uses a type in iroh.socket.remote_map.remote_state.
- The types involved
iroh.socket.Socket→iroh.socket.remote_map.remote_state.RemoteStateMessage
- Direction
- iroh.socket uses iroh.socket.remote_map.remote_state, so a change to iroh.socket.remote_map.remote_state can break iroh.socket, while a change to iroh.socket can't break iroh.socket.remote_map.remote_state.
- Position
- Below the diagonal: iroh.socket uses a module listed above it, which is the healthy direction.
21→16 iroh.socket uses iroh.net_report.options.imp✕
- Connections
- 1 pair of types, where a type in iroh.socket uses a type in iroh.net_report.options.imp.
- The types involved
iroh.socket.EndpointInner→iroh.net_report.options.imp.Options
- Direction
- iroh.socket uses iroh.net_report.options.imp, so a change to iroh.net_report.options.imp can break iroh.socket, while a change to iroh.socket can't break iroh.net_report.options.imp.
- Position
- Below the diagonal: iroh.socket uses a module listed above it, which is the healthy direction.
21→17 iroh.socket uses iroh.net_report.report✕
- Connections
- 1 pair of types, where a type in iroh.socket uses a type in iroh.net_report.report.
- The types involved
iroh.socket.Actor→iroh.net_report.report.Report
- Direction
- iroh.socket uses iroh.net_report.report, so a change to iroh.net_report.report can break iroh.socket, while a change to iroh.socket can't break iroh.net_report.report.
- Position
- Below the diagonal: iroh.socket uses a module listed above it, which is the healthy direction.
21→18 iroh.socket uses iroh.socket.remote_map✕
- Connections
- 2 pairs of types, where a type in iroh.socket uses a type in iroh.socket.remote_map.
- The types involved
iroh.socket.Actor→iroh.socket.remote_map.RemoteMapiroh.socket.Socket→iroh.socket.remote_map.MappedAddrs
- Direction
- iroh.socket uses iroh.socket.remote_map, so a change to iroh.socket.remote_map can break iroh.socket, while a change to iroh.socket can't break iroh.socket.remote_map.
- Position
- Below the diagonal: iroh.socket uses a module listed above it, which is the healthy direction.
21→19 iroh.socket uses iroh.net_report✕
- Connections
- 1 pair of types, where a type in iroh.socket uses a type in iroh.net_report.
- The types involved
iroh.socket.Options→iroh.net_report.NetReportConfig
- Direction
- iroh.socket uses iroh.net_report, so a change to iroh.net_report can break iroh.socket, while a change to iroh.socket can't break iroh.net_report.
- Position
- Below the diagonal: iroh.socket uses a module listed above it, which is the healthy direction.
21→25 iroh.socket uses iroh.socket.transports part of a loop✕
- Connections
- 7 pairs of types, where a type in iroh.socket uses a type in iroh.socket.transports.
- The types involved
iroh.socket.Actor→iroh.socket.transports.NetworkChangeSenderiroh.socket.DirectAddrUpdateState→iroh.socket.transports.Senderiroh.socket.EndpointInner→iroh.socket.transports.Senderiroh.socket.Options→iroh.socket.transports.TransportConfigiroh.socket.Socket→iroh.socket.transports.Addriroh.socket.Socket→iroh.socket.transports.LocalTransportAddriroh.socket.StaticConfig→iroh.socket.transports.TransportConfig
- Direction
- iroh.socket uses iroh.socket.transports, so a change to iroh.socket.transports can break iroh.socket, while a change to iroh.socket can't break iroh.socket.transports.
- 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.
21→26 iroh.socket uses iroh.endpoint.quic part of a loop✕
- Connections
- 3 pairs of types, where a type in iroh.socket uses a type in iroh.endpoint.quic.
- The types involved
iroh.socket.Options→iroh.endpoint.quic.ServerConfigiroh.socket.StaticConfig→iroh.endpoint.quic.QuicTransportConfigiroh.socket.StaticConfig→iroh.endpoint.quic.ServerConfig
- Direction
- iroh.socket uses iroh.endpoint.quic, so a change to iroh.endpoint.quic can break iroh.socket, while a change to iroh.socket can't break iroh.endpoint.quic.
- 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.
21→28 iroh.socket uses iroh.endpoint.connection part of a loop✕
- Connections
- 1 pair of types, where a type in iroh.socket uses a type in iroh.endpoint.connection.
- The types involved
iroh.socket.EndpointInner→iroh.endpoint.connection.Connection
- Direction
- iroh.socket uses iroh.endpoint.connection, so a change to iroh.endpoint.connection can break iroh.socket, while a change to iroh.socket can't break iroh.endpoint.connection.
- 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.
21→30 iroh.socket uses iroh.endpoint part of a loop✕
- Connections
- 2 pairs of types, where a type in iroh.socket uses a type in iroh.endpoint.
- The types involved
iroh.socket.Actor→iroh.endpoint.Endpointiroh.socket.EndpointInner→iroh.endpoint.Endpoint
- Direction
- iroh.socket uses iroh.endpoint, so a change to iroh.endpoint can break iroh.socket, while a change to iroh.socket can't break iroh.endpoint.
- 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.
21→31 iroh.socket uses iroh.address_lookup part of a loop✕
- Connections
- 1 pair of types, where a type in iroh.socket uses a type in iroh.address_lookup.
- The types involved
iroh.socket.Socket→iroh.address_lookup.AddressLookupServices
- Direction
- iroh.socket uses iroh.address_lookup, so a change to iroh.address_lookup can break iroh.socket, while a change to iroh.socket can't break iroh.address_lookup.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
22→2 iroh.socket.transports.relay.actor uses iroh_base.key✕
- Connections
- 2 pairs of types, where a type in iroh.socket.transports.relay.actor uses a type in iroh_base.key.
- The types involved
iroh.socket.transports.relay.actor.Config→iroh_base.key.SecretKeyiroh.socket.transports.relay.actor.RelayConnectionOptions→iroh_base.key.SecretKey
- Direction
- iroh.socket.transports.relay.actor uses iroh_base.key, so a change to iroh_base.key can break iroh.socket.transports.relay.actor, while a change to iroh.socket.transports.relay.actor can't break iroh_base.key.
- Position
- Below the diagonal: iroh.socket.transports.relay.actor uses a module listed above it, which is the healthy direction.
22→3 iroh.socket.transports.relay.actor uses iroh_base.relay_url✕
- Connections
- 6 pairs of types, where a type in iroh.socket.transports.relay.actor uses a type in iroh_base.relay_url.
- The types involved
iroh.socket.transports.relay.actor.ActiveRelayActor→iroh_base.relay_url.RelayUrliroh.socket.transports.relay.actor.ActiveRelayActorOptions→iroh_base.relay_url.RelayUrliroh.socket.transports.relay.actor.HomeRelayWatch→iroh_base.relay_url.RelayUrliroh.socket.transports.relay.actor.RelayActor→iroh_base.relay_url.RelayUrliroh.socket.transports.relay.actor.RelayRecvDatagram→iroh_base.relay_url.RelayUrliroh.socket.transports.relay.actor.RelaySendItem→iroh_base.relay_url.RelayUrl
- Direction
- iroh.socket.transports.relay.actor uses iroh_base.relay_url, so a change to iroh_base.relay_url can break iroh.socket.transports.relay.actor, while a change to iroh.socket.transports.relay.actor can't break iroh_base.relay_url.
- Position
- Below the diagonal: iroh.socket.transports.relay.actor uses a module listed above it, which is the healthy direction.
22→4 iroh.socket.transports.relay.actor uses iroh_relay.protos.relay✕
- Connections
- 3 pairs of types, where a type in iroh.socket.transports.relay.actor uses a type in iroh_relay.protos.relay.
- The types involved
iroh.socket.transports.relay.actor.ActiveRelayActor→iroh_relay.protos.relay.RelayToClientMsgiroh.socket.transports.relay.actor.RelayRecvDatagram→iroh_relay.protos.relay.Datagramsiroh.socket.transports.relay.actor.RelaySendItem→iroh_relay.protos.relay.Datagrams
- Direction
- iroh.socket.transports.relay.actor uses iroh_relay.protos.relay, so a change to iroh_relay.protos.relay can break iroh.socket.transports.relay.actor, while a change to iroh.socket.transports.relay.actor can't break iroh_relay.protos.relay.
- Position
- Below the diagonal: iroh.socket.transports.relay.actor uses a module listed above it, which is the healthy direction.
22→6 iroh.socket.transports.relay.actor uses iroh_dns.dns✕
- Connections
- 2 pairs of types, where a type in iroh.socket.transports.relay.actor uses a type in iroh_dns.dns.
- The types involved
iroh.socket.transports.relay.actor.Config→iroh_dns.dns.DnsResolveriroh.socket.transports.relay.actor.RelayConnectionOptions→iroh_dns.dns.DnsResolver
- Direction
- iroh.socket.transports.relay.actor uses iroh_dns.dns, so a change to iroh_dns.dns can break iroh.socket.transports.relay.actor, while a change to iroh.socket.transports.relay.actor can't break iroh_dns.dns.
- Position
- Below the diagonal: iroh.socket.transports.relay.actor uses a module listed above it, which is the healthy direction.
22→9 iroh.socket.transports.relay.actor uses iroh_relay.relay_map✕
- Connections
- 1 pair of types, where a type in iroh.socket.transports.relay.actor uses a type in iroh_relay.relay_map.
- The types involved
iroh.socket.transports.relay.actor.Config→iroh_relay.relay_map.RelayMap
- Direction
- iroh.socket.transports.relay.actor uses iroh_relay.relay_map, so a change to iroh_relay.relay_map can break iroh.socket.transports.relay.actor, while a change to iroh.socket.transports.relay.actor can't break iroh_relay.relay_map.
- Position
- Below the diagonal: iroh.socket.transports.relay.actor uses a module listed above it, which is the healthy direction.
22→11 iroh.socket.transports.relay.actor uses iroh_relay.client✕
- Connections
- 2 pairs of types, where a type in iroh.socket.transports.relay.actor uses a type in iroh_relay.client.
- The types involved
iroh.socket.transports.relay.actor.ActiveRelayActor→iroh_relay.client.ClientBuilderiroh.socket.transports.relay.actor.ActiveRelayActor→iroh_relay.client.ClientStream
- Direction
- iroh.socket.transports.relay.actor uses iroh_relay.client, so a change to iroh_relay.client can break iroh.socket.transports.relay.actor, while a change to iroh.socket.transports.relay.actor can't break iroh_relay.client.
- Position
- Below the diagonal: iroh.socket.transports.relay.actor uses a module listed above it, which is the healthy direction.
22→14 iroh.socket.transports.relay.actor uses iroh.net_report.reportgen✕
- Connections
- 1 pair of types, where a type in iroh.socket.transports.relay.actor uses a type in iroh.net_report.reportgen.
- The types involved
iroh.socket.transports.relay.actor.ActiveRelayActor→iroh.net_report.reportgen.Client
- Direction
- iroh.socket.transports.relay.actor uses iroh.net_report.reportgen, so a change to iroh.net_report.reportgen can break iroh.socket.transports.relay.actor, while a change to iroh.socket.transports.relay.actor can't break iroh.net_report.reportgen.
- Position
- Below the diagonal: iroh.socket.transports.relay.actor uses a module listed above it, which is the healthy direction.
22→17 iroh.socket.transports.relay.actor uses iroh.net_report.report✕
- Connections
- 1 pair of types, where a type in iroh.socket.transports.relay.actor uses a type in iroh.net_report.report.
- The types involved
iroh.socket.transports.relay.actor.RelayActor→iroh.net_report.report.Report
- Direction
- iroh.socket.transports.relay.actor uses iroh.net_report.report, so a change to iroh.net_report.report can break iroh.socket.transports.relay.actor, while a change to iroh.socket.transports.relay.actor can't break iroh.net_report.report.
- Position
- Below the diagonal: iroh.socket.transports.relay.actor uses a module listed above it, which is the healthy direction.
22→20 iroh.socket.transports.relay.actor uses iroh.socket.transports.ip✕
- Connections
- 1 pair of types, where a type in iroh.socket.transports.relay.actor uses a type in iroh.socket.transports.ip.
- The types involved
iroh.socket.transports.relay.actor.RelayActor→iroh.socket.transports.ip.Config
- Direction
- iroh.socket.transports.relay.actor uses iroh.socket.transports.ip, so a change to iroh.socket.transports.ip can break iroh.socket.transports.relay.actor, while a change to iroh.socket.transports.relay.actor can't break iroh.socket.transports.ip.
- Position
- Below the diagonal: iroh.socket.transports.relay.actor uses a module listed above it, which is the healthy direction.
22→25 iroh.socket.transports.relay.actor uses iroh.socket.transports part of a loop✕
- Connections
- 4 pairs of types, where a type in iroh.socket.transports.relay.actor uses a type in iroh.socket.transports.
- The types involved
iroh.socket.transports.relay.actor.ActiveRelayActor→iroh.socket.transports.Senderiroh.socket.transports.relay.actor.ActiveRelayActorOptions→iroh.socket.transports.Senderiroh.socket.transports.relay.actor.ActiveRelayHandle→iroh.socket.transports.Senderiroh.socket.transports.relay.actor.RelayActor→iroh.socket.transports.Sender
- Direction
- iroh.socket.transports.relay.actor uses iroh.socket.transports, so a change to iroh.socket.transports can break iroh.socket.transports.relay.actor, while a change to iroh.socket.transports.relay.actor can't break iroh.socket.transports.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
22→30 iroh.socket.transports.relay.actor uses iroh.endpoint part of a loop✕
- Connections
- 1 pair of types, where a type in iroh.socket.transports.relay.actor uses a type in iroh.endpoint.
- The types involved
iroh.socket.transports.relay.actor.HomeRelayWatch→iroh.endpoint.RelayStatus
- Direction
- iroh.socket.transports.relay.actor uses iroh.endpoint, so a change to iroh.endpoint can break iroh.socket.transports.relay.actor, while a change to iroh.socket.transports.relay.actor can't break iroh.endpoint.
- 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.
23→1 iroh_relay.server.clients uses iroh.address_lookup.metrics✕
- Connections
- 1 pair of types, where a type in iroh_relay.server.clients uses a type in iroh.address_lookup.metrics.
- The types involved
iroh_relay.server.clients.Clients→iroh.address_lookup.metrics.Metrics
- Direction
- iroh_relay.server.clients uses iroh.address_lookup.metrics, so a change to iroh.address_lookup.metrics can break iroh_relay.server.clients, while a change to iroh_relay.server.clients can't break iroh.address_lookup.metrics.
- Position
- Below the diagonal: iroh_relay.server.clients uses a module listed above it, which is the healthy direction.
23→4 iroh_relay.server.clients uses iroh_relay.protos.relay✕
- Connections
- 1 pair of types, where a type in iroh_relay.server.clients uses a type in iroh_relay.protos.relay.
- The types involved
iroh_relay.server.clients.Clients→iroh_relay.protos.relay.Datagrams
- Direction
- iroh_relay.server.clients uses iroh_relay.protos.relay, so a change to iroh_relay.protos.relay can break iroh_relay.server.clients, while a change to iroh_relay.server.clients can't break iroh_relay.protos.relay.
- Position
- Below the diagonal: iroh_relay.server.clients uses a module listed above it, which is the healthy direction.
23→6 iroh_relay.server.clients uses iroh_dns.dns✕
- Connections
- 1 pair of types, where a type in iroh_relay.server.clients uses a type in iroh_dns.dns.
- The types involved
iroh_relay.server.clients.Clients→iroh_dns.dns.Inner
- Direction
- iroh_relay.server.clients uses iroh_dns.dns, so a change to iroh_dns.dns can break iroh_relay.server.clients, while a change to iroh_relay.server.clients can't break iroh_dns.dns.
- Position
- Below the diagonal: iroh_relay.server.clients uses a module listed above it, which is the healthy direction.
23→14 iroh_relay.server.clients uses iroh.net_report.reportgen✕
- Connections
- 1 pair of types, where a type in iroh_relay.server.clients uses a type in iroh.net_report.reportgen.
- The types involved
iroh_relay.server.clients.ClientState→iroh.net_report.reportgen.Client
- Direction
- iroh_relay.server.clients uses iroh.net_report.reportgen, so a change to iroh.net_report.reportgen can break iroh_relay.server.clients, while a change to iroh_relay.server.clients can't break iroh.net_report.reportgen.
- Position
- Below the diagonal: iroh_relay.server.clients uses a module listed above it, which is the healthy direction.
23→20 iroh_relay.server.clients uses iroh.socket.transports.ip✕
- Connections
- 1 pair of types, where a type in iroh_relay.server.clients uses a type in iroh.socket.transports.ip.
- The types involved
iroh_relay.server.clients.Clients→iroh.socket.transports.ip.Config
- Direction
- iroh_relay.server.clients uses iroh.socket.transports.ip, so a change to iroh.socket.transports.ip can break iroh_relay.server.clients, while a change to iroh_relay.server.clients can't break iroh.socket.transports.ip.
- Position
- Below the diagonal: iroh_relay.server.clients uses a module listed above it, which is the healthy direction.
23→37 iroh_relay.server.clients uses iroh_relay.server part of a loop✕
- Connections
- 2 pairs of types, where a type in iroh_relay.server.clients uses a type in iroh_relay.server.
- The types involved
iroh_relay.server.clients.Clients→iroh_relay.server.ConnectionIdiroh_relay.server.clients.Clients→iroh_relay.server.OnDisconnectGuard
- Direction
- iroh_relay.server.clients uses iroh_relay.server, so a change to iroh_relay.server can break iroh_relay.server.clients, while a change to iroh_relay.server.clients can't break iroh_relay.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→3 iroh.socket.transports.relay uses iroh_base.relay_url✕
- Connections
- 1 pair of types, where a type in iroh.socket.transports.relay uses a type in iroh_base.relay_url.
- The types involved
iroh.socket.transports.relay.RelaySender→iroh_base.relay_url.RelayUrl
- Direction
- iroh.socket.transports.relay uses iroh_base.relay_url, so a change to iroh_base.relay_url can break iroh.socket.transports.relay, while a change to iroh.socket.transports.relay can't break iroh_base.relay_url.
- Position
- Below the diagonal: iroh.socket.transports.relay uses a module listed above it, which is the healthy direction.
24→4 iroh.socket.transports.relay uses iroh_relay.protos.relay✕
- Connections
- 1 pair of types, where a type in iroh.socket.transports.relay uses a type in iroh_relay.protos.relay.
- The types involved
iroh.socket.transports.relay.relay$module→iroh_relay.protos.relay.Datagrams
- Direction
- iroh.socket.transports.relay uses iroh_relay.protos.relay, so a change to iroh_relay.protos.relay can break iroh.socket.transports.relay, while a change to iroh.socket.transports.relay can't break iroh_relay.protos.relay.
- Position
- Below the diagonal: iroh.socket.transports.relay uses a module listed above it, which is the healthy direction.
24→17 iroh.socket.transports.relay uses iroh.net_report.report✕
- Connections
- 1 pair of types, where a type in iroh.socket.transports.relay uses a type in iroh.net_report.report.
- The types involved
iroh.socket.transports.relay.RelayNetworkChangeSender→iroh.net_report.report.Report
- Direction
- iroh.socket.transports.relay uses iroh.net_report.report, so a change to iroh.net_report.report can break iroh.socket.transports.relay, while a change to iroh.socket.transports.relay can't break iroh.net_report.report.
- Position
- Below the diagonal: iroh.socket.transports.relay uses a module listed above it, which is the healthy direction.
24→22 iroh.socket.transports.relay uses iroh.socket.transports.relay.actor✕
- Connections
- 3 pairs of types, where a type in iroh.socket.transports.relay uses a type in iroh.socket.transports.relay.actor.
- The types involved
iroh.socket.transports.relay.RelayNetworkChangeSender→iroh.socket.transports.relay.actor.RelayActorMessageiroh.socket.transports.relay.RelayTransport→iroh.socket.transports.relay.actor.HomeRelayWatchiroh.socket.transports.relay.RelayTransport→iroh.socket.transports.relay.actor.RelayRecvDatagram
- Direction
- iroh.socket.transports.relay uses iroh.socket.transports.relay.actor, so a change to iroh.socket.transports.relay.actor can break iroh.socket.transports.relay, while a change to iroh.socket.transports.relay can't break iroh.socket.transports.relay.actor.
- Position
- Below the diagonal: iroh.socket.transports.relay uses a module listed above it, which is the healthy direction.
24→25 iroh.socket.transports.relay uses iroh.socket.transports part of a loop✕
- Connections
- 4 pairs of types, where a type in iroh.socket.transports.relay uses a type in iroh.socket.transports.
- The types involved
iroh.socket.transports.relay.RelayNetworkChangeSender→iroh.socket.transports.Senderiroh.socket.transports.relay.RelaySender→iroh.socket.transports.Transmitiroh.socket.transports.relay.RelayTransport→iroh.socket.transports.Senderiroh.socket.transports.relay.relay$module→iroh.socket.transports.Transmit
- Direction
- iroh.socket.transports.relay uses iroh.socket.transports, so a change to iroh.socket.transports can break iroh.socket.transports.relay, while a change to iroh.socket.transports.relay can't break iroh.socket.transports.
- 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.
25→12 iroh.socket.transports uses iroh_base.endpoint_addr✕
- Connections
- 3 pairs of types, where a type in iroh.socket.transports uses a type in iroh_base.endpoint_addr.
- The types involved
iroh.socket.transports.Addr→iroh_base.endpoint_addr.CustomAddriroh.socket.transports.Addr→iroh_base.endpoint_addr.TransportAddriroh.socket.transports.RecvInfo→iroh_base.endpoint_addr.CustomAddr
- Direction
- iroh.socket.transports uses iroh_base.endpoint_addr, so a change to iroh_base.endpoint_addr can break iroh.socket.transports, while a change to iroh.socket.transports can't break iroh_base.endpoint_addr.
- Position
- Below the diagonal: iroh.socket.transports uses a module listed above it, which is the healthy direction.
25→17 iroh.socket.transports uses iroh.net_report.report✕
- Connections
- 1 pair of types, where a type in iroh.socket.transports uses a type in iroh.net_report.report.
- The types involved
iroh.socket.transports.NetworkChangeSender→iroh.net_report.report.Report
- Direction
- iroh.socket.transports uses iroh.net_report.report, so a change to iroh.net_report.report can break iroh.socket.transports, while a change to iroh.socket.transports can't break iroh.net_report.report.
- Position
- Below the diagonal: iroh.socket.transports uses a module listed above it, which is the healthy direction.
25→20 iroh.socket.transports uses iroh.socket.transports.ip✕
- Connections
- 3 pairs of types, where a type in iroh.socket.transports uses a type in iroh.socket.transports.ip.
- The types involved
iroh.socket.transports.NetworkChangeSender→iroh.socket.transports.ip.IpNetworkChangeSenderiroh.socket.transports.Transports→iroh.socket.transports.ip.IpTransportsiroh.socket.transports.TransportsSender→iroh.socket.transports.ip.IpTransportsSender
- Direction
- iroh.socket.transports uses iroh.socket.transports.ip, so a change to iroh.socket.transports.ip can break iroh.socket.transports, while a change to iroh.socket.transports can't break iroh.socket.transports.ip.
- Position
- Below the diagonal: iroh.socket.transports uses a module listed above it, which is the healthy direction.
25→21 iroh.socket.transports uses iroh.socket✕
- Connections
- 3 pairs of types, where a type in iroh.socket.transports uses a type in iroh.socket.
- The types involved
iroh.socket.transports.Sender→iroh.socket.Socketiroh.socket.transports.Transport→iroh.socket.Socketiroh.socket.transports.Transports→iroh.socket.Socket
- Direction
- iroh.socket.transports uses iroh.socket, so a change to iroh.socket can break iroh.socket.transports, while a change to iroh.socket.transports can't break iroh.socket.
- Position
- Below the diagonal: iroh.socket.transports uses a module listed above it, which is the healthy direction.
25→24 iroh.socket.transports uses iroh.socket.transports.relay✕
- Connections
- 3 pairs of types, where a type in iroh.socket.transports uses a type in iroh.socket.transports.relay.
- The types involved
iroh.socket.transports.NetworkChangeSender→iroh.socket.transports.relay.RelayNetworkChangeSenderiroh.socket.transports.Transports→iroh.socket.transports.relay.RelayTransportiroh.socket.transports.TransportsSender→iroh.socket.transports.relay.RelaySender
- Direction
- iroh.socket.transports uses iroh.socket.transports.relay, so a change to iroh.socket.transports.relay can break iroh.socket.transports, while a change to iroh.socket.transports can't break iroh.socket.transports.relay.
- Position
- Below the diagonal: iroh.socket.transports uses a module listed above it, which is the healthy direction.
26→25 iroh.endpoint.quic uses iroh.socket.transports✕
- Connections
- 2 pairs of types, where a type in iroh.endpoint.quic uses a type in iroh.socket.transports.
- The types involved
iroh.endpoint.quic.QuicTransportConfig→iroh.socket.transports.TransportConfigiroh.endpoint.quic.QuicTransportConfigBuilder→iroh.socket.transports.TransportConfig
- Direction
- iroh.endpoint.quic uses iroh.socket.transports, so a change to iroh.socket.transports can break iroh.endpoint.quic, while a change to iroh.endpoint.quic can't break iroh.socket.transports.
- Position
- Below the diagonal: iroh.endpoint.quic uses a module listed above it, which is the healthy direction.
27→1 iroh_dns_server.store.signed_packets uses iroh.address_lookup.metrics✕
- Connections
- 2 pairs of types, where a type in iroh_dns_server.store.signed_packets uses a type in iroh.address_lookup.metrics.
- The types involved
iroh_dns_server.store.signed_packets.Actor→iroh.address_lookup.metrics.Metricsiroh_dns_server.store.signed_packets.SignedPacketStore→iroh.address_lookup.metrics.Metrics
- Direction
- iroh_dns_server.store.signed_packets uses iroh.address_lookup.metrics, so a change to iroh.address_lookup.metrics can break iroh_dns_server.store.signed_packets, while a change to iroh_dns_server.store.signed_packets can't break iroh.address_lookup.metrics.
- Position
- Below the diagonal: iroh_dns_server.store.signed_packets uses a module listed above it, which is the healthy direction.
27→7 iroh_dns_server.store.signed_packets uses iroh_dns.pkarr✕
- Connections
- 3 pairs of types, where a type in iroh_dns_server.store.signed_packets uses a type in iroh_dns.pkarr.
- The types involved
iroh_dns_server.store.signed_packets.SignedPacketStore→iroh_dns.pkarr.SignedPacketiroh_dns_server.store.signed_packets.signed_packets$module→iroh_dns.pkarr.SignedPacketiroh_dns_server.store.signed_packets.signed_packets$module→iroh_dns.pkarr.Timestamp
- Direction
- iroh_dns_server.store.signed_packets uses iroh_dns.pkarr, so a change to iroh_dns.pkarr can break iroh_dns_server.store.signed_packets, while a change to iroh_dns_server.store.signed_packets can't break iroh_dns.pkarr.
- Position
- Below the diagonal: iroh_dns_server.store.signed_packets uses a module listed above it, which is the healthy direction.
27→16 iroh_dns_server.store.signed_packets uses iroh.net_report.options.imp✕
- Connections
- 3 pairs of types, where a type in iroh_dns_server.store.signed_packets uses a type in iroh.net_report.options.imp.
- The types involved
iroh_dns_server.store.signed_packets.Actor→iroh.net_report.options.imp.Optionsiroh_dns_server.store.signed_packets.SignedPacketStore→iroh.net_report.options.imp.Optionsiroh_dns_server.store.signed_packets.signed_packets$module→iroh.net_report.options.imp.Options
- Direction
- iroh_dns_server.store.signed_packets uses iroh.net_report.options.imp, so a change to iroh.net_report.options.imp can break iroh_dns_server.store.signed_packets, while a change to iroh_dns_server.store.signed_packets can't break iroh.net_report.options.imp.
- Position
- Below the diagonal: iroh_dns_server.store.signed_packets uses a module listed above it, which is the healthy direction.
27→25 iroh_dns_server.store.signed_packets uses iroh.socket.transports✕
- Connections
- 2 pairs of types, where a type in iroh_dns_server.store.signed_packets uses a type in iroh.socket.transports.
- The types involved
iroh_dns_server.store.signed_packets.SignedPacketStore→iroh.socket.transports.Senderiroh_dns_server.store.signed_packets.signed_packets$module→iroh.socket.transports.Sender
- Direction
- iroh_dns_server.store.signed_packets uses iroh.socket.transports, so a change to iroh.socket.transports can break iroh_dns_server.store.signed_packets, while a change to iroh_dns_server.store.signed_packets can't break iroh.socket.transports.
- Position
- Below the diagonal: iroh_dns_server.store.signed_packets uses a module listed above it, which is the healthy direction.
28→13 iroh.endpoint.connection uses iroh.socket.remote_map.remote_state.path_watcher✕
- Connections
- 6 pairs of types, where a type in iroh.endpoint.connection uses a type in iroh.socket.remote_map.remote_state.path_watcher.
- The types involved
iroh.endpoint.connection.Connection→iroh.socket.remote_map.remote_state.path_watcher.PathEventStreamiroh.endpoint.connection.Connection→iroh.socket.remote_map.remote_state.path_watcher.PathListiroh.endpoint.connection.Connection→iroh.socket.remote_map.remote_state.path_watcher.PathListStreamiroh.endpoint.connection.HandshakeCompletedData→iroh.socket.remote_map.remote_state.path_watcher.PathStateReceiveriroh.endpoint.connection.IncomingZeroRttData→iroh.socket.remote_map.remote_state.path_watcher.Sharediroh.endpoint.connection.OutgoingZeroRttData→iroh.socket.remote_map.remote_state.path_watcher.Shared
- Direction
- iroh.endpoint.connection uses iroh.socket.remote_map.remote_state.path_watcher, so a change to iroh.socket.remote_map.remote_state.path_watcher can break iroh.endpoint.connection, while a change to iroh.endpoint.connection can't break iroh.socket.remote_map.remote_state.path_watcher.
- Position
- Below the diagonal: iroh.endpoint.connection uses a module listed above it, which is the healthy direction.
28→25 iroh.endpoint.connection uses iroh.socket.transports✕
- Connections
- 2 pairs of types, where a type in iroh.endpoint.connection uses a type in iroh.socket.transports.
- The types involved
iroh.endpoint.connection.Incoming→iroh.socket.transports.LocalTransportAddriroh.endpoint.connection.IncomingAddr→iroh.socket.transports.Addr
- Direction
- iroh.endpoint.connection uses iroh.socket.transports, so a change to iroh.socket.transports can break iroh.endpoint.connection, while a change to iroh.endpoint.connection can't break iroh.socket.transports.
- Position
- Below the diagonal: iroh.endpoint.connection uses a module listed above it, which is the healthy direction.
28→26 iroh.endpoint.connection uses iroh.endpoint.quic✕
- Connections
- 1 pair of types, where a type in iroh.endpoint.connection uses a type in iroh.endpoint.quic.
- The types involved
iroh.endpoint.connection.Incoming→iroh.endpoint.quic.ServerConfig
- Direction
- iroh.endpoint.connection uses iroh.endpoint.quic, so a change to iroh.endpoint.quic can break iroh.endpoint.connection, while a change to iroh.endpoint.connection can't break iroh.endpoint.quic.
- Position
- Below the diagonal: iroh.endpoint.connection uses a module listed above it, which is the healthy direction.
28→30 iroh.endpoint.connection uses iroh.endpoint part of a loop✕
- Connections
- 6 pairs of types, where a type in iroh.endpoint.connection uses a type in iroh.endpoint.
- The types involved
iroh.endpoint.connection.Accept→iroh.endpoint.Endpointiroh.endpoint.connection.Accepting→iroh.endpoint.Endpointiroh.endpoint.connection.Connecting→iroh.endpoint.Endpointiroh.endpoint.connection.Incoming→iroh.endpoint.Endpointiroh.endpoint.connection.RetryError→iroh.endpoint.Endpointiroh.endpoint.connection.connection$module→iroh.endpoint.Endpoint
- Direction
- iroh.endpoint.connection uses iroh.endpoint, so a change to iroh.endpoint can break iroh.endpoint.connection, while a change to iroh.endpoint.connection can't break iroh.endpoint.
- 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.
29→1 iroh_dns_server.store uses iroh.address_lookup.metrics✕
- Connections
- 2 pairs of types, where a type in iroh_dns_server.store uses a type in iroh.address_lookup.metrics.
- The types involved
iroh_dns_server.store.ZoneCache→iroh.address_lookup.metrics.Metricsiroh_dns_server.store.ZoneStore→iroh.address_lookup.metrics.Metrics
- Direction
- iroh_dns_server.store uses iroh.address_lookup.metrics, so a change to iroh.address_lookup.metrics can break iroh_dns_server.store, while a change to iroh_dns_server.store can't break iroh.address_lookup.metrics.
- Position
- Below the diagonal: iroh_dns_server.store uses a module listed above it, which is the healthy direction.
29→7 iroh_dns_server.store uses iroh_dns.pkarr✕
- Connections
- 4 pairs of types, where a type in iroh_dns_server.store uses a type in iroh_dns.pkarr.
- The types involved
iroh_dns_server.store.CachedZone→iroh_dns.pkarr.SignedPacketiroh_dns_server.store.CachedZone→iroh_dns.pkarr.Timestampiroh_dns_server.store.ZoneCache→iroh_dns.pkarr.SignedPacketiroh_dns_server.store.ZoneStore→iroh_dns.pkarr.SignedPacket
- Direction
- iroh_dns_server.store uses iroh_dns.pkarr, so a change to iroh_dns.pkarr can break iroh_dns_server.store, while a change to iroh_dns_server.store can't break iroh_dns.pkarr.
- Position
- Below the diagonal: iroh_dns_server.store uses a module listed above it, which is the healthy direction.
29→16 iroh_dns_server.store uses iroh.net_report.options.imp✕
- Connections
- 1 pair of types, where a type in iroh_dns_server.store uses a type in iroh.net_report.options.imp.
- The types involved
iroh_dns_server.store.ZoneStore→iroh.net_report.options.imp.Options
- Direction
- iroh_dns_server.store uses iroh.net_report.options.imp, so a change to iroh.net_report.options.imp can break iroh_dns_server.store, while a change to iroh_dns_server.store can't break iroh.net_report.options.imp.
- Position
- Below the diagonal: iroh_dns_server.store uses a module listed above it, which is the healthy direction.
29→27 iroh_dns_server.store uses iroh_dns_server.store.signed_packets✕
- Connections
- 1 pair of types, where a type in iroh_dns_server.store uses a type in iroh_dns_server.store.signed_packets.
- The types involved
iroh_dns_server.store.ZoneStore→iroh_dns_server.store.signed_packets.SignedPacketStore
- Direction
- iroh_dns_server.store uses iroh_dns_server.store.signed_packets, so a change to iroh_dns_server.store.signed_packets can break iroh_dns_server.store, while a change to iroh_dns_server.store can't break iroh_dns_server.store.signed_packets.
- Position
- Below the diagonal: iroh_dns_server.store uses a module listed above it, which is the healthy direction.
30→2 iroh.endpoint uses iroh_base.key✕
- Connections
- 2 pairs of types, where a type in iroh.endpoint uses a type in iroh_base.key.
- The types involved
iroh.endpoint.Builder→iroh_base.key.SecretKeyiroh.endpoint.Endpoint→iroh_base.key.SecretKey
- Direction
- iroh.endpoint uses iroh_base.key, so a change to iroh_base.key can break iroh.endpoint, while a change to iroh.endpoint can't break iroh_base.key.
- Position
- Below the diagonal: iroh.endpoint uses a module listed above it, which is the healthy direction.
30→3 iroh.endpoint uses iroh_base.relay_url✕
- Connections
- 2 pairs of types, where a type in iroh.endpoint uses a type in iroh_base.relay_url.
- The types involved
iroh.endpoint.Endpoint→iroh_base.relay_url.RelayUrliroh.endpoint.RelayStatus→iroh_base.relay_url.RelayUrl
- Direction
- iroh.endpoint uses iroh_base.relay_url, so a change to iroh_base.relay_url can break iroh.endpoint, while a change to iroh.endpoint can't break iroh_base.relay_url.
- Position
- Below the diagonal: iroh.endpoint uses a module listed above it, which is the healthy direction.
30→6 iroh.endpoint uses iroh_dns.dns✕
- Connections
- 1 pair of types, where a type in iroh.endpoint uses a type in iroh_dns.dns.
- The types involved
iroh.endpoint.Builder→iroh_dns.dns.DnsResolver
- Direction
- iroh.endpoint uses iroh_dns.dns, so a change to iroh_dns.dns can break iroh.endpoint, while a change to iroh.endpoint can't break iroh_dns.dns.
- Position
- Below the diagonal: iroh.endpoint uses a module listed above it, which is the healthy direction.
30→9 iroh.endpoint uses iroh_relay.relay_map✕
- Connections
- 2 pairs of types, where a type in iroh.endpoint uses a type in iroh_relay.relay_map.
- The types involved
iroh.endpoint.Endpoint→iroh_relay.relay_map.RelayConfigiroh.endpoint.RelayMode→iroh_relay.relay_map.RelayMap
- Direction
- iroh.endpoint uses iroh_relay.relay_map, so a change to iroh_relay.relay_map can break iroh.endpoint, while a change to iroh.endpoint can't break iroh_relay.relay_map.
- Position
- Below the diagonal: iroh.endpoint uses a module listed above it, which is the healthy direction.
30→10 iroh.endpoint uses iroh_dns.endpoint_info✕
- Connections
- 3 pairs of types, where a type in iroh.endpoint uses a type in iroh_dns.endpoint_info.
- The types involved
iroh.endpoint.Builder→iroh_dns.endpoint_info.AddrFilteriroh.endpoint.Builder→iroh_dns.endpoint_info.UserDatairoh.endpoint.Endpoint→iroh_dns.endpoint_info.UserData
- Direction
- iroh.endpoint uses iroh_dns.endpoint_info, so a change to iroh_dns.endpoint_info can break iroh.endpoint, while a change to iroh.endpoint can't break iroh_dns.endpoint_info.
- Position
- Below the diagonal: iroh.endpoint uses a module listed above it, which is the healthy direction.
30→12 iroh.endpoint uses iroh_base.endpoint_addr✕
- Connections
- 1 pair of types, where a type in iroh.endpoint uses a type in iroh_base.endpoint_addr.
- The types involved
iroh.endpoint.Endpoint→iroh_base.endpoint_addr.EndpointAddr
- Direction
- iroh.endpoint uses iroh_base.endpoint_addr, so a change to iroh_base.endpoint_addr can break iroh.endpoint, while a change to iroh.endpoint can't break iroh_base.endpoint_addr.
- Position
- Below the diagonal: iroh.endpoint uses a module listed above it, which is the healthy direction.
30→19 iroh.endpoint uses iroh.net_report✕
- Connections
- 1 pair of types, where a type in iroh.endpoint uses a type in iroh.net_report.
- The types involved
iroh.endpoint.Builder→iroh.net_report.NetReportConfig
- Direction
- iroh.endpoint uses iroh.net_report, so a change to iroh.net_report can break iroh.endpoint, while a change to iroh.endpoint can't break iroh.net_report.
- Position
- Below the diagonal: iroh.endpoint uses a module listed above it, which is the healthy direction.
30→21 iroh.endpoint uses iroh.socket✕
- Connections
- 1 pair of types, where a type in iroh.endpoint uses a type in iroh.socket.
- The types involved
iroh.endpoint.Endpoint→iroh.socket.EndpointInner
- Direction
- iroh.endpoint uses iroh.socket, so a change to iroh.socket can break iroh.endpoint, while a change to iroh.endpoint can't break iroh.socket.
- Position
- Below the diagonal: iroh.endpoint uses a module listed above it, which is the healthy direction.
30→22 iroh.endpoint uses iroh.socket.transports.relay.actor✕
- Connections
- 1 pair of types, where a type in iroh.endpoint uses a type in iroh.socket.transports.relay.actor.
- The types involved
iroh.endpoint.RelayStatus→iroh.socket.transports.relay.actor.RelayConnectionState
- Direction
- iroh.endpoint uses iroh.socket.transports.relay.actor, so a change to iroh.socket.transports.relay.actor can break iroh.endpoint, while a change to iroh.endpoint can't break iroh.socket.transports.relay.actor.
- Position
- Below the diagonal: iroh.endpoint uses a module listed above it, which is the healthy direction.
30→25 iroh.endpoint uses iroh.socket.transports✕
- Connections
- 2 pairs of types, where a type in iroh.endpoint uses a type in iroh.socket.transports.
- The types involved
iroh.endpoint.Builder→iroh.socket.transports.TransportConfigiroh.endpoint.Endpoint→iroh.socket.transports.Addr
- Direction
- iroh.endpoint uses iroh.socket.transports, so a change to iroh.socket.transports can break iroh.endpoint, while a change to iroh.endpoint can't break iroh.socket.transports.
- Position
- Below the diagonal: iroh.endpoint uses a module listed above it, which is the healthy direction.
30→26 iroh.endpoint uses iroh.endpoint.quic✕
- Connections
- 3 pairs of types, where a type in iroh.endpoint uses a type in iroh.endpoint.quic.
- The types involved
iroh.endpoint.Builder→iroh.endpoint.quic.QuicTransportConfigiroh.endpoint.ConnectOptions→iroh.endpoint.quic.QuicTransportConfigiroh.endpoint.Endpoint→iroh.endpoint.quic.ServerConfigBuilder
- Direction
- iroh.endpoint uses iroh.endpoint.quic, so a change to iroh.endpoint.quic can break iroh.endpoint, while a change to iroh.endpoint can't break iroh.endpoint.quic.
- Position
- Below the diagonal: iroh.endpoint uses a module listed above it, which is the healthy direction.
30→28 iroh.endpoint uses iroh.endpoint.connection✕
- Connections
- 1 pair of types, where a type in iroh.endpoint uses a type in iroh.endpoint.connection.
- The types involved
iroh.endpoint.Endpoint→iroh.endpoint.connection.Accept
- Direction
- iroh.endpoint uses iroh.endpoint.connection, so a change to iroh.endpoint.connection can break iroh.endpoint, while a change to iroh.endpoint can't break iroh.endpoint.connection.
- Position
- Below the diagonal: iroh.endpoint uses a module listed above it, which is the healthy direction.
31→1 iroh.address_lookup uses iroh.address_lookup.metrics✕
- Connections
- 2 pairs of types, where a type in iroh.address_lookup uses a type in iroh.address_lookup.metrics.
- The types involved
iroh.address_lookup.AddressLookupServices→iroh.address_lookup.metrics.Metricsiroh.address_lookup.AddressLookupStream→iroh.address_lookup.metrics.Metrics
- Direction
- iroh.address_lookup uses iroh.address_lookup.metrics, so a change to iroh.address_lookup.metrics can break iroh.address_lookup, while a change to iroh.address_lookup can't break iroh.address_lookup.metrics.
- Position
- Below the diagonal: iroh.address_lookup uses a module listed above it, which is the healthy direction.
31→10 iroh.address_lookup uses iroh_dns.endpoint_info✕
- Connections
- 7 pairs of types, where a type in iroh.address_lookup uses a type in iroh_dns.endpoint_info.
- The types involved
iroh.address_lookup.AddressLookup→iroh_dns.endpoint_info.EndpointDatairoh.address_lookup.AddressLookupServices→iroh_dns.endpoint_info.AddrFilteriroh.address_lookup.AddressLookupServices→iroh_dns.endpoint_info.EndpointDatairoh.address_lookup.FilteredAddressLookup→iroh_dns.endpoint_info.AddrFilteriroh.address_lookup.FilteredAddressLookup→iroh_dns.endpoint_info.EndpointDatairoh.address_lookup.Item→iroh_dns.endpoint_info.EndpointInfoiroh.address_lookup.Item→iroh_dns.endpoint_info.UserData
- Direction
- iroh.address_lookup uses iroh_dns.endpoint_info, so a change to iroh_dns.endpoint_info can break iroh.address_lookup, while a change to iroh.address_lookup can't break iroh_dns.endpoint_info.
- Position
- Below the diagonal: iroh.address_lookup uses a module listed above it, which is the healthy direction.
31→12 iroh.address_lookup uses iroh_base.endpoint_addr✕
- Connections
- 1 pair of types, where a type in iroh.address_lookup uses a type in iroh_base.endpoint_addr.
- The types involved
iroh.address_lookup.Item→iroh_base.endpoint_addr.EndpointAddr
- Direction
- iroh.address_lookup uses iroh_base.endpoint_addr, so a change to iroh_base.endpoint_addr can break iroh.address_lookup, while a change to iroh.address_lookup can't break iroh_base.endpoint_addr.
- Position
- Below the diagonal: iroh.address_lookup uses a module listed above it, which is the healthy direction.
31→30 iroh.address_lookup uses iroh.endpoint✕
- Connections
- 2 pairs of types, where a type in iroh.address_lookup uses a type in iroh.endpoint.
- The types involved
iroh.address_lookup.AddressLookupBuilder→iroh.endpoint.Endpointiroh.address_lookup.DynAddressLookupBuilder→iroh.endpoint.Endpoint
- Direction
- iroh.address_lookup uses iroh.endpoint, so a change to iroh.endpoint can break iroh.address_lookup, while a change to iroh.address_lookup can't break iroh.endpoint.
- Position
- Below the diagonal: iroh.address_lookup uses a module listed above it, which is the healthy direction.
32→13 iroh_dns_server.http uses iroh.socket.remote_map.remote_state.path_watcher✕
- Connections
- 1 pair of types, where a type in iroh_dns_server.http uses a type in iroh.socket.remote_map.remote_state.path_watcher.
- The types involved
iroh_dns_server.http.http$module→iroh.socket.remote_map.remote_state.path_watcher.State
- Direction
- iroh_dns_server.http uses iroh.socket.remote_map.remote_state.path_watcher, so a change to iroh.socket.remote_map.remote_state.path_watcher can break iroh_dns_server.http, while a change to iroh_dns_server.http can't break iroh.socket.remote_map.remote_state.path_watcher.
- Position
- Below the diagonal: iroh_dns_server.http uses a module listed above it, which is the healthy direction.
32→30 iroh_dns_server.http uses iroh.endpoint✕
- Connections
- 1 pair of types, where a type in iroh_dns_server.http uses a type in iroh.endpoint.
- The types involved
iroh_dns_server.http.http$module→iroh.endpoint.Builder
- Direction
- iroh_dns_server.http uses iroh.endpoint, so a change to iroh.endpoint can break iroh_dns_server.http, while a change to iroh_dns_server.http can't break iroh.endpoint.
- Position
- Below the diagonal: iroh_dns_server.http uses a module listed above it, which is the healthy direction.
33→1 iroh_relay.server.http_server uses iroh.address_lookup.metrics✕
- Connections
- 3 pairs of types, where a type in iroh_relay.server.http_server uses a type in iroh.address_lookup.metrics.
- The types involved
iroh_relay.server.http_server.Inner→iroh.address_lookup.metrics.Metricsiroh_relay.server.http_server.RelayService→iroh.address_lookup.metrics.Metricsiroh_relay.server.http_server.ServerBuilder→iroh.address_lookup.metrics.Metrics
- Direction
- iroh_relay.server.http_server uses iroh.address_lookup.metrics, so a change to iroh.address_lookup.metrics can break iroh_relay.server.http_server, while a change to iroh_relay.server.http_server can't break iroh.address_lookup.metrics.
- Position
- Below the diagonal: iroh_relay.server.http_server uses a module listed above it, which is the healthy direction.
33→5 iroh_relay.server.http_server uses iroh.tls✕
- Connections
- 3 pairs of types, where a type in iroh_relay.server.http_server uses a type in iroh.tls.
- The types involved
iroh_relay.server.http_server.RelayService→iroh.tls.TlsConfigiroh_relay.server.http_server.RelayServiceWithNotify→iroh.tls.TlsConfigiroh_relay.server.http_server.ServerBuilder→iroh.tls.TlsConfig
- Direction
- iroh_relay.server.http_server uses iroh.tls, so a change to iroh.tls can break iroh_relay.server.http_server, while a change to iroh_relay.server.http_server can't break iroh.tls.
- Position
- Below the diagonal: iroh_relay.server.http_server uses a module listed above it, which is the healthy direction.
33→6 iroh_relay.server.http_server uses iroh_dns.dns✕
- Connections
- 1 pair of types, where a type in iroh_relay.server.http_server uses a type in iroh_dns.dns.
- The types involved
iroh_relay.server.http_server.RelayService→iroh_dns.dns.Inner
- Direction
- iroh_relay.server.http_server uses iroh_dns.dns, so a change to iroh_dns.dns can break iroh_relay.server.http_server, while a change to iroh_relay.server.http_server can't break iroh_dns.dns.
- Position
- Below the diagonal: iroh_relay.server.http_server uses a module listed above it, which is the healthy direction.
33→23 iroh_relay.server.http_server uses iroh_relay.server.clients✕
- Connections
- 2 pairs of types, where a type in iroh_relay.server.http_server uses a type in iroh_relay.server.clients.
- The types involved
iroh_relay.server.http_server.Inner→iroh_relay.server.clients.Clientsiroh_relay.server.http_server.RelayService→iroh_relay.server.clients.Clients
- Direction
- iroh_relay.server.http_server uses iroh_relay.server.clients, so a change to iroh_relay.server.clients can break iroh_relay.server.http_server, while a change to iroh_relay.server.http_server can't break iroh_relay.server.clients.
- Position
- Below the diagonal: iroh_relay.server.http_server uses a module listed above it, which is the healthy direction.
33→25 iroh_relay.server.http_server uses iroh.socket.transports✕
- Connections
- 1 pair of types, where a type in iroh_relay.server.http_server uses a type in iroh.socket.transports.
- The types involved
iroh_relay.server.http_server.Inner→iroh.socket.transports.Sender
- Direction
- iroh_relay.server.http_server uses iroh.socket.transports, so a change to iroh.socket.transports can break iroh_relay.server.http_server, while a change to iroh_relay.server.http_server can't break iroh.socket.transports.
- Position
- Below the diagonal: iroh_relay.server.http_server uses a module listed above it, which is the healthy direction.
33→26 iroh_relay.server.http_server uses iroh.endpoint.quic✕
- Connections
- 1 pair of types, where a type in iroh_relay.server.http_server uses a type in iroh.endpoint.quic.
- The types involved
iroh_relay.server.http_server.TlsConfig→iroh.endpoint.quic.ServerConfig
- Direction
- iroh_relay.server.http_server uses iroh.endpoint.quic, so a change to iroh.endpoint.quic can break iroh_relay.server.http_server, while a change to iroh_relay.server.http_server can't break iroh.endpoint.quic.
- Position
- Below the diagonal: iroh_relay.server.http_server uses a module listed above it, which is the healthy direction.
33→30 iroh_relay.server.http_server uses iroh.endpoint✕
- Connections
- 1 pair of types, where a type in iroh_relay.server.http_server uses a type in iroh.endpoint.
- The types involved
iroh_relay.server.http_server.RelayServiceWithNotify→iroh.endpoint.Builder
- Direction
- iroh_relay.server.http_server uses iroh.endpoint, so a change to iroh.endpoint can break iroh_relay.server.http_server, while a change to iroh_relay.server.http_server can't break iroh.endpoint.
- Position
- Below the diagonal: iroh_relay.server.http_server uses a module listed above it, which is the healthy direction.
33→37 iroh_relay.server.http_server uses iroh_relay.server part of a loop✕
- Connections
- 2 pairs of types, where a type in iroh_relay.server.http_server uses a type in iroh_relay.server.
- The types involved
iroh_relay.server.http_server.RelayService→iroh_relay.server.ClientRateLimitiroh_relay.server.http_server.ServerBuilder→iroh_relay.server.ClientRateLimit
- Direction
- iroh_relay.server.http_server uses iroh_relay.server, so a change to iroh_relay.server can break iroh_relay.server.http_server, while a change to iroh_relay.server.http_server can't break iroh_relay.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.
34→2 iroh.address_lookup.pkarr uses iroh_base.key✕
- Connections
- 3 pairs of types, where a type in iroh.address_lookup.pkarr uses a type in iroh_base.key.
- The types involved
iroh.address_lookup.pkarr.PkarrPublisher→iroh_base.key.SecretKeyiroh.address_lookup.pkarr.PkarrPublisherBuilder→iroh_base.key.SecretKeyiroh.address_lookup.pkarr.PublisherService→iroh_base.key.SecretKey
- Direction
- iroh.address_lookup.pkarr uses iroh_base.key, so a change to iroh_base.key can break iroh.address_lookup.pkarr, while a change to iroh.address_lookup.pkarr can't break iroh_base.key.
- Position
- Below the diagonal: iroh.address_lookup.pkarr uses a module listed above it, which is the healthy direction.
34→6 iroh.address_lookup.pkarr uses iroh_dns.dns✕
- Connections
- 4 pairs of types, where a type in iroh.address_lookup.pkarr uses a type in iroh_dns.dns.
- The types involved
iroh.address_lookup.pkarr.PkarrPublisherBuilder→iroh_dns.dns.DnsResolveriroh.address_lookup.pkarr.PkarrRelayClient→iroh_dns.dns.DnsResolveriroh.address_lookup.pkarr.PkarrRelayClientBuilder→iroh_dns.dns.DnsResolveriroh.address_lookup.pkarr.PkarrResolverBuilder→iroh_dns.dns.DnsResolver
- Direction
- iroh.address_lookup.pkarr uses iroh_dns.dns, so a change to iroh_dns.dns can break iroh.address_lookup.pkarr, while a change to iroh.address_lookup.pkarr can't break iroh_dns.dns.
- Position
- Below the diagonal: iroh.address_lookup.pkarr uses a module listed above it, which is the healthy direction.
34→7 iroh.address_lookup.pkarr uses iroh_dns.pkarr✕
- Connections
- 1 pair of types, where a type in iroh.address_lookup.pkarr uses a type in iroh_dns.pkarr.
- The types involved
iroh.address_lookup.pkarr.PkarrRelayClient→iroh_dns.pkarr.SignedPacket
- Direction
- iroh.address_lookup.pkarr uses iroh_dns.pkarr, so a change to iroh_dns.pkarr can break iroh.address_lookup.pkarr, while a change to iroh.address_lookup.pkarr can't break iroh_dns.pkarr.
- Position
- Below the diagonal: iroh.address_lookup.pkarr uses a module listed above it, which is the healthy direction.
34→10 iroh.address_lookup.pkarr uses iroh_dns.endpoint_info✕
- Connections
- 4 pairs of types, where a type in iroh.address_lookup.pkarr uses a type in iroh_dns.endpoint_info.
- The types involved
iroh.address_lookup.pkarr.PkarrPublisher→iroh_dns.endpoint_info.AddrFilteriroh.address_lookup.pkarr.PkarrPublisher→iroh_dns.endpoint_info.EndpointDatairoh.address_lookup.pkarr.PkarrPublisherBuilder→iroh_dns.endpoint_info.AddrFilteriroh.address_lookup.pkarr.PublisherService→iroh_dns.endpoint_info.EndpointInfo
- Direction
- iroh.address_lookup.pkarr uses iroh_dns.endpoint_info, so a change to iroh_dns.endpoint_info can break iroh.address_lookup.pkarr, while a change to iroh.address_lookup.pkarr can't break iroh_dns.endpoint_info.
- Position
- Below the diagonal: iroh.address_lookup.pkarr uses a module listed above it, which is the healthy direction.
34→14 iroh.address_lookup.pkarr uses iroh.net_report.reportgen✕
- Connections
- 1 pair of types, where a type in iroh.address_lookup.pkarr uses a type in iroh.net_report.reportgen.
- The types involved
iroh.address_lookup.pkarr.PkarrRelayClient→iroh.net_report.reportgen.Client
- Direction
- iroh.address_lookup.pkarr uses iroh.net_report.reportgen, so a change to iroh.net_report.reportgen can break iroh.address_lookup.pkarr, while a change to iroh.address_lookup.pkarr can't break iroh.net_report.reportgen.
- Position
- Below the diagonal: iroh.address_lookup.pkarr uses a module listed above it, which is the healthy direction.
34→30 iroh.address_lookup.pkarr uses iroh.endpoint✕
- Connections
- 2 pairs of types, where a type in iroh.address_lookup.pkarr uses a type in iroh.endpoint.
- The types involved
iroh.address_lookup.pkarr.PkarrPublisherBuilder→iroh.endpoint.Endpointiroh.address_lookup.pkarr.PkarrResolverBuilder→iroh.endpoint.Endpoint
- Direction
- iroh.address_lookup.pkarr uses iroh.endpoint, so a change to iroh.endpoint can break iroh.address_lookup.pkarr, while a change to iroh.address_lookup.pkarr can't break iroh.endpoint.
- Position
- Below the diagonal: iroh.address_lookup.pkarr uses a module listed above it, which is the healthy direction.
34→31 iroh.address_lookup.pkarr uses iroh.address_lookup✕
- Connections
- 4 pairs of types, where a type in iroh.address_lookup.pkarr uses a type in iroh.address_lookup.
- The types involved
iroh.address_lookup.pkarr.PkarrPublisher→iroh.address_lookup.AddressLookupiroh.address_lookup.pkarr.PkarrPublisherBuilder→iroh.address_lookup.AddressLookupBuilderiroh.address_lookup.pkarr.PkarrResolver→iroh.address_lookup.AddressLookupiroh.address_lookup.pkarr.PkarrResolverBuilder→iroh.address_lookup.AddressLookupBuilder
- Direction
- iroh.address_lookup.pkarr uses iroh.address_lookup, so a change to iroh.address_lookup can break iroh.address_lookup.pkarr, while a change to iroh.address_lookup.pkarr can't break iroh.address_lookup.
- Position
- Below the diagonal: iroh.address_lookup.pkarr uses a module listed above it, which is the healthy direction.
35→1 iroh_dns_server.server uses iroh.address_lookup.metrics✕
- Connections
- 1 pair of types, where a type in iroh_dns_server.server uses a type in iroh.address_lookup.metrics.
- The types involved
iroh_dns_server.server.Server→iroh.address_lookup.metrics.Metrics
- Direction
- iroh_dns_server.server uses iroh.address_lookup.metrics, so a change to iroh.address_lookup.metrics can break iroh_dns_server.server, while a change to iroh_dns_server.server can't break iroh.address_lookup.metrics.
- Position
- Below the diagonal: iroh_dns_server.server uses a module listed above it, which is the healthy direction.
35→20 iroh_dns_server.server uses iroh.socket.transports.ip✕
- Connections
- 1 pair of types, where a type in iroh_dns_server.server uses a type in iroh.socket.transports.ip.
- The types involved
iroh_dns_server.server.Server→iroh.socket.transports.ip.Config
- Direction
- iroh_dns_server.server uses iroh.socket.transports.ip, so a change to iroh.socket.transports.ip can break iroh_dns_server.server, while a change to iroh_dns_server.server can't break iroh.socket.transports.ip.
- Position
- Below the diagonal: iroh_dns_server.server uses a module listed above it, which is the healthy direction.
35→29 iroh_dns_server.server uses iroh_dns_server.store✕
- Connections
- 1 pair of types, where a type in iroh_dns_server.server uses a type in iroh_dns_server.store.
- The types involved
iroh_dns_server.server.Server→iroh_dns_server.store.ZoneStore
- Direction
- iroh_dns_server.server uses iroh_dns_server.store, so a change to iroh_dns_server.store can break iroh_dns_server.server, while a change to iroh_dns_server.server can't break iroh_dns_server.store.
- Position
- Below the diagonal: iroh_dns_server.server uses a module listed above it, which is the healthy direction.
35→32 iroh_dns_server.server uses iroh_dns_server.http✕
- Connections
- 1 pair of types, where a type in iroh_dns_server.server uses a type in iroh_dns_server.http.
- The types involved
iroh_dns_server.server.Server→iroh_dns_server.http.HttpServer
- Direction
- iroh_dns_server.server uses iroh_dns_server.http, so a change to iroh_dns_server.http can break iroh_dns_server.server, while a change to iroh_dns_server.server can't break iroh_dns_server.http.
- Position
- Below the diagonal: iroh_dns_server.server uses a module listed above it, which is the healthy direction.
35→36 iroh_dns_server.server uses iroh_dns_server.dns part of a loop✕
- Connections
- 1 pair of types, where a type in iroh_dns_server.server uses a type in iroh_dns_server.dns.
- The types involved
iroh_dns_server.server.Server→iroh_dns_server.dns.DnsServer
- Direction
- iroh_dns_server.server uses iroh_dns_server.dns, so a change to iroh_dns_server.dns can break iroh_dns_server.server, while a change to iroh_dns_server.server can't break iroh_dns_server.dns.
- 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.
36→1 iroh_dns_server.dns uses iroh.address_lookup.metrics✕
- Connections
- 1 pair of types, where a type in iroh_dns_server.dns uses a type in iroh.address_lookup.metrics.
- The types involved
iroh_dns_server.dns.DnsHandler→iroh.address_lookup.metrics.Metrics
- Direction
- iroh_dns_server.dns uses iroh.address_lookup.metrics, so a change to iroh.address_lookup.metrics can break iroh_dns_server.dns, while a change to iroh_dns_server.dns can't break iroh.address_lookup.metrics.
- Position
- Below the diagonal: iroh_dns_server.dns uses a module listed above it, which is the healthy direction.
36→25 iroh_dns_server.dns uses iroh.socket.transports✕
- Connections
- 1 pair of types, where a type in iroh_dns_server.dns uses a type in iroh.socket.transports.
- The types involved
iroh_dns_server.dns.Handle→iroh.socket.transports.Sender
- Direction
- iroh_dns_server.dns uses iroh.socket.transports, so a change to iroh.socket.transports can break iroh_dns_server.dns, while a change to iroh_dns_server.dns can't break iroh.socket.transports.
- Position
- Below the diagonal: iroh_dns_server.dns uses a module listed above it, which is the healthy direction.
36→29 iroh_dns_server.dns uses iroh_dns_server.store✕
- Connections
- 1 pair of types, where a type in iroh_dns_server.dns uses a type in iroh_dns_server.store.
- The types involved
iroh_dns_server.dns.DnsHandler→iroh_dns_server.store.ZoneStore
- Direction
- iroh_dns_server.dns uses iroh_dns_server.store, so a change to iroh_dns_server.store can break iroh_dns_server.dns, while a change to iroh_dns_server.dns can't break iroh_dns_server.store.
- Position
- Below the diagonal: iroh_dns_server.dns uses a module listed above it, which is the healthy direction.
36→35 iroh_dns_server.dns uses iroh_dns_server.server✕
- Connections
- 1 pair of types, where a type in iroh_dns_server.dns uses a type in iroh_dns_server.server.
- The types involved
iroh_dns_server.dns.DnsServer→iroh_dns_server.server.Server
- Direction
- iroh_dns_server.dns uses iroh_dns_server.server, so a change to iroh_dns_server.server can break iroh_dns_server.dns, while a change to iroh_dns_server.dns can't break iroh_dns_server.server.
- Position
- Below the diagonal: iroh_dns_server.dns uses a module listed above it, which is the healthy direction.
37→3 iroh_relay.server uses iroh_base.relay_url✕
- Connections
- 1 pair of types, where a type in iroh_relay.server uses a type in iroh_base.relay_url.
- The types involved
iroh_relay.server.Server→iroh_base.relay_url.RelayUrl
- Direction
- iroh_relay.server uses iroh_base.relay_url, so a change to iroh_base.relay_url can break iroh_relay.server, while a change to iroh_relay.server can't break iroh_base.relay_url.
- Position
- Below the diagonal: iroh_relay.server uses a module listed above it, which is the healthy direction.
37→5 iroh_relay.server uses iroh.tls✕
- Connections
- 1 pair of types, where a type in iroh_relay.server uses a type in iroh.tls.
- The types involved
iroh_relay.server.RelayConfig→iroh.tls.TlsConfig
- Direction
- iroh_relay.server uses iroh.tls, so a change to iroh.tls can break iroh_relay.server, while a change to iroh_relay.server can't break iroh.tls.
- Position
- Below the diagonal: iroh_relay.server uses a module listed above it, which is the healthy direction.
37→9 iroh_relay.server uses iroh_relay.relay_map✕
- Connections
- 1 pair of types, where a type in iroh_relay.server uses a type in iroh_relay.relay_map.
- The types involved
iroh_relay.server.ServerConfig→iroh_relay.relay_map.RelayConfig
- Direction
- iroh_relay.server uses iroh_relay.relay_map, so a change to iroh_relay.relay_map can break iroh_relay.server, while a change to iroh_relay.server can't break iroh_relay.relay_map.
- Position
- Below the diagonal: iroh_relay.server uses a module listed above it, which is the healthy direction.
37→14 iroh_relay.server uses iroh.net_report.reportgen✕
- Connections
- 1 pair of types, where a type in iroh_relay.server uses a type in iroh.net_report.reportgen.
- The types involved
iroh_relay.server.ServerConfig→iroh.net_report.reportgen.QuicConfig
- Direction
- iroh_relay.server uses iroh.net_report.reportgen, so a change to iroh.net_report.reportgen can break iroh_relay.server, while a change to iroh_relay.server can't break iroh.net_report.reportgen.
- Position
- Below the diagonal: iroh_relay.server uses a module listed above it, which is the healthy direction.
37→26 iroh_relay.server uses iroh.endpoint.quic✕
- Connections
- 2 pairs of types, where a type in iroh_relay.server uses a type in iroh.endpoint.quic.
- The types involved
iroh_relay.server.QuicConfig→iroh.endpoint.quic.ServerConfigiroh_relay.server.Server→iroh.endpoint.quic.ServerConfig
- Direction
- iroh_relay.server uses iroh.endpoint.quic, so a change to iroh.endpoint.quic can break iroh_relay.server, while a change to iroh_relay.server can't break iroh.endpoint.quic.
- Position
- Below the diagonal: iroh_relay.server uses a module listed above it, which is the healthy direction.
37→33 iroh_relay.server uses iroh_relay.server.http_server✕
- Connections
- 1 pair of types, where a type in iroh_relay.server uses a type in iroh_relay.server.http_server.
- The types involved
iroh_relay.server.Server→iroh_relay.server.http_server.RelayService
- Direction
- iroh_relay.server uses iroh_relay.server.http_server, so a change to iroh_relay.server.http_server can break iroh_relay.server, while a change to iroh_relay.server can't break iroh_relay.server.http_server.
- Position
- Below the diagonal: iroh_relay.server uses a module listed above it, which is the healthy direction.
37→35 iroh_relay.server uses iroh_dns_server.server✕
- Connections
- 1 pair of types, where a type in iroh_relay.server uses a type in iroh_dns_server.server.
- The types involved
iroh_relay.server.server$module→iroh_dns_server.server.Server
- Direction
- iroh_relay.server uses iroh_dns_server.server, so a change to iroh_dns_server.server can break iroh_relay.server, while a change to iroh_relay.server can't break iroh_dns_server.server.
- Position
- Below the diagonal: iroh_relay.server uses a module listed above it, which is the healthy direction.
37→38 iroh_relay.server uses iroh_relay.main part of a loop✕
- Connections
- 1 pair of types, where a type in iroh_relay.server uses a type in iroh_relay.main.
- The types involved
iroh_relay.server.RelayConfig→iroh_relay.main.Limits
- Direction
- iroh_relay.server uses iroh_relay.main, so a change to iroh_relay.main can break iroh_relay.server, while a change to iroh_relay.server can't break iroh_relay.main.
- 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.
38→5 iroh_relay.main uses iroh.tls✕
- Connections
- 2 pairs of types, where a type in iroh_relay.main uses a type in iroh.tls.
- The types involved
iroh_relay.main.Config→iroh.tls.TlsConfigiroh_relay.main.main$module→iroh.tls.TlsConfig
- Direction
- iroh_relay.main uses iroh.tls, so a change to iroh.tls can break iroh_relay.main, while a change to iroh_relay.main can't break iroh.tls.
- Position
- Below the diagonal: iroh_relay.main uses a module listed above it, which is the healthy direction.
38→14 iroh_relay.main uses iroh.net_report.reportgen✕
- Connections
- 2 pairs of types, where a type in iroh_relay.main uses a type in iroh.net_report.reportgen.
- The types involved
iroh_relay.main.HttpAccess→iroh.net_report.reportgen.Clientiroh_relay.main.main$module→iroh.net_report.reportgen.Client
- Direction
- iroh_relay.main uses iroh.net_report.reportgen, so a change to iroh.net_report.reportgen can break iroh_relay.main, while a change to iroh_relay.main can't break iroh.net_report.reportgen.
- Position
- Below the diagonal: iroh_relay.main uses a module listed above it, which is the healthy direction.
38→20 iroh_relay.main uses iroh.socket.transports.ip✕
- Connections
- 2 pairs of types, where a type in iroh_relay.main uses a type in iroh.socket.transports.ip.
- The types involved
iroh_relay.main.TlsConfig→iroh.socket.transports.ip.Configiroh_relay.main.main$module→iroh.socket.transports.ip.Config
- Direction
- iroh_relay.main uses iroh.socket.transports.ip, so a change to iroh.socket.transports.ip can break iroh_relay.main, while a change to iroh_relay.main can't break iroh.socket.transports.ip.
- Position
- Below the diagonal: iroh_relay.main uses a module listed above it, which is the healthy direction.
38→37 iroh_relay.main uses iroh_relay.server✕
- Connections
- 12 pairs of types, where a type in iroh_relay.main uses a type in iroh_relay.server.
- The types involved
iroh_relay.main.AllowlistAccess→iroh_relay.server.Accessiroh_relay.main.AllowlistAccess→iroh_relay.server.AccessControliroh_relay.main.AllowlistAccess→iroh_relay.server.ClientRequestiroh_relay.main.DenylistAccess→iroh_relay.server.Accessiroh_relay.main.DenylistAccess→iroh_relay.server.AccessControliroh_relay.main.DenylistAccess→iroh_relay.server.ClientRequestiroh_relay.main.HttpAccess→iroh_relay.server.Accessiroh_relay.main.HttpAccess→iroh_relay.server.AccessControliroh_relay.main.HttpAccess→iroh_relay.server.ClientRequestiroh_relay.main.SharedTokenAccess→iroh_relay.server.Accessiroh_relay.main.SharedTokenAccess→iroh_relay.server.AccessControliroh_relay.main.SharedTokenAccess→iroh_relay.server.ClientRequest
- Direction
- iroh_relay.main uses iroh_relay.server, so a change to iroh_relay.server can break iroh_relay.main, while a change to iroh_relay.main can't break iroh_relay.server.
- Position
- Below the diagonal: iroh_relay.main uses a module listed above it, which is the healthy direction.
39→1 iroh_relay.server.streams uses iroh.address_lookup.metrics✕
- Connections
- 1 pair of types, where a type in iroh_relay.server.streams uses a type in iroh.address_lookup.metrics.
- The types involved
iroh_relay.server.streams.RateLimited→iroh.address_lookup.metrics.Metrics
- Direction
- iroh_relay.server.streams uses iroh.address_lookup.metrics, so a change to iroh.address_lookup.metrics can break iroh_relay.server.streams, while a change to iroh_relay.server.streams can't break iroh.address_lookup.metrics.
- Position
- Below the diagonal: iroh_relay.server.streams uses a module listed above it, which is the healthy direction.
39→4 iroh_relay.server.streams uses iroh_relay.protos.relay✕
- Connections
- 1 pair of types, where a type in iroh_relay.server.streams uses a type in iroh_relay.protos.relay.
- The types involved
iroh_relay.server.streams.RelayedStream→iroh_relay.protos.relay.RelayToClientMsg
- Direction
- iroh_relay.server.streams uses iroh_relay.protos.relay, so a change to iroh_relay.protos.relay can break iroh_relay.server.streams, while a change to iroh_relay.server.streams can't break iroh_relay.protos.relay.
- Position
- Below the diagonal: iroh_relay.server.streams uses a module listed above it, which is the healthy direction.
39→25 iroh_relay.server.streams uses iroh.socket.transports✕
- Connections
- 1 pair of types, where a type in iroh_relay.server.streams uses a type in iroh.socket.transports.
- The types involved
iroh_relay.server.streams.RateLimited→iroh.socket.transports.Sender
- Direction
- iroh_relay.server.streams uses iroh.socket.transports, so a change to iroh.socket.transports can break iroh_relay.server.streams, while a change to iroh_relay.server.streams can't break iroh.socket.transports.
- Position
- Below the diagonal: iroh_relay.server.streams uses a module listed above it, which is the healthy direction.
39→37 iroh_relay.server.streams uses iroh_relay.server✕
- Connections
- 1 pair of types, where a type in iroh_relay.server.streams uses a type in iroh_relay.server.
- The types involved
iroh_relay.server.streams.Bucket→iroh_relay.server.ClientRateLimit
- Direction
- iroh_relay.server.streams uses iroh_relay.server, so a change to iroh_relay.server can break iroh_relay.server.streams, while a change to iroh_relay.server.streams can't break iroh_relay.server.
- Position
- Below the diagonal: iroh_relay.server.streams uses a module listed above it, which is the healthy direction.
40→1 iroh_relay.server.client uses iroh.address_lookup.metrics✕
- Connections
- 2 pairs of types, where a type in iroh_relay.server.client uses a type in iroh.address_lookup.metrics.
- The types involved
iroh_relay.server.client.Actor→iroh.address_lookup.metrics.Metricsiroh_relay.server.client.Client→iroh.address_lookup.metrics.Metrics
- Direction
- iroh_relay.server.client uses iroh.address_lookup.metrics, so a change to iroh.address_lookup.metrics can break iroh_relay.server.client, while a change to iroh_relay.server.client can't break iroh.address_lookup.metrics.
- Position
- Below the diagonal: iroh_relay.server.client uses a module listed above it, which is the healthy direction.
40→4 iroh_relay.server.client uses iroh_relay.protos.relay✕
- Connections
- 5 pairs of types, where a type in iroh_relay.server.client uses a type in iroh_relay.protos.relay.
- The types involved
iroh_relay.server.client.Actor→iroh_relay.protos.relay.Datagramsiroh_relay.server.client.Actor→iroh_relay.protos.relay.RelayToClientMsgiroh_relay.server.client.Client→iroh_relay.protos.relay.Datagramsiroh_relay.server.client.Client→iroh_relay.protos.relay.Statusiroh_relay.server.client.Packet→iroh_relay.protos.relay.Datagrams
- Direction
- iroh_relay.server.client uses iroh_relay.protos.relay, so a change to iroh_relay.protos.relay can break iroh_relay.server.client, while a change to iroh_relay.server.client can't break iroh_relay.protos.relay.
- Position
- Below the diagonal: iroh_relay.server.client uses a module listed above it, which is the healthy direction.
40→8 iroh_relay.server.client uses iroh_relay.client.conn✕
- Connections
- 1 pair of types, where a type in iroh_relay.server.client uses a type in iroh_relay.client.conn.
- The types involved
iroh_relay.server.client.ForwardPacketError→iroh_relay.client.conn.SendError
- Direction
- iroh_relay.server.client uses iroh_relay.client.conn, so a change to iroh_relay.client.conn can break iroh_relay.server.client, while a change to iroh_relay.server.client can't break iroh_relay.client.conn.
- Position
- Below the diagonal: iroh_relay.server.client uses a module listed above it, which is the healthy direction.
40→14 iroh_relay.server.client uses iroh.net_report.reportgen✕
- Connections
- 1 pair of types, where a type in iroh_relay.server.client uses a type in iroh.net_report.reportgen.
- The types involved
iroh_relay.server.client.Client→iroh.net_report.reportgen.Client
- Direction
- iroh_relay.server.client uses iroh.net_report.reportgen, so a change to iroh.net_report.reportgen can break iroh_relay.server.client, while a change to iroh_relay.server.client can't break iroh.net_report.reportgen.
- Position
- Below the diagonal: iroh_relay.server.client uses a module listed above it, which is the healthy direction.
40→20 iroh_relay.server.client uses iroh.socket.transports.ip✕
- Connections
- 1 pair of types, where a type in iroh_relay.server.client uses a type in iroh.socket.transports.ip.
- The types involved
iroh_relay.server.client.Client→iroh.socket.transports.ip.Config
- Direction
- iroh_relay.server.client uses iroh.socket.transports.ip, so a change to iroh.socket.transports.ip can break iroh_relay.server.client, while a change to iroh_relay.server.client can't break iroh.socket.transports.ip.
- Position
- Below the diagonal: iroh_relay.server.client uses a module listed above it, which is the healthy direction.
40→23 iroh_relay.server.client uses iroh_relay.server.clients✕
- Connections
- 2 pairs of types, where a type in iroh_relay.server.client uses a type in iroh_relay.server.clients.
- The types involved
iroh_relay.server.client.Actor→iroh_relay.server.clients.Clientsiroh_relay.server.client.Client→iroh_relay.server.clients.Clients
- Direction
- iroh_relay.server.client uses iroh_relay.server.clients, so a change to iroh_relay.server.clients can break iroh_relay.server.client, while a change to iroh_relay.server.client can't break iroh_relay.server.clients.
- Position
- Below the diagonal: iroh_relay.server.client uses a module listed above it, which is the healthy direction.
40→25 iroh_relay.server.client uses iroh.socket.transports✕
- Connections
- 1 pair of types, where a type in iroh_relay.server.client uses a type in iroh.socket.transports.
- The types involved
iroh_relay.server.client.Client→iroh.socket.transports.Sender
- Direction
- iroh_relay.server.client uses iroh.socket.transports, so a change to iroh.socket.transports can break iroh_relay.server.client, while a change to iroh_relay.server.client can't break iroh.socket.transports.
- Position
- Below the diagonal: iroh_relay.server.client uses a module listed above it, which is the healthy direction.
40→37 iroh_relay.server.client uses iroh_relay.server✕
- Connections
- 3 pairs of types, where a type in iroh_relay.server.client uses a type in iroh_relay.server.
- The types involved
iroh_relay.server.client.Actor→iroh_relay.server.OnDisconnectGuardiroh_relay.server.client.Client→iroh_relay.server.ConnectionIdiroh_relay.server.client.Config→iroh_relay.server.OnDisconnectGuard
- Direction
- iroh_relay.server.client uses iroh_relay.server, so a change to iroh_relay.server can break iroh_relay.server.client, while a change to iroh_relay.server.client can't break iroh_relay.server.
- Position
- Below the diagonal: iroh_relay.server.client uses a module listed above it, which is the healthy direction.
40→39 iroh_relay.server.client uses iroh_relay.server.streams✕
- Connections
- 2 pairs of types, where a type in iroh_relay.server.client uses a type in iroh_relay.server.streams.
- The types involved
iroh_relay.server.client.Actor→iroh_relay.server.streams.RelayedStreamiroh_relay.server.client.Config→iroh_relay.server.streams.RelayedStream
- Direction
- iroh_relay.server.client uses iroh_relay.server.streams, so a change to iroh_relay.server.streams can break iroh_relay.server.client, while a change to iroh_relay.server.client can't break iroh_relay.server.streams.
- Position
- Below the diagonal: iroh_relay.server.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 — Event Sourcing
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 22 | High / Critical |
| A02:2025 — Security Misconfiguration | 12 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 10 | Medium |
Roadmap
First, implement a global authentication guard with explicit public opt-outs and named role rules to secure all endpoints by default. Next, replace weak cryptographic hashes with SHA-256 or non-cryptographic alternatives based on their security relevance, and address the missing security headers. Then, resolve the four static analysis findings regarding secrets in Docker and release configurations. Finally, document significant design decisions in a dedicated ADR folder to establish a clear record of architectural choices and their consequences.
| 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. | +14.6 pts | Medium | Access Controls |
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +2.8 pts | Low | ADR Quality |
| Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED (2). | +2.3 pts | Low | Static Analysis (SAST) |
| Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED, REDACTED. | +2.3 pts | Low | Static Analysis (SAST) |
| Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (xxhash, murmurhash) where it only derives an identifier such as a cache key. | +3.3 pts | Medium | Web-Security Posture |
| Resolve the 5 High IaC finding(s) in IaC & Container Security — start with REDACTED (3), REDACTED (2). | +1.5 pts | Low | IaC & Container Security |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +2.6 pts | Medium | Architecture documentation |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +1.3 pts | Low | Supply-chain Provenance & Signing |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.5 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 4.5 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| iroh/src/net_report.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| iroh/src/socket/transports.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| iroh/src/socket.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| iroh/src/socket/transports/relay/actor.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| iroh/src/socket/remote_map/remote_state.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| iroh/src/protocol.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| iroh/src/socket/transports/ip.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| iroh-relay/src/server.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| iroh/src/endpoint.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| iroh/src/address_lookup/pkarr.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| iroh/bench/src/iroh.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| REDACTED | 6.1 | Mixed | Dependency Vulnerabilities: Medium advisory (unmaintained): REDACTED |
| iroh/tests/patchbay/degrade.rs | 7.0 | Mixed | Test Reliability: Test declared unreliable: degrade_server_congested_cellular |
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. 54 of 54 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 — 54 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, 207 of 235 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.
- D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This repository declares 2 of its own test(s) unreliable. The built-in reliability runner does not support this repository's ecosystem (.rs), so the suite was not re-run and no reliability score is given — these are the repository's own declarations, not our measurement.
- 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) — 47 | 48 | ### Target image 49 | >>> FROM alpine:latest AS iroh-dns-server 50 | 51 | RUN apk update && apk add ca-certificates && update-ca-certificates -------------------- ERROR: failed to solve: alpine:latest: failed to resolve source metadata for docker.io/library/alpine:latest: failed to do request: Head "https://registry-1.docker.io/v2/library/alpine/manifests/latest": Forbidden; runtime evidence skipped.
- C1 Data Protection — 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. 'redb' is imported (iroh-dns-server/src/store/signed_packets.rs:11), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- C3 Audit Trail — 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. 'redb' is imported (iroh-dns-server/src/store/signed_packets.rs:11), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- C4 Data Retention — 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. 'redb' is imported (iroh-dns-server/src/store/signed_packets.rs:11), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- C5 Data-Subject Rights — 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. 'redb' is imported (iroh-dns-server/src/store/signed_packets.rs:11), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- 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 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 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.
- M4 Documentation accuracy — 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. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9). Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- 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 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.
- X3 Exception handling — 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 PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go and JavaScript/TypeScript source only, and no C# was loaded and no PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go, JavaScript or TypeScript 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. 126 further occurrence(s) are not listed individually; the score already reflects all 166.
- 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.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality 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
9 function(s) exceeded the cyclomatic complexity threshold of 15; the worst was Client::spawn_qad_probes at 37.
What to do
- Bring the 9 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with Client::spawn_qad_probes (cyclomatic 37), Transports::inner_poll_recv (cyclomatic 32), Actor::run (cyclomatic 24). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 9 together lifts Cyclomatic Complexity from 8.3 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
28 function(s) exceeded the cognitive complexity threshold of 15; the worst was Client::spawn_qad_probes at 60.
What to do
- Bring the 28 bodies over 15 down to 15 or less in Cognitive Complexity — start with Client::spawn_qad_probes (cognitive 60), Actor::run (cognitive 38), ActiveRelayActor::run_connected (cognitive 36). — 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 28 together lifts Cognitive Complexity from 6.5 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
18 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 11 FileTooLong finding(s) in God Classes — start with socket.rs, actor.rs, remote_state.rs. — One of this dimension's main actionable groups (11 warning-level).
- Resolve the 4 TooManyMethods finding(s) in God Classes — start with endpoint.rs (2), quic.rs, connection.rs. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 2 MethodTooLong finding(s) in God Classes — start with server.rs, net_report.rs. — 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
25 duplicated block group(s) detected. A further 2 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted. 8 of the 27 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
What to do
- Resolve the 3 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with pkarr.rs, streams.rs, reportgen.rs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 3 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with endpoint_addr.rs (2), endpoint.rs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 Duplicated block (22 lines × 2) finding(s) in Code Duplication — start with net_report.rs, iroh.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
5 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)
0 of 130 classes have LCOM4 above 3.
D9 · Test Distribution
334 test methods: 243 unit, 91 integration, 0 BDD, 0 e2e. The Rust suite contributes 334 `#[test]` function(s) across 56 file(s) declaring at least one; its unit/integration split is Cargo's own — 12 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.
D12 · Dependency Hygiene
15 outdated, 0 yanked direct Cargo dependencies. 86 of 87 direct crates were graded against crates.io (0 not published there, 1 not resolved by a committed REDACTED). 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.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 504 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
No churn × complexity hotspots in the window. Repeated repair below the complexity floor: iroh-dns-server/src/http.rs (4 of 5 changes were fixes)
What to do
- Resolve the 1 Repeated repair finding(s) in Churn × Complexity Hotspots — start with http.rs. — One of this dimension's main actionable groups (1 warning-level).
D16 · Bus Factor
1 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is iroh/src/socket/remote_map/remote_state/path_watcher.rs. Counted over 90 of the 108 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D17 · Explicit Debt
33 deducted task-comment markers across 46205 LoC (0.1/KLoC) → score 9.9. 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 33 TodoComment finding(s) in Explicit Debt — start with remote_state.rs (5), socket.rs (3), http.rs (2). — One of this dimension's main actionable groups (33 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. 10 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
1 of 5 build units (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)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
22 finding(s): 0 critical, 21 high, 1 medium, 0 low. 11 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 6 file(s) — `iroh-dns/src/dns.rs` (line 955), `iroh-relay/src/server/http_server.rs` (line 57), `iroh/src/address_lookup.rs` (lines 565–580), `iroh/src/endpoint.rs` (lines 1287–1314, line 1314, line 3065), `iroh/src/socket.rs` (line 880), … (+1 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 5 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (4 issue-level).
- Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (4 issue-level).
- No action in Static Analysis (SAST) — all 10 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 (10 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
4 finding(s): 0 critical, 0 high, 4 medium, 0 low.
What to do
- Resolve the 2 Medium advisory (unmaintained) finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Medium advisory (unsound) finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Medium vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D31 · IaC & Container Security
12 finding(s): 0 critical, 5 high, 5 medium, 2 low.
What to do
- Resolve the 5 High IaC finding(s) in IaC & Container Security — start with REDACTED (3), REDACTED (2). — One of this dimension's main actionable groups (5 issue-level).
- Resolve the 5 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (4), REDACTED. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 2 Low IaC finding(s) in IaC & Container Security — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 recommendation-level).
D34 · Knowledge Freshness
1 of 90 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is iroh-relay/src/client/util.rs. Counted over 90 of the 108 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
Strongest change-coupling: mapped_addrs.rs↔remote_state.rs 57%
What to do
- Resolve the 1 Change coupling finding(s) in Change Coupling — start with mapped_addrs.rs. — One of this dimension's main actionable groups (1 warning-level).
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
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
- `Client.get_report` is a read-named query yet it performs a durable write on the read path (a persist to a store/repository). A query must stay side-effect-free so reads are safe to retry, cache, and route to a read replica; move the write into a command. — iroh/src/net_report.rs:296
What to do
- Keep query handlers read-only — move the writes/event-publishes into a command handler so reads stay safe to retry, cache, and route to a read replica.
C2 · Access Controls
- This repository serves requests — a server (.serve_connection) (iroh-relay/src/server.rs:1142) — 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. — iroh-relay/src/server.rs:1142
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.
ES1 · Fold determinism
ES2 · Immutable events
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 a README to the 1 of 6 project(s) that lack one — worth up to 0.3 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.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
- iroh-dns/README.md links to `pkarr.org`, but `iroh-dns/pkarr.org` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — iroh-dns/README.md:5
What to do
- Reconcile the README with reality: iroh-dns/README.md links to `pkarr.org`, but `iroh-dns/pkarr.org` does not exist.
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
What to do
- Add OpenTelemetry tracing/metrics (opentelemetry with tracing-opentelemetry) so requests are traceable across the system, not just health-probable.
P3 · Security & performance tooling
What to do
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
P6 · Release Hygiene
P7 · Outbound HTTP resilience
- `reqwest::Client::builder(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. (×3) — iroh-relay/src/main.rs:225, iroh/src/util.rs:16, iroh/src/util.rs:23
What to do
- Give every client a whole-request bound: `reqwest::Client::builder().timeout(Duration::from_secs(10))` (never `reqwest::get` or `Client::new()`, which have none), ureq's `timeout_global`, or wrap the call in `tokio::time::timeout`; add retry with back-off (`reqwest-retry`'s `RetryTransientMiddleware`, `backoff`) around dependencies that fail.
PF1 · Benchmark discipline
PF3 · Async & latency hygiene
S1 · Web-Security Posture
- MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`sha2::Sha256::digest(…)`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call. — iroh-relay/src/server/http_server.rs:84
- Set: Content-Security-Policy, Strict-Transport-Security. Missing: X-Content-Type-Options, X-Frame-Options — the four headers that carry the points of this card's security-headers term (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options), 0.5 each.(−1.0 on this card.) The server: `.serve_connection(` (iroh-relay/src/server.rs:1142).
What to do
- Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (xxhash, murmurhash) where it only derives an identifier such as a cache key.
- Add X-Content-Type-Options, X-Frame-Options beside the headers the Rust server already sets.
X1 · Async correctness
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X21 · Side-effecting pattern guard
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X30 · Support guard that admits what it rejects
X4 · Structured logging
- `debug!` at line 309 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`. — iroh-relay/src/main.rs:309
- `warn!` at line 331 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`. — iroh-relay/src/main.rs:331
- `debug!` at line 606 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`. — iroh-relay/src/main.rs:606
- `debug!` at line 139 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`. — iroh-relay/src/quic.rs:139
- `debug!` at line 216 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`. — iroh-relay/src/quic.rs:216
- `debug!` at line 234 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`. — iroh-relay/src/quic.rs:234
- `debug!` at line 777 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`. — iroh-relay/src/server.rs:777
- `error!` at line 778 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`. — iroh-relay/src/server.rs:778
- `debug!` at line 844 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`. — iroh-relay/src/server.rs:844
- `error!` at line 1146 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`. — iroh-relay/src/server.rs:1146
- `error!` at line 1152 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`. — iroh-relay/src/server.rs:1152
- `warn!` at line 186 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`. — iroh-relay/src/server/client.rs:186
- `warn!` at line 356 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`. — iroh-relay/src/server/client.rs:356
- `trace!` at line 419 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`. — iroh-relay/src/server/client.rs:419
- `warn!` at line 507 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`. — iroh-relay/src/server/client.rs:507
- `trace!` at line 64 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`. — iroh-relay/src/server/clients.rs:64
- `info!` at line 468 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`. — iroh-relay/src/server/http_server.rs:468
- `debug!` at line 492 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`. — iroh-relay/src/server/http_server.rs:492
- `error!` at line 503 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`. — iroh-relay/src/server/http_server.rs:503
- `warn!` at line 645 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`. — iroh-relay/src/server/http_server.rs:645
- `warn!` at line 654 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`. — iroh-relay/src/server/http_server.rs:654
- `debug!` at line 180 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`. — iroh-relay/src/client/tls.rs:180
- `debug!` at line 195 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`. — iroh-relay/src/client/tls.rs:195
- `error!` at line 202 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`. — iroh-relay/src/client/tls.rs:202
- `debug!` at line 291 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`. — iroh-relay/src/client/tls.rs:291
- `info!` 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: `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`. — iroh-dns-server/src/config.rs:190
- `info!` at line 118 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`. — iroh-dns-server/src/dns.rs:118
- `info!` at line 172 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`. — iroh-dns-server/src/http.rs:172
- `info!` at line 211 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`. — iroh-dns-server/src/http.rs:211
- `debug!` at line 32 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`. — iroh-dns-server/src/main.rs:32
- `warn!` at line 137 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`. — iroh-dns-server/src/store.rs:137
- `debug!` at line 144 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`. — iroh-dns-server/src/store.rs:144
- `debug!` at line 149 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`. — iroh-dns-server/src/store.rs:149
- `trace!` at line 237 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`. — iroh-dns-server/src/store.rs:237
- `trace!` at line 241 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`. — iroh-dns-server/src/store.rs:241
- `error!` at line 110 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`. — iroh-dns-server/src/store/signed_packets.rs:110
- `trace!` at line 153 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`. — iroh-dns-server/src/store/signed_packets.rs:153
- `warn!` at line 157 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`. — iroh-dns-server/src/store/signed_packets.rs:157
- `trace!` at line 163 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`. — iroh-dns-server/src/store/signed_packets.rs:163
- `trace!` at line 198 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`. — iroh-dns-server/src/store/signed_packets.rs:198
What to do
- Interpolated log message defeats structured logging
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 75% | Strong | Solid. |
| Architecture | 93% | Exemplary | Solid. |
| Maturity | 67% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 70% | Adequate — gated by P7 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 38% | Weak — gated by D29, D36, C2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Event Sourcing | 100% | Exemplary | Strongest area. |
| Performance | 89% | Strong | Solid. |
Unscored — 2 check(s) recorded observations but carry no score
- D11 Test Reliability — 2 observation(s) recorded · This repository declares 2 of its own test(s) unreliable. The built-in reliability runner does not support this repository's ecosystem (.rs), so the suite was not re-run and no reliability score is given — these are the repository's own declarations, not our measurement.
- X7 Silent fallback defaults — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: this repository stores data through 'redb' (iroh-dns-server/src/store/signed_packets.rs:11) but declares no persisted model this check reads (Diesel table! columns, SeaORM entity / Diesel model / sqlx FromRow struct fields, CREATE TABLE and ALTER TABLE … ADD columns in SQL migrations and SQL string literals). Personal data may be written through raw SQL or a hosted backend, so whether its changes need an audit trail could not be established, and the trail's absence is not scored.
- C4 Data Retention — Not assessed: this repository stores data through 'redb' (iroh-dns-server/src/store/signed_packets.rs:11) but declares no persisted model this check reads (Diesel table! columns, SeaORM entity / Diesel model / sqlx FromRow struct fields, CREATE TABLE and ALTER TABLE … ADD columns in SQL migrations and SQL string literals). Personal data may be written through raw SQL or a hosted backend, so whether a retention limit applies here could not be established, and its absence is not scored.
- C5 Data-Subject Rights — Not assessed: this repository stores data through 'redb' (iroh-dns-server/src/store/signed_packets.rs:11) but declares no persisted model this check reads (Diesel table! columns, SeaORM entity / Diesel model / sqlx FromRow struct fields, CREATE TABLE and ALTER TABLE … ADD columns in SQL migrations and SQL string literals). Personal data may be written through raw SQL or a hosted backend, so whether data-subject rights apply here could not be established, and their absence is not scored.
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 61 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: 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 — Not applicable: 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) — 47 | 48 | ### Target image 49 | >>> FROM alpine:latest AS iroh-dns-server 50 | 51 | RUN apk update && apk add ca-certificates && update-ca-certificates -------------------- ERROR: failed to solve: alpine:latest: failed to resolve source metadata for docker.io/library/alpine:latest: failed to do request: Head "https://registry-1.docker.io/v2/library/alpine/manifests/latest": 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 — Not assessed: this repository stores data through 'redb' (iroh-dns-server/src/store/signed_packets.rs:11) but declares no persisted model this check reads (Diesel table! columns, SeaORM entity / Diesel model / sqlx FromRow struct fields, CREATE TABLE and ALTER TABLE … ADD columns in SQL migrations and SQL string literals). Personal data may be written through raw SQL or a hosted backend, so the absence of a personal-data field here is not evidence that none is stored, and encryption at rest is not scored over a subject that could not be established.
- D10 Test Quality — ~7125 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.
- 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; 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 .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.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- 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 (2 of 3 signals for this style — below the bar we score at): 37 value object(s); 1 domain event(s); its domain events are published by services or handlers — no domain entity raises one
- 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
- 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'.
- 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
- PF2 Allocation hygiene — Not applicable: Rust spells out every heap allocation and makes borrowed slices (&[T], &str) its ordinary parameter types, so the allocation-aware style this card rewards elsewhere is the language's baseline rather than a rung to climb.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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
- X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. Rust's compiler refuses the unsynchronised version: a collection shared between a callback's thread and the waiting body must be `Sync`, which a `Vec`, `VecDeque` or `HashMap` is only behind a `Mutex`/`RwLock`, so the race this check looks for cannot be written in safe Rust. Not a gap in the analyzer and not a finding about your code.
- X3 Exception handling — 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.
- 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 — 29 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
- Test declared unreliable: degrade_server_congested_cellular iroh/tests/patchbay/degrade.rs:224
- Test declared unreliable: degrade_server_very_bad_cellular iroh/tests/patchbay/degrade.rs:231
- Query writes persistent state on the read path: Client.get_report iroh/src/net_report.rs:296
- REDACTED
- REDACTED
- REDACTED
Serious — 135 finding(s)
- TodoComment iroh-relay/src/quic.rs:326
- TodoComment iroh-relay/src/server.rs:487
- TodoComment iroh-relay/src/server/client.rs:513
- TodoComment iroh-relay/src/server/metrics.rs:107
- TodoComment iroh-relay/src/server/streams.rs:543
- TodoComment iroh-dns-server/src/http.rs:237
- TodoComment iroh-dns-server/src/http.rs:336
- TodoComment iroh-dns-server/src/util.rs:155
- TodoComment iroh-dns-server/src/http/doh.rs:79
- TodoComment iroh-dns-server/src/dns/node_zone_handler.rs:31
- TodoComment iroh/src/address_lookup.rs:383
- TodoComment iroh/src/endpoint.rs:2734
- TodoComment iroh/src/endpoint.rs:3889
- TodoComment iroh/src/net_report.rs:496
- TodoComment iroh/src/protocol.rs:135
- TodoComment iroh/src/socket.rs:100
- TodoComment iroh/src/socket.rs:2766
- TodoComment iroh/src/socket.rs:2881
- TodoComment iroh/src/tls.rs:87
- TodoComment iroh/src/socket/remote_map.rs:48
- TodoComment iroh/src/socket/remote_map/remote_state.rs:57
- TodoComment iroh/src/socket/transports.rs:1211
- TodoComment iroh/src/socket/transports.rs:1295
- TodoComment iroh/src/socket/transports/ip.rs:180
- TodoComment iroh/src/socket/transports/relay/actor.rs:673
- FileTooLong: src/socket.rs iroh/src/socket.rs
- FileTooLong: relay/actor.rs iroh/src/socket/transports/relay/actor.rs
- FileTooLong: remote_map/remote_state.rs iroh/src/socket/remote_map/remote_state.rs
- FileTooLong: socket/transports.rs iroh/src/socket/transports.rs
- FileTooLong: src/endpoint.rs iroh/src/endpoint.rs
- FileTooLong: src/server.rs iroh-relay/src/server.rs
- FileTooLong: src/net_report.rs iroh/src/net_report.rs
- FileTooLong: server/http_server.rs iroh-relay/src/server/http_server.rs
- FileTooLong: src/dns.rs iroh-dns/src/dns.rs
- FileTooLong: net_report/reportgen.rs iroh/src/net_report/reportgen.rs
- FileTooLong: endpoint/connection.rs iroh/src/endpoint/connection.rs
- Actor::run (cognitive 38) iroh/src/socket.rs:1484
- Actor::collect_local_addresses (cognitive 21) iroh/src/socket.rs:1907
- Actor::handle_message (cognitive 20) iroh-dns-server/src/store/signed_packets.rs:149
- Actor::run_inner (cognitive 18) iroh/src/net_report/reportgen.rs:233
- Actor::update_direct_addresses (cognitive 16) iroh/src/socket.rs:1827
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Client::spawn_qad_probes (cognitive 60) iroh/src/net_report.rs:443
- Client::have_enough_reports (cognitive 35) iroh/src/net_report.rs:661
- Client::get_report (cognitive 31) iroh/src/net_report.rs:296
- Client::add_report_history_and_set_preferred_relay (cognitive 18) iroh/src/net_report.rs:749
- ActiveRelayActor::run_connected (cognitive 36) iroh/src/socket/transports/relay/actor.rs:556
- ActiveRelayActor::run_dialing (cognitive 25) iroh/src/socket/transports/relay/actor.rs:451
- ActiveRelayActor::run_sending (cognitive 18) iroh/src/socket/transports/relay/actor.rs:798
- ActiveRelayActor::handle_relay_msg (cognitive 16) iroh/src/socket/transports/relay/actor.rs:715
- TooManyMethods: QuicTransportConfigBuilder iroh/src/endpoint/quic.rs:93
- TooManyMethods: Connection iroh/src/endpoint/connection.rs:748
- TooManyMethods: Builder iroh/src/endpoint.rs:131
- TooManyMethods: Endpoint iroh/src/endpoint.rs:908
- RemoteStateActor::run (cognitive 23) iroh/src/socket/remote_map/remote_state.rs:237
- RemoteStateActor::apply_selected_path (cognitive 17) iroh/src/socket/remote_map/remote_state.rs:685
- RemoteStateActor::handle_msg_network_change (cognitive 16) iroh/src/socket/remote_map/remote_state.rs:455
- Duplicated block (9 lines × 2) iroh/src/address_lookup/pkarr.rs:257
- Duplicated block (9 lines × 2) iroh-relay/src/client/streams.rs:118
- Duplicated block (9 lines × 2) iroh/src/net_report/reportgen.rs:726
- Duplicated block (6 lines × 2) iroh-base/src/endpoint_addr.rs:137
- Duplicated block (6 lines × 2) iroh-base/src/endpoint_addr.rs:147
- Duplicated block (6 lines × 2) iroh/src/endpoint.rs:1900
- Outbound HTTP without resilience iroh-relay/src/main.rs:225
- Outbound HTTP without resilience iroh/src/util.rs:16
- Outbound HTTP without resilience iroh/src/util.rs:23
- Client::spawn_qad_probes (cyclomatic 37) iroh/src/net_report.rs:443
- Client::have_enough_reports (cyclomatic 23) iroh/src/net_report.rs:661
- iroh_relay::client::tls::dial_happy_eyeballs (cognitive 33) iroh-relay/src/client/tls.rs:246
- iroh_relay::build_relay_config (cognitive 25) iroh-relay/src/main.rs:694
- Transports::inner_poll_recv (cognitive 31) iroh/src/socket/transports.rs:278
- Transports::bind (cognitive 16) iroh/src/socket/transports.rs:188
- MethodTooLong: Server.spawn iroh-relay/src/server.rs:692
- MethodTooLong: Client.spawn_qad_probes iroh/src/net_report.rs:443
- REDACTED
- REDACTED
- Duplicated block (22 lines × 2) iroh/src/net_report.rs:868
- Duplicated block (22 lines × 2) iroh/bench/src/iroh.rs:289
- Duplicated block (15 lines × 2) iroh-relay/src/client.rs:267
- Duplicated block (15 lines × 2) iroh/bench/src/iroh.rs:189
- Duplicated block (12 lines × 2) iroh-relay/src/protos/relay.rs:427
- Duplicated block (12 lines × 2) iroh/src/socket/transports/relay/actor.rs:602
- No authorization iroh-relay/src/server.rs:1142
- Transports::inner_poll_recv (cyclomatic 32) iroh/src/socket/transports.rs:278
- Actor::run (cyclomatic 24) iroh/src/socket.rs:1484
- ActiveRelayActor::run_connected (cyclomatic 23) iroh/src/socket/transports/relay/actor.rs:556
- RemoteStateActor::run (cyclomatic 21) iroh/src/socket/remote_map/remote_state.rs:237
- RouterBuilder::spawn (cyclomatic 17) iroh/src/protocol.rs:512
- TransportsSender::poll_send (cyclomatic 17) iroh/src/socket/transports.rs:965
- iroh_relay::client::tls::dial_happy_eyeballs (cyclomatic 16) iroh-relay/src/client/tls.rs:246
- Repeated repair: iroh-dns-server/src/http.rs iroh-dns-server/src/http.rs:143
- RouterBuilder::spawn (cognitive 35) iroh/src/protocol.rs:512
- TransportsSender::poll_send (cognitive 33) iroh/src/socket/transports.rs:965
- IpTransports::bind (cognitive 28) iroh/src/socket/transports/ip.rs:416
- Report::update (cognitive 27) iroh/src/net_report/report.rs:68
- Server::spawn (cognitive 24) iroh-relay/src/server.rs:692
- DnsResolver::resolve_host_all (cognitive 20) iroh-dns/src/dns.rs:908
- Config::is_valid_send_addr (cognitive 17) iroh/src/socket/transports/ip.rs:114
- RelayTransport::poll_recv (cognitive 17) iroh/src/socket/transports/relay.rs:91
- REDACTED
- TooManyFields: Metrics iroh/src/socket/metrics.rs:8
- REDACTED
- REDACTED
- Change coupling: mapped_addrs.rs ↔ remote_state.rs iroh/src/socket/mapped_addrs.rs:1
- REDACTED
- REDACTED
- Edited copy of a member (56 corresponding lines) iroh/src/net_report.rs:831
- Duplicated block (30 lines × 2) iroh/src/net_report.rs:835
- Duplicated block (25 lines × 2) iroh/src/net_report.rs:583
- Duplicated block (22–23 lines × 2) iroh/src/net_report.rs:695
- Duplicated block (11–12 lines × 2) iroh-dns/src/pkarr.rs:192
- Duplicated block (10 lines × 2) iroh/src/net_report.rs:508
- Duplicated block (8 lines × 2) iroh/src/net_report.rs:571
- Duplicated block (7 lines × 2) iroh/src/address_lookup/pkarr.rs:676
- Duplicated block (5 lines × 2) iroh-dns/src/pkarr.rs:93
- Edited copy of a member (45 corresponding lines) iroh/bench/src/iroh.rs:159
- Duplicated block (27 lines × 2) iroh/bench/src/iroh.rs:207
- Duplicated block (23 lines × 2) iroh/bench/src/iroh.rs:160
- Duplicated block (17 lines × 2) iroh/bench/src/iroh.rs:240
- Duplicated block (14 lines × 2) iroh/bench/src/iroh.rs:260
- Duplicated block (13 lines × 2) iroh/bench/src/bin/bulk.rs:78
- Off the main sequence: iroh-base
- Weak hash algorithm iroh-relay/src/server/http_server.rs:84
Minor — 56 finding(s)
- Interpolated log message defeats structured logging iroh-relay/src/main.rs:309
- Interpolated log message defeats structured logging iroh-relay/src/main.rs:331
- Interpolated log message defeats structured logging iroh-relay/src/main.rs:606
- Interpolated log message defeats structured logging iroh-relay/src/quic.rs:139
- Interpolated log message defeats structured logging iroh-relay/src/quic.rs:216
- Interpolated log message defeats structured logging iroh-relay/src/quic.rs:234
- Interpolated log message defeats structured logging iroh-relay/src/server.rs:777
- Interpolated log message defeats structured logging iroh-relay/src/server.rs:778
- Interpolated log message defeats structured logging iroh-relay/src/server.rs:844
- Interpolated log message defeats structured logging iroh-relay/src/server.rs:1146
- Interpolated log message defeats structured logging iroh-relay/src/server.rs:1152
- Interpolated log message defeats structured logging iroh-relay/src/server/client.rs:186
- Interpolated log message defeats structured logging iroh-relay/src/server/client.rs:356
- Interpolated log message defeats structured logging iroh-relay/src/server/client.rs:419
- Interpolated log message defeats structured logging iroh-relay/src/server/client.rs:507
- Interpolated log message defeats structured logging iroh-relay/src/server/clients.rs:64
- Interpolated log message defeats structured logging iroh-relay/src/server/http_server.rs:468
- Interpolated log message defeats structured logging iroh-relay/src/server/http_server.rs:492
- Interpolated log message defeats structured logging iroh-relay/src/server/http_server.rs:503
- Interpolated log message defeats structured logging iroh-relay/src/server/http_server.rs:645
- Interpolated log message defeats structured logging iroh-relay/src/server/http_server.rs:654
- Interpolated log message defeats structured logging iroh-relay/src/client/tls.rs:180
- Interpolated log message defeats structured logging iroh-relay/src/client/tls.rs:195
- Interpolated log message defeats structured logging iroh-relay/src/client/tls.rs:202
- Interpolated log message defeats structured logging iroh-relay/src/client/tls.rs:291
- REDACTED
- REDACTED
- Silent fallback default on Err iroh-dns/src/pkarr.rs:192
- Silent fallback default on Err iroh-dns/src/pkarr.rs:227
- Off-boarding risk: anonymized user #1
- No ADRs found
- Projects may be oversized for their cohesion
- Orphaned files with no living knowledge
- Orphaned file iroh-relay/src/client/util.rs:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- README/code drift iroh-dns/README.md:5
- Security headers incomplete
Minor — 15 finding(s)
- Outdated: arc-swap
- Outdated: ctutils
- Outdated: hyper-util
- Outdated: n0-watcher
- Outdated: redb
- Outdated: rustls-platform-verifier
- Outdated: serde_json
- Outdated: smallvec
- Outdated: tokio
- Outdated: tokio-rustls
- Outdated: tokio-util
- Outdated: toml
- Outdated: wasm-bindgen-futures
- Outdated: webpki-roots
- Outdated: zeroize
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-f98389fdab8644998b7104139373576a/history.json --exit-code 0 --source . | 2 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-f98389fdab8644998b7104139373576a/tree.json --exit-code 0 --source . | 2 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/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 . | 22 | 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 . | 4 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 12 | 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 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |