Executive summary
ProvableHQ/snarkOS falls short of our standard for production, held back most by its Event Sourcing lens, the way the code stores and replays its history of events. It scores 56 out of 100 and is rated Adequate, and 77 of its 78 critical findings are security problems.
Event Sourcing, at 49, is the weakest lens and counts most in the score. The best first step for the work it takes is replacing the six exposed passwords or keys and switching the old ones off, worth about 4 points. Making the events unchangeable would lift Event Sourcing itself, worth about 6 points. Raising Event Sourcing to 70 would lift the score to about 61.
Forty-eight pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Fifteen passwords or keys in the code's history and six in the code are open to anyone who can read the repository, and four secrets can leak from the build pipeline. Pinning each tool to an exact version, replacing each exposed password or key and limiting each secret to its own step would close these risks. Setting a waiting period for automatic updates would fix the automatic dependency update that takes a new release at once, and the pipeline step that installs packages without pinning their versions needs the packages it installs pinned to exact versions. Making recorded events unchangeable would take care of the recorded event that can be changed afterwards.
The product code is 51,128 lines, about €57,000 to rebuild.
If Event Sourcing rose from 49 to 70, the lowest score rated Strong, the score would rise from 56 to about 61.
New since the last survey: 48 findings
- Coupling · Off the main sequence: snarkos-node-metrics
- REDACTED Scanning · REDACTED
- REDACTED Scanning · REDACTED
- REDACTED Scanning · REDACTED
- Explicit Debt · TodoComment node/consensus/src/lib.rs
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Dependency Vulnerabilities · REDACTED
- Change Coupling · Change coupling: test_helpers.rs ↔ router.rs node/router/src/test_helpers.rs
- Change Coupling · Change coupling: test_helpers.rs ↔ router.rs node/router/src/test_helpers.rs
- 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
- Outbound HTTP resilience · Outbound HTTP without resilience cli/src/commands/developer/mod.rs
- Outbound HTTP resilience · Outbound HTTP without resilience cli/src/commands/developer/mod.rs
- Outbound HTTP resilience · Outbound HTTP without resilience cli/src/commands/developer/mod.rs
- Outbound HTTP resilience · Outbound HTTP without resilience cli/src/commands/developer/scan.rs
- Outbound HTTP resilience · Outbound HTTP without resilience node/cdn/src/blocks.rs
Fixed since the last survey: 18 findings
- Code Duplication · Duplicated block (9 lines × 2) node/router/src/inbound.rs
- Churn × Complexity Hotspots · Repeated repair: node/bft/src/worker.rs node/bft/src/worker.rs
- Explicit Debt · TodoComment node/bft/src/primary/proposal_task.rs
- Explicit Debt · TodoComment node/consensus/src/lib.rs
- Explicit Debt · TodoComment node/consensus/src/lib.rs
- Static Analysis (SAST) · High: watchdog-mutable-circleci-orb-version .circleci/config.yml
- Static Analysis (SAST) · High: watchdog-mutable-circleci-executor-image .circleci/config.yml
- Static Analysis (SAST) · High: watchdog-unverified-download-in-run .circleci/config.yml
- Static Analysis (SAST) · High: REDACTED .circleci/config.yml
- Static Analysis (SAST) · High: REDACTED .circleci/config.yml
- Static Analysis (SAST) · High: REDACTED .circleci/config.yml
- Static Analysis (SAST) · High: watchdog-unverified-download-in-run .circleci/config.yml
- Static Analysis (SAST) · High: REDACTED REDACTED
- Change Coupling · Change-coupling hub: test_helpers.rs → router.rs, router.rs, router.rs node/router/src/test_helpers.rs
- Supply-chain Provenance & Signing · CI installs an unverified third-party binary .circleci/config.yml
- Supply-chain Provenance & Signing · CI installs an unverified third-party binary .circleci/config.yml
- Supply-chain Provenance & Signing REDACTED
- Outbound HTTP resilience · Outbound HTTP without resilience cli/src/commands/developer/mod.rs
Rebuild cost: about €57,000 · Estimate
| Cost to rebuild | €19,000 to €94,000, for 313 to 993 hours of work, about 0.4 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 56. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Medium: 51,128 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 snarkos_node_rest.helpers.path | 2 snarkos_node_sync_locators.block_locators | 3 snarkos_node_bft.helpers.channels | 4 snarkos_node_bft_events | 5 snarkos_node_network.node_type | 6 snarkos_node_sync.block_sync | 7 snarkos_node_tcp.helpers.connections | 8 snarkos_utilities.node_data | 9 snarkos_node_tcp.tcp | 10 snarkos_node_bft_events.disconnect | 11 snarkos_node_tcp | 12 snarkos_node_network.peering | 13 snarkos_node_router_messages | 14 snarkos_node_tcp.protocols.handshake | 15 snarkos_node_tcp.protocols.on_connect | 16 snarkos_node_bft_events.block_request | 17 snarkos_node_router_messages.ping | 18 snarkos_node_tcp.protocols.reading | 19 snarkos_node_tcp.protocols.writing | 20 snarkos_node_bft.sync | 21 snarkos_node_router | 22 snarkos_node_bft.gateway | 23 snarkos_node_router.outbound | 24 snarkos_utilities.signals | 25 snarkos_node_bft.primary | 26 snarkos_node_bft.worker | 27 snarkos_node_router.heartbeat | 28 snarkos_node_router.inbound | 29 snarkos_node_bft.bft | 30 snarkos_node_router.routing | 31 snarkos_node_consensus | 32 snarkos_node_rest | 33 snarkos_node.node | 34 snarkos_display | 35 snarkos_account | 36 snarkos_node.client | 37 snarkos_node.prover | 38 snarkos_node.validator | 39 snarkos_node_router.test_helpers | 40 snarkos_node.bootstrap_client |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 snarkos_node_rest.helpers.path | ||||||||||||||||||||||||||||||||||||||||
| 2 snarkos_node_sync_locators.block_locators | ||||||||||||||||||||||||||||||||||||||||
| 3 snarkos_node_bft.helpers.channels | 1 | |||||||||||||||||||||||||||||||||||||||
| 4 snarkos_node_bft_events | 1 | |||||||||||||||||||||||||||||||||||||||
| 5 snarkos_node_network.node_type | 1 | |||||||||||||||||||||||||||||||||||||||
| 6 snarkos_node_sync.block_sync | 1 | |||||||||||||||||||||||||||||||||||||||
| 7 snarkos_node_tcp.helpers.connections | 2 | |||||||||||||||||||||||||||||||||||||||
| 8 snarkos_utilities.node_data | 1 | |||||||||||||||||||||||||||||||||||||||
| 9 snarkos_node_tcp.tcp | 4 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 10 snarkos_node_bft_events.disconnect | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 11 snarkos_node_tcp | 1 | |||||||||||||||||||||||||||||||||||||||
| 12 snarkos_node_network.peering | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 13 snarkos_node_router_messages | 1 | |||||||||||||||||||||||||||||||||||||||
| 14 snarkos_node_tcp.protocols.handshake | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 15 snarkos_node_tcp.protocols.on_connect | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 snarkos_node_bft_events.block_request | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 17 snarkos_node_router_messages.ping | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 18 snarkos_node_tcp.protocols.reading | 2 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 19 snarkos_node_tcp.protocols.writing | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 20 snarkos_node_bft.sync | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 21 snarkos_node_router | 1 | 2 | 1 | 2 | 2 | 1 | 1 | 1 | 1 | 1 | 2 | |||||||||||||||||||||||||||||
| 22 snarkos_node_bft.gateway | 3 | 2 | 1 | 3 | 2 | 2 | 3 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 2 | ||||||||||||||||||||||||
| 23 snarkos_node_router.outbound | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 24 snarkos_utilities.signals | 1 | |||||||||||||||||||||||||||||||||||||||
| 25 snarkos_node_bft.primary | 2 | 1 | 1 | 1 | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 26 snarkos_node_bft.worker | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 27 snarkos_node_router.heartbeat | 1 | |||||||||||||||||||||||||||||||||||||||
| 28 snarkos_node_router.inbound | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 29 snarkos_node_bft.bft | 3 | 1 | 1 | 1 | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||
| 30 snarkos_node_router.routing | 1 | 1 | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 31 snarkos_node_consensus | 2 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 32 snarkos_node_rest | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 33 snarkos_node.node | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 34 snarkos_display | 1 | |||||||||||||||||||||||||||||||||||||||
| 35 snarkos_account | 1 | |||||||||||||||||||||||||||||||||||||||
| 36 snarkos_node.client | 1 | 3 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 2 | 1 | ||||||||||||||||||||
| 37 snarkos_node.prover | 1 | 3 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||
| 38 snarkos_node.validator | 1 | 3 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 2 | 1 | |||||||||||||||||||
| 39 snarkos_node_router.test_helpers | 2 | 3 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||
| 40 snarkos_node.bootstrap_client | 1 | 3 | 2 | 2 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 2 | 1 |
3→2 snarkos_node_bft.helpers.channels uses snarkos_node_sync_locators.block_locators✕
- Connections
- 1 pair of types, where a type in snarkos_node_bft.helpers.channels uses a type in snarkos_node_sync_locators.block_locators.
- The types involved
snarkos_node_bft.helpers.channels.SyncSender→snarkos_node_sync_locators.block_locators.BlockLocators
- Direction
- snarkos_node_bft.helpers.channels uses snarkos_node_sync_locators.block_locators, so a change to snarkos_node_sync_locators.block_locators can break snarkos_node_bft.helpers.channels, while a change to snarkos_node_bft.helpers.channels can't break snarkos_node_sync_locators.block_locators.
- Position
- Below the diagonal: snarkos_node_bft.helpers.channels uses a module listed above it, which is the healthy direction.
4→10 snarkos_node_bft_events uses snarkos_node_bft_events.disconnect part of a loop✕
- Connections
- 1 pair of types, where a type in snarkos_node_bft_events uses a type in snarkos_node_bft_events.disconnect.
- The types involved
snarkos_node_bft_events.Event→snarkos_node_bft_events.disconnect.DisconnectReason
- Direction
- snarkos_node_bft_events uses snarkos_node_bft_events.disconnect, so a change to snarkos_node_bft_events.disconnect can break snarkos_node_bft_events, while a change to snarkos_node_bft_events can't break snarkos_node_bft_events.disconnect.
- 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.
5→34 snarkos_node_network.node_type uses snarkos_display part of a loop✕
- Connections
- 1 pair of types, where a type in snarkos_node_network.node_type uses a type in snarkos_display.
- The types involved
snarkos_node_network.node_type.NodeType→snarkos_display.Display
- Direction
- snarkos_node_network.node_type uses snarkos_display, so a change to snarkos_display can break snarkos_node_network.node_type, while a change to snarkos_node_network.node_type can't break snarkos_display.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→2 snarkos_node_sync.block_sync uses snarkos_node_sync_locators.block_locators✕
- Connections
- 1 pair of types, where a type in snarkos_node_sync.block_sync uses a type in snarkos_node_sync_locators.block_locators.
- The types involved
snarkos_node_sync.block_sync.BlockSync→snarkos_node_sync_locators.block_locators.BlockLocators
- Direction
- snarkos_node_sync.block_sync uses snarkos_node_sync_locators.block_locators, so a change to snarkos_node_sync_locators.block_locators can break snarkos_node_sync.block_sync, while a change to snarkos_node_sync.block_sync can't break snarkos_node_sync_locators.block_locators.
- Position
- Below the diagonal: snarkos_node_sync.block_sync uses a module listed above it, which is the healthy direction.
7→20 snarkos_node_tcp.helpers.connections uses snarkos_node_bft.sync part of a loop✕
- Connections
- 2 pairs of types, where a type in snarkos_node_tcp.helpers.connections uses a type in snarkos_node_bft.sync.
- The types involved
snarkos_node_tcp.helpers.connections.AR→snarkos_node_bft.sync.Syncsnarkos_node_tcp.helpers.connections.AW→snarkos_node_bft.sync.Sync
- Direction
- snarkos_node_tcp.helpers.connections uses snarkos_node_bft.sync, so a change to snarkos_node_bft.sync can break snarkos_node_tcp.helpers.connections, while a change to snarkos_node_tcp.helpers.connections can't break snarkos_node_bft.sync.
- 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→1 snarkos_utilities.node_data uses snarkos_node_rest.helpers.path✕
- Connections
- 1 pair of types, where a type in snarkos_utilities.node_data uses a type in snarkos_node_rest.helpers.path.
- The types involved
snarkos_utilities.node_data.NodeDataDir→snarkos_node_rest.helpers.path.Path
- Direction
- snarkos_utilities.node_data uses snarkos_node_rest.helpers.path, so a change to snarkos_node_rest.helpers.path can break snarkos_utilities.node_data, while a change to snarkos_utilities.node_data can't break snarkos_node_rest.helpers.path.
- Position
- Below the diagonal: snarkos_utilities.node_data uses a module listed above it, which is the healthy direction.
9→7 snarkos_node_tcp.tcp uses snarkos_node_tcp.helpers.connections✕
- Connections
- 4 pairs of types, where a type in snarkos_node_tcp.tcp uses a type in snarkos_node_tcp.helpers.connections.
- The types involved
snarkos_node_tcp.tcp.InnerTcp→snarkos_node_tcp.helpers.connections.Connectionssnarkos_node_tcp.tcp.Tcp→snarkos_node_tcp.helpers.connections.Connectionsnarkos_node_tcp.tcp.Tcp→snarkos_node_tcp.helpers.connections.ConnectionSidesnarkos_node_tcp.tcp.Tcp→snarkos_node_tcp.helpers.connections.DisconnectOrigin
- Direction
- snarkos_node_tcp.tcp uses snarkos_node_tcp.helpers.connections, so a change to snarkos_node_tcp.helpers.connections can break snarkos_node_tcp.tcp, while a change to snarkos_node_tcp.tcp can't break snarkos_node_tcp.helpers.connections.
- Position
- Below the diagonal: snarkos_node_tcp.tcp uses a module listed above it, which is the healthy direction.
9→20 snarkos_node_tcp.tcp uses snarkos_node_bft.sync part of a loop✕
- Connections
- 1 pair of types, where a type in snarkos_node_tcp.tcp uses a type in snarkos_node_bft.sync.
- The types involved
snarkos_node_tcp.tcp.ApplicationError→snarkos_node_bft.sync.Sync
- Direction
- snarkos_node_tcp.tcp uses snarkos_node_bft.sync, so a change to snarkos_node_bft.sync can break snarkos_node_tcp.tcp, while a change to snarkos_node_tcp.tcp can't break snarkos_node_bft.sync.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→34 snarkos_node_tcp.tcp uses snarkos_display part of a loop✕
- Connections
- 1 pair of types, where a type in snarkos_node_tcp.tcp uses a type in snarkos_display.
- The types involved
snarkos_node_tcp.tcp.ApplicationError→snarkos_display.Display
- Direction
- snarkos_node_tcp.tcp uses snarkos_display, so a change to snarkos_display can break snarkos_node_tcp.tcp, while a change to snarkos_node_tcp.tcp can't break snarkos_display.
- 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 snarkos_node_bft_events.disconnect uses snarkos_node_bft_events✕
- Connections
- 1 pair of types, where a type in snarkos_node_bft_events.disconnect uses a type in snarkos_node_bft_events.
- The types involved
snarkos_node_bft_events.disconnect.Disconnect→snarkos_node_bft_events.EventTrait
- Direction
- snarkos_node_bft_events.disconnect uses snarkos_node_bft_events, so a change to snarkos_node_bft_events can break snarkos_node_bft_events.disconnect, while a change to snarkos_node_bft_events.disconnect can't break snarkos_node_bft_events.
- Position
- Below the diagonal: snarkos_node_bft_events.disconnect uses a module listed above it, which is the healthy direction.
10→9 snarkos_node_bft_events.disconnect uses snarkos_node_tcp.tcp✕
- Connections
- 2 pairs of types, where a type in snarkos_node_bft_events.disconnect uses a type in snarkos_node_tcp.tcp.
- The types involved
snarkos_node_bft_events.disconnect.DisconnectReason→snarkos_node_tcp.tcp.ApplicationErrorsnarkos_node_bft_events.disconnect.DisconnectReason→snarkos_node_tcp.tcp.ConnectError
- Direction
- snarkos_node_bft_events.disconnect uses snarkos_node_tcp.tcp, so a change to snarkos_node_tcp.tcp can break snarkos_node_bft_events.disconnect, while a change to snarkos_node_bft_events.disconnect can't break snarkos_node_tcp.tcp.
- Position
- Below the diagonal: snarkos_node_bft_events.disconnect uses a module listed above it, which is the healthy direction.
10→34 snarkos_node_bft_events.disconnect uses snarkos_display part of a loop✕
- Connections
- 1 pair of types, where a type in snarkos_node_bft_events.disconnect uses a type in snarkos_display.
- The types involved
snarkos_node_bft_events.disconnect.DisconnectReason→snarkos_display.Display
- Direction
- snarkos_node_bft_events.disconnect uses snarkos_display, so a change to snarkos_display can break snarkos_node_bft_events.disconnect, while a change to snarkos_node_bft_events.disconnect can't break snarkos_display.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→9 snarkos_node_tcp uses snarkos_node_tcp.tcp✕
- Connections
- 1 pair of types, where a type in snarkos_node_tcp uses a type in snarkos_node_tcp.tcp.
- The types involved
snarkos_node_tcp.P2P→snarkos_node_tcp.tcp.Tcp
- Direction
- snarkos_node_tcp uses snarkos_node_tcp.tcp, so a change to snarkos_node_tcp.tcp can break snarkos_node_tcp, while a change to snarkos_node_tcp can't break snarkos_node_tcp.tcp.
- Position
- Below the diagonal: snarkos_node_tcp uses a module listed above it, which is the healthy direction.
12→1 snarkos_node_network.peering uses snarkos_node_rest.helpers.path✕
- Connections
- 1 pair of types, where a type in snarkos_node_network.peering uses a type in snarkos_node_rest.helpers.path.
- The types involved
snarkos_node_network.peering.PeerPoolHandling→snarkos_node_rest.helpers.path.Path
- Direction
- snarkos_node_network.peering uses snarkos_node_rest.helpers.path, so a change to snarkos_node_rest.helpers.path can break snarkos_node_network.peering, while a change to snarkos_node_network.peering can't break snarkos_node_rest.helpers.path.
- Position
- Below the diagonal: snarkos_node_network.peering uses a module listed above it, which is the healthy direction.
12→5 snarkos_node_network.peering uses snarkos_node_network.node_type✕
- Connections
- 1 pair of types, where a type in snarkos_node_network.peering uses a type in snarkos_node_network.node_type.
- The types involved
snarkos_node_network.peering.PeerPoolHandling→snarkos_node_network.node_type.NodeType
- Direction
- snarkos_node_network.peering uses snarkos_node_network.node_type, so a change to snarkos_node_network.node_type can break snarkos_node_network.peering, while a change to snarkos_node_network.peering can't break snarkos_node_network.node_type.
- Position
- Below the diagonal: snarkos_node_network.peering uses a module listed above it, which is the healthy direction.
12→9 snarkos_node_network.peering uses snarkos_node_tcp.tcp✕
- Connections
- 1 pair of types, where a type in snarkos_node_network.peering uses a type in snarkos_node_tcp.tcp.
- The types involved
snarkos_node_network.peering.PeeringError→snarkos_node_tcp.tcp.ApplicationError
- Direction
- snarkos_node_network.peering uses snarkos_node_tcp.tcp, so a change to snarkos_node_tcp.tcp can break snarkos_node_network.peering, while a change to snarkos_node_network.peering can't break snarkos_node_tcp.tcp.
- Position
- Below the diagonal: snarkos_node_network.peering uses a module listed above it, which is the healthy direction.
12→11 snarkos_node_network.peering uses snarkos_node_tcp✕
- Connections
- 1 pair of types, where a type in snarkos_node_network.peering uses a type in snarkos_node_tcp.
- The types involved
snarkos_node_network.peering.PeerPoolHandling→snarkos_node_tcp.P2P
- Direction
- snarkos_node_network.peering uses snarkos_node_tcp, so a change to snarkos_node_tcp can break snarkos_node_network.peering, while a change to snarkos_node_network.peering can't break snarkos_node_tcp.
- Position
- Below the diagonal: snarkos_node_network.peering uses a module listed above it, which is the healthy direction.
12→34 snarkos_node_network.peering uses snarkos_display part of a loop✕
- Connections
- 1 pair of types, where a type in snarkos_node_network.peering uses a type in snarkos_display.
- The types involved
snarkos_node_network.peering.PeeringError→snarkos_display.Display
- Direction
- snarkos_node_network.peering uses snarkos_display, so a change to snarkos_display can break snarkos_node_network.peering, while a change to snarkos_node_network.peering can't break snarkos_display.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→10 snarkos_node_router_messages uses snarkos_node_bft_events.disconnect✕
- Connections
- 1 pair of types, where a type in snarkos_node_router_messages uses a type in snarkos_node_bft_events.disconnect.
- The types involved
snarkos_node_router_messages.Message→snarkos_node_bft_events.disconnect.DisconnectReason
- Direction
- snarkos_node_router_messages uses snarkos_node_bft_events.disconnect, so a change to snarkos_node_bft_events.disconnect can break snarkos_node_router_messages, while a change to snarkos_node_router_messages can't break snarkos_node_bft_events.disconnect.
- Position
- Below the diagonal: snarkos_node_router_messages uses a module listed above it, which is the healthy direction.
14→7 snarkos_node_tcp.protocols.handshake uses snarkos_node_tcp.helpers.connections✕
- Connections
- 1 pair of types, where a type in snarkos_node_tcp.protocols.handshake uses a type in snarkos_node_tcp.helpers.connections.
- The types involved
snarkos_node_tcp.protocols.handshake.Handshake→snarkos_node_tcp.helpers.connections.Connection
- Direction
- snarkos_node_tcp.protocols.handshake uses snarkos_node_tcp.helpers.connections, so a change to snarkos_node_tcp.helpers.connections can break snarkos_node_tcp.protocols.handshake, while a change to snarkos_node_tcp.protocols.handshake can't break snarkos_node_tcp.helpers.connections.
- Position
- Below the diagonal: snarkos_node_tcp.protocols.handshake uses a module listed above it, which is the healthy direction.
14→11 snarkos_node_tcp.protocols.handshake uses snarkos_node_tcp✕
- Connections
- 1 pair of types, where a type in snarkos_node_tcp.protocols.handshake uses a type in snarkos_node_tcp.
- The types involved
snarkos_node_tcp.protocols.handshake.Handshake→snarkos_node_tcp.P2P
- Direction
- snarkos_node_tcp.protocols.handshake uses snarkos_node_tcp, so a change to snarkos_node_tcp can break snarkos_node_tcp.protocols.handshake, while a change to snarkos_node_tcp.protocols.handshake can't break snarkos_node_tcp.
- Position
- Below the diagonal: snarkos_node_tcp.protocols.handshake uses a module listed above it, which is the healthy direction.
15→11 snarkos_node_tcp.protocols.on_connect uses snarkos_node_tcp✕
- Connections
- 1 pair of types, where a type in snarkos_node_tcp.protocols.on_connect uses a type in snarkos_node_tcp.
- The types involved
snarkos_node_tcp.protocols.on_connect.OnConnect→snarkos_node_tcp.P2P
- Direction
- snarkos_node_tcp.protocols.on_connect uses snarkos_node_tcp, so a change to snarkos_node_tcp can break snarkos_node_tcp.protocols.on_connect, while a change to snarkos_node_tcp.protocols.on_connect can't break snarkos_node_tcp.
- Position
- Below the diagonal: snarkos_node_tcp.protocols.on_connect uses a module listed above it, which is the healthy direction.
16→4 snarkos_node_bft_events.block_request uses snarkos_node_bft_events✕
- Connections
- 1 pair of types, where a type in snarkos_node_bft_events.block_request uses a type in snarkos_node_bft_events.
- The types involved
snarkos_node_bft_events.block_request.BlockRequest→snarkos_node_bft_events.EventTrait
- Direction
- snarkos_node_bft_events.block_request uses snarkos_node_bft_events, so a change to snarkos_node_bft_events can break snarkos_node_bft_events.block_request, while a change to snarkos_node_bft_events.block_request can't break snarkos_node_bft_events.
- Position
- Below the diagonal: snarkos_node_bft_events.block_request uses a module listed above it, which is the healthy direction.
16→13 snarkos_node_bft_events.block_request uses snarkos_node_router_messages✕
- Connections
- 1 pair of types, where a type in snarkos_node_bft_events.block_request uses a type in snarkos_node_router_messages.
- The types involved
snarkos_node_bft_events.block_request.BlockRequest→snarkos_node_router_messages.MessageTrait
- Direction
- snarkos_node_bft_events.block_request uses snarkos_node_router_messages, so a change to snarkos_node_router_messages can break snarkos_node_bft_events.block_request, while a change to snarkos_node_bft_events.block_request can't break snarkos_node_router_messages.
- Position
- Below the diagonal: snarkos_node_bft_events.block_request uses a module listed above it, which is the healthy direction.
17→2 snarkos_node_router_messages.ping uses snarkos_node_sync_locators.block_locators✕
- Connections
- 1 pair of types, where a type in snarkos_node_router_messages.ping uses a type in snarkos_node_sync_locators.block_locators.
- The types involved
snarkos_node_router_messages.ping.Ping→snarkos_node_sync_locators.block_locators.BlockLocators
- Direction
- snarkos_node_router_messages.ping uses snarkos_node_sync_locators.block_locators, so a change to snarkos_node_sync_locators.block_locators can break snarkos_node_router_messages.ping, while a change to snarkos_node_router_messages.ping can't break snarkos_node_sync_locators.block_locators.
- Position
- Below the diagonal: snarkos_node_router_messages.ping uses a module listed above it, which is the healthy direction.
17→5 snarkos_node_router_messages.ping uses snarkos_node_network.node_type✕
- Connections
- 1 pair of types, where a type in snarkos_node_router_messages.ping uses a type in snarkos_node_network.node_type.
- The types involved
snarkos_node_router_messages.ping.Ping→snarkos_node_network.node_type.NodeType
- Direction
- snarkos_node_router_messages.ping uses snarkos_node_network.node_type, so a change to snarkos_node_network.node_type can break snarkos_node_router_messages.ping, while a change to snarkos_node_router_messages.ping can't break snarkos_node_network.node_type.
- Position
- Below the diagonal: snarkos_node_router_messages.ping uses a module listed above it, which is the healthy direction.
17→13 snarkos_node_router_messages.ping uses snarkos_node_router_messages✕
- Connections
- 1 pair of types, where a type in snarkos_node_router_messages.ping uses a type in snarkos_node_router_messages.
- The types involved
snarkos_node_router_messages.ping.Ping→snarkos_node_router_messages.MessageTrait
- Direction
- snarkos_node_router_messages.ping uses snarkos_node_router_messages, so a change to snarkos_node_router_messages can break snarkos_node_router_messages.ping, while a change to snarkos_node_router_messages.ping can't break snarkos_node_router_messages.
- Position
- Below the diagonal: snarkos_node_router_messages.ping uses a module listed above it, which is the healthy direction.
18→7 snarkos_node_tcp.protocols.reading uses snarkos_node_tcp.helpers.connections✕
- Connections
- 2 pairs of types, where a type in snarkos_node_tcp.protocols.reading uses a type in snarkos_node_tcp.helpers.connections.
- The types involved
snarkos_node_tcp.protocols.reading.Reading→snarkos_node_tcp.helpers.connections.ConnectionSidesnarkos_node_tcp.protocols.reading.ReadingInternal→snarkos_node_tcp.helpers.connections.Connection
- Direction
- snarkos_node_tcp.protocols.reading uses snarkos_node_tcp.helpers.connections, so a change to snarkos_node_tcp.helpers.connections can break snarkos_node_tcp.protocols.reading, while a change to snarkos_node_tcp.protocols.reading can't break snarkos_node_tcp.helpers.connections.
- Position
- Below the diagonal: snarkos_node_tcp.protocols.reading uses a module listed above it, which is the healthy direction.
18→9 snarkos_node_tcp.protocols.reading uses snarkos_node_tcp.tcp✕
- Connections
- 1 pair of types, where a type in snarkos_node_tcp.protocols.reading uses a type in snarkos_node_tcp.tcp.
- The types involved
snarkos_node_tcp.protocols.reading.CountingCodec→snarkos_node_tcp.tcp.Tcp
- Direction
- snarkos_node_tcp.protocols.reading uses snarkos_node_tcp.tcp, so a change to snarkos_node_tcp.tcp can break snarkos_node_tcp.protocols.reading, while a change to snarkos_node_tcp.protocols.reading can't break snarkos_node_tcp.tcp.
- Position
- Below the diagonal: snarkos_node_tcp.protocols.reading uses a module listed above it, which is the healthy direction.
18→11 snarkos_node_tcp.protocols.reading uses snarkos_node_tcp✕
- Connections
- 1 pair of types, where a type in snarkos_node_tcp.protocols.reading uses a type in snarkos_node_tcp.
- The types involved
snarkos_node_tcp.protocols.reading.Reading→snarkos_node_tcp.P2P
- Direction
- snarkos_node_tcp.protocols.reading uses snarkos_node_tcp, so a change to snarkos_node_tcp can break snarkos_node_tcp.protocols.reading, while a change to snarkos_node_tcp.protocols.reading can't break snarkos_node_tcp.
- Position
- Below the diagonal: snarkos_node_tcp.protocols.reading uses a module listed above it, which is the healthy direction.
18→13 snarkos_node_tcp.protocols.reading uses snarkos_node_router_messages✕
- Connections
- 1 pair of types, where a type in snarkos_node_tcp.protocols.reading uses a type in snarkos_node_router_messages.
- The types involved
snarkos_node_tcp.protocols.reading.Reading→snarkos_node_router_messages.Message
- Direction
- snarkos_node_tcp.protocols.reading uses snarkos_node_router_messages, so a change to snarkos_node_router_messages can break snarkos_node_tcp.protocols.reading, while a change to snarkos_node_tcp.protocols.reading can't break snarkos_node_router_messages.
- Position
- Below the diagonal: snarkos_node_tcp.protocols.reading uses a module listed above it, which is the healthy direction.
19→7 snarkos_node_tcp.protocols.writing uses snarkos_node_tcp.helpers.connections✕
- Connections
- 1 pair of types, where a type in snarkos_node_tcp.protocols.writing uses a type in snarkos_node_tcp.helpers.connections.
- The types involved
snarkos_node_tcp.protocols.writing.Writing→snarkos_node_tcp.helpers.connections.ConnectionSide
- Direction
- snarkos_node_tcp.protocols.writing uses snarkos_node_tcp.helpers.connections, so a change to snarkos_node_tcp.helpers.connections can break snarkos_node_tcp.protocols.writing, while a change to snarkos_node_tcp.protocols.writing can't break snarkos_node_tcp.helpers.connections.
- Position
- Below the diagonal: snarkos_node_tcp.protocols.writing uses a module listed above it, which is the healthy direction.
19→11 snarkos_node_tcp.protocols.writing uses snarkos_node_tcp✕
- Connections
- 1 pair of types, where a type in snarkos_node_tcp.protocols.writing uses a type in snarkos_node_tcp.
- The types involved
snarkos_node_tcp.protocols.writing.Writing→snarkos_node_tcp.P2P
- Direction
- snarkos_node_tcp.protocols.writing uses snarkos_node_tcp, so a change to snarkos_node_tcp can break snarkos_node_tcp.protocols.writing, while a change to snarkos_node_tcp.protocols.writing can't break snarkos_node_tcp.
- Position
- Below the diagonal: snarkos_node_tcp.protocols.writing uses a module listed above it, which is the healthy direction.
19→13 snarkos_node_tcp.protocols.writing uses snarkos_node_router_messages✕
- Connections
- 2 pairs of types, where a type in snarkos_node_tcp.protocols.writing uses a type in snarkos_node_router_messages.
- The types involved
snarkos_node_tcp.protocols.writing.Writing→snarkos_node_router_messages.Messagesnarkos_node_tcp.protocols.writing.WritingInternal→snarkos_node_router_messages.Message
- Direction
- snarkos_node_tcp.protocols.writing uses snarkos_node_router_messages, so a change to snarkos_node_router_messages can break snarkos_node_tcp.protocols.writing, while a change to snarkos_node_tcp.protocols.writing can't break snarkos_node_router_messages.
- Position
- Below the diagonal: snarkos_node_tcp.protocols.writing uses a module listed above it, which is the healthy direction.
20→2 snarkos_node_bft.sync uses snarkos_node_sync_locators.block_locators✕
- Connections
- 1 pair of types, where a type in snarkos_node_bft.sync uses a type in snarkos_node_sync_locators.block_locators.
- The types involved
snarkos_node_bft.sync.Sync→snarkos_node_sync_locators.block_locators.BlockLocators
- Direction
- snarkos_node_bft.sync uses snarkos_node_sync_locators.block_locators, so a change to snarkos_node_sync_locators.block_locators can break snarkos_node_bft.sync, while a change to snarkos_node_bft.sync can't break snarkos_node_sync_locators.block_locators.
- Position
- Below the diagonal: snarkos_node_bft.sync uses a module listed above it, which is the healthy direction.
20→3 snarkos_node_bft.sync uses snarkos_node_bft.helpers.channels✕
- Connections
- 1 pair of types, where a type in snarkos_node_bft.sync uses a type in snarkos_node_bft.helpers.channels.
- The types involved
snarkos_node_bft.sync.Sync→snarkos_node_bft.helpers.channels.SyncReceiver
- Direction
- snarkos_node_bft.sync uses snarkos_node_bft.helpers.channels, so a change to snarkos_node_bft.helpers.channels can break snarkos_node_bft.sync, while a change to snarkos_node_bft.sync can't break snarkos_node_bft.helpers.channels.
- Position
- Below the diagonal: snarkos_node_bft.sync uses a module listed above it, which is the healthy direction.
20→6 snarkos_node_bft.sync uses snarkos_node_sync.block_sync✕
- Connections
- 1 pair of types, where a type in snarkos_node_bft.sync uses a type in snarkos_node_sync.block_sync.
- The types involved
snarkos_node_bft.sync.Sync→snarkos_node_sync.block_sync.BlockSync
- Direction
- snarkos_node_bft.sync uses snarkos_node_sync.block_sync, so a change to snarkos_node_sync.block_sync can break snarkos_node_bft.sync, while a change to snarkos_node_bft.sync can't break snarkos_node_sync.block_sync.
- Position
- Below the diagonal: snarkos_node_bft.sync uses a module listed above it, which is the healthy direction.
20→17 snarkos_node_bft.sync uses snarkos_node_router_messages.ping✕
- Connections
- 1 pair of types, where a type in snarkos_node_bft.sync uses a type in snarkos_node_router_messages.ping.
- The types involved
snarkos_node_bft.sync.Sync→snarkos_node_router_messages.ping.Ping
- Direction
- snarkos_node_bft.sync uses snarkos_node_router_messages.ping, so a change to snarkos_node_router_messages.ping can break snarkos_node_bft.sync, while a change to snarkos_node_bft.sync can't break snarkos_node_router_messages.ping.
- Position
- Below the diagonal: snarkos_node_bft.sync uses a module listed above it, which is the healthy direction.
20→22 snarkos_node_bft.sync uses snarkos_node_bft.gateway part of a loop✕
- Connections
- 1 pair of types, where a type in snarkos_node_bft.sync uses a type in snarkos_node_bft.gateway.
- The types involved
snarkos_node_bft.sync.Sync→snarkos_node_bft.gateway.Gateway
- Direction
- snarkos_node_bft.sync uses snarkos_node_bft.gateway, so a change to snarkos_node_bft.gateway can break snarkos_node_bft.sync, while a change to snarkos_node_bft.sync can't break snarkos_node_bft.gateway.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
21→2 snarkos_node_router uses snarkos_node_sync_locators.block_locators✕
- Connections
- 1 pair of types, where a type in snarkos_node_router uses a type in snarkos_node_sync_locators.block_locators.
- The types involved
snarkos_node_router.Router→snarkos_node_sync_locators.block_locators.BlockLocators
- Direction
- snarkos_node_router uses snarkos_node_sync_locators.block_locators, so a change to snarkos_node_sync_locators.block_locators can break snarkos_node_router, while a change to snarkos_node_router can't break snarkos_node_sync_locators.block_locators.
- Position
- Below the diagonal: snarkos_node_router uses a module listed above it, which is the healthy direction.
21→5 snarkos_node_router uses snarkos_node_network.node_type✕
- Connections
- 2 pairs of types, where a type in snarkos_node_router uses a type in snarkos_node_network.node_type.
- The types involved
snarkos_node_router.InnerRouter→snarkos_node_network.node_type.NodeTypesnarkos_node_router.Router→snarkos_node_network.node_type.NodeType
- Direction
- snarkos_node_router uses snarkos_node_network.node_type, so a change to snarkos_node_network.node_type can break snarkos_node_router, while a change to snarkos_node_router can't break snarkos_node_network.node_type.
- Position
- Below the diagonal: snarkos_node_router uses a module listed above it, which is the healthy direction.
21→7 snarkos_node_router uses snarkos_node_tcp.helpers.connections✕
- Connections
- 1 pair of types, where a type in snarkos_node_router uses a type in snarkos_node_tcp.helpers.connections.
- The types involved
snarkos_node_router.Router→snarkos_node_tcp.helpers.connections.ConnectionSide
- Direction
- snarkos_node_router uses snarkos_node_tcp.helpers.connections, so a change to snarkos_node_tcp.helpers.connections can break snarkos_node_router, while a change to snarkos_node_router can't break snarkos_node_tcp.helpers.connections.
- Position
- Below the diagonal: snarkos_node_router uses a module listed above it, which is the healthy direction.
21→8 snarkos_node_router uses snarkos_utilities.node_data✕
- Connections
- 2 pairs of types, where a type in snarkos_node_router uses a type in snarkos_utilities.node_data.
- The types involved
snarkos_node_router.InnerRouter→snarkos_utilities.node_data.NodeDataDirsnarkos_node_router.Router→snarkos_utilities.node_data.NodeDataDir
- Direction
- snarkos_node_router uses snarkos_utilities.node_data, so a change to snarkos_utilities.node_data can break snarkos_node_router, while a change to snarkos_node_router can't break snarkos_utilities.node_data.
- Position
- Below the diagonal: snarkos_node_router uses a module listed above it, which is the healthy direction.
21→9 snarkos_node_router uses snarkos_node_tcp.tcp✕
- Connections
- 2 pairs of types, where a type in snarkos_node_router uses a type in snarkos_node_tcp.tcp.
- The types involved
snarkos_node_router.InnerRouter→snarkos_node_tcp.tcp.Tcpsnarkos_node_router.Router→snarkos_node_tcp.tcp.Tcp
- Direction
- snarkos_node_router uses snarkos_node_tcp.tcp, so a change to snarkos_node_tcp.tcp can break snarkos_node_router, while a change to snarkos_node_router can't break snarkos_node_tcp.tcp.
- Position
- Below the diagonal: snarkos_node_router uses a module listed above it, which is the healthy direction.
21→10 snarkos_node_router uses snarkos_node_bft_events.disconnect✕
- Connections
- 1 pair of types, where a type in snarkos_node_router uses a type in snarkos_node_bft_events.disconnect.
- The types involved
snarkos_node_router.Router→snarkos_node_bft_events.disconnect.DisconnectReason
- Direction
- snarkos_node_router uses snarkos_node_bft_events.disconnect, so a change to snarkos_node_bft_events.disconnect can break snarkos_node_router, while a change to snarkos_node_router can't break snarkos_node_bft_events.disconnect.
- Position
- Below the diagonal: snarkos_node_router uses a module listed above it, which is the healthy direction.
21→11 snarkos_node_router uses snarkos_node_tcp✕
- Connections
- 1 pair of types, where a type in snarkos_node_router uses a type in snarkos_node_tcp.
- The types involved
snarkos_node_router.Router→snarkos_node_tcp.P2P
- Direction
- snarkos_node_router uses snarkos_node_tcp, so a change to snarkos_node_tcp can break snarkos_node_router, while a change to snarkos_node_router can't break snarkos_node_tcp.
- Position
- Below the diagonal: snarkos_node_router uses a module listed above it, which is the healthy direction.
21→12 snarkos_node_router uses snarkos_node_network.peering✕
- Connections
- 1 pair of types, where a type in snarkos_node_router uses a type in snarkos_node_network.peering.
- The types involved
snarkos_node_router.Router→snarkos_node_network.peering.PeerPoolHandling
- Direction
- snarkos_node_router uses snarkos_node_network.peering, so a change to snarkos_node_network.peering can break snarkos_node_router, while a change to snarkos_node_router can't break snarkos_node_network.peering.
- Position
- Below the diagonal: snarkos_node_router uses a module listed above it, which is the healthy direction.
21→13 snarkos_node_router uses snarkos_node_router_messages✕
- Connections
- 1 pair of types, where a type in snarkos_node_router uses a type in snarkos_node_router_messages.
- The types involved
snarkos_node_router.Router→snarkos_node_router_messages.Message
- Direction
- snarkos_node_router uses snarkos_node_router_messages, so a change to snarkos_node_router_messages can break snarkos_node_router, while a change to snarkos_node_router can't break snarkos_node_router_messages.
- Position
- Below the diagonal: snarkos_node_router uses a module listed above it, which is the healthy direction.
21→19 snarkos_node_router uses snarkos_node_tcp.protocols.writing✕
- Connections
- 1 pair of types, where a type in snarkos_node_router uses a type in snarkos_node_tcp.protocols.writing.
- The types involved
snarkos_node_router.Router→snarkos_node_tcp.protocols.writing.Writing
- Direction
- snarkos_node_router uses snarkos_node_tcp.protocols.writing, so a change to snarkos_node_tcp.protocols.writing can break snarkos_node_router, while a change to snarkos_node_router can't break snarkos_node_tcp.protocols.writing.
- Position
- Below the diagonal: snarkos_node_router uses a module listed above it, which is the healthy direction.
21→35 snarkos_node_router uses snarkos_account part of a loop✕
- Connections
- 2 pairs of types, where a type in snarkos_node_router uses a type in snarkos_account.
- The types involved
snarkos_node_router.InnerRouter→snarkos_account.Accountsnarkos_node_router.Router→snarkos_account.Account
- Direction
- snarkos_node_router uses snarkos_account, so a change to snarkos_account can break snarkos_node_router, while a change to snarkos_node_router can't break snarkos_account.
- 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→3 snarkos_node_bft.gateway uses snarkos_node_bft.helpers.channels✕
- Connections
- 3 pairs of types, where a type in snarkos_node_bft.gateway uses a type in snarkos_node_bft.helpers.channels.
- The types involved
snarkos_node_bft.gateway.Gateway→snarkos_node_bft.helpers.channels.PrimarySendersnarkos_node_bft.gateway.Gateway→snarkos_node_bft.helpers.channels.SyncSendersnarkos_node_bft.gateway.Gateway→snarkos_node_bft.helpers.channels.WorkerSender
- Direction
- snarkos_node_bft.gateway uses snarkos_node_bft.helpers.channels, so a change to snarkos_node_bft.helpers.channels can break snarkos_node_bft.gateway, while a change to snarkos_node_bft.gateway can't break snarkos_node_bft.helpers.channels.
- Position
- Below the diagonal: snarkos_node_bft.gateway uses a module listed above it, which is the healthy direction.
22→4 snarkos_node_bft.gateway uses snarkos_node_bft_events✕
- Connections
- 2 pairs of types, where a type in snarkos_node_bft.gateway uses a type in snarkos_node_bft_events.
- The types involved
snarkos_node_bft.gateway.Gateway→snarkos_node_bft_events.Eventsnarkos_node_bft.gateway.Transport→snarkos_node_bft_events.Event
- Direction
- snarkos_node_bft.gateway uses snarkos_node_bft_events, so a change to snarkos_node_bft_events can break snarkos_node_bft.gateway, while a change to snarkos_node_bft.gateway can't break snarkos_node_bft_events.
- Position
- Below the diagonal: snarkos_node_bft.gateway uses a module listed above it, which is the healthy direction.
22→5 snarkos_node_bft.gateway uses snarkos_node_network.node_type✕
- Connections
- 1 pair of types, where a type in snarkos_node_bft.gateway uses a type in snarkos_node_network.node_type.
- The types involved
snarkos_node_bft.gateway.Gateway→snarkos_node_network.node_type.NodeType
- Direction
- snarkos_node_bft.gateway uses snarkos_node_network.node_type, so a change to snarkos_node_network.node_type can break snarkos_node_bft.gateway, while a change to snarkos_node_bft.gateway can't break snarkos_node_network.node_type.
- Position
- Below the diagonal: snarkos_node_bft.gateway uses a module listed above it, which is the healthy direction.
22→7 snarkos_node_bft.gateway uses snarkos_node_tcp.helpers.connections✕
- Connections
- 3 pairs of types, where a type in snarkos_node_bft.gateway uses a type in snarkos_node_tcp.helpers.connections.
- The types involved
snarkos_node_bft.gateway.Gateway→snarkos_node_tcp.helpers.connections.Connectionsnarkos_node_bft.gateway.Gateway→snarkos_node_tcp.helpers.connections.ConnectionSidesnarkos_node_bft.gateway.Gateway→snarkos_node_tcp.helpers.connections.DisconnectOrigin
- Direction
- snarkos_node_bft.gateway uses snarkos_node_tcp.helpers.connections, so a change to snarkos_node_tcp.helpers.connections can break snarkos_node_bft.gateway, while a change to snarkos_node_bft.gateway can't break snarkos_node_tcp.helpers.connections.
- Position
- Below the diagonal: snarkos_node_bft.gateway uses a module listed above it, which is the healthy direction.
22→8 snarkos_node_bft.gateway uses snarkos_utilities.node_data✕
- Connections
- 2 pairs of types, where a type in snarkos_node_bft.gateway uses a type in snarkos_utilities.node_data.
- The types involved
snarkos_node_bft.gateway.Gateway→snarkos_utilities.node_data.NodeDataDirsnarkos_node_bft.gateway.InnerGateway→snarkos_utilities.node_data.NodeDataDir
- Direction
- snarkos_node_bft.gateway uses snarkos_utilities.node_data, so a change to snarkos_utilities.node_data can break snarkos_node_bft.gateway, while a change to snarkos_node_bft.gateway can't break snarkos_utilities.node_data.
- Position
- Below the diagonal: snarkos_node_bft.gateway uses a module listed above it, which is the healthy direction.
22→9 snarkos_node_bft.gateway uses snarkos_node_tcp.tcp✕
- Connections
- 2 pairs of types, where a type in snarkos_node_bft.gateway uses a type in snarkos_node_tcp.tcp.
- The types involved
snarkos_node_bft.gateway.Gateway→snarkos_node_tcp.tcp.Tcpsnarkos_node_bft.gateway.InnerGateway→snarkos_node_tcp.tcp.Tcp
- Direction
- snarkos_node_bft.gateway uses snarkos_node_tcp.tcp, so a change to snarkos_node_tcp.tcp can break snarkos_node_bft.gateway, while a change to snarkos_node_bft.gateway can't break snarkos_node_tcp.tcp.
- Position
- Below the diagonal: snarkos_node_bft.gateway uses a module listed above it, which is the healthy direction.
22→10 snarkos_node_bft.gateway uses snarkos_node_bft_events.disconnect✕
- Connections
- 3 pairs of types, where a type in snarkos_node_bft.gateway uses a type in snarkos_node_bft_events.disconnect.
- The types involved
snarkos_node_bft.gateway.Gateway→snarkos_node_bft_events.disconnect.Disconnectsnarkos_node_bft.gateway.Gateway→snarkos_node_bft_events.disconnect.DisconnectReasonsnarkos_node_bft.gateway.gateway$module→snarkos_node_bft_events.disconnect.DisconnectReason
- Direction
- snarkos_node_bft.gateway uses snarkos_node_bft_events.disconnect, so a change to snarkos_node_bft_events.disconnect can break snarkos_node_bft.gateway, while a change to snarkos_node_bft.gateway can't break snarkos_node_bft_events.disconnect.
- Position
- Below the diagonal: snarkos_node_bft.gateway uses a module listed above it, which is the healthy direction.
22→11 snarkos_node_bft.gateway uses snarkos_node_tcp✕
- Connections
- 1 pair of types, where a type in snarkos_node_bft.gateway uses a type in snarkos_node_tcp.
- The types involved
snarkos_node_bft.gateway.Gateway→snarkos_node_tcp.P2P
- Direction
- snarkos_node_bft.gateway uses snarkos_node_tcp, so a change to snarkos_node_tcp can break snarkos_node_bft.gateway, while a change to snarkos_node_bft.gateway can't break snarkos_node_tcp.
- Position
- Below the diagonal: snarkos_node_bft.gateway uses a module listed above it, which is the healthy direction.
22→12 snarkos_node_bft.gateway uses snarkos_node_network.peering✕
- Connections
- 1 pair of types, where a type in snarkos_node_bft.gateway uses a type in snarkos_node_network.peering.
- The types involved
snarkos_node_bft.gateway.Gateway→snarkos_node_network.peering.PeerPoolHandling
- Direction
- snarkos_node_bft.gateway uses snarkos_node_network.peering, so a change to snarkos_node_network.peering can break snarkos_node_bft.gateway, while a change to snarkos_node_bft.gateway can't break snarkos_node_network.peering.
- Position
- Below the diagonal: snarkos_node_bft.gateway uses a module listed above it, which is the healthy direction.
22→13 snarkos_node_bft.gateway uses snarkos_node_router_messages✕
- Connections
- 1 pair of types, where a type in snarkos_node_bft.gateway uses a type in snarkos_node_router_messages.
- The types involved
snarkos_node_bft.gateway.Gateway→snarkos_node_router_messages.Message
- Direction
- snarkos_node_bft.gateway uses snarkos_node_router_messages, so a change to snarkos_node_router_messages can break snarkos_node_bft.gateway, while a change to snarkos_node_bft.gateway can't break snarkos_node_router_messages.
- Position
- Below the diagonal: snarkos_node_bft.gateway uses a module listed above it, which is the healthy direction.
22→14 snarkos_node_bft.gateway uses snarkos_node_tcp.protocols.handshake✕
- Connections
- 1 pair of types, where a type in snarkos_node_bft.gateway uses a type in snarkos_node_tcp.protocols.handshake.
- The types involved
snarkos_node_bft.gateway.Gateway→snarkos_node_tcp.protocols.handshake.Handshake
- Direction
- snarkos_node_bft.gateway uses snarkos_node_tcp.protocols.handshake, so a change to snarkos_node_tcp.protocols.handshake can break snarkos_node_bft.gateway, while a change to snarkos_node_bft.gateway can't break snarkos_node_tcp.protocols.handshake.
- Position
- Below the diagonal: snarkos_node_bft.gateway uses a module listed above it, which is the healthy direction.
22→15 snarkos_node_bft.gateway uses snarkos_node_tcp.protocols.on_connect✕
- Connections
- 1 pair of types, where a type in snarkos_node_bft.gateway uses a type in snarkos_node_tcp.protocols.on_connect.
- The types involved
snarkos_node_bft.gateway.Gateway→snarkos_node_tcp.protocols.on_connect.OnConnect
- Direction
- snarkos_node_bft.gateway uses snarkos_node_tcp.protocols.on_connect, so a change to snarkos_node_tcp.protocols.on_connect can break snarkos_node_bft.gateway, while a change to snarkos_node_bft.gateway can't break snarkos_node_tcp.protocols.on_connect.
- Position
- Below the diagonal: snarkos_node_bft.gateway uses a module listed above it, which is the healthy direction.
22→18 snarkos_node_bft.gateway uses snarkos_node_tcp.protocols.reading✕
- Connections
- 1 pair of types, where a type in snarkos_node_bft.gateway uses a type in snarkos_node_tcp.protocols.reading.
- The types involved
snarkos_node_bft.gateway.Gateway→snarkos_node_tcp.protocols.reading.Reading
- Direction
- snarkos_node_bft.gateway uses snarkos_node_tcp.protocols.reading, so a change to snarkos_node_tcp.protocols.reading can break snarkos_node_bft.gateway, while a change to snarkos_node_bft.gateway can't break snarkos_node_tcp.protocols.reading.
- Position
- Below the diagonal: snarkos_node_bft.gateway uses a module listed above it, which is the healthy direction.
22→19 snarkos_node_bft.gateway uses snarkos_node_tcp.protocols.writing✕
- Connections
- 1 pair of types, where a type in snarkos_node_bft.gateway uses a type in snarkos_node_tcp.protocols.writing.
- The types involved
snarkos_node_bft.gateway.Gateway→snarkos_node_tcp.protocols.writing.Writing
- Direction
- snarkos_node_bft.gateway uses snarkos_node_tcp.protocols.writing, so a change to snarkos_node_tcp.protocols.writing can break snarkos_node_bft.gateway, while a change to snarkos_node_bft.gateway can't break snarkos_node_tcp.protocols.writing.
- Position
- Below the diagonal: snarkos_node_bft.gateway uses a module listed above it, which is the healthy direction.
22→20 snarkos_node_bft.gateway uses snarkos_node_bft.sync✕
- Connections
- 1 pair of types, where a type in snarkos_node_bft.gateway uses a type in snarkos_node_bft.sync.
- The types involved
snarkos_node_bft.gateway.Transport→snarkos_node_bft.sync.Sync
- Direction
- snarkos_node_bft.gateway uses snarkos_node_bft.sync, so a change to snarkos_node_bft.sync can break snarkos_node_bft.gateway, while a change to snarkos_node_bft.gateway can't break snarkos_node_bft.sync.
- Position
- Below the diagonal: snarkos_node_bft.gateway uses a module listed above it, which is the healthy direction.
22→35 snarkos_node_bft.gateway uses snarkos_account part of a loop✕
- Connections
- 2 pairs of types, where a type in snarkos_node_bft.gateway uses a type in snarkos_account.
- The types involved
snarkos_node_bft.gateway.Gateway→snarkos_account.Accountsnarkos_node_bft.gateway.InnerGateway→snarkos_account.Account
- Direction
- snarkos_node_bft.gateway uses snarkos_account, so a change to snarkos_account can break snarkos_node_bft.gateway, while a change to snarkos_node_bft.gateway can't break snarkos_account.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→13 snarkos_node_router.outbound uses snarkos_node_router_messages✕
- Connections
- 1 pair of types, where a type in snarkos_node_router.outbound uses a type in snarkos_node_router_messages.
- The types involved
snarkos_node_router.outbound.Outbound→snarkos_node_router_messages.Message
- Direction
- snarkos_node_router.outbound uses snarkos_node_router_messages, so a change to snarkos_node_router_messages can break snarkos_node_router.outbound, while a change to snarkos_node_router.outbound can't break snarkos_node_router_messages.
- Position
- Below the diagonal: snarkos_node_router.outbound uses a module listed above it, which is the healthy direction.
23→21 snarkos_node_router.outbound uses snarkos_node_router✕
- Connections
- 1 pair of types, where a type in snarkos_node_router.outbound uses a type in snarkos_node_router.
- The types involved
snarkos_node_router.outbound.Outbound→snarkos_node_router.Router
- Direction
- snarkos_node_router.outbound uses snarkos_node_router, so a change to snarkos_node_router can break snarkos_node_router.outbound, while a change to snarkos_node_router.outbound can't break snarkos_node_router.
- Position
- Below the diagonal: snarkos_node_router.outbound uses a module listed above it, which is the healthy direction.
24→20 snarkos_utilities.signals uses snarkos_node_bft.sync✕
- Connections
- 1 pair of types, where a type in snarkos_utilities.signals uses a type in snarkos_node_bft.sync.
- The types involved
snarkos_utilities.signals.Stoppable→snarkos_node_bft.sync.Sync
- Direction
- snarkos_utilities.signals uses snarkos_node_bft.sync, so a change to snarkos_node_bft.sync can break snarkos_utilities.signals, while a change to snarkos_utilities.signals can't break snarkos_node_bft.sync.
- Position
- Below the diagonal: snarkos_utilities.signals uses a module listed above it, which is the healthy direction.
25→3 snarkos_node_bft.primary uses snarkos_node_bft.helpers.channels✕
- Connections
- 2 pairs of types, where a type in snarkos_node_bft.primary uses a type in snarkos_node_bft.helpers.channels.
- The types involved
snarkos_node_bft.primary.Primary→snarkos_node_bft.helpers.channels.PrimaryReceiversnarkos_node_bft.primary.Primary→snarkos_node_bft.helpers.channels.PrimarySender
- Direction
- snarkos_node_bft.primary uses snarkos_node_bft.helpers.channels, so a change to snarkos_node_bft.helpers.channels can break snarkos_node_bft.primary, while a change to snarkos_node_bft.primary can't break snarkos_node_bft.helpers.channels.
- Position
- Below the diagonal: snarkos_node_bft.primary uses a module listed above it, which is the healthy direction.
25→6 snarkos_node_bft.primary uses snarkos_node_sync.block_sync✕
- Connections
- 1 pair of types, where a type in snarkos_node_bft.primary uses a type in snarkos_node_sync.block_sync.
- The types involved
snarkos_node_bft.primary.Primary→snarkos_node_sync.block_sync.BlockSync
- Direction
- snarkos_node_bft.primary uses snarkos_node_sync.block_sync, so a change to snarkos_node_sync.block_sync can break snarkos_node_bft.primary, while a change to snarkos_node_bft.primary can't break snarkos_node_sync.block_sync.
- Position
- Below the diagonal: snarkos_node_bft.primary uses a module listed above it, which is the healthy direction.
25→8 snarkos_node_bft.primary uses snarkos_utilities.node_data✕
- Connections
- 1 pair of types, where a type in snarkos_node_bft.primary uses a type in snarkos_utilities.node_data.
- The types involved
snarkos_node_bft.primary.Primary→snarkos_utilities.node_data.NodeDataDir
- Direction
- snarkos_node_bft.primary uses snarkos_utilities.node_data, so a change to snarkos_utilities.node_data can break snarkos_node_bft.primary, while a change to snarkos_node_bft.primary can't break snarkos_utilities.node_data.
- Position
- Below the diagonal: snarkos_node_bft.primary uses a module listed above it, which is the healthy direction.
25→17 snarkos_node_bft.primary uses snarkos_node_router_messages.ping✕
- Connections
- 1 pair of types, where a type in snarkos_node_bft.primary uses a type in snarkos_node_router_messages.ping.
- The types involved
snarkos_node_bft.primary.Primary→snarkos_node_router_messages.ping.Ping
- Direction
- snarkos_node_bft.primary uses snarkos_node_router_messages.ping, so a change to snarkos_node_router_messages.ping can break snarkos_node_bft.primary, while a change to snarkos_node_bft.primary can't break snarkos_node_router_messages.ping.
- Position
- Below the diagonal: snarkos_node_bft.primary uses a module listed above it, which is the healthy direction.
25→20 snarkos_node_bft.primary uses snarkos_node_bft.sync✕
- Connections
- 2 pairs of types, where a type in snarkos_node_bft.primary uses a type in snarkos_node_bft.sync.
- The types involved
snarkos_node_bft.primary.Primary→snarkos_node_bft.sync.Syncsnarkos_node_bft.primary.PrimaryCallback→snarkos_node_bft.sync.Sync
- Direction
- snarkos_node_bft.primary uses snarkos_node_bft.sync, so a change to snarkos_node_bft.sync can break snarkos_node_bft.primary, while a change to snarkos_node_bft.primary can't break snarkos_node_bft.sync.
- Position
- Below the diagonal: snarkos_node_bft.primary uses a module listed above it, which is the healthy direction.
25→22 snarkos_node_bft.primary uses snarkos_node_bft.gateway✕
- Connections
- 1 pair of types, where a type in snarkos_node_bft.primary uses a type in snarkos_node_bft.gateway.
- The types involved
snarkos_node_bft.primary.Primary→snarkos_node_bft.gateway.Gateway
- Direction
- snarkos_node_bft.primary uses snarkos_node_bft.gateway, so a change to snarkos_node_bft.gateway can break snarkos_node_bft.primary, while a change to snarkos_node_bft.primary can't break snarkos_node_bft.gateway.
- Position
- Below the diagonal: snarkos_node_bft.primary uses a module listed above it, which is the healthy direction.
25→35 snarkos_node_bft.primary uses snarkos_account part of a loop✕
- Connections
- 1 pair of types, where a type in snarkos_node_bft.primary uses a type in snarkos_account.
- The types involved
snarkos_node_bft.primary.Primary→snarkos_account.Account
- Direction
- snarkos_node_bft.primary uses snarkos_account, so a change to snarkos_account can break snarkos_node_bft.primary, while a change to snarkos_node_bft.primary can't break snarkos_account.
- 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→3 snarkos_node_bft.worker uses snarkos_node_bft.helpers.channels✕
- Connections
- 1 pair of types, where a type in snarkos_node_bft.worker uses a type in snarkos_node_bft.helpers.channels.
- The types involved
snarkos_node_bft.worker.Worker→snarkos_node_bft.helpers.channels.WorkerReceiver
- Direction
- snarkos_node_bft.worker uses snarkos_node_bft.helpers.channels, so a change to snarkos_node_bft.helpers.channels can break snarkos_node_bft.worker, while a change to snarkos_node_bft.worker can't break snarkos_node_bft.helpers.channels.
- Position
- Below the diagonal: snarkos_node_bft.worker uses a module listed above it, which is the healthy direction.
26→22 snarkos_node_bft.worker uses snarkos_node_bft.gateway✕
- Connections
- 1 pair of types, where a type in snarkos_node_bft.worker uses a type in snarkos_node_bft.gateway.
- The types involved
snarkos_node_bft.worker.Worker→snarkos_node_bft.gateway.Gateway
- Direction
- snarkos_node_bft.worker uses snarkos_node_bft.gateway, so a change to snarkos_node_bft.gateway can break snarkos_node_bft.worker, while a change to snarkos_node_bft.worker can't break snarkos_node_bft.gateway.
- Position
- Below the diagonal: snarkos_node_bft.worker uses a module listed above it, which is the healthy direction.
27→23 snarkos_node_router.heartbeat uses snarkos_node_router.outbound✕
- Connections
- 1 pair of types, where a type in snarkos_node_router.heartbeat uses a type in snarkos_node_router.outbound.
- The types involved
snarkos_node_router.heartbeat.Heartbeat→snarkos_node_router.outbound.Outbound
- Direction
- snarkos_node_router.heartbeat uses snarkos_node_router.outbound, so a change to snarkos_node_router.outbound can break snarkos_node_router.heartbeat, while a change to snarkos_node_router.heartbeat can't break snarkos_node_router.outbound.
- Position
- Below the diagonal: snarkos_node_router.heartbeat uses a module listed above it, which is the healthy direction.
28→13 snarkos_node_router.inbound uses snarkos_node_router_messages✕
- Connections
- 1 pair of types, where a type in snarkos_node_router.inbound uses a type in snarkos_node_router_messages.
- The types involved
snarkos_node_router.inbound.Inbound→snarkos_node_router_messages.Message
- Direction
- snarkos_node_router.inbound uses snarkos_node_router_messages, so a change to snarkos_node_router_messages can break snarkos_node_router.inbound, while a change to snarkos_node_router.inbound can't break snarkos_node_router_messages.
- Position
- Below the diagonal: snarkos_node_router.inbound uses a module listed above it, which is the healthy direction.
28→16 snarkos_node_router.inbound uses snarkos_node_bft_events.block_request✕
- Connections
- 1 pair of types, where a type in snarkos_node_router.inbound uses a type in snarkos_node_bft_events.block_request.
- The types involved
snarkos_node_router.inbound.Inbound→snarkos_node_bft_events.block_request.BlockRequest
- Direction
- snarkos_node_router.inbound uses snarkos_node_bft_events.block_request, so a change to snarkos_node_bft_events.block_request can break snarkos_node_router.inbound, while a change to snarkos_node_router.inbound can't break snarkos_node_bft_events.block_request.
- Position
- Below the diagonal: snarkos_node_router.inbound uses a module listed above it, which is the healthy direction.
28→17 snarkos_node_router.inbound uses snarkos_node_router_messages.ping✕
- Connections
- 1 pair of types, where a type in snarkos_node_router.inbound uses a type in snarkos_node_router_messages.ping.
- The types involved
snarkos_node_router.inbound.Inbound→snarkos_node_router_messages.ping.Ping
- Direction
- snarkos_node_router.inbound uses snarkos_node_router_messages.ping, so a change to snarkos_node_router_messages.ping can break snarkos_node_router.inbound, while a change to snarkos_node_router.inbound can't break snarkos_node_router_messages.ping.
- Position
- Below the diagonal: snarkos_node_router.inbound uses a module listed above it, which is the healthy direction.
28→18 snarkos_node_router.inbound uses snarkos_node_tcp.protocols.reading✕
- Connections
- 1 pair of types, where a type in snarkos_node_router.inbound uses a type in snarkos_node_tcp.protocols.reading.
- The types involved
snarkos_node_router.inbound.Inbound→snarkos_node_tcp.protocols.reading.Reading
- Direction
- snarkos_node_router.inbound uses snarkos_node_tcp.protocols.reading, so a change to snarkos_node_tcp.protocols.reading can break snarkos_node_router.inbound, while a change to snarkos_node_router.inbound can't break snarkos_node_tcp.protocols.reading.
- Position
- Below the diagonal: snarkos_node_router.inbound uses a module listed above it, which is the healthy direction.
28→23 snarkos_node_router.inbound uses snarkos_node_router.outbound✕
- Connections
- 1 pair of types, where a type in snarkos_node_router.inbound uses a type in snarkos_node_router.outbound.
- The types involved
snarkos_node_router.inbound.Inbound→snarkos_node_router.outbound.Outbound
- Direction
- snarkos_node_router.inbound uses snarkos_node_router.outbound, so a change to snarkos_node_router.outbound can break snarkos_node_router.inbound, while a change to snarkos_node_router.inbound can't break snarkos_node_router.outbound.
- Position
- Below the diagonal: snarkos_node_router.inbound uses a module listed above it, which is the healthy direction.
29→3 snarkos_node_bft.bft uses snarkos_node_bft.helpers.channels✕
- Connections
- 3 pairs of types, where a type in snarkos_node_bft.bft uses a type in snarkos_node_bft.helpers.channels.
- The types involved
snarkos_node_bft.bft.BFT→snarkos_node_bft.helpers.channels.ConsensusSendersnarkos_node_bft.bft.BFT→snarkos_node_bft.helpers.channels.PrimaryReceiversnarkos_node_bft.bft.BFT→snarkos_node_bft.helpers.channels.PrimarySender
- Direction
- snarkos_node_bft.bft uses snarkos_node_bft.helpers.channels, so a change to snarkos_node_bft.helpers.channels can break snarkos_node_bft.bft, while a change to snarkos_node_bft.bft can't break snarkos_node_bft.helpers.channels.
- Position
- Below the diagonal: snarkos_node_bft.bft uses a module listed above it, which is the healthy direction.
29→6 snarkos_node_bft.bft uses snarkos_node_sync.block_sync✕
- Connections
- 1 pair of types, where a type in snarkos_node_bft.bft uses a type in snarkos_node_sync.block_sync.
- The types involved
snarkos_node_bft.bft.BFT→snarkos_node_sync.block_sync.BlockSync
- Direction
- snarkos_node_bft.bft uses snarkos_node_sync.block_sync, so a change to snarkos_node_sync.block_sync can break snarkos_node_bft.bft, while a change to snarkos_node_bft.bft can't break snarkos_node_sync.block_sync.
- Position
- Below the diagonal: snarkos_node_bft.bft uses a module listed above it, which is the healthy direction.
29→8 snarkos_node_bft.bft uses snarkos_utilities.node_data✕
- Connections
- 1 pair of types, where a type in snarkos_node_bft.bft uses a type in snarkos_utilities.node_data.
- The types involved
snarkos_node_bft.bft.BFT→snarkos_utilities.node_data.NodeDataDir
- Direction
- snarkos_node_bft.bft uses snarkos_utilities.node_data, so a change to snarkos_utilities.node_data can break snarkos_node_bft.bft, while a change to snarkos_node_bft.bft can't break snarkos_utilities.node_data.
- Position
- Below the diagonal: snarkos_node_bft.bft uses a module listed above it, which is the healthy direction.
29→17 snarkos_node_bft.bft uses snarkos_node_router_messages.ping✕
- Connections
- 1 pair of types, where a type in snarkos_node_bft.bft uses a type in snarkos_node_router_messages.ping.
- The types involved
snarkos_node_bft.bft.BFT→snarkos_node_router_messages.ping.Ping
- Direction
- snarkos_node_bft.bft uses snarkos_node_router_messages.ping, so a change to snarkos_node_router_messages.ping can break snarkos_node_bft.bft, while a change to snarkos_node_bft.bft can't break snarkos_node_router_messages.ping.
- Position
- Below the diagonal: snarkos_node_bft.bft uses a module listed above it, which is the healthy direction.
29→20 snarkos_node_bft.bft uses snarkos_node_bft.sync✕
- Connections
- 1 pair of types, where a type in snarkos_node_bft.bft uses a type in snarkos_node_bft.sync.
- The types involved
snarkos_node_bft.bft.BFT→snarkos_node_bft.sync.SyncCallback
- Direction
- snarkos_node_bft.bft uses snarkos_node_bft.sync, so a change to snarkos_node_bft.sync can break snarkos_node_bft.bft, while a change to snarkos_node_bft.bft can't break snarkos_node_bft.sync.
- Position
- Below the diagonal: snarkos_node_bft.bft uses a module listed above it, which is the healthy direction.
29→25 snarkos_node_bft.bft uses snarkos_node_bft.primary✕
- Connections
- 2 pairs of types, where a type in snarkos_node_bft.bft uses a type in snarkos_node_bft.primary.
- The types involved
snarkos_node_bft.bft.BFT→snarkos_node_bft.primary.Primarysnarkos_node_bft.bft.BFT→snarkos_node_bft.primary.PrimaryCallback
- Direction
- snarkos_node_bft.bft uses snarkos_node_bft.primary, so a change to snarkos_node_bft.primary can break snarkos_node_bft.bft, while a change to snarkos_node_bft.bft can't break snarkos_node_bft.primary.
- Position
- Below the diagonal: snarkos_node_bft.bft uses a module listed above it, which is the healthy direction.
29→35 snarkos_node_bft.bft uses snarkos_account part of a loop✕
- Connections
- 1 pair of types, where a type in snarkos_node_bft.bft uses a type in snarkos_account.
- The types involved
snarkos_node_bft.bft.BFT→snarkos_account.Account
- Direction
- snarkos_node_bft.bft uses snarkos_account, so a change to snarkos_account can break snarkos_node_bft.bft, while a change to snarkos_node_bft.bft can't break snarkos_account.
- 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.
30→10 snarkos_node_router.routing uses snarkos_node_bft_events.disconnect✕
- Connections
- 1 pair of types, where a type in snarkos_node_router.routing uses a type in snarkos_node_bft_events.disconnect.
- The types involved
snarkos_node_router.routing.Routing→snarkos_node_bft_events.disconnect.Disconnect
- Direction
- snarkos_node_router.routing uses snarkos_node_bft_events.disconnect, so a change to snarkos_node_bft_events.disconnect can break snarkos_node_router.routing, while a change to snarkos_node_router.routing can't break snarkos_node_bft_events.disconnect.
- Position
- Below the diagonal: snarkos_node_router.routing uses a module listed above it, which is the healthy direction.
30→11 snarkos_node_router.routing uses snarkos_node_tcp✕
- Connections
- 1 pair of types, where a type in snarkos_node_router.routing uses a type in snarkos_node_tcp.
- The types involved
snarkos_node_router.routing.Routing→snarkos_node_tcp.P2P
- Direction
- snarkos_node_router.routing uses snarkos_node_tcp, so a change to snarkos_node_tcp can break snarkos_node_router.routing, while a change to snarkos_node_router.routing can't break snarkos_node_tcp.
- Position
- Below the diagonal: snarkos_node_router.routing uses a module listed above it, which is the healthy direction.
30→14 snarkos_node_router.routing uses snarkos_node_tcp.protocols.handshake✕
- Connections
- 1 pair of types, where a type in snarkos_node_router.routing uses a type in snarkos_node_tcp.protocols.handshake.
- The types involved
snarkos_node_router.routing.Routing→snarkos_node_tcp.protocols.handshake.Handshake
- Direction
- snarkos_node_router.routing uses snarkos_node_tcp.protocols.handshake, so a change to snarkos_node_tcp.protocols.handshake can break snarkos_node_router.routing, while a change to snarkos_node_router.routing can't break snarkos_node_tcp.protocols.handshake.
- Position
- Below the diagonal: snarkos_node_router.routing uses a module listed above it, which is the healthy direction.
30→15 snarkos_node_router.routing uses snarkos_node_tcp.protocols.on_connect✕
- Connections
- 1 pair of types, where a type in snarkos_node_router.routing uses a type in snarkos_node_tcp.protocols.on_connect.
- The types involved
snarkos_node_router.routing.Routing→snarkos_node_tcp.protocols.on_connect.OnConnect
- Direction
- snarkos_node_router.routing uses snarkos_node_tcp.protocols.on_connect, so a change to snarkos_node_tcp.protocols.on_connect can break snarkos_node_router.routing, while a change to snarkos_node_router.routing can't break snarkos_node_tcp.protocols.on_connect.
- Position
- Below the diagonal: snarkos_node_router.routing uses a module listed above it, which is the healthy direction.
30→23 snarkos_node_router.routing uses snarkos_node_router.outbound✕
- Connections
- 1 pair of types, where a type in snarkos_node_router.routing uses a type in snarkos_node_router.outbound.
- The types involved
snarkos_node_router.routing.Routing→snarkos_node_router.outbound.Outbound
- Direction
- snarkos_node_router.routing uses snarkos_node_router.outbound, so a change to snarkos_node_router.outbound can break snarkos_node_router.routing, while a change to snarkos_node_router.routing can't break snarkos_node_router.outbound.
- Position
- Below the diagonal: snarkos_node_router.routing uses a module listed above it, which is the healthy direction.
30→27 snarkos_node_router.routing uses snarkos_node_router.heartbeat✕
- Connections
- 1 pair of types, where a type in snarkos_node_router.routing uses a type in snarkos_node_router.heartbeat.
- The types involved
snarkos_node_router.routing.Routing→snarkos_node_router.heartbeat.Heartbeat
- Direction
- snarkos_node_router.routing uses snarkos_node_router.heartbeat, so a change to snarkos_node_router.heartbeat can break snarkos_node_router.routing, while a change to snarkos_node_router.routing can't break snarkos_node_router.heartbeat.
- Position
- Below the diagonal: snarkos_node_router.routing uses a module listed above it, which is the healthy direction.
30→28 snarkos_node_router.routing uses snarkos_node_router.inbound✕
- Connections
- 1 pair of types, where a type in snarkos_node_router.routing uses a type in snarkos_node_router.inbound.
- The types involved
snarkos_node_router.routing.Routing→snarkos_node_router.inbound.Inbound
- Direction
- snarkos_node_router.routing uses snarkos_node_router.inbound, so a change to snarkos_node_router.inbound can break snarkos_node_router.routing, while a change to snarkos_node_router.routing can't break snarkos_node_router.inbound.
- Position
- Below the diagonal: snarkos_node_router.routing uses a module listed above it, which is the healthy direction.
31→3 snarkos_node_consensus uses snarkos_node_bft.helpers.channels✕
- Connections
- 2 pairs of types, where a type in snarkos_node_consensus uses a type in snarkos_node_bft.helpers.channels.
- The types involved
snarkos_node_consensus.Consensus→snarkos_node_bft.helpers.channels.ConsensusReceiversnarkos_node_consensus.Consensus→snarkos_node_bft.helpers.channels.PrimarySender
- Direction
- snarkos_node_consensus uses snarkos_node_bft.helpers.channels, so a change to snarkos_node_bft.helpers.channels can break snarkos_node_consensus, while a change to snarkos_node_consensus can't break snarkos_node_bft.helpers.channels.
- Position
- Below the diagonal: snarkos_node_consensus uses a module listed above it, which is the healthy direction.
31→6 snarkos_node_consensus uses snarkos_node_sync.block_sync✕
- Connections
- 1 pair of types, where a type in snarkos_node_consensus uses a type in snarkos_node_sync.block_sync.
- The types involved
snarkos_node_consensus.Consensus→snarkos_node_sync.block_sync.BlockSync
- Direction
- snarkos_node_consensus uses snarkos_node_sync.block_sync, so a change to snarkos_node_sync.block_sync can break snarkos_node_consensus, while a change to snarkos_node_consensus can't break snarkos_node_sync.block_sync.
- Position
- Below the diagonal: snarkos_node_consensus uses a module listed above it, which is the healthy direction.
31→8 snarkos_node_consensus uses snarkos_utilities.node_data✕
- Connections
- 1 pair of types, where a type in snarkos_node_consensus uses a type in snarkos_utilities.node_data.
- The types involved
snarkos_node_consensus.Consensus→snarkos_utilities.node_data.NodeDataDir
- Direction
- snarkos_node_consensus uses snarkos_utilities.node_data, so a change to snarkos_utilities.node_data can break snarkos_node_consensus, while a change to snarkos_node_consensus can't break snarkos_utilities.node_data.
- Position
- Below the diagonal: snarkos_node_consensus uses a module listed above it, which is the healthy direction.
31→17 snarkos_node_consensus uses snarkos_node_router_messages.ping✕
- Connections
- 1 pair of types, where a type in snarkos_node_consensus uses a type in snarkos_node_router_messages.ping.
- The types involved
snarkos_node_consensus.Consensus→snarkos_node_router_messages.ping.Ping
- Direction
- snarkos_node_consensus uses snarkos_node_router_messages.ping, so a change to snarkos_node_router_messages.ping can break snarkos_node_consensus, while a change to snarkos_node_consensus can't break snarkos_node_router_messages.ping.
- Position
- Below the diagonal: snarkos_node_consensus uses a module listed above it, which is the healthy direction.
31→29 snarkos_node_consensus uses snarkos_node_bft.bft✕
- Connections
- 1 pair of types, where a type in snarkos_node_consensus uses a type in snarkos_node_bft.bft.
- The types involved
snarkos_node_consensus.Consensus→snarkos_node_bft.bft.BFT
- Direction
- snarkos_node_consensus uses snarkos_node_bft.bft, so a change to snarkos_node_bft.bft can break snarkos_node_consensus, while a change to snarkos_node_consensus can't break snarkos_node_bft.bft.
- Position
- Below the diagonal: snarkos_node_consensus uses a module listed above it, which is the healthy direction.
31→35 snarkos_node_consensus uses snarkos_account part of a loop✕
- Connections
- 1 pair of types, where a type in snarkos_node_consensus uses a type in snarkos_account.
- The types involved
snarkos_node_consensus.Consensus→snarkos_account.Account
- Direction
- snarkos_node_consensus uses snarkos_account, so a change to snarkos_account can break snarkos_node_consensus, while a change to snarkos_node_consensus can't break snarkos_account.
- 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.
32→1 snarkos_node_rest uses snarkos_node_rest.helpers.path✕
- Connections
- 1 pair of types, where a type in snarkos_node_rest uses a type in snarkos_node_rest.helpers.path.
- The types involved
snarkos_node_rest.Rest→snarkos_node_rest.helpers.path.Path
- Direction
- snarkos_node_rest uses snarkos_node_rest.helpers.path, so a change to snarkos_node_rest.helpers.path can break snarkos_node_rest, while a change to snarkos_node_rest can't break snarkos_node_rest.helpers.path.
- Position
- Below the diagonal: snarkos_node_rest uses a module listed above it, which is the healthy direction.
32→6 snarkos_node_rest uses snarkos_node_sync.block_sync✕
- Connections
- 1 pair of types, where a type in snarkos_node_rest uses a type in snarkos_node_sync.block_sync.
- The types involved
snarkos_node_rest.Rest→snarkos_node_sync.block_sync.BlockSync
- Direction
- snarkos_node_rest uses snarkos_node_sync.block_sync, so a change to snarkos_node_sync.block_sync can break snarkos_node_rest, while a change to snarkos_node_rest can't break snarkos_node_sync.block_sync.
- Position
- Below the diagonal: snarkos_node_rest uses a module listed above it, which is the healthy direction.
32→21 snarkos_node_rest uses snarkos_node_router✕
- Connections
- 1 pair of types, where a type in snarkos_node_rest uses a type in snarkos_node_router.
- The types involved
snarkos_node_rest.Rest→snarkos_node_router.Router
- Direction
- snarkos_node_rest uses snarkos_node_router, so a change to snarkos_node_router can break snarkos_node_rest, while a change to snarkos_node_rest can't break snarkos_node_router.
- Position
- Below the diagonal: snarkos_node_rest uses a module listed above it, which is the healthy direction.
32→31 snarkos_node_rest uses snarkos_node_consensus✕
- Connections
- 1 pair of types, where a type in snarkos_node_rest uses a type in snarkos_node_consensus.
- The types involved
snarkos_node_rest.Rest→snarkos_node_consensus.Consensus
- Direction
- snarkos_node_rest uses snarkos_node_consensus, so a change to snarkos_node_consensus can break snarkos_node_rest, while a change to snarkos_node_rest can't break snarkos_node_consensus.
- Position
- Below the diagonal: snarkos_node_rest uses a module listed above it, which is the healthy direction.
33→1 snarkos_node.node uses snarkos_node_rest.helpers.path✕
- Connections
- 1 pair of types, where a type in snarkos_node.node uses a type in snarkos_node_rest.helpers.path.
- The types involved
snarkos_node.node.node$module→snarkos_node_rest.helpers.path.Path
- Direction
- snarkos_node.node uses snarkos_node_rest.helpers.path, so a change to snarkos_node_rest.helpers.path can break snarkos_node.node, while a change to snarkos_node.node can't break snarkos_node_rest.helpers.path.
- Position
- Below the diagonal: snarkos_node.node uses a module listed above it, which is the healthy direction.
33→5 snarkos_node.node uses snarkos_node_network.node_type✕
- Connections
- 1 pair of types, where a type in snarkos_node.node uses a type in snarkos_node_network.node_type.
- The types involved
snarkos_node.node.Node→snarkos_node_network.node_type.NodeType
- Direction
- snarkos_node.node uses snarkos_node_network.node_type, so a change to snarkos_node_network.node_type can break snarkos_node.node, while a change to snarkos_node.node can't break snarkos_node_network.node_type.
- Position
- Below the diagonal: snarkos_node.node uses a module listed above it, which is the healthy direction.
33→8 snarkos_node.node uses snarkos_utilities.node_data✕
- Connections
- 1 pair of types, where a type in snarkos_node.node uses a type in snarkos_utilities.node_data.
- The types involved
snarkos_node.node.Node→snarkos_utilities.node_data.NodeDataDir
- Direction
- snarkos_node.node uses snarkos_utilities.node_data, so a change to snarkos_utilities.node_data can break snarkos_node.node, while a change to snarkos_node.node can't break snarkos_utilities.node_data.
- Position
- Below the diagonal: snarkos_node.node uses a module listed above it, which is the healthy direction.
33→24 snarkos_node.node uses snarkos_utilities.signals✕
- Connections
- 1 pair of types, where a type in snarkos_node.node uses a type in snarkos_utilities.signals.
- The types involved
snarkos_node.node.Node→snarkos_utilities.signals.SignalHandler
- Direction
- snarkos_node.node uses snarkos_utilities.signals, so a change to snarkos_utilities.signals can break snarkos_node.node, while a change to snarkos_node.node can't break snarkos_utilities.signals.
- Position
- Below the diagonal: snarkos_node.node uses a module listed above it, which is the healthy direction.
33→32 snarkos_node.node uses snarkos_node_rest✕
- Connections
- 1 pair of types, where a type in snarkos_node.node uses a type in snarkos_node_rest.
- The types involved
snarkos_node.node.Node→snarkos_node_rest.RestVerificationLimits
- Direction
- snarkos_node.node uses snarkos_node_rest, so a change to snarkos_node_rest can break snarkos_node.node, while a change to snarkos_node.node can't break snarkos_node_rest.
- Position
- Below the diagonal: snarkos_node.node uses a module listed above it, which is the healthy direction.
33→35 snarkos_node.node uses snarkos_account part of a loop✕
- Connections
- 1 pair of types, where a type in snarkos_node.node uses a type in snarkos_account.
- The types involved
snarkos_node.node.Node→snarkos_account.Account
- Direction
- snarkos_node.node uses snarkos_account, so a change to snarkos_account can break snarkos_node.node, while a change to snarkos_node.node can't break snarkos_account.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
34→33 snarkos_display uses snarkos_node.node✕
- Connections
- 1 pair of types, where a type in snarkos_display uses a type in snarkos_node.node.
- The types involved
snarkos_display.Display→snarkos_node.node.Node
- Direction
- snarkos_display uses snarkos_node.node, so a change to snarkos_node.node can break snarkos_display, while a change to snarkos_display can't break snarkos_node.node.
- Position
- Below the diagonal: snarkos_display uses a module listed above it, which is the healthy direction.
35→34 snarkos_account uses snarkos_display✕
- Connections
- 1 pair of types, where a type in snarkos_account uses a type in snarkos_display.
- The types involved
snarkos_account.Account→snarkos_display.Display
- Direction
- snarkos_account uses snarkos_display, so a change to snarkos_display can break snarkos_account, while a change to snarkos_account can't break snarkos_display.
- Position
- Below the diagonal: snarkos_account uses a module listed above it, which is the healthy direction.
36→6 snarkos_node.client uses snarkos_node_sync.block_sync✕
- Connections
- 1 pair of types, where a type in snarkos_node.client uses a type in snarkos_node_sync.block_sync.
- The types involved
snarkos_node.client.Client→snarkos_node_sync.block_sync.BlockSync
- Direction
- snarkos_node.client uses snarkos_node_sync.block_sync, so a change to snarkos_node_sync.block_sync can break snarkos_node.client, while a change to snarkos_node.client can't break snarkos_node_sync.block_sync.
- Position
- Below the diagonal: snarkos_node.client uses a module listed above it, which is the healthy direction.
36→7 snarkos_node.client uses snarkos_node_tcp.helpers.connections✕
- Connections
- 3 pairs of types, where a type in snarkos_node.client uses a type in snarkos_node_tcp.helpers.connections.
- The types involved
snarkos_node.client.Client→snarkos_node_tcp.helpers.connections.Connectionsnarkos_node.client.Client→snarkos_node_tcp.helpers.connections.ConnectionSidesnarkos_node.client.Client→snarkos_node_tcp.helpers.connections.DisconnectOrigin
- Direction
- snarkos_node.client uses snarkos_node_tcp.helpers.connections, so a change to snarkos_node_tcp.helpers.connections can break snarkos_node.client, while a change to snarkos_node.client can't break snarkos_node_tcp.helpers.connections.
- Position
- Below the diagonal: snarkos_node.client uses a module listed above it, which is the healthy direction.
36→8 snarkos_node.client uses snarkos_utilities.node_data✕
- Connections
- 1 pair of types, where a type in snarkos_node.client uses a type in snarkos_utilities.node_data.
- The types involved
snarkos_node.client.Client→snarkos_utilities.node_data.NodeDataDir
- Direction
- snarkos_node.client uses snarkos_utilities.node_data, so a change to snarkos_utilities.node_data can break snarkos_node.client, while a change to snarkos_node.client can't break snarkos_utilities.node_data.
- Position
- Below the diagonal: snarkos_node.client uses a module listed above it, which is the healthy direction.
36→9 snarkos_node.client uses snarkos_node_tcp.tcp✕
- Connections
- 1 pair of types, where a type in snarkos_node.client uses a type in snarkos_node_tcp.tcp.
- The types involved
snarkos_node.client.Client→snarkos_node_tcp.tcp.Tcp
- Direction
- snarkos_node.client uses snarkos_node_tcp.tcp, so a change to snarkos_node_tcp.tcp can break snarkos_node.client, while a change to snarkos_node.client can't break snarkos_node_tcp.tcp.
- Position
- Below the diagonal: snarkos_node.client uses a module listed above it, which is the healthy direction.
36→10 snarkos_node.client uses snarkos_node_bft_events.disconnect✕
- Connections
- 1 pair of types, where a type in snarkos_node.client uses a type in snarkos_node_bft_events.disconnect.
- The types involved
snarkos_node.client.Client→snarkos_node_bft_events.disconnect.Disconnect
- Direction
- snarkos_node.client uses snarkos_node_bft_events.disconnect, so a change to snarkos_node_bft_events.disconnect can break snarkos_node.client, while a change to snarkos_node.client can't break snarkos_node_bft_events.disconnect.
- Position
- Below the diagonal: snarkos_node.client uses a module listed above it, which is the healthy direction.
36→11 snarkos_node.client uses snarkos_node_tcp✕
- Connections
- 1 pair of types, where a type in snarkos_node.client uses a type in snarkos_node_tcp.
- The types involved
snarkos_node.client.Client→snarkos_node_tcp.P2P
- Direction
- snarkos_node.client uses snarkos_node_tcp, so a change to snarkos_node_tcp can break snarkos_node.client, while a change to snarkos_node.client can't break snarkos_node_tcp.
- Position
- Below the diagonal: snarkos_node.client uses a module listed above it, which is the healthy direction.
36→13 snarkos_node.client uses snarkos_node_router_messages✕
- Connections
- 1 pair of types, where a type in snarkos_node.client uses a type in snarkos_node_router_messages.
- The types involved
snarkos_node.client.Client→snarkos_node_router_messages.Message
- Direction
- snarkos_node.client uses snarkos_node_router_messages, so a change to snarkos_node_router_messages can break snarkos_node.client, while a change to snarkos_node.client can't break snarkos_node_router_messages.
- Position
- Below the diagonal: snarkos_node.client uses a module listed above it, which is the healthy direction.
36→14 snarkos_node.client uses snarkos_node_tcp.protocols.handshake✕
- Connections
- 1 pair of types, where a type in snarkos_node.client uses a type in snarkos_node_tcp.protocols.handshake.
- The types involved
snarkos_node.client.Client→snarkos_node_tcp.protocols.handshake.Handshake
- Direction
- snarkos_node.client uses snarkos_node_tcp.protocols.handshake, so a change to snarkos_node_tcp.protocols.handshake can break snarkos_node.client, while a change to snarkos_node.client can't break snarkos_node_tcp.protocols.handshake.
- Position
- Below the diagonal: snarkos_node.client uses a module listed above it, which is the healthy direction.
36→15 snarkos_node.client uses snarkos_node_tcp.protocols.on_connect✕
- Connections
- 1 pair of types, where a type in snarkos_node.client uses a type in snarkos_node_tcp.protocols.on_connect.
- The types involved
snarkos_node.client.Client→snarkos_node_tcp.protocols.on_connect.OnConnect
- Direction
- snarkos_node.client uses snarkos_node_tcp.protocols.on_connect, so a change to snarkos_node_tcp.protocols.on_connect can break snarkos_node.client, while a change to snarkos_node.client can't break snarkos_node_tcp.protocols.on_connect.
- Position
- Below the diagonal: snarkos_node.client uses a module listed above it, which is the healthy direction.
36→16 snarkos_node.client uses snarkos_node_bft_events.block_request✕
- Connections
- 1 pair of types, where a type in snarkos_node.client uses a type in snarkos_node_bft_events.block_request.
- The types involved
snarkos_node.client.Client→snarkos_node_bft_events.block_request.BlockRequest
- Direction
- snarkos_node.client uses snarkos_node_bft_events.block_request, so a change to snarkos_node_bft_events.block_request can break snarkos_node.client, while a change to snarkos_node.client can't break snarkos_node_bft_events.block_request.
- Position
- Below the diagonal: snarkos_node.client uses a module listed above it, which is the healthy direction.
36→17 snarkos_node.client uses snarkos_node_router_messages.ping✕
- Connections
- 1 pair of types, where a type in snarkos_node.client uses a type in snarkos_node_router_messages.ping.
- The types involved
snarkos_node.client.Client→snarkos_node_router_messages.ping.Ping
- Direction
- snarkos_node.client uses snarkos_node_router_messages.ping, so a change to snarkos_node_router_messages.ping can break snarkos_node.client, while a change to snarkos_node.client can't break snarkos_node_router_messages.ping.
- Position
- Below the diagonal: snarkos_node.client uses a module listed above it, which is the healthy direction.
36→18 snarkos_node.client uses snarkos_node_tcp.protocols.reading✕
- Connections
- 1 pair of types, where a type in snarkos_node.client uses a type in snarkos_node_tcp.protocols.reading.
- The types involved
snarkos_node.client.Client→snarkos_node_tcp.protocols.reading.Reading
- Direction
- snarkos_node.client uses snarkos_node_tcp.protocols.reading, so a change to snarkos_node_tcp.protocols.reading can break snarkos_node.client, while a change to snarkos_node.client can't break snarkos_node_tcp.protocols.reading.
- Position
- Below the diagonal: snarkos_node.client uses a module listed above it, which is the healthy direction.
36→21 snarkos_node.client uses snarkos_node_router✕
- Connections
- 1 pair of types, where a type in snarkos_node.client uses a type in snarkos_node_router.
- The types involved
snarkos_node.client.Client→snarkos_node_router.Router
- Direction
- snarkos_node.client uses snarkos_node_router, so a change to snarkos_node_router can break snarkos_node.client, while a change to snarkos_node.client can't break snarkos_node_router.
- Position
- Below the diagonal: snarkos_node.client uses a module listed above it, which is the healthy direction.
36→23 snarkos_node.client uses snarkos_node_router.outbound✕
- Connections
- 1 pair of types, where a type in snarkos_node.client uses a type in snarkos_node_router.outbound.
- The types involved
snarkos_node.client.Client→snarkos_node_router.outbound.Outbound
- Direction
- snarkos_node.client uses snarkos_node_router.outbound, so a change to snarkos_node_router.outbound can break snarkos_node.client, while a change to snarkos_node.client can't break snarkos_node_router.outbound.
- Position
- Below the diagonal: snarkos_node.client uses a module listed above it, which is the healthy direction.
36→24 snarkos_node.client uses snarkos_utilities.signals✕
- Connections
- 1 pair of types, where a type in snarkos_node.client uses a type in snarkos_utilities.signals.
- The types involved
snarkos_node.client.Client→snarkos_utilities.signals.SignalHandler
- Direction
- snarkos_node.client uses snarkos_utilities.signals, so a change to snarkos_utilities.signals can break snarkos_node.client, while a change to snarkos_node.client can't break snarkos_utilities.signals.
- Position
- Below the diagonal: snarkos_node.client uses a module listed above it, which is the healthy direction.
36→27 snarkos_node.client uses snarkos_node_router.heartbeat✕
- Connections
- 1 pair of types, where a type in snarkos_node.client uses a type in snarkos_node_router.heartbeat.
- The types involved
snarkos_node.client.Client→snarkos_node_router.heartbeat.Heartbeat
- Direction
- snarkos_node.client uses snarkos_node_router.heartbeat, so a change to snarkos_node_router.heartbeat can break snarkos_node.client, while a change to snarkos_node.client can't break snarkos_node_router.heartbeat.
- Position
- Below the diagonal: snarkos_node.client uses a module listed above it, which is the healthy direction.
36→28 snarkos_node.client uses snarkos_node_router.inbound✕
- Connections
- 1 pair of types, where a type in snarkos_node.client uses a type in snarkos_node_router.inbound.
- The types involved
snarkos_node.client.Client→snarkos_node_router.inbound.Inbound
- Direction
- snarkos_node.client uses snarkos_node_router.inbound, so a change to snarkos_node_router.inbound can break snarkos_node.client, while a change to snarkos_node.client can't break snarkos_node_router.inbound.
- Position
- Below the diagonal: snarkos_node.client uses a module listed above it, which is the healthy direction.
36→30 snarkos_node.client uses snarkos_node_router.routing✕
- Connections
- 1 pair of types, where a type in snarkos_node.client uses a type in snarkos_node_router.routing.
- The types involved
snarkos_node.client.Client→snarkos_node_router.routing.Routing
- Direction
- snarkos_node.client uses snarkos_node_router.routing, so a change to snarkos_node_router.routing can break snarkos_node.client, while a change to snarkos_node.client can't break snarkos_node_router.routing.
- Position
- Below the diagonal: snarkos_node.client uses a module listed above it, which is the healthy direction.
36→32 snarkos_node.client uses snarkos_node_rest✕
- Connections
- 2 pairs of types, where a type in snarkos_node.client uses a type in snarkos_node_rest.
- The types involved
snarkos_node.client.Client→snarkos_node_rest.Restsnarkos_node.client.Client→snarkos_node_rest.RestVerificationLimits
- Direction
- snarkos_node.client uses snarkos_node_rest, so a change to snarkos_node_rest can break snarkos_node.client, while a change to snarkos_node.client can't break snarkos_node_rest.
- Position
- Below the diagonal: snarkos_node.client uses a module listed above it, which is the healthy direction.
36→35 snarkos_node.client uses snarkos_account✕
- Connections
- 1 pair of types, where a type in snarkos_node.client uses a type in snarkos_account.
- The types involved
snarkos_node.client.Client→snarkos_account.Account
- Direction
- snarkos_node.client uses snarkos_account, so a change to snarkos_account can break snarkos_node.client, while a change to snarkos_node.client can't break snarkos_account.
- Position
- Below the diagonal: snarkos_node.client uses a module listed above it, which is the healthy direction.
37→6 snarkos_node.prover uses snarkos_node_sync.block_sync✕
- Connections
- 1 pair of types, where a type in snarkos_node.prover uses a type in snarkos_node_sync.block_sync.
- The types involved
snarkos_node.prover.Prover→snarkos_node_sync.block_sync.BlockSync
- Direction
- snarkos_node.prover uses snarkos_node_sync.block_sync, so a change to snarkos_node_sync.block_sync can break snarkos_node.prover, while a change to snarkos_node.prover can't break snarkos_node_sync.block_sync.
- Position
- Below the diagonal: snarkos_node.prover uses a module listed above it, which is the healthy direction.
37→7 snarkos_node.prover uses snarkos_node_tcp.helpers.connections✕
- Connections
- 3 pairs of types, where a type in snarkos_node.prover uses a type in snarkos_node_tcp.helpers.connections.
- The types involved
snarkos_node.prover.Prover→snarkos_node_tcp.helpers.connections.Connectionsnarkos_node.prover.Prover→snarkos_node_tcp.helpers.connections.ConnectionSidesnarkos_node.prover.Prover→snarkos_node_tcp.helpers.connections.DisconnectOrigin
- Direction
- snarkos_node.prover uses snarkos_node_tcp.helpers.connections, so a change to snarkos_node_tcp.helpers.connections can break snarkos_node.prover, while a change to snarkos_node.prover can't break snarkos_node_tcp.helpers.connections.
- Position
- Below the diagonal: snarkos_node.prover uses a module listed above it, which is the healthy direction.
37→8 snarkos_node.prover uses snarkos_utilities.node_data✕
- Connections
- 1 pair of types, where a type in snarkos_node.prover uses a type in snarkos_utilities.node_data.
- The types involved
snarkos_node.prover.Prover→snarkos_utilities.node_data.NodeDataDir
- Direction
- snarkos_node.prover uses snarkos_utilities.node_data, so a change to snarkos_utilities.node_data can break snarkos_node.prover, while a change to snarkos_node.prover can't break snarkos_utilities.node_data.
- Position
- Below the diagonal: snarkos_node.prover uses a module listed above it, which is the healthy direction.
37→9 snarkos_node.prover uses snarkos_node_tcp.tcp✕
- Connections
- 1 pair of types, where a type in snarkos_node.prover uses a type in snarkos_node_tcp.tcp.
- The types involved
snarkos_node.prover.Prover→snarkos_node_tcp.tcp.Tcp
- Direction
- snarkos_node.prover uses snarkos_node_tcp.tcp, so a change to snarkos_node_tcp.tcp can break snarkos_node.prover, while a change to snarkos_node.prover can't break snarkos_node_tcp.tcp.
- Position
- Below the diagonal: snarkos_node.prover uses a module listed above it, which is the healthy direction.
37→10 snarkos_node.prover uses snarkos_node_bft_events.disconnect✕
- Connections
- 1 pair of types, where a type in snarkos_node.prover uses a type in snarkos_node_bft_events.disconnect.
- The types involved
snarkos_node.prover.Prover→snarkos_node_bft_events.disconnect.Disconnect
- Direction
- snarkos_node.prover uses snarkos_node_bft_events.disconnect, so a change to snarkos_node_bft_events.disconnect can break snarkos_node.prover, while a change to snarkos_node.prover can't break snarkos_node_bft_events.disconnect.
- Position
- Below the diagonal: snarkos_node.prover uses a module listed above it, which is the healthy direction.
37→11 snarkos_node.prover uses snarkos_node_tcp✕
- Connections
- 1 pair of types, where a type in snarkos_node.prover uses a type in snarkos_node_tcp.
- The types involved
snarkos_node.prover.Prover→snarkos_node_tcp.P2P
- Direction
- snarkos_node.prover uses snarkos_node_tcp, so a change to snarkos_node_tcp can break snarkos_node.prover, while a change to snarkos_node.prover can't break snarkos_node_tcp.
- Position
- Below the diagonal: snarkos_node.prover uses a module listed above it, which is the healthy direction.
37→13 snarkos_node.prover uses snarkos_node_router_messages✕
- Connections
- 1 pair of types, where a type in snarkos_node.prover uses a type in snarkos_node_router_messages.
- The types involved
snarkos_node.prover.Prover→snarkos_node_router_messages.Message
- Direction
- snarkos_node.prover uses snarkos_node_router_messages, so a change to snarkos_node_router_messages can break snarkos_node.prover, while a change to snarkos_node.prover can't break snarkos_node_router_messages.
- Position
- Below the diagonal: snarkos_node.prover uses a module listed above it, which is the healthy direction.
37→14 snarkos_node.prover uses snarkos_node_tcp.protocols.handshake✕
- Connections
- 1 pair of types, where a type in snarkos_node.prover uses a type in snarkos_node_tcp.protocols.handshake.
- The types involved
snarkos_node.prover.Prover→snarkos_node_tcp.protocols.handshake.Handshake
- Direction
- snarkos_node.prover uses snarkos_node_tcp.protocols.handshake, so a change to snarkos_node_tcp.protocols.handshake can break snarkos_node.prover, while a change to snarkos_node.prover can't break snarkos_node_tcp.protocols.handshake.
- Position
- Below the diagonal: snarkos_node.prover uses a module listed above it, which is the healthy direction.
37→15 snarkos_node.prover uses snarkos_node_tcp.protocols.on_connect✕
- Connections
- 1 pair of types, where a type in snarkos_node.prover uses a type in snarkos_node_tcp.protocols.on_connect.
- The types involved
snarkos_node.prover.Prover→snarkos_node_tcp.protocols.on_connect.OnConnect
- Direction
- snarkos_node.prover uses snarkos_node_tcp.protocols.on_connect, so a change to snarkos_node_tcp.protocols.on_connect can break snarkos_node.prover, while a change to snarkos_node.prover can't break snarkos_node_tcp.protocols.on_connect.
- Position
- Below the diagonal: snarkos_node.prover uses a module listed above it, which is the healthy direction.
37→16 snarkos_node.prover uses snarkos_node_bft_events.block_request✕
- Connections
- 1 pair of types, where a type in snarkos_node.prover uses a type in snarkos_node_bft_events.block_request.
- The types involved
snarkos_node.prover.Prover→snarkos_node_bft_events.block_request.BlockRequest
- Direction
- snarkos_node.prover uses snarkos_node_bft_events.block_request, so a change to snarkos_node_bft_events.block_request can break snarkos_node.prover, while a change to snarkos_node.prover can't break snarkos_node_bft_events.block_request.
- Position
- Below the diagonal: snarkos_node.prover uses a module listed above it, which is the healthy direction.
37→17 snarkos_node.prover uses snarkos_node_router_messages.ping✕
- Connections
- 1 pair of types, where a type in snarkos_node.prover uses a type in snarkos_node_router_messages.ping.
- The types involved
snarkos_node.prover.Prover→snarkos_node_router_messages.ping.Ping
- Direction
- snarkos_node.prover uses snarkos_node_router_messages.ping, so a change to snarkos_node_router_messages.ping can break snarkos_node.prover, while a change to snarkos_node.prover can't break snarkos_node_router_messages.ping.
- Position
- Below the diagonal: snarkos_node.prover uses a module listed above it, which is the healthy direction.
37→18 snarkos_node.prover uses snarkos_node_tcp.protocols.reading✕
- Connections
- 1 pair of types, where a type in snarkos_node.prover uses a type in snarkos_node_tcp.protocols.reading.
- The types involved
snarkos_node.prover.Prover→snarkos_node_tcp.protocols.reading.Reading
- Direction
- snarkos_node.prover uses snarkos_node_tcp.protocols.reading, so a change to snarkos_node_tcp.protocols.reading can break snarkos_node.prover, while a change to snarkos_node.prover can't break snarkos_node_tcp.protocols.reading.
- Position
- Below the diagonal: snarkos_node.prover uses a module listed above it, which is the healthy direction.
37→21 snarkos_node.prover uses snarkos_node_router✕
- Connections
- 1 pair of types, where a type in snarkos_node.prover uses a type in snarkos_node_router.
- The types involved
snarkos_node.prover.Prover→snarkos_node_router.Router
- Direction
- snarkos_node.prover uses snarkos_node_router, so a change to snarkos_node_router can break snarkos_node.prover, while a change to snarkos_node.prover can't break snarkos_node_router.
- Position
- Below the diagonal: snarkos_node.prover uses a module listed above it, which is the healthy direction.
37→23 snarkos_node.prover uses snarkos_node_router.outbound✕
- Connections
- 1 pair of types, where a type in snarkos_node.prover uses a type in snarkos_node_router.outbound.
- The types involved
snarkos_node.prover.Prover→snarkos_node_router.outbound.Outbound
- Direction
- snarkos_node.prover uses snarkos_node_router.outbound, so a change to snarkos_node_router.outbound can break snarkos_node.prover, while a change to snarkos_node.prover can't break snarkos_node_router.outbound.
- Position
- Below the diagonal: snarkos_node.prover uses a module listed above it, which is the healthy direction.
37→24 snarkos_node.prover uses snarkos_utilities.signals✕
- Connections
- 1 pair of types, where a type in snarkos_node.prover uses a type in snarkos_utilities.signals.
- The types involved
snarkos_node.prover.Prover→snarkos_utilities.signals.SignalHandler
- Direction
- snarkos_node.prover uses snarkos_utilities.signals, so a change to snarkos_utilities.signals can break snarkos_node.prover, while a change to snarkos_node.prover can't break snarkos_utilities.signals.
- Position
- Below the diagonal: snarkos_node.prover uses a module listed above it, which is the healthy direction.
37→27 snarkos_node.prover uses snarkos_node_router.heartbeat✕
- Connections
- 1 pair of types, where a type in snarkos_node.prover uses a type in snarkos_node_router.heartbeat.
- The types involved
snarkos_node.prover.Prover→snarkos_node_router.heartbeat.Heartbeat
- Direction
- snarkos_node.prover uses snarkos_node_router.heartbeat, so a change to snarkos_node_router.heartbeat can break snarkos_node.prover, while a change to snarkos_node.prover can't break snarkos_node_router.heartbeat.
- Position
- Below the diagonal: snarkos_node.prover uses a module listed above it, which is the healthy direction.
37→28 snarkos_node.prover uses snarkos_node_router.inbound✕
- Connections
- 1 pair of types, where a type in snarkos_node.prover uses a type in snarkos_node_router.inbound.
- The types involved
snarkos_node.prover.Prover→snarkos_node_router.inbound.Inbound
- Direction
- snarkos_node.prover uses snarkos_node_router.inbound, so a change to snarkos_node_router.inbound can break snarkos_node.prover, while a change to snarkos_node.prover can't break snarkos_node_router.inbound.
- Position
- Below the diagonal: snarkos_node.prover uses a module listed above it, which is the healthy direction.
37→30 snarkos_node.prover uses snarkos_node_router.routing✕
- Connections
- 1 pair of types, where a type in snarkos_node.prover uses a type in snarkos_node_router.routing.
- The types involved
snarkos_node.prover.Prover→snarkos_node_router.routing.Routing
- Direction
- snarkos_node.prover uses snarkos_node_router.routing, so a change to snarkos_node_router.routing can break snarkos_node.prover, while a change to snarkos_node.prover can't break snarkos_node_router.routing.
- Position
- Below the diagonal: snarkos_node.prover uses a module listed above it, which is the healthy direction.
37→35 snarkos_node.prover uses snarkos_account✕
- Connections
- 1 pair of types, where a type in snarkos_node.prover uses a type in snarkos_account.
- The types involved
snarkos_node.prover.Prover→snarkos_account.Account
- Direction
- snarkos_node.prover uses snarkos_account, so a change to snarkos_account can break snarkos_node.prover, while a change to snarkos_node.prover can't break snarkos_account.
- Position
- Below the diagonal: snarkos_node.prover uses a module listed above it, which is the healthy direction.
38→6 snarkos_node.validator uses snarkos_node_sync.block_sync✕
- Connections
- 1 pair of types, where a type in snarkos_node.validator uses a type in snarkos_node_sync.block_sync.
- The types involved
snarkos_node.validator.Validator→snarkos_node_sync.block_sync.BlockSync
- Direction
- snarkos_node.validator uses snarkos_node_sync.block_sync, so a change to snarkos_node_sync.block_sync can break snarkos_node.validator, while a change to snarkos_node.validator can't break snarkos_node_sync.block_sync.
- Position
- Below the diagonal: snarkos_node.validator uses a module listed above it, which is the healthy direction.
38→7 snarkos_node.validator uses snarkos_node_tcp.helpers.connections✕
- Connections
- 3 pairs of types, where a type in snarkos_node.validator uses a type in snarkos_node_tcp.helpers.connections.
- The types involved
snarkos_node.validator.Validator→snarkos_node_tcp.helpers.connections.Connectionsnarkos_node.validator.Validator→snarkos_node_tcp.helpers.connections.ConnectionSidesnarkos_node.validator.Validator→snarkos_node_tcp.helpers.connections.DisconnectOrigin
- Direction
- snarkos_node.validator uses snarkos_node_tcp.helpers.connections, so a change to snarkos_node_tcp.helpers.connections can break snarkos_node.validator, while a change to snarkos_node.validator can't break snarkos_node_tcp.helpers.connections.
- Position
- Below the diagonal: snarkos_node.validator uses a module listed above it, which is the healthy direction.
38→8 snarkos_node.validator uses snarkos_utilities.node_data✕
- Connections
- 1 pair of types, where a type in snarkos_node.validator uses a type in snarkos_utilities.node_data.
- The types involved
snarkos_node.validator.Validator→snarkos_utilities.node_data.NodeDataDir
- Direction
- snarkos_node.validator uses snarkos_utilities.node_data, so a change to snarkos_utilities.node_data can break snarkos_node.validator, while a change to snarkos_node.validator can't break snarkos_utilities.node_data.
- Position
- Below the diagonal: snarkos_node.validator uses a module listed above it, which is the healthy direction.
38→9 snarkos_node.validator uses snarkos_node_tcp.tcp✕
- Connections
- 1 pair of types, where a type in snarkos_node.validator uses a type in snarkos_node_tcp.tcp.
- The types involved
snarkos_node.validator.Validator→snarkos_node_tcp.tcp.Tcp
- Direction
- snarkos_node.validator uses snarkos_node_tcp.tcp, so a change to snarkos_node_tcp.tcp can break snarkos_node.validator, while a change to snarkos_node.validator can't break snarkos_node_tcp.tcp.
- Position
- Below the diagonal: snarkos_node.validator uses a module listed above it, which is the healthy direction.
38→10 snarkos_node.validator uses snarkos_node_bft_events.disconnect✕
- Connections
- 1 pair of types, where a type in snarkos_node.validator uses a type in snarkos_node_bft_events.disconnect.
- The types involved
snarkos_node.validator.Validator→snarkos_node_bft_events.disconnect.Disconnect
- Direction
- snarkos_node.validator uses snarkos_node_bft_events.disconnect, so a change to snarkos_node_bft_events.disconnect can break snarkos_node.validator, while a change to snarkos_node.validator can't break snarkos_node_bft_events.disconnect.
- Position
- Below the diagonal: snarkos_node.validator uses a module listed above it, which is the healthy direction.
38→11 snarkos_node.validator uses snarkos_node_tcp✕
- Connections
- 1 pair of types, where a type in snarkos_node.validator uses a type in snarkos_node_tcp.
- The types involved
snarkos_node.validator.Validator→snarkos_node_tcp.P2P
- Direction
- snarkos_node.validator uses snarkos_node_tcp, so a change to snarkos_node_tcp can break snarkos_node.validator, while a change to snarkos_node.validator can't break snarkos_node_tcp.
- Position
- Below the diagonal: snarkos_node.validator uses a module listed above it, which is the healthy direction.
38→13 snarkos_node.validator uses snarkos_node_router_messages✕
- Connections
- 1 pair of types, where a type in snarkos_node.validator uses a type in snarkos_node_router_messages.
- The types involved
snarkos_node.validator.Validator→snarkos_node_router_messages.Message
- Direction
- snarkos_node.validator uses snarkos_node_router_messages, so a change to snarkos_node_router_messages can break snarkos_node.validator, while a change to snarkos_node.validator can't break snarkos_node_router_messages.
- Position
- Below the diagonal: snarkos_node.validator uses a module listed above it, which is the healthy direction.
38→14 snarkos_node.validator uses snarkos_node_tcp.protocols.handshake✕
- Connections
- 1 pair of types, where a type in snarkos_node.validator uses a type in snarkos_node_tcp.protocols.handshake.
- The types involved
snarkos_node.validator.Validator→snarkos_node_tcp.protocols.handshake.Handshake
- Direction
- snarkos_node.validator uses snarkos_node_tcp.protocols.handshake, so a change to snarkos_node_tcp.protocols.handshake can break snarkos_node.validator, while a change to snarkos_node.validator can't break snarkos_node_tcp.protocols.handshake.
- Position
- Below the diagonal: snarkos_node.validator uses a module listed above it, which is the healthy direction.
38→15 snarkos_node.validator uses snarkos_node_tcp.protocols.on_connect✕
- Connections
- 1 pair of types, where a type in snarkos_node.validator uses a type in snarkos_node_tcp.protocols.on_connect.
- The types involved
snarkos_node.validator.Validator→snarkos_node_tcp.protocols.on_connect.OnConnect
- Direction
- snarkos_node.validator uses snarkos_node_tcp.protocols.on_connect, so a change to snarkos_node_tcp.protocols.on_connect can break snarkos_node.validator, while a change to snarkos_node.validator can't break snarkos_node_tcp.protocols.on_connect.
- Position
- Below the diagonal: snarkos_node.validator uses a module listed above it, which is the healthy direction.
38→16 snarkos_node.validator uses snarkos_node_bft_events.block_request✕
- Connections
- 1 pair of types, where a type in snarkos_node.validator uses a type in snarkos_node_bft_events.block_request.
- The types involved
snarkos_node.validator.Validator→snarkos_node_bft_events.block_request.BlockRequest
- Direction
- snarkos_node.validator uses snarkos_node_bft_events.block_request, so a change to snarkos_node_bft_events.block_request can break snarkos_node.validator, while a change to snarkos_node.validator can't break snarkos_node_bft_events.block_request.
- Position
- Below the diagonal: snarkos_node.validator uses a module listed above it, which is the healthy direction.
38→17 snarkos_node.validator uses snarkos_node_router_messages.ping✕
- Connections
- 1 pair of types, where a type in snarkos_node.validator uses a type in snarkos_node_router_messages.ping.
- The types involved
snarkos_node.validator.Validator→snarkos_node_router_messages.ping.Ping
- Direction
- snarkos_node.validator uses snarkos_node_router_messages.ping, so a change to snarkos_node_router_messages.ping can break snarkos_node.validator, while a change to snarkos_node.validator can't break snarkos_node_router_messages.ping.
- Position
- Below the diagonal: snarkos_node.validator uses a module listed above it, which is the healthy direction.
38→18 snarkos_node.validator uses snarkos_node_tcp.protocols.reading✕
- Connections
- 1 pair of types, where a type in snarkos_node.validator uses a type in snarkos_node_tcp.protocols.reading.
- The types involved
snarkos_node.validator.Validator→snarkos_node_tcp.protocols.reading.Reading
- Direction
- snarkos_node.validator uses snarkos_node_tcp.protocols.reading, so a change to snarkos_node_tcp.protocols.reading can break snarkos_node.validator, while a change to snarkos_node.validator can't break snarkos_node_tcp.protocols.reading.
- Position
- Below the diagonal: snarkos_node.validator uses a module listed above it, which is the healthy direction.
38→21 snarkos_node.validator uses snarkos_node_router✕
- Connections
- 1 pair of types, where a type in snarkos_node.validator uses a type in snarkos_node_router.
- The types involved
snarkos_node.validator.Validator→snarkos_node_router.Router
- Direction
- snarkos_node.validator uses snarkos_node_router, so a change to snarkos_node_router can break snarkos_node.validator, while a change to snarkos_node.validator can't break snarkos_node_router.
- Position
- Below the diagonal: snarkos_node.validator uses a module listed above it, which is the healthy direction.
38→23 snarkos_node.validator uses snarkos_node_router.outbound✕
- Connections
- 1 pair of types, where a type in snarkos_node.validator uses a type in snarkos_node_router.outbound.
- The types involved
snarkos_node.validator.Validator→snarkos_node_router.outbound.Outbound
- Direction
- snarkos_node.validator uses snarkos_node_router.outbound, so a change to snarkos_node_router.outbound can break snarkos_node.validator, while a change to snarkos_node.validator can't break snarkos_node_router.outbound.
- Position
- Below the diagonal: snarkos_node.validator uses a module listed above it, which is the healthy direction.
38→24 snarkos_node.validator uses snarkos_utilities.signals✕
- Connections
- 1 pair of types, where a type in snarkos_node.validator uses a type in snarkos_utilities.signals.
- The types involved
snarkos_node.validator.Validator→snarkos_utilities.signals.SignalHandler
- Direction
- snarkos_node.validator uses snarkos_utilities.signals, so a change to snarkos_utilities.signals can break snarkos_node.validator, while a change to snarkos_node.validator can't break snarkos_utilities.signals.
- Position
- Below the diagonal: snarkos_node.validator uses a module listed above it, which is the healthy direction.
38→27 snarkos_node.validator uses snarkos_node_router.heartbeat✕
- Connections
- 1 pair of types, where a type in snarkos_node.validator uses a type in snarkos_node_router.heartbeat.
- The types involved
snarkos_node.validator.Validator→snarkos_node_router.heartbeat.Heartbeat
- Direction
- snarkos_node.validator uses snarkos_node_router.heartbeat, so a change to snarkos_node_router.heartbeat can break snarkos_node.validator, while a change to snarkos_node.validator can't break snarkos_node_router.heartbeat.
- Position
- Below the diagonal: snarkos_node.validator uses a module listed above it, which is the healthy direction.
38→28 snarkos_node.validator uses snarkos_node_router.inbound✕
- Connections
- 1 pair of types, where a type in snarkos_node.validator uses a type in snarkos_node_router.inbound.
- The types involved
snarkos_node.validator.Validator→snarkos_node_router.inbound.Inbound
- Direction
- snarkos_node.validator uses snarkos_node_router.inbound, so a change to snarkos_node_router.inbound can break snarkos_node.validator, while a change to snarkos_node.validator can't break snarkos_node_router.inbound.
- Position
- Below the diagonal: snarkos_node.validator uses a module listed above it, which is the healthy direction.
38→30 snarkos_node.validator uses snarkos_node_router.routing✕
- Connections
- 1 pair of types, where a type in snarkos_node.validator uses a type in snarkos_node_router.routing.
- The types involved
snarkos_node.validator.Validator→snarkos_node_router.routing.Routing
- Direction
- snarkos_node.validator uses snarkos_node_router.routing, so a change to snarkos_node_router.routing can break snarkos_node.validator, while a change to snarkos_node.validator can't break snarkos_node_router.routing.
- Position
- Below the diagonal: snarkos_node.validator uses a module listed above it, which is the healthy direction.
38→31 snarkos_node.validator uses snarkos_node_consensus✕
- Connections
- 1 pair of types, where a type in snarkos_node.validator uses a type in snarkos_node_consensus.
- The types involved
snarkos_node.validator.Validator→snarkos_node_consensus.Consensus
- Direction
- snarkos_node.validator uses snarkos_node_consensus, so a change to snarkos_node_consensus can break snarkos_node.validator, while a change to snarkos_node.validator can't break snarkos_node_consensus.
- Position
- Below the diagonal: snarkos_node.validator uses a module listed above it, which is the healthy direction.
38→32 snarkos_node.validator uses snarkos_node_rest✕
- Connections
- 2 pairs of types, where a type in snarkos_node.validator uses a type in snarkos_node_rest.
- The types involved
snarkos_node.validator.Validator→snarkos_node_rest.Restsnarkos_node.validator.Validator→snarkos_node_rest.RestVerificationLimits
- Direction
- snarkos_node.validator uses snarkos_node_rest, so a change to snarkos_node_rest can break snarkos_node.validator, while a change to snarkos_node.validator can't break snarkos_node_rest.
- Position
- Below the diagonal: snarkos_node.validator uses a module listed above it, which is the healthy direction.
38→35 snarkos_node.validator uses snarkos_account✕
- Connections
- 1 pair of types, where a type in snarkos_node.validator uses a type in snarkos_account.
- The types involved
snarkos_node.validator.Validator→snarkos_account.Account
- Direction
- snarkos_node.validator uses snarkos_account, so a change to snarkos_account can break snarkos_node.validator, while a change to snarkos_node.validator can't break snarkos_account.
- Position
- Below the diagonal: snarkos_node.validator uses a module listed above it, which is the healthy direction.
39→5 snarkos_node_router.test_helpers uses snarkos_node_network.node_type✕
- Connections
- 2 pairs of types, where a type in snarkos_node_router.test_helpers uses a type in snarkos_node_network.node_type.
- The types involved
snarkos_node_router.test_helpers.TestRouter→snarkos_node_network.node_type.NodeTypesnarkos_node_router.test_helpers.test_helpers$module→snarkos_node_network.node_type.NodeType
- Direction
- snarkos_node_router.test_helpers uses snarkos_node_network.node_type, so a change to snarkos_node_network.node_type can break snarkos_node_router.test_helpers, while a change to snarkos_node_router.test_helpers can't break snarkos_node_network.node_type.
- Position
- Below the diagonal: snarkos_node_router.test_helpers uses a module listed above it, which is the healthy direction.
39→7 snarkos_node_router.test_helpers uses snarkos_node_tcp.helpers.connections✕
- Connections
- 3 pairs of types, where a type in snarkos_node_router.test_helpers uses a type in snarkos_node_tcp.helpers.connections.
- The types involved
snarkos_node_router.test_helpers.TestRouter→snarkos_node_tcp.helpers.connections.Connectionsnarkos_node_router.test_helpers.TestRouter→snarkos_node_tcp.helpers.connections.ConnectionSidesnarkos_node_router.test_helpers.TestRouter→snarkos_node_tcp.helpers.connections.DisconnectOrigin
- Direction
- snarkos_node_router.test_helpers uses snarkos_node_tcp.helpers.connections, so a change to snarkos_node_tcp.helpers.connections can break snarkos_node_router.test_helpers, while a change to snarkos_node_router.test_helpers can't break snarkos_node_tcp.helpers.connections.
- Position
- Below the diagonal: snarkos_node_router.test_helpers uses a module listed above it, which is the healthy direction.
39→9 snarkos_node_router.test_helpers uses snarkos_node_tcp.tcp✕
- Connections
- 1 pair of types, where a type in snarkos_node_router.test_helpers uses a type in snarkos_node_tcp.tcp.
- The types involved
snarkos_node_router.test_helpers.TestRouter→snarkos_node_tcp.tcp.Tcp
- Direction
- snarkos_node_router.test_helpers uses snarkos_node_tcp.tcp, so a change to snarkos_node_tcp.tcp can break snarkos_node_router.test_helpers, while a change to snarkos_node_router.test_helpers can't break snarkos_node_tcp.tcp.
- Position
- Below the diagonal: snarkos_node_router.test_helpers uses a module listed above it, which is the healthy direction.
39→10 snarkos_node_router.test_helpers uses snarkos_node_bft_events.disconnect✕
- Connections
- 1 pair of types, where a type in snarkos_node_router.test_helpers uses a type in snarkos_node_bft_events.disconnect.
- The types involved
snarkos_node_router.test_helpers.TestRouter→snarkos_node_bft_events.disconnect.Disconnect
- Direction
- snarkos_node_router.test_helpers uses snarkos_node_bft_events.disconnect, so a change to snarkos_node_bft_events.disconnect can break snarkos_node_router.test_helpers, while a change to snarkos_node_router.test_helpers can't break snarkos_node_bft_events.disconnect.
- Position
- Below the diagonal: snarkos_node_router.test_helpers uses a module listed above it, which is the healthy direction.
39→11 snarkos_node_router.test_helpers uses snarkos_node_tcp✕
- Connections
- 1 pair of types, where a type in snarkos_node_router.test_helpers uses a type in snarkos_node_tcp.
- The types involved
snarkos_node_router.test_helpers.TestRouter→snarkos_node_tcp.P2P
- Direction
- snarkos_node_router.test_helpers uses snarkos_node_tcp, so a change to snarkos_node_tcp can break snarkos_node_router.test_helpers, while a change to snarkos_node_router.test_helpers can't break snarkos_node_tcp.
- Position
- Below the diagonal: snarkos_node_router.test_helpers uses a module listed above it, which is the healthy direction.
39→12 snarkos_node_router.test_helpers uses snarkos_node_network.peering✕
- Connections
- 1 pair of types, where a type in snarkos_node_router.test_helpers uses a type in snarkos_node_network.peering.
- The types involved
snarkos_node_router.test_helpers.TestRouter→snarkos_node_network.peering.PeerPoolHandling
- Direction
- snarkos_node_router.test_helpers uses snarkos_node_network.peering, so a change to snarkos_node_network.peering can break snarkos_node_router.test_helpers, while a change to snarkos_node_router.test_helpers can't break snarkos_node_network.peering.
- Position
- Below the diagonal: snarkos_node_router.test_helpers uses a module listed above it, which is the healthy direction.
39→13 snarkos_node_router.test_helpers uses snarkos_node_router_messages✕
- Connections
- 1 pair of types, where a type in snarkos_node_router.test_helpers uses a type in snarkos_node_router_messages.
- The types involved
snarkos_node_router.test_helpers.TestRouter→snarkos_node_router_messages.Message
- Direction
- snarkos_node_router.test_helpers uses snarkos_node_router_messages, so a change to snarkos_node_router_messages can break snarkos_node_router.test_helpers, while a change to snarkos_node_router.test_helpers can't break snarkos_node_router_messages.
- Position
- Below the diagonal: snarkos_node_router.test_helpers uses a module listed above it, which is the healthy direction.
39→14 snarkos_node_router.test_helpers uses snarkos_node_tcp.protocols.handshake✕
- Connections
- 1 pair of types, where a type in snarkos_node_router.test_helpers uses a type in snarkos_node_tcp.protocols.handshake.
- The types involved
snarkos_node_router.test_helpers.TestRouter→snarkos_node_tcp.protocols.handshake.Handshake
- Direction
- snarkos_node_router.test_helpers uses snarkos_node_tcp.protocols.handshake, so a change to snarkos_node_tcp.protocols.handshake can break snarkos_node_router.test_helpers, while a change to snarkos_node_router.test_helpers can't break snarkos_node_tcp.protocols.handshake.
- Position
- Below the diagonal: snarkos_node_router.test_helpers uses a module listed above it, which is the healthy direction.
39→15 snarkos_node_router.test_helpers uses snarkos_node_tcp.protocols.on_connect✕
- Connections
- 1 pair of types, where a type in snarkos_node_router.test_helpers uses a type in snarkos_node_tcp.protocols.on_connect.
- The types involved
snarkos_node_router.test_helpers.TestRouter→snarkos_node_tcp.protocols.on_connect.OnConnect
- Direction
- snarkos_node_router.test_helpers uses snarkos_node_tcp.protocols.on_connect, so a change to snarkos_node_tcp.protocols.on_connect can break snarkos_node_router.test_helpers, while a change to snarkos_node_router.test_helpers can't break snarkos_node_tcp.protocols.on_connect.
- Position
- Below the diagonal: snarkos_node_router.test_helpers uses a module listed above it, which is the healthy direction.
39→16 snarkos_node_router.test_helpers uses snarkos_node_bft_events.block_request✕
- Connections
- 1 pair of types, where a type in snarkos_node_router.test_helpers uses a type in snarkos_node_bft_events.block_request.
- The types involved
snarkos_node_router.test_helpers.TestRouter→snarkos_node_bft_events.block_request.BlockRequest
- Direction
- snarkos_node_router.test_helpers uses snarkos_node_bft_events.block_request, so a change to snarkos_node_bft_events.block_request can break snarkos_node_router.test_helpers, while a change to snarkos_node_router.test_helpers can't break snarkos_node_bft_events.block_request.
- Position
- Below the diagonal: snarkos_node_router.test_helpers uses a module listed above it, which is the healthy direction.
39→17 snarkos_node_router.test_helpers uses snarkos_node_router_messages.ping✕
- Connections
- 1 pair of types, where a type in snarkos_node_router.test_helpers uses a type in snarkos_node_router_messages.ping.
- The types involved
snarkos_node_router.test_helpers.TestRouter→snarkos_node_router_messages.ping.Ping
- Direction
- snarkos_node_router.test_helpers uses snarkos_node_router_messages.ping, so a change to snarkos_node_router_messages.ping can break snarkos_node_router.test_helpers, while a change to snarkos_node_router.test_helpers can't break snarkos_node_router_messages.ping.
- Position
- Below the diagonal: snarkos_node_router.test_helpers uses a module listed above it, which is the healthy direction.
39→18 snarkos_node_router.test_helpers uses snarkos_node_tcp.protocols.reading✕
- Connections
- 1 pair of types, where a type in snarkos_node_router.test_helpers uses a type in snarkos_node_tcp.protocols.reading.
- The types involved
snarkos_node_router.test_helpers.TestRouter→snarkos_node_tcp.protocols.reading.Reading
- Direction
- snarkos_node_router.test_helpers uses snarkos_node_tcp.protocols.reading, so a change to snarkos_node_tcp.protocols.reading can break snarkos_node_router.test_helpers, while a change to snarkos_node_router.test_helpers can't break snarkos_node_tcp.protocols.reading.
- Position
- Below the diagonal: snarkos_node_router.test_helpers uses a module listed above it, which is the healthy direction.
39→19 snarkos_node_router.test_helpers uses snarkos_node_tcp.protocols.writing✕
- Connections
- 1 pair of types, where a type in snarkos_node_router.test_helpers uses a type in snarkos_node_tcp.protocols.writing.
- The types involved
snarkos_node_router.test_helpers.TestRouter→snarkos_node_tcp.protocols.writing.Writing
- Direction
- snarkos_node_router.test_helpers uses snarkos_node_tcp.protocols.writing, so a change to snarkos_node_tcp.protocols.writing can break snarkos_node_router.test_helpers, while a change to snarkos_node_router.test_helpers can't break snarkos_node_tcp.protocols.writing.
- Position
- Below the diagonal: snarkos_node_router.test_helpers uses a module listed above it, which is the healthy direction.
39→21 snarkos_node_router.test_helpers uses snarkos_node_router✕
- Connections
- 1 pair of types, where a type in snarkos_node_router.test_helpers uses a type in snarkos_node_router.
- The types involved
snarkos_node_router.test_helpers.TestRouter→snarkos_node_router.Router
- Direction
- snarkos_node_router.test_helpers uses snarkos_node_router, so a change to snarkos_node_router can break snarkos_node_router.test_helpers, while a change to snarkos_node_router.test_helpers can't break snarkos_node_router.
- Position
- Below the diagonal: snarkos_node_router.test_helpers uses a module listed above it, which is the healthy direction.
39→23 snarkos_node_router.test_helpers uses snarkos_node_router.outbound✕
- Connections
- 1 pair of types, where a type in snarkos_node_router.test_helpers uses a type in snarkos_node_router.outbound.
- The types involved
snarkos_node_router.test_helpers.TestRouter→snarkos_node_router.outbound.Outbound
- Direction
- snarkos_node_router.test_helpers uses snarkos_node_router.outbound, so a change to snarkos_node_router.outbound can break snarkos_node_router.test_helpers, while a change to snarkos_node_router.test_helpers can't break snarkos_node_router.outbound.
- Position
- Below the diagonal: snarkos_node_router.test_helpers uses a module listed above it, which is the healthy direction.
39→27 snarkos_node_router.test_helpers uses snarkos_node_router.heartbeat✕
- Connections
- 1 pair of types, where a type in snarkos_node_router.test_helpers uses a type in snarkos_node_router.heartbeat.
- The types involved
snarkos_node_router.test_helpers.TestRouter→snarkos_node_router.heartbeat.Heartbeat
- Direction
- snarkos_node_router.test_helpers uses snarkos_node_router.heartbeat, so a change to snarkos_node_router.heartbeat can break snarkos_node_router.test_helpers, while a change to snarkos_node_router.test_helpers can't break snarkos_node_router.heartbeat.
- Position
- Below the diagonal: snarkos_node_router.test_helpers uses a module listed above it, which is the healthy direction.
39→28 snarkos_node_router.test_helpers uses snarkos_node_router.inbound✕
- Connections
- 1 pair of types, where a type in snarkos_node_router.test_helpers uses a type in snarkos_node_router.inbound.
- The types involved
snarkos_node_router.test_helpers.TestRouter→snarkos_node_router.inbound.Inbound
- Direction
- snarkos_node_router.test_helpers uses snarkos_node_router.inbound, so a change to snarkos_node_router.inbound can break snarkos_node_router.test_helpers, while a change to snarkos_node_router.test_helpers can't break snarkos_node_router.inbound.
- Position
- Below the diagonal: snarkos_node_router.test_helpers uses a module listed above it, which is the healthy direction.
39→30 snarkos_node_router.test_helpers uses snarkos_node_router.routing✕
- Connections
- 1 pair of types, where a type in snarkos_node_router.test_helpers uses a type in snarkos_node_router.routing.
- The types involved
snarkos_node_router.test_helpers.TestRouter→snarkos_node_router.routing.Routing
- Direction
- snarkos_node_router.test_helpers uses snarkos_node_router.routing, so a change to snarkos_node_router.routing can break snarkos_node_router.test_helpers, while a change to snarkos_node_router.test_helpers can't break snarkos_node_router.routing.
- Position
- Below the diagonal: snarkos_node_router.test_helpers uses a module listed above it, which is the healthy direction.
39→35 snarkos_node_router.test_helpers uses snarkos_account✕
- Connections
- 1 pair of types, where a type in snarkos_node_router.test_helpers uses a type in snarkos_account.
- The types involved
snarkos_node_router.test_helpers.test_helpers$module→snarkos_account.Account
- Direction
- snarkos_node_router.test_helpers uses snarkos_account, so a change to snarkos_account can break snarkos_node_router.test_helpers, while a change to snarkos_node_router.test_helpers can't break snarkos_account.
- Position
- Below the diagonal: snarkos_node_router.test_helpers uses a module listed above it, which is the healthy direction.
40→5 snarkos_node.bootstrap_client uses snarkos_node_network.node_type✕
- Connections
- 1 pair of types, where a type in snarkos_node.bootstrap_client uses a type in snarkos_node_network.node_type.
- The types involved
snarkos_node.bootstrap_client.BootstrapClient→snarkos_node_network.node_type.NodeType
- Direction
- snarkos_node.bootstrap_client uses snarkos_node_network.node_type, so a change to snarkos_node_network.node_type can break snarkos_node.bootstrap_client, while a change to snarkos_node.bootstrap_client can't break snarkos_node_network.node_type.
- Position
- Below the diagonal: snarkos_node.bootstrap_client uses a module listed above it, which is the healthy direction.
40→7 snarkos_node.bootstrap_client uses snarkos_node_tcp.helpers.connections✕
- Connections
- 3 pairs of types, where a type in snarkos_node.bootstrap_client uses a type in snarkos_node_tcp.helpers.connections.
- The types involved
snarkos_node.bootstrap_client.BootstrapClient→snarkos_node_tcp.helpers.connections.Connectionsnarkos_node.bootstrap_client.BootstrapClient→snarkos_node_tcp.helpers.connections.ConnectionSidesnarkos_node.bootstrap_client.BootstrapClient→snarkos_node_tcp.helpers.connections.DisconnectOrigin
- Direction
- snarkos_node.bootstrap_client uses snarkos_node_tcp.helpers.connections, so a change to snarkos_node_tcp.helpers.connections can break snarkos_node.bootstrap_client, while a change to snarkos_node.bootstrap_client can't break snarkos_node_tcp.helpers.connections.
- Position
- Below the diagonal: snarkos_node.bootstrap_client uses a module listed above it, which is the healthy direction.
40→9 snarkos_node.bootstrap_client uses snarkos_node_tcp.tcp✕
- Connections
- 2 pairs of types, where a type in snarkos_node.bootstrap_client uses a type in snarkos_node_tcp.tcp.
- The types involved
snarkos_node.bootstrap_client.BootstrapClient→snarkos_node_tcp.tcp.Tcpsnarkos_node.bootstrap_client.InnerBootstrapClient→snarkos_node_tcp.tcp.Tcp
- Direction
- snarkos_node.bootstrap_client uses snarkos_node_tcp.tcp, so a change to snarkos_node_tcp.tcp can break snarkos_node.bootstrap_client, while a change to snarkos_node.bootstrap_client can't break snarkos_node_tcp.tcp.
- Position
- Below the diagonal: snarkos_node.bootstrap_client uses a module listed above it, which is the healthy direction.
40→10 snarkos_node.bootstrap_client uses snarkos_node_bft_events.disconnect✕
- Connections
- 2 pairs of types, where a type in snarkos_node.bootstrap_client uses a type in snarkos_node_bft_events.disconnect.
- The types involved
snarkos_node.bootstrap_client.BootstrapClient→snarkos_node_bft_events.disconnect.Disconnectsnarkos_node.bootstrap_client.BootstrapClient→snarkos_node_bft_events.disconnect.DisconnectReason
- Direction
- snarkos_node.bootstrap_client uses snarkos_node_bft_events.disconnect, so a change to snarkos_node_bft_events.disconnect can break snarkos_node.bootstrap_client, while a change to snarkos_node.bootstrap_client can't break snarkos_node_bft_events.disconnect.
- Position
- Below the diagonal: snarkos_node.bootstrap_client uses a module listed above it, which is the healthy direction.
40→11 snarkos_node.bootstrap_client uses snarkos_node_tcp✕
- Connections
- 1 pair of types, where a type in snarkos_node.bootstrap_client uses a type in snarkos_node_tcp.
- The types involved
snarkos_node.bootstrap_client.BootstrapClient→snarkos_node_tcp.P2P
- Direction
- snarkos_node.bootstrap_client uses snarkos_node_tcp, so a change to snarkos_node_tcp can break snarkos_node.bootstrap_client, while a change to snarkos_node.bootstrap_client can't break snarkos_node_tcp.
- Position
- Below the diagonal: snarkos_node.bootstrap_client uses a module listed above it, which is the healthy direction.
40→12 snarkos_node.bootstrap_client uses snarkos_node_network.peering✕
- Connections
- 1 pair of types, where a type in snarkos_node.bootstrap_client uses a type in snarkos_node_network.peering.
- The types involved
snarkos_node.bootstrap_client.BootstrapClient→snarkos_node_network.peering.PeerPoolHandling
- Direction
- snarkos_node.bootstrap_client uses snarkos_node_network.peering, so a change to snarkos_node_network.peering can break snarkos_node.bootstrap_client, while a change to snarkos_node.bootstrap_client can't break snarkos_node_network.peering.
- Position
- Below the diagonal: snarkos_node.bootstrap_client uses a module listed above it, which is the healthy direction.
40→13 snarkos_node.bootstrap_client uses snarkos_node_router_messages✕
- Connections
- 1 pair of types, where a type in snarkos_node.bootstrap_client uses a type in snarkos_node_router_messages.
- The types involved
snarkos_node.bootstrap_client.BootstrapClient→snarkos_node_router_messages.Message
- Direction
- snarkos_node.bootstrap_client uses snarkos_node_router_messages, so a change to snarkos_node_router_messages can break snarkos_node.bootstrap_client, while a change to snarkos_node.bootstrap_client can't break snarkos_node_router_messages.
- Position
- Below the diagonal: snarkos_node.bootstrap_client uses a module listed above it, which is the healthy direction.
40→14 snarkos_node.bootstrap_client uses snarkos_node_tcp.protocols.handshake✕
- Connections
- 1 pair of types, where a type in snarkos_node.bootstrap_client uses a type in snarkos_node_tcp.protocols.handshake.
- The types involved
snarkos_node.bootstrap_client.BootstrapClient→snarkos_node_tcp.protocols.handshake.Handshake
- Direction
- snarkos_node.bootstrap_client uses snarkos_node_tcp.protocols.handshake, so a change to snarkos_node_tcp.protocols.handshake can break snarkos_node.bootstrap_client, while a change to snarkos_node.bootstrap_client can't break snarkos_node_tcp.protocols.handshake.
- Position
- Below the diagonal: snarkos_node.bootstrap_client uses a module listed above it, which is the healthy direction.
40→15 snarkos_node.bootstrap_client uses snarkos_node_tcp.protocols.on_connect✕
- Connections
- 1 pair of types, where a type in snarkos_node.bootstrap_client uses a type in snarkos_node_tcp.protocols.on_connect.
- The types involved
snarkos_node.bootstrap_client.BootstrapClient→snarkos_node_tcp.protocols.on_connect.OnConnect
- Direction
- snarkos_node.bootstrap_client uses snarkos_node_tcp.protocols.on_connect, so a change to snarkos_node_tcp.protocols.on_connect can break snarkos_node.bootstrap_client, while a change to snarkos_node.bootstrap_client can't break snarkos_node_tcp.protocols.on_connect.
- Position
- Below the diagonal: snarkos_node.bootstrap_client uses a module listed above it, which is the healthy direction.
40→18 snarkos_node.bootstrap_client uses snarkos_node_tcp.protocols.reading✕
- Connections
- 1 pair of types, where a type in snarkos_node.bootstrap_client uses a type in snarkos_node_tcp.protocols.reading.
- The types involved
snarkos_node.bootstrap_client.BootstrapClient→snarkos_node_tcp.protocols.reading.Reading
- Direction
- snarkos_node.bootstrap_client uses snarkos_node_tcp.protocols.reading, so a change to snarkos_node_tcp.protocols.reading can break snarkos_node.bootstrap_client, while a change to snarkos_node.bootstrap_client can't break snarkos_node_tcp.protocols.reading.
- Position
- Below the diagonal: snarkos_node.bootstrap_client uses a module listed above it, which is the healthy direction.
40→19 snarkos_node.bootstrap_client uses snarkos_node_tcp.protocols.writing✕
- Connections
- 1 pair of types, where a type in snarkos_node.bootstrap_client uses a type in snarkos_node_tcp.protocols.writing.
- The types involved
snarkos_node.bootstrap_client.BootstrapClient→snarkos_node_tcp.protocols.writing.Writing
- Direction
- snarkos_node.bootstrap_client uses snarkos_node_tcp.protocols.writing, so a change to snarkos_node_tcp.protocols.writing can break snarkos_node.bootstrap_client, while a change to snarkos_node.bootstrap_client can't break snarkos_node_tcp.protocols.writing.
- Position
- Below the diagonal: snarkos_node.bootstrap_client uses a module listed above it, which is the healthy direction.
40→24 snarkos_node.bootstrap_client uses snarkos_utilities.signals✕
- Connections
- 1 pair of types, where a type in snarkos_node.bootstrap_client uses a type in snarkos_utilities.signals.
- The types involved
snarkos_node.bootstrap_client.BootstrapClient→snarkos_utilities.signals.SignalHandler
- Direction
- snarkos_node.bootstrap_client uses snarkos_utilities.signals, so a change to snarkos_utilities.signals can break snarkos_node.bootstrap_client, while a change to snarkos_node.bootstrap_client can't break snarkos_utilities.signals.
- Position
- Below the diagonal: snarkos_node.bootstrap_client uses a module listed above it, which is the healthy direction.
40→35 snarkos_node.bootstrap_client uses snarkos_account✕
- Connections
- 2 pairs of types, where a type in snarkos_node.bootstrap_client uses a type in snarkos_account.
- The types involved
snarkos_node.bootstrap_client.BootstrapClient→snarkos_account.Accountsnarkos_node.bootstrap_client.InnerBootstrapClient→snarkos_account.Account
- Direction
- snarkos_node.bootstrap_client uses snarkos_account, so a change to snarkos_account can break snarkos_node.bootstrap_client, while a change to snarkos_node.bootstrap_client can't break snarkos_account.
- Position
- Below the diagonal: snarkos_node.bootstrap_client uses a module listed above it, which is the healthy direction.
40→36 snarkos_node.bootstrap_client uses snarkos_node.client✕
- Connections
- 1 pair of types, where a type in snarkos_node.bootstrap_client uses a type in snarkos_node.client.
- The types involved
snarkos_node.bootstrap_client.InnerBootstrapClient→snarkos_node.client.Client
- Direction
- snarkos_node.bootstrap_client uses snarkos_node.client, so a change to snarkos_node.client can break snarkos_node.bootstrap_client, while a change to snarkos_node.bootstrap_client can't break snarkos_node.client.
- Position
- Below the diagonal: snarkos_node.bootstrap_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 | 56 | High / Critical |
| A07:2025 — Authentication Failures | 22 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 14 | Medium |
| A02:2025 — Security Misconfiguration | 2 | High / Critical |
Roadmap
First, address the six leaked secrets by resolving findings in REDACTED and REDACTED, and establish immutable event handling to ensure data integrity. Next, harden outbound HTTP resilience by enforcing request timeouts and adding retry logic with back-off for all client calls. Finally, complete the architecture documentation by recording significant design decisions as formal ADRs to improve long-term maintainability.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 6 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (5), REDACTED. | +3.7 pts | Low | REDACTED Scanning |
| Improve Immutable events (currently 1.0/10). | +6.4 pts | Medium | Immutable events |
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +1.7 pts | Low | ADR Quality |
| Give every client a whole-request bound: `reqwest::Client::builder().timeout(Duration::from_secs(10))` (never `reqwest::get` or `Client::new()`, which have none), ureq's `timeout_global`, or wrap the call in `tokio::time::timeout`; add retry with back-off (`reqwest-retry`'s `RetryTransientMiddleware`, `backoff`) around dependencies that fail. | +2.2 pts | Medium | Outbound HTTP resilience |
| 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.6 pts | Medium | Architecture documentation |
| Interpolated log message defeats structured logging | +1.2 pts | Medium | Structured logging |
| Add a `healthcheck:` to the served compose service — probing the endpoint it already answers on where it has one — with `depends_on: condition: service_healthy` on whatever waits for it, and keep the deployed image tag immutable and recorded so rolling back is re-pointing at the previous tag rather than rebuilding. | +1.1 pts | Medium | Deployment & Rollback |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +1.1 pts | Medium | Release Hygiene |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.5 | 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 | 4.4 | Mixed | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 4.6 | Mixed | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 4.6 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 4.6 | Mixed | Secrets (history): REDACTED: REDACTED |
| node/src/client/mod.rs | 4.8 | Mixed | Cognitive Complexity: Client::initialize_solution_verification (cognitive 28) |
| REDACTED | 5.1 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 5.8 | Mixed | Secrets (history): REDACTED: REDACTED |
| node/bft/src/gateway.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| node/bft/src/primary.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| cli/src/commands/start.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| node/bft/src/sync/mod.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| node/sync/src/block_sync.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| node/bft/src/helpers/storage.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| node/cdn/src/blocks.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| node/rest/src/routes.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| node/consensus/src/lib.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| REDACTED | 6.1 | Mixed | Dependency Vulnerabilities: Medium advisory (unmaintained): REDACTED |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
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. 55 of 55 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
What we checked — 55 dimensions across the health lenses
- Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 361 of 409 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, 109 test files), but it was not re-run: no test result was produced. 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.
- 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. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D21 Naming Consistency — 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.
- 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.
- C1 Data Protection — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'rocksdb' is imported (node/src/node.rs:38), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- C3 Audit Trail — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'rocksdb' is imported (node/src/node.rs:38), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- C4 Data Retention — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'rocksdb' is imported (node/src/node.rs:38), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- C5 Data-Subject Rights — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'rocksdb' is imported (node/src/node.rs:38), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- GD1 Unfinished & placeholder code — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- M4 Documentation accuracy — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- X12 Unreachable branch — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X13 Undrained process stream — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X16 Unfloored truncation loop — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X17 Uncapped recursion over a caller-supplied document — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X18 Disposal-pattern correctness — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X19 Unrestored process-global state — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X22 Contradicted release guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Java, TypeScript/JavaScript, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X23 Unguarded diagnostic materialisation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X24 Document value interpolated into markup unescaped — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X25 Inert configuration knob — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart and Ruby source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart or Ruby was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X3 Exception handling — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go and JavaScript/TypeScript source only, and no C# was loaded and no PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go, JavaScript or TypeScript was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X4 Structured logging — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 477 further occurrence(s) are not listed individually; the score already reflects all 517.
- X5 Nullable reference types — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax and MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, and Kotlin source only, and no C# was loaded, no TypeScript was found, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
15 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was Gateway::inbound at 57. A further 8 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being DisconnectReason::read_le at 21 — they are counted neither in the figure above nor in this dimension's score. 2 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold functions was excluded, so the exclusion is disclosed nowhere in the file itself: node/router/messages/src/helpers/disconnect.rs (DisconnectReason::read_le at 21), node/bft/events/src/lib.rs (Event::read_le at 18). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 15 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with Gateway::inbound (cyclomatic 57), Inbound::inbound (cyclomatic 47), Primary::propose_batch (cyclomatic 46). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 15 together lifts Cyclomatic Complexity from 7.4 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
46 method(s) exceeded the cognitive complexity threshold of 15; the worst was Primary::propose_batch at 93.
What to do
- Bring the 4 bodies over 60 down to 60 or less in Cognitive Complexity — start with Primary::propose_batch (cognitive 93), Gateway::inbound (cognitive 70), Inbound::inbound (cognitive 64). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 4 together lifts Cognitive Complexity from 5.7 to about 6.2/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
- 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
28 god class(es) detected.
What to do
- Resolve the 8 MethodTooLong finding(s) in God Classes — start with primary.rs (2), lib.rs (2), gateway.rs. — One of this dimension's main actionable groups (8 warning-level).
- Resolve the 7 ClassTooLong finding(s) in God Classes — start with primary.rs, gateway.rs, block_sync.rs. — One of this dimension's main actionable groups (7 warning-level).
- Resolve the 6 TooManyMethods finding(s) in God Classes — start with lib.rs, gateway.rs, primary.rs. — One of this dimension's main actionable groups (6 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
33 duplicated block group(s) detected. A further 2 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.
What to do
- Resolve the 6 Duplicated block (13 lines × 2) finding(s) in Code Duplication — start with gateway.rs, cache.rs, node.rs. — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 5 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with gateway.rs (2), disconnect.rs (2), cache.rs. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 3 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with storage.rs, mod.rs, blocks.rs. — One of this dimension's main actionable groups (3 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
21 production modules (Cargo), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 5 module(s) off the main sequence, with abstractness counted on 20 of the 21 (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 5 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (5 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)
5 of 87 classes have LCOM4 above 3.
What to do
- Resolve the 5 Low cohesion finding(s) in Cohesion (LCOM4) — start with mod.rs (2), mock.rs, storage.rs. — One of this dimension's main actionable groups (5 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
545 test methods: 502 unit, 28 integration, 0 BDD, 15 e2e. The Rust suite contributes 545 `#[test]` function(s) across 109 file(s) declaring at least one; its unit/integration split is Cargo's own — 11 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
10 outdated, 0 yanked direct Cargo dependencies. Only DIRECT edges are graded: a transitive crate cannot be moved past what its parent's requirement admits, so reporting one would be advice its owner cannot take. A newer release is reported only where this repository's OWN requirement already admits it, so the remedy is `cargo update` and never a manifest edit — which means a release outside the declared range is deliberately NOT charged, because a written-down constraint is a decision rather than a defect. Note that a bare requirement is a CARET, and for a 0.x crate its ceiling is the minor. Whether any crate is UNMAINTAINED is not graded — crates.io publishes no maintenance status, and release age does not stand in for one. Known CVEs in this dependency graph are D30's question, read from REDACTED there.
D13 · REDACTED Scanning
3 secret(s) detected.
What to do
- Resolve the 6 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (5), REDACTED. — One of this dimension's main actionable groups (6 issue-level).
- Enforce REDACTED Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D14 · License Compliance
0 of 624 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. A further 61 crate(s) in the closure resolve from git, a path or a private registry and publish no licence this pass can read; they are outside this verdict. This repository publishes itself under Apache-2.0, which is its own choice and is not judged here.
D15 · Churn × Complexity Hotspots
Top hotspots: node/bft/src/primary.rs (38×46=1748); node/bft/src/gateway.rs (26×57=1482); cli/src/commands/start.rs (12×37=444) Repeated repair below the complexity floor: node/router/messages/src/helpers/codec.rs (5 of 8 changes were fixes); node/router/messages/src/unconfirmed_transaction.rs (3 of 5 changes were fixes)
What to do
- Resolve the 7 Hotspot finding(s) in Churn × Complexity Hotspots — start with primary.rs, gateway.rs, start.rs. — One of this dimension's main actionable groups (7 warning-level).
- Resolve the 2 Repeated repair finding(s) in Churn × Complexity Hotspots — start with codec.rs, unconfirmed_transaction.rs. — One of this dimension's main actionable groups (2 warning-level).
D16 · Bus Factor
15 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is node/rest/src/history_compat.rs. Counted over 142 of the 170 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 3 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (3 recommendation-level).
- Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
D17 · Explicit Debt
60 deducted task-comment markers across 51128 LoC (0.1/KLoC) → score 9.8. 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 60 TodoComment finding(s) in Explicit Debt — start with block_sync.rs (8), lib.rs (5), mod.rs (5). — One of this dimension's main actionable groups (60 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. 21 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 21 build units (Cargo) flagged as possibly oversized/incoherent.
D28 · Secrets (history)
15 finding(s): 0 critical, 15 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 15 REDACTED finding(s) in Secrets (history) — start with REDACTED (5), REDACTED (5), REDACTED (2). — One of this dimension's main actionable groups (15 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
56 finding(s): 0 critical, 55 high, 1 medium, 0 low. 48 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 6 file(s) — `.ci/test_full_upgrade.sh` (line 210, line 327), `.ci/test_reset_minority.sh` (line 31), `.ci/test_restart_majority.sh` (line 32), `REDACTED` (line 373), `node/bft/src/primary.rs` (line 431, line 436, line 441, …), … (+1 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 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 (3), REDACTED. — One of this dimension's main actionable groups (4 issue-level).
- No action in Static Analysis (SAST) — all 45 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 (45 issue-level, 0 of them charged here).
- No action in Static Analysis (SAST) — all 3 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 (3 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
4 finding(s): 0 critical, 0 high, 4 medium, 0 low.
What to do
- Resolve the 2 Medium advisory (unmaintained) finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Medium vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
D31 · IaC & Container Security
2 finding(s): 0 critical, 1 high, 1 medium, 0 low.
What to do
- Resolve the 1 High IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Medium IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D34 · Knowledge Freshness
13 of 142 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is node/bft/src/helpers/cache.rs. Counted over 142 of the 170 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
Strongest change-coupling: mock.rs↔prover.rs 80%; test_helpers.rs↔router.rs 71%; execute.rs↔transfer_private.rs 69%
What to do
- Resolve the 8 Change coupling finding(s) in Change Coupling — start with test_helpers.rs (2), mod.rs (2), mock.rs. — One of this dimension's main actionable groups (8 warning-level).
- Resolve the 1 Change coupling clique finding(s) in Change Coupling — start with deploy.rs. — One of this dimension's main actionable groups (1 warning-level).
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 4 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED (3), REDACTED. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
1 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.
What to do
- Resolve the 1 End-of-life runtime finding(s) in Platform End-of-Life — start with rust-toolchain.toml. — One of this dimension's main actionable groups (1 warning-level).
Frontend & cross-cutting dimensions
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX4 · Dependency direction
AX9 · CQS / query purity
C2 · Access Controls
ES1 · Fold determinism
ES2 · Immutable events
- `Event` conforms to a domain-event contract but carries a freely-mutable `pub` field. Events are immutable facts — model them with private fields (set once in the constructor) so a recorded event can never be rewritten. — node/bft/events/src/lib.rs:97
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
What to do
- Consider OpenTelemetry tracing/metrics (opentelemetry with tracing-opentelemetry) and a health-check endpoint (a /health route on your axum/actix router) for operability.
P3 · Security & performance tooling
What to do
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- Deployment is orchestrated by compose, but no service declares a `healthcheck:` and nothing pins a previous image to fall back to — the runtime can tell that the container is up, not that it is serving, so a bad release is harder to detect and reverse.
- Deployment is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever reaches the release trigger goes to production unreviewed, so a mistaken merge or tag is live before anyone can stop it.
What to do
- Add a `healthcheck:` to the served compose service — probing the endpoint it already answers on where it has one — with `depends_on: condition: service_healthy` on whatever waits for it, and keep the deployed image tag immutable and recorded so rolling back is re-pointing at the previous tag rather than rebuilding.
- Add an approval/environment gate (required reviewers / protection rules) before production promotion.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
P7 · Outbound HTTP resilience
- `ureq::post(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — cli/src/commands/developer/mod.rs:305
- `ureq::get(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. (×4) — cli/src/commands/developer/mod.rs:321, cli/src/commands/developer/mod.rs:338, cli/src/commands/developer/scan.rs:156, …
- `Client::builder()` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. (×2) — node/cdn/src/blocks.rs:174, node/cdn/src/blocks.rs:191
- `reqwest::Client::new(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — node/src/bootstrap_client/mod.rs:98
What to do
- Give every client a whole-request bound: `reqwest::Client::builder().timeout(Duration::from_secs(10))` (never `reqwest::get` or `Client::new()`, which have none), ureq's `timeout_global`, or wrap the call in `tokio::time::timeout`; add retry with back-off (`reqwest-retry`'s `RetryTransientMiddleware`, `backoff`) around dependencies that fail.
PF1 · Benchmark discipline
PF3 · Async & latency hygiene
S1 · Web-Security Posture
- This repository starts an HTTP server and nothing in its Rust source or committed `Rocket.toml` secures the transport: no TLS served (actix-web `bind_rustls`/`bind_openssl`, axum-server `bind_rustls` with a `RustlsConfig`, tonic `ServerTlsConfig`, a `TlsAcceptor`, Rocket's `[default.tls]`), no `Strict-Transport-Security` header, no `X-Forwarded-Proto` read from a TLS-terminating proxy — so its traffic may cross the network in clear text. (−2.0 on this card.) The server: `axum::serve(` (node/rest/src/lib.rs:504).
- 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(` (node/rest/src/lib.rs:504).
What to do
- Secure the server's transport: serve TLS itself (`HttpServer::bind_rustls_0_23(addr, config)` in actix-web, `axum_server::bind_rustls(addr, RustlsConfig::from_pem_file(…))`, tonic's `Server::builder().tls_config(ServerTlsConfig::new().identity(…))`, Rocket's `[default.tls]`), or run it behind a TLS-terminating proxy and check `X-Forwarded-Proto`; send `Strict-Transport-Security` once it is HTTPS-only.
- Set security response headers on what the server sends — actix-web's `DefaultHeaders::new().add((header::X_CONTENT_TYPE_OPTIONS, "nosniff"))`, tower-http's `SetResponseHeaderLayer::overriding(…)` on an axum router, or keep Rocket's default `Shield` — with `Content-Security-Policy`, `X-Content-Type-Options` and a frame policy on every response.
X1 · Async correctness
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X21 · Side-effecting pattern guard
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X30 · Support guard that admits what it rejects
X4 · Structured logging
- `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`. (×2) — utilities/src/signals.rs:130, node/tcp/src/protocols/writing.rs:130
- `error!` at line 145 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`. — utilities/src/signals.rs:145
- `debug!` at line 65 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`. (×2) — snarkos/main.rs:65, node/tcp/src/protocols/handshake.rs:65
- `info!` at line 99 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — snarkos/main.rs:99
- `debug!` at line 107 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`. — snarkos/main.rs:107
- `error!` at line 170 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`. — snarkos/main.rs:170
- `error!` at line 307 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`. — node/tcp/src/tcp.rs:307
- `trace!` at line 315 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`. — node/tcp/src/tcp.rs:315
- `debug!` at line 320 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`. — node/tcp/src/tcp.rs:320
- `error!` at line 342 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — node/tcp/src/tcp.rs:342
- `error!` at line 351 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`. — node/tcp/src/tcp.rs:351
- `debug!` at line 401 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`. — node/tcp/src/tcp.rs:401
- `debug!` at line 406 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`. — node/tcp/src/tcp.rs:406
- `warn!` at line 408 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — node/tcp/src/tcp.rs:408
- `debug!` at line 467 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`. — node/tcp/src/tcp.rs:467
- `error!` at line 472 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`. — node/tcp/src/tcp.rs:472
- `debug!` at line 482 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`. — node/tcp/src/tcp.rs:482
- `debug!` at line 489 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`. — node/tcp/src/tcp.rs:489
- `warn!` at line 498 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — node/tcp/src/tcp.rs:498
- `error!` at line 505 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`. — node/tcp/src/tcp.rs:505
- `debug!` at line 522 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`. — node/tcp/src/tcp.rs:522
- `debug!` at line 525 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`. — node/tcp/src/tcp.rs:525
- `error!` at line 538 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`. — node/tcp/src/tcp.rs:538
- `warn!` at line 568 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — node/tcp/src/tcp.rs:568
- `warn!` at line 571 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — node/tcp/src/tcp.rs:571
- `warn!` at line 581 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — node/tcp/src/tcp.rs:581
- `debug!` at line 615 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`. — node/tcp/src/tcp.rs:615
- `debug!` at line 74 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`. — node/tcp/src/protocols/handshake.rs:74
- `error!` 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: `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`. — node/tcp/src/protocols/reading.rs:165
- `error!` at line 226 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`. — node/tcp/src/protocols/reading.rs:226
- `trace!` at line 280 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`. — node/tcp/src/protocols/reading.rs:280
- `warn!` at line 321 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — node/tcp/src/protocols/reading.rs:321
- `error!` at line 161 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`. — node/tcp/src/protocols/writing.rs:161
- `trace!` at line 252 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`. — node/tcp/src/protocols/writing.rs:252
- `error!` at line 255 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`. — node/tcp/src/protocols/writing.rs:255
- `trace!` at line 466 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`. — node/sync/src/block_sync.rs:466
- `warn!` at line 478 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — node/sync/src/block_sync.rs:478
- `debug!` at line 484 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`. — node/sync/src/block_sync.rs:484
What to do
- Interpolated log message defeats structured logging
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 65% | Adequate — gated by X4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 96% | Exemplary | Strongest area. |
| Maturity | 62% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 54% | Adequate — gated by D13, P7 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 67% | Adequate — gated by D28, D29, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Event Sourcing | 49% | Weak — gated by ES2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 94% | Exemplary | Solid. |
Unscored — 4 check(s) recorded observations but carry no score
- AXH1 Runtime security headers — 11 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXI1 Runtime container hardening — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility (rendered) — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X10 Duplicated predicate — 3 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: this repository stores data through 'rocksdb' (node/src/node.rs:38) but declares no persisted model this check reads (Diesel table! columns, SeaORM entity / Diesel model / sqlx FromRow struct fields, CREATE TABLE and ALTER TABLE … ADD columns in SQL migrations and SQL string literals). Personal data may be written through raw SQL or a hosted backend, so whether its changes need an audit trail could not be established, and the trail's absence is not scored.
- C4 Data Retention — Not assessed: this repository stores data through 'rocksdb' (node/src/node.rs:38) but declares no persisted model this check reads (Diesel table! columns, SeaORM entity / Diesel model / sqlx FromRow struct fields, CREATE TABLE and ALTER TABLE … ADD columns in SQL migrations and SQL string literals). Personal data may be written through raw SQL or a hosted backend, so whether a retention limit applies here could not be established, and its absence is not scored.
- C5 Data-Subject Rights — Not assessed: this repository stores data through 'rocksdb' (node/src/node.rs:38) but declares no persisted model this check reads (Diesel table! columns, SeaORM entity / Diesel model / sqlx FromRow struct fields, CREATE TABLE and ALTER TABLE … ADD columns in SQL migrations and SQL string literals). Personal data may be written through raw SQL or a hosted backend, so whether data-subject rights apply here could not be established, and their absence is not scored.
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 62 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one.
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. 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
- AX8 Test isolation — no test/production split to check
- AXA1 Runtime unauthenticated reachability — This run crawled public routes only — it had no logged-in session, so there is no authenticated surface to compare anonymous access against and nothing was measured. This is a statement about this run, not about your application: nothing here says access control is missing, and nothing here says it is present.
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXS1 Runtime exposed surface — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- C1 Data Protection — Not assessed: this repository stores data through 'rocksdb' (node/src/node.rs:38) but declares no persisted model this check reads (Diesel table! columns, SeaORM entity / Diesel model / sqlx FromRow struct fields, CREATE TABLE and ALTER TABLE … ADD columns in SQL migrations and SQL string literals). Personal data may be written through raw SQL or a hosted backend, so the absence of a personal-data field here is not evidence that none is stored, and encryption at rest is not scored over a subject that could not be established.
- D10 Test Quality — ~5124 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; Python, Rust, html not measured.
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed Rust surface was not measured.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ projects each declaring an entity of their own. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C# and Visual Basic comments only — this repository's production source is .rs, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.rs), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 6 value object(s); 1 domain event(s); its domain events are published by services or handlers — no domain entity raises one
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF2 Allocation hygiene — Not applicable: Rust spells out every heap allocation and makes borrowed slices (&[T], &str) its ordinary parameter types, so the allocation-aware style this card rewards elsewhere is the language's baseline rather than a rung to climb.
- X12 Unreachable branch — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X13 Undrained process stream — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X16 Unfloored truncation loop — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X17 Uncapped recursion over a caller-supplied document — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X18 Disposal-pattern correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X19 Unrestored process-global state — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X2 Cancellation propagation — no C# was loaded; this repository's Rust was read, and no request in it can be cancelled by a caller — a Rust request takes no token: a future is cancelled by dropping it, from outside the call (select!, a timeout, an aborted task), and reqwest, hyper and tonic take none
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X22 Contradicted release guard — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X23 Unguarded diagnostic materialisation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X24 Document value interpolated into markup unescaped — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X25 Inert configuration knob — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. Rust's compiler refuses the unsynchronised version: a collection shared between a callback's thread and the waiting body must be `Sync`, which a `Vec`, `VecDeque` or `HashMap` is only behind a `Mutex`/`RwLock`, so the race this check looks for cannot be written in safe Rust. Not a gap in the analyzer and not a finding about your code.
- X3 Exception handling — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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 — 78 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Mutable domain event: Event node/bft/events/src/lib.rs:97
Serious — 247 finding(s)
- TodoComment node/tests/common/test_peer.rs:155
- TodoComment node/tcp/src/tcp.rs:94
- TodoComment node/tcp/src/tcp.rs:305
- TodoComment node/sync/src/block_sync.rs:78
- TodoComment node/sync/src/block_sync.rs:414
- TodoComment node/sync/src/block_sync.rs:689
- TodoComment node/sync/src/block_sync.rs:916
- TodoComment node/sync/src/block_sync.rs:1147
- TodoComment node/sync/src/block_sync.rs:1443
- TodoComment node/sync/src/block_sync.rs:1477
- TodoComment node/sync/src/block_sync.rs:1587
- TodoComment node/sync/src/ping.rs:38
- TodoComment node/sync/locators/src/block_locators.rs:108
- TodoComment node/sync/locators/src/block_locators.rs:216
- TodoComment node/sync/locators/src/block_locators.rs:270
- TodoComment node/src/lib.rs:77
- TodoComment node/src/validator/mod.rs:297
- TodoComment node/src/validator/router.rs:56
- TodoComment node/src/prover/router.rs:164
- TodoComment node/src/client/router.rs:148
- TodoComment node/src/client/router.rs:262
- TodoComment node/bft/src/gateway.rs:772
- TodoComment node/router/tests/cleanups.rs:46
- TodoComment node/router/src/heartbeat.rs:86
- TodoComment node/router/src/heartbeat.rs:226
- Runtime security header not set: content-security-policy
- Runtime security header not set: cross-origin-embedder-policy
- Runtime security header not set: cross-origin-opener-policy
- Runtime security header not set: cross-origin-resource-policy
- Runtime security header not set: permissions-policy
- Runtime security header not set: referrer-policy
- Runtime security header not set: strict-transport-security
- Runtime security header not set: x-content-type-options
- Runtime security header not set: x-dns-prefetch-control
- Runtime security header not set: x-frame-options
- Runtime security header not set: x-permitted-cross-domain-policies
- MethodTooLong: Primary.propose_batch node/bft/src/primary.rs:476
- MethodTooLong: Gateway.inbound node/bft/src/gateway.rs:604
- MethodTooLong: Primary.start_handlers node/bft/src/primary.rs:1406
- MethodTooLong: Inbound.inbound node/router/src/inbound.rs:80
- MethodTooLong: BFT.commit_leader_certificate node/bft/src/bft.rs:596
- MethodTooLong: Rest.build_routes node/rest/src/lib.rs:280
- MethodTooLong: Start.parse_node cli/src/commands/start.rs:800
- MethodTooLong: Consensus.try_advance_to_next_block node/consensus/src/lib.rs:633
- Change coupling: mock.rs ↔ prover.rs node/bft/ledger-service/src/mock.rs:1
- Change coupling: test_helpers.rs ↔ router.rs node/router/src/test_helpers.rs:1
- Change coupling: test_helpers.rs ↔ router.rs node/router/src/test_helpers.rs:1
- Change coupling: memory.rs ↔ persistent.rs node/bft/storage-service/src/memory.rs:1
- Change coupling: certificate_response.rs ↔ storage.rs node/bft/events/src/certificate_response.rs:1
- Change coupling: mod.rs ↔ mod.rs node/src/client/mod.rs:1
- Change coupling: ready.rs ↔ primary.rs node/bft/src/helpers/ready.rs:1
- Change coupling: mod.rs ↔ mod.rs node/src/prover/mod.rs:1
- Outbound HTTP without resilience cli/src/commands/developer/mod.rs:305
- Outbound HTTP without resilience cli/src/commands/developer/mod.rs:321
- Outbound HTTP without resilience cli/src/commands/developer/mod.rs:338
- Outbound HTTP without resilience cli/src/commands/developer/scan.rs:156
- Outbound HTTP without resilience cli/src/commands/developer/scan.rs:404
- Outbound HTTP without resilience node/cdn/src/blocks.rs:174
- Outbound HTTP without resilience node/cdn/src/blocks.rs:191
- Outbound HTTP without resilience node/src/bootstrap_client/mod.rs:98
- Hotspot: node/bft/src/primary.rs node/bft/src/primary.rs:476
- Hotspot: node/bft/src/gateway.rs node/bft/src/gateway.rs:604
- Hotspot: cli/src/commands/start.rs cli/src/commands/start.rs:800
- Hotspot: node/bft/src/helpers/storage.rs node/bft/src/helpers/storage.rs:915
- Hotspot: node/bft/src/bft.rs node/bft/src/bft.rs:596
- Hotspot: node/src/node.rs node/src/node.rs:385
- Hotspot: node/router/src/inbound.rs node/router/src/inbound.rs:80
- BlockSync::prepare_block_requests (cognitive 40) node/sync/src/block_sync.rs:974
- BlockSync::update_peer_locators (cognitive 21) node/sync/src/block_sync.rs:813
- BlockSync::send_block_requests (cognitive 20) node/sync/src/block_sync.rs:433
- BlockSync::try_issuing_block_requests (cognitive 18) node/sync/src/block_sync.rs:545
- BlockSync::insert_block_responses (cognitive 17) node/sync/src/block_sync.rs:594
- BlockSync::try_advancing_block_synchronization (cognitive 16) node/sync/src/block_sync.rs:683
- BlockSync::handle_block_request_timeouts (cognitive 16) node/sync/src/block_sync.rs:1347
- ClassTooLong: Primary node/bft/src/primary.rs:153
- ClassTooLong: Gateway node/bft/src/gateway.rs:173
- ClassTooLong: BlockSync node/sync/src/block_sync.rs:202
- ClassTooLong: Start cli/src/commands/start.rs:140
- ClassTooLong: Sync node/bft/src/sync/mod.rs:81
- ClassTooLong: BFT node/bft/src/bft.rs:61
- ClassTooLong: Consensus node/consensus/src/lib.rs:102
- TooManyMethods: Rest node/rest/src/lib.rs:197
- TooManyMethods: Gateway node/bft/src/gateway.rs:173
- TooManyMethods: Primary node/bft/src/primary.rs:153
- TooManyMethods: BlockSync node/sync/src/block_sync.rs:202
- TooManyMethods: Storage node/bft/src/helpers/storage.rs:74
- TooManyMethods: Worker node/bft/src/worker.rs:52
- FileTooLong: src/primary.rs node/bft/src/primary.rs
- FileTooLong: src/gateway.rs node/bft/src/gateway.rs
- FileTooLong: src/routes.rs node/rest/src/routes.rs
- FileTooLong: src/block_sync.rs node/sync/src/block_sync.rs
- FileTooLong: commands/start.rs cli/src/commands/start.rs
- FileTooLong: sync/mod.rs node/bft/src/sync/mod.rs
- Duplicated block (13 lines × 2) node/bft/src/gateway.rs:728
- Duplicated block (13 lines × 2) node/bft/src/helpers/cache.rs:216
- Duplicated block (13 lines × 2) node/src/node.rs:142
- Duplicated block (13 lines × 2) node/bft/src/bft.rs:333
- Duplicated block (13 lines × 2) cli/src/commands/developer/deploy.rs:217
- Duplicated block (13 lines × 2) node/src/client/mod.rs:602
- Gateway::inbound (cognitive 70) node/bft/src/gateway.rs:604
- Gateway::perform_handshake (cognitive 28) node/bft/src/gateway.rs:1560
- Gateway::log_connected_validators (cognitive 17) node/bft/src/gateway.rs:998
- Gateway::handle_bootstrap_peers (cognitive 17) node/bft/src/gateway.rs:1150
- Gateway::handle_min_connected_validators (cognitive 17) node/bft/src/gateway.rs:1231
- Duplicated block (8 lines × 2) node/bft/src/gateway.rs:283
- Duplicated block (8 lines × 2) node/bft/src/gateway.rs:1909
- Duplicated block (8 lines × 2) node/tcp/src/protocols/disconnect.rs:53
- Duplicated block (8 lines × 2) node/bft/events/src/disconnect.rs:74
- Duplicated block (8 lines × 2) node/bft/src/helpers/cache.rs:205
- Off the main sequence: snarkos-account
- Off the main sequence: snarkos-node-metrics
- Off the main sequence: snarkos-node-sync-locators
- Off the main sequence: snarkos-utilities
- Off the main sequence: snarkos-node-network
- Low cohesion: MockLedgerService (LCOM4 7) node/bft/ledger-service/src/mock.rs:42
- Low cohesion: Storage (LCOM4 6) node/bft/src/helpers/storage.rs:74
- Low cohesion: Gateway (LCOM4 4) node/bft/src/gateway.rs:173
- Low cohesion: Client (LCOM4 4) node/src/client/mod.rs:100
- Low cohesion: Prover (LCOM4 4) node/src/prover/mod.rs:71
- Primary::propose_batch (cognitive 93) node/bft/src/primary.rs:476
- Primary::start_handlers (cognitive 63) node/bft/src/primary.rs:1406
- Primary::process_batch_propose_from_peer (cognitive 27) node/bft/src/primary.rs:892
- Primary::add_signature_to_batch (cognitive 17) node/bft/src/primary.rs:1142
- Start::parse_node (cognitive 47) cli/src/commands/start.rs:800
- Start::parse_development (cognitive 33) cli/src/commands/start.rs:558
- Start::check_for_old_storage_format (cognitive 18) cli/src/commands/start.rs:1025
- Start::parse_genesis (cognitive 16) cli/src/commands/start.rs:659
- Sync::sync_storage_with_ledger_at_bootup (cognitive 37) node/bft/src/sync/mod.rs:347
- Sync::try_sync_storage_with_block (cognitive 29) node/bft/src/sync/mod.rs:805
- Sync::try_advancing_block_synchronization_inner (cognitive 27) node/bft/src/sync/mod.rs:509
- Sync::run (cognitive 17) node/bft/src/sync/mod.rs:159
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Primary::propose_batch (cyclomatic 46) node/bft/src/primary.rs:476
- Primary::start_handlers (cyclomatic 33) node/bft/src/primary.rs:1406
- Primary::process_batch_propose_from_peer (cyclomatic 22) node/bft/src/primary.rs:892
- BFT::commit_leader_certificate (cognitive 58) node/bft/src/bft.rs:596
- BFT::try_advance_to_next_round (cognitive 20) node/bft/src/bft.rs:228
- BFT::order_dag_with_dfs (cognitive 17) node/bft/src/bft.rs:861
- Client::initialize_solution_verification (cognitive 28) node/src/client/mod.rs:338
- Client::initialize_execute_verification (cognitive 21) node/src/client/mod.rs:505
- Client::initialize_deploy_verification (cognitive 20) node/src/client/mod.rs:420
- Duplicated block (7 lines × 2) node/bft/src/helpers/storage.rs:976
- Duplicated block (7 lines × 2) node/bft/src/sync/mod.rs:1009
- Duplicated block (7 lines × 2) node/cdn/src/blocks.rs:450
- Duplicated block (6 lines × 2) node/bft/src/gateway.rs:835
- Duplicated block (6 lines × 2) node/router/src/handshake.rs:184
- Duplicated block (6 lines × 2) node/router/src/handshake.rs:198
- Duplicated block (5 lines × 2) node/tcp/src/protocols/handshake.rs:52
- Duplicated block (5 lines × 2) node/bft/src/gateway.rs:952
- Duplicated block (5 lines × 2) node/bft/src/gateway.rs:1951
- Gateway::inbound (cyclomatic 57) node/bft/src/gateway.rs:604
- Gateway::perform_handshake (cyclomatic 18) node/bft/src/gateway.rs:1560
- Start::parse_node (cyclomatic 37) cli/src/commands/start.rs:800
- Start::parse_development (cyclomatic 16) cli/src/commands/start.rs:558
- Repeated repair: node/router/messages/src/helpers/codec.rs node/router/messages/src/helpers/codec.rs:96
- Repeated repair: node/router/messages/src/unconfirmed_transaction.rs node/router/messages/src/unconfirmed_transaction.rs:49
- snarkos_node_cdn::blocks::download_block_bundles (cognitive 33) node/cdn/src/blocks.rs:327
- snarkos_node_cdn::blocks::load_blocks (cognitive 17) node/cdn/src/blocks.rs:183
- BFTPersistentStorage::remove_transmissions (cognitive 29) node/bft/storage-service/src/persistent.rs:227
- BFTPersistentStorage::insert_transmissions (cognitive 23) node/bft/storage-service/src/persistent.rs:134
- Storage::sync_certificate_with_block (cognitive 25) node/bft/src/helpers/storage.rs:915
- Storage::check_batch_header (cognitive 24) node/bft/src/helpers/storage.rs:535
- snarkos_cli::helpers::fd_check::spawn_fd_monitor (cognitive 17) cli/src/helpers/fd_check.rs:135
- snarkos_cli::helpers::logger::parse_log_verbosity (cognitive 17) cli/src/helpers/logger.rs:35
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (11 lines × 2) node/sync/src/block_sync.rs:1329
- Duplicated block (11 lines × 2) node/sync/src/ping.rs:75
- Container process runs as root: metrics-prometheus-1
- WCAG 1.4.3 reproducibly failed in a rendered surface
- WCAG 4.1.2 reproducibly failed in a rendered surface
- Inbound::inbound (cyclomatic 47) node/router/src/inbound.rs:80
- BFT::commit_leader_certificate (cyclomatic 26) node/bft/src/bft.rs:596
- Sync::try_sync_storage_with_block (cyclomatic 23) node/bft/src/sync/mod.rs:805
- Node::perform_auto_checkpoints (cyclomatic 21) node/src/node.rs:385
- BlockSync::prepare_block_requests (cyclomatic 20) node/sync/src/block_sync.rs:974
- Account::parse (cyclomatic 17) cli/src/commands/account.rs:114
- Developer::handle_transaction (cyclomatic 17) cli/src/commands/developer/mod.rs:424
- Storage::sync_certificate_with_block (cyclomatic 17) node/bft/src/helpers/storage.rs:915
- Inbound::inbound (cognitive 64) node/router/src/inbound.rs:80
- Node::perform_auto_checkpoints (cognitive 40) node/src/node.rs:385
- Developer::handle_transaction (cognitive 27) cli/src/commands/developer/mod.rs:424
- BootstrapClient::perform_handshake (cognitive 24) node/src/bootstrap_client/handshake.rs:113
- Router::handshake (cognitive 22) node/router/src/handshake.rs:86
- BFTMemoryService::insert_transmissions (cognitive 19) node/bft/storage-service/src/memory.rs:72
- PeerPoolHandling::insert_candidate_peers (cognitive 17) node/network/src/peering.rs:206
- snarkos::snarkos::main (cognitive 16) snarkos/main.rs:74
- REDACTED
- TooManyFields: Start cli/src/commands/start.rs:140
- REDACTED
- Change coupling clique: deploy.rs, execute.rs, transfer_private.rs cli/src/commands/developer/deploy.rs
- REDACTED
- REDACTED
- Near-duplicate member pair (21 shared lines) node/router/src/handshake.rs:175
- Members sharing a duplicated core (5 members, 50+ identical tokens) node/rest/src/routes.rs:387
- Duplicated block (26 lines × 2) cli/src/commands/account.rs:244
- Duplicated block (18 lines × 2) node/src/client/mod.rs:222
- Duplicated block (16–17 lines × 2) node/consensus/src/lib.rs:650
- Duplicated block (14–15 lines × 2) node/bft/events/src/challenge_request.rs:62
- Duplicated block (14 lines × 2) node/bft/src/sync/mod.rs:203
- Duplicated block (12 lines × 5) node/rest/src/routes.rs:395
- Duplicated block (12 lines × 2) node/bft/src/sync/mod.rs:1017
- Duplicated block (3–10 lines × 3) node/router/src/handshake.rs:225
- Duplicated block (9 lines × 3) node/router/messages/src/helpers/codec.rs:81
- Duplicated block (8 lines × 3) node/bft/ledger-service/src/lib.rs:52
- Duplicated block (6 lines × 3) node/tcp/src/protocols/handshake.rs:52
- End-of-life runtime: Rust 1.96 rust-toolchain.toml:1
Minor — 74 finding(s)
- Interpolated log message defeats structured logging utilities/src/signals.rs:130
- Interpolated log message defeats structured logging utilities/src/signals.rs:145
- Interpolated log message defeats structured logging snarkos/main.rs:65
- Interpolated log message defeats structured logging snarkos/main.rs:99
- Interpolated log message defeats structured logging snarkos/main.rs:107
- Interpolated log message defeats structured logging snarkos/main.rs:170
- Interpolated log message defeats structured logging node/tcp/src/tcp.rs:307
- Interpolated log message defeats structured logging node/tcp/src/tcp.rs:315
- Interpolated log message defeats structured logging node/tcp/src/tcp.rs:320
- Interpolated log message defeats structured logging node/tcp/src/tcp.rs:342
- Interpolated log message defeats structured logging node/tcp/src/tcp.rs:351
- Interpolated log message defeats structured logging node/tcp/src/tcp.rs:401
- Interpolated log message defeats structured logging node/tcp/src/tcp.rs:406
- Interpolated log message defeats structured logging node/tcp/src/tcp.rs:408
- Interpolated log message defeats structured logging node/tcp/src/tcp.rs:467
- Interpolated log message defeats structured logging node/tcp/src/tcp.rs:472
- Interpolated log message defeats structured logging node/tcp/src/tcp.rs:482
- Interpolated log message defeats structured logging node/tcp/src/tcp.rs:489
- Interpolated log message defeats structured logging node/tcp/src/tcp.rs:498
- Interpolated log message defeats structured logging node/tcp/src/tcp.rs:505
- Interpolated log message defeats structured logging node/tcp/src/tcp.rs:522
- Interpolated log message defeats structured logging node/tcp/src/tcp.rs:525
- Interpolated log message defeats structured logging node/tcp/src/tcp.rs:538
- Interpolated log message defeats structured logging node/tcp/src/tcp.rs:568
- Interpolated log message defeats structured logging node/tcp/src/tcp.rs:571
- Orphaned file node/bft/src/helpers/cache.rs:1
- Orphaned file account/src/lib.rs:1
- Orphaned file node/bft/events/src/certificate_response.rs:1
- Orphaned file node/bft/events/src/validators_response.rs:1
- Orphaned file node/bft/events/src/transmission_response.rs:1
- Orphaned file cli/src/helpers/dynamic_format.rs:1
- Orphaned file node/bft/src/helpers/partition.rs:1
- Orphaned file node/bft/events/src/block_request.rs:1
- Orphaned file cli/src/commands/account/sign.rs:1
- Orphaned file cli/src/helpers/bech32m.rs:1
- Orphaned file node/bft/events/src/transmission_request.rs:1
- Orphaned file display/src/pages/logs.rs:1
- Orphaned file node/sync/src/block_sync/metrics.rs:1
- Off-boarding risk: anonymized user #1
- Off-boarding risk: anonymized user #2
- Off-boarding risk: anonymized user #3
- Duplicated predicate node/bft/src/sync/mod.rs:1022
- Duplicated predicate node/src/prover/router.rs:76
- Duplicated predicate node/network/src/peering.rs:128
- Further sole-owners (lower concentration)
- No ADRs found
- REDACTED
- Orphaned files with no living knowledge
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- No rollback/health safety
- No release approval gate
- No changelog
- No app-layer HTTPS enforcement detected
- No security response headers detected
Minor — 10 finding(s)
- Outdated: cfg-if
- Outdated: proptest
- Outdated: self_update
- Outdated: serde_json
- Outdated: sha2
- Outdated: smol_str
- Outdated: thiserror
- Outdated: tokio-util
- Outdated: toml
- Outdated: zeroize
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-774c6530fe7440a49b060542d0306269/history.json --exit-code 0 --source . | 29 | 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-774c6530fe7440a49b060542d0306269/tree.json --exit-code 0 --source . | 7 | 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 . | 56 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 4 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 2 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |