Executive summary
libp2p/rust-libp2p meets our standard for a preview release, though it has pipeline tools referenced by a changeable name. It scores 66 out of 100 and is rated Strong, and 65 of its 66 critical findings are security problems.
Security and Compliance, at 51, is the weakest lens and counts most in the score. The best first step is checking access in every handler, worth about 11 points. Adding the security headers comes next, worth about 5 points. Raising Security and Compliance to 68 would lift the score to about 74.
Fifty-six pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Four secrets can leak from the build pipeline, and two settings leave the servers or containers unsafe. Pinning each tool to an exact version, limiting each secret to its own step and correcting the unsafe settings would close these risks. Setting a waiting period for automatic updates would fix the automatic dependency update that takes a new release at once, and giving the pull-request workflow read-only access would deal with the pipeline that outsiders can trigger with write access. Moving the write out of the read operation would take care of the read operation that also writes data.
The product code is 92,996 lines, about €140,000 to rebuild.
If Security and Compliance rose from 51 to 68, the lowest score rated Strong, the score would rise from 66 to about 74.
New since the last survey: 20 findings
- Cognitive Complexity · MemoryStore::on_swarm_event (cognitive 22) misc/peer-store/src/memory_store.rs
- God Classes · FileTooLong: src/keypair.rs identity/src/keypair.rs
- Code Duplication · Duplicated block (7 lines × 2) identity/src/keypair.rs
- Code Duplication · Duplicated block (7 lines × 2) identity/src/keypair.rs
- Code Duplication · Duplicated block (6 lines × 2) identity/src/keypair.rs
- Code Duplication · Duplicated block (6 lines × 2) identity/src/keypair.rs
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
Fixed since the last survey: 4 findings
- Churn × Complexity Hotspots · Hotspot: protocols/gossipsub/src/behaviour.rs protocols/gossipsub/src/behaviour.rs
- Supply-chain Provenance & Signing REDACTED
- Supply-chain Provenance & Signing REDACTED
- Supply-chain Provenance & Signing REDACTED
Rebuild cost: about €140,000 · Estimate
| Cost to rebuild | €45,000 to €230,000, for 758 to 2,403 hours of work, about 0.9 person-years for 1 to 2 engineers |
|---|---|
| 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.9 at a score of 66. 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: 92,996 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 libp2p_core.connection | 2 libp2p_gossipsub.topic | 3 libp2p_identity.ecdsa | 4 libp2p_webrtc.tokio.req_res_chan | 5 libp2p_webrtc_utils.fingerprint | 6 multistream_select.dialer_select | 7 libp2p_core.transport.global_only | 8 libp2p_identity.peer_id | 9 libp2p_swarm.stream_protocol | 10 libp2p_webrtc_utils.stream | 11 libp2p_identify.protocol | 12 libp2p_kad.kbucket.key | 13 libp2p_core.upgrade | 14 libp2p_kad.protocol | 15 multistream_select.protocol | 16 prost_codec | 17 libp2p_autonat.v2.protocol | 18 libp2p_core.transport.upgrade | 19 libp2p_mplex.io | 20 libp2p_swarm.handler | 21 libp2p_autonat.v1.protocol | 22 libp2p_core.transport | 23 libp2p_autonat.v1.generated.structs.message | 24 libp2p_core.transport.memory | 25 libp2p_swarm | 26 libp2p_gossipsub.types | 27 libp2p_swarm.behaviour | 28 libp2p_gossipsub.behaviour | 29 libp2p_gossipsub.protocol | 30 libp2p_identify.behaviour | 31 libp2p_mdns.behaviour | 32 libp2p_peer_store.memory_store | 33 libp2p_relay.priv_client | 34 libp2p_swarm.dummy | 35 libp2p_autonat.v1.behaviour | 36 libp2p_kad.handler | 37 libp2p_metrics | 38 libp2p_request_response | 39 libp2p_kad.behaviour | 40 libp2p_rendezvous.client |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 libp2p_core.connection | ||||||||||||||||||||||||||||||||||||||||
| 2 libp2p_gossipsub.topic | ||||||||||||||||||||||||||||||||||||||||
| 3 libp2p_identity.ecdsa | ||||||||||||||||||||||||||||||||||||||||
| 4 libp2p_webrtc.tokio.req_res_chan | ||||||||||||||||||||||||||||||||||||||||
| 5 libp2p_webrtc_utils.fingerprint | ||||||||||||||||||||||||||||||||||||||||
| 6 multistream_select.dialer_select | ||||||||||||||||||||||||||||||||||||||||
| 7 libp2p_core.transport.global_only | 2 | |||||||||||||||||||||||||||||||||||||||
| 8 libp2p_identity.peer_id | 1 | |||||||||||||||||||||||||||||||||||||||
| 9 libp2p_swarm.stream_protocol | 1 | |||||||||||||||||||||||||||||||||||||||
| 10 libp2p_webrtc_utils.stream | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 11 libp2p_identify.protocol | 3 | 3 | ||||||||||||||||||||||||||||||||||||||
| 12 libp2p_kad.kbucket.key | 1 | |||||||||||||||||||||||||||||||||||||||
| 13 libp2p_core.upgrade | 4 | |||||||||||||||||||||||||||||||||||||||
| 14 libp2p_kad.protocol | 1 | 1 | 1 | 3 | 3 | 2 | ||||||||||||||||||||||||||||||||||
| 15 multistream_select.protocol | 2 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 16 prost_codec | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 17 libp2p_autonat.v2.protocol | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 18 libp2p_core.transport.upgrade | 2 | 1 | 1 | 4 | ||||||||||||||||||||||||||||||||||||
| 19 libp2p_mplex.io | 1 | |||||||||||||||||||||||||||||||||||||||
| 20 libp2p_swarm.handler | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 21 libp2p_autonat.v1.protocol | 1 | 1 | 2 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 22 libp2p_core.transport | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 23 libp2p_autonat.v1.generated.structs.message | 1 | |||||||||||||||||||||||||||||||||||||||
| 24 libp2p_core.transport.memory | 2 | 1 | 1 | 1 | 3 | |||||||||||||||||||||||||||||||||||
| 25 libp2p_swarm | 1 | 1 | 3 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||||
| 26 libp2p_gossipsub.types | 6 | 3 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 27 libp2p_swarm.behaviour | 4 | 7 | 6 | 6 | 2 | |||||||||||||||||||||||||||||||||||
| 28 libp2p_gossipsub.behaviour | 1 | 2 | 1 | 3 | 1 | 1 | 1 | 6 | 5 | |||||||||||||||||||||||||||||||
| 29 libp2p_gossipsub.protocol | 2 | 1 | 1 | 3 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 30 libp2p_identify.behaviour | 1 | 4 | 3 | 1 | 2 | 1 | 3 | |||||||||||||||||||||||||||||||||
| 31 libp2p_mdns.behaviour | 1 | 2 | 1 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||
| 32 libp2p_peer_store.memory_store | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 33 libp2p_relay.priv_client | 1 | 1 | 2 | 1 | 1 | 1 | 4 | |||||||||||||||||||||||||||||||||
| 34 libp2p_swarm.dummy | 1 | 1 | 1 | 2 | 1 | 2 | ||||||||||||||||||||||||||||||||||
| 35 libp2p_autonat.v1.behaviour | 1 | 1 | 1 | 1 | 6 | 1 | ||||||||||||||||||||||||||||||||||
| 36 libp2p_kad.handler | 1 | 1 | 1 | 4 | 1 | 4 | 1 | 1 | ||||||||||||||||||||||||||||||||
| 37 libp2p_metrics | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 38 libp2p_request_response | 1 | 1 | 1 | 2 | 1 | 2 | 1 | 5 | 1 | |||||||||||||||||||||||||||||||
| 39 libp2p_kad.behaviour | 1 | 4 | 1 | 7 | 1 | 1 | 2 | 1 | 1 | 6 | 2 | 1 | 1 | |||||||||||||||||||||||||||
| 40 libp2p_rendezvous.client | 1 | 1 | 1 | 1 | 1 | 1 | 2 | 1 | 1 |
7→22 libp2p_core.transport.global_only uses libp2p_core.transport part of a loop✕
- Connections
- 2 pairs of types, where a type in libp2p_core.transport.global_only uses a type in libp2p_core.transport.
- The types involved
libp2p_core.transport.global_only.Transport→libp2p_core.transport.DialOptslibp2p_core.transport.global_only.Transport→libp2p_core.transport.ListenerId
- Direction
- libp2p_core.transport.global_only uses libp2p_core.transport, so a change to libp2p_core.transport can break libp2p_core.transport.global_only, while a change to libp2p_core.transport.global_only can't break libp2p_core.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.
8→3 libp2p_identity.peer_id uses libp2p_identity.ecdsa✕
- Connections
- 1 pair of types, where a type in libp2p_identity.peer_id uses a type in libp2p_identity.ecdsa.
- The types involved
libp2p_identity.peer_id.PeerId→libp2p_identity.ecdsa.PublicKey
- Direction
- libp2p_identity.peer_id uses libp2p_identity.ecdsa, so a change to libp2p_identity.ecdsa can break libp2p_identity.peer_id, while a change to libp2p_identity.peer_id can't break libp2p_identity.ecdsa.
- Position
- Below the diagonal: libp2p_identity.peer_id uses a module listed above it, which is the healthy direction.
9→16 libp2p_swarm.stream_protocol uses prost_codec part of a loop✕
- Connections
- 1 pair of types, where a type in libp2p_swarm.stream_protocol uses a type in prost_codec.
- The types involved
libp2p_swarm.stream_protocol.InvalidProtocol→prost_codec.Error
- Direction
- libp2p_swarm.stream_protocol uses prost_codec, so a change to prost_codec can break libp2p_swarm.stream_protocol, while a change to libp2p_swarm.stream_protocol can't break prost_codec.
- 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→4 libp2p_webrtc_utils.stream uses libp2p_webrtc.tokio.req_res_chan✕
- Connections
- 1 pair of types, where a type in libp2p_webrtc_utils.stream uses a type in libp2p_webrtc.tokio.req_res_chan.
- The types involved
libp2p_webrtc_utils.stream.Stream→libp2p_webrtc.tokio.req_res_chan.Sender
- Direction
- libp2p_webrtc_utils.stream uses libp2p_webrtc.tokio.req_res_chan, so a change to libp2p_webrtc.tokio.req_res_chan can break libp2p_webrtc_utils.stream, while a change to libp2p_webrtc_utils.stream can't break libp2p_webrtc.tokio.req_res_chan.
- Position
- Below the diagonal: libp2p_webrtc_utils.stream uses a module listed above it, which is the healthy direction.
10→6 libp2p_webrtc_utils.stream uses multistream_select.dialer_select✕
- Connections
- 1 pair of types, where a type in libp2p_webrtc_utils.stream uses a type in multistream_select.dialer_select.
- The types involved
libp2p_webrtc_utils.stream.Stream→multistream_select.dialer_select.State
- Direction
- libp2p_webrtc_utils.stream uses multistream_select.dialer_select, so a change to multistream_select.dialer_select can break libp2p_webrtc_utils.stream, while a change to libp2p_webrtc_utils.stream can't break multistream_select.dialer_select.
- Position
- Below the diagonal: libp2p_webrtc_utils.stream uses a module listed above it, which is the healthy direction.
11→3 libp2p_identify.protocol uses libp2p_identity.ecdsa✕
- Connections
- 3 pairs of types, where a type in libp2p_identify.protocol uses a type in libp2p_identity.ecdsa.
- The types involved
libp2p_identify.protocol.Info→libp2p_identity.ecdsa.PublicKeylibp2p_identify.protocol.PushInfo→libp2p_identity.ecdsa.PublicKeylibp2p_identify.protocol.protocol$module→libp2p_identity.ecdsa.PublicKey
- Direction
- libp2p_identify.protocol uses libp2p_identity.ecdsa, so a change to libp2p_identity.ecdsa can break libp2p_identify.protocol, while a change to libp2p_identify.protocol can't break libp2p_identity.ecdsa.
- Position
- Below the diagonal: libp2p_identify.protocol uses a module listed above it, which is the healthy direction.
11→9 libp2p_identify.protocol uses libp2p_swarm.stream_protocol✕
- Connections
- 3 pairs of types, where a type in libp2p_identify.protocol uses a type in libp2p_swarm.stream_protocol.
- The types involved
libp2p_identify.protocol.Info→libp2p_swarm.stream_protocol.StreamProtocollibp2p_identify.protocol.PushInfo→libp2p_swarm.stream_protocol.StreamProtocollibp2p_identify.protocol.protocol$module→libp2p_swarm.stream_protocol.StreamProtocol
- Direction
- libp2p_identify.protocol uses libp2p_swarm.stream_protocol, so a change to libp2p_swarm.stream_protocol can break libp2p_identify.protocol, while a change to libp2p_identify.protocol can't break libp2p_swarm.stream_protocol.
- Position
- Below the diagonal: libp2p_identify.protocol uses a module listed above it, which is the healthy direction.
12→8 libp2p_kad.kbucket.key uses libp2p_identity.peer_id✕
- Connections
- 1 pair of types, where a type in libp2p_kad.kbucket.key uses a type in libp2p_identity.peer_id.
- The types involved
libp2p_kad.kbucket.key.Key→libp2p_identity.peer_id.PeerId
- Direction
- libp2p_kad.kbucket.key uses libp2p_identity.peer_id, so a change to libp2p_identity.peer_id can break libp2p_kad.kbucket.key, while a change to libp2p_kad.kbucket.key can't break libp2p_identity.peer_id.
- Position
- Below the diagonal: libp2p_kad.kbucket.key uses a module listed above it, which is the healthy direction.
13→11 libp2p_core.upgrade uses libp2p_identify.protocol✕
- Connections
- 4 pairs of types, where a type in libp2p_core.upgrade uses a type in libp2p_identify.protocol.
- The types involved
libp2p_core.upgrade.InboundConnectionUpgrade→libp2p_identify.protocol.Infolibp2p_core.upgrade.InboundUpgrade→libp2p_identify.protocol.Infolibp2p_core.upgrade.OutboundConnectionUpgrade→libp2p_identify.protocol.Infolibp2p_core.upgrade.OutboundUpgrade→libp2p_identify.protocol.Info
- Direction
- libp2p_core.upgrade uses libp2p_identify.protocol, so a change to libp2p_identify.protocol can break libp2p_core.upgrade, while a change to libp2p_core.upgrade can't break libp2p_identify.protocol.
- Position
- Below the diagonal: libp2p_core.upgrade uses a module listed above it, which is the healthy direction.
14→8 libp2p_kad.protocol uses libp2p_identity.peer_id✕
- Connections
- 1 pair of types, where a type in libp2p_kad.protocol uses a type in libp2p_identity.peer_id.
- The types involved
libp2p_kad.protocol.KadPeer→libp2p_identity.peer_id.PeerId
- Direction
- libp2p_kad.protocol uses libp2p_identity.peer_id, so a change to libp2p_identity.peer_id can break libp2p_kad.protocol, while a change to libp2p_kad.protocol can't break libp2p_identity.peer_id.
- Position
- Below the diagonal: libp2p_kad.protocol uses a module listed above it, which is the healthy direction.
14→9 libp2p_kad.protocol uses libp2p_swarm.stream_protocol✕
- Connections
- 1 pair of types, where a type in libp2p_kad.protocol uses a type in libp2p_swarm.stream_protocol.
- The types involved
libp2p_kad.protocol.ProtocolConfig→libp2p_swarm.stream_protocol.StreamProtocol
- Direction
- libp2p_kad.protocol uses libp2p_swarm.stream_protocol, so a change to libp2p_swarm.stream_protocol can break libp2p_kad.protocol, while a change to libp2p_kad.protocol can't break libp2p_swarm.stream_protocol.
- Position
- Below the diagonal: libp2p_kad.protocol uses a module listed above it, which is the healthy direction.
14→11 libp2p_kad.protocol uses libp2p_identify.protocol✕
- Connections
- 1 pair of types, where a type in libp2p_kad.protocol uses a type in libp2p_identify.protocol.
- The types involved
libp2p_kad.protocol.ProtocolConfig→libp2p_identify.protocol.Info
- Direction
- libp2p_kad.protocol uses libp2p_identify.protocol, so a change to libp2p_identify.protocol can break libp2p_kad.protocol, while a change to libp2p_kad.protocol can't break libp2p_identify.protocol.
- Position
- Below the diagonal: libp2p_kad.protocol uses a module listed above it, which is the healthy direction.
14→13 libp2p_kad.protocol uses libp2p_core.upgrade✕
- Connections
- 3 pairs of types, where a type in libp2p_kad.protocol uses a type in libp2p_core.upgrade.
- The types involved
libp2p_kad.protocol.ProtocolConfig→libp2p_core.upgrade.InboundUpgradelibp2p_kad.protocol.ProtocolConfig→libp2p_core.upgrade.OutboundUpgradelibp2p_kad.protocol.ProtocolConfig→libp2p_core.upgrade.UpgradeInfo
- Direction
- libp2p_kad.protocol uses libp2p_core.upgrade, so a change to libp2p_core.upgrade can break libp2p_kad.protocol, while a change to libp2p_kad.protocol can't break libp2p_core.upgrade.
- Position
- Below the diagonal: libp2p_kad.protocol uses a module listed above it, which is the healthy direction.
14→15 libp2p_kad.protocol uses multistream_select.protocol part of a loop✕
- Connections
- 3 pairs of types, where a type in libp2p_kad.protocol uses a type in multistream_select.protocol.
- The types involved
libp2p_kad.protocol.KadRequestMsg→multistream_select.protocol.Messagelibp2p_kad.protocol.KadResponseMsg→multistream_select.protocol.Messagelibp2p_kad.protocol.protocol$module→multistream_select.protocol.Message
- Direction
- libp2p_kad.protocol uses multistream_select.protocol, so a change to multistream_select.protocol can break libp2p_kad.protocol, while a change to libp2p_kad.protocol can't break multistream_select.protocol.
- 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→16 libp2p_kad.protocol uses prost_codec part of a loop✕
- Connections
- 2 pairs of types, where a type in libp2p_kad.protocol uses a type in prost_codec.
- The types involved
libp2p_kad.protocol.Codec→prost_codec.Codeclibp2p_kad.protocol.protocol$module→prost_codec.Error
- Direction
- libp2p_kad.protocol uses prost_codec, so a change to prost_codec can break libp2p_kad.protocol, while a change to libp2p_kad.protocol can't break prost_codec.
- 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→10 multistream_select.protocol uses libp2p_webrtc_utils.stream✕
- Connections
- 2 pairs of types, where a type in multistream_select.protocol uses a type in libp2p_webrtc_utils.stream.
- The types involved
multistream_select.protocol.MessageIO→libp2p_webrtc_utils.stream.Streammultistream_select.protocol.MessageReader→libp2p_webrtc_utils.stream.Stream
- Direction
- multistream_select.protocol uses libp2p_webrtc_utils.stream, so a change to libp2p_webrtc_utils.stream can break multistream_select.protocol, while a change to multistream_select.protocol can't break libp2p_webrtc_utils.stream.
- Position
- Below the diagonal: multistream_select.protocol uses a module listed above it, which is the healthy direction.
15→14 multistream_select.protocol uses libp2p_kad.protocol✕
- Connections
- 2 pairs of types, where a type in multistream_select.protocol uses a type in libp2p_kad.protocol.
- The types involved
multistream_select.protocol.Message→libp2p_kad.protocol.KadRequestMsgmultistream_select.protocol.Message→libp2p_kad.protocol.KadResponseMsg
- Direction
- multistream_select.protocol uses libp2p_kad.protocol, so a change to libp2p_kad.protocol can break multistream_select.protocol, while a change to multistream_select.protocol can't break libp2p_kad.protocol.
- Position
- Below the diagonal: multistream_select.protocol uses a module listed above it, which is the healthy direction.
15→16 multistream_select.protocol uses prost_codec part of a loop✕
- Connections
- 1 pair of types, where a type in multistream_select.protocol uses a type in prost_codec.
- The types involved
multistream_select.protocol.ProtocolError→prost_codec.Error
- Direction
- multistream_select.protocol uses prost_codec, so a change to prost_codec can break multistream_select.protocol, while a change to multistream_select.protocol can't break prost_codec.
- 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→8 prost_codec uses libp2p_identity.peer_id✕
- Connections
- 1 pair of types, where a type in prost_codec uses a type in libp2p_identity.peer_id.
- The types involved
prost_codec.Error→libp2p_identity.peer_id.ParseError
- Direction
- prost_codec uses libp2p_identity.peer_id, so a change to libp2p_identity.peer_id can break prost_codec, while a change to prost_codec can't break libp2p_identity.peer_id.
- Position
- Below the diagonal: prost_codec uses a module listed above it, which is the healthy direction.
16→15 prost_codec uses multistream_select.protocol✕
- Connections
- 1 pair of types, where a type in prost_codec uses a type in multistream_select.protocol.
- The types involved
prost_codec.Error→multistream_select.protocol.ProtocolError
- Direction
- prost_codec uses multistream_select.protocol, so a change to multistream_select.protocol can break prost_codec, while a change to prost_codec can't break multistream_select.protocol.
- Position
- Below the diagonal: prost_codec uses a module listed above it, which is the healthy direction.
17→15 libp2p_autonat.v2.protocol uses multistream_select.protocol✕
- Connections
- 2 pairs of types, where a type in libp2p_autonat.v2.protocol uses a type in multistream_select.protocol.
- The types involved
libp2p_autonat.v2.protocol.Request→multistream_select.protocol.Messagelibp2p_autonat.v2.protocol.Response→multistream_select.protocol.Message
- Direction
- libp2p_autonat.v2.protocol uses multistream_select.protocol, so a change to multistream_select.protocol can break libp2p_autonat.v2.protocol, while a change to libp2p_autonat.v2.protocol can't break multistream_select.protocol.
- Position
- Below the diagonal: libp2p_autonat.v2.protocol uses a module listed above it, which is the healthy direction.
17→16 libp2p_autonat.v2.protocol uses prost_codec✕
- Connections
- 1 pair of types, where a type in libp2p_autonat.v2.protocol uses a type in prost_codec.
- The types involved
libp2p_autonat.v2.protocol.protocol$module→prost_codec.Error
- Direction
- libp2p_autonat.v2.protocol uses prost_codec, so a change to prost_codec can break libp2p_autonat.v2.protocol, while a change to libp2p_autonat.v2.protocol can't break prost_codec.
- Position
- Below the diagonal: libp2p_autonat.v2.protocol uses a module listed above it, which is the healthy direction.
17→23 libp2p_autonat.v2.protocol uses libp2p_autonat.v1.generated.structs.message part of a loop✕
- Connections
- 1 pair of types, where a type in libp2p_autonat.v2.protocol uses a type in libp2p_autonat.v1.generated.structs.message.
- The types involved
libp2p_autonat.v2.protocol.DialResponse→libp2p_autonat.v1.generated.structs.message.ResponseStatus
- Direction
- libp2p_autonat.v2.protocol uses libp2p_autonat.v1.generated.structs.message, so a change to libp2p_autonat.v1.generated.structs.message can break libp2p_autonat.v2.protocol, while a change to libp2p_autonat.v2.protocol can't break libp2p_autonat.v1.generated.structs.message.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→7 libp2p_core.transport.upgrade uses libp2p_core.transport.global_only✕
- Connections
- 2 pairs of types, where a type in libp2p_core.transport.upgrade uses a type in libp2p_core.transport.global_only.
- The types involved
libp2p_core.transport.upgrade.Multiplexed→libp2p_core.transport.global_only.Transportlibp2p_core.transport.upgrade.Upgrade→libp2p_core.transport.global_only.Transport
- Direction
- libp2p_core.transport.upgrade uses libp2p_core.transport.global_only, so a change to libp2p_core.transport.global_only can break libp2p_core.transport.upgrade, while a change to libp2p_core.transport.upgrade can't break libp2p_core.transport.global_only.
- Position
- Below the diagonal: libp2p_core.transport.upgrade uses a module listed above it, which is the healthy direction.
18→8 libp2p_core.transport.upgrade uses libp2p_identity.peer_id✕
- Connections
- 1 pair of types, where a type in libp2p_core.transport.upgrade uses a type in libp2p_identity.peer_id.
- The types involved
libp2p_core.transport.upgrade.Multiplex→libp2p_identity.peer_id.PeerId
- Direction
- libp2p_core.transport.upgrade uses libp2p_identity.peer_id, so a change to libp2p_identity.peer_id can break libp2p_core.transport.upgrade, while a change to libp2p_core.transport.upgrade can't break libp2p_identity.peer_id.
- Position
- Below the diagonal: libp2p_core.transport.upgrade uses a module listed above it, which is the healthy direction.
18→16 libp2p_core.transport.upgrade uses prost_codec✕
- Connections
- 1 pair of types, where a type in libp2p_core.transport.upgrade uses a type in prost_codec.
- The types involved
libp2p_core.transport.upgrade.TransportUpgradeError→prost_codec.Error
- Direction
- libp2p_core.transport.upgrade uses prost_codec, so a change to prost_codec can break libp2p_core.transport.upgrade, while a change to libp2p_core.transport.upgrade can't break prost_codec.
- Position
- Below the diagonal: libp2p_core.transport.upgrade uses a module listed above it, which is the healthy direction.
18→22 libp2p_core.transport.upgrade uses libp2p_core.transport part of a loop✕
- Connections
- 4 pairs of types, where a type in libp2p_core.transport.upgrade uses a type in libp2p_core.transport.
- The types involved
libp2p_core.transport.upgrade.Multiplexed→libp2p_core.transport.DialOptslibp2p_core.transport.upgrade.Multiplexed→libp2p_core.transport.ListenerIdlibp2p_core.transport.upgrade.Upgrade→libp2p_core.transport.DialOptslibp2p_core.transport.upgrade.Upgrade→libp2p_core.transport.ListenerId
- Direction
- libp2p_core.transport.upgrade uses libp2p_core.transport, so a change to libp2p_core.transport can break libp2p_core.transport.upgrade, while a change to libp2p_core.transport.upgrade can't break libp2p_core.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.
19→16 libp2p_mplex.io uses prost_codec✕
- Connections
- 1 pair of types, where a type in libp2p_mplex.io uses a type in prost_codec.
- The types involved
libp2p_mplex.io.Multiplexed→prost_codec.Error
- Direction
- libp2p_mplex.io uses prost_codec, so a change to prost_codec can break libp2p_mplex.io, while a change to libp2p_mplex.io can't break prost_codec.
- Position
- Below the diagonal: libp2p_mplex.io uses a module listed above it, which is the healthy direction.
20→9 libp2p_swarm.handler uses libp2p_swarm.stream_protocol✕
- Connections
- 1 pair of types, where a type in libp2p_swarm.handler uses a type in libp2p_swarm.stream_protocol.
- The types involved
libp2p_swarm.handler.ProtocolsChange→libp2p_swarm.stream_protocol.StreamProtocol
- Direction
- libp2p_swarm.handler uses libp2p_swarm.stream_protocol, so a change to libp2p_swarm.stream_protocol can break libp2p_swarm.handler, while a change to libp2p_swarm.handler can't break libp2p_swarm.stream_protocol.
- Position
- Below the diagonal: libp2p_swarm.handler uses a module listed above it, which is the healthy direction.
20→16 libp2p_swarm.handler uses prost_codec✕
- Connections
- 2 pairs of types, where a type in libp2p_swarm.handler uses a type in prost_codec.
- The types involved
libp2p_swarm.handler.ListenUpgradeError→prost_codec.Errorlibp2p_swarm.handler.StreamUpgradeError→prost_codec.Error
- Direction
- libp2p_swarm.handler uses prost_codec, so a change to prost_codec can break libp2p_swarm.handler, while a change to libp2p_swarm.handler can't break prost_codec.
- Position
- Below the diagonal: libp2p_swarm.handler uses a module listed above it, which is the healthy direction.
21→8 libp2p_autonat.v1.protocol uses libp2p_identity.peer_id✕
- Connections
- 1 pair of types, where a type in libp2p_autonat.v1.protocol uses a type in libp2p_identity.peer_id.
- The types involved
libp2p_autonat.v1.protocol.DialRequest→libp2p_identity.peer_id.PeerId
- Direction
- libp2p_autonat.v1.protocol uses libp2p_identity.peer_id, so a change to libp2p_identity.peer_id can break libp2p_autonat.v1.protocol, while a change to libp2p_autonat.v1.protocol can't break libp2p_identity.peer_id.
- Position
- Below the diagonal: libp2p_autonat.v1.protocol uses a module listed above it, which is the healthy direction.
21→9 libp2p_autonat.v1.protocol uses libp2p_swarm.stream_protocol✕
- Connections
- 1 pair of types, where a type in libp2p_autonat.v1.protocol uses a type in libp2p_swarm.stream_protocol.
- The types involved
libp2p_autonat.v1.protocol.AutoNatCodec→libp2p_swarm.stream_protocol.StreamProtocol
- Direction
- libp2p_autonat.v1.protocol uses libp2p_swarm.stream_protocol, so a change to libp2p_swarm.stream_protocol can break libp2p_autonat.v1.protocol, while a change to libp2p_autonat.v1.protocol can't break libp2p_swarm.stream_protocol.
- Position
- Below the diagonal: libp2p_autonat.v1.protocol uses a module listed above it, which is the healthy direction.
21→15 libp2p_autonat.v1.protocol uses multistream_select.protocol✕
- Connections
- 2 pairs of types, where a type in libp2p_autonat.v1.protocol uses a type in multistream_select.protocol.
- The types involved
libp2p_autonat.v1.protocol.DialRequest→multistream_select.protocol.Messagelibp2p_autonat.v1.protocol.DialResponse→multistream_select.protocol.Message
- Direction
- libp2p_autonat.v1.protocol uses multistream_select.protocol, so a change to multistream_select.protocol can break libp2p_autonat.v1.protocol, while a change to libp2p_autonat.v1.protocol can't break multistream_select.protocol.
- Position
- Below the diagonal: libp2p_autonat.v1.protocol uses a module listed above it, which is the healthy direction.
21→16 libp2p_autonat.v1.protocol uses prost_codec✕
- Connections
- 2 pairs of types, where a type in libp2p_autonat.v1.protocol uses a type in prost_codec.
- The types involved
libp2p_autonat.v1.protocol.AutoNatCodec→prost_codec.Codeclibp2p_autonat.v1.protocol.protocol$module→prost_codec.Codec
- Direction
- libp2p_autonat.v1.protocol uses prost_codec, so a change to prost_codec can break libp2p_autonat.v1.protocol, while a change to libp2p_autonat.v1.protocol can't break prost_codec.
- Position
- Below the diagonal: libp2p_autonat.v1.protocol uses a module listed above it, which is the healthy direction.
21→17 libp2p_autonat.v1.protocol uses libp2p_autonat.v2.protocol✕
- Connections
- 1 pair of types, where a type in libp2p_autonat.v1.protocol uses a type in libp2p_autonat.v2.protocol.
- The types involved
libp2p_autonat.v1.protocol.AutoNatCodec→libp2p_autonat.v2.protocol.Response
- Direction
- libp2p_autonat.v1.protocol uses libp2p_autonat.v2.protocol, so a change to libp2p_autonat.v2.protocol can break libp2p_autonat.v1.protocol, while a change to libp2p_autonat.v1.protocol can't break libp2p_autonat.v2.protocol.
- Position
- Below the diagonal: libp2p_autonat.v1.protocol uses a module listed above it, which is the healthy direction.
21→23 libp2p_autonat.v1.protocol uses libp2p_autonat.v1.generated.structs.message part of a loop✕
- Connections
- 1 pair of types, where a type in libp2p_autonat.v1.protocol uses a type in libp2p_autonat.v1.generated.structs.message.
- The types involved
libp2p_autonat.v1.protocol.ResponseError→libp2p_autonat.v1.generated.structs.message.ResponseStatus
- Direction
- libp2p_autonat.v1.protocol uses libp2p_autonat.v1.generated.structs.message, so a change to libp2p_autonat.v1.generated.structs.message can break libp2p_autonat.v1.protocol, while a change to libp2p_autonat.v1.protocol can't break libp2p_autonat.v1.generated.structs.message.
- 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→1 libp2p_core.transport uses libp2p_core.connection✕
- Connections
- 1 pair of types, where a type in libp2p_core.transport uses a type in libp2p_core.connection.
- The types involved
libp2p_core.transport.DialOpts→libp2p_core.connection.Endpoint
- Direction
- libp2p_core.transport uses libp2p_core.connection, so a change to libp2p_core.connection can break libp2p_core.transport, while a change to libp2p_core.transport can't break libp2p_core.connection.
- Position
- Below the diagonal: libp2p_core.transport uses a module listed above it, which is the healthy direction.
22→16 libp2p_core.transport uses prost_codec✕
- Connections
- 1 pair of types, where a type in libp2p_core.transport uses a type in prost_codec.
- The types involved
libp2p_core.transport.TransportError→prost_codec.Error
- Direction
- libp2p_core.transport uses prost_codec, so a change to prost_codec can break libp2p_core.transport, while a change to libp2p_core.transport can't break prost_codec.
- Position
- Below the diagonal: libp2p_core.transport uses a module listed above it, which is the healthy direction.
22→18 libp2p_core.transport uses libp2p_core.transport.upgrade✕
- Connections
- 1 pair of types, where a type in libp2p_core.transport uses a type in libp2p_core.transport.upgrade.
- The types involved
libp2p_core.transport.Transport→libp2p_core.transport.upgrade.Builder
- Direction
- libp2p_core.transport uses libp2p_core.transport.upgrade, so a change to libp2p_core.transport.upgrade can break libp2p_core.transport, while a change to libp2p_core.transport can't break libp2p_core.transport.upgrade.
- Position
- Below the diagonal: libp2p_core.transport uses a module listed above it, which is the healthy direction.
23→21 libp2p_autonat.v1.generated.structs.message uses libp2p_autonat.v1.protocol✕
- Connections
- 1 pair of types, where a type in libp2p_autonat.v1.generated.structs.message uses a type in libp2p_autonat.v1.protocol.
- The types involved
libp2p_autonat.v1.generated.structs.message.ResponseStatus→libp2p_autonat.v1.protocol.ResponseError
- Direction
- libp2p_autonat.v1.generated.structs.message uses libp2p_autonat.v1.protocol, so a change to libp2p_autonat.v1.protocol can break libp2p_autonat.v1.generated.structs.message, while a change to libp2p_autonat.v1.generated.structs.message can't break libp2p_autonat.v1.protocol.
- Position
- Below the diagonal: libp2p_autonat.v1.generated.structs.message uses a module listed above it, which is the healthy direction.
24→4 libp2p_core.transport.memory uses libp2p_webrtc.tokio.req_res_chan✕
- Connections
- 2 pairs of types, where a type in libp2p_core.transport.memory uses a type in libp2p_webrtc.tokio.req_res_chan.
- The types involved
libp2p_core.transport.memory.Chan→libp2p_webrtc.tokio.req_res_chan.Receiverlibp2p_core.transport.memory.Chan→libp2p_webrtc.tokio.req_res_chan.Sender
- Direction
- libp2p_core.transport.memory uses libp2p_webrtc.tokio.req_res_chan, so a change to libp2p_webrtc.tokio.req_res_chan can break libp2p_core.transport.memory, while a change to libp2p_core.transport.memory can't break libp2p_webrtc.tokio.req_res_chan.
- Position
- Below the diagonal: libp2p_core.transport.memory uses a module listed above it, which is the healthy direction.
24→7 libp2p_core.transport.memory uses libp2p_core.transport.global_only✕
- Connections
- 1 pair of types, where a type in libp2p_core.transport.memory uses a type in libp2p_core.transport.global_only.
- The types involved
libp2p_core.transport.memory.MemoryTransport→libp2p_core.transport.global_only.Transport
- Direction
- libp2p_core.transport.memory uses libp2p_core.transport.global_only, so a change to libp2p_core.transport.global_only can break libp2p_core.transport.memory, while a change to libp2p_core.transport.memory can't break libp2p_core.transport.global_only.
- Position
- Below the diagonal: libp2p_core.transport.memory uses a module listed above it, which is the healthy direction.
24→10 libp2p_core.transport.memory uses libp2p_webrtc_utils.stream✕
- Connections
- 1 pair of types, where a type in libp2p_core.transport.memory uses a type in libp2p_webrtc_utils.stream.
- The types involved
libp2p_core.transport.memory.Chan→libp2p_webrtc_utils.stream.Stream
- Direction
- libp2p_core.transport.memory uses libp2p_webrtc_utils.stream, so a change to libp2p_webrtc_utils.stream can break libp2p_core.transport.memory, while a change to libp2p_core.transport.memory can't break libp2p_webrtc_utils.stream.
- Position
- Below the diagonal: libp2p_core.transport.memory uses a module listed above it, which is the healthy direction.
24→16 libp2p_core.transport.memory uses prost_codec✕
- Connections
- 1 pair of types, where a type in libp2p_core.transport.memory uses a type in prost_codec.
- The types involved
libp2p_core.transport.memory.MemoryTransportError→prost_codec.Error
- Direction
- libp2p_core.transport.memory uses prost_codec, so a change to prost_codec can break libp2p_core.transport.memory, while a change to libp2p_core.transport.memory can't break prost_codec.
- Position
- Below the diagonal: libp2p_core.transport.memory uses a module listed above it, which is the healthy direction.
24→22 libp2p_core.transport.memory uses libp2p_core.transport✕
- Connections
- 3 pairs of types, where a type in libp2p_core.transport.memory uses a type in libp2p_core.transport.
- The types involved
libp2p_core.transport.memory.Listener→libp2p_core.transport.ListenerIdlibp2p_core.transport.memory.MemoryTransport→libp2p_core.transport.DialOptslibp2p_core.transport.memory.MemoryTransport→libp2p_core.transport.ListenerId
- Direction
- libp2p_core.transport.memory uses libp2p_core.transport, so a change to libp2p_core.transport can break libp2p_core.transport.memory, while a change to libp2p_core.transport.memory can't break libp2p_core.transport.
- Position
- Below the diagonal: libp2p_core.transport.memory uses a module listed above it, which is the healthy direction.
25→8 libp2p_swarm uses libp2p_identity.peer_id✕
- Connections
- 1 pair of types, where a type in libp2p_swarm uses a type in libp2p_identity.peer_id.
- The types involved
libp2p_swarm.Swarm→libp2p_identity.peer_id.PeerId
- Direction
- libp2p_swarm uses libp2p_identity.peer_id, so a change to libp2p_identity.peer_id can break libp2p_swarm, while a change to libp2p_swarm can't break libp2p_identity.peer_id.
- Position
- Below the diagonal: libp2p_swarm uses a module listed above it, which is the healthy direction.
25→10 libp2p_swarm uses libp2p_webrtc_utils.stream✕
- Connections
- 1 pair of types, where a type in libp2p_swarm uses a type in libp2p_webrtc_utils.stream.
- The types involved
libp2p_swarm.Swarm→libp2p_webrtc_utils.stream.Stream
- Direction
- libp2p_swarm uses libp2p_webrtc_utils.stream, so a change to libp2p_webrtc_utils.stream can break libp2p_swarm, while a change to libp2p_swarm can't break libp2p_webrtc_utils.stream.
- Position
- Below the diagonal: libp2p_swarm uses a module listed above it, which is the healthy direction.
25→16 libp2p_swarm uses prost_codec✕
- Connections
- 3 pairs of types, where a type in libp2p_swarm uses a type in prost_codec.
- The types involved
libp2p_swarm.ConnectionDenied→prost_codec.Errorlibp2p_swarm.DialError→prost_codec.Errorlibp2p_swarm.ListenError→prost_codec.Error
- Direction
- libp2p_swarm uses prost_codec, so a change to prost_codec can break libp2p_swarm, while a change to libp2p_swarm can't break prost_codec.
- Position
- Below the diagonal: libp2p_swarm uses a module listed above it, which is the healthy direction.
25→19 libp2p_swarm uses libp2p_mplex.io✕
- Connections
- 1 pair of types, where a type in libp2p_swarm uses a type in libp2p_mplex.io.
- The types involved
libp2p_swarm.Swarm→libp2p_mplex.io.ConnectionId
- Direction
- libp2p_swarm uses libp2p_mplex.io, so a change to libp2p_mplex.io can break libp2p_swarm, while a change to libp2p_swarm can't break libp2p_mplex.io.
- Position
- Below the diagonal: libp2p_swarm uses a module listed above it, which is the healthy direction.
25→22 libp2p_swarm uses libp2p_core.transport✕
- Connections
- 2 pairs of types, where a type in libp2p_swarm uses a type in libp2p_core.transport.
- The types involved
libp2p_swarm.Swarm→libp2p_core.transport.ListenerIdlibp2p_swarm.Swarm→libp2p_core.transport.TransportEvent
- Direction
- libp2p_swarm uses libp2p_core.transport, so a change to libp2p_core.transport can break libp2p_swarm, while a change to libp2p_swarm can't break libp2p_core.transport.
- Position
- Below the diagonal: libp2p_swarm uses a module listed above it, which is the healthy direction.
25→27 libp2p_swarm uses libp2p_swarm.behaviour part of a loop✕
- Connections
- 1 pair of types, where a type in libp2p_swarm uses a type in libp2p_swarm.behaviour.
- The types involved
libp2p_swarm.Swarm→libp2p_swarm.behaviour.ToSwarm
- Direction
- libp2p_swarm uses libp2p_swarm.behaviour, so a change to libp2p_swarm.behaviour can break libp2p_swarm, while a change to libp2p_swarm can't break libp2p_swarm.behaviour.
- 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.
26→2 libp2p_gossipsub.types uses libp2p_gossipsub.topic✕
- Connections
- 6 pairs of types, where a type in libp2p_gossipsub.types uses a type in libp2p_gossipsub.topic.
- The types involved
libp2p_gossipsub.types.Graft→libp2p_gossipsub.topic.TopicHashlibp2p_gossipsub.types.IHave→libp2p_gossipsub.topic.TopicHashlibp2p_gossipsub.types.Message→libp2p_gossipsub.topic.TopicHashlibp2p_gossipsub.types.Prune→libp2p_gossipsub.topic.TopicHashlibp2p_gossipsub.types.RawMessage→libp2p_gossipsub.topic.TopicHashlibp2p_gossipsub.types.Subscription→libp2p_gossipsub.topic.TopicHash
- Direction
- libp2p_gossipsub.types uses libp2p_gossipsub.topic, so a change to libp2p_gossipsub.topic can break libp2p_gossipsub.types, while a change to libp2p_gossipsub.types can't break libp2p_gossipsub.topic.
- Position
- Below the diagonal: libp2p_gossipsub.types uses a module listed above it, which is the healthy direction.
26→8 libp2p_gossipsub.types uses libp2p_identity.peer_id✕
- Connections
- 3 pairs of types, where a type in libp2p_gossipsub.types uses a type in libp2p_identity.peer_id.
- The types involved
libp2p_gossipsub.types.Message→libp2p_identity.peer_id.PeerIdlibp2p_gossipsub.types.PeerInfo→libp2p_identity.peer_id.PeerIdlibp2p_gossipsub.types.RawMessage→libp2p_identity.peer_id.PeerId
- Direction
- libp2p_gossipsub.types uses libp2p_identity.peer_id, so a change to libp2p_identity.peer_id can break libp2p_gossipsub.types, while a change to libp2p_gossipsub.types can't break libp2p_identity.peer_id.
- Position
- Below the diagonal: libp2p_gossipsub.types uses a module listed above it, which is the healthy direction.
26→19 libp2p_gossipsub.types uses libp2p_mplex.io✕
- Connections
- 1 pair of types, where a type in libp2p_gossipsub.types uses a type in libp2p_mplex.io.
- The types involved
libp2p_gossipsub.types.PeerDetails→libp2p_mplex.io.ConnectionId
- Direction
- libp2p_gossipsub.types uses libp2p_mplex.io, so a change to libp2p_mplex.io can break libp2p_gossipsub.types, while a change to libp2p_gossipsub.types can't break libp2p_mplex.io.
- Position
- Below the diagonal: libp2p_gossipsub.types uses a module listed above it, which is the healthy direction.
26→23 libp2p_gossipsub.types uses libp2p_autonat.v1.generated.structs.message✕
- Connections
- 1 pair of types, where a type in libp2p_gossipsub.types uses a type in libp2p_autonat.v1.generated.structs.message.
- The types involved
libp2p_gossipsub.types.Prune→libp2p_autonat.v1.generated.structs.message.PeerInfo
- Direction
- libp2p_gossipsub.types uses libp2p_autonat.v1.generated.structs.message, so a change to libp2p_autonat.v1.generated.structs.message can break libp2p_gossipsub.types, while a change to libp2p_gossipsub.types can't break libp2p_autonat.v1.generated.structs.message.
- Position
- Below the diagonal: libp2p_gossipsub.types uses a module listed above it, which is the healthy direction.
27→1 libp2p_swarm.behaviour uses libp2p_core.connection✕
- Connections
- 4 pairs of types, where a type in libp2p_swarm.behaviour uses a type in libp2p_core.connection.
- The types involved
libp2p_swarm.behaviour.AddressChange→libp2p_core.connection.ConnectedPointlibp2p_swarm.behaviour.ConnectionClosed→libp2p_core.connection.ConnectedPointlibp2p_swarm.behaviour.ConnectionEstablished→libp2p_core.connection.ConnectedPointlibp2p_swarm.behaviour.NetworkBehaviour→libp2p_core.connection.Endpoint
- Direction
- libp2p_swarm.behaviour uses libp2p_core.connection, so a change to libp2p_core.connection can break libp2p_swarm.behaviour, while a change to libp2p_swarm.behaviour can't break libp2p_core.connection.
- Position
- Below the diagonal: libp2p_swarm.behaviour uses a module listed above it, which is the healthy direction.
27→8 libp2p_swarm.behaviour uses libp2p_identity.peer_id✕
- Connections
- 7 pairs of types, where a type in libp2p_swarm.behaviour uses a type in libp2p_identity.peer_id.
- The types involved
libp2p_swarm.behaviour.AddressChange→libp2p_identity.peer_id.PeerIdlibp2p_swarm.behaviour.ConnectionClosed→libp2p_identity.peer_id.PeerIdlibp2p_swarm.behaviour.ConnectionEstablished→libp2p_identity.peer_id.PeerIdlibp2p_swarm.behaviour.DialFailure→libp2p_identity.peer_id.PeerIdlibp2p_swarm.behaviour.ListenFailure→libp2p_identity.peer_id.PeerIdlibp2p_swarm.behaviour.NetworkBehaviour→libp2p_identity.peer_id.PeerIdlibp2p_swarm.behaviour.NewExternalAddrOfPeer→libp2p_identity.peer_id.PeerId
- Direction
- libp2p_swarm.behaviour uses libp2p_identity.peer_id, so a change to libp2p_identity.peer_id can break libp2p_swarm.behaviour, while a change to libp2p_swarm.behaviour can't break libp2p_identity.peer_id.
- Position
- Below the diagonal: libp2p_swarm.behaviour uses a module listed above it, which is the healthy direction.
27→19 libp2p_swarm.behaviour uses libp2p_mplex.io✕
- Connections
- 6 pairs of types, where a type in libp2p_swarm.behaviour uses a type in libp2p_mplex.io.
- The types involved
libp2p_swarm.behaviour.AddressChange→libp2p_mplex.io.ConnectionIdlibp2p_swarm.behaviour.ConnectionClosed→libp2p_mplex.io.ConnectionIdlibp2p_swarm.behaviour.ConnectionEstablished→libp2p_mplex.io.ConnectionIdlibp2p_swarm.behaviour.DialFailure→libp2p_mplex.io.ConnectionIdlibp2p_swarm.behaviour.ListenFailure→libp2p_mplex.io.ConnectionIdlibp2p_swarm.behaviour.NetworkBehaviour→libp2p_mplex.io.ConnectionId
- Direction
- libp2p_swarm.behaviour uses libp2p_mplex.io, so a change to libp2p_mplex.io can break libp2p_swarm.behaviour, while a change to libp2p_swarm.behaviour can't break libp2p_mplex.io.
- Position
- Below the diagonal: libp2p_swarm.behaviour uses a module listed above it, which is the healthy direction.
27→22 libp2p_swarm.behaviour uses libp2p_core.transport✕
- Connections
- 6 pairs of types, where a type in libp2p_swarm.behaviour uses a type in libp2p_core.transport.
- The types involved
libp2p_swarm.behaviour.ExpiredListenAddr→libp2p_core.transport.ListenerIdlibp2p_swarm.behaviour.ListenerClosed→libp2p_core.transport.ListenerIdlibp2p_swarm.behaviour.ListenerError→libp2p_core.transport.ListenerIdlibp2p_swarm.behaviour.NetworkBehaviour→libp2p_core.transport.PortUselibp2p_swarm.behaviour.NewListenAddr→libp2p_core.transport.ListenerIdlibp2p_swarm.behaviour.NewListener→libp2p_core.transport.ListenerId
- Direction
- libp2p_swarm.behaviour uses libp2p_core.transport, so a change to libp2p_core.transport can break libp2p_swarm.behaviour, while a change to libp2p_swarm.behaviour can't break libp2p_core.transport.
- Position
- Below the diagonal: libp2p_swarm.behaviour uses a module listed above it, which is the healthy direction.
27→25 libp2p_swarm.behaviour uses libp2p_swarm✕
- Connections
- 2 pairs of types, where a type in libp2p_swarm.behaviour uses a type in libp2p_swarm.
- The types involved
libp2p_swarm.behaviour.DialFailure→libp2p_swarm.DialErrorlibp2p_swarm.behaviour.ListenFailure→libp2p_swarm.ListenError
- Direction
- libp2p_swarm.behaviour uses libp2p_swarm, so a change to libp2p_swarm can break libp2p_swarm.behaviour, while a change to libp2p_swarm.behaviour can't break libp2p_swarm.
- Position
- Below the diagonal: libp2p_swarm.behaviour uses a module listed above it, which is the healthy direction.
28→1 libp2p_gossipsub.behaviour uses libp2p_core.connection✕
- Connections
- 1 pair of types, where a type in libp2p_gossipsub.behaviour uses a type in libp2p_core.connection.
- The types involved
libp2p_gossipsub.behaviour.Behaviour→libp2p_core.connection.Endpoint
- Direction
- libp2p_gossipsub.behaviour uses libp2p_core.connection, so a change to libp2p_core.connection can break libp2p_gossipsub.behaviour, while a change to libp2p_gossipsub.behaviour can't break libp2p_core.connection.
- Position
- Below the diagonal: libp2p_gossipsub.behaviour uses a module listed above it, which is the healthy direction.
28→2 libp2p_gossipsub.behaviour uses libp2p_gossipsub.topic✕
- Connections
- 2 pairs of types, where a type in libp2p_gossipsub.behaviour uses a type in libp2p_gossipsub.topic.
- The types involved
libp2p_gossipsub.behaviour.Behaviour→libp2p_gossipsub.topic.TopicHashlibp2p_gossipsub.behaviour.behaviour$module→libp2p_gossipsub.topic.TopicHash
- Direction
- libp2p_gossipsub.behaviour uses libp2p_gossipsub.topic, so a change to libp2p_gossipsub.topic can break libp2p_gossipsub.behaviour, while a change to libp2p_gossipsub.behaviour can't break libp2p_gossipsub.topic.
- Position
- Below the diagonal: libp2p_gossipsub.behaviour uses a module listed above it, which is the healthy direction.
28→6 libp2p_gossipsub.behaviour uses multistream_select.dialer_select✕
- Connections
- 1 pair of types, where a type in libp2p_gossipsub.behaviour uses a type in multistream_select.dialer_select.
- The types involved
libp2p_gossipsub.behaviour.Behaviour→multistream_select.dialer_select.State
- Direction
- libp2p_gossipsub.behaviour uses multistream_select.dialer_select, so a change to multistream_select.dialer_select can break libp2p_gossipsub.behaviour, while a change to libp2p_gossipsub.behaviour can't break multistream_select.dialer_select.
- Position
- Below the diagonal: libp2p_gossipsub.behaviour uses a module listed above it, which is the healthy direction.
28→8 libp2p_gossipsub.behaviour uses libp2p_identity.peer_id✕
- Connections
- 3 pairs of types, where a type in libp2p_gossipsub.behaviour uses a type in libp2p_identity.peer_id.
- The types involved
libp2p_gossipsub.behaviour.Behaviour→libp2p_identity.peer_id.PeerIdlibp2p_gossipsub.behaviour.PublishConfig→libp2p_identity.peer_id.PeerIdlibp2p_gossipsub.behaviour.behaviour$module→libp2p_identity.peer_id.PeerId
- Direction
- libp2p_gossipsub.behaviour uses libp2p_identity.peer_id, so a change to libp2p_identity.peer_id can break libp2p_gossipsub.behaviour, while a change to libp2p_gossipsub.behaviour can't break libp2p_identity.peer_id.
- Position
- Below the diagonal: libp2p_gossipsub.behaviour uses a module listed above it, which is the healthy direction.
28→19 libp2p_gossipsub.behaviour uses libp2p_mplex.io✕
- Connections
- 1 pair of types, where a type in libp2p_gossipsub.behaviour uses a type in libp2p_mplex.io.
- The types involved
libp2p_gossipsub.behaviour.Behaviour→libp2p_mplex.io.ConnectionId
- Direction
- libp2p_gossipsub.behaviour uses libp2p_mplex.io, so a change to libp2p_mplex.io can break libp2p_gossipsub.behaviour, while a change to libp2p_gossipsub.behaviour can't break libp2p_mplex.io.
- Position
- Below the diagonal: libp2p_gossipsub.behaviour uses a module listed above it, which is the healthy direction.
28→22 libp2p_gossipsub.behaviour uses libp2p_core.transport✕
- Connections
- 1 pair of types, where a type in libp2p_gossipsub.behaviour uses a type in libp2p_core.transport.
- The types involved
libp2p_gossipsub.behaviour.Behaviour→libp2p_core.transport.PortUse
- Direction
- libp2p_gossipsub.behaviour uses libp2p_core.transport, so a change to libp2p_core.transport can break libp2p_gossipsub.behaviour, while a change to libp2p_gossipsub.behaviour can't break libp2p_core.transport.
- Position
- Below the diagonal: libp2p_gossipsub.behaviour uses a module listed above it, which is the healthy direction.
28→23 libp2p_gossipsub.behaviour uses libp2p_autonat.v1.generated.structs.message✕
- Connections
- 1 pair of types, where a type in libp2p_gossipsub.behaviour uses a type in libp2p_autonat.v1.generated.structs.message.
- The types involved
libp2p_gossipsub.behaviour.Behaviour→libp2p_autonat.v1.generated.structs.message.PeerInfo
- Direction
- libp2p_gossipsub.behaviour uses libp2p_autonat.v1.generated.structs.message, so a change to libp2p_autonat.v1.generated.structs.message can break libp2p_gossipsub.behaviour, while a change to libp2p_gossipsub.behaviour can't break libp2p_autonat.v1.generated.structs.message.
- Position
- Below the diagonal: libp2p_gossipsub.behaviour uses a module listed above it, which is the healthy direction.
28→26 libp2p_gossipsub.behaviour uses libp2p_gossipsub.types✕
- Connections
- 6 pairs of types, where a type in libp2p_gossipsub.behaviour uses a type in libp2p_gossipsub.types.
- The types involved
libp2p_gossipsub.behaviour.Behaviour→libp2p_gossipsub.types.Extensionslibp2p_gossipsub.behaviour.Behaviour→libp2p_gossipsub.types.MessageAcceptancelibp2p_gossipsub.behaviour.Behaviour→libp2p_gossipsub.types.MessageIdlibp2p_gossipsub.behaviour.Behaviour→libp2p_gossipsub.types.Prunelibp2p_gossipsub.behaviour.Behaviour→libp2p_gossipsub.types.RawMessagelibp2p_gossipsub.behaviour.Behaviour→libp2p_gossipsub.types.RpcOut
- Direction
- libp2p_gossipsub.behaviour uses libp2p_gossipsub.types, so a change to libp2p_gossipsub.types can break libp2p_gossipsub.behaviour, while a change to libp2p_gossipsub.behaviour can't break libp2p_gossipsub.types.
- Position
- Below the diagonal: libp2p_gossipsub.behaviour uses a module listed above it, which is the healthy direction.
28→27 libp2p_gossipsub.behaviour uses libp2p_swarm.behaviour✕
- Connections
- 5 pairs of types, where a type in libp2p_gossipsub.behaviour uses a type in libp2p_swarm.behaviour.
- The types involved
libp2p_gossipsub.behaviour.Behaviour→libp2p_swarm.behaviour.AddressChangelibp2p_gossipsub.behaviour.Behaviour→libp2p_swarm.behaviour.ConnectionClosedlibp2p_gossipsub.behaviour.Behaviour→libp2p_swarm.behaviour.ConnectionEstablishedlibp2p_gossipsub.behaviour.Behaviour→libp2p_swarm.behaviour.FromSwarmlibp2p_gossipsub.behaviour.Behaviour→libp2p_swarm.behaviour.NetworkBehaviour
- Direction
- libp2p_gossipsub.behaviour uses libp2p_swarm.behaviour, so a change to libp2p_swarm.behaviour can break libp2p_gossipsub.behaviour, while a change to libp2p_gossipsub.behaviour can't break libp2p_swarm.behaviour.
- Position
- Below the diagonal: libp2p_gossipsub.behaviour uses a module listed above it, which is the healthy direction.
29→2 libp2p_gossipsub.protocol uses libp2p_gossipsub.topic✕
- Connections
- 2 pairs of types, where a type in libp2p_gossipsub.protocol uses a type in libp2p_gossipsub.topic.
- The types involved
libp2p_gossipsub.protocol.GossipsubCodec→libp2p_gossipsub.topic.TopicHashlibp2p_gossipsub.protocol.ProtocolConfig→libp2p_gossipsub.topic.TopicHash
- Direction
- libp2p_gossipsub.protocol uses libp2p_gossipsub.topic, so a change to libp2p_gossipsub.topic can break libp2p_gossipsub.protocol, while a change to libp2p_gossipsub.protocol can't break libp2p_gossipsub.topic.
- Position
- Below the diagonal: libp2p_gossipsub.protocol uses a module listed above it, which is the healthy direction.
29→9 libp2p_gossipsub.protocol uses libp2p_swarm.stream_protocol✕
- Connections
- 1 pair of types, where a type in libp2p_gossipsub.protocol uses a type in libp2p_swarm.stream_protocol.
- The types involved
libp2p_gossipsub.protocol.ProtocolId→libp2p_swarm.stream_protocol.StreamProtocol
- Direction
- libp2p_gossipsub.protocol uses libp2p_swarm.stream_protocol, so a change to libp2p_swarm.stream_protocol can break libp2p_gossipsub.protocol, while a change to libp2p_gossipsub.protocol can't break libp2p_swarm.stream_protocol.
- Position
- Below the diagonal: libp2p_gossipsub.protocol uses a module listed above it, which is the healthy direction.
29→11 libp2p_gossipsub.protocol uses libp2p_identify.protocol✕
- Connections
- 1 pair of types, where a type in libp2p_gossipsub.protocol uses a type in libp2p_identify.protocol.
- The types involved
libp2p_gossipsub.protocol.ProtocolConfig→libp2p_identify.protocol.Info
- Direction
- libp2p_gossipsub.protocol uses libp2p_identify.protocol, so a change to libp2p_identify.protocol can break libp2p_gossipsub.protocol, while a change to libp2p_gossipsub.protocol can't break libp2p_identify.protocol.
- Position
- Below the diagonal: libp2p_gossipsub.protocol uses a module listed above it, which is the healthy direction.
29→13 libp2p_gossipsub.protocol uses libp2p_core.upgrade✕
- Connections
- 3 pairs of types, where a type in libp2p_gossipsub.protocol uses a type in libp2p_core.upgrade.
- The types involved
libp2p_gossipsub.protocol.ProtocolConfig→libp2p_core.upgrade.InboundUpgradelibp2p_gossipsub.protocol.ProtocolConfig→libp2p_core.upgrade.OutboundUpgradelibp2p_gossipsub.protocol.ProtocolConfig→libp2p_core.upgrade.UpgradeInfo
- Direction
- libp2p_gossipsub.protocol uses libp2p_core.upgrade, so a change to libp2p_core.upgrade can break libp2p_gossipsub.protocol, while a change to libp2p_gossipsub.protocol can't break libp2p_core.upgrade.
- Position
- Below the diagonal: libp2p_gossipsub.protocol uses a module listed above it, which is the healthy direction.
29→15 libp2p_gossipsub.protocol uses multistream_select.protocol✕
- Connections
- 1 pair of types, where a type in libp2p_gossipsub.protocol uses a type in multistream_select.protocol.
- The types involved
libp2p_gossipsub.protocol.GossipsubCodec→multistream_select.protocol.Message
- Direction
- libp2p_gossipsub.protocol uses multistream_select.protocol, so a change to multistream_select.protocol can break libp2p_gossipsub.protocol, while a change to libp2p_gossipsub.protocol can't break multistream_select.protocol.
- Position
- Below the diagonal: libp2p_gossipsub.protocol uses a module listed above it, which is the healthy direction.
29→16 libp2p_gossipsub.protocol uses prost_codec✕
- Connections
- 1 pair of types, where a type in libp2p_gossipsub.protocol uses a type in prost_codec.
- The types involved
libp2p_gossipsub.protocol.GossipsubCodec→prost_codec.Codec
- Direction
- libp2p_gossipsub.protocol uses prost_codec, so a change to prost_codec can break libp2p_gossipsub.protocol, while a change to libp2p_gossipsub.protocol can't break prost_codec.
- Position
- Below the diagonal: libp2p_gossipsub.protocol uses a module listed above it, which is the healthy direction.
29→26 libp2p_gossipsub.protocol uses libp2p_gossipsub.types✕
- Connections
- 1 pair of types, where a type in libp2p_gossipsub.protocol uses a type in libp2p_gossipsub.types.
- The types involved
libp2p_gossipsub.protocol.ProtocolId→libp2p_gossipsub.types.PeerKind
- Direction
- libp2p_gossipsub.protocol uses libp2p_gossipsub.types, so a change to libp2p_gossipsub.types can break libp2p_gossipsub.protocol, while a change to libp2p_gossipsub.protocol can't break libp2p_gossipsub.types.
- Position
- Below the diagonal: libp2p_gossipsub.protocol uses a module listed above it, which is the healthy direction.
30→1 libp2p_identify.behaviour uses libp2p_core.connection✕
- Connections
- 1 pair of types, where a type in libp2p_identify.behaviour uses a type in libp2p_core.connection.
- The types involved
libp2p_identify.behaviour.Behaviour→libp2p_core.connection.Endpoint
- Direction
- libp2p_identify.behaviour uses libp2p_core.connection, so a change to libp2p_core.connection can break libp2p_identify.behaviour, while a change to libp2p_identify.behaviour can't break libp2p_core.connection.
- Position
- Below the diagonal: libp2p_identify.behaviour uses a module listed above it, which is the healthy direction.
30→3 libp2p_identify.behaviour uses libp2p_identity.ecdsa✕
- Connections
- 4 pairs of types, where a type in libp2p_identify.behaviour uses a type in libp2p_identity.ecdsa.
- The types involved
libp2p_identify.behaviour.Config→libp2p_identity.ecdsa.Keypairlibp2p_identify.behaviour.Config→libp2p_identity.ecdsa.PublicKeylibp2p_identify.behaviour.KeyType→libp2p_identity.ecdsa.Keypairlibp2p_identify.behaviour.KeyType→libp2p_identity.ecdsa.PublicKey
- Direction
- libp2p_identify.behaviour uses libp2p_identity.ecdsa, so a change to libp2p_identity.ecdsa can break libp2p_identify.behaviour, while a change to libp2p_identify.behaviour can't break libp2p_identity.ecdsa.
- Position
- Below the diagonal: libp2p_identify.behaviour uses a module listed above it, which is the healthy direction.
30→8 libp2p_identify.behaviour uses libp2p_identity.peer_id✕
- Connections
- 3 pairs of types, where a type in libp2p_identify.behaviour uses a type in libp2p_identity.peer_id.
- The types involved
libp2p_identify.behaviour.Behaviour→libp2p_identity.peer_id.PeerIdlibp2p_identify.behaviour.PeerCache→libp2p_identity.peer_id.PeerIdlibp2p_identify.behaviour.behaviour$module→libp2p_identity.peer_id.PeerId
- Direction
- libp2p_identify.behaviour uses libp2p_identity.peer_id, so a change to libp2p_identity.peer_id can break libp2p_identify.behaviour, while a change to libp2p_identify.behaviour can't break libp2p_identity.peer_id.
- Position
- Below the diagonal: libp2p_identify.behaviour uses a module listed above it, which is the healthy direction.
30→15 libp2p_identify.behaviour uses multistream_select.protocol✕
- Connections
- 1 pair of types, where a type in libp2p_identify.behaviour uses a type in multistream_select.protocol.
- The types involved
libp2p_identify.behaviour.behaviour$module→multistream_select.protocol.Protocol
- Direction
- libp2p_identify.behaviour uses multistream_select.protocol, so a change to multistream_select.protocol can break libp2p_identify.behaviour, while a change to libp2p_identify.behaviour can't break multistream_select.protocol.
- Position
- Below the diagonal: libp2p_identify.behaviour uses a module listed above it, which is the healthy direction.
30→19 libp2p_identify.behaviour uses libp2p_mplex.io✕
- Connections
- 2 pairs of types, where a type in libp2p_identify.behaviour uses a type in libp2p_mplex.io.
- The types involved
libp2p_identify.behaviour.Behaviour→libp2p_mplex.io.ConnectionIdlibp2p_identify.behaviour.Event→libp2p_mplex.io.ConnectionId
- Direction
- libp2p_identify.behaviour uses libp2p_mplex.io, so a change to libp2p_mplex.io can break libp2p_identify.behaviour, while a change to libp2p_identify.behaviour can't break libp2p_mplex.io.
- Position
- Below the diagonal: libp2p_identify.behaviour uses a module listed above it, which is the healthy direction.
30→22 libp2p_identify.behaviour uses libp2p_core.transport✕
- Connections
- 1 pair of types, where a type in libp2p_identify.behaviour uses a type in libp2p_core.transport.
- The types involved
libp2p_identify.behaviour.Behaviour→libp2p_core.transport.PortUse
- Direction
- libp2p_identify.behaviour uses libp2p_core.transport, so a change to libp2p_core.transport can break libp2p_identify.behaviour, while a change to libp2p_identify.behaviour can't break libp2p_core.transport.
- Position
- Below the diagonal: libp2p_identify.behaviour uses a module listed above it, which is the healthy direction.
30→27 libp2p_identify.behaviour uses libp2p_swarm.behaviour✕
- Connections
- 3 pairs of types, where a type in libp2p_identify.behaviour uses a type in libp2p_swarm.behaviour.
- The types involved
libp2p_identify.behaviour.Behaviour→libp2p_swarm.behaviour.ConnectionEstablishedlibp2p_identify.behaviour.Behaviour→libp2p_swarm.behaviour.FromSwarmlibp2p_identify.behaviour.Behaviour→libp2p_swarm.behaviour.NetworkBehaviour
- Direction
- libp2p_identify.behaviour uses libp2p_swarm.behaviour, so a change to libp2p_swarm.behaviour can break libp2p_identify.behaviour, while a change to libp2p_identify.behaviour can't break libp2p_swarm.behaviour.
- Position
- Below the diagonal: libp2p_identify.behaviour uses a module listed above it, which is the healthy direction.
31→1 libp2p_mdns.behaviour uses libp2p_core.connection✕
- Connections
- 1 pair of types, where a type in libp2p_mdns.behaviour uses a type in libp2p_core.connection.
- The types involved
libp2p_mdns.behaviour.Behaviour→libp2p_core.connection.Endpoint
- Direction
- libp2p_mdns.behaviour uses libp2p_core.connection, so a change to libp2p_core.connection can break libp2p_mdns.behaviour, while a change to libp2p_mdns.behaviour can't break libp2p_core.connection.
- Position
- Below the diagonal: libp2p_mdns.behaviour uses a module listed above it, which is the healthy direction.
31→4 libp2p_mdns.behaviour uses libp2p_webrtc.tokio.req_res_chan✕
- Connections
- 2 pairs of types, where a type in libp2p_mdns.behaviour uses a type in libp2p_webrtc.tokio.req_res_chan.
- The types involved
libp2p_mdns.behaviour.Behaviour→libp2p_webrtc.tokio.req_res_chan.Receiverlibp2p_mdns.behaviour.Behaviour→libp2p_webrtc.tokio.req_res_chan.Sender
- Direction
- libp2p_mdns.behaviour uses libp2p_webrtc.tokio.req_res_chan, so a change to libp2p_webrtc.tokio.req_res_chan can break libp2p_mdns.behaviour, while a change to libp2p_mdns.behaviour can't break libp2p_webrtc.tokio.req_res_chan.
- Position
- Below the diagonal: libp2p_mdns.behaviour uses a module listed above it, which is the healthy direction.
31→8 libp2p_mdns.behaviour uses libp2p_identity.peer_id✕
- Connections
- 1 pair of types, where a type in libp2p_mdns.behaviour uses a type in libp2p_identity.peer_id.
- The types involved
libp2p_mdns.behaviour.Behaviour→libp2p_identity.peer_id.PeerId
- Direction
- libp2p_mdns.behaviour uses libp2p_identity.peer_id, so a change to libp2p_identity.peer_id can break libp2p_mdns.behaviour, while a change to libp2p_mdns.behaviour can't break libp2p_identity.peer_id.
- Position
- Below the diagonal: libp2p_mdns.behaviour uses a module listed above it, which is the healthy direction.
31→19 libp2p_mdns.behaviour uses libp2p_mplex.io✕
- Connections
- 1 pair of types, where a type in libp2p_mdns.behaviour uses a type in libp2p_mplex.io.
- The types involved
libp2p_mdns.behaviour.Behaviour→libp2p_mplex.io.ConnectionId
- Direction
- libp2p_mdns.behaviour uses libp2p_mplex.io, so a change to libp2p_mplex.io can break libp2p_mdns.behaviour, while a change to libp2p_mdns.behaviour can't break libp2p_mplex.io.
- Position
- Below the diagonal: libp2p_mdns.behaviour uses a module listed above it, which is the healthy direction.
31→22 libp2p_mdns.behaviour uses libp2p_core.transport✕
- Connections
- 1 pair of types, where a type in libp2p_mdns.behaviour uses a type in libp2p_core.transport.
- The types involved
libp2p_mdns.behaviour.Behaviour→libp2p_core.transport.PortUse
- Direction
- libp2p_mdns.behaviour uses libp2p_core.transport, so a change to libp2p_core.transport can break libp2p_mdns.behaviour, while a change to libp2p_mdns.behaviour can't break libp2p_core.transport.
- Position
- Below the diagonal: libp2p_mdns.behaviour uses a module listed above it, which is the healthy direction.
31→27 libp2p_mdns.behaviour uses libp2p_swarm.behaviour✕
- Connections
- 2 pairs of types, where a type in libp2p_mdns.behaviour uses a type in libp2p_swarm.behaviour.
- The types involved
libp2p_mdns.behaviour.Behaviour→libp2p_swarm.behaviour.FromSwarmlibp2p_mdns.behaviour.Behaviour→libp2p_swarm.behaviour.NetworkBehaviour
- Direction
- libp2p_mdns.behaviour uses libp2p_swarm.behaviour, so a change to libp2p_swarm.behaviour can break libp2p_mdns.behaviour, while a change to libp2p_mdns.behaviour can't break libp2p_swarm.behaviour.
- Position
- Below the diagonal: libp2p_mdns.behaviour uses a module listed above it, which is the healthy direction.
32→8 libp2p_peer_store.memory_store uses libp2p_identity.peer_id✕
- Connections
- 1 pair of types, where a type in libp2p_peer_store.memory_store uses a type in libp2p_identity.peer_id.
- The types involved
libp2p_peer_store.memory_store.MemoryStore→libp2p_identity.peer_id.PeerId
- Direction
- libp2p_peer_store.memory_store uses libp2p_identity.peer_id, so a change to libp2p_identity.peer_id can break libp2p_peer_store.memory_store, while a change to libp2p_peer_store.memory_store can't break libp2p_identity.peer_id.
- Position
- Below the diagonal: libp2p_peer_store.memory_store uses a module listed above it, which is the healthy direction.
32→27 libp2p_peer_store.memory_store uses libp2p_swarm.behaviour✕
- Connections
- 1 pair of types, where a type in libp2p_peer_store.memory_store uses a type in libp2p_swarm.behaviour.
- The types involved
libp2p_peer_store.memory_store.MemoryStore→libp2p_swarm.behaviour.FromSwarm
- Direction
- libp2p_peer_store.memory_store uses libp2p_swarm.behaviour, so a change to libp2p_swarm.behaviour can break libp2p_peer_store.memory_store, while a change to libp2p_peer_store.memory_store can't break libp2p_swarm.behaviour.
- Position
- Below the diagonal: libp2p_peer_store.memory_store uses a module listed above it, which is the healthy direction.
33→1 libp2p_relay.priv_client uses libp2p_core.connection✕
- Connections
- 1 pair of types, where a type in libp2p_relay.priv_client uses a type in libp2p_core.connection.
- The types involved
libp2p_relay.priv_client.Behaviour→libp2p_core.connection.Endpoint
- Direction
- libp2p_relay.priv_client uses libp2p_core.connection, so a change to libp2p_core.connection can break libp2p_relay.priv_client, while a change to libp2p_relay.priv_client can't break libp2p_core.connection.
- Position
- Below the diagonal: libp2p_relay.priv_client uses a module listed above it, which is the healthy direction.
33→4 libp2p_relay.priv_client uses libp2p_webrtc.tokio.req_res_chan✕
- Connections
- 1 pair of types, where a type in libp2p_relay.priv_client uses a type in libp2p_webrtc.tokio.req_res_chan.
- The types involved
libp2p_relay.priv_client.Behaviour→libp2p_webrtc.tokio.req_res_chan.Receiver
- Direction
- libp2p_relay.priv_client uses libp2p_webrtc.tokio.req_res_chan, so a change to libp2p_webrtc.tokio.req_res_chan can break libp2p_relay.priv_client, while a change to libp2p_relay.priv_client can't break libp2p_webrtc.tokio.req_res_chan.
- Position
- Below the diagonal: libp2p_relay.priv_client uses a module listed above it, which is the healthy direction.
33→8 libp2p_relay.priv_client uses libp2p_identity.peer_id✕
- Connections
- 2 pairs of types, where a type in libp2p_relay.priv_client uses a type in libp2p_identity.peer_id.
- The types involved
libp2p_relay.priv_client.Behaviour→libp2p_identity.peer_id.PeerIdlibp2p_relay.priv_client.priv_client$module→libp2p_identity.peer_id.PeerId
- Direction
- libp2p_relay.priv_client uses libp2p_identity.peer_id, so a change to libp2p_identity.peer_id can break libp2p_relay.priv_client, while a change to libp2p_relay.priv_client can't break libp2p_identity.peer_id.
- Position
- Below the diagonal: libp2p_relay.priv_client uses a module listed above it, which is the healthy direction.
33→10 libp2p_relay.priv_client uses libp2p_webrtc_utils.stream✕
- Connections
- 1 pair of types, where a type in libp2p_relay.priv_client uses a type in libp2p_webrtc_utils.stream.
- The types involved
libp2p_relay.priv_client.ConnectionState→libp2p_webrtc_utils.stream.Stream
- Direction
- libp2p_relay.priv_client uses libp2p_webrtc_utils.stream, so a change to libp2p_webrtc_utils.stream can break libp2p_relay.priv_client, while a change to libp2p_relay.priv_client can't break libp2p_webrtc_utils.stream.
- Position
- Below the diagonal: libp2p_relay.priv_client uses a module listed above it, which is the healthy direction.
33→19 libp2p_relay.priv_client uses libp2p_mplex.io✕
- Connections
- 1 pair of types, where a type in libp2p_relay.priv_client uses a type in libp2p_mplex.io.
- The types involved
libp2p_relay.priv_client.Behaviour→libp2p_mplex.io.ConnectionId
- Direction
- libp2p_relay.priv_client uses libp2p_mplex.io, so a change to libp2p_mplex.io can break libp2p_relay.priv_client, while a change to libp2p_relay.priv_client can't break libp2p_mplex.io.
- Position
- Below the diagonal: libp2p_relay.priv_client uses a module listed above it, which is the healthy direction.
33→22 libp2p_relay.priv_client uses libp2p_core.transport✕
- Connections
- 1 pair of types, where a type in libp2p_relay.priv_client uses a type in libp2p_core.transport.
- The types involved
libp2p_relay.priv_client.Behaviour→libp2p_core.transport.PortUse
- Direction
- libp2p_relay.priv_client uses libp2p_core.transport, so a change to libp2p_core.transport can break libp2p_relay.priv_client, while a change to libp2p_relay.priv_client can't break libp2p_core.transport.
- Position
- Below the diagonal: libp2p_relay.priv_client uses a module listed above it, which is the healthy direction.
33→27 libp2p_relay.priv_client uses libp2p_swarm.behaviour✕
- Connections
- 4 pairs of types, where a type in libp2p_relay.priv_client uses a type in libp2p_swarm.behaviour.
- The types involved
libp2p_relay.priv_client.Behaviour→libp2p_swarm.behaviour.ConnectionClosedlibp2p_relay.priv_client.Behaviour→libp2p_swarm.behaviour.FromSwarmlibp2p_relay.priv_client.Behaviour→libp2p_swarm.behaviour.ListenerClosedlibp2p_relay.priv_client.Behaviour→libp2p_swarm.behaviour.NetworkBehaviour
- Direction
- libp2p_relay.priv_client uses libp2p_swarm.behaviour, so a change to libp2p_swarm.behaviour can break libp2p_relay.priv_client, while a change to libp2p_relay.priv_client can't break libp2p_swarm.behaviour.
- Position
- Below the diagonal: libp2p_relay.priv_client uses a module listed above it, which is the healthy direction.
34→1 libp2p_swarm.dummy uses libp2p_core.connection✕
- Connections
- 1 pair of types, where a type in libp2p_swarm.dummy uses a type in libp2p_core.connection.
- The types involved
libp2p_swarm.dummy.Behaviour→libp2p_core.connection.Endpoint
- Direction
- libp2p_swarm.dummy uses libp2p_core.connection, so a change to libp2p_core.connection can break libp2p_swarm.dummy, while a change to libp2p_swarm.dummy can't break libp2p_core.connection.
- Position
- Below the diagonal: libp2p_swarm.dummy uses a module listed above it, which is the healthy direction.
34→8 libp2p_swarm.dummy uses libp2p_identity.peer_id✕
- Connections
- 1 pair of types, where a type in libp2p_swarm.dummy uses a type in libp2p_identity.peer_id.
- The types involved
libp2p_swarm.dummy.Behaviour→libp2p_identity.peer_id.PeerId
- Direction
- libp2p_swarm.dummy uses libp2p_identity.peer_id, so a change to libp2p_identity.peer_id can break libp2p_swarm.dummy, while a change to libp2p_swarm.dummy can't break libp2p_identity.peer_id.
- Position
- Below the diagonal: libp2p_swarm.dummy uses a module listed above it, which is the healthy direction.
34→19 libp2p_swarm.dummy uses libp2p_mplex.io✕
- Connections
- 1 pair of types, where a type in libp2p_swarm.dummy uses a type in libp2p_mplex.io.
- The types involved
libp2p_swarm.dummy.Behaviour→libp2p_mplex.io.ConnectionId
- Direction
- libp2p_swarm.dummy uses libp2p_mplex.io, so a change to libp2p_mplex.io can break libp2p_swarm.dummy, while a change to libp2p_swarm.dummy can't break libp2p_mplex.io.
- Position
- Below the diagonal: libp2p_swarm.dummy uses a module listed above it, which is the healthy direction.
34→20 libp2p_swarm.dummy uses libp2p_swarm.handler✕
- Connections
- 2 pairs of types, where a type in libp2p_swarm.dummy uses a type in libp2p_swarm.handler.
- The types involved
libp2p_swarm.dummy.ConnectionHandler→libp2p_swarm.handler.ConnectionEventlibp2p_swarm.dummy.ConnectionHandler→libp2p_swarm.handler.SubstreamProtocol
- Direction
- libp2p_swarm.dummy uses libp2p_swarm.handler, so a change to libp2p_swarm.handler can break libp2p_swarm.dummy, while a change to libp2p_swarm.dummy can't break libp2p_swarm.handler.
- Position
- Below the diagonal: libp2p_swarm.dummy uses a module listed above it, which is the healthy direction.
34→22 libp2p_swarm.dummy uses libp2p_core.transport✕
- Connections
- 1 pair of types, where a type in libp2p_swarm.dummy uses a type in libp2p_core.transport.
- The types involved
libp2p_swarm.dummy.Behaviour→libp2p_core.transport.PortUse
- Direction
- libp2p_swarm.dummy uses libp2p_core.transport, so a change to libp2p_core.transport can break libp2p_swarm.dummy, while a change to libp2p_swarm.dummy can't break libp2p_core.transport.
- Position
- Below the diagonal: libp2p_swarm.dummy uses a module listed above it, which is the healthy direction.
34→27 libp2p_swarm.dummy uses libp2p_swarm.behaviour✕
- Connections
- 2 pairs of types, where a type in libp2p_swarm.dummy uses a type in libp2p_swarm.behaviour.
- The types involved
libp2p_swarm.dummy.Behaviour→libp2p_swarm.behaviour.FromSwarmlibp2p_swarm.dummy.Behaviour→libp2p_swarm.behaviour.NetworkBehaviour
- Direction
- libp2p_swarm.dummy uses libp2p_swarm.behaviour, so a change to libp2p_swarm.behaviour can break libp2p_swarm.dummy, while a change to libp2p_swarm.dummy can't break libp2p_swarm.behaviour.
- Position
- Below the diagonal: libp2p_swarm.dummy uses a module listed above it, which is the healthy direction.
35→1 libp2p_autonat.v1.behaviour uses libp2p_core.connection✕
- Connections
- 1 pair of types, where a type in libp2p_autonat.v1.behaviour uses a type in libp2p_core.connection.
- The types involved
libp2p_autonat.v1.behaviour.Behaviour→libp2p_core.connection.Endpoint
- Direction
- libp2p_autonat.v1.behaviour uses libp2p_core.connection, so a change to libp2p_core.connection can break libp2p_autonat.v1.behaviour, while a change to libp2p_autonat.v1.behaviour can't break libp2p_core.connection.
- Position
- Below the diagonal: libp2p_autonat.v1.behaviour uses a module listed above it, which is the healthy direction.
35→8 libp2p_autonat.v1.behaviour uses libp2p_identity.peer_id✕
- Connections
- 1 pair of types, where a type in libp2p_autonat.v1.behaviour uses a type in libp2p_identity.peer_id.
- The types involved
libp2p_autonat.v1.behaviour.Behaviour→libp2p_identity.peer_id.PeerId
- Direction
- libp2p_autonat.v1.behaviour uses libp2p_identity.peer_id, so a change to libp2p_identity.peer_id can break libp2p_autonat.v1.behaviour, while a change to libp2p_autonat.v1.behaviour can't break libp2p_identity.peer_id.
- Position
- Below the diagonal: libp2p_autonat.v1.behaviour uses a module listed above it, which is the healthy direction.
35→19 libp2p_autonat.v1.behaviour uses libp2p_mplex.io✕
- Connections
- 1 pair of types, where a type in libp2p_autonat.v1.behaviour uses a type in libp2p_mplex.io.
- The types involved
libp2p_autonat.v1.behaviour.Behaviour→libp2p_mplex.io.ConnectionId
- Direction
- libp2p_autonat.v1.behaviour uses libp2p_mplex.io, so a change to libp2p_mplex.io can break libp2p_autonat.v1.behaviour, while a change to libp2p_autonat.v1.behaviour can't break libp2p_mplex.io.
- Position
- Below the diagonal: libp2p_autonat.v1.behaviour uses a module listed above it, which is the healthy direction.
35→22 libp2p_autonat.v1.behaviour uses libp2p_core.transport✕
- Connections
- 1 pair of types, where a type in libp2p_autonat.v1.behaviour uses a type in libp2p_core.transport.
- The types involved
libp2p_autonat.v1.behaviour.Behaviour→libp2p_core.transport.PortUse
- Direction
- libp2p_autonat.v1.behaviour uses libp2p_core.transport, so a change to libp2p_core.transport can break libp2p_autonat.v1.behaviour, while a change to libp2p_autonat.v1.behaviour can't break libp2p_core.transport.
- Position
- Below the diagonal: libp2p_autonat.v1.behaviour uses a module listed above it, which is the healthy direction.
35→27 libp2p_autonat.v1.behaviour uses libp2p_swarm.behaviour✕
- Connections
- 6 pairs of types, where a type in libp2p_autonat.v1.behaviour uses a type in libp2p_swarm.behaviour.
- The types involved
libp2p_autonat.v1.behaviour.Behaviour→libp2p_swarm.behaviour.AddressChangelibp2p_autonat.v1.behaviour.Behaviour→libp2p_swarm.behaviour.ConnectionClosedlibp2p_autonat.v1.behaviour.Behaviour→libp2p_swarm.behaviour.ConnectionEstablishedlibp2p_autonat.v1.behaviour.Behaviour→libp2p_swarm.behaviour.DialFailurelibp2p_autonat.v1.behaviour.Behaviour→libp2p_swarm.behaviour.FromSwarmlibp2p_autonat.v1.behaviour.Behaviour→libp2p_swarm.behaviour.NetworkBehaviour
- Direction
- libp2p_autonat.v1.behaviour uses libp2p_swarm.behaviour, so a change to libp2p_swarm.behaviour can break libp2p_autonat.v1.behaviour, while a change to libp2p_autonat.v1.behaviour can't break libp2p_swarm.behaviour.
- Position
- Below the diagonal: libp2p_autonat.v1.behaviour uses a module listed above it, which is the healthy direction.
35→32 libp2p_autonat.v1.behaviour uses libp2p_peer_store.memory_store✕
- Connections
- 1 pair of types, where a type in libp2p_autonat.v1.behaviour uses a type in libp2p_peer_store.memory_store.
- The types involved
libp2p_autonat.v1.behaviour.HandleInnerEvent→libp2p_peer_store.memory_store.Event
- Direction
- libp2p_autonat.v1.behaviour uses libp2p_peer_store.memory_store, so a change to libp2p_peer_store.memory_store can break libp2p_autonat.v1.behaviour, while a change to libp2p_autonat.v1.behaviour can't break libp2p_peer_store.memory_store.
- Position
- Below the diagonal: libp2p_autonat.v1.behaviour uses a module listed above it, which is the healthy direction.
36→1 libp2p_kad.handler uses libp2p_core.connection✕
- Connections
- 1 pair of types, where a type in libp2p_kad.handler uses a type in libp2p_core.connection.
- The types involved
libp2p_kad.handler.Handler→libp2p_core.connection.ConnectedPoint
- Direction
- libp2p_kad.handler uses libp2p_core.connection, so a change to libp2p_core.connection can break libp2p_kad.handler, while a change to libp2p_kad.handler can't break libp2p_core.connection.
- Position
- Below the diagonal: libp2p_kad.handler uses a module listed above it, which is the healthy direction.
36→8 libp2p_kad.handler uses libp2p_identity.peer_id✕
- Connections
- 1 pair of types, where a type in libp2p_kad.handler uses a type in libp2p_identity.peer_id.
- The types involved
libp2p_kad.handler.Handler→libp2p_identity.peer_id.PeerId
- Direction
- libp2p_kad.handler uses libp2p_identity.peer_id, so a change to libp2p_identity.peer_id can break libp2p_kad.handler, while a change to libp2p_kad.handler can't break libp2p_identity.peer_id.
- Position
- Below the diagonal: libp2p_kad.handler uses a module listed above it, which is the healthy direction.
36→10 libp2p_kad.handler uses libp2p_webrtc_utils.stream✕
- Connections
- 1 pair of types, where a type in libp2p_kad.handler uses a type in libp2p_webrtc_utils.stream.
- The types involved
libp2p_kad.handler.InboundSubstreamState→libp2p_webrtc_utils.stream.Stream
- Direction
- libp2p_kad.handler uses libp2p_webrtc_utils.stream, so a change to libp2p_webrtc_utils.stream can break libp2p_kad.handler, while a change to libp2p_kad.handler can't break libp2p_webrtc_utils.stream.
- Position
- Below the diagonal: libp2p_kad.handler uses a module listed above it, which is the healthy direction.
36→14 libp2p_kad.handler uses libp2p_kad.protocol✕
- Connections
- 4 pairs of types, where a type in libp2p_kad.handler uses a type in libp2p_kad.protocol.
- The types involved
libp2p_kad.handler.Handler→libp2p_kad.protocol.KadRequestMsglibp2p_kad.handler.Handler→libp2p_kad.protocol.KadResponseMsglibp2p_kad.handler.InboundSubstreamState→libp2p_kad.protocol.KadResponseMsglibp2p_kad.handler.handler$module→libp2p_kad.protocol.KadResponseMsg
- Direction
- libp2p_kad.handler uses libp2p_kad.protocol, so a change to libp2p_kad.protocol can break libp2p_kad.handler, while a change to libp2p_kad.handler can't break libp2p_kad.protocol.
- Position
- Below the diagonal: libp2p_kad.handler uses a module listed above it, which is the healthy direction.
36→16 libp2p_kad.handler uses prost_codec✕
- Connections
- 1 pair of types, where a type in libp2p_kad.handler uses a type in prost_codec.
- The types involved
libp2p_kad.handler.HandlerQueryErr→prost_codec.Error
- Direction
- libp2p_kad.handler uses prost_codec, so a change to prost_codec can break libp2p_kad.handler, while a change to libp2p_kad.handler can't break prost_codec.
- Position
- Below the diagonal: libp2p_kad.handler uses a module listed above it, which is the healthy direction.
36→20 libp2p_kad.handler uses libp2p_swarm.handler✕
- Connections
- 4 pairs of types, where a type in libp2p_kad.handler uses a type in libp2p_swarm.handler.
- The types involved
libp2p_kad.handler.Handler→libp2p_swarm.handler.ConnectionEventlibp2p_kad.handler.Handler→libp2p_swarm.handler.FullyNegotiatedInboundlibp2p_kad.handler.Handler→libp2p_swarm.handler.FullyNegotiatedOutboundlibp2p_kad.handler.Handler→libp2p_swarm.handler.SubstreamProtocol
- Direction
- libp2p_kad.handler uses libp2p_swarm.handler, so a change to libp2p_swarm.handler can break libp2p_kad.handler, while a change to libp2p_kad.handler can't break libp2p_swarm.handler.
- Position
- Below the diagonal: libp2p_kad.handler uses a module listed above it, which is the healthy direction.
36→29 libp2p_kad.handler uses libp2p_gossipsub.protocol✕
- Connections
- 1 pair of types, where a type in libp2p_kad.handler uses a type in libp2p_gossipsub.protocol.
- The types involved
libp2p_kad.handler.Handler→libp2p_gossipsub.protocol.ProtocolConfig
- Direction
- libp2p_kad.handler uses libp2p_gossipsub.protocol, so a change to libp2p_gossipsub.protocol can break libp2p_kad.handler, while a change to libp2p_kad.handler can't break libp2p_gossipsub.protocol.
- Position
- Below the diagonal: libp2p_kad.handler uses a module listed above it, which is the healthy direction.
36→34 libp2p_kad.handler uses libp2p_swarm.dummy✕
- Connections
- 1 pair of types, where a type in libp2p_kad.handler uses a type in libp2p_swarm.dummy.
- The types involved
libp2p_kad.handler.Handler→libp2p_swarm.dummy.ConnectionHandler
- Direction
- libp2p_kad.handler uses libp2p_swarm.dummy, so a change to libp2p_swarm.dummy can break libp2p_kad.handler, while a change to libp2p_kad.handler can't break libp2p_swarm.dummy.
- Position
- Below the diagonal: libp2p_kad.handler uses a module listed above it, which is the healthy direction.
37→25 libp2p_metrics uses libp2p_swarm✕
- Connections
- 1 pair of types, where a type in libp2p_metrics uses a type in libp2p_swarm.
- The types involved
libp2p_metrics.Metrics→libp2p_swarm.SwarmEvent
- Direction
- libp2p_metrics uses libp2p_swarm, so a change to libp2p_swarm can break libp2p_metrics, while a change to libp2p_metrics can't break libp2p_swarm.
- Position
- Below the diagonal: libp2p_metrics uses a module listed above it, which is the healthy direction.
37→32 libp2p_metrics uses libp2p_peer_store.memory_store✕
- Connections
- 2 pairs of types, where a type in libp2p_metrics uses a type in libp2p_peer_store.memory_store.
- The types involved
libp2p_metrics.Metrics→libp2p_peer_store.memory_store.Eventlibp2p_metrics.Recorder→libp2p_peer_store.memory_store.Event
- Direction
- libp2p_metrics uses libp2p_peer_store.memory_store, so a change to libp2p_peer_store.memory_store can break libp2p_metrics, while a change to libp2p_metrics can't break libp2p_peer_store.memory_store.
- Position
- Below the diagonal: libp2p_metrics uses a module listed above it, which is the healthy direction.
38→1 libp2p_request_response uses libp2p_core.connection✕
- Connections
- 1 pair of types, where a type in libp2p_request_response uses a type in libp2p_core.connection.
- The types involved
libp2p_request_response.Behaviour→libp2p_core.connection.Endpoint
- Direction
- libp2p_request_response uses libp2p_core.connection, so a change to libp2p_core.connection can break libp2p_request_response, while a change to libp2p_request_response can't break libp2p_core.connection.
- Position
- Below the diagonal: libp2p_request_response uses a module listed above it, which is the healthy direction.
38→4 libp2p_request_response uses libp2p_webrtc.tokio.req_res_chan✕
- Connections
- 1 pair of types, where a type in libp2p_request_response uses a type in libp2p_webrtc.tokio.req_res_chan.
- The types involved
libp2p_request_response.ResponseChannel→libp2p_webrtc.tokio.req_res_chan.Sender
- Direction
- libp2p_request_response uses libp2p_webrtc.tokio.req_res_chan, so a change to libp2p_webrtc.tokio.req_res_chan can break libp2p_request_response, while a change to libp2p_request_response can't break libp2p_webrtc.tokio.req_res_chan.
- Position
- Below the diagonal: libp2p_request_response uses a module listed above it, which is the healthy direction.
38→8 libp2p_request_response uses libp2p_identity.peer_id✕
- Connections
- 1 pair of types, where a type in libp2p_request_response uses a type in libp2p_identity.peer_id.
- The types involved
libp2p_request_response.Behaviour→libp2p_identity.peer_id.PeerId
- Direction
- libp2p_request_response uses libp2p_identity.peer_id, so a change to libp2p_identity.peer_id can break libp2p_request_response, while a change to libp2p_request_response can't break libp2p_identity.peer_id.
- Position
- Below the diagonal: libp2p_request_response uses a module listed above it, which is the healthy direction.
38→16 libp2p_request_response uses prost_codec✕
- Connections
- 2 pairs of types, where a type in libp2p_request_response uses a type in prost_codec.
- The types involved
libp2p_request_response.InboundFailure→prost_codec.Errorlibp2p_request_response.OutboundFailure→prost_codec.Error
- Direction
- libp2p_request_response uses prost_codec, so a change to prost_codec can break libp2p_request_response, while a change to libp2p_request_response can't break prost_codec.
- Position
- Below the diagonal: libp2p_request_response uses a module listed above it, which is the healthy direction.
38→17 libp2p_request_response uses libp2p_autonat.v2.protocol✕
- Connections
- 1 pair of types, where a type in libp2p_request_response uses a type in libp2p_autonat.v2.protocol.
- The types involved
libp2p_request_response.Behaviour→libp2p_autonat.v2.protocol.Response
- Direction
- libp2p_request_response uses libp2p_autonat.v2.protocol, so a change to libp2p_autonat.v2.protocol can break libp2p_request_response, while a change to libp2p_request_response can't break libp2p_autonat.v2.protocol.
- Position
- Below the diagonal: libp2p_request_response uses a module listed above it, which is the healthy direction.
38→19 libp2p_request_response uses libp2p_mplex.io✕
- Connections
- 2 pairs of types, where a type in libp2p_request_response uses a type in libp2p_mplex.io.
- The types involved
libp2p_request_response.Behaviour→libp2p_mplex.io.ConnectionIdlibp2p_request_response.Connection→libp2p_mplex.io.ConnectionId
- Direction
- libp2p_request_response uses libp2p_mplex.io, so a change to libp2p_mplex.io can break libp2p_request_response, while a change to libp2p_request_response can't break libp2p_mplex.io.
- Position
- Below the diagonal: libp2p_request_response uses a module listed above it, which is the healthy direction.
38→22 libp2p_request_response uses libp2p_core.transport✕
- Connections
- 1 pair of types, where a type in libp2p_request_response uses a type in libp2p_core.transport.
- The types involved
libp2p_request_response.Behaviour→libp2p_core.transport.PortUse
- Direction
- libp2p_request_response uses libp2p_core.transport, so a change to libp2p_core.transport can break libp2p_request_response, while a change to libp2p_request_response can't break libp2p_core.transport.
- Position
- Below the diagonal: libp2p_request_response uses a module listed above it, which is the healthy direction.
38→27 libp2p_request_response uses libp2p_swarm.behaviour✕
- Connections
- 5 pairs of types, where a type in libp2p_request_response uses a type in libp2p_swarm.behaviour.
- The types involved
libp2p_request_response.Behaviour→libp2p_swarm.behaviour.AddressChangelibp2p_request_response.Behaviour→libp2p_swarm.behaviour.ConnectionClosedlibp2p_request_response.Behaviour→libp2p_swarm.behaviour.DialFailurelibp2p_request_response.Behaviour→libp2p_swarm.behaviour.FromSwarmlibp2p_request_response.Behaviour→libp2p_swarm.behaviour.NetworkBehaviour
- Direction
- libp2p_request_response uses libp2p_swarm.behaviour, so a change to libp2p_swarm.behaviour can break libp2p_request_response, while a change to libp2p_request_response can't break libp2p_swarm.behaviour.
- Position
- Below the diagonal: libp2p_request_response uses a module listed above it, which is the healthy direction.
38→33 libp2p_request_response uses libp2p_relay.priv_client✕
- Connections
- 1 pair of types, where a type in libp2p_request_response uses a type in libp2p_relay.priv_client.
- The types involved
libp2p_request_response.Behaviour→libp2p_relay.priv_client.Connection
- Direction
- libp2p_request_response uses libp2p_relay.priv_client, so a change to libp2p_relay.priv_client can break libp2p_request_response, while a change to libp2p_request_response can't break libp2p_relay.priv_client.
- Position
- Below the diagonal: libp2p_request_response uses a module listed above it, which is the healthy direction.
39→1 libp2p_kad.behaviour uses libp2p_core.connection✕
- Connections
- 1 pair of types, where a type in libp2p_kad.behaviour uses a type in libp2p_core.connection.
- The types involved
libp2p_kad.behaviour.Behaviour→libp2p_core.connection.Endpoint
- Direction
- libp2p_kad.behaviour uses libp2p_core.connection, so a change to libp2p_core.connection can break libp2p_kad.behaviour, while a change to libp2p_kad.behaviour can't break libp2p_core.connection.
- Position
- Below the diagonal: libp2p_kad.behaviour uses a module listed above it, which is the healthy direction.
39→8 libp2p_kad.behaviour uses libp2p_identity.peer_id✕
- Connections
- 4 pairs of types, where a type in libp2p_kad.behaviour uses a type in libp2p_identity.peer_id.
- The types involved
libp2p_kad.behaviour.Behaviour→libp2p_identity.peer_id.PeerIdlibp2p_kad.behaviour.BootstrapOk→libp2p_identity.peer_id.PeerIdlibp2p_kad.behaviour.PeerInfo→libp2p_identity.peer_id.PeerIdlibp2p_kad.behaviour.PeerRecord→libp2p_identity.peer_id.PeerId
- Direction
- libp2p_kad.behaviour uses libp2p_identity.peer_id, so a change to libp2p_identity.peer_id can break libp2p_kad.behaviour, while a change to libp2p_kad.behaviour can't break libp2p_identity.peer_id.
- Position
- Below the diagonal: libp2p_kad.behaviour uses a module listed above it, which is the healthy direction.
39→9 libp2p_kad.behaviour uses libp2p_swarm.stream_protocol✕
- Connections
- 1 pair of types, where a type in libp2p_kad.behaviour uses a type in libp2p_swarm.stream_protocol.
- The types involved
libp2p_kad.behaviour.Config→libp2p_swarm.stream_protocol.StreamProtocol
- Direction
- libp2p_kad.behaviour uses libp2p_swarm.stream_protocol, so a change to libp2p_swarm.stream_protocol can break libp2p_kad.behaviour, while a change to libp2p_kad.behaviour can't break libp2p_swarm.stream_protocol.
- Position
- Below the diagonal: libp2p_kad.behaviour uses a module listed above it, which is the healthy direction.
39→12 libp2p_kad.behaviour uses libp2p_kad.kbucket.key✕
- Connections
- 7 pairs of types, where a type in libp2p_kad.behaviour uses a type in libp2p_kad.kbucket.key.
- The types involved
libp2p_kad.behaviour.AddProviderError→libp2p_kad.kbucket.key.Keylibp2p_kad.behaviour.AddProviderOk→libp2p_kad.kbucket.key.Keylibp2p_kad.behaviour.Behaviour→libp2p_kad.kbucket.key.Keylibp2p_kad.behaviour.GetProvidersError→libp2p_kad.kbucket.key.Keylibp2p_kad.behaviour.GetRecordError→libp2p_kad.kbucket.key.Keylibp2p_kad.behaviour.PutRecordError→libp2p_kad.kbucket.key.Keylibp2p_kad.behaviour.PutRecordOk→libp2p_kad.kbucket.key.Key
- Direction
- libp2p_kad.behaviour uses libp2p_kad.kbucket.key, so a change to libp2p_kad.kbucket.key can break libp2p_kad.behaviour, while a change to libp2p_kad.behaviour can't break libp2p_kad.kbucket.key.
- Position
- Below the diagonal: libp2p_kad.behaviour uses a module listed above it, which is the healthy direction.
39→14 libp2p_kad.behaviour uses libp2p_kad.protocol✕
- Connections
- 1 pair of types, where a type in libp2p_kad.behaviour uses a type in libp2p_kad.protocol.
- The types involved
libp2p_kad.behaviour.Behaviour→libp2p_kad.protocol.KadPeer
- Direction
- libp2p_kad.behaviour uses libp2p_kad.protocol, so a change to libp2p_kad.protocol can break libp2p_kad.behaviour, while a change to libp2p_kad.behaviour can't break libp2p_kad.protocol.
- Position
- Below the diagonal: libp2p_kad.behaviour uses a module listed above it, which is the healthy direction.
39→16 libp2p_kad.behaviour uses prost_codec✕
- Connections
- 1 pair of types, where a type in libp2p_kad.behaviour uses a type in prost_codec.
- The types involved
libp2p_kad.behaviour.NoKnownPeers→prost_codec.Error
- Direction
- libp2p_kad.behaviour uses prost_codec, so a change to prost_codec can break libp2p_kad.behaviour, while a change to libp2p_kad.behaviour can't break prost_codec.
- Position
- Below the diagonal: libp2p_kad.behaviour uses a module listed above it, which is the healthy direction.
39→19 libp2p_kad.behaviour uses libp2p_mplex.io✕
- Connections
- 2 pairs of types, where a type in libp2p_kad.behaviour uses a type in libp2p_mplex.io.
- The types involved
libp2p_kad.behaviour.Behaviour→libp2p_mplex.io.ConnectionIdlibp2p_kad.behaviour.Behaviour→libp2p_mplex.io.Status
- Direction
- libp2p_kad.behaviour uses libp2p_mplex.io, so a change to libp2p_mplex.io can break libp2p_kad.behaviour, while a change to libp2p_kad.behaviour can't break libp2p_mplex.io.
- Position
- Below the diagonal: libp2p_kad.behaviour uses a module listed above it, which is the healthy direction.
39→22 libp2p_kad.behaviour uses libp2p_core.transport✕
- Connections
- 1 pair of types, where a type in libp2p_kad.behaviour uses a type in libp2p_core.transport.
- The types involved
libp2p_kad.behaviour.Behaviour→libp2p_core.transport.PortUse
- Direction
- libp2p_kad.behaviour uses libp2p_core.transport, so a change to libp2p_core.transport can break libp2p_kad.behaviour, while a change to libp2p_kad.behaviour can't break libp2p_core.transport.
- Position
- Below the diagonal: libp2p_kad.behaviour uses a module listed above it, which is the healthy direction.
39→23 libp2p_kad.behaviour uses libp2p_autonat.v1.generated.structs.message✕
- Connections
- 1 pair of types, where a type in libp2p_kad.behaviour uses a type in libp2p_autonat.v1.generated.structs.message.
- The types involved
libp2p_kad.behaviour.GetClosestPeersOk→libp2p_autonat.v1.generated.structs.message.PeerInfo
- Direction
- libp2p_kad.behaviour uses libp2p_autonat.v1.generated.structs.message, so a change to libp2p_autonat.v1.generated.structs.message can break libp2p_kad.behaviour, while a change to libp2p_kad.behaviour can't break libp2p_autonat.v1.generated.structs.message.
- Position
- Below the diagonal: libp2p_kad.behaviour uses a module listed above it, which is the healthy direction.
39→27 libp2p_kad.behaviour uses libp2p_swarm.behaviour✕
- Connections
- 6 pairs of types, where a type in libp2p_kad.behaviour uses a type in libp2p_swarm.behaviour.
- The types involved
libp2p_kad.behaviour.Behaviour→libp2p_swarm.behaviour.AddressChangelibp2p_kad.behaviour.Behaviour→libp2p_swarm.behaviour.ConnectionClosedlibp2p_kad.behaviour.Behaviour→libp2p_swarm.behaviour.ConnectionEstablishedlibp2p_kad.behaviour.Behaviour→libp2p_swarm.behaviour.DialFailurelibp2p_kad.behaviour.Behaviour→libp2p_swarm.behaviour.FromSwarmlibp2p_kad.behaviour.Behaviour→libp2p_swarm.behaviour.NetworkBehaviour
- Direction
- libp2p_kad.behaviour uses libp2p_swarm.behaviour, so a change to libp2p_swarm.behaviour can break libp2p_kad.behaviour, while a change to libp2p_kad.behaviour can't break libp2p_swarm.behaviour.
- Position
- Below the diagonal: libp2p_kad.behaviour uses a module listed above it, which is the healthy direction.
39→29 libp2p_kad.behaviour uses libp2p_gossipsub.protocol✕
- Connections
- 2 pairs of types, where a type in libp2p_kad.behaviour uses a type in libp2p_gossipsub.protocol.
- The types involved
libp2p_kad.behaviour.Behaviour→libp2p_gossipsub.protocol.ProtocolConfiglibp2p_kad.behaviour.Config→libp2p_gossipsub.protocol.ProtocolConfig
- Direction
- libp2p_kad.behaviour uses libp2p_gossipsub.protocol, so a change to libp2p_gossipsub.protocol can break libp2p_kad.behaviour, while a change to libp2p_kad.behaviour can't break libp2p_gossipsub.protocol.
- Position
- Below the diagonal: libp2p_kad.behaviour uses a module listed above it, which is the healthy direction.
39→32 libp2p_kad.behaviour uses libp2p_peer_store.memory_store✕
- Connections
- 1 pair of types, where a type in libp2p_kad.behaviour uses a type in libp2p_peer_store.memory_store.
- The types involved
libp2p_kad.behaviour.Behaviour→libp2p_peer_store.memory_store.Event
- Direction
- libp2p_kad.behaviour uses libp2p_peer_store.memory_store, so a change to libp2p_peer_store.memory_store can break libp2p_kad.behaviour, while a change to libp2p_kad.behaviour can't break libp2p_peer_store.memory_store.
- Position
- Below the diagonal: libp2p_kad.behaviour uses a module listed above it, which is the healthy direction.
39→36 libp2p_kad.behaviour uses libp2p_kad.handler✕
- Connections
- 1 pair of types, where a type in libp2p_kad.behaviour uses a type in libp2p_kad.handler.
- The types involved
libp2p_kad.behaviour.Behaviour→libp2p_kad.handler.RequestId
- Direction
- libp2p_kad.behaviour uses libp2p_kad.handler, so a change to libp2p_kad.handler can break libp2p_kad.behaviour, while a change to libp2p_kad.behaviour can't break libp2p_kad.handler.
- Position
- Below the diagonal: libp2p_kad.behaviour uses a module listed above it, which is the healthy direction.
40→1 libp2p_rendezvous.client uses libp2p_core.connection✕
- Connections
- 1 pair of types, where a type in libp2p_rendezvous.client uses a type in libp2p_core.connection.
- The types involved
libp2p_rendezvous.client.Behaviour→libp2p_core.connection.Endpoint
- Direction
- libp2p_rendezvous.client uses libp2p_core.connection, so a change to libp2p_core.connection can break libp2p_rendezvous.client, while a change to libp2p_rendezvous.client can't break libp2p_core.connection.
- Position
- Below the diagonal: libp2p_rendezvous.client uses a module listed above it, which is the healthy direction.
40→3 libp2p_rendezvous.client uses libp2p_identity.ecdsa✕
- Connections
- 1 pair of types, where a type in libp2p_rendezvous.client uses a type in libp2p_identity.ecdsa.
- The types involved
libp2p_rendezvous.client.Behaviour→libp2p_identity.ecdsa.Keypair
- Direction
- libp2p_rendezvous.client uses libp2p_identity.ecdsa, so a change to libp2p_identity.ecdsa can break libp2p_rendezvous.client, while a change to libp2p_rendezvous.client can't break libp2p_identity.ecdsa.
- Position
- Below the diagonal: libp2p_rendezvous.client uses a module listed above it, which is the healthy direction.
40→8 libp2p_rendezvous.client uses libp2p_identity.peer_id✕
- Connections
- 1 pair of types, where a type in libp2p_rendezvous.client uses a type in libp2p_identity.peer_id.
- The types involved
libp2p_rendezvous.client.Behaviour→libp2p_identity.peer_id.PeerId
- Direction
- libp2p_rendezvous.client uses libp2p_identity.peer_id, so a change to libp2p_identity.peer_id can break libp2p_rendezvous.client, while a change to libp2p_rendezvous.client can't break libp2p_identity.peer_id.
- Position
- Below the diagonal: libp2p_rendezvous.client uses a module listed above it, which is the healthy direction.
40→15 libp2p_rendezvous.client uses multistream_select.protocol✕
- Connections
- 1 pair of types, where a type in libp2p_rendezvous.client uses a type in multistream_select.protocol.
- The types involved
libp2p_rendezvous.client.Behaviour→multistream_select.protocol.Message
- Direction
- libp2p_rendezvous.client uses multistream_select.protocol, so a change to multistream_select.protocol can break libp2p_rendezvous.client, while a change to libp2p_rendezvous.client can't break multistream_select.protocol.
- Position
- Below the diagonal: libp2p_rendezvous.client uses a module listed above it, which is the healthy direction.
40→19 libp2p_rendezvous.client uses libp2p_mplex.io✕
- Connections
- 1 pair of types, where a type in libp2p_rendezvous.client uses a type in libp2p_mplex.io.
- The types involved
libp2p_rendezvous.client.Behaviour→libp2p_mplex.io.ConnectionId
- Direction
- libp2p_rendezvous.client uses libp2p_mplex.io, so a change to libp2p_mplex.io can break libp2p_rendezvous.client, while a change to libp2p_rendezvous.client can't break libp2p_mplex.io.
- Position
- Below the diagonal: libp2p_rendezvous.client uses a module listed above it, which is the healthy direction.
40→22 libp2p_rendezvous.client uses libp2p_core.transport✕
- Connections
- 1 pair of types, where a type in libp2p_rendezvous.client uses a type in libp2p_core.transport.
- The types involved
libp2p_rendezvous.client.Behaviour→libp2p_core.transport.PortUse
- Direction
- libp2p_rendezvous.client uses libp2p_core.transport, so a change to libp2p_core.transport can break libp2p_rendezvous.client, while a change to libp2p_rendezvous.client can't break libp2p_core.transport.
- Position
- Below the diagonal: libp2p_rendezvous.client uses a module listed above it, which is the healthy direction.
40→27 libp2p_rendezvous.client uses libp2p_swarm.behaviour✕
- Connections
- 2 pairs of types, where a type in libp2p_rendezvous.client uses a type in libp2p_swarm.behaviour.
- The types involved
libp2p_rendezvous.client.Behaviour→libp2p_swarm.behaviour.FromSwarmlibp2p_rendezvous.client.Behaviour→libp2p_swarm.behaviour.NetworkBehaviour
- Direction
- libp2p_rendezvous.client uses libp2p_swarm.behaviour, so a change to libp2p_swarm.behaviour can break libp2p_rendezvous.client, while a change to libp2p_rendezvous.client can't break libp2p_swarm.behaviour.
- Position
- Below the diagonal: libp2p_rendezvous.client uses a module listed above it, which is the healthy direction.
40→32 libp2p_rendezvous.client uses libp2p_peer_store.memory_store✕
- Connections
- 1 pair of types, where a type in libp2p_rendezvous.client uses a type in libp2p_peer_store.memory_store.
- The types involved
libp2p_rendezvous.client.Behaviour→libp2p_peer_store.memory_store.Event
- Direction
- libp2p_rendezvous.client uses libp2p_peer_store.memory_store, so a change to libp2p_peer_store.memory_store can break libp2p_rendezvous.client, while a change to libp2p_rendezvous.client can't break libp2p_peer_store.memory_store.
- Position
- Below the diagonal: libp2p_rendezvous.client uses a module listed above it, which is the healthy direction.
40→38 libp2p_rendezvous.client uses libp2p_request_response✕
- Connections
- 1 pair of types, where a type in libp2p_rendezvous.client uses a type in libp2p_request_response.
- The types involved
libp2p_rendezvous.client.Behaviour→libp2p_request_response.OutboundRequestId
- Direction
- libp2p_rendezvous.client uses libp2p_request_response, so a change to libp2p_request_response can break libp2p_rendezvous.client, while a change to libp2p_rendezvous.client can't break libp2p_request_response.
- Position
- Below the diagonal: libp2p_rendezvous.client uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Event Sourcing
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 66 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 19 | High / Critical |
| A02:2025 — Security Misconfiguration | 4 | High / Critical |
Roadmap
First, enforce a protect-by-default authorization model by applying global authentication guards with explicit public opt-outs to ensure every route is secured. Second, harden the web security posture by configuring response headers such as Content-Security-Policy and X-Content-Type-Options on all server responses. Third, restrict token permissions in the supply-chain workflows to improve provenance and signing integrity. Finally, establish a documentation practice by recording significant design decisions as Architecture Decision Records in a dedicated folder.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Enforce authorization at every handler — a guard on each route, or a global authentication guard/middleware with explicit public opt-outs, so protected-by-default is demonstrable. | +11.0 pts | Medium | Access Controls |
| Set security response headers on what the server sends — actix-web's `DefaultHeaders::new().add((header::X_CONTENT_TYPE_OPTIONS, "nosniff"))`, tower-http's `SetResponseHeaderLayer::overriding(…)` on an axum router, or keep Rocket's default `Shield` — with `Content-Security-Policy`, `X-Content-Type-Options` and a frame policy on every response. | +5.0 pts | Medium | Web-Security Posture |
| Resolve the 4 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. | +2.1 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +2.0 pts | Low | ADR Quality |
| Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED, REDACTED. | +1.6 pts | Low | Static Analysis (SAST) |
| Resolve the 2 High IaC finding(s) in IaC & Container Security — start with REDACTED (2). | +1.1 pts | Low | IaC & Container Security |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. | +1.1 pts | Low | Supply-chain Provenance & Signing |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +1.7 pts | Medium | Architecture documentation |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.4 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.0 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Dependency Vulnerabilities: Medium CVE: REDACTED |
| misc/multistream-select/src/listener_select.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| protocols/kad/src/behaviour.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| swarm-derive/src/lib.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| protocols/kad/src/handler.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| protocols/mdns/src/behaviour/iface.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| misc/multistream-select/src/dialer_select.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| misc/server/src/main.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| protocols/floodsub/src/layer.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| protocols/ping/src/handler.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| protocols/relay/src/priv_client/transport.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| misc/multistream-select/src/negotiated.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 64 of 64 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.8 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
What we checked — 64 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, 332 of 356 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Watchdog duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
| LLM (sampled · advisory) | Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement | — | ◐ LLM · sampled · advisory |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.rs) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage read, produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
- D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.rs) and this repository declares a Cargo test suite (repository root, 138 test files), but it was not re-run: its build outgrew the 6 GB scratch ceiling (6.239 GB measured) and was stopped; its suite was not run. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D24 Comment Value — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D27 Navigability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- D34 Knowledge Freshness — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. File-level freshness contradicts repo activity: 96 commits in the last 90 days, yet 159 of 208 significant files carry no living knowledge. Those two readings cannot both be true, so the per-file recency signal is treated as unreliable here and freshness is not scored for this run.
- AX6 Interface segregation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AXR1 Runtime accessibility — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (examples/metrics/docker-compose.yml). compose up failed (exit 18 — an image could not be pulled) — otel-collector Pulling jaeger-all-in-one Pulling jaeger-all-in-one Error Get "https://registry-1.docker.io/v2/": Forbidden otel-collector Error Get "https://registry-1.docker.io/v2/": Forbidden Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the earlier `compose pull` step reported: otel-collector Pulling jaeger-all-in-one Pulling jaeger-all-in-one Error Get "https://registry-1.docker.io/v2/": Forbidden otel-collector Error Get "https://registry-1.docker.io/v2/": Forbidden Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; runtime evidence skipped.
- GD1 Unfinished & placeholder code — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Python, Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's Python, 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.
- X16 Unfloored truncation loop — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X18 Disposal-pattern correctness — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X4 Structured logging — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 126 further occurrence(s) are not listed individually; the score already reflects all 166.
- X5 Nullable reference types — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax and MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, and Kotlin source only, and no C# was loaded, no TypeScript was found, and this repository's Python, Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- 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 REDACTED (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.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
25 function(s) exceeded the cyclomatic complexity threshold of 15; the worst was ListenerSelectFuture::poll at 32.
What to do
- Bring the 25 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with ListenerSelectFuture::poll (cyclomatic 32), UDPMuxNewAddr::poll (cyclomatic 31), Connection::poll (cyclomatic 30). — 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 25 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.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
41 function(s) exceeded the cognitive complexity threshold of 15; the worst was UDPMuxNewAddr::poll at 76.
What to do
- Bring the 1 body over 60 down to 60 or less in Cognitive Complexity — start with UDPMuxNewAddr::poll (cognitive 76). — Refactoring it lifts Cognitive Complexity from 6.3 to about 6.5/10.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
27 god class(es) detected.
What to do
- Resolve the 11 MethodTooLong finding(s) in God Classes — start with behaviour.rs (3), lib.rs (3), pool.rs. — One of this dimension's main actionable groups (11 warning-level).
- Resolve the 9 FileTooLong finding(s) in God Classes — start with behaviour.rs (2), lib.rs (2), io.rs. — One of this dimension's main actionable groups (9 warning-level).
- Resolve the 5 ClassTooLong finding(s) in God Classes — start with behaviour.rs (2), lib.rs (2), io.rs. — One of this dimension's main actionable groups (5 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
53 duplicated block group(s) detected. One further row reports members as variants of one another; it aggregates block groups already counted above and is not itself counted. 4 of the 54 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 7 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with keypair.rs (2), global_only.rs, negotiated.rs. — One of this dimension's main actionable groups (7 warning-level).
- Resolve the 6 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with keypair.rs (2), kbucket.rs, connection.rs. — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 5 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with lib.rs (3), map_err.rs, behaviour.rs. — One of this dimension's main actionable groups (5 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
48 production modules (Cargo), 0 dependency cycle(s), 3 unstable depended-on module(s). Read from the build's own module declarations; 7 module(s) off the main sequence, with abstractness counted on 39 of the 48 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What to do
- Resolve the 7 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (7 warning-level).
- Resolve the 1 Unstable project libp2p-autonat finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Unstable project libp2p-metrics finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
1 of 172 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with lib.rs. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D9 · Test Distribution
706 test methods: 565 unit, 141 integration, 0 BDD, 0 e2e. The Rust suite contributes 706 `#[test]` function(s) across 138 file(s) declaring at least one; its unit/integration split is Cargo's own — 35 of those file(s) are integration-test targets under a crate's tests/ directory, and the rest are #[test] functions compiled into the crate they test.
D12 · Dependency Hygiene
2 outdated, 0 author-deprecated direct Go module(s), 0 pinning or checksum defect(s). Whether any of these modules is UNMAINTAINED is not graded — proxy.golang.org publishes no maintenance status, and release age does not stand in for one. Whether any is UNUSED is not graded either: that is a source question, not a registry one. Known CVEs in this module graph are D30's question, read from go.mod and go.sum there.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 596 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository's REDACTED closed over its manifests' `[dependencies]` and `[build-dependencies]`. Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D16 · Bus Factor
3 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is protocols/autonat/src/v2/client/behaviour.rs. Counted over 208 of the 255 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D17 · Explicit Debt
56 deducted task-comment markers across 92996 LoC (0.1/KLoC) → score 9.9. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 47 TodoComment finding(s) in Explicit Debt — start with lib.rs (7), protocol.rs (5), behaviour.rs (4). — One of this dimension's main actionable groups (47 warning-level).
- Resolve the 7 FixmeComment finding(s) in Explicit Debt — start with smoke.rs (5), stream_protocol.rs, behaviour.rs. — One of this dimension's main actionable groups (7 warning-level).
- Resolve the 1 HackComment finding(s) in Explicit Debt — start with protocol.rs. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 11 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
0 of 47 build units (Cargo) flagged as possibly oversized/incoherent.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
66 finding(s): 0 critical, 62 high, 4 medium, 0 low. 56 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 1 file(s) — `scripts/ensure-version-bump-and-changelog.sh` (line 32) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 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 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (4 issue-level).
- No action in Static Analysis (SAST) — all 54 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 (54 issue-level, 0 of them charged here).
- No action in Static Analysis (SAST) — all 2 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 (2 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
8 finding(s): 0 critical, 0 high, 8 medium, 0 low.
What to do
- Resolve the 5 Medium vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (5). — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 2 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Medium advisory (unmaintained) finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D31 · IaC & Container Security
4 finding(s): 0 critical, 2 high, 2 medium, 0 low.
What to do
- Resolve the 2 High IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 2 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 4 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
D37 · Vulnerability-disclosure Policy
A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 2 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
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX4 · Dependency direction
AX8 · Test isolation
AX9 · CQS / query purity
- `Behaviour.get_record` is a read-named query yet it performs a durable write on the read path (a persist to a store/repository). A query must stay side-effect-free so reads are safe to retry, cache, and route to a read replica; move the write into a command. — protocols/kad/src/behaviour.rs:797
What to do
- Keep query handlers read-only — move the writes/event-publishes into a command handler so reads stay safe to retry, cache, and route to a read replica.
C2 · Access Controls
- Authorization rules exist but no route guard, auth middleware or handler that refuses a caller was found.
What to do
- Enforce authorization at every handler — a guard on each route, or a global authentication guard/middleware with explicit public opt-outs, so protected-by-default is demonstrable.
ES1 · Fold determinism
ES2 · Immutable events
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add a README to the 50 of 70 project(s) that lack one — worth up to 1.4 pts.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
- Only 40/43 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `misc/gen-proto`, `misc/keygen`, `wasm-tests/webtransport-tests/echo-server`.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
- Add a health-check endpoint (a /health route on your axum/actix router) so orchestrators and load balancers can probe liveness/readiness.
P3 · Security & performance tooling
What to do
- Dependabot is configured but does not watch `gomod` — add that `package-ecosystem` entry to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
What to do
- Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where Watchdog can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it.
P6 · Release Hygiene
PF1 · Benchmark discipline
PF3 · Async & latency hygiene
S1 · Web-Security Posture
- None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is set on a response this repository's Rust server sends — defense in depth, even when a proxy could set them. (−2.0 on this card.) The server: `axum::serve(` (misc/server/src/http_service.rs:44).
- No handler of this repository's Rust server answers 400, 413 or 422 (`StatusCode::BAD_REQUEST`, `HttpResponse::BadRequest()`, `Status::BadRequest`, tonic `Status::invalid_argument`), and nothing declares validation — no `validator`/`garde` derive, no body limit (`DefaultBodyLimit::max`, `RequestBodyLimitLayer`, `JsonConfig::default().limit(…)`, Rocket `Limits`) — nothing shows inbound requests being checked, and refused, before a handler acts on them. A check that answers its failure with 200 and an error body is not seen. (−2.0 on this card.) The server: `axum::serve(` (misc/server/src/http_service.rs:44).
What to do
- Set security response headers on what the server sends — actix-web's `DefaultHeaders::new().add((header::X_CONTENT_TYPE_OPTIONS, "nosniff"))`, tower-http's `SetResponseHeaderLayer::overriding(…)` on an axum router, or keep Rocket's default `Shield` — with `Content-Security-Policy`, `X-Content-Type-Options` and a frame policy on every response.
- Validate what the server reads from a request — path, query, headers, body size and shape — and answer what fails with 400 (413 for an oversized body) before a handler acts on it: derive `validator::Validate` (or `garde::Validate`) on the request types and reject with `StatusCode::BAD_REQUEST`, and cap bodies with `DefaultBodyLimit::max`/`RequestBodyLimitLayer` or actix's `JsonConfig::default().limit(…)`.
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X17 · Uncapped recursion over a caller-supplied document
X19 · Unrestored process-global state
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
X30 · Support guard that admits what it rejects
X4 · Structured logging
- `debug!` at line 79 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`. — transports/webtransport-websys/src/transport.rs:79
- `debug!` at line 138 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`. — transports/websocket/src/framed.rs:138
- `debug!` at line 324 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`. — transports/websocket/src/framed.rs:324
- `debug!` at line 392 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`. — transports/websocket/src/framed.rs:392
- `debug!` at line 626 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`. — transports/websocket/src/framed.rs:626
- `debug!` at line 165 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`. — transports/webrtc-websys/src/connection.rs:165
- `error!` 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: `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`. — transports/webrtc/src/tokio/connection.rs:122
- `error!` at line 130 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`. — transports/webrtc/src/tokio/connection.rs:130
- `error!` at line 139 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `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`. — transports/webrtc/src/tokio/connection.rs:139
- `debug!` at line 191 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`. — transports/webrtc/src/tokio/connection.rs:191
- `error!` at line 293 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`. — transports/webrtc/src/tokio/connection.rs:293
- `error!` 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: `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`. — transports/webrtc/src/tokio/connection.rs:295
- `error!` at line 300 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`. — transports/webrtc/src/tokio/connection.rs:300
- `debug!` at line 180 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — transports/webrtc/src/tokio/udp_mux.rs:180
- `debug!` at line 348 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `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`. — transports/webrtc/src/tokio/udp_mux.rs:348
- `debug!` at line 374 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`. — transports/webrtc/src/tokio/udp_mux.rs:374
- `error!` at line 390 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`. — transports/webrtc/src/tokio/udp_mux.rs:390
- `debug!` at line 407 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`. — transports/webrtc/src/tokio/udp_mux.rs:407
- `error!` at line 410 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`. — transports/webrtc/src/tokio/udp_mux.rs:410
- `debug!` at line 476 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`. — transports/webrtc/src/tokio/udp_mux.rs:476
- `debug!` at line 517 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`. — transports/webrtc/src/tokio/udp_mux.rs:517
- `debug!` at line 342 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `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`. — transports/tcp/src/lib.rs:342
- `trace!` at line 36 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`. — transports/quic/src/hole_punching.rs:36
- `debug!` at line 322 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`. — transports/quic/src/transport.rs:322
- `trace!` at line 177 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`. — transports/noise/src/io/framed.rs:177
- `trace!` at line 182 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`. — transports/noise/src/io/framed.rs:182
- `trace!` at line 202 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `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`. — transports/noise/src/io/framed.rs:202
- `trace!` at line 207 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`. — transports/noise/src/io/framed.rs:207
- `debug!` at line 316 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`. — transports/dns/src/lib.rs:316
- `debug!` at line 532 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`. — transports/dns/src/lib.rs:532
- `debug!` at line 363 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`. — swarm/src/connection.rs:363
- `debug!` at line 565 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`. — swarm/src/connection.rs:565
- `debug!` at line 837 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`. — swarm/src/lib.rs:837
- `debug!` at line 839 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`. — swarm/src/lib.rs:839
- `debug!` at line 857 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`. — swarm/src/lib.rs:857
- `debug!` at line 883 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`. — swarm/src/lib.rs:883
- `debug!` at line 890 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`. — swarm/src/lib.rs:890
- `debug!` at line 758 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`. — swarm/src/connection/pool.rs:758
- `debug!` at line 225 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`. — protocols/upnp/src/behaviour.rs:225
- `debug!` at line 257 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`. — protocols/upnp/src/behaviour.rs:257
What to do
- Interpolated log message defeats structured logging
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 77% | Strong | Solid. |
| Architecture | 98% | Exemplary | Solid. |
| Maturity | 76% | Strong | Solid. |
| Readiness | 80% | Strong | Solid. |
| Security | 51% | Adequate — gated by D29, D36, C2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Event Sourcing | 100% | Exemplary | Strongest area. |
| Performance | 91% | Exemplary | Solid. |
Unscored — 1 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 56 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: this repository's Go imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one.
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No Go request handler (a net/http, Gin, Echo, Fiber or fasthttp handler, or a gRPC service method) is declared as a method or function, and no handler function literal writes a value captured from outside it, so no state is shared between request goroutines. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. 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
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — compose up failed (exit 18 — an image could not be pulled) — otel-collector Pulling jaeger-all-in-one Pulling jaeger-all-in-one Error Get "https://registry-1.docker.io/v2/": Forbidden otel-collector Error Get "https://registry-1.docker.io/v2/": Forbidden Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the earlier `compose pull` step reported: otel-collector Pulling jaeger-all-in-one Pulling jaeger-all-in-one Error Get "https://registry-1.docker.io/v2/": Forbidden otel-collector Error Get "https://registry-1.docker.io/v2/": Forbidden Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no data at rest for these controls to protect.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~20041 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.
- D11 Test Reliability — Test reliability not included — the .rs suite was found but not re-run
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — Naming consistency is measured on C# only; Go, Python, Rust not measured.
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed Rust surface was not measured.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ projects each declaring an entity of their own. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C# and Visual Basic comments only — this repository's production source is .go, .py, .rs, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.rs), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D34 Knowledge Freshness — knowledge concentrated in recent work — freshness signal contradicted by repo activity
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — applicable but not scored (2 signals for this style, 2 needed — the count is met but a required primary signal is absent): 144 value object(s); 26 domain event(s); its domain events are published by services or handlers — no domain entity raises one
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- M4 Documentation accuracy — Not applicable: the 12 current-state document(s) make no claim of a kind M4 checks. 4 claim(s) of kinds M4 does not check were not checked (path 2, command argument 1, environment variable 1); M4 checks only links and versions.
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HTTP client call or construction in the Python, Rust source (service entry point: misc/server/src/http_service.rs:38 (Router::new()))
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF2 Allocation hygiene — Not applicable: Rust spells out every heap allocation and makes borrowed slices (&[T], &str) its ordinary parameter types, so the allocation-aware style this card rewards elsewhere is the language's baseline rather than a rung to climb.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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
- 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
- X2 Cancellation propagation — no C# was loaded; this repository's Python and Rust were read, and no request in it can be cancelled by a caller — a Python request takes no token: asyncio cancels the task and trio or anyio the scope that made it, from outside the call, and requests, httpx, aiohttp and gRPC take a timeout, not a cancellation; 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.
- 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 — 66 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Query writes persistent state on the read path: Behaviour.get_record protocols/kad/src/behaviour.rs:797
- REDACTED
- REDACTED
- REDACTED
Serious — 235 finding(s)
- TodoComment transports/webtransport-websys/src/connection.rs:120
- TodoComment transports/webrtc/src/tokio/transport.rs:125
- TodoComment transports/webrtc/src/tokio/upgrade.rs:190
- TodoComment transports/uds/src/lib.rs:162
- TodoComment transports/uds/src/lib.rs:325
- TodoComment transports/uds/src/lib.rs:334
- TodoComment transports/tls/src/verifier.rs:90
- TodoComment transports/tls/src/verifier.rs:93
- TodoComment transports/quic/src/connection.rs:109
- TodoComment swarm-derive/src/lib.rs:269
- TodoComment swarm-derive/src/lib.rs:309
- TodoComment swarm-derive/src/lib.rs:359
- TodoComment swarm/tests/swarm_derive.rs:36
- TodoComment swarm/src/handler/one_shot.rs:40
- TodoComment swarm/src/connection/error.rs:29
- TodoComment protocols/relay/src/lib.rs:82
- TodoComment protocols/relay/src/priv_client/transport.rs:202
- TodoComment protocols/ping/src/handler.rs:197
- TodoComment protocols/mdns/src/behaviour/iface.rs:145
- TodoComment protocols/mdns/src/behaviour/iface.rs:153
- TodoComment protocols/mdns/src/behaviour/iface/dns.rs:53
- TodoComment protocols/mdns/src/behaviour/iface/dns.rs:68
- TodoComment protocols/mdns/src/behaviour/iface/dns.rs:438
- TodoComment protocols/mdns/src/behaviour/iface/query.rs:77
- TodoComment protocols/mdns/src/behaviour/iface/query.rs:261
- MethodTooLong: Behaviour.on_connection_handler_event protocols/relay/src/behaviour.rs:534
- MethodTooLong: Swarm.handle_pool_event swarm/src/lib.rs:685
- MethodTooLong: Pool.poll swarm/src/connection/pool.rs:567
- MethodTooLong: Behaviour.on_connection_handler_event protocols/kad/src/behaviour.rs:2282
- MethodTooLong: Behaviour.query_finished protocols/kad/src/behaviour.rs:1453
- MethodTooLong: Connection.poll swarm/src/connection.rs:253
- MethodTooLong: Behaviour.on_connection_handler_event protocols/request-response/src/lib.rs:849
- MethodTooLong: UDPMuxNewAddr.poll transports/webrtc/src/tokio/udp_mux.rs:188
- MethodTooLong: Swarm.handle_transport_event swarm/src/lib.rs:939
- MethodTooLong: ListenerSelectFuture.poll misc/multistream-select/src/listener_select.rs:124
- MethodTooLong: Handler.poll protocols/relay/src/priv_client/handler.rs:272
- Behaviour::on_connection_handler_event (cognitive 54) protocols/kad/src/behaviour.rs:2282
- Behaviour::poll (cognitive 50) protocols/kad/src/behaviour.rs:2549
- Behaviour::poll (cognitive 47) protocols/mdns/src/behaviour.rs:272
- Behaviour::on_connection_handler_event (cognitive 27) protocols/floodsub/src/layer.rs:360
- Behaviour::on_connection_handler_event (cognitive 24) protocols/relay/src/behaviour.rs:534
- Behaviour::connection_updated (cognitive 21) protocols/kad/src/behaviour.rs:1326
- Behaviour::query_finished (cognitive 19) protocols/kad/src/behaviour.rs:1453
- Behaviour::emit_new_external_addr_candidate_event (cognitive 17) protocols/identify/src/behaviour.rs:350
- Behaviour::on_swarm_event (cognitive 17) protocols/identify/src/behaviour.rs:551
- FileTooLong: src/behaviour.rs protocols/kad/src/behaviour.rs
- FileTooLong: src/lib.rs swarm/src/lib.rs
- FileTooLong: src/behaviour.rs protocols/relay/src/behaviour.rs
- FileTooLong: src/io.rs muxers/mplex/src/io.rs
- FileTooLong: connection/pool.rs swarm/src/connection/pool.rs
- FileTooLong: src/handler.rs protocols/kad/src/handler.rs
- FileTooLong: src/lib.rs protocols/request-response/src/lib.rs
- FileTooLong: src/keypair.rs identity/src/keypair.rs
- FileTooLong: src/framed.rs transports/websocket/src/framed.rs
- FixmeComment transports/webrtc/tests/smoke.rs:199
- FixmeComment transports/webrtc/tests/smoke.rs:236
- FixmeComment transports/quic/tests/smoke.rs:673
- FixmeComment transports/quic/tests/smoke.rs:710
- FixmeComment transports/quic/tests/smoke.rs:353
- FixmeComment swarm/src/stream_protocol.rs:45
- FixmeComment protocols/autonat/src/v2/client/behaviour.rs:361
- Duplicated block (6 lines × 2) core/src/transport/global_only.rs:267
- Duplicated block (6 lines × 2) identity/src/keypair.rs:479
- Duplicated block (6 lines × 2) identity/src/keypair.rs:773
- Duplicated block (6 lines × 2) misc/multistream-select/src/negotiated.rs:248
- Duplicated block (6 lines × 2) swarm/src/handler/multi.rs:261
- Duplicated block (6 lines × 2) transports/webrtc-websys/src/transport.rs:87
- Duplicated block (6 lines × 2) wasm-tests/webtransport-tests/src/lib.rs:163
- Off the main sequence: libp2p-identity
- Off the main sequence: libp2p-pnet
- Off the main sequence: multistream-select
- Off the main sequence: prost-codec
- Off the main sequence: rw-stream-sink
- Off the main sequence: libp2p-swarm
- Off the main sequence: libp2p-core
- Behaviour::on_connection_handler_event (cyclomatic 29) protocols/kad/src/behaviour.rs:2282
- Behaviour::on_connection_handler_event (cyclomatic 26) protocols/relay/src/behaviour.rs:534
- Behaviour::poll (cyclomatic 23) protocols/kad/src/behaviour.rs:2549
- Behaviour::poll (cyclomatic 21) protocols/mdns/src/behaviour.rs:272
- Behaviour::on_connection_handler_event (cyclomatic 16) protocols/floodsub/src/layer.rs:360
- Behaviour::query_finished (cyclomatic 16) protocols/kad/src/behaviour.rs:1453
- Duplicated block (7 lines × 2) identity/src/keypair.rs:499
- Duplicated block (7 lines × 2) identity/src/keypair.rs:793
- Duplicated block (7 lines × 2) protocols/kad/src/kbucket.rs:280
- Duplicated block (7 lines × 2) transports/quic/src/connection.rs:80
- Duplicated block (7 lines × 2) transports/tls/src/lib.rs:46
- Duplicated block (7 lines × 2) core/src/upgrade/apply.rs:148
- ClassTooLong: Behaviour protocols/kad/src/behaviour.rs:67
- ClassTooLong: Swarm swarm/src/lib.rs:309
- ClassTooLong: Multiplexed muxers/mplex/src/io.rs:65
- ClassTooLong: Behaviour protocols/request-response/src/lib.rs:346
- ClassTooLong: Behaviour protocols/relay/src/behaviour.rs:256
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (10 lines × 2) core/src/transport/map_err.rs:121
- Duplicated block (10 lines × 2) swarm-derive/src/lib.rs:290
- Duplicated block (10 lines × 2) swarm-derive/src/lib.rs:301
- Duplicated block (10 lines × 2) swarm/src/behaviour.rs:346
- Duplicated block (10 lines × 2) muxers/test-harness/src/lib.rs:234
- Duplicated block (9 lines × 2) core/src/transport/choice.rs:114
- Duplicated block (9 lines × 2) core/src/transport/upgrade.rs:524
- Duplicated block (9 lines × 2) misc/multistream-select/src/length_delimited.rs:344
- Duplicated block (9 lines × 2) transports/websocket/src/quicksink.rs:184
- Duplicated block (9 lines × 2) transports/websocket/src/quicksink.rs:193
- Duplicated block (8 lines × 2) misc/multistream-select/src/length_delimited.rs:267
- Duplicated block (8 lines × 2) protocols/floodsub/src/layer.rs:138
- Duplicated block (8 lines × 2) protocols/relay/src/copy_future.rs:89
- Duplicated block (8 lines × 2) transports/webrtc/src/tokio/connection.rs:162
- Duplicated block (8 lines × 2) wasm-tests/webtransport-tests/src/lib.rs:210
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (5 lines × 2) identity/src/keypair.rs:485
- Duplicated block (5 lines × 2) identity/src/keypair.rs:779
- Duplicated block (5 lines × 2) transports/webrtc-websys/src/stream/poll_data_channel.rs:98
- Duplicated block (5 lines × 2) muxers/mplex/src/io.rs:154
- Handler::poll (cognitive 28) protocols/relay/src/priv_client/handler.rs:272
- Handler::poll (cognitive 19) protocols/ping/src/handler.rs:237
- Handler::poll (cognitive 17) protocols/identify/src/handler.rs:339
- Duplicated block (14 lines × 2) core/src/transport/and_then.rs:106
- Duplicated block (14 lines × 2) core/src/transport/upgrade.rs:504
- Duplicated block (14 lines × 2) transports/webrtc-websys/src/stream/poll_data_channel.rs:184
- Handler::poll (cyclomatic 21) protocols/relay/src/priv_client/handler.rs:272
- Handler::poll (cyclomatic 16) protocols/ping/src/handler.rs:237
- ClosestPeersIter::next (cognitive 22) protocols/kad/src/query/peers/closest.rs:304
- ClosestPeersIter::on_success (cognitive 20) protocols/kad/src/query/peers/closest.rs:156
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (13–14 lines × 2) protocols/kad/src/jobs.rs:242
- Duplicated block (13–14 lines × 2) protocols/relay/src/priv_client.rs:225
- Duplicated block (12–14 lines × 2) protocols/relay/src/behaviour.rs:126
- Duplicated block (12–14 lines × 2) wasm-tests/webtransport-tests/src/lib.rs:292
- Duplicated block (13 lines × 2) protocols/identify/src/handler.rs:362
- Duplicated block (13 lines × 2) transports/webrtc-websys/src/connection.rs:161
- Duplicated block (8 lines × 3) transports/websocket/src/quicksink.rs:190
- Duplicated block (8 lines × 3) core/src/transport/global_only.rs:247
- Duplicated block (6 lines × 3) core/src/upgrade/select.rs:86
- Duplicated block (6 lines × 3) core/src/upgrade/select.rs:120
- ListenerSelectFuture::poll (cyclomatic 32) misc/multistream-select/src/listener_select.rs:124
- UDPMuxNewAddr::poll (cyclomatic 31) transports/webrtc/src/tokio/udp_mux.rs:188
- Connection::poll (cyclomatic 30) swarm/src/connection.rs:253
- Pool::poll (cyclomatic 26) swarm/src/connection/pool.rs:567
- libp2p_swarm_derive::build_struct (cyclomatic 25) swarm-derive/src/lib.rs:57
- InboundSubstreamState::poll_next (cyclomatic 22) protocols/kad/src/handler.rs:867
- Endpoint::from_multiaddr (cyclomatic 22) transports/webtransport-websys/src/endpoint.rs:22
- libp2p_dns::resolve (cyclomatic 21) transports/dns/src/lib.rs:427
- InterfaceState::poll (cyclomatic 20) protocols/mdns/src/behaviour/iface.rs:207
- P2pCertificate::signature_scheme (cyclomatic 19) transports/tls/src/certificate.rs:428
- DialerSelectFuture::poll (cyclomatic 18) misc/multistream-select/src/dialer_select.rs:99
- libp2p_server::main (cyclomatic 18) misc/server/src/main.rs:44
- ClosestDisjointPeersIter::next (cyclomatic 17) protocols/kad/src/query/peers/closest/disjoint.rs:190
- Transport::do_dial (cyclomatic 17) transports/dns/src/lib.rs:213
- Codec::decode (cyclomatic 16) muxers/mplex/src/codec.rs:206
- libp2p_autonat::v2::client::handler::dial_request::start_stream_handle (cyclomatic 16) protocols/autonat/src/v2/client/handler/dial_request.rs:207
- libp2p_websocket::framed::parse_ws_dial_addr (cyclomatic 16) transports/websocket/src/framed.rs:504
- HackComment transports/noise/src/protocol.rs:311
- XxxComment misc/webrtc-utils/src/sdp.rs:61
- UDPMuxNewAddr::poll (cognitive 76) transports/webrtc/src/tokio/udp_mux.rs:188
- ListenerSelectFuture::poll (cognitive 58) misc/multistream-select/src/listener_select.rs:124
- libp2p_dns::resolve (cognitive 52) transports/dns/src/lib.rs:427
- Connection::poll (cognitive 46) swarm/src/connection.rs:253
- Transport::do_dial (cognitive 46) transports/dns/src/lib.rs:213
- Pool::poll (cognitive 45) swarm/src/connection/pool.rs:567
- libp2p_swarm_derive::build_struct (cognitive 38) swarm-derive/src/lib.rs:57
- DialerSelectFuture::poll (cognitive 30) misc/multistream-select/src/dialer_select.rs:99
- Endpoint::from_multiaddr (cognitive 30) transports/webtransport-websys/src/endpoint.rs:22
- Swarm::poll_next_event (cognitive 28) swarm/src/lib.rs:1181
- InterfaceState::poll (cognitive 27) protocols/mdns/src/behaviour/iface.rs:207
- LengthDelimited::poll_next (cognitive 26) misc/multistream-select/src/length_delimited.rs:148
- P2pCertificate::signature_scheme (cognitive 26) transports/tls/src/certificate.rs:428
- keygen::main (cognitive 25) misc/keygen/src/main.rs:52
- GenTransport::dial (cognitive 25) transports/quic/src/transport.rs:264
- libp2p_relay::priv_client::transport::parse_relayed_multiaddr (cognitive 24) protocols/relay/src/priv_client/transport.rs:266
- MemoryStore::on_swarm_event (cognitive 22) misc/peer-store/src/memory_store.rs:194
- Multiplexed::poll_read_stream (cognitive 22) muxers/mplex/src/io.rs:434
- KBucket::apply_pending (cognitive 22) protocols/kad/src/kbucket/bucket.rs:220
- ClosestDisjointPeersIter::next (cognitive 20) protocols/kad/src/query/peers/closest/disjoint.rs:190
- Codec::decode (cognitive 19) muxers/mplex/src/codec.rs:206
- InboundSubstreamState::poll_next (cognitive 19) protocols/kad/src/handler.rs:867
- PutRecordJob::poll (cognitive 19) protocols/kad/src/jobs.rs:198
- MultiHandler::on_connection_event (cognitive 19) swarm/src/handler/multi.rs:145
- Negotiated::poll (cognitive 18) misc/multistream-select/src/negotiated.rs:115
- libp2p_server::main (cognitive 18) misc/server/src/main.rs:44
- FixedPeersIter::next (cognitive 17) protocols/kad/src/query/peers/fixed.rs:129
- REDACTED
- REDACTED
- FunctionTooLong: libp2p_swarm_derive::build_struct swarm-derive/src/lib.rs:57
- TooManyMethods: Behaviour protocols/kad/src/behaviour.rs:67
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Near-duplicate member family (3 members, 15 shared lines) core/src/transport/global_only.rs:246
- Duplicated block (20 lines × 2) transports/websocket/src/quicksink.rs:209
- Duplicated block (18 lines × 2) misc/connection-limits/src/lib.rs:326
- Duplicated block (13 lines × 3) core/src/upgrade/select.rs:62
- Duplicated block (11 lines × 3) transports/dns/src/lib.rs:444
- Duplicated block (11 lines × 2) protocols/relay/src/behaviour.rs:469
- Duplicated block (9–10 lines × 2) protocols/kad/src/behaviour.rs:1506
- Duplicated block (7 lines × 3) core/src/transport/global_only.rs:257
- Duplicated block (8 lines × 4) protocols/relay/src/priv_client/transport.rs:173
- Unstable project libp2p-autonat
- Unstable project libp2p-metrics
- Unstable project libp2p-rendezvous
- Low cohesion: Substream (LCOM4 4) muxers/mplex/src/lib.rs:196
Minor — 53 finding(s)
- Interpolated log message defeats structured logging transports/webtransport-websys/src/transport.rs:79
- Interpolated log message defeats structured logging transports/websocket/src/framed.rs:138
- Interpolated log message defeats structured logging transports/websocket/src/framed.rs:324
- Interpolated log message defeats structured logging transports/websocket/src/framed.rs:392
- Interpolated log message defeats structured logging transports/websocket/src/framed.rs:626
- Interpolated log message defeats structured logging transports/webrtc-websys/src/connection.rs:165
- Interpolated log message defeats structured logging transports/webrtc/src/tokio/connection.rs:122
- Interpolated log message defeats structured logging transports/webrtc/src/tokio/connection.rs:130
- Interpolated log message defeats structured logging transports/webrtc/src/tokio/connection.rs:139
- Interpolated log message defeats structured logging transports/webrtc/src/tokio/connection.rs:191
- Interpolated log message defeats structured logging transports/webrtc/src/tokio/connection.rs:293
- Interpolated log message defeats structured logging transports/webrtc/src/tokio/connection.rs:295
- Interpolated log message defeats structured logging transports/webrtc/src/tokio/connection.rs:300
- Interpolated log message defeats structured logging transports/webrtc/src/tokio/udp_mux.rs:180
- Interpolated log message defeats structured logging transports/webrtc/src/tokio/udp_mux.rs:348
- Interpolated log message defeats structured logging transports/webrtc/src/tokio/udp_mux.rs:374
- Interpolated log message defeats structured logging transports/webrtc/src/tokio/udp_mux.rs:390
- Interpolated log message defeats structured logging transports/webrtc/src/tokio/udp_mux.rs:407
- Interpolated log message defeats structured logging transports/webrtc/src/tokio/udp_mux.rs:410
- Interpolated log message defeats structured logging transports/webrtc/src/tokio/udp_mux.rs:476
- Interpolated log message defeats structured logging transports/webrtc/src/tokio/udp_mux.rs:517
- Interpolated log message defeats structured logging transports/tcp/src/lib.rs:342
- Interpolated log message defeats structured logging transports/quic/src/hole_punching.rs:36
- Interpolated log message defeats structured logging transports/quic/src/transport.rs:322
- Interpolated log message defeats structured logging transports/noise/src/io/framed.rs:177
- Duplicated predicate protocols/autonat/src/v1/behaviour.rs:665
- Duplicated predicate transports/webrtc-websys/src/transport.rs:89
- Thin authorization enforcement
- Off-boarding risk: anonymized user #1
- Further sole-owners (lower concentration)
- No ADRs found
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- Logging is not universal
- No security response headers detected
- No inbound request validation detected
Minor — 2 finding(s)
- Outdated: github.com/libp2p/go-libp2p
- Outdated: github.com/quic-go/quic-go
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-9cfc03b242cf4f7e9252e70896931a69/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-9cfc03b242cf4f7e9252e70896931a69/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/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 66 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 8 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 4 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |