Executive summary
quinn-rs/quinn falls short of our standard for a preview release, in part because we found no recorded design decisions and no architecture document or diagram. It scores 62 out of 100 and is rated Adequate, and all 55 of its critical findings are security problems.
Maturity, at 53, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 8 points. Restoring certificate checks is another step, worth about 4 points. Raising Maturity to 62 would lift the score to about 66.
Forty-nine pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Two secrets can leak from the build pipeline, and one automatic update takes new releases before a bad one can be spotted. Pinning each tool to an exact version, limiting each secret to its own step and setting a waiting period for automatic updates would close these risks. The password or key in the code's history needs replacing, with the old one switched off. The pipeline step that installs packages without pinning their versions needs the packages it installs pinned to exact versions.
The product code is 36,215 lines, about €49,000 to rebuild.
If Maturity rose from 53 to 62, the lowest score rated Strong, the score would rise from 62 to about 66.
New since the last survey: 30 findings
- Code Duplication · Edited copy of a member (25 corresponding lines) quinn-udp/src/apple_fast.rs
- Code Duplication · Edited copy of a member (18 corresponding lines) quinn/src/endpoint.rs
- Code Duplication · Edited copy of a member (21 corresponding lines) quinn/src/connection.rs
- Code Duplication · Edited copy of a member (23 corresponding lines) quinn/src/recv_stream.rs
- Code Duplication · Edited copy of a member (11 corresponding lines) quinn-proto/src/frame.rs
- Code Duplication · Edited copy of a member (10 corresponding lines) quinn/src/runtime/smol.rs
- Code Duplication · Edited copy of a member (19 corresponding lines) quinn-proto/src/connection/qlog.rs
- Code Duplication · Edited copy of a member (9 corresponding lines) quinn-udp/src/apple_fast.rs
- Code Duplication · Edited copies of one member (3 members, 11+ corresponding lines) quinn-udp/src/unix.rs
- Code Duplication · Edited copy of a member (16 corresponding lines) quinn-udp/src/unix.rs
- Code Duplication · Edited copy of a member (9 corresponding lines) quinn/src/recv_stream.rs
- Code Duplication · Edited copies of one member (4 members, 5+ corresponding lines) quinn/src/connection.rs
- Code Duplication · Edited copy of a member (6 corresponding lines) quinn/src/runtime/smol.rs
- Code Duplication · Duplicated block (15 lines × 2) quinn/src/connection.rs
- Code Duplication · Duplicated block (9 lines × 2) quinn-udp/src/apple_fast.rs
- Code Duplication · Edited copy of a member (28 corresponding lines) bench/src/lib.rs
- Code Duplication · Edited copy of a member (22 corresponding lines) perf/src/client.rs
- Code Duplication · Edited copy of a member (14 corresponding lines) perf/src/stats.rs
- Code Duplication · Edited copy of a member (10 corresponding lines) perf/src/server.rs
- Code Coverage · Low coverage: bench/src/lib.rs bench/src/lib.rs
- Code Coverage · Low coverage: bench/src/stats.rs bench/src/stats.rs
- Code Coverage · Low coverage: perf/src/client.rs perf/src/client.rs
- Code Coverage · Low coverage: perf/src/lib.rs perf/src/lib.rs
- Code Coverage · Low coverage: perf/src/noprotection.rs perf/src/noprotection.rs
- Code Coverage · Low coverage: perf/src/server.rs perf/src/server.rs
- Code Coverage · Low coverage: perf/src/stats.rs perf/src/stats.rs
- Code Coverage · Low coverage: quinn-proto/src/congestion/bbr/mod.rs quinn-proto/src/congestion/bbr/mod.rs
- Code Coverage · Low coverage: quinn-proto/src/congestion/new_reno.rs quinn-proto/src/congestion/new_reno.rs
- Code Coverage · Low coverage: quinn-proto/src/crypto.rs quinn-proto/src/crypto.rs
- Dependency Vulnerabilities · REDACTED
Fixed since the last survey: 4 findings
- Churn × Complexity Hotspots · Hotspot: quinn/src/connection.rs quinn/src/connection.rs
- Churn × Complexity Hotspots · Hotspot: quinn-proto/src/frame.rs quinn-proto/src/frame.rs
- Secrets (history) · REDACTED: REDACTED quicr/examples/key.pem
- Documentation (README) · README may be stale
Rebuild cost: about €49,000 · Estimate
| Cost to rebuild | €16,000 to €82,000, for 272 to 862 hours of work, about 0.3 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 62. 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: 36,215 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 quinn.connection | 2 quinn_proto.coding | 3 quinn_udp | 4 quinn_udp.cmsg | 5 quinn.incoming | 6 quinn.runtime | 7 quinn_proto.bloom_token_log | 8 quinn_proto.packet | 9 quinn_proto.varint | 10 quinn_udp.unix | 11 quinn.runtime.smol | 12 quinn_proto.connection.assembler | 13 quinn_proto.connection.streams | 14 quinn_proto.frame | 15 quinn_proto.transport_parameters | 16 quinn_udp.apple_fast | 17 quinn.endpoint | 18 quinn_proto.connection.datagrams | 19 quinn_proto.connection.streams.recv | 20 quinn_proto.connection.streams.send | 21 quinn_proto.connection.streams.state | 22 quinn_proto.crypto | 23 quinn_proto.connection.spaces | 24 quinn_proto.connection.paths | 25 quinn_proto.congestion | 26 quinn_proto.connection.qlog | 27 quinn_proto.config.transport | 28 quinn_proto.congestion.bbr | 29 quinn_proto.congestion.cubic | 30 quinn_proto.config | 31 quinn_proto.connection.ack_frequency | 32 quinn_proto.token | 33 quinn_proto.shared | 34 quinn_proto | 35 quinn_proto.cid_queue | 36 quinn_proto.connection.packet_crypto | 37 quinn_proto.connection | 38 quinn_proto.endpoint | 39 quinn_proto.transport_error | 40 quinn_proto.crypto.rustls |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 quinn.connection | ||||||||||||||||||||||||||||||||||||||||
| 2 quinn_proto.coding | ||||||||||||||||||||||||||||||||||||||||
| 3 quinn_udp | ||||||||||||||||||||||||||||||||||||||||
| 4 quinn_udp.cmsg | ||||||||||||||||||||||||||||||||||||||||
| 5 quinn.incoming | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 6 quinn.runtime | 1 | |||||||||||||||||||||||||||||||||||||||
| 7 quinn_proto.bloom_token_log | 1 | |||||||||||||||||||||||||||||||||||||||
| 8 quinn_proto.packet | 1 | 5 | ||||||||||||||||||||||||||||||||||||||
| 9 quinn_proto.varint | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 10 quinn_udp.unix | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 11 quinn.runtime.smol | 3 | |||||||||||||||||||||||||||||||||||||||
| 12 quinn_proto.connection.assembler | 1 | |||||||||||||||||||||||||||||||||||||||
| 13 quinn_proto.connection.streams | 2 | 2 | 3 | 2 | 6 | |||||||||||||||||||||||||||||||||||
| 14 quinn_proto.frame | 2 | 4 | 1 | 2 | 4 | |||||||||||||||||||||||||||||||||||
| 15 quinn_proto.transport_parameters | 1 | 2 | 1 | 2 | 2 | 3 | 1 | |||||||||||||||||||||||||||||||||
| 16 quinn_udp.apple_fast | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 17 quinn.endpoint | 5 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 18 quinn_proto.connection.datagrams | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 19 quinn_proto.connection.streams.recv | 1 | 2 | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 20 quinn_proto.connection.streams.send | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 21 quinn_proto.connection.streams.state | 1 | 4 | 3 | 1 | 2 | 2 | 3 | |||||||||||||||||||||||||||||||||
| 22 quinn_proto.crypto | 2 | 7 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 23 quinn_proto.connection.spaces | 1 | 1 | 3 | 3 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 24 quinn_proto.connection.paths | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 25 quinn_proto.congestion | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 26 quinn_proto.connection.qlog | 2 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 27 quinn_proto.config.transport | 3 | 3 | ||||||||||||||||||||||||||||||||||||||
| 28 quinn_proto.congestion.bbr | 1 | 3 | ||||||||||||||||||||||||||||||||||||||
| 29 quinn_proto.congestion.cubic | 1 | 1 | 3 | |||||||||||||||||||||||||||||||||||||
| 30 quinn_proto.config | 2 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 31 quinn_proto.connection.ack_frequency | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 32 quinn_proto.token | 1 | 2 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 33 quinn_proto.shared | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 34 quinn_proto | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 35 quinn_proto.cid_queue | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 36 quinn_proto.connection.packet_crypto | 3 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 37 quinn_proto.connection | 1 | 5 | 2 | 3 | 5 | 2 | 2 | 2 | 2 | 5 | 2 | 2 | 2 | 1 | 1 | 7 | 6 | 1 | 2 | |||||||||||||||||||||
| 38 quinn_proto.endpoint | 4 | 1 | 5 | 1 | 4 | 2 | 12 | 4 | 4 | |||||||||||||||||||||||||||||||
| 39 quinn_proto.transport_error | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 40 quinn_proto.crypto.rustls | 3 | 4 | 2 | 3 | 2 | 1 | 1 |
5→1 quinn.incoming uses quinn.connection✕
- Connections
- 1 pair of types, where a type in quinn.incoming uses a type in quinn.connection.
- The types involved
quinn.incoming.Incoming→quinn.connection.State
- Direction
- quinn.incoming uses quinn.connection, so a change to quinn.connection can break quinn.incoming, while a change to quinn.incoming can't break quinn.connection.
- Position
- Below the diagonal: quinn.incoming uses a module listed above it, which is the healthy direction.
5→17 quinn.incoming uses quinn.endpoint part of a loop✕
- Connections
- 2 pairs of types, where a type in quinn.incoming uses a type in quinn.endpoint.
- The types involved
quinn.incoming.Incoming→quinn.endpoint.EndpointRefquinn.incoming.State→quinn.endpoint.EndpointRef
- Direction
- quinn.incoming uses quinn.endpoint, so a change to quinn.endpoint can break quinn.incoming, while a change to quinn.incoming can't break quinn.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→11 quinn.runtime uses quinn.runtime.smol part of a loop✕
- Connections
- 1 pair of types, where a type in quinn.runtime uses a type in quinn.runtime.smol.
- The types involved
quinn.runtime.Runtime→quinn.runtime.smol.UdpSocket
- Direction
- quinn.runtime uses quinn.runtime.smol, so a change to quinn.runtime.smol can break quinn.runtime, while a change to quinn.runtime can't break quinn.runtime.smol.
- 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→32 quinn_proto.bloom_token_log uses quinn_proto.token part of a loop✕
- Connections
- 1 pair of types, where a type in quinn_proto.bloom_token_log uses a type in quinn_proto.token.
- The types involved
quinn_proto.bloom_token_log.BloomTokenLog→quinn_proto.token.TokenLog
- Direction
- quinn_proto.bloom_token_log uses quinn_proto.token, so a change to quinn_proto.token can break quinn_proto.bloom_token_log, while a change to quinn_proto.bloom_token_log can't break quinn_proto.token.
- 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.
8→2 quinn_proto.packet uses quinn_proto.coding✕
- Connections
- 1 pair of types, where a type in quinn_proto.packet uses a type in quinn_proto.coding.
- The types involved
quinn_proto.packet.PacketDecodeError→quinn_proto.coding.UnexpectedEnd
- Direction
- quinn_proto.packet uses quinn_proto.coding, so a change to quinn_proto.coding can break quinn_proto.packet, while a change to quinn_proto.packet can't break quinn_proto.coding.
- Position
- Below the diagonal: quinn_proto.packet uses a module listed above it, which is the healthy direction.
8→33 quinn_proto.packet uses quinn_proto.shared part of a loop✕
- Connections
- 5 pairs of types, where a type in quinn_proto.packet uses a type in quinn_proto.shared.
- The types involved
quinn_proto.packet.Header→quinn_proto.shared.ConnectionIdquinn_proto.packet.InitialHeader→quinn_proto.shared.ConnectionIdquinn_proto.packet.PartialDecode→quinn_proto.shared.ConnectionIdquinn_proto.packet.ProtectedHeader→quinn_proto.shared.ConnectionIdquinn_proto.packet.ProtectedInitialHeader→quinn_proto.shared.ConnectionId
- Direction
- quinn_proto.packet uses quinn_proto.shared, so a change to quinn_proto.shared can break quinn_proto.packet, while a change to quinn_proto.packet can't break quinn_proto.shared.
- 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.
9→2 quinn_proto.varint uses quinn_proto.coding✕
- Connections
- 1 pair of types, where a type in quinn_proto.varint uses a type in quinn_proto.coding.
- The types involved
quinn_proto.varint.VarInt→quinn_proto.coding.Codec
- Direction
- quinn_proto.varint uses quinn_proto.coding, so a change to quinn_proto.coding can break quinn_proto.varint, while a change to quinn_proto.varint can't break quinn_proto.coding.
- Position
- Below the diagonal: quinn_proto.varint uses a module listed above it, which is the healthy direction.
9→34 quinn_proto.varint uses quinn_proto part of a loop✕
- Connections
- 1 pair of types, where a type in quinn_proto.varint uses a type in quinn_proto.
- The types involved
quinn_proto.varint.VarInt→quinn_proto.StreamId
- Direction
- quinn_proto.varint uses quinn_proto, so a change to quinn_proto can break quinn_proto.varint, while a change to quinn_proto.varint can't break quinn_proto.
- 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→3 quinn_udp.unix uses quinn_udp✕
- Connections
- 3 pairs of types, where a type in quinn_udp.unix uses a type in quinn_udp.
- The types involved
quinn_udp.unix.UdpSocketState→quinn_udp.Transmitquinn_udp.unix.UdpSocketState→quinn_udp.UdpSockRefquinn_udp.unix.unix$module→quinn_udp.Transmit
- Direction
- quinn_udp.unix uses quinn_udp, so a change to quinn_udp can break quinn_udp.unix, while a change to quinn_udp.unix can't break quinn_udp.
- Position
- Below the diagonal: quinn_udp.unix uses a module listed above it, which is the healthy direction.
10→4 quinn_udp.unix uses quinn_udp.cmsg✕
- Connections
- 1 pair of types, where a type in quinn_udp.unix uses a type in quinn_udp.cmsg.
- The types involved
quinn_udp.unix.ControlMetadata→quinn_udp.cmsg.CMsg
- Direction
- quinn_udp.unix uses quinn_udp.cmsg, so a change to quinn_udp.cmsg can break quinn_udp.unix, while a change to quinn_udp.unix can't break quinn_udp.cmsg.
- Position
- Below the diagonal: quinn_udp.unix uses a module listed above it, which is the healthy direction.
11→6 quinn.runtime.smol uses quinn.runtime✕
- Connections
- 3 pairs of types, where a type in quinn.runtime.smol uses a type in quinn.runtime.
- The types involved
quinn.runtime.smol.SmolRuntime→quinn.runtime.Runtimequinn.runtime.smol.UdpSocket→quinn.runtime.AsyncUdpSocketquinn.runtime.smol.UdpSocket→quinn.runtime.UdpSenderHelperSocket
- Direction
- quinn.runtime.smol uses quinn.runtime, so a change to quinn.runtime can break quinn.runtime.smol, while a change to quinn.runtime.smol can't break quinn.runtime.
- Position
- Below the diagonal: quinn.runtime.smol uses a module listed above it, which is the healthy direction.
12→7 quinn_proto.connection.assembler uses quinn_proto.bloom_token_log✕
- Connections
- 1 pair of types, where a type in quinn_proto.connection.assembler uses a type in quinn_proto.bloom_token_log.
- The types involved
quinn_proto.connection.assembler.Assembler→quinn_proto.bloom_token_log.State
- Direction
- quinn_proto.connection.assembler uses quinn_proto.bloom_token_log, so a change to quinn_proto.bloom_token_log can break quinn_proto.connection.assembler, while a change to quinn_proto.connection.assembler can't break quinn_proto.bloom_token_log.
- Position
- Below the diagonal: quinn_proto.connection.assembler uses a module listed above it, which is the healthy direction.
13→7 quinn_proto.connection.streams uses quinn_proto.bloom_token_log✕
- Connections
- 2 pairs of types, where a type in quinn_proto.connection.streams uses a type in quinn_proto.bloom_token_log.
- The types involved
quinn_proto.connection.streams.SendStream→quinn_proto.bloom_token_log.Statequinn_proto.connection.streams.Streams→quinn_proto.bloom_token_log.State
- Direction
- quinn_proto.connection.streams uses quinn_proto.bloom_token_log, so a change to quinn_proto.bloom_token_log can break quinn_proto.connection.streams, while a change to quinn_proto.connection.streams can't break quinn_proto.bloom_token_log.
- Position
- Below the diagonal: quinn_proto.connection.streams uses a module listed above it, which is the healthy direction.
13→9 quinn_proto.connection.streams uses quinn_proto.varint✕
- Connections
- 2 pairs of types, where a type in quinn_proto.connection.streams uses a type in quinn_proto.varint.
- The types involved
quinn_proto.connection.streams.RecvStream→quinn_proto.varint.VarIntquinn_proto.connection.streams.SendStream→quinn_proto.varint.VarInt
- Direction
- quinn_proto.connection.streams uses quinn_proto.varint, so a change to quinn_proto.varint can break quinn_proto.connection.streams, while a change to quinn_proto.connection.streams can't break quinn_proto.varint.
- Position
- Below the diagonal: quinn_proto.connection.streams uses a module listed above it, which is the healthy direction.
13→21 quinn_proto.connection.streams uses quinn_proto.connection.streams.state part of a loop✕
- Connections
- 3 pairs of types, where a type in quinn_proto.connection.streams uses a type in quinn_proto.connection.streams.state.
- The types involved
quinn_proto.connection.streams.RecvStream→quinn_proto.connection.streams.state.StreamsStatequinn_proto.connection.streams.SendStream→quinn_proto.connection.streams.state.StreamsStatequinn_proto.connection.streams.Streams→quinn_proto.connection.streams.state.StreamsState
- Direction
- quinn_proto.connection.streams uses quinn_proto.connection.streams.state, so a change to quinn_proto.connection.streams.state can break quinn_proto.connection.streams, while a change to quinn_proto.connection.streams can't break quinn_proto.connection.streams.state.
- 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→23 quinn_proto.connection.streams uses quinn_proto.connection.spaces part of a loop✕
- Connections
- 2 pairs of types, where a type in quinn_proto.connection.streams uses a type in quinn_proto.connection.spaces.
- The types involved
quinn_proto.connection.streams.RecvStream→quinn_proto.connection.spaces.Retransmitsquinn_proto.connection.streams.SendStream→quinn_proto.connection.spaces.Retransmits
- Direction
- quinn_proto.connection.streams uses quinn_proto.connection.spaces, so a change to quinn_proto.connection.spaces can break quinn_proto.connection.streams, while a change to quinn_proto.connection.streams can't break quinn_proto.connection.spaces.
- 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→34 quinn_proto.connection.streams uses quinn_proto part of a loop✕
- Connections
- 6 pairs of types, where a type in quinn_proto.connection.streams uses a type in quinn_proto.
- The types involved
quinn_proto.connection.streams.PendingStream→quinn_proto.StreamIdquinn_proto.connection.streams.PendingStreamsQueue→quinn_proto.StreamIdquinn_proto.connection.streams.RecvStream→quinn_proto.StreamIdquinn_proto.connection.streams.SendStream→quinn_proto.StreamIdquinn_proto.connection.streams.Streams→quinn_proto.Dirquinn_proto.connection.streams.Streams→quinn_proto.StreamId
- Direction
- quinn_proto.connection.streams uses quinn_proto, so a change to quinn_proto can break quinn_proto.connection.streams, while a change to quinn_proto.connection.streams can't break quinn_proto.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→2 quinn_proto.frame uses quinn_proto.coding✕
- Connections
- 2 pairs of types, where a type in quinn_proto.frame uses a type in quinn_proto.coding.
- The types involved
quinn_proto.frame.FrameType→quinn_proto.coding.Codecquinn_proto.frame.IterErr→quinn_proto.coding.UnexpectedEnd
- Direction
- quinn_proto.frame uses quinn_proto.coding, so a change to quinn_proto.coding can break quinn_proto.frame, while a change to quinn_proto.frame can't break quinn_proto.coding.
- Position
- Below the diagonal: quinn_proto.frame uses a module listed above it, which is the healthy direction.
14→9 quinn_proto.frame uses quinn_proto.varint✕
- Connections
- 4 pairs of types, where a type in quinn_proto.frame uses a type in quinn_proto.varint.
- The types involved
quinn_proto.frame.AckFrequency→quinn_proto.varint.VarIntquinn_proto.frame.ApplicationClose→quinn_proto.varint.VarIntquinn_proto.frame.ResetStream→quinn_proto.varint.VarIntquinn_proto.frame.StopSending→quinn_proto.varint.VarInt
- Direction
- quinn_proto.frame uses quinn_proto.varint, so a change to quinn_proto.varint can break quinn_proto.frame, while a change to quinn_proto.frame can't break quinn_proto.varint.
- Position
- Below the diagonal: quinn_proto.frame uses a module listed above it, which is the healthy direction.
14→32 quinn_proto.frame uses quinn_proto.token part of a loop✕
- Connections
- 1 pair of types, where a type in quinn_proto.frame uses a type in quinn_proto.token.
- The types involved
quinn_proto.frame.NewConnectionId→quinn_proto.token.ResetToken
- Direction
- quinn_proto.frame uses quinn_proto.token, so a change to quinn_proto.token can break quinn_proto.frame, while a change to quinn_proto.frame can't break quinn_proto.token.
- 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→33 quinn_proto.frame uses quinn_proto.shared part of a loop✕
- Connections
- 2 pairs of types, where a type in quinn_proto.frame uses a type in quinn_proto.shared.
- The types involved
quinn_proto.frame.EcnCounts→quinn_proto.shared.EcnCodepointquinn_proto.frame.NewConnectionId→quinn_proto.shared.ConnectionId
- Direction
- quinn_proto.frame uses quinn_proto.shared, so a change to quinn_proto.shared can break quinn_proto.frame, while a change to quinn_proto.frame can't break quinn_proto.shared.
- 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→34 quinn_proto.frame uses quinn_proto part of a loop✕
- Connections
- 4 pairs of types, where a type in quinn_proto.frame uses a type in quinn_proto.
- The types involved
quinn_proto.frame.ResetStream→quinn_proto.StreamIdquinn_proto.frame.StopSending→quinn_proto.StreamIdquinn_proto.frame.Stream→quinn_proto.StreamIdquinn_proto.frame.StreamMeta→quinn_proto.StreamId
- Direction
- quinn_proto.frame uses quinn_proto, so a change to quinn_proto can break quinn_proto.frame, while a change to quinn_proto.frame can't break quinn_proto.
- 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→2 quinn_proto.transport_parameters uses quinn_proto.coding✕
- Connections
- 1 pair of types, where a type in quinn_proto.transport_parameters uses a type in quinn_proto.coding.
- The types involved
quinn_proto.transport_parameters.Error→quinn_proto.coding.UnexpectedEnd
- Direction
- quinn_proto.transport_parameters uses quinn_proto.coding, so a change to quinn_proto.coding can break quinn_proto.transport_parameters, while a change to quinn_proto.transport_parameters can't break quinn_proto.coding.
- Position
- Below the diagonal: quinn_proto.transport_parameters uses a module listed above it, which is the healthy direction.
15→9 quinn_proto.transport_parameters uses quinn_proto.varint✕
- Connections
- 2 pairs of types, where a type in quinn_proto.transport_parameters uses a type in quinn_proto.varint.
- The types involved
quinn_proto.transport_parameters.ReservedTransportParameter→quinn_proto.varint.VarIntquinn_proto.transport_parameters.TransportParameters→quinn_proto.varint.VarInt
- Direction
- quinn_proto.transport_parameters uses quinn_proto.varint, so a change to quinn_proto.varint can break quinn_proto.transport_parameters, while a change to quinn_proto.transport_parameters can't break quinn_proto.varint.
- Position
- Below the diagonal: quinn_proto.transport_parameters uses a module listed above it, which is the healthy direction.
15→27 quinn_proto.transport_parameters uses quinn_proto.config.transport part of a loop✕
- Connections
- 1 pair of types, where a type in quinn_proto.transport_parameters uses a type in quinn_proto.config.transport.
- The types involved
quinn_proto.transport_parameters.TransportParameters→quinn_proto.config.transport.TransportConfig
- Direction
- quinn_proto.transport_parameters uses quinn_proto.config.transport, so a change to quinn_proto.config.transport can break quinn_proto.transport_parameters, while a change to quinn_proto.transport_parameters can't break quinn_proto.config.transport.
- 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→30 quinn_proto.transport_parameters uses quinn_proto.config part of a loop✕
- Connections
- 2 pairs of types, where a type in quinn_proto.transport_parameters uses a type in quinn_proto.config.
- The types involved
quinn_proto.transport_parameters.TransportParameters→quinn_proto.config.EndpointConfigquinn_proto.transport_parameters.TransportParameters→quinn_proto.config.ServerConfig
- Direction
- quinn_proto.transport_parameters uses quinn_proto.config, so a change to quinn_proto.config can break quinn_proto.transport_parameters, while a change to quinn_proto.transport_parameters can't break quinn_proto.config.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→32 quinn_proto.transport_parameters uses quinn_proto.token part of a loop✕
- Connections
- 2 pairs of types, where a type in quinn_proto.transport_parameters uses a type in quinn_proto.token.
- The types involved
quinn_proto.transport_parameters.PreferredAddress→quinn_proto.token.ResetTokenquinn_proto.transport_parameters.TransportParameters→quinn_proto.token.ResetToken
- Direction
- quinn_proto.transport_parameters uses quinn_proto.token, so a change to quinn_proto.token can break quinn_proto.transport_parameters, while a change to quinn_proto.transport_parameters can't break quinn_proto.token.
- 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→33 quinn_proto.transport_parameters uses quinn_proto.shared part of a loop✕
- Connections
- 3 pairs of types, where a type in quinn_proto.transport_parameters uses a type in quinn_proto.shared.
- The types involved
quinn_proto.transport_parameters.PreferredAddress→quinn_proto.shared.ConnectionIdquinn_proto.transport_parameters.TransportParameters→quinn_proto.shared.ConnectionIdquinn_proto.transport_parameters.transport_parameters$module→quinn_proto.shared.ConnectionId
- Direction
- quinn_proto.transport_parameters uses quinn_proto.shared, so a change to quinn_proto.shared can break quinn_proto.transport_parameters, while a change to quinn_proto.transport_parameters can't break quinn_proto.shared.
- 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→34 quinn_proto.transport_parameters uses quinn_proto part of a loop✕
- Connections
- 1 pair of types, where a type in quinn_proto.transport_parameters uses a type in quinn_proto.
- The types involved
quinn_proto.transport_parameters.TransportParameters→quinn_proto.Side
- Direction
- quinn_proto.transport_parameters uses quinn_proto, so a change to quinn_proto can break quinn_proto.transport_parameters, while a change to quinn_proto.transport_parameters can't break quinn_proto.
- 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→3 quinn_udp.apple_fast uses quinn_udp✕
- Connections
- 1 pair of types, where a type in quinn_udp.apple_fast uses a type in quinn_udp.
- The types involved
quinn_udp.apple_fast.apple_fast$module→quinn_udp.Transmit
- Direction
- quinn_udp.apple_fast uses quinn_udp, so a change to quinn_udp can break quinn_udp.apple_fast, while a change to quinn_udp.apple_fast can't break quinn_udp.
- Position
- Below the diagonal: quinn_udp.apple_fast uses a module listed above it, which is the healthy direction.
16→4 quinn_udp.apple_fast uses quinn_udp.cmsg✕
- Connections
- 1 pair of types, where a type in quinn_udp.apple_fast uses a type in quinn_udp.cmsg.
- The types involved
quinn_udp.apple_fast.msghdr_x→quinn_udp.cmsg.MsgHdr
- Direction
- quinn_udp.apple_fast uses quinn_udp.cmsg, so a change to quinn_udp.cmsg can break quinn_udp.apple_fast, while a change to quinn_udp.apple_fast can't break quinn_udp.cmsg.
- Position
- Below the diagonal: quinn_udp.apple_fast uses a module listed above it, which is the healthy direction.
16→10 quinn_udp.apple_fast uses quinn_udp.unix✕
- Connections
- 1 pair of types, where a type in quinn_udp.apple_fast uses a type in quinn_udp.unix.
- The types involved
quinn_udp.apple_fast.apple_fast$module→quinn_udp.unix.UdpSocketState
- Direction
- quinn_udp.apple_fast uses quinn_udp.unix, so a change to quinn_udp.unix can break quinn_udp.apple_fast, while a change to quinn_udp.apple_fast can't break quinn_udp.unix.
- Position
- Below the diagonal: quinn_udp.apple_fast uses a module listed above it, which is the healthy direction.
17→1 quinn.endpoint uses quinn.connection✕
- Connections
- 5 pairs of types, where a type in quinn.endpoint uses a type in quinn.connection.
- The types involved
quinn.endpoint.ConnectionSet→quinn.connection.Connectingquinn.endpoint.ConnectionSet→quinn.connection.Connectionquinn.endpoint.EndpointInner→quinn.connection.Sharedquinn.endpoint.EndpointInner→quinn.connection.Statequinn.endpoint.State→quinn.connection.Shared
- Direction
- quinn.endpoint uses quinn.connection, so a change to quinn.connection can break quinn.endpoint, while a change to quinn.endpoint can't break quinn.connection.
- Position
- Below the diagonal: quinn.endpoint uses a module listed above it, which is the healthy direction.
17→5 quinn.endpoint uses quinn.incoming✕
- Connections
- 1 pair of types, where a type in quinn.endpoint uses a type in quinn.incoming.
- The types involved
quinn.endpoint.EndpointInner→quinn.incoming.Incoming
- Direction
- quinn.endpoint uses quinn.incoming, so a change to quinn.incoming can break quinn.endpoint, while a change to quinn.endpoint can't break quinn.incoming.
- Position
- Below the diagonal: quinn.endpoint uses a module listed above it, which is the healthy direction.
17→11 quinn.endpoint uses quinn.runtime.smol✕
- Connections
- 1 pair of types, where a type in quinn.endpoint uses a type in quinn.runtime.smol.
- The types involved
quinn.endpoint.Endpoint→quinn.runtime.smol.UdpSocket
- Direction
- quinn.endpoint uses quinn.runtime.smol, so a change to quinn.runtime.smol can break quinn.endpoint, while a change to quinn.endpoint can't break quinn.runtime.smol.
- Position
- Below the diagonal: quinn.endpoint uses a module listed above it, which is the healthy direction.
18→14 quinn_proto.connection.datagrams uses quinn_proto.frame✕
- Connections
- 2 pairs of types, where a type in quinn_proto.connection.datagrams uses a type in quinn_proto.frame.
- The types involved
quinn_proto.connection.datagrams.DatagramBuffer→quinn_proto.frame.Datagramquinn_proto.connection.datagrams.DatagramState→quinn_proto.frame.Datagram
- Direction
- quinn_proto.connection.datagrams uses quinn_proto.frame, so a change to quinn_proto.frame can break quinn_proto.connection.datagrams, while a change to quinn_proto.connection.datagrams can't break quinn_proto.frame.
- Position
- Below the diagonal: quinn_proto.connection.datagrams uses a module listed above it, which is the healthy direction.
18→37 quinn_proto.connection.datagrams uses quinn_proto.connection part of a loop✕
- Connections
- 1 pair of types, where a type in quinn_proto.connection.datagrams uses a type in quinn_proto.connection.
- The types involved
quinn_proto.connection.datagrams.Datagrams→quinn_proto.connection.Connection
- Direction
- quinn_proto.connection.datagrams uses quinn_proto.connection, so a change to quinn_proto.connection can break quinn_proto.connection.datagrams, while a change to quinn_proto.connection.datagrams can't break quinn_proto.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.
19→9 quinn_proto.connection.streams.recv uses quinn_proto.varint✕
- Connections
- 1 pair of types, where a type in quinn_proto.connection.streams.recv uses a type in quinn_proto.varint.
- The types involved
quinn_proto.connection.streams.recv.Recv→quinn_proto.varint.VarInt
- Direction
- quinn_proto.connection.streams.recv uses quinn_proto.varint, so a change to quinn_proto.varint can break quinn_proto.connection.streams.recv, while a change to quinn_proto.connection.streams.recv can't break quinn_proto.varint.
- Position
- Below the diagonal: quinn_proto.connection.streams.recv uses a module listed above it, which is the healthy direction.
19→12 quinn_proto.connection.streams.recv uses quinn_proto.connection.assembler✕
- Connections
- 2 pairs of types, where a type in quinn_proto.connection.streams.recv uses a type in quinn_proto.connection.assembler.
- The types involved
quinn_proto.connection.streams.recv.ReadableError→quinn_proto.connection.assembler.IllegalOrderedReadquinn_proto.connection.streams.recv.Recv→quinn_proto.connection.assembler.Assembler
- Direction
- quinn_proto.connection.streams.recv uses quinn_proto.connection.assembler, so a change to quinn_proto.connection.assembler can break quinn_proto.connection.streams.recv, while a change to quinn_proto.connection.streams.recv can't break quinn_proto.connection.assembler.
- Position
- Below the diagonal: quinn_proto.connection.streams.recv uses a module listed above it, which is the healthy direction.
19→13 quinn_proto.connection.streams.recv uses quinn_proto.connection.streams✕
- Connections
- 1 pair of types, where a type in quinn_proto.connection.streams.recv uses a type in quinn_proto.connection.streams.
- The types involved
quinn_proto.connection.streams.recv.Chunks→quinn_proto.connection.streams.ShouldTransmit
- Direction
- quinn_proto.connection.streams.recv uses quinn_proto.connection.streams, so a change to quinn_proto.connection.streams can break quinn_proto.connection.streams.recv, while a change to quinn_proto.connection.streams.recv can't break quinn_proto.connection.streams.
- Position
- Below the diagonal: quinn_proto.connection.streams.recv uses a module listed above it, which is the healthy direction.
19→14 quinn_proto.connection.streams.recv uses quinn_proto.frame✕
- Connections
- 1 pair of types, where a type in quinn_proto.connection.streams.recv uses a type in quinn_proto.frame.
- The types involved
quinn_proto.connection.streams.recv.Recv→quinn_proto.frame.Stream
- Direction
- quinn_proto.connection.streams.recv uses quinn_proto.frame, so a change to quinn_proto.frame can break quinn_proto.connection.streams.recv, while a change to quinn_proto.connection.streams.recv can't break quinn_proto.frame.
- Position
- Below the diagonal: quinn_proto.connection.streams.recv uses a module listed above it, which is the healthy direction.
19→21 quinn_proto.connection.streams.recv uses quinn_proto.connection.streams.state part of a loop✕
- Connections
- 1 pair of types, where a type in quinn_proto.connection.streams.recv uses a type in quinn_proto.connection.streams.state.
- The types involved
quinn_proto.connection.streams.recv.Chunks→quinn_proto.connection.streams.state.StreamsState
- Direction
- quinn_proto.connection.streams.recv uses quinn_proto.connection.streams.state, so a change to quinn_proto.connection.streams.state can break quinn_proto.connection.streams.recv, while a change to quinn_proto.connection.streams.recv can't break quinn_proto.connection.streams.state.
- 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→23 quinn_proto.connection.streams.recv uses quinn_proto.connection.spaces part of a loop✕
- Connections
- 1 pair of types, where a type in quinn_proto.connection.streams.recv uses a type in quinn_proto.connection.spaces.
- The types involved
quinn_proto.connection.streams.recv.Chunks→quinn_proto.connection.spaces.Retransmits
- Direction
- quinn_proto.connection.streams.recv uses quinn_proto.connection.spaces, so a change to quinn_proto.connection.spaces can break quinn_proto.connection.streams.recv, while a change to quinn_proto.connection.streams.recv can't break quinn_proto.connection.spaces.
- 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→34 quinn_proto.connection.streams.recv uses quinn_proto part of a loop✕
- Connections
- 1 pair of types, where a type in quinn_proto.connection.streams.recv uses a type in quinn_proto.
- The types involved
quinn_proto.connection.streams.recv.Chunks→quinn_proto.StreamId
- Direction
- quinn_proto.connection.streams.recv uses quinn_proto, so a change to quinn_proto can break quinn_proto.connection.streams.recv, while a change to quinn_proto.connection.streams.recv can't break quinn_proto.
- 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→9 quinn_proto.connection.streams.send uses quinn_proto.varint✕
- Connections
- 1 pair of types, where a type in quinn_proto.connection.streams.send uses a type in quinn_proto.varint.
- The types involved
quinn_proto.connection.streams.send.Send→quinn_proto.varint.VarInt
- Direction
- quinn_proto.connection.streams.send uses quinn_proto.varint, so a change to quinn_proto.varint can break quinn_proto.connection.streams.send, while a change to quinn_proto.connection.streams.send can't break quinn_proto.varint.
- Position
- Below the diagonal: quinn_proto.connection.streams.send uses a module listed above it, which is the healthy direction.
20→14 quinn_proto.connection.streams.send uses quinn_proto.frame✕
- Connections
- 1 pair of types, where a type in quinn_proto.connection.streams.send uses a type in quinn_proto.frame.
- The types involved
quinn_proto.connection.streams.send.Send→quinn_proto.frame.StreamMeta
- Direction
- quinn_proto.connection.streams.send uses quinn_proto.frame, so a change to quinn_proto.frame can break quinn_proto.connection.streams.send, while a change to quinn_proto.connection.streams.send can't break quinn_proto.frame.
- Position
- Below the diagonal: quinn_proto.connection.streams.send uses a module listed above it, which is the healthy direction.
21→9 quinn_proto.connection.streams.state uses quinn_proto.varint✕
- Connections
- 1 pair of types, where a type in quinn_proto.connection.streams.state uses a type in quinn_proto.varint.
- The types involved
quinn_proto.connection.streams.state.StreamsState→quinn_proto.varint.VarInt
- Direction
- quinn_proto.connection.streams.state uses quinn_proto.varint, so a change to quinn_proto.varint can break quinn_proto.connection.streams.state, while a change to quinn_proto.connection.streams.state can't break quinn_proto.varint.
- Position
- Below the diagonal: quinn_proto.connection.streams.state uses a module listed above it, which is the healthy direction.
21→13 quinn_proto.connection.streams.state uses quinn_proto.connection.streams✕
- Connections
- 4 pairs of types, where a type in quinn_proto.connection.streams.state uses a type in quinn_proto.connection.streams.
- The types involved
quinn_proto.connection.streams.state.StreamsState→quinn_proto.connection.streams.PendingStreamsQueuequinn_proto.connection.streams.state.StreamsState→quinn_proto.connection.streams.ShouldTransmitquinn_proto.connection.streams.state.StreamsState→quinn_proto.connection.streams.StreamEventquinn_proto.connection.streams.state.StreamsState→quinn_proto.connection.streams.StreamHalf
- Direction
- quinn_proto.connection.streams.state uses quinn_proto.connection.streams, so a change to quinn_proto.connection.streams can break quinn_proto.connection.streams.state, while a change to quinn_proto.connection.streams.state can't break quinn_proto.connection.streams.
- Position
- Below the diagonal: quinn_proto.connection.streams.state uses a module listed above it, which is the healthy direction.
21→14 quinn_proto.connection.streams.state uses quinn_proto.frame✕
- Connections
- 3 pairs of types, where a type in quinn_proto.connection.streams.state uses a type in quinn_proto.frame.
- The types involved
quinn_proto.connection.streams.state.StreamsState→quinn_proto.frame.ResetStreamquinn_proto.connection.streams.state.StreamsState→quinn_proto.frame.Streamquinn_proto.connection.streams.state.StreamsState→quinn_proto.frame.StreamMeta
- Direction
- quinn_proto.connection.streams.state uses quinn_proto.frame, so a change to quinn_proto.frame can break quinn_proto.connection.streams.state, while a change to quinn_proto.connection.streams.state can't break quinn_proto.frame.
- Position
- Below the diagonal: quinn_proto.connection.streams.state uses a module listed above it, which is the healthy direction.
21→15 quinn_proto.connection.streams.state uses quinn_proto.transport_parameters✕
- Connections
- 1 pair of types, where a type in quinn_proto.connection.streams.state uses a type in quinn_proto.transport_parameters.
- The types involved
quinn_proto.connection.streams.state.StreamsState→quinn_proto.transport_parameters.TransportParameters
- Direction
- quinn_proto.connection.streams.state uses quinn_proto.transport_parameters, so a change to quinn_proto.transport_parameters can break quinn_proto.connection.streams.state, while a change to quinn_proto.connection.streams.state can't break quinn_proto.transport_parameters.
- Position
- Below the diagonal: quinn_proto.connection.streams.state uses a module listed above it, which is the healthy direction.
21→19 quinn_proto.connection.streams.state uses quinn_proto.connection.streams.recv✕
- Connections
- 2 pairs of types, where a type in quinn_proto.connection.streams.state uses a type in quinn_proto.connection.streams.recv.
- The types involved
quinn_proto.connection.streams.state.StreamRecv→quinn_proto.connection.streams.recv.Recvquinn_proto.connection.streams.state.state$module→quinn_proto.connection.streams.recv.Recv
- Direction
- quinn_proto.connection.streams.state uses quinn_proto.connection.streams.recv, so a change to quinn_proto.connection.streams.recv can break quinn_proto.connection.streams.state, while a change to quinn_proto.connection.streams.state can't break quinn_proto.connection.streams.recv.
- Position
- Below the diagonal: quinn_proto.connection.streams.state uses a module listed above it, which is the healthy direction.
21→23 quinn_proto.connection.streams.state uses quinn_proto.connection.spaces part of a loop✕
- Connections
- 2 pairs of types, where a type in quinn_proto.connection.streams.state uses a type in quinn_proto.connection.spaces.
- The types involved
quinn_proto.connection.streams.state.StreamsState→quinn_proto.connection.spaces.Retransmitsquinn_proto.connection.streams.state.StreamsState→quinn_proto.connection.spaces.ThinRetransmits
- Direction
- quinn_proto.connection.streams.state uses quinn_proto.connection.spaces, so a change to quinn_proto.connection.spaces can break quinn_proto.connection.streams.state, while a change to quinn_proto.connection.streams.state can't break quinn_proto.connection.spaces.
- 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→34 quinn_proto.connection.streams.state uses quinn_proto part of a loop✕
- Connections
- 3 pairs of types, where a type in quinn_proto.connection.streams.state uses a type in quinn_proto.
- The types involved
quinn_proto.connection.streams.state.StreamsState→quinn_proto.Dirquinn_proto.connection.streams.state.StreamsState→quinn_proto.Sidequinn_proto.connection.streams.state.StreamsState→quinn_proto.StreamId
- Direction
- quinn_proto.connection.streams.state uses quinn_proto, so a change to quinn_proto can break quinn_proto.connection.streams.state, while a change to quinn_proto.connection.streams.state can't break quinn_proto.
- 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→15 quinn_proto.crypto uses quinn_proto.transport_parameters✕
- Connections
- 2 pairs of types, where a type in quinn_proto.crypto uses a type in quinn_proto.transport_parameters.
- The types involved
quinn_proto.crypto.ClientConfig→quinn_proto.transport_parameters.TransportParametersquinn_proto.crypto.ServerConfig→quinn_proto.transport_parameters.TransportParameters
- Direction
- quinn_proto.crypto uses quinn_proto.transport_parameters, so a change to quinn_proto.transport_parameters can break quinn_proto.crypto, while a change to quinn_proto.crypto can't break quinn_proto.transport_parameters.
- Position
- Below the diagonal: quinn_proto.crypto uses a module listed above it, which is the healthy direction.
22→20 quinn_proto.crypto uses quinn_proto.connection.streams.send✕
- Connections
- 7 pairs of types, where a type in quinn_proto.crypto uses a type in quinn_proto.connection.streams.send.
- The types involved
quinn_proto.crypto.ClientConfig→quinn_proto.connection.streams.send.Sendquinn_proto.crypto.HandshakeTokenKey→quinn_proto.connection.streams.send.Sendquinn_proto.crypto.HeaderKey→quinn_proto.connection.streams.send.Sendquinn_proto.crypto.HmacKey→quinn_proto.connection.streams.send.Sendquinn_proto.crypto.PacketKey→quinn_proto.connection.streams.send.Sendquinn_proto.crypto.ServerConfig→quinn_proto.connection.streams.send.Sendquinn_proto.crypto.Session→quinn_proto.connection.streams.send.Send
- Direction
- quinn_proto.crypto uses quinn_proto.connection.streams.send, so a change to quinn_proto.connection.streams.send can break quinn_proto.crypto, while a change to quinn_proto.crypto can't break quinn_proto.connection.streams.send.
- Position
- Below the diagonal: quinn_proto.crypto uses a module listed above it, which is the healthy direction.
22→33 quinn_proto.crypto uses quinn_proto.shared part of a loop✕
- Connections
- 2 pairs of types, where a type in quinn_proto.crypto uses a type in quinn_proto.shared.
- The types involved
quinn_proto.crypto.ServerConfig→quinn_proto.shared.ConnectionIdquinn_proto.crypto.Session→quinn_proto.shared.ConnectionId
- Direction
- quinn_proto.crypto uses quinn_proto.shared, so a change to quinn_proto.shared can break quinn_proto.crypto, while a change to quinn_proto.crypto can't break quinn_proto.shared.
- 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→34 quinn_proto.crypto uses quinn_proto part of a loop✕
- Connections
- 1 pair of types, where a type in quinn_proto.crypto uses a type in quinn_proto.
- The types involved
quinn_proto.crypto.Session→quinn_proto.Side
- Direction
- quinn_proto.crypto uses quinn_proto, so a change to quinn_proto can break quinn_proto.crypto, while a change to quinn_proto.crypto can't break quinn_proto.
- 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→8 quinn_proto.connection.spaces uses quinn_proto.packet✕
- Connections
- 1 pair of types, where a type in quinn_proto.connection.spaces uses a type in quinn_proto.packet.
- The types involved
quinn_proto.connection.spaces.PacketNumberFilter→quinn_proto.packet.SpaceId
- Direction
- quinn_proto.connection.spaces uses quinn_proto.packet, so a change to quinn_proto.packet can break quinn_proto.connection.spaces, while a change to quinn_proto.connection.spaces can't break quinn_proto.packet.
- Position
- Below the diagonal: quinn_proto.connection.spaces uses a module listed above it, which is the healthy direction.
23→12 quinn_proto.connection.spaces uses quinn_proto.connection.assembler✕
- Connections
- 1 pair of types, where a type in quinn_proto.connection.spaces uses a type in quinn_proto.connection.assembler.
- The types involved
quinn_proto.connection.spaces.PacketSpace→quinn_proto.connection.assembler.Assembler
- Direction
- quinn_proto.connection.spaces uses quinn_proto.connection.assembler, so a change to quinn_proto.connection.assembler can break quinn_proto.connection.spaces, while a change to quinn_proto.connection.spaces can't break quinn_proto.connection.assembler.
- Position
- Below the diagonal: quinn_proto.connection.spaces uses a module listed above it, which is the healthy direction.
23→14 quinn_proto.connection.spaces uses quinn_proto.frame✕
- Connections
- 3 pairs of types, where a type in quinn_proto.connection.spaces uses a type in quinn_proto.frame.
- The types involved
quinn_proto.connection.spaces.PacketSpace→quinn_proto.frame.EcnCountsquinn_proto.connection.spaces.PendingAcks→quinn_proto.frame.AckFrequencyquinn_proto.connection.spaces.Retransmits→quinn_proto.frame.StopSending
- Direction
- quinn_proto.connection.spaces uses quinn_proto.frame, so a change to quinn_proto.frame can break quinn_proto.connection.spaces, while a change to quinn_proto.connection.spaces can't break quinn_proto.frame.
- Position
- Below the diagonal: quinn_proto.connection.spaces uses a module listed above it, which is the healthy direction.
23→21 quinn_proto.connection.spaces uses quinn_proto.connection.streams.state✕
- Connections
- 3 pairs of types, where a type in quinn_proto.connection.spaces uses a type in quinn_proto.connection.streams.state.
- The types involved
quinn_proto.connection.spaces.PacketSpace→quinn_proto.connection.streams.state.StreamsStatequinn_proto.connection.spaces.Retransmits→quinn_proto.connection.streams.state.StreamsStatequinn_proto.connection.spaces.ThinRetransmits→quinn_proto.connection.streams.state.StreamsState
- Direction
- quinn_proto.connection.spaces uses quinn_proto.connection.streams.state, so a change to quinn_proto.connection.streams.state can break quinn_proto.connection.spaces, while a change to quinn_proto.connection.spaces can't break quinn_proto.connection.streams.state.
- Position
- Below the diagonal: quinn_proto.connection.spaces uses a module listed above it, which is the healthy direction.
23→22 quinn_proto.connection.spaces uses quinn_proto.crypto✕
- Connections
- 1 pair of types, where a type in quinn_proto.connection.spaces uses a type in quinn_proto.crypto.
- The types involved
quinn_proto.connection.spaces.PacketSpace→quinn_proto.crypto.Keys
- Direction
- quinn_proto.connection.spaces uses quinn_proto.crypto, so a change to quinn_proto.crypto can break quinn_proto.connection.spaces, while a change to quinn_proto.connection.spaces can't break quinn_proto.crypto.
- Position
- Below the diagonal: quinn_proto.connection.spaces uses a module listed above it, which is the healthy direction.
23→33 quinn_proto.connection.spaces uses quinn_proto.shared part of a loop✕
- Connections
- 1 pair of types, where a type in quinn_proto.connection.spaces uses a type in quinn_proto.shared.
- The types involved
quinn_proto.connection.spaces.Retransmits→quinn_proto.shared.IssuedCid
- Direction
- quinn_proto.connection.spaces uses quinn_proto.shared, so a change to quinn_proto.shared can break quinn_proto.connection.spaces, while a change to quinn_proto.connection.spaces can't break quinn_proto.shared.
- 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→23 quinn_proto.connection.paths uses quinn_proto.connection.spaces✕
- Connections
- 3 pairs of types, where a type in quinn_proto.connection.paths uses a type in quinn_proto.connection.spaces.
- The types involved
quinn_proto.connection.paths.InFlight→quinn_proto.connection.spaces.SentPacketquinn_proto.connection.paths.PathData→quinn_proto.connection.spaces.PacketSpacequinn_proto.connection.paths.PathData→quinn_proto.connection.spaces.SentPacket
- Direction
- quinn_proto.connection.paths uses quinn_proto.connection.spaces, so a change to quinn_proto.connection.spaces can break quinn_proto.connection.paths, while a change to quinn_proto.connection.paths can't break quinn_proto.connection.spaces.
- Position
- Below the diagonal: quinn_proto.connection.paths uses a module listed above it, which is the healthy direction.
24→27 quinn_proto.connection.paths uses quinn_proto.config.transport part of a loop✕
- Connections
- 1 pair of types, where a type in quinn_proto.connection.paths uses a type in quinn_proto.config.transport.
- The types involved
quinn_proto.connection.paths.PathData→quinn_proto.config.transport.TransportConfig
- Direction
- quinn_proto.connection.paths uses quinn_proto.config.transport, so a change to quinn_proto.config.transport can break quinn_proto.connection.paths, while a change to quinn_proto.connection.paths can't break quinn_proto.config.transport.
- 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→20 quinn_proto.congestion uses quinn_proto.connection.streams.send✕
- Connections
- 1 pair of types, where a type in quinn_proto.congestion uses a type in quinn_proto.connection.streams.send.
- The types involved
quinn_proto.congestion.Controller→quinn_proto.connection.streams.send.Send
- Direction
- quinn_proto.congestion uses quinn_proto.connection.streams.send, so a change to quinn_proto.connection.streams.send can break quinn_proto.congestion, while a change to quinn_proto.congestion can't break quinn_proto.connection.streams.send.
- Position
- Below the diagonal: quinn_proto.congestion uses a module listed above it, which is the healthy direction.
25→24 quinn_proto.congestion uses quinn_proto.connection.paths✕
- Connections
- 1 pair of types, where a type in quinn_proto.congestion uses a type in quinn_proto.connection.paths.
- The types involved
quinn_proto.congestion.Controller→quinn_proto.connection.paths.RttEstimator
- Direction
- quinn_proto.congestion uses quinn_proto.connection.paths, so a change to quinn_proto.connection.paths can break quinn_proto.congestion, while a change to quinn_proto.congestion can't break quinn_proto.connection.paths.
- Position
- Below the diagonal: quinn_proto.congestion uses a module listed above it, which is the healthy direction.
26→8 quinn_proto.connection.qlog uses quinn_proto.packet✕
- Connections
- 2 pairs of types, where a type in quinn_proto.connection.qlog uses a type in quinn_proto.packet.
- The types involved
quinn_proto.connection.qlog.QlogSink→quinn_proto.packet.SpaceIdquinn_proto.connection.qlog.qlog$module→quinn_proto.packet.SpaceId
- Direction
- quinn_proto.connection.qlog uses quinn_proto.packet, so a change to quinn_proto.packet can break quinn_proto.connection.qlog, while a change to quinn_proto.connection.qlog can't break quinn_proto.packet.
- Position
- Below the diagonal: quinn_proto.connection.qlog uses a module listed above it, which is the healthy direction.
26→23 quinn_proto.connection.qlog uses quinn_proto.connection.spaces✕
- Connections
- 1 pair of types, where a type in quinn_proto.connection.qlog uses a type in quinn_proto.connection.spaces.
- The types involved
quinn_proto.connection.qlog.QlogSink→quinn_proto.connection.spaces.SentPacket
- Direction
- quinn_proto.connection.qlog uses quinn_proto.connection.spaces, so a change to quinn_proto.connection.spaces can break quinn_proto.connection.qlog, while a change to quinn_proto.connection.qlog can't break quinn_proto.connection.spaces.
- Position
- Below the diagonal: quinn_proto.connection.qlog uses a module listed above it, which is the healthy direction.
26→24 quinn_proto.connection.qlog uses quinn_proto.connection.paths✕
- Connections
- 1 pair of types, where a type in quinn_proto.connection.qlog uses a type in quinn_proto.connection.paths.
- The types involved
quinn_proto.connection.qlog.QlogSink→quinn_proto.connection.paths.PathData
- Direction
- quinn_proto.connection.qlog uses quinn_proto.connection.paths, so a change to quinn_proto.connection.paths can break quinn_proto.connection.qlog, while a change to quinn_proto.connection.qlog can't break quinn_proto.connection.paths.
- Position
- Below the diagonal: quinn_proto.connection.qlog uses a module listed above it, which is the healthy direction.
26→33 quinn_proto.connection.qlog uses quinn_proto.shared part of a loop✕
- Connections
- 2 pairs of types, where a type in quinn_proto.connection.qlog uses a type in quinn_proto.shared.
- The types involved
quinn_proto.connection.qlog.QlogSink→quinn_proto.shared.ConnectionIdquinn_proto.connection.qlog.QlogStream→quinn_proto.shared.ConnectionId
- Direction
- quinn_proto.connection.qlog uses quinn_proto.shared, so a change to quinn_proto.shared can break quinn_proto.connection.qlog, while a change to quinn_proto.connection.qlog can't break quinn_proto.shared.
- 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.
27→9 quinn_proto.config.transport uses quinn_proto.varint✕
- Connections
- 3 pairs of types, where a type in quinn_proto.config.transport uses a type in quinn_proto.varint.
- The types involved
quinn_proto.config.transport.AckFrequencyConfig→quinn_proto.varint.VarIntquinn_proto.config.transport.IdleTimeout→quinn_proto.varint.VarIntquinn_proto.config.transport.TransportConfig→quinn_proto.varint.VarInt
- Direction
- quinn_proto.config.transport uses quinn_proto.varint, so a change to quinn_proto.varint can break quinn_proto.config.transport, while a change to quinn_proto.config.transport can't break quinn_proto.varint.
- Position
- Below the diagonal: quinn_proto.config.transport uses a module listed above it, which is the healthy direction.
27→26 quinn_proto.config.transport uses quinn_proto.connection.qlog✕
- Connections
- 3 pairs of types, where a type in quinn_proto.config.transport uses a type in quinn_proto.connection.qlog.
- The types involved
quinn_proto.config.transport.QlogConfig→quinn_proto.connection.qlog.QlogStreamquinn_proto.config.transport.TransportConfig→quinn_proto.connection.qlog.QlogSinkquinn_proto.config.transport.TransportConfig→quinn_proto.connection.qlog.QlogStream
- Direction
- quinn_proto.config.transport uses quinn_proto.connection.qlog, so a change to quinn_proto.connection.qlog can break quinn_proto.config.transport, while a change to quinn_proto.config.transport can't break quinn_proto.connection.qlog.
- Position
- Below the diagonal: quinn_proto.config.transport uses a module listed above it, which is the healthy direction.
28→24 quinn_proto.congestion.bbr uses quinn_proto.connection.paths✕
- Connections
- 1 pair of types, where a type in quinn_proto.congestion.bbr uses a type in quinn_proto.connection.paths.
- The types involved
quinn_proto.congestion.bbr.Bbr→quinn_proto.connection.paths.RttEstimator
- Direction
- quinn_proto.congestion.bbr uses quinn_proto.connection.paths, so a change to quinn_proto.connection.paths can break quinn_proto.congestion.bbr, while a change to quinn_proto.congestion.bbr can't break quinn_proto.connection.paths.
- Position
- Below the diagonal: quinn_proto.congestion.bbr uses a module listed above it, which is the healthy direction.
28→25 quinn_proto.congestion.bbr uses quinn_proto.congestion✕
- Connections
- 3 pairs of types, where a type in quinn_proto.congestion.bbr uses a type in quinn_proto.congestion.
- The types involved
quinn_proto.congestion.bbr.Bbr→quinn_proto.congestion.Controllerquinn_proto.congestion.bbr.Bbr→quinn_proto.congestion.ControllerMetricsquinn_proto.congestion.bbr.BbrConfig→quinn_proto.congestion.ControllerFactory
- Direction
- quinn_proto.congestion.bbr uses quinn_proto.congestion, so a change to quinn_proto.congestion can break quinn_proto.congestion.bbr, while a change to quinn_proto.congestion.bbr can't break quinn_proto.congestion.
- Position
- Below the diagonal: quinn_proto.congestion.bbr uses a module listed above it, which is the healthy direction.
29→7 quinn_proto.congestion.cubic uses quinn_proto.bloom_token_log✕
- Connections
- 1 pair of types, where a type in quinn_proto.congestion.cubic uses a type in quinn_proto.bloom_token_log.
- The types involved
quinn_proto.congestion.cubic.Cubic→quinn_proto.bloom_token_log.State
- Direction
- quinn_proto.congestion.cubic uses quinn_proto.bloom_token_log, so a change to quinn_proto.bloom_token_log can break quinn_proto.congestion.cubic, while a change to quinn_proto.congestion.cubic can't break quinn_proto.bloom_token_log.
- Position
- Below the diagonal: quinn_proto.congestion.cubic uses a module listed above it, which is the healthy direction.
29→24 quinn_proto.congestion.cubic uses quinn_proto.connection.paths✕
- Connections
- 1 pair of types, where a type in quinn_proto.congestion.cubic uses a type in quinn_proto.connection.paths.
- The types involved
quinn_proto.congestion.cubic.Cubic→quinn_proto.connection.paths.RttEstimator
- Direction
- quinn_proto.congestion.cubic uses quinn_proto.connection.paths, so a change to quinn_proto.connection.paths can break quinn_proto.congestion.cubic, while a change to quinn_proto.congestion.cubic can't break quinn_proto.connection.paths.
- Position
- Below the diagonal: quinn_proto.congestion.cubic uses a module listed above it, which is the healthy direction.
29→25 quinn_proto.congestion.cubic uses quinn_proto.congestion✕
- Connections
- 3 pairs of types, where a type in quinn_proto.congestion.cubic uses a type in quinn_proto.congestion.
- The types involved
quinn_proto.congestion.cubic.Cubic→quinn_proto.congestion.Controllerquinn_proto.congestion.cubic.Cubic→quinn_proto.congestion.ControllerMetricsquinn_proto.congestion.cubic.CubicConfig→quinn_proto.congestion.ControllerFactory
- Direction
- quinn_proto.congestion.cubic uses quinn_proto.congestion, so a change to quinn_proto.congestion can break quinn_proto.congestion.cubic, while a change to quinn_proto.congestion.cubic can't break quinn_proto.congestion.
- Position
- Below the diagonal: quinn_proto.congestion.cubic uses a module listed above it, which is the healthy direction.
30→9 quinn_proto.config uses quinn_proto.varint✕
- Connections
- 2 pairs of types, where a type in quinn_proto.config uses a type in quinn_proto.varint.
- The types involved
quinn_proto.config.ConfigError→quinn_proto.varint.VarIntBoundsExceededquinn_proto.config.EndpointConfig→quinn_proto.varint.VarInt
- Direction
- quinn_proto.config uses quinn_proto.varint, so a change to quinn_proto.varint can break quinn_proto.config, while a change to quinn_proto.config can't break quinn_proto.varint.
- Position
- Below the diagonal: quinn_proto.config uses a module listed above it, which is the healthy direction.
30→20 quinn_proto.config uses quinn_proto.connection.streams.send✕
- Connections
- 1 pair of types, where a type in quinn_proto.config uses a type in quinn_proto.connection.streams.send.
- The types involved
quinn_proto.config.TimeSource→quinn_proto.connection.streams.send.Send
- Direction
- quinn_proto.config uses quinn_proto.connection.streams.send, so a change to quinn_proto.connection.streams.send can break quinn_proto.config, while a change to quinn_proto.config can't break quinn_proto.connection.streams.send.
- Position
- Below the diagonal: quinn_proto.config uses a module listed above it, which is the healthy direction.
30→27 quinn_proto.config uses quinn_proto.config.transport✕
- Connections
- 2 pairs of types, where a type in quinn_proto.config uses a type in quinn_proto.config.transport.
- The types involved
quinn_proto.config.ClientConfig→quinn_proto.config.transport.TransportConfigquinn_proto.config.ServerConfig→quinn_proto.config.transport.TransportConfig
- Direction
- quinn_proto.config uses quinn_proto.config.transport, so a change to quinn_proto.config.transport can break quinn_proto.config, while a change to quinn_proto.config can't break quinn_proto.config.transport.
- Position
- Below the diagonal: quinn_proto.config uses a module listed above it, which is the healthy direction.
31→9 quinn_proto.connection.ack_frequency uses quinn_proto.varint✕
- Connections
- 1 pair of types, where a type in quinn_proto.connection.ack_frequency uses a type in quinn_proto.varint.
- The types involved
quinn_proto.connection.ack_frequency.AckFrequencyState→quinn_proto.varint.VarInt
- Direction
- quinn_proto.connection.ack_frequency uses quinn_proto.varint, so a change to quinn_proto.varint can break quinn_proto.connection.ack_frequency, while a change to quinn_proto.connection.ack_frequency can't break quinn_proto.varint.
- Position
- Below the diagonal: quinn_proto.connection.ack_frequency uses a module listed above it, which is the healthy direction.
31→14 quinn_proto.connection.ack_frequency uses quinn_proto.frame✕
- Connections
- 1 pair of types, where a type in quinn_proto.connection.ack_frequency uses a type in quinn_proto.frame.
- The types involved
quinn_proto.connection.ack_frequency.AckFrequencyState→quinn_proto.frame.AckFrequency
- Direction
- quinn_proto.connection.ack_frequency uses quinn_proto.frame, so a change to quinn_proto.frame can break quinn_proto.connection.ack_frequency, while a change to quinn_proto.connection.ack_frequency can't break quinn_proto.frame.
- Position
- Below the diagonal: quinn_proto.connection.ack_frequency uses a module listed above it, which is the healthy direction.
31→15 quinn_proto.connection.ack_frequency uses quinn_proto.transport_parameters✕
- Connections
- 1 pair of types, where a type in quinn_proto.connection.ack_frequency uses a type in quinn_proto.transport_parameters.
- The types involved
quinn_proto.connection.ack_frequency.AckFrequencyState→quinn_proto.transport_parameters.TransportParameters
- Direction
- quinn_proto.connection.ack_frequency uses quinn_proto.transport_parameters, so a change to quinn_proto.transport_parameters can break quinn_proto.connection.ack_frequency, while a change to quinn_proto.connection.ack_frequency can't break quinn_proto.transport_parameters.
- Position
- Below the diagonal: quinn_proto.connection.ack_frequency uses a module listed above it, which is the healthy direction.
31→23 quinn_proto.connection.ack_frequency uses quinn_proto.connection.spaces✕
- Connections
- 1 pair of types, where a type in quinn_proto.connection.ack_frequency uses a type in quinn_proto.connection.spaces.
- The types involved
quinn_proto.connection.ack_frequency.AckFrequencyState→quinn_proto.connection.spaces.PendingAcks
- Direction
- quinn_proto.connection.ack_frequency uses quinn_proto.connection.spaces, so a change to quinn_proto.connection.spaces can break quinn_proto.connection.ack_frequency, while a change to quinn_proto.connection.ack_frequency can't break quinn_proto.connection.spaces.
- Position
- Below the diagonal: quinn_proto.connection.ack_frequency uses a module listed above it, which is the healthy direction.
31→27 quinn_proto.connection.ack_frequency uses quinn_proto.config.transport✕
- Connections
- 1 pair of types, where a type in quinn_proto.connection.ack_frequency uses a type in quinn_proto.config.transport.
- The types involved
quinn_proto.connection.ack_frequency.AckFrequencyState→quinn_proto.config.transport.AckFrequencyConfig
- Direction
- quinn_proto.connection.ack_frequency uses quinn_proto.config.transport, so a change to quinn_proto.config.transport can break quinn_proto.connection.ack_frequency, while a change to quinn_proto.connection.ack_frequency can't break quinn_proto.config.transport.
- Position
- Below the diagonal: quinn_proto.connection.ack_frequency uses a module listed above it, which is the healthy direction.
32→8 quinn_proto.token uses quinn_proto.packet✕
- Connections
- 1 pair of types, where a type in quinn_proto.token uses a type in quinn_proto.packet.
- The types involved
quinn_proto.token.IncomingToken→quinn_proto.packet.InitialHeader
- Direction
- quinn_proto.token uses quinn_proto.packet, so a change to quinn_proto.packet can break quinn_proto.token, while a change to quinn_proto.token can't break quinn_proto.packet.
- Position
- Below the diagonal: quinn_proto.token uses a module listed above it, which is the healthy direction.
32→20 quinn_proto.token uses quinn_proto.connection.streams.send✕
- Connections
- 2 pairs of types, where a type in quinn_proto.token uses a type in quinn_proto.connection.streams.send.
- The types involved
quinn_proto.token.TokenLog→quinn_proto.connection.streams.send.Sendquinn_proto.token.TokenStore→quinn_proto.connection.streams.send.Send
- Direction
- quinn_proto.token uses quinn_proto.connection.streams.send, so a change to quinn_proto.connection.streams.send can break quinn_proto.token, while a change to quinn_proto.token can't break quinn_proto.connection.streams.send.
- Position
- Below the diagonal: quinn_proto.token uses a module listed above it, which is the healthy direction.
32→30 quinn_proto.token uses quinn_proto.config✕
- Connections
- 1 pair of types, where a type in quinn_proto.token uses a type in quinn_proto.config.
- The types involved
quinn_proto.token.IncomingToken→quinn_proto.config.ServerConfig
- Direction
- quinn_proto.token uses quinn_proto.config, so a change to quinn_proto.config can break quinn_proto.token, while a change to quinn_proto.token can't break quinn_proto.config.
- Position
- Below the diagonal: quinn_proto.token uses a module listed above it, which is the healthy direction.
32→33 quinn_proto.token uses quinn_proto.shared part of a loop✕
- Connections
- 2 pairs of types, where a type in quinn_proto.token uses a type in quinn_proto.shared.
- The types involved
quinn_proto.token.IncomingToken→quinn_proto.shared.ConnectionIdquinn_proto.token.ResetToken→quinn_proto.shared.ConnectionId
- Direction
- quinn_proto.token uses quinn_proto.shared, so a change to quinn_proto.shared can break quinn_proto.token, while a change to quinn_proto.token can't break quinn_proto.shared.
- 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.
33→8 quinn_proto.shared uses quinn_proto.packet✕
- Connections
- 1 pair of types, where a type in quinn_proto.shared uses a type in quinn_proto.packet.
- The types involved
quinn_proto.shared.DatagramConnectionEvent→quinn_proto.packet.PartialDecode
- Direction
- quinn_proto.shared uses quinn_proto.packet, so a change to quinn_proto.packet can break quinn_proto.shared, while a change to quinn_proto.shared can't break quinn_proto.packet.
- Position
- Below the diagonal: quinn_proto.shared uses a module listed above it, which is the healthy direction.
33→32 quinn_proto.shared uses quinn_proto.token✕
- Connections
- 1 pair of types, where a type in quinn_proto.shared uses a type in quinn_proto.token.
- The types involved
quinn_proto.shared.IssuedCid→quinn_proto.token.ResetToken
- Direction
- quinn_proto.shared uses quinn_proto.token, so a change to quinn_proto.token can break quinn_proto.shared, while a change to quinn_proto.shared can't break quinn_proto.token.
- Position
- Below the diagonal: quinn_proto.shared uses a module listed above it, which is the healthy direction.
34→2 quinn_proto uses quinn_proto.coding✕
- Connections
- 1 pair of types, where a type in quinn_proto uses a type in quinn_proto.coding.
- The types involved
quinn_proto.StreamId→quinn_proto.coding.Codec
- Direction
- quinn_proto uses quinn_proto.coding, so a change to quinn_proto.coding can break quinn_proto, while a change to quinn_proto can't break quinn_proto.coding.
- Position
- Below the diagonal: quinn_proto uses a module listed above it, which is the healthy direction.
34→9 quinn_proto uses quinn_proto.varint✕
- Connections
- 1 pair of types, where a type in quinn_proto uses a type in quinn_proto.varint.
- The types involved
quinn_proto.StreamId→quinn_proto.varint.VarInt
- Direction
- quinn_proto uses quinn_proto.varint, so a change to quinn_proto.varint can break quinn_proto, while a change to quinn_proto can't break quinn_proto.varint.
- Position
- Below the diagonal: quinn_proto uses a module listed above it, which is the healthy direction.
34→33 quinn_proto uses quinn_proto.shared✕
- Connections
- 1 pair of types, where a type in quinn_proto uses a type in quinn_proto.shared.
- The types involved
quinn_proto.Transmit→quinn_proto.shared.EcnCodepoint
- Direction
- quinn_proto uses quinn_proto.shared, so a change to quinn_proto.shared can break quinn_proto, while a change to quinn_proto can't break quinn_proto.shared.
- Position
- Below the diagonal: quinn_proto uses a module listed above it, which is the healthy direction.
35→14 quinn_proto.cid_queue uses quinn_proto.frame✕
- Connections
- 1 pair of types, where a type in quinn_proto.cid_queue uses a type in quinn_proto.frame.
- The types involved
quinn_proto.cid_queue.CidQueue→quinn_proto.frame.NewConnectionId
- Direction
- quinn_proto.cid_queue uses quinn_proto.frame, so a change to quinn_proto.frame can break quinn_proto.cid_queue, while a change to quinn_proto.cid_queue can't break quinn_proto.frame.
- Position
- Below the diagonal: quinn_proto.cid_queue uses a module listed above it, which is the healthy direction.
35→33 quinn_proto.cid_queue uses quinn_proto.shared✕
- Connections
- 1 pair of types, where a type in quinn_proto.cid_queue uses a type in quinn_proto.shared.
- The types involved
quinn_proto.cid_queue.CidQueue→quinn_proto.shared.ConnectionId
- Direction
- quinn_proto.cid_queue uses quinn_proto.shared, so a change to quinn_proto.shared can break quinn_proto.cid_queue, while a change to quinn_proto.cid_queue can't break quinn_proto.shared.
- Position
- Below the diagonal: quinn_proto.cid_queue uses a module listed above it, which is the healthy direction.
36→8 quinn_proto.connection.packet_crypto uses quinn_proto.packet✕
- Connections
- 3 pairs of types, where a type in quinn_proto.connection.packet_crypto uses a type in quinn_proto.packet.
- The types involved
quinn_proto.connection.packet_crypto.UnprotectHeaderResult→quinn_proto.packet.Packetquinn_proto.connection.packet_crypto.packet_crypto$module→quinn_proto.packet.Packetquinn_proto.connection.packet_crypto.packet_crypto$module→quinn_proto.packet.PartialDecode
- Direction
- quinn_proto.connection.packet_crypto uses quinn_proto.packet, so a change to quinn_proto.packet can break quinn_proto.connection.packet_crypto, while a change to quinn_proto.connection.packet_crypto can't break quinn_proto.packet.
- Position
- Below the diagonal: quinn_proto.connection.packet_crypto uses a module listed above it, which is the healthy direction.
36→22 quinn_proto.connection.packet_crypto uses quinn_proto.crypto✕
- Connections
- 2 pairs of types, where a type in quinn_proto.connection.packet_crypto uses a type in quinn_proto.crypto.
- The types involved
quinn_proto.connection.packet_crypto.PrevCrypto→quinn_proto.crypto.KeyPairquinn_proto.connection.packet_crypto.packet_crypto$module→quinn_proto.crypto.KeyPair
- Direction
- quinn_proto.connection.packet_crypto uses quinn_proto.crypto, so a change to quinn_proto.crypto can break quinn_proto.connection.packet_crypto, while a change to quinn_proto.connection.packet_crypto can't break quinn_proto.crypto.
- Position
- Below the diagonal: quinn_proto.connection.packet_crypto uses a module listed above it, which is the healthy direction.
36→32 quinn_proto.connection.packet_crypto uses quinn_proto.token✕
- Connections
- 1 pair of types, where a type in quinn_proto.connection.packet_crypto uses a type in quinn_proto.token.
- The types involved
quinn_proto.connection.packet_crypto.packet_crypto$module→quinn_proto.token.ResetToken
- Direction
- quinn_proto.connection.packet_crypto uses quinn_proto.token, so a change to quinn_proto.token can break quinn_proto.connection.packet_crypto, while a change to quinn_proto.connection.packet_crypto can't break quinn_proto.token.
- Position
- Below the diagonal: quinn_proto.connection.packet_crypto uses a module listed above it, which is the healthy direction.
36→34 quinn_proto.connection.packet_crypto uses quinn_proto✕
- Connections
- 1 pair of types, where a type in quinn_proto.connection.packet_crypto uses a type in quinn_proto.
- The types involved
quinn_proto.connection.packet_crypto.packet_crypto$module→quinn_proto.Side
- Direction
- quinn_proto.connection.packet_crypto uses quinn_proto, so a change to quinn_proto can break quinn_proto.connection.packet_crypto, while a change to quinn_proto.connection.packet_crypto can't break quinn_proto.
- Position
- Below the diagonal: quinn_proto.connection.packet_crypto uses a module listed above it, which is the healthy direction.
37→7 quinn_proto.connection uses quinn_proto.bloom_token_log✕
- Connections
- 1 pair of types, where a type in quinn_proto.connection uses a type in quinn_proto.bloom_token_log.
- The types involved
quinn_proto.connection.Connection→quinn_proto.bloom_token_log.State
- Direction
- quinn_proto.connection uses quinn_proto.bloom_token_log, so a change to quinn_proto.bloom_token_log can break quinn_proto.connection, while a change to quinn_proto.connection can't break quinn_proto.bloom_token_log.
- Position
- Below the diagonal: quinn_proto.connection uses a module listed above it, which is the healthy direction.
37→8 quinn_proto.connection uses quinn_proto.packet✕
- Connections
- 5 pairs of types, where a type in quinn_proto.connection uses a type in quinn_proto.packet.
- The types involved
quinn_proto.connection.Connection→quinn_proto.packet.InitialPacketquinn_proto.connection.Connection→quinn_proto.packet.Packetquinn_proto.connection.Connection→quinn_proto.packet.PartialDecodequinn_proto.connection.Connection→quinn_proto.packet.SpaceIdquinn_proto.connection.EarlyPacket→quinn_proto.packet.Packet
- Direction
- quinn_proto.connection uses quinn_proto.packet, so a change to quinn_proto.packet can break quinn_proto.connection, while a change to quinn_proto.connection can't break quinn_proto.packet.
- Position
- Below the diagonal: quinn_proto.connection uses a module listed above it, which is the healthy direction.
37→9 quinn_proto.connection uses quinn_proto.varint✕
- Connections
- 2 pairs of types, where a type in quinn_proto.connection uses a type in quinn_proto.varint.
- The types involved
quinn_proto.connection.Connection→quinn_proto.varint.VarIntquinn_proto.connection.connection$module→quinn_proto.varint.VarInt
- Direction
- quinn_proto.connection uses quinn_proto.varint, so a change to quinn_proto.varint can break quinn_proto.connection, while a change to quinn_proto.connection can't break quinn_proto.varint.
- Position
- Below the diagonal: quinn_proto.connection uses a module listed above it, which is the healthy direction.
37→13 quinn_proto.connection uses quinn_proto.connection.streams✕
- Connections
- 3 pairs of types, where a type in quinn_proto.connection uses a type in quinn_proto.connection.streams.
- The types involved
quinn_proto.connection.Connection→quinn_proto.connection.streams.RecvStreamquinn_proto.connection.Connection→quinn_proto.connection.streams.SendStreamquinn_proto.connection.Connection→quinn_proto.connection.streams.Streams
- Direction
- quinn_proto.connection uses quinn_proto.connection.streams, so a change to quinn_proto.connection.streams can break quinn_proto.connection, while a change to quinn_proto.connection can't break quinn_proto.connection.streams.
- Position
- Below the diagonal: quinn_proto.connection uses a module listed above it, which is the healthy direction.
37→14 quinn_proto.connection uses quinn_proto.frame✕
- Connections
- 5 pairs of types, where a type in quinn_proto.connection uses a type in quinn_proto.frame.
- The types involved
quinn_proto.connection.Connection→quinn_proto.frame.Ackquinn_proto.connection.Connection→quinn_proto.frame.Closequinn_proto.connection.Connection→quinn_proto.frame.Cryptoquinn_proto.connection.Connection→quinn_proto.frame.EcnCountsquinn_proto.connection.ConnectionError→quinn_proto.frame.Close
- Direction
- quinn_proto.connection uses quinn_proto.frame, so a change to quinn_proto.frame can break quinn_proto.connection, while a change to quinn_proto.connection can't break quinn_proto.frame.
- Position
- Below the diagonal: quinn_proto.connection uses a module listed above it, which is the healthy direction.
37→15 quinn_proto.connection uses quinn_proto.transport_parameters✕
- Connections
- 2 pairs of types, where a type in quinn_proto.connection uses a type in quinn_proto.transport_parameters.
- The types involved
quinn_proto.connection.Connection→quinn_proto.transport_parameters.TransportParametersquinn_proto.connection.connection$module→quinn_proto.transport_parameters.TransportParameters
- Direction
- quinn_proto.connection uses quinn_proto.transport_parameters, so a change to quinn_proto.transport_parameters can break quinn_proto.connection, while a change to quinn_proto.connection can't break quinn_proto.transport_parameters.
- Position
- Below the diagonal: quinn_proto.connection uses a module listed above it, which is the healthy direction.
37→18 quinn_proto.connection uses quinn_proto.connection.datagrams✕
- Connections
- 2 pairs of types, where a type in quinn_proto.connection uses a type in quinn_proto.connection.datagrams.
- The types involved
quinn_proto.connection.Connection→quinn_proto.connection.datagrams.DatagramStatequinn_proto.connection.Connection→quinn_proto.connection.datagrams.Datagrams
- Direction
- quinn_proto.connection uses quinn_proto.connection.datagrams, so a change to quinn_proto.connection.datagrams can break quinn_proto.connection, while a change to quinn_proto.connection can't break quinn_proto.connection.datagrams.
- Position
- Below the diagonal: quinn_proto.connection uses a module listed above it, which is the healthy direction.
37→21 quinn_proto.connection uses quinn_proto.connection.streams.state✕
- Connections
- 2 pairs of types, where a type in quinn_proto.connection uses a type in quinn_proto.connection.streams.state.
- The types involved
quinn_proto.connection.Connection→quinn_proto.connection.streams.state.StreamsStatequinn_proto.connection.SentFrames→quinn_proto.connection.streams.state.StreamsState
- Direction
- quinn_proto.connection uses quinn_proto.connection.streams.state, so a change to quinn_proto.connection.streams.state can break quinn_proto.connection, while a change to quinn_proto.connection can't break quinn_proto.connection.streams.state.
- Position
- Below the diagonal: quinn_proto.connection uses a module listed above it, which is the healthy direction.
37→22 quinn_proto.connection uses quinn_proto.crypto✕
- Connections
- 2 pairs of types, where a type in quinn_proto.connection uses a type in quinn_proto.crypto.
- The types involved
quinn_proto.connection.Connection→quinn_proto.crypto.KeyPairquinn_proto.connection.Connection→quinn_proto.crypto.Keys
- Direction
- quinn_proto.connection uses quinn_proto.crypto, so a change to quinn_proto.crypto can break quinn_proto.connection, while a change to quinn_proto.connection can't break quinn_proto.crypto.
- Position
- Below the diagonal: quinn_proto.connection uses a module listed above it, which is the healthy direction.
37→23 quinn_proto.connection uses quinn_proto.connection.spaces✕
- Connections
- 5 pairs of types, where a type in quinn_proto.connection uses a type in quinn_proto.connection.spaces.
- The types involved
quinn_proto.connection.Connection→quinn_proto.connection.spaces.PacketNumberFilterquinn_proto.connection.Connection→quinn_proto.connection.spaces.PacketSpacequinn_proto.connection.Connection→quinn_proto.connection.spaces.SendableFramesquinn_proto.connection.Connection→quinn_proto.connection.spaces.SentPacketquinn_proto.connection.SentFrames→quinn_proto.connection.spaces.ThinRetransmits
- Direction
- quinn_proto.connection uses quinn_proto.connection.spaces, so a change to quinn_proto.connection.spaces can break quinn_proto.connection, while a change to quinn_proto.connection can't break quinn_proto.connection.spaces.
- Position
- Below the diagonal: quinn_proto.connection uses a module listed above it, which is the healthy direction.
37→24 quinn_proto.connection uses quinn_proto.connection.paths✕
- Connections
- 2 pairs of types, where a type in quinn_proto.connection uses a type in quinn_proto.connection.paths.
- The types involved
quinn_proto.connection.Connection→quinn_proto.connection.paths.PathDataquinn_proto.connection.Connection→quinn_proto.connection.paths.PathResponses
- Direction
- quinn_proto.connection uses quinn_proto.connection.paths, so a change to quinn_proto.connection.paths can break quinn_proto.connection, while a change to quinn_proto.connection can't break quinn_proto.connection.paths.
- Position
- Below the diagonal: quinn_proto.connection uses a module listed above it, which is the healthy direction.
37→27 quinn_proto.connection uses quinn_proto.config.transport✕
- Connections
- 2 pairs of types, where a type in quinn_proto.connection uses a type in quinn_proto.config.transport.
- The types involved
quinn_proto.connection.Connection→quinn_proto.config.transport.TransportConfigquinn_proto.connection.ConnectionArgs→quinn_proto.config.transport.TransportConfig
- Direction
- quinn_proto.connection uses quinn_proto.config.transport, so a change to quinn_proto.config.transport can break quinn_proto.connection, while a change to quinn_proto.connection can't break quinn_proto.config.transport.
- Position
- Below the diagonal: quinn_proto.connection uses a module listed above it, which is the healthy direction.
37→30 quinn_proto.connection uses quinn_proto.config✕
- Connections
- 2 pairs of types, where a type in quinn_proto.connection uses a type in quinn_proto.config.
- The types involved
quinn_proto.connection.Connection→quinn_proto.config.EndpointConfigquinn_proto.connection.ConnectionArgs→quinn_proto.config.EndpointConfig
- Direction
- quinn_proto.connection uses quinn_proto.config, so a change to quinn_proto.config can break quinn_proto.connection, while a change to quinn_proto.connection can't break quinn_proto.config.
- Position
- Below the diagonal: quinn_proto.connection uses a module listed above it, which is the healthy direction.
37→31 quinn_proto.connection uses quinn_proto.connection.ack_frequency✕
- Connections
- 1 pair of types, where a type in quinn_proto.connection uses a type in quinn_proto.connection.ack_frequency.
- The types involved
quinn_proto.connection.Connection→quinn_proto.connection.ack_frequency.AckFrequencyState
- Direction
- quinn_proto.connection uses quinn_proto.connection.ack_frequency, so a change to quinn_proto.connection.ack_frequency can break quinn_proto.connection, while a change to quinn_proto.connection can't break quinn_proto.connection.ack_frequency.
- Position
- Below the diagonal: quinn_proto.connection uses a module listed above it, which is the healthy direction.
37→32 quinn_proto.connection uses quinn_proto.token✕
- Connections
- 1 pair of types, where a type in quinn_proto.connection uses a type in quinn_proto.token.
- The types involved
quinn_proto.connection.Connection→quinn_proto.token.ResetToken
- Direction
- quinn_proto.connection uses quinn_proto.token, so a change to quinn_proto.token can break quinn_proto.connection, while a change to quinn_proto.connection can't break quinn_proto.token.
- Position
- Below the diagonal: quinn_proto.connection uses a module listed above it, which is the healthy direction.
37→33 quinn_proto.connection uses quinn_proto.shared✕
- Connections
- 7 pairs of types, where a type in quinn_proto.connection uses a type in quinn_proto.shared.
- The types involved
quinn_proto.connection.Connection→quinn_proto.shared.ConnectionEventquinn_proto.connection.Connection→quinn_proto.shared.ConnectionIdquinn_proto.connection.Connection→quinn_proto.shared.EcnCodepointquinn_proto.connection.Connection→quinn_proto.shared.EndpointEventquinn_proto.connection.ConnectionArgs→quinn_proto.shared.ConnectionIdquinn_proto.connection.EarlyPacket→quinn_proto.shared.EcnCodepointquinn_proto.connection.SideArgs→quinn_proto.shared.ConnectionId
- Direction
- quinn_proto.connection uses quinn_proto.shared, so a change to quinn_proto.shared can break quinn_proto.connection, while a change to quinn_proto.connection can't break quinn_proto.shared.
- Position
- Below the diagonal: quinn_proto.connection uses a module listed above it, which is the healthy direction.
37→34 quinn_proto.connection uses quinn_proto✕
- Connections
- 6 pairs of types, where a type in quinn_proto.connection uses a type in quinn_proto.
- The types involved
quinn_proto.connection.Connection→quinn_proto.Dirquinn_proto.connection.Connection→quinn_proto.Sidequinn_proto.connection.Connection→quinn_proto.StreamIdquinn_proto.connection.Connection→quinn_proto.Transmitquinn_proto.connection.ConnectionSide→quinn_proto.Sidequinn_proto.connection.SideArgs→quinn_proto.Side
- Direction
- quinn_proto.connection uses quinn_proto, so a change to quinn_proto can break quinn_proto.connection, while a change to quinn_proto.connection can't break quinn_proto.
- Position
- Below the diagonal: quinn_proto.connection uses a module listed above it, which is the healthy direction.
37→35 quinn_proto.connection uses quinn_proto.cid_queue✕
- Connections
- 1 pair of types, where a type in quinn_proto.connection uses a type in quinn_proto.cid_queue.
- The types involved
quinn_proto.connection.Connection→quinn_proto.cid_queue.CidQueue
- Direction
- quinn_proto.connection uses quinn_proto.cid_queue, so a change to quinn_proto.cid_queue can break quinn_proto.connection, while a change to quinn_proto.connection can't break quinn_proto.cid_queue.
- Position
- Below the diagonal: quinn_proto.connection uses a module listed above it, which is the healthy direction.
37→36 quinn_proto.connection uses quinn_proto.connection.packet_crypto✕
- Connections
- 2 pairs of types, where a type in quinn_proto.connection uses a type in quinn_proto.connection.packet_crypto.
- The types involved
quinn_proto.connection.Connection→quinn_proto.connection.packet_crypto.PrevCryptoquinn_proto.connection.Connection→quinn_proto.connection.packet_crypto.ZeroRttCrypto
- Direction
- quinn_proto.connection uses quinn_proto.connection.packet_crypto, so a change to quinn_proto.connection.packet_crypto can break quinn_proto.connection, while a change to quinn_proto.connection can't break quinn_proto.connection.packet_crypto.
- Position
- Below the diagonal: quinn_proto.connection uses a module listed above it, which is the healthy direction.
38→8 quinn_proto.endpoint uses quinn_proto.packet✕
- Connections
- 4 pairs of types, where a type in quinn_proto.endpoint uses a type in quinn_proto.packet.
- The types involved
quinn_proto.endpoint.Accepting→quinn_proto.packet.InitialPacketquinn_proto.endpoint.ConnectionIndex→quinn_proto.packet.PartialDecodequinn_proto.endpoint.Endpoint→quinn_proto.packet.ProtectedInitialHeaderquinn_proto.endpoint.Incoming→quinn_proto.packet.InitialPacket
- Direction
- quinn_proto.endpoint uses quinn_proto.packet, so a change to quinn_proto.packet can break quinn_proto.endpoint, while a change to quinn_proto.endpoint can't break quinn_proto.packet.
- Position
- Below the diagonal: quinn_proto.endpoint uses a module listed above it, which is the healthy direction.
38→15 quinn_proto.endpoint uses quinn_proto.transport_parameters✕
- Connections
- 1 pair of types, where a type in quinn_proto.endpoint uses a type in quinn_proto.transport_parameters.
- The types involved
quinn_proto.endpoint.Accepting→quinn_proto.transport_parameters.TransportParameters
- Direction
- quinn_proto.endpoint uses quinn_proto.transport_parameters, so a change to quinn_proto.transport_parameters can break quinn_proto.endpoint, while a change to quinn_proto.endpoint can't break quinn_proto.transport_parameters.
- Position
- Below the diagonal: quinn_proto.endpoint uses a module listed above it, which is the healthy direction.
38→22 quinn_proto.endpoint uses quinn_proto.crypto✕
- Connections
- 5 pairs of types, where a type in quinn_proto.endpoint uses a type in quinn_proto.crypto.
- The types involved
quinn_proto.endpoint.Accepted→quinn_proto.crypto.Keysquinn_proto.endpoint.Accepting→quinn_proto.crypto.Keysquinn_proto.endpoint.ConnectError→quinn_proto.crypto.UnsupportedVersionquinn_proto.endpoint.Endpoint→quinn_proto.crypto.Keysquinn_proto.endpoint.Incoming→quinn_proto.crypto.Keys
- Direction
- quinn_proto.endpoint uses quinn_proto.crypto, so a change to quinn_proto.crypto can break quinn_proto.endpoint, while a change to quinn_proto.endpoint can't break quinn_proto.crypto.
- Position
- Below the diagonal: quinn_proto.endpoint uses a module listed above it, which is the healthy direction.
38→27 quinn_proto.endpoint uses quinn_proto.config.transport✕
- Connections
- 1 pair of types, where a type in quinn_proto.endpoint uses a type in quinn_proto.config.transport.
- The types involved
quinn_proto.endpoint.Endpoint→quinn_proto.config.transport.TransportConfig
- Direction
- quinn_proto.endpoint uses quinn_proto.config.transport, so a change to quinn_proto.config.transport can break quinn_proto.endpoint, while a change to quinn_proto.endpoint can't break quinn_proto.config.transport.
- Position
- Below the diagonal: quinn_proto.endpoint uses a module listed above it, which is the healthy direction.
38→30 quinn_proto.endpoint uses quinn_proto.config✕
- Connections
- 4 pairs of types, where a type in quinn_proto.endpoint uses a type in quinn_proto.config.
- The types involved
quinn_proto.endpoint.Endpoint→quinn_proto.config.ClientConfigquinn_proto.endpoint.Endpoint→quinn_proto.config.EndpointConfigquinn_proto.endpoint.Endpoint→quinn_proto.config.ServerConfigquinn_proto.endpoint.IncomingBuffer→quinn_proto.config.ServerConfig
- Direction
- quinn_proto.endpoint uses quinn_proto.config, so a change to quinn_proto.config can break quinn_proto.endpoint, while a change to quinn_proto.endpoint can't break quinn_proto.config.
- Position
- Below the diagonal: quinn_proto.endpoint uses a module listed above it, which is the healthy direction.
38→32 quinn_proto.endpoint uses quinn_proto.token✕
- Connections
- 2 pairs of types, where a type in quinn_proto.endpoint uses a type in quinn_proto.token.
- The types involved
quinn_proto.endpoint.Incoming→quinn_proto.token.IncomingTokenquinn_proto.endpoint.ResetTokenTable→quinn_proto.token.ResetToken
- Direction
- quinn_proto.endpoint uses quinn_proto.token, so a change to quinn_proto.token can break quinn_proto.endpoint, while a change to quinn_proto.endpoint can't break quinn_proto.token.
- Position
- Below the diagonal: quinn_proto.endpoint uses a module listed above it, which is the healthy direction.
38→33 quinn_proto.endpoint uses quinn_proto.shared✕
- Connections
- 12 pairs of types, where a type in quinn_proto.endpoint uses a type in quinn_proto.shared.
- The types involved
quinn_proto.endpoint.Accepted→quinn_proto.shared.ConnectionIdquinn_proto.endpoint.Accepting→quinn_proto.shared.EcnCodepointquinn_proto.endpoint.ConnectionIndex→quinn_proto.shared.ConnectionIdquinn_proto.endpoint.ConnectionMeta→quinn_proto.shared.ConnectionIdquinn_proto.endpoint.Endpoint→quinn_proto.shared.ConnectionEventquinn_proto.endpoint.Endpoint→quinn_proto.shared.ConnectionIdquinn_proto.endpoint.Endpoint→quinn_proto.shared.DatagramConnectionEventquinn_proto.endpoint.Endpoint→quinn_proto.shared.EcnCodepointquinn_proto.endpoint.Endpoint→quinn_proto.shared.EndpointEventquinn_proto.endpoint.Incoming→quinn_proto.shared.ConnectionIdquinn_proto.endpoint.Incoming→quinn_proto.shared.EcnCodepointquinn_proto.endpoint.IncomingBuffer→quinn_proto.shared.DatagramConnectionEvent
- Direction
- quinn_proto.endpoint uses quinn_proto.shared, so a change to quinn_proto.shared can break quinn_proto.endpoint, while a change to quinn_proto.endpoint can't break quinn_proto.shared.
- Position
- Below the diagonal: quinn_proto.endpoint uses a module listed above it, which is the healthy direction.
38→34 quinn_proto.endpoint uses quinn_proto✕
- Connections
- 4 pairs of types, where a type in quinn_proto.endpoint uses a type in quinn_proto.
- The types involved
quinn_proto.endpoint.AcceptError→quinn_proto.Transmitquinn_proto.endpoint.ConnectionMeta→quinn_proto.Sidequinn_proto.endpoint.Endpoint→quinn_proto.Sidequinn_proto.endpoint.Endpoint→quinn_proto.Transmit
- Direction
- quinn_proto.endpoint uses quinn_proto, so a change to quinn_proto can break quinn_proto.endpoint, while a change to quinn_proto.endpoint can't break quinn_proto.
- Position
- Below the diagonal: quinn_proto.endpoint uses a module listed above it, which is the healthy direction.
38→37 quinn_proto.endpoint uses quinn_proto.connection✕
- Connections
- 4 pairs of types, where a type in quinn_proto.endpoint uses a type in quinn_proto.connection.
- The types involved
quinn_proto.endpoint.AcceptError→quinn_proto.connection.ConnectionErrorquinn_proto.endpoint.Accepting→quinn_proto.connection.ConnectionArgsquinn_proto.endpoint.Endpoint→quinn_proto.connection.Connectionquinn_proto.endpoint.Endpoint→quinn_proto.connection.SideArgs
- Direction
- quinn_proto.endpoint uses quinn_proto.connection, so a change to quinn_proto.connection can break quinn_proto.endpoint, while a change to quinn_proto.endpoint can't break quinn_proto.connection.
- Position
- Below the diagonal: quinn_proto.endpoint uses a module listed above it, which is the healthy direction.
39→2 quinn_proto.transport_error uses quinn_proto.coding✕
- Connections
- 1 pair of types, where a type in quinn_proto.transport_error uses a type in quinn_proto.coding.
- The types involved
quinn_proto.transport_error.Code→quinn_proto.coding.Codec
- Direction
- quinn_proto.transport_error uses quinn_proto.coding, so a change to quinn_proto.coding can break quinn_proto.transport_error, while a change to quinn_proto.transport_error can't break quinn_proto.coding.
- Position
- Below the diagonal: quinn_proto.transport_error uses a module listed above it, which is the healthy direction.
39→13 quinn_proto.transport_error uses quinn_proto.connection.streams✕
- Connections
- 1 pair of types, where a type in quinn_proto.transport_error uses a type in quinn_proto.connection.streams.
- The types involved
quinn_proto.transport_error.Error→quinn_proto.connection.streams.ClosedStream
- Direction
- quinn_proto.transport_error uses quinn_proto.connection.streams, so a change to quinn_proto.connection.streams can break quinn_proto.transport_error, while a change to quinn_proto.transport_error can't break quinn_proto.connection.streams.
- Position
- Below the diagonal: quinn_proto.transport_error uses a module listed above it, which is the healthy direction.
39→14 quinn_proto.transport_error uses quinn_proto.frame✕
- Connections
- 1 pair of types, where a type in quinn_proto.transport_error uses a type in quinn_proto.frame.
- The types involved
quinn_proto.transport_error.Error→quinn_proto.frame.FrameType
- Direction
- quinn_proto.transport_error uses quinn_proto.frame, so a change to quinn_proto.frame can break quinn_proto.transport_error, while a change to quinn_proto.transport_error can't break quinn_proto.frame.
- Position
- Below the diagonal: quinn_proto.transport_error uses a module listed above it, which is the healthy direction.
39→19 quinn_proto.transport_error uses quinn_proto.connection.streams.recv✕
- Connections
- 1 pair of types, where a type in quinn_proto.transport_error uses a type in quinn_proto.connection.streams.recv.
- The types involved
quinn_proto.transport_error.Error→quinn_proto.connection.streams.recv.ReadError
- Direction
- quinn_proto.transport_error uses quinn_proto.connection.streams.recv, so a change to quinn_proto.connection.streams.recv can break quinn_proto.transport_error, while a change to quinn_proto.transport_error can't break quinn_proto.connection.streams.recv.
- Position
- Below the diagonal: quinn_proto.transport_error uses a module listed above it, which is the healthy direction.
39→20 quinn_proto.transport_error uses quinn_proto.connection.streams.send✕
- Connections
- 1 pair of types, where a type in quinn_proto.transport_error uses a type in quinn_proto.connection.streams.send.
- The types involved
quinn_proto.transport_error.Error→quinn_proto.connection.streams.send.WriteError
- Direction
- quinn_proto.transport_error uses quinn_proto.connection.streams.send, so a change to quinn_proto.connection.streams.send can break quinn_proto.transport_error, while a change to quinn_proto.transport_error can't break quinn_proto.connection.streams.send.
- Position
- Below the diagonal: quinn_proto.transport_error uses a module listed above it, which is the healthy direction.
39→37 quinn_proto.transport_error uses quinn_proto.connection✕
- Connections
- 1 pair of types, where a type in quinn_proto.transport_error uses a type in quinn_proto.connection.
- The types involved
quinn_proto.transport_error.Error→quinn_proto.connection.ConnectionError
- Direction
- quinn_proto.transport_error uses quinn_proto.connection, so a change to quinn_proto.connection can break quinn_proto.transport_error, while a change to quinn_proto.transport_error can't break quinn_proto.connection.
- Position
- Below the diagonal: quinn_proto.transport_error uses a module listed above it, which is the healthy direction.
40→15 quinn_proto.crypto.rustls uses quinn_proto.transport_parameters✕
- Connections
- 3 pairs of types, where a type in quinn_proto.crypto.rustls uses a type in quinn_proto.transport_parameters.
- The types involved
quinn_proto.crypto.rustls.QuicClientConfig→quinn_proto.transport_parameters.TransportParametersquinn_proto.crypto.rustls.QuicServerConfig→quinn_proto.transport_parameters.TransportParametersquinn_proto.crypto.rustls.rustls$module→quinn_proto.transport_parameters.TransportParameters
- Direction
- quinn_proto.crypto.rustls uses quinn_proto.transport_parameters, so a change to quinn_proto.transport_parameters can break quinn_proto.crypto.rustls, while a change to quinn_proto.crypto.rustls can't break quinn_proto.transport_parameters.
- Position
- Below the diagonal: quinn_proto.crypto.rustls uses a module listed above it, which is the healthy direction.
40→22 quinn_proto.crypto.rustls uses quinn_proto.crypto✕
- Connections
- 4 pairs of types, where a type in quinn_proto.crypto.rustls uses a type in quinn_proto.crypto.
- The types involved
quinn_proto.crypto.rustls.TlsSession→quinn_proto.crypto.KeyPairquinn_proto.crypto.rustls.TlsSession→quinn_proto.crypto.Keysquinn_proto.crypto.rustls.TlsSession→quinn_proto.crypto.Sessionquinn_proto.crypto.rustls.rustls$module→quinn_proto.crypto.Keys
- Direction
- quinn_proto.crypto.rustls uses quinn_proto.crypto, so a change to quinn_proto.crypto can break quinn_proto.crypto.rustls, while a change to quinn_proto.crypto.rustls can't break quinn_proto.crypto.
- Position
- Below the diagonal: quinn_proto.crypto.rustls uses a module listed above it, which is the healthy direction.
40→30 quinn_proto.crypto.rustls uses quinn_proto.config✕
- Connections
- 2 pairs of types, where a type in quinn_proto.crypto.rustls uses a type in quinn_proto.config.
- The types involved
quinn_proto.crypto.rustls.QuicClientConfig→quinn_proto.config.ClientConfigquinn_proto.crypto.rustls.QuicServerConfig→quinn_proto.config.ServerConfig
- Direction
- quinn_proto.crypto.rustls uses quinn_proto.config, so a change to quinn_proto.config can break quinn_proto.crypto.rustls, while a change to quinn_proto.crypto.rustls can't break quinn_proto.config.
- Position
- Below the diagonal: quinn_proto.crypto.rustls uses a module listed above it, which is the healthy direction.
40→33 quinn_proto.crypto.rustls uses quinn_proto.shared✕
- Connections
- 3 pairs of types, where a type in quinn_proto.crypto.rustls uses a type in quinn_proto.shared.
- The types involved
quinn_proto.crypto.rustls.QuicServerConfig→quinn_proto.shared.ConnectionIdquinn_proto.crypto.rustls.TlsSession→quinn_proto.shared.ConnectionIdquinn_proto.crypto.rustls.rustls$module→quinn_proto.shared.ConnectionId
- Direction
- quinn_proto.crypto.rustls uses quinn_proto.shared, so a change to quinn_proto.shared can break quinn_proto.crypto.rustls, while a change to quinn_proto.crypto.rustls can't break quinn_proto.shared.
- Position
- Below the diagonal: quinn_proto.crypto.rustls uses a module listed above it, which is the healthy direction.
40→34 quinn_proto.crypto.rustls uses quinn_proto✕
- Connections
- 2 pairs of types, where a type in quinn_proto.crypto.rustls uses a type in quinn_proto.
- The types involved
quinn_proto.crypto.rustls.TlsSession→quinn_proto.Sidequinn_proto.crypto.rustls.rustls$module→quinn_proto.Side
- Direction
- quinn_proto.crypto.rustls uses quinn_proto, so a change to quinn_proto can break quinn_proto.crypto.rustls, while a change to quinn_proto.crypto.rustls can't break quinn_proto.
- Position
- Below the diagonal: quinn_proto.crypto.rustls uses a module listed above it, which is the healthy direction.
40→37 quinn_proto.crypto.rustls uses quinn_proto.connection✕
- Connections
- 1 pair of types, where a type in quinn_proto.crypto.rustls uses a type in quinn_proto.connection.
- The types involved
quinn_proto.crypto.rustls.TlsSession→quinn_proto.connection.Connection
- Direction
- quinn_proto.crypto.rustls uses quinn_proto.connection, so a change to quinn_proto.connection can break quinn_proto.crypto.rustls, while a change to quinn_proto.crypto.rustls can't break quinn_proto.connection.
- Position
- Below the diagonal: quinn_proto.crypto.rustls uses a module listed above it, which is the healthy direction.
40→39 quinn_proto.crypto.rustls uses quinn_proto.transport_error✕
- Connections
- 1 pair of types, where a type in quinn_proto.crypto.rustls uses a type in quinn_proto.transport_error.
- The types involved
quinn_proto.crypto.rustls.NoInitialCipherSuite→quinn_proto.transport_error.Error
- Direction
- quinn_proto.crypto.rustls uses quinn_proto.transport_error, so a change to quinn_proto.transport_error can break quinn_proto.crypto.rustls, while a change to quinn_proto.crypto.rustls can't break quinn_proto.transport_error.
- Position
- Below the diagonal: quinn_proto.crypto.rustls 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 | 54 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 8 | Medium |
| A07:2025 — Authentication Failures | 2 | High / Critical |
Roadmap
Top priorities: Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Cargo.toml; 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; Stop accepting every TLS certificate: delete `danger_accept_invalid_certs(true)` / `SslVerifyMode::NONE` / the rustls verifier that returns `ServerCertVerified::assertion()` unconditionally, and trust a self-signed or private server by adding its CA as a root (`add_root_certificate`, a rustls `RootCertStore`) — never by switching verification off.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Cargo.toml. | +8.2 pts | Low | ADR Quality |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +7.7 pts | Medium | Architecture documentation |
| Stop accepting every TLS certificate: delete `danger_accept_invalid_certs(true)` / `SslVerifyMode::NONE` / the rustls verifier that returns `ServerCertVerified::assertion()` unconditionally, and trust a self-signed or private server by adding its CA as a root (`add_root_certificate`, a rustls `RootCertStore`) — never by switching verification off. | +3.8 pts | Medium | Web-Security Posture |
| Resolve the 3 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. | +1.8 pts | Low | Supply-chain Provenance & Signing |
| 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. | +3.6 pts | Medium | Documentation (README) |
| Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. | +0.9 pts | Low | Static Analysis (SAST) |
| Resolve the 5 Hotspot finding(s) in Churn × Complexity Hotspots — start with mod.rs, state.rs, endpoint.rs. | +1.7 pts | High | Churn × Complexity Hotspots |
| Resolve the 1 REDACTED finding(s) in Secrets (history) — start with REDACTED. | +0.8 pts | Low | Secrets (history) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 1.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.5 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| quinn-proto/src/congestion/bbr/mod.rs | 5.5 | Mixed | God Classes: TooManyFields: Bbr |
| quinn-udp/src/unix.rs | 5.6 | Mixed | Cognitive Complexity: quinn_udp::unix::send (cognitive 19) |
| perf/src/client.rs | 5.9 | Mixed | Code Duplication: Edited copy of a member (22 corresponding lines) |
| quinn-proto/src/connection/mod.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| quinn/src/connection.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| quinn/src/endpoint.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| perf/src/stats.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| bench/src/lib.rs | 6.3 | Mixed | Code Duplication: Edited copy of a member (28 corresponding lines) |
| quinn-proto/src/packet.rs | 6.7 | Mixed | Explicit Debt: TodoComment |
| quinn-proto/src/connection/send_buffer.rs | 6.7 | Mixed | Explicit Debt: TodoComment |
| perf/src/server.rs | 7.0 | Near-clean | Code Duplication: Edited copy of a member (10 corresponding lines) |
| bench/src/stats.rs | 7.0 | Near-clean | Code Duplication: Duplicated block (9 lines × 2) |
| quinn-proto/src/connection/streams/state.rs | 7.0 | Near-clean | Cyclomatic Complexity: StreamsState::write_control_frames (cyclomatic 30) |
| quinn-proto/src/frame.rs | 7.1 | Near-clean | Cyclomatic Complexity: Iter::try_next (cyclomatic 37) |
| quinn-udp/src/apple_fast.rs | 7.1 | Near-clean | Code Duplication: Edited copy of a member (25 corresponding lines) |
| quinn-proto/src/endpoint.rs | 7.1 | Near-clean | Cyclomatic Complexity: Endpoint::handle (cyclomatic 16) |
| quinn-proto/src/transport_parameters.rs | 7.2 | Near-clean | Cyclomatic Complexity: TransportParameters::read (cyclomatic 28) |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 45 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 1.0, the weighted average across measured dimensions.
What we checked — 45 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, 231 of 250 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22'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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D27 Navigability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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.
- AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby 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.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X25 Inert configuration knob — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and 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 — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 23 further occurrence(s) are not listed individually; the score already reflects all 63.
- X5 Nullable reference types — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax and 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
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- 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.
- 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
15 function(s) exceeded the cyclomatic complexity threshold of 15; the worst was Connection::poll_transmit at 71. A further 7 function(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being FrameType::fmt at 28 — they are counted neither in the figure above nor in this dimension's score. 2 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold functions was excluded, so the exclusion is disclosed nowhere in the file itself: quinn-proto/src/connection/stats.rs (FrameStats::record at 25), quinn-proto/src/transport_error.rs (Code::fmt at 20). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 15 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with Connection::poll_transmit (cyclomatic 71), Connection::process_payload (cyclomatic 63), Iter::try_next (cyclomatic 37). — 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 15 together lifts Cyclomatic Complexity from 7.2 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
19 function(s) exceeded the cognitive complexity threshold of 15; the worst was Connection::poll_transmit at 152.
What to do
- Bring the 3 bodies over 60 down to 60 or less in Cognitive Complexity — start with Connection::poll_transmit (cognitive 152), Connection::process_payload (cognitive 92), Connection::process_decrypted_packet (cognitive 63). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 3 together lifts Cognitive Complexity from 6.1 to about 7.0/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
D3 · God Classes
26 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 9 MethodTooLong finding(s) in God Classes — start with mod.rs (5), endpoint.rs, frame.rs. — One of this dimension's main actionable groups (9 warning-level).
- Resolve the 8 FileTooLong finding(s) in God Classes — start with endpoint.rs (2), mod.rs, connection.rs. — One of this dimension's main actionable groups (8 warning-level).
- Resolve the 3 ClassTooLong finding(s) in God Classes — start with mod.rs, endpoint.rs, state.rs. — One of this dimension's main actionable groups (3 warning-level).
D4 · Code Duplication
17 duplicated block group(s) detected. 2.1 % of the production lines (752 of 36,215) are in a reported copy. A further 17 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 8 of the 34 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 2 Edited copy of a member (10 corresponding lines) finding(s) in Code Duplication — start with smol.rs, server.rs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Edited copy of a member (9 corresponding lines) finding(s) in Code Duplication — start with apple_fast.rs, recv_stream.rs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Duplicated block (12 lines × 2) finding(s) in Code Duplication — start with endpoint.rs, state.rs. — One of this dimension's main actionable groups (2 warning-level).
D5 · Coupling
4 production modules (Cargo), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 2 module(s) off the main sequence.
What to do
- Resolve the 2 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (2 warning-level).
D6 · Cohesion (LCOM4)
2 of 125 classes have LCOM4 above 3.
What to do
- Resolve the 2 Low cohesion finding(s) in Cohesion (LCOM4) — start with unix.rs, mod.rs. — One of this dimension's main actionable groups (2 warning-level).
D8 · Code Coverage
Line coverage 79.4% — 10 file(s) below 50%. Measured from the Rust suite (repository root: `cargo test --workspace` instrumented over 77 production file(s), 12 test binaries and 1 doc-test binaries).
What to do
- Resolve the 10 Low coverage finding(s) in Code Coverage — start with lib.rs (2), stats.rs (2), client.rs. — One of this dimension's main actionable groups (10 warning-level).
D11 · Test Reliability
0 flaky across 1 measured tier(s). Rust (repository root, 42 test files): measured (0 flaky).
D12 · Dependency Hygiene
3 outdated, 0 yanked direct Cargo dependencies. Only DIRECT edges are graded: a transitive crate cannot be moved past what its parent's requirement admits, so reporting one would be advice its owner cannot take. A newer release is reported only where this repository's OWN requirement already admits it, so the remedy is `cargo update` and never a manifest edit — which means a release outside the declared range is deliberately NOT charged, because a written-down constraint is a decision rather than a defect. Note that a bare requirement is a CARET, and for a 0.x crate its ceiling is the minor. Whether any crate is UNMAINTAINED is not graded — crates.io publishes no maintenance status, and release age does not stand in for one. Known CVEs in this dependency graph are D30's question, read from REDACTED there.
D13 · REDACTED Scanning
REDACTED scan ran and found no leaked secrets.
D14 · License Compliance
0 of 270 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. This repository publishes itself under MIT OR Apache-2.0, which is its own choice and is not judged here.
D15 · Churn × Complexity Hotspots
Top hotspots: quinn-proto/src/connection/mod.rs (27×71=1917); quinn-proto/src/connection/streams/state.rs (14×30=420); quinn-proto/src/endpoint.rs (20×16=320) Repeated repair below the complexity floor: quinn-udp/src/windows.rs (4 of 6 changes were fixes)
What to do
- Resolve the 5 Hotspot finding(s) in Churn × Complexity Hotspots — start with mod.rs, state.rs, endpoint.rs. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 1 Repeated repair finding(s) in Churn × Complexity Hotspots — start with windows.rs. — One of this dimension's main actionable groups (1 warning-level).
D16 · Bus Factor
5 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is quinn-proto/src/connection/send_buffer.rs. Counted over 73 of the 82 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D17 · Explicit Debt
9 deducted task-comment markers across 36215 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 8 TodoComment finding(s) in Explicit Debt — start with packet.rs, token.rs, mod.rs. — One of this dimension's main actionable groups (8 warning-level).
- Resolve the 1 HackComment finding(s) in Explicit Debt — start with rustls.rs. — One of this dimension's main actionable groups (1 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 9 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Cargo.toml. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
1 of 4 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)
1 finding(s): 0 critical, 1 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 1 REDACTED finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
54 finding(s): 0 critical, 53 high, 1 medium, 0 low. 49 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 49 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 (49 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
1 finding(s): 0 critical, 0 high, 1 medium, 0 low.
What to do
- 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).
D34 · Knowledge Freshness
4 of 73 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is quinn-proto/src/connection/cid_state.rs. Counted over 73 of the 82 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: cubic.rs↔new_reno.rs 69%; send_buffer.rs↔state.rs 54%; mod.rs↔new_reno.rs 54%
What to do
- Resolve the 3 Change coupling finding(s) in Change Coupling — start with cubic.rs, send_buffer.rs, mod.rs. — One of this dimension's main actionable groups (3 warning-level).
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 3 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX9 · CQS / query purity
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.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
- Only 4/5 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `docs/book`.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
P3 · Security & performance tooling
What to do
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
PF1 · Benchmark discipline
PF3 · Async & latency hygiene
S1 · Web-Security Posture
- a rustls `ServerCertVerifier` that accepts every certificate (`SkipServerVerification`) is set on a TLS client, so every peer certificate is accepted — including one an attacker presents. Chain, expiry, revocation and hostname are all skipped, so an attacker on the network path can present any certificate and read or rewrite the traffic — the connection is encrypted to the attacker, not to the intended host. Remove the override so the TLS stack verifies the peer — reqwest, native-tls, rustls and openssl's `SslConnector` all check the chain and hostname when nothing is set. If the server presents a self-signed or privately-issued certificate, trust THAT issuer rather than every certificate: `reqwest::ClientBuilder::add_root_certificate(Certificate::from_pem(…))`, a rustls `RootCertStore` holding its CA, or `SslConnectorBuilder::set_ca_file`, which keeps the chain and hostname checks on. — docs/book/src/bin/certificate.rs:28
What to do
- Stop accepting every TLS certificate: delete `danger_accept_invalid_certs(true)` / `SslVerifyMode::NONE` / the rustls verifier that returns `ServerCertVerified::assertion()` unconditionally, and trust a self-signed or private server by adding its CA as a root (`add_root_certificate`, a rustls `RootCertStore`) — never by switching verification off.
X1 · Async correctness
X14 · Bypassable address classification
X21 · Side-effecting pattern guard
X4 · Structured logging
- `trace!` at line 122 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`. — quinn-proto/src/endpoint.rs:122
- `trace!` at line 209 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`. — quinn-proto/src/endpoint.rs:209
- `debug!` at line 250 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`. — quinn-proto/src/endpoint.rs:250
- `debug!` at line 295 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`. — quinn-proto/src/endpoint.rs:295
- `debug!` at line 303 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`. — quinn-proto/src/endpoint.rs:303
- `debug!` at line 442 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`. — quinn-proto/src/endpoint.rs:442
- `debug!` at line 449 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`. — quinn-proto/src/endpoint.rs:449
- `debug!` at line 456 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`. — quinn-proto/src/endpoint.rs:456
- `debug!` 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: `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`. — quinn-proto/src/endpoint.rs:468
- `trace!` at line 490 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`. — quinn-proto/src/endpoint.rs:490
- `debug!` at line 760 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`. — quinn-proto/src/endpoint.rs:760
- `debug!` at line 816 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`. — quinn-proto/src/endpoint.rs:816
- `trace!` at line 58 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`. — quinn-proto/src/connection/cid_state.rs:58
- `trace!` at line 181 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`. — quinn-proto/src/connection/datagrams.rs:181
- `trace!` at line 696 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`. — quinn-proto/src/connection/mod.rs:696
- `trace!` at line 896 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`. — quinn-proto/src/connection/mod.rs:896
- `trace!` at line 1034 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`. — quinn-proto/src/connection/mod.rs:1034
- `trace!` at line 1090 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`. — quinn-proto/src/connection/mod.rs:1090
- `trace!` at line 1168 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`. — quinn-proto/src/connection/mod.rs:1168
- `trace!` at line 1274 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`. — quinn-proto/src/connection/mod.rs:1274
- `debug!` at line 1674 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`. — quinn-proto/src/connection/mod.rs:1674
- `trace!` at line 1855 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`. — quinn-proto/src/connection/mod.rs:1855
- `error!` at line 2176 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`. — quinn-proto/src/connection/mod.rs:2176
- `warn!` at line 2208 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`. — quinn-proto/src/connection/mod.rs:2208
- `trace!` at line 2229 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`. — quinn-proto/src/connection/mod.rs:2229
- `trace!` at line 2271 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`. — quinn-proto/src/connection/mod.rs:2271
- `trace!` at line 2285 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`. — quinn-proto/src/connection/mod.rs:2285
- `trace!` at line 2306 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`. — quinn-proto/src/connection/mod.rs:2306
- `trace!` at line 2345 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`. — quinn-proto/src/connection/mod.rs:2345
- `trace!` at line 2380 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`. — quinn-proto/src/connection/mod.rs:2380
- `warn!` at line 2409 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`. — quinn-proto/src/connection/mod.rs:2409
- `debug!` at line 2557 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`. — quinn-proto/src/connection/mod.rs:2557
- `debug!` at line 2612 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`. — quinn-proto/src/connection/mod.rs:2612
- `trace!` at line 2663 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`. — quinn-proto/src/connection/mod.rs:2663
- `debug!` at line 2715 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`. — quinn-proto/src/connection/mod.rs:2715
- `trace!` at line 2786 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`. — quinn-proto/src/connection/mod.rs:2786
- `debug!` at line 2794 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`. — quinn-proto/src/connection/mod.rs:2794
- `trace!` at line 2942 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`. — quinn-proto/src/connection/mod.rs:2942
- `debug!` at line 3027 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`. — quinn-proto/src/connection/mod.rs:3027
- `debug!` at line 3043 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`. — quinn-proto/src/connection/mod.rs:3043
What to do
- Interpolated log message defeats structured logging
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 72% | Strong | Solid. |
| Architecture | 90% | Exemplary | Solid. |
| Maturity | 53% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 77% | Strong | Solid. |
| Security | 60% | Adequate — gated by D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Event Sourcing | 100% | Exemplary | Strongest area. |
| Performance | 89% | Exemplary | Solid. |
Unscored — 2 check(s) recorded observations but carry no score
- P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
- X10 Duplicated predicate — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 2 control(s) we could not find positive evidence for
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 68 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.
- 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
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no data at rest for these controls to protect.
- C2 Access Controls — No access-control surface detected in the analyzed source — this repository starts no server another machine can reach (no actix-web HttpServer, axum::serve, Rocket launch, warp::serve, poem or salvo Server, tonic Server::builder, hyper or tiny_http server outside examples and tests, none bound beyond loopback). Access control is therefore N/A here — a crate is authorized by the application that serves it, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~7969 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 — N/A — too few peers to establish a naming convention (4463 declarations, no unit with a dominant convention).
- 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+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .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.
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 50 value object(s); 2 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
- ES1 Fold determinism — not applicable — the code was read and holds no event-replay fold, so there is nothing for this check to judge
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- M4 Documentation accuracy — Not applicable: the 9 current-state document(s) make no claim of a kind M4 checks. 3 claim(s) of kinds M4 does not check were not checked (path 1, environment variable 2); M4 checks only links and versions and artefact counts.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the Rust source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage data present for 77 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- 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
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X16 Unfloored truncation loop — 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.
- X27 Collection changed while being enumerated — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 55 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- TLS certificate validation disabled docs/book/src/bin/certificate.rs:28
Serious — 133 finding(s)
- Low coverage: bench/src/lib.rs bench/src/lib.rs:1
- Low coverage: bench/src/stats.rs bench/src/stats.rs:1
- Low coverage: perf/src/client.rs perf/src/client.rs:1
- Low coverage: perf/src/lib.rs perf/src/lib.rs:1
- Low coverage: perf/src/noprotection.rs perf/src/noprotection.rs:1
- Low coverage: perf/src/server.rs perf/src/server.rs:1
- Low coverage: perf/src/stats.rs perf/src/stats.rs:1
- Low coverage: quinn-proto/src/congestion/bbr/mod.rs quinn-proto/src/congestion/bbr/mod.rs:1
- Low coverage: quinn-proto/src/congestion/new_reno.rs quinn-proto/src/congestion/new_reno.rs:1
- Low coverage: quinn-proto/src/crypto.rs quinn-proto/src/crypto.rs:1
- MethodTooLong: Connection.poll_transmit quinn-proto/src/connection/mod.rs:466
- MethodTooLong: Connection.process_payload quinn-proto/src/connection/mod.rs:2908
- MethodTooLong: Connection.process_decrypted_packet quinn-proto/src/connection/mod.rs:2589
- MethodTooLong: Connection.populate_packet quinn-proto/src/connection/mod.rs:3326
- MethodTooLong: Endpoint.start_accept quinn-proto/src/endpoint.rs:580
- MethodTooLong: Iter.try_next quinn-proto/src/frame.rs:585
- MethodTooLong: StreamsState.write_control_frames quinn-proto/src/connection/streams/state.rs:426
- MethodTooLong: PacketBuilder.new quinn-proto/src/connection/packet_builder.rs:35
- MethodTooLong: Connection.new quinn-proto/src/connection/mod.rs:255
- Connection::poll_transmit (cyclomatic 71) quinn-proto/src/connection/mod.rs:466
- Connection::process_payload (cyclomatic 63) quinn-proto/src/connection/mod.rs:2908
- Connection::process_decrypted_packet (cyclomatic 36) quinn-proto/src/connection/mod.rs:2589
- Connection::populate_packet (cyclomatic 34) quinn-proto/src/connection/mod.rs:3326
- Connection::on_ack_received (cyclomatic 20) quinn-proto/src/connection/mod.rs:1502
- Connection::handle_packet (cyclomatic 20) quinn-proto/src/connection/mod.rs:2370
- Connection::detect_lost_packets (cyclomatic 17) quinn-proto/src/connection/mod.rs:1768
- Connection::finish_packet (cyclomatic 17) quinn-proto/src/connection/mod.rs:2529
- TodoComment quinn-proto/src/packet.rs:602
- TodoComment quinn-proto/src/token.rs:372
- TodoComment quinn-proto/src/connection/mod.rs:3637
- TodoComment quinn-proto/src/connection/send_buffer.rs:24
- TodoComment quinn-proto/src/connection/spaces.rs:169
- TodoComment quinn/src/connection.rs:1270
- TodoComment quinn/src/endpoint.rs:599
- TodoComment perf/src/stats.rs:273
- FileTooLong: connection/mod.rs quinn-proto/src/connection/mod.rs
- FileTooLong: src/endpoint.rs quinn-proto/src/endpoint.rs
- FileTooLong: src/connection.rs quinn/src/connection.rs
- FileTooLong: src/endpoint.rs quinn/src/endpoint.rs
- FileTooLong: src/frame.rs quinn-proto/src/frame.rs
- FileTooLong: src/unix.rs quinn-udp/src/unix.rs
- FileTooLong: streams/state.rs quinn-proto/src/connection/streams/state.rs
- FileTooLong: src/packet.rs quinn-proto/src/packet.rs
- Connection::poll_transmit (cognitive 152) quinn-proto/src/connection/mod.rs:466
- Connection::process_payload (cognitive 92) quinn-proto/src/connection/mod.rs:2908
- Connection::process_decrypted_packet (cognitive 63) quinn-proto/src/connection/mod.rs:2589
- Connection::populate_packet (cognitive 42) quinn-proto/src/connection/mod.rs:3326
- Connection::detect_lost_packets (cognitive 35) quinn-proto/src/connection/mod.rs:1768
- Connection::on_ack_received (cognitive 34) quinn-proto/src/connection/mod.rs:1502
- Connection::handle_packet (cognitive 30) quinn-proto/src/connection/mod.rs:2370
- Hotspot: quinn-proto/src/connection/mod.rs quinn-proto/src/connection/mod.rs:466
- Hotspot: quinn-proto/src/connection/streams/state.rs quinn-proto/src/connection/streams/state.rs:426
- Hotspot: quinn-proto/src/endpoint.rs quinn-proto/src/endpoint.rs:144
- Hotspot: quinn-proto/src/transport_parameters.rs quinn-proto/src/transport_parameters.rs:408
- Hotspot: quinn-proto/src/connection/packet_builder.rs quinn-proto/src/connection/packet_builder.rs:35
- ClassTooLong: Connection quinn-proto/src/connection/mod.rs:134
- ClassTooLong: Endpoint quinn-proto/src/endpoint.rs:45
- ClassTooLong: StreamsState quinn-proto/src/connection/streams/state.rs:69
- TooManyMethods: Connection quinn-proto/src/connection/mod.rs:134
- TooManyMethods: StreamsState quinn-proto/src/connection/streams/state.rs:69
- TooManyMethods: Connection quinn/src/connection.rs:331
- TooManyFields: Connection quinn-proto/src/connection/mod.rs:134
- TooManyFields: Bbr quinn-proto/src/congestion/bbr/mod.rs:26
- TooManyFields: StreamsState quinn-proto/src/connection/streams/state.rs:69
- Change coupling: cubic.rs ↔ new_reno.rs quinn-proto/src/congestion/cubic.rs:1
- Change coupling: send_buffer.rs ↔ state.rs quinn-proto/src/connection/send_buffer.rs:1
- Change coupling: mod.rs ↔ new_reno.rs quinn-proto/src/congestion/bbr/mod.rs:1
- REDACTED
- REDACTED
- REDACTED
- TransportParameters::read (cyclomatic 28) quinn-proto/src/transport_parameters.rs:408
- TransportParameters::write (cyclomatic 25) quinn-proto/src/transport_parameters.rs:309
- StreamsState::write_control_frames (cognitive 43) quinn-proto/src/connection/streams/state.rs:426
- StreamsState::write_stream_frames (cognitive 20) quinn-proto/src/connection/streams/state.rs:608
- TransportParameters::write (cognitive 41) quinn-proto/src/transport_parameters.rs:309
- TransportParameters::read (cognitive 38) quinn-proto/src/transport_parameters.rs:408
- Edited copy of a member (10 corresponding lines) quinn/src/runtime/smol.rs:83
- Edited copy of a member (10 corresponding lines) perf/src/server.rs:124
- Edited copy of a member (9 corresponding lines) quinn-udp/src/apple_fast.rs:186
- Edited copy of a member (9 corresponding lines) quinn/src/recv_stream.rs:272
- Duplicated block (12 lines × 2) quinn/src/endpoint.rs:86
- Duplicated block (12 lines × 2) quinn-proto/src/connection/streams/state.rs:261
- Duplicated block (9 lines × 2) quinn-udp/src/apple_fast.rs:110
- Duplicated block (9 lines × 2) bench/src/stats.rs:49
- Duplicated block (8 lines × 2) quinn/src/recv_stream.rs:648
- Duplicated block (8 lines × 2) perf/src/client.rs:119
- Off the main sequence: quinn-proto
- Off the main sequence: quinn-udp
- Low cohesion: UdpSocketState (LCOM4 5) quinn-udp/src/unix.rs:32
- Low cohesion: EndpointConfig (LCOM4 4) quinn-proto/src/config/mod.rs:37
- Iter::try_next (cyclomatic 37) quinn-proto/src/frame.rs:585
- StreamsState::write_control_frames (cyclomatic 30) quinn-proto/src/connection/streams/state.rs:426
- State::forward_app_events (cyclomatic 19) quinn/src/connection.rs:1319
- PacketBuilder::new (cyclomatic 18) quinn-proto/src/connection/packet_builder.rs:35
- Endpoint::handle (cyclomatic 16) quinn-proto/src/endpoint.rs:144
- Repeated repair: quinn-udp/src/windows.rs quinn-udp/src/windows.rs:388
- HackComment quinn-proto/src/crypto/rustls.rs:130
- Iter::try_next (cognitive 32) quinn-proto/src/frame.rs:585
- RecvState::poll_socket (cognitive 27) quinn/src/endpoint.rs:898
- PacketBuilder::new (cognitive 22) quinn-proto/src/connection/packet_builder.rs:35
- Endpoint::handle (cognitive 22) quinn-proto/src/endpoint.rs:144
- Assembler::defragment (cognitive 19) quinn-proto/src/connection/assembler.rs:104
- quinn_udp::unix::send (cognitive 19) quinn-udp/src/unix.rs:508
- RecvStream::poll_read_generic (cognitive 16) quinn/src/recv_stream.rs:354
- UdpSocketState::new (cognitive 16) quinn-udp/src/windows.rs:46
- REDACTED
- REDACTED
- REDACTED
- Edited copy of a member (25 corresponding lines) quinn-udp/src/apple_fast.rs:154
- Edited copy of a member (18 corresponding lines) quinn/src/endpoint.rs:85
- Edited copy of a member (21 corresponding lines) quinn/src/connection.rs:929
- Edited copy of a member (23 corresponding lines) quinn/src/recv_stream.rs:134
- Edited copy of a member (11 corresponding lines) quinn-proto/src/frame.rs:288
- Edited copy of a member (19 corresponding lines) quinn-proto/src/connection/qlog.rs:130
- Edited copies of one member (3 members, 11+ corresponding lines) quinn-udp/src/unix.rs:224
- Edited copy of a member (16 corresponding lines) quinn-udp/src/unix.rs:1004
- Edited copies of one member (4 members, 5+ corresponding lines) quinn/src/connection.rs:828
- Edited copy of a member (6 corresponding lines) quinn/src/runtime/smol.rs:50
- Duplicated block (13–18 lines × 2) quinn-udp/src/apple_fast.rs:83
- Duplicated block (15 lines × 2) quinn/src/connection.rs:968
- Duplicated block (14 lines × 2) quinn-udp/src/apple_fast.rs:119
- Duplicated block (9–10 lines × 2) quinn-udp/src/wasi.rs:42
- Duplicated block (10 lines × 2) quinn-udp/src/unix.rs:526
- Duplicated block (7 lines × 2) quinn-udp/src/apple_fast.rs:187
- Duplicated block (11 lines × 2) quinn-proto/src/shared.rs:157
- Duplicated block (6 lines × 2) quinn/src/runtime/smol.rs:71
- Duplicated block (5 lines × 2) quinn-proto/src/frame.rs:296
- Edited copy of a member (28 corresponding lines) bench/src/lib.rs:97
- Edited copy of a member (22 corresponding lines) perf/src/client.rs:264
- Edited copy of a member (14 corresponding lines) perf/src/stats.rs:138
- Duplicated block (17 lines × 2) bench/src/lib.rs:213
- Duplicated block (6–8 lines × 2) perf/src/client.rs:316
- Coverage collected but not gated
Minor — 59 finding(s)
- Interpolated log message defeats structured logging quinn-proto/src/endpoint.rs:122
- Interpolated log message defeats structured logging quinn-proto/src/endpoint.rs:209
- Interpolated log message defeats structured logging quinn-proto/src/endpoint.rs:250
- Interpolated log message defeats structured logging quinn-proto/src/endpoint.rs:295
- Interpolated log message defeats structured logging quinn-proto/src/endpoint.rs:303
- Interpolated log message defeats structured logging quinn-proto/src/endpoint.rs:442
- Interpolated log message defeats structured logging quinn-proto/src/endpoint.rs:449
- Interpolated log message defeats structured logging quinn-proto/src/endpoint.rs:456
- Interpolated log message defeats structured logging quinn-proto/src/endpoint.rs:468
- Interpolated log message defeats structured logging quinn-proto/src/endpoint.rs:490
- Interpolated log message defeats structured logging quinn-proto/src/endpoint.rs:760
- Interpolated log message defeats structured logging quinn-proto/src/endpoint.rs:816
- Interpolated log message defeats structured logging quinn-proto/src/connection/cid_state.rs:58
- Interpolated log message defeats structured logging quinn-proto/src/connection/datagrams.rs:181
- Interpolated log message defeats structured logging quinn-proto/src/connection/mod.rs:696
- Interpolated log message defeats structured logging quinn-proto/src/connection/mod.rs:896
- Interpolated log message defeats structured logging quinn-proto/src/connection/mod.rs:1034
- Interpolated log message defeats structured logging quinn-proto/src/connection/mod.rs:1090
- Interpolated log message defeats structured logging quinn-proto/src/connection/mod.rs:1168
- Interpolated log message defeats structured logging quinn-proto/src/connection/mod.rs:1274
- Interpolated log message defeats structured logging quinn-proto/src/connection/mod.rs:1674
- Interpolated log message defeats structured logging quinn-proto/src/connection/mod.rs:1855
- Interpolated log message defeats structured logging quinn-proto/src/connection/mod.rs:2176
- Interpolated log message defeats structured logging quinn-proto/src/connection/mod.rs:2208
- Interpolated log message defeats structured logging quinn-proto/src/connection/mod.rs:2229
- Orphaned file quinn-proto/src/connection/cid_state.rs:1
- Orphaned file quinn/src/work_limiter.rs:1
- Orphaned file quinn-proto/src/congestion/bbr/min_max.rs:1
- Orphaned file bench/src/stats.rs:1
- Duplicated predicate quinn/src/recv_stream.rs:561
- Duplicated predicate quinn/src/recv_stream.rs:274
- Off-boarding risk: anonymized user #1
- Further sole-owners (lower concentration)
- No ADRs found perf/Cargo.toml:8
- Projects may be oversized for their cohesion
- REDACTED
- Orphaned files with no living knowledge
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- Logging is not universal
- No changelog
Minor — 3 finding(s)
- Outdated: aws-lc-rs
- Outdated: qlog
- Outdated: rustls-pki-types
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-12a2fce470654908b6e362bb07ffc55f/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/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-12a2fce470654908b6e362bb07ffc55f/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 54 | 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 . | 1 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 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 |