Executive summary
domcyrus/rustnet meets our standard for production. It scores 81 out of 100 and is rated Strong, and 35 of its 36 critical findings are security problems.
Every lens scores high enough to be rated Strong, so no single lens holds the score back. The best first step is recording design decisions, worth about 2 points.
Nine pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Seven secrets can leak from the build pipeline, and six pipeline steps put outside input straight into a shell command, so an attacker can run commands in the build pipeline. Pinning each tool to an exact version, limiting each secret to its own step and passing outside input through environment variables would close these risks. Fixing the weaknesses the scanner points to would fix the five security weaknesses in the code, and the three pipeline steps that install packages without pinning their versions need the packages they install pinned to exact versions. The set of files in separate parts that keep changing together needs that dependency made explicit.
The product code is 80,993 lines, about €150,000 to rebuild.
The weakest lenses score close to each other, so improving any of them moves the score.
New since the last survey: 15 findings
- Cyclomatic Complexity · ProcessExitTracker::reconcile (cyclomatic 21) crates/rustnet-host/src/linux/lifecycle.rs
- Cyclomatic Complexity · DnsAnalyticsTracker::record_packet (cyclomatic 18) crates/rustnet-core/src/network/dns_analytics.rs
- Cognitive Complexity · ProcessExitTracker::reconcile (cognitive 35) crates/rustnet-host/src/linux/lifecycle.rs
- Cognitive Complexity · DnsAnalyticsTracker::record_packet (cognitive 21) crates/rustnet-core/src/network/dns_analytics.rs
- Cognitive Complexity · rustnet_monitor::ui::tabs::host::draw_dns_evidence (cognitive 19) src/ui/tabs/host.rs
- Cognitive Complexity · SocketLifecycleTracker::scan_closed (cognitive 17) crates/rustnet-host/src/lifecycle/inventory.rs
- Cognitive Complexity · ProcessExitTracker::scan_closed (cognitive 16) crates/rustnet-host/src/linux/lifecycle.rs
- God Classes · FileTooLong: types/connection.rs crates/rustnet-core/src/network/types/connection.rs
- God Classes · FileTooLong: src/lib.rs crates/rustnet-host/src/lib.rs
- God Classes · ClassTooLong: Connection crates/rustnet-core/src/network/types/connection.rs
- God Classes · FunctionTooLong: rustnet_monitor::ui::widgets::status_bar::view_hints src/ui/widgets/status_bar.rs
- Churn × Complexity Hotspots · Hotspot: src/app/logging.rs src/app/logging.rs
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Change Coupling · Change coupling: details.rs ↔ help.rs src/ui/tabs/details.rs
Fixed since the last survey: 9 findings
- Cyclomatic Complexity · MacOSProcessLookup::parse_lsof_output (cyclomatic 23) crates/rustnet-host/src/macos/process.rs
- Cyclomatic Complexity · DnsAnalyticsTracker::snapshot (cyclomatic 17) crates/rustnet-core/src/network/dns_analytics.rs
- Cognitive Complexity · MacOSProcessLookup::parse_lsof_output (cognitive 43) crates/rustnet-host/src/macos/process.rs
- Cognitive Complexity · DnsAnalyticsTracker::snapshot (cognitive 28) crates/rustnet-core/src/network/dns_analytics.rs
- Churn × Complexity Hotspots · Hotspot: crates/rustnet-host/src/macos/process.rs crates/rustnet-host/src/macos/process.rs
- Static Analysis (SAST) · High: REDACTED REDACTED
- Static Analysis (SAST) · High: REDACTED REDACTED
- Static Analysis (SAST) · High: REDACTED .github/workflows/rust.yml
- Static Analysis (SAST) · High: REDACTED .github/workflows/security.yml
Rebuild cost: about €150,000 · Estimate
| Cost to rebuild | €51,000 to €260,000, for 858 to 2,720 hours of work, about 1.1 person-years for 1 to 3 engineers |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×1.4 at a score of 81. 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: 80,993 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 rustnet_core.network.dns | 2 rustnet_core.network.interface_stats | 3 rustnet_core.network.protocol | 4 rustnet_core.network.time_window | 5 rustnet_core.network.types.protocol_info | 6 rustnet_monitor.app.runtime | 7 rustnet_sandbox | 8 rustnet_core.network.interface_stats.errors | 9 rustnet_core.network.protocol.tcp | 10 rustnet_core.network.types.network_events | 11 rustnet_core.network.types.connection | 12 rustnet_core.network.types.identity | 13 rustnet_core.network.dns_analytics | 14 rustnet_core.network.parser | 15 rustnet_host | 16 rustnet_core.network.merge | 17 rustnet_host.lifecycle.inventory | 18 rustnet_host.linux.ebpf | 19 rustnet_monitor.app.logging | 20 rustnet_monitor.network.kubernetes | 21 rustnet_core.network.tracker | 22 rustnet_host.linux.ebpf.tracker_libbpf | 23 rustnet_host.linux.process | 24 rustnet_monitor.app.types | 25 rustnet_core.network.process_activity | 26 rustnet_host.linux.enhanced | 27 rustnet_monitor.app.capture | 28 rustnet_monitor.app.pcapng_export | 29 rustnet_host.windows.process | 30 rustnet_monitor.app.sampling | 31 rustnet_monitor.app.state | 32 rustnet_monitor.ui.state | 33 rustnet_monitor.headless.schema | 34 rustnet_monitor.ui.component | 35 rustnet_monitor.ui | 36 rustnet_monitor.ui.tabs.activity | 37 rustnet_monitor.ui.tabs.details | 38 rustnet_monitor.ui.tabs.graph | 39 rustnet_monitor.ui.tabs.host | 40 rustnet_monitor.ui.tabs.overview |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 rustnet_core.network.dns | ||||||||||||||||||||||||||||||||||||||||
| 2 rustnet_core.network.interface_stats | ||||||||||||||||||||||||||||||||||||||||
| 3 rustnet_core.network.protocol | ||||||||||||||||||||||||||||||||||||||||
| 4 rustnet_core.network.time_window | ||||||||||||||||||||||||||||||||||||||||
| 5 rustnet_core.network.types.protocol_info | ||||||||||||||||||||||||||||||||||||||||
| 6 rustnet_monitor.app.runtime | ||||||||||||||||||||||||||||||||||||||||
| 7 rustnet_sandbox | ||||||||||||||||||||||||||||||||||||||||
| 8 rustnet_core.network.interface_stats.errors | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 9 rustnet_core.network.protocol.tcp | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 10 rustnet_core.network.types.network_events | 2 | |||||||||||||||||||||||||||||||||||||||
| 11 rustnet_core.network.types.connection | 2 | 1 | 6 | |||||||||||||||||||||||||||||||||||||
| 12 rustnet_core.network.types.identity | 2 | |||||||||||||||||||||||||||||||||||||||
| 13 rustnet_core.network.dns_analytics | 2 | 4 | 2 | |||||||||||||||||||||||||||||||||||||
| 14 rustnet_core.network.parser | 1 | 1 | 1 | 6 | ||||||||||||||||||||||||||||||||||||
| 15 rustnet_host | 1 | 6 | ||||||||||||||||||||||||||||||||||||||
| 16 rustnet_core.network.merge | 8 | 3 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 17 rustnet_host.lifecycle.inventory | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 18 rustnet_host.linux.ebpf | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 19 rustnet_monitor.app.logging | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 20 rustnet_monitor.network.kubernetes | 4 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 21 rustnet_core.network.tracker | 1 | 2 | 3 | 4 | 4 | 2 | 2 | 1 | ||||||||||||||||||||||||||||||||
| 22 rustnet_host.linux.ebpf.tracker_libbpf | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 23 rustnet_host.linux.process | 1 | 7 | 8 | 1 | ||||||||||||||||||||||||||||||||||||
| 24 rustnet_monitor.app.types | 1 | |||||||||||||||||||||||||||||||||||||||
| 25 rustnet_core.network.process_activity | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 26 rustnet_host.linux.enhanced | 1 | 4 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 27 rustnet_monitor.app.capture | 1 | 1 | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||
| 28 rustnet_monitor.app.pcapng_export | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 29 rustnet_host.windows.process | 1 | 2 | 6 | 1 | ||||||||||||||||||||||||||||||||||||
| 30 rustnet_monitor.app.sampling | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 31 rustnet_monitor.app.state | 1 | 1 | 1 | 5 | 3 | 1 | 1 | 2 | 1 | 1 | 1 | 1 | 1 | 1 | 7 | 2 | 4 | |||||||||||||||||||||||
| 32 rustnet_monitor.ui.state | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 33 rustnet_monitor.headless.schema | 4 | 2 | 1 | 3 | ||||||||||||||||||||||||||||||||||||
| 34 rustnet_monitor.ui.component | 1 | 2 | 4 | |||||||||||||||||||||||||||||||||||||
| 35 rustnet_monitor.ui | 1 | 1 | 1 | 1 | 2 | 2 | ||||||||||||||||||||||||||||||||||
| 36 rustnet_monitor.ui.tabs.activity | 3 | 1 | 5 | 3 | ||||||||||||||||||||||||||||||||||||
| 37 rustnet_monitor.ui.tabs.details | 1 | 3 | 1 | 2 | 3 | 5 | ||||||||||||||||||||||||||||||||||
| 38 rustnet_monitor.ui.tabs.graph | 2 | 1 | 1 | 3 | 3 | |||||||||||||||||||||||||||||||||||
| 39 rustnet_monitor.ui.tabs.host | 1 | 1 | 2 | 1 | 3 | |||||||||||||||||||||||||||||||||||
| 40 rustnet_monitor.ui.tabs.overview | 1 | 1 | 1 | 2 | 1 | 5 | 5 |
8→2 rustnet_core.network.interface_stats.errors uses rustnet_core.network.interface_stats✕
- Connections
- 1 pair of types, where a type in rustnet_core.network.interface_stats.errors uses a type in rustnet_core.network.interface_stats.
- The types involved
rustnet_core.network.interface_stats.errors.errors$module→rustnet_core.network.interface_stats.InterfaceStats
- Direction
- rustnet_core.network.interface_stats.errors uses rustnet_core.network.interface_stats, so a change to rustnet_core.network.interface_stats can break rustnet_core.network.interface_stats.errors, while a change to rustnet_core.network.interface_stats.errors can't break rustnet_core.network.interface_stats.
- Position
- Below the diagonal: rustnet_core.network.interface_stats.errors uses a module listed above it, which is the healthy direction.
8→4 rustnet_core.network.interface_stats.errors uses rustnet_core.network.time_window✕
- Connections
- 2 pairs of types, where a type in rustnet_core.network.interface_stats.errors uses a type in rustnet_core.network.time_window.
- The types involved
rustnet_core.network.interface_stats.errors.InterfaceErrorTracker→rustnet_core.network.time_window.TimeWindowrustnet_core.network.interface_stats.errors.InterfaceHistory→rustnet_core.network.time_window.CounterHistory
- Direction
- rustnet_core.network.interface_stats.errors uses rustnet_core.network.time_window, so a change to rustnet_core.network.time_window can break rustnet_core.network.interface_stats.errors, while a change to rustnet_core.network.interface_stats.errors can't break rustnet_core.network.time_window.
- Position
- Below the diagonal: rustnet_core.network.interface_stats.errors uses a module listed above it, which is the healthy direction.
9→3 rustnet_core.network.protocol.tcp uses rustnet_core.network.protocol✕
- Connections
- 1 pair of types, where a type in rustnet_core.network.protocol.tcp uses a type in rustnet_core.network.protocol.
- The types involved
rustnet_core.network.protocol.tcp.tcp$module→rustnet_core.network.protocol.TransportParams
- Direction
- rustnet_core.network.protocol.tcp uses rustnet_core.network.protocol, so a change to rustnet_core.network.protocol can break rustnet_core.network.protocol.tcp, while a change to rustnet_core.network.protocol.tcp can't break rustnet_core.network.protocol.
- Position
- Below the diagonal: rustnet_core.network.protocol.tcp uses a module listed above it, which is the healthy direction.
9→14 rustnet_core.network.protocol.tcp uses rustnet_core.network.parser part of a loop✕
- Connections
- 2 pairs of types, where a type in rustnet_core.network.protocol.tcp uses a type in rustnet_core.network.parser.
- The types involved
rustnet_core.network.protocol.tcp.tcp$module→rustnet_core.network.parser.ParsedPacketrustnet_core.network.protocol.tcp.tcp$module→rustnet_core.network.parser.ParserConfig
- Direction
- rustnet_core.network.protocol.tcp uses rustnet_core.network.parser, so a change to rustnet_core.network.parser can break rustnet_core.network.protocol.tcp, while a change to rustnet_core.network.protocol.tcp can't break rustnet_core.network.parser.
- 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 rustnet_core.network.types.network_events uses rustnet_core.network.time_window✕
- Connections
- 2 pairs of types, where a type in rustnet_core.network.types.network_events uses a type in rustnet_core.network.time_window.
- The types involved
rustnet_core.network.types.network_events.NetworkEventHistory→rustnet_core.network.time_window.CounterHistoryrustnet_core.network.types.network_events.NetworkEventHistory→rustnet_core.network.time_window.TimeWindow
- Direction
- rustnet_core.network.types.network_events uses rustnet_core.network.time_window, so a change to rustnet_core.network.time_window can break rustnet_core.network.types.network_events, while a change to rustnet_core.network.types.network_events can't break rustnet_core.network.time_window.
- Position
- Below the diagonal: rustnet_core.network.types.network_events uses a module listed above it, which is the healthy direction.
11→5 rustnet_core.network.types.connection uses rustnet_core.network.types.protocol_info✕
- Connections
- 2 pairs of types, where a type in rustnet_core.network.types.connection uses a type in rustnet_core.network.types.protocol_info.
- The types involved
rustnet_core.network.types.connection.Connection→rustnet_core.network.types.protocol_info.DpiInforustnet_core.network.types.connection.Connection→rustnet_core.network.types.protocol_info.QuicInfo
- Direction
- rustnet_core.network.types.connection uses rustnet_core.network.types.protocol_info, so a change to rustnet_core.network.types.protocol_info can break rustnet_core.network.types.connection, while a change to rustnet_core.network.types.connection can't break rustnet_core.network.types.protocol_info.
- Position
- Below the diagonal: rustnet_core.network.types.connection uses a module listed above it, which is the healthy direction.
11→10 rustnet_core.network.types.connection uses rustnet_core.network.types.network_events✕
- Connections
- 1 pair of types, where a type in rustnet_core.network.types.connection uses a type in rustnet_core.network.types.network_events.
- The types involved
rustnet_core.network.types.connection.Connection→rustnet_core.network.types.network_events.ConnectionNetworkEvents
- Direction
- rustnet_core.network.types.connection uses rustnet_core.network.types.network_events, so a change to rustnet_core.network.types.network_events can break rustnet_core.network.types.connection, while a change to rustnet_core.network.types.connection can't break rustnet_core.network.types.network_events.
- Position
- Below the diagonal: rustnet_core.network.types.connection uses a module listed above it, which is the healthy direction.
11→12 rustnet_core.network.types.connection uses rustnet_core.network.types.identity part of a loop✕
- Connections
- 6 pairs of types, where a type in rustnet_core.network.types.connection uses a type in rustnet_core.network.types.identity.
- The types involved
rustnet_core.network.types.connection.Connection→rustnet_core.network.types.identity.AddrKindrustnet_core.network.types.connection.Connection→rustnet_core.network.types.identity.MatchQualityrustnet_core.network.types.connection.Connection→rustnet_core.network.types.identity.ProcessLineagerustnet_core.network.types.connection.Connection→rustnet_core.network.types.identity.Protocolrustnet_core.network.types.connection.Connection→rustnet_core.network.types.identity.ProtocolStaterustnet_core.network.types.connection.Connection→rustnet_core.network.types.identity.TcpState
- Direction
- rustnet_core.network.types.connection uses rustnet_core.network.types.identity, so a change to rustnet_core.network.types.identity can break rustnet_core.network.types.connection, while a change to rustnet_core.network.types.connection can't break rustnet_core.network.types.identity.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→11 rustnet_core.network.types.identity uses rustnet_core.network.types.connection✕
- Connections
- 2 pairs of types, where a type in rustnet_core.network.types.identity uses a type in rustnet_core.network.types.connection.
- The types involved
rustnet_core.network.types.identity.ConnectionKey→rustnet_core.network.types.connection.Connectionrustnet_core.network.types.identity.ConnectionObservation→rustnet_core.network.types.connection.Connection
- Direction
- rustnet_core.network.types.identity uses rustnet_core.network.types.connection, so a change to rustnet_core.network.types.connection can break rustnet_core.network.types.identity, while a change to rustnet_core.network.types.identity can't break rustnet_core.network.types.connection.
- Position
- Below the diagonal: rustnet_core.network.types.identity uses a module listed above it, which is the healthy direction.
13→4 rustnet_core.network.dns_analytics uses rustnet_core.network.time_window✕
- Connections
- 2 pairs of types, where a type in rustnet_core.network.dns_analytics uses a type in rustnet_core.network.time_window.
- The types involved
rustnet_core.network.dns_analytics.DnsAnalyticsSnapshot→rustnet_core.network.time_window.TimeWindowrustnet_core.network.dns_analytics.DnsAnalyticsTracker→rustnet_core.network.time_window.TimeWindow
- Direction
- rustnet_core.network.dns_analytics uses rustnet_core.network.time_window, so a change to rustnet_core.network.time_window can break rustnet_core.network.dns_analytics, while a change to rustnet_core.network.dns_analytics can't break rustnet_core.network.time_window.
- Position
- Below the diagonal: rustnet_core.network.dns_analytics uses a module listed above it, which is the healthy direction.
13→5 rustnet_core.network.dns_analytics uses rustnet_core.network.types.protocol_info✕
- Connections
- 4 pairs of types, where a type in rustnet_core.network.dns_analytics uses a type in rustnet_core.network.types.protocol_info.
- The types involved
rustnet_core.network.dns_analytics.CompletedTransaction→rustnet_core.network.types.protocol_info.DnsQueryTyperustnet_core.network.dns_analytics.DnsAnalyticsTracker→rustnet_core.network.types.protocol_info.DnsInforustnet_core.network.dns_analytics.DnsQuestionStats→rustnet_core.network.types.protocol_info.DnsQueryTyperustnet_core.network.dns_analytics.PendingTransaction→rustnet_core.network.types.protocol_info.DnsQueryType
- Direction
- rustnet_core.network.dns_analytics uses rustnet_core.network.types.protocol_info, so a change to rustnet_core.network.types.protocol_info can break rustnet_core.network.dns_analytics, while a change to rustnet_core.network.dns_analytics can't break rustnet_core.network.types.protocol_info.
- Position
- Below the diagonal: rustnet_core.network.dns_analytics uses a module listed above it, which is the healthy direction.
13→12 rustnet_core.network.dns_analytics uses rustnet_core.network.types.identity✕
- Connections
- 2 pairs of types, where a type in rustnet_core.network.dns_analytics uses a type in rustnet_core.network.types.identity.
- The types involved
rustnet_core.network.dns_analytics.DnsAnalyticsTracker→rustnet_core.network.types.identity.ConnectionKeyrustnet_core.network.dns_analytics.TransactionKey→rustnet_core.network.types.identity.ConnectionKey
- Direction
- rustnet_core.network.dns_analytics uses rustnet_core.network.types.identity, so a change to rustnet_core.network.types.identity can break rustnet_core.network.dns_analytics, while a change to rustnet_core.network.dns_analytics can't break rustnet_core.network.types.identity.
- Position
- Below the diagonal: rustnet_core.network.dns_analytics uses a module listed above it, which is the healthy direction.
14→3 rustnet_core.network.parser uses rustnet_core.network.protocol✕
- Connections
- 1 pair of types, where a type in rustnet_core.network.parser uses a type in rustnet_core.network.protocol.
- The types involved
rustnet_core.network.parser.PacketParser→rustnet_core.network.protocol.TransportParams
- Direction
- rustnet_core.network.parser uses rustnet_core.network.protocol, so a change to rustnet_core.network.protocol can break rustnet_core.network.parser, while a change to rustnet_core.network.parser can't break rustnet_core.network.protocol.
- Position
- Below the diagonal: rustnet_core.network.parser uses a module listed above it, which is the healthy direction.
14→9 rustnet_core.network.parser uses rustnet_core.network.protocol.tcp✕
- Connections
- 1 pair of types, where a type in rustnet_core.network.parser uses a type in rustnet_core.network.protocol.tcp.
- The types involved
rustnet_core.network.parser.ParsedPacket→rustnet_core.network.protocol.tcp.TcpHeaderInfo
- Direction
- rustnet_core.network.parser uses rustnet_core.network.protocol.tcp, so a change to rustnet_core.network.protocol.tcp can break rustnet_core.network.parser, while a change to rustnet_core.network.parser can't break rustnet_core.network.protocol.tcp.
- Position
- Below the diagonal: rustnet_core.network.parser uses a module listed above it, which is the healthy direction.
14→10 rustnet_core.network.parser uses rustnet_core.network.types.network_events✕
- Connections
- 1 pair of types, where a type in rustnet_core.network.parser uses a type in rustnet_core.network.types.network_events.
- The types involved
rustnet_core.network.parser.ParsedIcmpError→rustnet_core.network.types.network_events.IcmpError
- Direction
- rustnet_core.network.parser uses rustnet_core.network.types.network_events, so a change to rustnet_core.network.types.network_events can break rustnet_core.network.parser, while a change to rustnet_core.network.parser can't break rustnet_core.network.types.network_events.
- Position
- Below the diagonal: rustnet_core.network.parser uses a module listed above it, which is the healthy direction.
14→12 rustnet_core.network.parser uses rustnet_core.network.types.identity✕
- Connections
- 6 pairs of types, where a type in rustnet_core.network.parser uses a type in rustnet_core.network.types.identity.
- The types involved
rustnet_core.network.parser.PacketParser→rustnet_core.network.types.identity.AddrKindrustnet_core.network.parser.ParsedIcmpError→rustnet_core.network.types.identity.ConnectionKeyrustnet_core.network.parser.ParsedPacket→rustnet_core.network.types.identity.AddrKindrustnet_core.network.parser.ParsedPacket→rustnet_core.network.types.identity.ConnectionKeyrustnet_core.network.parser.ParsedPacket→rustnet_core.network.types.identity.Protocolrustnet_core.network.parser.ParsedPacket→rustnet_core.network.types.identity.ProtocolState
- Direction
- rustnet_core.network.parser uses rustnet_core.network.types.identity, so a change to rustnet_core.network.types.identity can break rustnet_core.network.parser, while a change to rustnet_core.network.parser can't break rustnet_core.network.types.identity.
- Position
- Below the diagonal: rustnet_core.network.parser uses a module listed above it, which is the healthy direction.
15→11 rustnet_host uses rustnet_core.network.types.connection✕
- Connections
- 1 pair of types, where a type in rustnet_host uses a type in rustnet_core.network.types.connection.
- The types involved
rustnet_host.ProcessLookup→rustnet_core.network.types.connection.Connection
- Direction
- rustnet_host uses rustnet_core.network.types.connection, so a change to rustnet_core.network.types.connection can break rustnet_host, while a change to rustnet_host can't break rustnet_core.network.types.connection.
- Position
- Below the diagonal: rustnet_host uses a module listed above it, which is the healthy direction.
15→12 rustnet_host uses rustnet_core.network.types.identity✕
- Connections
- 6 pairs of types, where a type in rustnet_host uses a type in rustnet_core.network.types.identity.
- The types involved
rustnet_host.HostSocket→rustnet_core.network.types.identity.Protocolrustnet_host.ProcessAttribution→rustnet_core.network.types.identity.MatchQualityrustnet_host.ProcessAttribution→rustnet_core.network.types.identity.ProcessLineagerustnet_host.SocketSnapshot→rustnet_core.network.types.identity.Protocolrustnet_host.rustnet_host$module→rustnet_core.network.types.identity.ConnectionKeyrustnet_host.rustnet_host$module→rustnet_core.network.types.identity.ProcessLineage
- Direction
- rustnet_host uses rustnet_core.network.types.identity, so a change to rustnet_core.network.types.identity can break rustnet_host, while a change to rustnet_host can't break rustnet_core.network.types.identity.
- Position
- Below the diagonal: rustnet_host uses a module listed above it, which is the healthy direction.
16→5 rustnet_core.network.merge uses rustnet_core.network.types.protocol_info✕
- Connections
- 8 pairs of types, where a type in rustnet_core.network.merge uses a type in rustnet_core.network.types.protocol_info.
- The types involved
rustnet_core.network.merge.merge$module→rustnet_core.network.types.protocol_info.DnsInforustnet_core.network.merge.merge$module→rustnet_core.network.types.protocol_info.FtpInforustnet_core.network.merge.merge$module→rustnet_core.network.types.protocol_info.HttpInforustnet_core.network.merge.merge$module→rustnet_core.network.types.protocol_info.MqttInforustnet_core.network.merge.merge$module→rustnet_core.network.types.protocol_info.NetBiosInforustnet_core.network.merge.merge$module→rustnet_core.network.types.protocol_info.QuicInforustnet_core.network.merge.merge$module→rustnet_core.network.types.protocol_info.SshInforustnet_core.network.merge.merge$module→rustnet_core.network.types.protocol_info.TlsInfo
- Direction
- rustnet_core.network.merge uses rustnet_core.network.types.protocol_info, so a change to rustnet_core.network.types.protocol_info can break rustnet_core.network.merge, while a change to rustnet_core.network.merge can't break rustnet_core.network.types.protocol_info.
- Position
- Below the diagonal: rustnet_core.network.merge uses a module listed above it, which is the healthy direction.
16→9 rustnet_core.network.merge uses rustnet_core.network.protocol.tcp✕
- Connections
- 3 pairs of types, where a type in rustnet_core.network.merge uses a type in rustnet_core.network.protocol.tcp.
- The types involved
rustnet_core.network.merge.TcpSegment→rustnet_core.network.protocol.tcp.SynWindowScalerustnet_core.network.merge.merge$module→rustnet_core.network.protocol.tcp.TcpFlagsrustnet_core.network.merge.merge$module→rustnet_core.network.protocol.tcp.TcpHeaderInfo
- Direction
- rustnet_core.network.merge uses rustnet_core.network.protocol.tcp, so a change to rustnet_core.network.protocol.tcp can break rustnet_core.network.merge, while a change to rustnet_core.network.merge can't break rustnet_core.network.protocol.tcp.
- Position
- Below the diagonal: rustnet_core.network.merge uses a module listed above it, which is the healthy direction.
16→11 rustnet_core.network.merge uses rustnet_core.network.types.connection✕
- Connections
- 1 pair of types, where a type in rustnet_core.network.merge uses a type in rustnet_core.network.types.connection.
- The types involved
rustnet_core.network.merge.merge$module→rustnet_core.network.types.connection.Connection
- Direction
- rustnet_core.network.merge uses rustnet_core.network.types.connection, so a change to rustnet_core.network.types.connection can break rustnet_core.network.merge, while a change to rustnet_core.network.merge can't break rustnet_core.network.types.connection.
- Position
- Below the diagonal: rustnet_core.network.merge uses a module listed above it, which is the healthy direction.
16→12 rustnet_core.network.merge uses rustnet_core.network.types.identity✕
- Connections
- 1 pair of types, where a type in rustnet_core.network.merge uses a type in rustnet_core.network.types.identity.
- The types involved
rustnet_core.network.merge.merge$module→rustnet_core.network.types.identity.TcpState
- Direction
- rustnet_core.network.merge uses rustnet_core.network.types.identity, so a change to rustnet_core.network.types.identity can break rustnet_core.network.merge, while a change to rustnet_core.network.merge can't break rustnet_core.network.types.identity.
- Position
- Below the diagonal: rustnet_core.network.merge uses a module listed above it, which is the healthy direction.
16→14 rustnet_core.network.merge uses rustnet_core.network.parser✕
- Connections
- 1 pair of types, where a type in rustnet_core.network.merge uses a type in rustnet_core.network.parser.
- The types involved
rustnet_core.network.merge.merge$module→rustnet_core.network.parser.ParsedPacket
- Direction
- rustnet_core.network.merge uses rustnet_core.network.parser, so a change to rustnet_core.network.parser can break rustnet_core.network.merge, while a change to rustnet_core.network.merge can't break rustnet_core.network.parser.
- Position
- Below the diagonal: rustnet_core.network.merge uses a module listed above it, which is the healthy direction.
17→11 rustnet_host.lifecycle.inventory uses rustnet_core.network.types.connection✕
- Connections
- 1 pair of types, where a type in rustnet_host.lifecycle.inventory uses a type in rustnet_core.network.types.connection.
- The types involved
rustnet_host.lifecycle.inventory.SocketLifecycleTracker→rustnet_core.network.types.connection.ProcessExitStatus
- Direction
- rustnet_host.lifecycle.inventory uses rustnet_core.network.types.connection, so a change to rustnet_core.network.types.connection can break rustnet_host.lifecycle.inventory, while a change to rustnet_host.lifecycle.inventory can't break rustnet_core.network.types.connection.
- Position
- Below the diagonal: rustnet_host.lifecycle.inventory uses a module listed above it, which is the healthy direction.
17→12 rustnet_host.lifecycle.inventory uses rustnet_core.network.types.identity✕
- Connections
- 1 pair of types, where a type in rustnet_host.lifecycle.inventory uses a type in rustnet_core.network.types.identity.
- The types involved
rustnet_host.lifecycle.inventory.inventory$module→rustnet_core.network.types.identity.ConnectionKey
- Direction
- rustnet_host.lifecycle.inventory uses rustnet_core.network.types.identity, so a change to rustnet_core.network.types.identity can break rustnet_host.lifecycle.inventory, while a change to rustnet_host.lifecycle.inventory can't break rustnet_core.network.types.identity.
- Position
- Below the diagonal: rustnet_host.lifecycle.inventory uses a module listed above it, which is the healthy direction.
17→15 rustnet_host.lifecycle.inventory uses rustnet_host✕
- Connections
- 2 pairs of types, where a type in rustnet_host.lifecycle.inventory uses a type in rustnet_host.
- The types involved
rustnet_host.lifecycle.inventory.SocketLifecycleTracker→rustnet_host.SocketSnapshotrustnet_host.lifecycle.inventory.inventory$module→rustnet_host.HostSocket
- Direction
- rustnet_host.lifecycle.inventory uses rustnet_host, so a change to rustnet_host can break rustnet_host.lifecycle.inventory, while a change to rustnet_host.lifecycle.inventory can't break rustnet_host.
- Position
- Below the diagonal: rustnet_host.lifecycle.inventory uses a module listed above it, which is the healthy direction.
18→12 rustnet_host.linux.ebpf uses rustnet_core.network.types.identity✕
- Connections
- 2 pairs of types, where a type in rustnet_host.linux.ebpf uses a type in rustnet_core.network.types.identity.
- The types involved
rustnet_host.linux.ebpf.ProcessInfo→rustnet_core.network.types.identity.ProcessAncestorrustnet_host.linux.ebpf.SocketMatch→rustnet_core.network.types.identity.MatchQuality
- Direction
- rustnet_host.linux.ebpf uses rustnet_core.network.types.identity, so a change to rustnet_core.network.types.identity can break rustnet_host.linux.ebpf, while a change to rustnet_host.linux.ebpf can't break rustnet_core.network.types.identity.
- Position
- Below the diagonal: rustnet_host.linux.ebpf uses a module listed above it, which is the healthy direction.
18→15 rustnet_host.linux.ebpf uses rustnet_host✕
- Connections
- 1 pair of types, where a type in rustnet_host.linux.ebpf uses a type in rustnet_host.
- The types involved
rustnet_host.linux.ebpf.ProcessInfo→rustnet_host.SocketCgroup
- Direction
- rustnet_host.linux.ebpf uses rustnet_host, so a change to rustnet_host can break rustnet_host.linux.ebpf, while a change to rustnet_host.linux.ebpf can't break rustnet_host.
- Position
- Below the diagonal: rustnet_host.linux.ebpf uses a module listed above it, which is the healthy direction.
19→1 rustnet_monitor.app.logging uses rustnet_core.network.dns✕
- Connections
- 1 pair of types, where a type in rustnet_monitor.app.logging uses a type in rustnet_core.network.dns.
- The types involved
rustnet_monitor.app.logging.logging$module→rustnet_core.network.dns.DnsResolver
- Direction
- rustnet_monitor.app.logging uses rustnet_core.network.dns, so a change to rustnet_core.network.dns can break rustnet_monitor.app.logging, while a change to rustnet_monitor.app.logging can't break rustnet_core.network.dns.
- Position
- Below the diagonal: rustnet_monitor.app.logging uses a module listed above it, which is the healthy direction.
19→5 rustnet_monitor.app.logging uses rustnet_core.network.types.protocol_info✕
- Connections
- 1 pair of types, where a type in rustnet_monitor.app.logging uses a type in rustnet_core.network.types.protocol_info.
- The types involved
rustnet_monitor.app.logging.logging$module→rustnet_core.network.types.protocol_info.ApplicationProtocol
- Direction
- rustnet_monitor.app.logging uses rustnet_core.network.types.protocol_info, so a change to rustnet_core.network.types.protocol_info can break rustnet_monitor.app.logging, while a change to rustnet_monitor.app.logging can't break rustnet_core.network.types.protocol_info.
- Position
- Below the diagonal: rustnet_monitor.app.logging uses a module listed above it, which is the healthy direction.
19→11 rustnet_monitor.app.logging uses rustnet_core.network.types.connection✕
- Connections
- 1 pair of types, where a type in rustnet_monitor.app.logging uses a type in rustnet_core.network.types.connection.
- The types involved
rustnet_monitor.app.logging.logging$module→rustnet_core.network.types.connection.Connection
- Direction
- rustnet_monitor.app.logging uses rustnet_core.network.types.connection, so a change to rustnet_core.network.types.connection can break rustnet_monitor.app.logging, while a change to rustnet_monitor.app.logging can't break rustnet_core.network.types.connection.
- Position
- Below the diagonal: rustnet_monitor.app.logging uses a module listed above it, which is the healthy direction.
19→12 rustnet_monitor.app.logging uses rustnet_core.network.types.identity✕
- Connections
- 1 pair of types, where a type in rustnet_monitor.app.logging uses a type in rustnet_core.network.types.identity.
- The types involved
rustnet_monitor.app.logging.logging$module→rustnet_core.network.types.identity.ProcessLineage
- Direction
- rustnet_monitor.app.logging uses rustnet_core.network.types.identity, so a change to rustnet_core.network.types.identity can break rustnet_monitor.app.logging, while a change to rustnet_monitor.app.logging can't break rustnet_core.network.types.identity.
- Position
- Below the diagonal: rustnet_monitor.app.logging uses a module listed above it, which is the healthy direction.
19→15 rustnet_monitor.app.logging uses rustnet_host✕
- Connections
- 1 pair of types, where a type in rustnet_monitor.app.logging uses a type in rustnet_host.
- The types involved
rustnet_monitor.app.logging.logging$module→rustnet_host.LocalPortStatus
- Direction
- rustnet_monitor.app.logging uses rustnet_host, so a change to rustnet_host can break rustnet_monitor.app.logging, while a change to rustnet_monitor.app.logging can't break rustnet_host.
- Position
- Below the diagonal: rustnet_monitor.app.logging uses a module listed above it, which is the healthy direction.
20→11 rustnet_monitor.network.kubernetes uses rustnet_core.network.types.connection✕
- Connections
- 4 pairs of types, where a type in rustnet_monitor.network.kubernetes uses a type in rustnet_core.network.types.connection.
- The types involved
rustnet_monitor.network.kubernetes.KubernetesResolver→rustnet_core.network.types.connection.K8sInforustnet_monitor.network.kubernetes.KubernetesSocketTable→rustnet_core.network.types.connection.Connectionrustnet_monitor.network.kubernetes.PodMetadata→rustnet_core.network.types.connection.K8sInforustnet_monitor.network.kubernetes.kubernetes$module→rustnet_core.network.types.connection.K8sInfo
- Direction
- rustnet_monitor.network.kubernetes uses rustnet_core.network.types.connection, so a change to rustnet_core.network.types.connection can break rustnet_monitor.network.kubernetes, while a change to rustnet_monitor.network.kubernetes can't break rustnet_core.network.types.connection.
- Position
- Below the diagonal: rustnet_monitor.network.kubernetes uses a module listed above it, which is the healthy direction.
20→12 rustnet_monitor.network.kubernetes uses rustnet_core.network.types.identity✕
- Connections
- 1 pair of types, where a type in rustnet_monitor.network.kubernetes uses a type in rustnet_core.network.types.identity.
- The types involved
rustnet_monitor.network.kubernetes.KubernetesSocketTable→rustnet_core.network.types.identity.ConnectionKey
- Direction
- rustnet_monitor.network.kubernetes uses rustnet_core.network.types.identity, so a change to rustnet_core.network.types.identity can break rustnet_monitor.network.kubernetes, while a change to rustnet_monitor.network.kubernetes can't break rustnet_core.network.types.identity.
- Position
- Below the diagonal: rustnet_monitor.network.kubernetes uses a module listed above it, which is the healthy direction.
20→15 rustnet_monitor.network.kubernetes uses rustnet_host✕
- Connections
- 2 pairs of types, where a type in rustnet_monitor.network.kubernetes uses a type in rustnet_host.
- The types involved
rustnet_monitor.network.kubernetes.KubernetesResolver→rustnet_host.SocketCgrouprustnet_monitor.network.kubernetes.kubernetes$module→rustnet_host.SocketCgroup
- Direction
- rustnet_monitor.network.kubernetes uses rustnet_host, so a change to rustnet_host can break rustnet_monitor.network.kubernetes, while a change to rustnet_monitor.network.kubernetes can't break rustnet_host.
- Position
- Below the diagonal: rustnet_monitor.network.kubernetes uses a module listed above it, which is the healthy direction.
21→4 rustnet_core.network.tracker uses rustnet_core.network.time_window✕
- Connections
- 1 pair of types, where a type in rustnet_core.network.tracker uses a type in rustnet_core.network.time_window.
- The types involved
rustnet_core.network.tracker.ConnectionTracker→rustnet_core.network.time_window.TimeWindow
- Direction
- rustnet_core.network.tracker uses rustnet_core.network.time_window, so a change to rustnet_core.network.time_window can break rustnet_core.network.tracker, while a change to rustnet_core.network.tracker can't break rustnet_core.network.time_window.
- Position
- Below the diagonal: rustnet_core.network.tracker uses a module listed above it, which is the healthy direction.
21→5 rustnet_core.network.tracker uses rustnet_core.network.types.protocol_info✕
- Connections
- 2 pairs of types, where a type in rustnet_core.network.tracker uses a type in rustnet_core.network.types.protocol_info.
- The types involved
rustnet_core.network.tracker.tracker$module→rustnet_core.network.types.protocol_info.ApplicationProtocolrustnet_core.network.tracker.tracker$module→rustnet_core.network.types.protocol_info.QuicPacketType
- Direction
- rustnet_core.network.tracker uses rustnet_core.network.types.protocol_info, so a change to rustnet_core.network.types.protocol_info can break rustnet_core.network.tracker, while a change to rustnet_core.network.tracker can't break rustnet_core.network.types.protocol_info.
- Position
- Below the diagonal: rustnet_core.network.tracker uses a module listed above it, which is the healthy direction.
21→10 rustnet_core.network.tracker uses rustnet_core.network.types.network_events✕
- Connections
- 3 pairs of types, where a type in rustnet_core.network.tracker uses a type in rustnet_core.network.types.network_events.
- The types involved
rustnet_core.network.tracker.ConnectionTracker→rustnet_core.network.types.network_events.NetworkEventCountsrustnet_core.network.tracker.ConnectionTracker→rustnet_core.network.types.network_events.NetworkEventHistoryrustnet_core.network.tracker.ConnectionTracker→rustnet_core.network.types.network_events.NetworkEventSnapshot
- Direction
- rustnet_core.network.tracker uses rustnet_core.network.types.network_events, so a change to rustnet_core.network.types.network_events can break rustnet_core.network.tracker, while a change to rustnet_core.network.tracker can't break rustnet_core.network.types.network_events.
- Position
- Below the diagonal: rustnet_core.network.tracker uses a module listed above it, which is the healthy direction.
21→11 rustnet_core.network.tracker uses rustnet_core.network.types.connection✕
- Connections
- 4 pairs of types, where a type in rustnet_core.network.tracker uses a type in rustnet_core.network.types.connection.
- The types involved
rustnet_core.network.tracker.ConnectionTracker→rustnet_core.network.types.connection.Connectionrustnet_core.network.tracker.HistoricKey→rustnet_core.network.types.connection.Connectionrustnet_core.network.tracker.IngestOutcome→rustnet_core.network.types.connection.Connectionrustnet_core.network.tracker.tracker$module→rustnet_core.network.types.connection.Connection
- Direction
- rustnet_core.network.tracker uses rustnet_core.network.types.connection, so a change to rustnet_core.network.types.connection can break rustnet_core.network.tracker, while a change to rustnet_core.network.tracker can't break rustnet_core.network.types.connection.
- Position
- Below the diagonal: rustnet_core.network.tracker uses a module listed above it, which is the healthy direction.
21→12 rustnet_core.network.tracker uses rustnet_core.network.types.identity✕
- Connections
- 4 pairs of types, where a type in rustnet_core.network.tracker uses a type in rustnet_core.network.types.identity.
- The types involved
rustnet_core.network.tracker.ConnectionTracker→rustnet_core.network.types.identity.ConnectionKeyrustnet_core.network.tracker.HistoricKey→rustnet_core.network.types.identity.ConnectionKeyrustnet_core.network.tracker.IngestOutcome→rustnet_core.network.types.identity.ConnectionKeyrustnet_core.network.tracker.PacketTimings→rustnet_core.network.types.identity.ConnectionKey
- Direction
- rustnet_core.network.tracker uses rustnet_core.network.types.identity, so a change to rustnet_core.network.types.identity can break rustnet_core.network.tracker, while a change to rustnet_core.network.tracker can't break rustnet_core.network.types.identity.
- Position
- Below the diagonal: rustnet_core.network.tracker uses a module listed above it, which is the healthy direction.
21→13 rustnet_core.network.tracker uses rustnet_core.network.dns_analytics✕
- Connections
- 2 pairs of types, where a type in rustnet_core.network.tracker uses a type in rustnet_core.network.dns_analytics.
- The types involved
rustnet_core.network.tracker.ConnectionTracker→rustnet_core.network.dns_analytics.DnsAnalyticsSnapshotrustnet_core.network.tracker.ConnectionTracker→rustnet_core.network.dns_analytics.DnsAnalyticsTracker
- Direction
- rustnet_core.network.tracker uses rustnet_core.network.dns_analytics, so a change to rustnet_core.network.dns_analytics can break rustnet_core.network.tracker, while a change to rustnet_core.network.tracker can't break rustnet_core.network.dns_analytics.
- Position
- Below the diagonal: rustnet_core.network.tracker uses a module listed above it, which is the healthy direction.
21→14 rustnet_core.network.tracker uses rustnet_core.network.parser✕
- Connections
- 2 pairs of types, where a type in rustnet_core.network.tracker uses a type in rustnet_core.network.parser.
- The types involved
rustnet_core.network.tracker.ConnectionTracker→rustnet_core.network.parser.ParsedPacketrustnet_core.network.tracker.tracker$module→rustnet_core.network.parser.ParsedPacket
- Direction
- rustnet_core.network.tracker uses rustnet_core.network.parser, so a change to rustnet_core.network.parser can break rustnet_core.network.tracker, while a change to rustnet_core.network.tracker can't break rustnet_core.network.parser.
- Position
- Below the diagonal: rustnet_core.network.tracker uses a module listed above it, which is the healthy direction.
21→16 rustnet_core.network.tracker uses rustnet_core.network.merge✕
- Connections
- 1 pair of types, where a type in rustnet_core.network.tracker uses a type in rustnet_core.network.merge.
- The types involved
rustnet_core.network.tracker.ConnectionTracker→rustnet_core.network.merge.TcpMergeEvents
- Direction
- rustnet_core.network.tracker uses rustnet_core.network.merge, so a change to rustnet_core.network.merge can break rustnet_core.network.tracker, while a change to rustnet_core.network.tracker can't break rustnet_core.network.merge.
- Position
- Below the diagonal: rustnet_core.network.tracker uses a module listed above it, which is the healthy direction.
22→15 rustnet_host.linux.ebpf.tracker_libbpf uses rustnet_host✕
- Connections
- 2 pairs of types, where a type in rustnet_host.linux.ebpf.tracker_libbpf uses a type in rustnet_host.
- The types involved
rustnet_host.linux.ebpf.tracker_libbpf.LibbpfSocketTracker→rustnet_host.AttributionBackendrustnet_host.linux.ebpf.tracker_libbpf.LibbpfSocketTracker→rustnet_host.AttributionCapabilities
- Direction
- rustnet_host.linux.ebpf.tracker_libbpf uses rustnet_host, so a change to rustnet_host can break rustnet_host.linux.ebpf.tracker_libbpf, while a change to rustnet_host.linux.ebpf.tracker_libbpf can't break rustnet_host.
- Position
- Below the diagonal: rustnet_host.linux.ebpf.tracker_libbpf uses a module listed above it, which is the healthy direction.
22→18 rustnet_host.linux.ebpf.tracker_libbpf uses rustnet_host.linux.ebpf✕
- Connections
- 1 pair of types, where a type in rustnet_host.linux.ebpf.tracker_libbpf uses a type in rustnet_host.linux.ebpf.
- The types involved
rustnet_host.linux.ebpf.tracker_libbpf.LibbpfSocketTracker→rustnet_host.linux.ebpf.SocketMatch
- Direction
- rustnet_host.linux.ebpf.tracker_libbpf uses rustnet_host.linux.ebpf, so a change to rustnet_host.linux.ebpf can break rustnet_host.linux.ebpf.tracker_libbpf, while a change to rustnet_host.linux.ebpf.tracker_libbpf can't break rustnet_host.linux.ebpf.
- Position
- Below the diagonal: rustnet_host.linux.ebpf.tracker_libbpf uses a module listed above it, which is the healthy direction.
23→11 rustnet_host.linux.process uses rustnet_core.network.types.connection✕
- Connections
- 1 pair of types, where a type in rustnet_host.linux.process uses a type in rustnet_core.network.types.connection.
- The types involved
rustnet_host.linux.process.LinuxProcessLookup→rustnet_core.network.types.connection.Connection
- Direction
- rustnet_host.linux.process uses rustnet_core.network.types.connection, so a change to rustnet_core.network.types.connection can break rustnet_host.linux.process, while a change to rustnet_host.linux.process can't break rustnet_core.network.types.connection.
- Position
- Below the diagonal: rustnet_host.linux.process uses a module listed above it, which is the healthy direction.
23→12 rustnet_host.linux.process uses rustnet_core.network.types.identity✕
- Connections
- 7 pairs of types, where a type in rustnet_host.linux.process uses a type in rustnet_core.network.types.identity.
- The types involved
rustnet_host.linux.process.LinuxProcessLookup→rustnet_core.network.types.identity.ConnectionKeyrustnet_host.linux.process.LinuxProcessLookup→rustnet_core.network.types.identity.MatchQualityrustnet_host.linux.process.LinuxProcessLookup→rustnet_core.network.types.identity.ProcessLineagerustnet_host.linux.process.LinuxProcessLookup→rustnet_core.network.types.identity.Protocolrustnet_host.linux.process.process$module→rustnet_core.network.types.identity.ConnectionKeyrustnet_host.linux.process.process$module→rustnet_core.network.types.identity.MatchQualityrustnet_host.linux.process.process$module→rustnet_core.network.types.identity.ProcessLineage
- Direction
- rustnet_host.linux.process uses rustnet_core.network.types.identity, so a change to rustnet_core.network.types.identity can break rustnet_host.linux.process, while a change to rustnet_host.linux.process can't break rustnet_core.network.types.identity.
- Position
- Below the diagonal: rustnet_host.linux.process uses a module listed above it, which is the healthy direction.
23→15 rustnet_host.linux.process uses rustnet_host✕
- Connections
- 8 pairs of types, where a type in rustnet_host.linux.process uses a type in rustnet_host.
- The types involved
rustnet_host.linux.process.LinuxProcessLookup→rustnet_host.HostSocketrustnet_host.linux.process.LinuxProcessLookup→rustnet_host.ProcessAttributionrustnet_host.linux.process.LinuxProcessLookup→rustnet_host.ProcessLookuprustnet_host.linux.process.LinuxProcessLookup→rustnet_host.SocketSnapshotrustnet_host.linux.process.RetainedSocketOwner→rustnet_host.HostSocketrustnet_host.linux.process.StartupSocketOwners→rustnet_host.SocketOwnerrustnet_host.linux.process.process$module→rustnet_host.HostTcpStaterustnet_host.linux.process.process$module→rustnet_host.SocketSnapshot
- Direction
- rustnet_host.linux.process uses rustnet_host, so a change to rustnet_host can break rustnet_host.linux.process, while a change to rustnet_host.linux.process can't break rustnet_host.
- Position
- Below the diagonal: rustnet_host.linux.process uses a module listed above it, which is the healthy direction.
23→18 rustnet_host.linux.process uses rustnet_host.linux.ebpf✕
- Connections
- 1 pair of types, where a type in rustnet_host.linux.process uses a type in rustnet_host.linux.ebpf.
- The types involved
rustnet_host.linux.process.process$module→rustnet_host.linux.ebpf.ProcessInfo
- Direction
- rustnet_host.linux.process uses rustnet_host.linux.ebpf, so a change to rustnet_host.linux.ebpf can break rustnet_host.linux.process, while a change to rustnet_host.linux.process can't break rustnet_host.linux.ebpf.
- Position
- Below the diagonal: rustnet_host.linux.process uses a module listed above it, which is the healthy direction.
24→20 rustnet_monitor.app.types uses rustnet_monitor.network.kubernetes✕
- Connections
- 1 pair of types, where a type in rustnet_monitor.app.types uses a type in rustnet_monitor.network.kubernetes.
- The types involved
rustnet_monitor.app.types.Config→rustnet_monitor.network.kubernetes.KubernetesMode
- Direction
- rustnet_monitor.app.types uses rustnet_monitor.network.kubernetes, so a change to rustnet_monitor.network.kubernetes can break rustnet_monitor.app.types, while a change to rustnet_monitor.app.types can't break rustnet_monitor.network.kubernetes.
- Position
- Below the diagonal: rustnet_monitor.app.types uses a module listed above it, which is the healthy direction.
25→11 rustnet_core.network.process_activity uses rustnet_core.network.types.connection✕
- Connections
- 3 pairs of types, where a type in rustnet_core.network.process_activity uses a type in rustnet_core.network.types.connection.
- The types involved
rustnet_core.network.process_activity.FlowActivity→rustnet_core.network.types.connection.Connectionrustnet_core.network.process_activity.ProcessIdentity→rustnet_core.network.types.connection.Connectionrustnet_core.network.process_activity.process_activity$module→rustnet_core.network.types.connection.Connection
- Direction
- rustnet_core.network.process_activity uses rustnet_core.network.types.connection, so a change to rustnet_core.network.types.connection can break rustnet_core.network.process_activity, while a change to rustnet_core.network.process_activity can't break rustnet_core.network.types.connection.
- Position
- Below the diagonal: rustnet_core.network.process_activity uses a module listed above it, which is the healthy direction.
25→21 rustnet_core.network.process_activity uses rustnet_core.network.tracker✕
- Connections
- 1 pair of types, where a type in rustnet_core.network.process_activity uses a type in rustnet_core.network.tracker.
- The types involved
rustnet_core.network.process_activity.process_activity$module→rustnet_core.network.tracker.HistoricKey
- Direction
- rustnet_core.network.process_activity uses rustnet_core.network.tracker, so a change to rustnet_core.network.tracker can break rustnet_core.network.process_activity, while a change to rustnet_core.network.process_activity can't break rustnet_core.network.tracker.
- Position
- Below the diagonal: rustnet_core.network.process_activity uses a module listed above it, which is the healthy direction.
26→11 rustnet_host.linux.enhanced uses rustnet_core.network.types.connection✕
- Connections
- 1 pair of types, where a type in rustnet_host.linux.enhanced uses a type in rustnet_core.network.types.connection.
- The types involved
rustnet_host.linux.enhanced.EnhancedLinuxProcessLookup→rustnet_core.network.types.connection.Connection
- Direction
- rustnet_host.linux.enhanced uses rustnet_core.network.types.connection, so a change to rustnet_core.network.types.connection can break rustnet_host.linux.enhanced, while a change to rustnet_host.linux.enhanced can't break rustnet_core.network.types.connection.
- Position
- Below the diagonal: rustnet_host.linux.enhanced uses a module listed above it, which is the healthy direction.
26→15 rustnet_host.linux.enhanced uses rustnet_host✕
- Connections
- 4 pairs of types, where a type in rustnet_host.linux.enhanced uses a type in rustnet_host.
- The types involved
rustnet_host.linux.enhanced.EnhancedLinuxProcessLookup→rustnet_host.DegradationReasonrustnet_host.linux.enhanced.EnhancedLinuxProcessLookup→rustnet_host.ProcessAttributionrustnet_host.linux.enhanced.EnhancedLinuxProcessLookup→rustnet_host.ProcessLookuprustnet_host.linux.enhanced.EnhancedLinuxProcessLookup→rustnet_host.SocketSnapshot
- Direction
- rustnet_host.linux.enhanced uses rustnet_host, so a change to rustnet_host can break rustnet_host.linux.enhanced, while a change to rustnet_host.linux.enhanced can't break rustnet_host.
- Position
- Below the diagonal: rustnet_host.linux.enhanced uses a module listed above it, which is the healthy direction.
26→18 rustnet_host.linux.enhanced uses rustnet_host.linux.ebpf✕
- Connections
- 1 pair of types, where a type in rustnet_host.linux.enhanced uses a type in rustnet_host.linux.ebpf.
- The types involved
rustnet_host.linux.enhanced.EnhancedLinuxProcessLookup→rustnet_host.linux.ebpf.SocketMatch
- Direction
- rustnet_host.linux.enhanced uses rustnet_host.linux.ebpf, so a change to rustnet_host.linux.ebpf can break rustnet_host.linux.enhanced, while a change to rustnet_host.linux.enhanced can't break rustnet_host.linux.ebpf.
- Position
- Below the diagonal: rustnet_host.linux.enhanced uses a module listed above it, which is the healthy direction.
26→23 rustnet_host.linux.enhanced uses rustnet_host.linux.process✕
- Connections
- 1 pair of types, where a type in rustnet_host.linux.enhanced uses a type in rustnet_host.linux.process.
- The types involved
rustnet_host.linux.enhanced.EnhancedLinuxProcessLookup→rustnet_host.linux.process.LinuxProcessLookup
- Direction
- rustnet_host.linux.enhanced uses rustnet_host.linux.process, so a change to rustnet_host.linux.process can break rustnet_host.linux.enhanced, while a change to rustnet_host.linux.enhanced can't break rustnet_host.linux.process.
- Position
- Below the diagonal: rustnet_host.linux.enhanced uses a module listed above it, which is the healthy direction.
27→1 rustnet_monitor.app.capture uses rustnet_core.network.dns✕
- Connections
- 1 pair of types, where a type in rustnet_monitor.app.capture uses a type in rustnet_core.network.dns.
- The types involved
rustnet_monitor.app.capture.capture$module→rustnet_core.network.dns.DnsResolver
- Direction
- rustnet_monitor.app.capture uses rustnet_core.network.dns, so a change to rustnet_core.network.dns can break rustnet_monitor.app.capture, while a change to rustnet_monitor.app.capture can't break rustnet_core.network.dns.
- Position
- Below the diagonal: rustnet_monitor.app.capture uses a module listed above it, which is the healthy direction.
27→14 rustnet_monitor.app.capture uses rustnet_core.network.parser✕
- Connections
- 1 pair of types, where a type in rustnet_monitor.app.capture uses a type in rustnet_core.network.parser.
- The types involved
rustnet_monitor.app.capture.capture$module→rustnet_core.network.parser.ParsedPacket
- Direction
- rustnet_monitor.app.capture uses rustnet_core.network.parser, so a change to rustnet_core.network.parser can break rustnet_monitor.app.capture, while a change to rustnet_monitor.app.capture can't break rustnet_core.network.parser.
- Position
- Below the diagonal: rustnet_monitor.app.capture uses a module listed above it, which is the healthy direction.
27→19 rustnet_monitor.app.capture uses rustnet_monitor.app.logging✕
- Connections
- 1 pair of types, where a type in rustnet_monitor.app.capture uses a type in rustnet_monitor.app.logging.
- The types involved
rustnet_monitor.app.capture.capture$module→rustnet_monitor.app.logging.JsonLineWriter
- Direction
- rustnet_monitor.app.capture uses rustnet_monitor.app.logging, so a change to rustnet_monitor.app.logging can break rustnet_monitor.app.capture, while a change to rustnet_monitor.app.capture can't break rustnet_monitor.app.logging.
- Position
- Below the diagonal: rustnet_monitor.app.capture uses a module listed above it, which is the healthy direction.
27→21 rustnet_monitor.app.capture uses rustnet_core.network.tracker✕
- Connections
- 2 pairs of types, where a type in rustnet_monitor.app.capture uses a type in rustnet_core.network.tracker.
- The types involved
rustnet_monitor.app.capture.capture$module→rustnet_core.network.tracker.ConnectionTrackerrustnet_monitor.app.capture.capture$module→rustnet_core.network.tracker.IngestOutcome
- Direction
- rustnet_monitor.app.capture uses rustnet_core.network.tracker, so a change to rustnet_core.network.tracker can break rustnet_monitor.app.capture, while a change to rustnet_monitor.app.capture can't break rustnet_core.network.tracker.
- Position
- Below the diagonal: rustnet_monitor.app.capture uses a module listed above it, which is the healthy direction.
27→24 rustnet_monitor.app.capture uses rustnet_monitor.app.types✕
- Connections
- 1 pair of types, where a type in rustnet_monitor.app.capture uses a type in rustnet_monitor.app.types.
- The types involved
rustnet_monitor.app.capture.capture$module→rustnet_monitor.app.types.AppStats
- Direction
- rustnet_monitor.app.capture uses rustnet_monitor.app.types, so a change to rustnet_monitor.app.types can break rustnet_monitor.app.capture, while a change to rustnet_monitor.app.capture can't break rustnet_monitor.app.types.
- Position
- Below the diagonal: rustnet_monitor.app.capture uses a module listed above it, which is the healthy direction.
28→11 rustnet_monitor.app.pcapng_export uses rustnet_core.network.types.connection✕
- Connections
- 1 pair of types, where a type in rustnet_monitor.app.pcapng_export uses a type in rustnet_core.network.types.connection.
- The types involved
rustnet_monitor.app.pcapng_export.pcapng_export$module→rustnet_core.network.types.connection.Connection
- Direction
- rustnet_monitor.app.pcapng_export uses rustnet_core.network.types.connection, so a change to rustnet_core.network.types.connection can break rustnet_monitor.app.pcapng_export, while a change to rustnet_monitor.app.pcapng_export can't break rustnet_core.network.types.connection.
- Position
- Below the diagonal: rustnet_monitor.app.pcapng_export uses a module listed above it, which is the healthy direction.
28→12 rustnet_monitor.app.pcapng_export uses rustnet_core.network.types.identity✕
- Connections
- 1 pair of types, where a type in rustnet_monitor.app.pcapng_export uses a type in rustnet_core.network.types.identity.
- The types involved
rustnet_monitor.app.pcapng_export.PcapngRecord→rustnet_core.network.types.identity.ConnectionKey
- Direction
- rustnet_monitor.app.pcapng_export uses rustnet_core.network.types.identity, so a change to rustnet_core.network.types.identity can break rustnet_monitor.app.pcapng_export, while a change to rustnet_monitor.app.pcapng_export can't break rustnet_core.network.types.identity.
- Position
- Below the diagonal: rustnet_monitor.app.pcapng_export uses a module listed above it, which is the healthy direction.
28→21 rustnet_monitor.app.pcapng_export uses rustnet_core.network.tracker✕
- Connections
- 1 pair of types, where a type in rustnet_monitor.app.pcapng_export uses a type in rustnet_core.network.tracker.
- The types involved
rustnet_monitor.app.pcapng_export.pcapng_export$module→rustnet_core.network.tracker.ConnectionTracker
- Direction
- rustnet_monitor.app.pcapng_export uses rustnet_core.network.tracker, so a change to rustnet_core.network.tracker can break rustnet_monitor.app.pcapng_export, while a change to rustnet_monitor.app.pcapng_export can't break rustnet_core.network.tracker.
- Position
- Below the diagonal: rustnet_monitor.app.pcapng_export uses a module listed above it, which is the healthy direction.
28→24 rustnet_monitor.app.pcapng_export uses rustnet_monitor.app.types✕
- Connections
- 1 pair of types, where a type in rustnet_monitor.app.pcapng_export uses a type in rustnet_monitor.app.types.
- The types involved
rustnet_monitor.app.pcapng_export.pcapng_export$module→rustnet_monitor.app.types.AppStats
- Direction
- rustnet_monitor.app.pcapng_export uses rustnet_monitor.app.types, so a change to rustnet_monitor.app.types can break rustnet_monitor.app.pcapng_export, while a change to rustnet_monitor.app.pcapng_export can't break rustnet_monitor.app.types.
- Position
- Below the diagonal: rustnet_monitor.app.pcapng_export uses a module listed above it, which is the healthy direction.
29→11 rustnet_host.windows.process uses rustnet_core.network.types.connection✕
- Connections
- 1 pair of types, where a type in rustnet_host.windows.process uses a type in rustnet_core.network.types.connection.
- The types involved
rustnet_host.windows.process.WindowsProcessLookup→rustnet_core.network.types.connection.Connection
- Direction
- rustnet_host.windows.process uses rustnet_core.network.types.connection, so a change to rustnet_core.network.types.connection can break rustnet_host.windows.process, while a change to rustnet_host.windows.process can't break rustnet_core.network.types.connection.
- Position
- Below the diagonal: rustnet_host.windows.process uses a module listed above it, which is the healthy direction.
29→12 rustnet_host.windows.process uses rustnet_core.network.types.identity✕
- Connections
- 2 pairs of types, where a type in rustnet_host.windows.process uses a type in rustnet_core.network.types.identity.
- The types involved
rustnet_host.windows.process.WindowsProcessLookup→rustnet_core.network.types.identity.ProcessLineagerustnet_host.windows.process.process$module→rustnet_core.network.types.identity.ConnectionKey
- Direction
- rustnet_host.windows.process uses rustnet_core.network.types.identity, so a change to rustnet_core.network.types.identity can break rustnet_host.windows.process, while a change to rustnet_host.windows.process can't break rustnet_core.network.types.identity.
- Position
- Below the diagonal: rustnet_host.windows.process uses a module listed above it, which is the healthy direction.
29→15 rustnet_host.windows.process uses rustnet_host✕
- Connections
- 6 pairs of types, where a type in rustnet_host.windows.process uses a type in rustnet_host.
- The types involved
rustnet_host.windows.process.WindowsProcessLookup→rustnet_host.DegradationReasonrustnet_host.windows.process.WindowsProcessLookup→rustnet_host.ProcessAttributionrustnet_host.windows.process.WindowsProcessLookup→rustnet_host.ProcessLookuprustnet_host.windows.process.WindowsProcessLookup→rustnet_host.SocketSnapshotrustnet_host.windows.process.process$module→rustnet_host.HostTcpStaterustnet_host.windows.process.process$module→rustnet_host.SocketOwner
- Direction
- rustnet_host.windows.process uses rustnet_host, so a change to rustnet_host can break rustnet_host.windows.process, while a change to rustnet_host.windows.process can't break rustnet_host.
- Position
- Below the diagonal: rustnet_host.windows.process uses a module listed above it, which is the healthy direction.
29→26 rustnet_host.windows.process uses rustnet_host.linux.enhanced✕
- Connections
- 1 pair of types, where a type in rustnet_host.windows.process uses a type in rustnet_host.linux.enhanced.
- The types involved
rustnet_host.windows.process.WindowsProcessLookup→rustnet_host.linux.enhanced.ProcessCache
- Direction
- rustnet_host.windows.process uses rustnet_host.linux.enhanced, so a change to rustnet_host.linux.enhanced can break rustnet_host.windows.process, while a change to rustnet_host.windows.process can't break rustnet_host.linux.enhanced.
- Position
- Below the diagonal: rustnet_host.windows.process uses a module listed above it, which is the healthy direction.
30→6 rustnet_monitor.app.sampling uses rustnet_monitor.app.runtime✕
- Connections
- 1 pair of types, where a type in rustnet_monitor.app.sampling uses a type in rustnet_monitor.app.runtime.
- The types involved
rustnet_monitor.app.sampling.sampling$module→rustnet_monitor.app.runtime.RuntimeSupervisor
- Direction
- rustnet_monitor.app.sampling uses rustnet_monitor.app.runtime, so a change to rustnet_monitor.app.runtime can break rustnet_monitor.app.sampling, while a change to rustnet_monitor.app.sampling can't break rustnet_monitor.app.runtime.
- Position
- Below the diagonal: rustnet_monitor.app.sampling uses a module listed above it, which is the healthy direction.
30→11 rustnet_monitor.app.sampling uses rustnet_core.network.types.connection✕
- Connections
- 1 pair of types, where a type in rustnet_monitor.app.sampling uses a type in rustnet_core.network.types.connection.
- The types involved
rustnet_monitor.app.sampling.sampling$module→rustnet_core.network.types.connection.Connection
- Direction
- rustnet_monitor.app.sampling uses rustnet_core.network.types.connection, so a change to rustnet_core.network.types.connection can break rustnet_monitor.app.sampling, while a change to rustnet_monitor.app.sampling can't break rustnet_core.network.types.connection.
- Position
- Below the diagonal: rustnet_monitor.app.sampling uses a module listed above it, which is the healthy direction.
30→21 rustnet_monitor.app.sampling uses rustnet_core.network.tracker✕
- Connections
- 1 pair of types, where a type in rustnet_monitor.app.sampling uses a type in rustnet_core.network.tracker.
- The types involved
rustnet_monitor.app.sampling.sampling$module→rustnet_core.network.tracker.ConnectionTracker
- Direction
- rustnet_monitor.app.sampling uses rustnet_core.network.tracker, so a change to rustnet_core.network.tracker can break rustnet_monitor.app.sampling, while a change to rustnet_monitor.app.sampling can't break rustnet_core.network.tracker.
- Position
- Below the diagonal: rustnet_monitor.app.sampling uses a module listed above it, which is the healthy direction.
30→25 rustnet_monitor.app.sampling uses rustnet_core.network.process_activity✕
- Connections
- 1 pair of types, where a type in rustnet_monitor.app.sampling uses a type in rustnet_core.network.process_activity.
- The types involved
rustnet_monitor.app.sampling.sampling$module→rustnet_core.network.process_activity.ProcessActivityTracker
- Direction
- rustnet_monitor.app.sampling uses rustnet_core.network.process_activity, so a change to rustnet_core.network.process_activity can break rustnet_monitor.app.sampling, while a change to rustnet_monitor.app.sampling can't break rustnet_core.network.process_activity.
- Position
- Below the diagonal: rustnet_monitor.app.sampling uses a module listed above it, which is the healthy direction.
31→1 rustnet_monitor.app.state uses rustnet_core.network.dns✕
- Connections
- 1 pair of types, where a type in rustnet_monitor.app.state uses a type in rustnet_core.network.dns.
- The types involved
rustnet_monitor.app.state.App→rustnet_core.network.dns.DnsResolver
- Direction
- rustnet_monitor.app.state uses rustnet_core.network.dns, so a change to rustnet_core.network.dns can break rustnet_monitor.app.state, while a change to rustnet_monitor.app.state can't break rustnet_core.network.dns.
- Position
- Below the diagonal: rustnet_monitor.app.state uses a module listed above it, which is the healthy direction.
31→2 rustnet_monitor.app.state uses rustnet_core.network.interface_stats✕
- Connections
- 1 pair of types, where a type in rustnet_monitor.app.state uses a type in rustnet_core.network.interface_stats.
- The types involved
rustnet_monitor.app.state.App→rustnet_core.network.interface_stats.InterfaceStats
- Direction
- rustnet_monitor.app.state uses rustnet_core.network.interface_stats, so a change to rustnet_core.network.interface_stats can break rustnet_monitor.app.state, while a change to rustnet_monitor.app.state can't break rustnet_core.network.interface_stats.
- Position
- Below the diagonal: rustnet_monitor.app.state uses a module listed above it, which is the healthy direction.
31→4 rustnet_monitor.app.state uses rustnet_core.network.time_window✕
- Connections
- 1 pair of types, where a type in rustnet_monitor.app.state uses a type in rustnet_core.network.time_window.
- The types involved
rustnet_monitor.app.state.App→rustnet_core.network.time_window.TimeWindow
- Direction
- rustnet_monitor.app.state uses rustnet_core.network.time_window, so a change to rustnet_core.network.time_window can break rustnet_monitor.app.state, while a change to rustnet_monitor.app.state can't break rustnet_core.network.time_window.
- Position
- Below the diagonal: rustnet_monitor.app.state uses a module listed above it, which is the healthy direction.
31→6 rustnet_monitor.app.state uses rustnet_monitor.app.runtime✕
- Connections
- 5 pairs of types, where a type in rustnet_monitor.app.state uses a type in rustnet_monitor.app.runtime.
- The types involved
rustnet_monitor.app.state.App→rustnet_monitor.app.runtime.InitStatusrustnet_monitor.app.state.App→rustnet_monitor.app.runtime.RuntimeSupervisorrustnet_monitor.app.state.App→rustnet_monitor.app.runtime.ShutdownSignalrustnet_monitor.app.state.App→rustnet_monitor.app.runtime.StopReportrustnet_monitor.app.state.App→rustnet_monitor.app.runtime.WorkerStartupPermit
- Direction
- rustnet_monitor.app.state uses rustnet_monitor.app.runtime, so a change to rustnet_monitor.app.runtime can break rustnet_monitor.app.state, while a change to rustnet_monitor.app.state can't break rustnet_monitor.app.runtime.
- Position
- Below the diagonal: rustnet_monitor.app.state uses a module listed above it, which is the healthy direction.
31→7 rustnet_monitor.app.state uses rustnet_sandbox✕
- Connections
- 3 pairs of types, where a type in rustnet_monitor.app.state uses a type in rustnet_sandbox.
- The types involved
rustnet_monitor.app.state.App→rustnet_sandbox.SandboxConfigrustnet_monitor.app.state.App→rustnet_sandbox.SandboxModerustnet_monitor.app.state.App→rustnet_sandbox.SandboxReport
- Direction
- rustnet_monitor.app.state uses rustnet_sandbox, so a change to rustnet_sandbox can break rustnet_monitor.app.state, while a change to rustnet_monitor.app.state can't break rustnet_sandbox.
- Position
- Below the diagonal: rustnet_monitor.app.state uses a module listed above it, which is the healthy direction.
31→8 rustnet_monitor.app.state uses rustnet_core.network.interface_stats.errors✕
- Connections
- 1 pair of types, where a type in rustnet_monitor.app.state uses a type in rustnet_core.network.interface_stats.errors.
- The types involved
rustnet_monitor.app.state.App→rustnet_core.network.interface_stats.errors.InterfaceErrorTracker
- Direction
- rustnet_monitor.app.state uses rustnet_core.network.interface_stats.errors, so a change to rustnet_core.network.interface_stats.errors can break rustnet_monitor.app.state, while a change to rustnet_monitor.app.state can't break rustnet_core.network.interface_stats.errors.
- Position
- Below the diagonal: rustnet_monitor.app.state uses a module listed above it, which is the healthy direction.
31→10 rustnet_monitor.app.state uses rustnet_core.network.types.network_events✕
- Connections
- 1 pair of types, where a type in rustnet_monitor.app.state uses a type in rustnet_core.network.types.network_events.
- The types involved
rustnet_monitor.app.state.App→rustnet_core.network.types.network_events.NetworkEventSnapshot
- Direction
- rustnet_monitor.app.state uses rustnet_core.network.types.network_events, so a change to rustnet_core.network.types.network_events can break rustnet_monitor.app.state, while a change to rustnet_monitor.app.state can't break rustnet_core.network.types.network_events.
- Position
- Below the diagonal: rustnet_monitor.app.state uses a module listed above it, which is the healthy direction.
31→11 rustnet_monitor.app.state uses rustnet_core.network.types.connection✕
- Connections
- 2 pairs of types, where a type in rustnet_monitor.app.state uses a type in rustnet_core.network.types.connection.
- The types involved
rustnet_monitor.app.state.App→rustnet_core.network.types.connection.Connectionrustnet_monitor.app.state.state$module→rustnet_core.network.types.connection.Connection
- Direction
- rustnet_monitor.app.state uses rustnet_core.network.types.connection, so a change to rustnet_core.network.types.connection can break rustnet_monitor.app.state, while a change to rustnet_monitor.app.state can't break rustnet_core.network.types.connection.
- Position
- Below the diagonal: rustnet_monitor.app.state uses a module listed above it, which is the healthy direction.
31→12 rustnet_monitor.app.state uses rustnet_core.network.types.identity✕
- Connections
- 1 pair of types, where a type in rustnet_monitor.app.state uses a type in rustnet_core.network.types.identity.
- The types involved
rustnet_monitor.app.state.App→rustnet_core.network.types.identity.Protocol
- Direction
- rustnet_monitor.app.state uses rustnet_core.network.types.identity, so a change to rustnet_core.network.types.identity can break rustnet_monitor.app.state, while a change to rustnet_monitor.app.state can't break rustnet_core.network.types.identity.
- Position
- Below the diagonal: rustnet_monitor.app.state uses a module listed above it, which is the healthy direction.
31→13 rustnet_monitor.app.state uses rustnet_core.network.dns_analytics✕
- Connections
- 1 pair of types, where a type in rustnet_monitor.app.state uses a type in rustnet_core.network.dns_analytics.
- The types involved
rustnet_monitor.app.state.App→rustnet_core.network.dns_analytics.DnsAnalyticsSnapshot
- Direction
- rustnet_monitor.app.state uses rustnet_core.network.dns_analytics, so a change to rustnet_core.network.dns_analytics can break rustnet_monitor.app.state, while a change to rustnet_monitor.app.state can't break rustnet_core.network.dns_analytics.
- Position
- Below the diagonal: rustnet_monitor.app.state uses a module listed above it, which is the healthy direction.
31→15 rustnet_monitor.app.state uses rustnet_host✕
- Connections
- 1 pair of types, where a type in rustnet_monitor.app.state uses a type in rustnet_host.
- The types involved
rustnet_monitor.app.state.App→rustnet_host.SocketSnapshot
- Direction
- rustnet_monitor.app.state uses rustnet_host, so a change to rustnet_host can break rustnet_monitor.app.state, while a change to rustnet_monitor.app.state can't break rustnet_host.
- Position
- Below the diagonal: rustnet_monitor.app.state uses a module listed above it, which is the healthy direction.
31→19 rustnet_monitor.app.state uses rustnet_monitor.app.logging✕
- Connections
- 1 pair of types, where a type in rustnet_monitor.app.state uses a type in rustnet_monitor.app.logging.
- The types involved
rustnet_monitor.app.state.App→rustnet_monitor.app.logging.JsonLineWriter
- Direction
- rustnet_monitor.app.state uses rustnet_monitor.app.logging, so a change to rustnet_monitor.app.logging can break rustnet_monitor.app.state, while a change to rustnet_monitor.app.state can't break rustnet_monitor.app.logging.
- Position
- Below the diagonal: rustnet_monitor.app.state uses a module listed above it, which is the healthy direction.
31→20 rustnet_monitor.app.state uses rustnet_monitor.network.kubernetes✕
- Connections
- 1 pair of types, where a type in rustnet_monitor.app.state uses a type in rustnet_monitor.network.kubernetes.
- The types involved
rustnet_monitor.app.state.App→rustnet_monitor.network.kubernetes.KubernetesMode
- Direction
- rustnet_monitor.app.state uses rustnet_monitor.network.kubernetes, so a change to rustnet_monitor.network.kubernetes can break rustnet_monitor.app.state, while a change to rustnet_monitor.app.state can't break rustnet_monitor.network.kubernetes.
- Position
- Below the diagonal: rustnet_monitor.app.state uses a module listed above it, which is the healthy direction.
31→21 rustnet_monitor.app.state uses rustnet_core.network.tracker✕
- Connections
- 1 pair of types, where a type in rustnet_monitor.app.state uses a type in rustnet_core.network.tracker.
- The types involved
rustnet_monitor.app.state.App→rustnet_core.network.tracker.ConnectionTracker
- Direction
- rustnet_monitor.app.state uses rustnet_core.network.tracker, so a change to rustnet_core.network.tracker can break rustnet_monitor.app.state, while a change to rustnet_monitor.app.state can't break rustnet_core.network.tracker.
- Position
- Below the diagonal: rustnet_monitor.app.state uses a module listed above it, which is the healthy direction.
31→24 rustnet_monitor.app.state uses rustnet_monitor.app.types✕
- Connections
- 7 pairs of types, where a type in rustnet_monitor.app.state uses a type in rustnet_monitor.app.types.
- The types involved
rustnet_monitor.app.state.App→rustnet_monitor.app.types.AppOutputHandlesrustnet_monitor.app.state.App→rustnet_monitor.app.types.AppStatsrustnet_monitor.app.state.App→rustnet_monitor.app.types.Configrustnet_monitor.app.state.App→rustnet_monitor.app.types.ConnRateHistorySnapshotrustnet_monitor.app.state.App→rustnet_monitor.app.types.ConnectionCountsrustnet_monitor.app.state.App→rustnet_monitor.app.types.ProcessDetectionStatusrustnet_monitor.app.state.state$module→rustnet_monitor.app.types.Config
- Direction
- rustnet_monitor.app.state uses rustnet_monitor.app.types, so a change to rustnet_monitor.app.types can break rustnet_monitor.app.state, while a change to rustnet_monitor.app.state can't break rustnet_monitor.app.types.
- Position
- Below the diagonal: rustnet_monitor.app.state uses a module listed above it, which is the healthy direction.
31→25 rustnet_monitor.app.state uses rustnet_core.network.process_activity✕
- Connections
- 2 pairs of types, where a type in rustnet_monitor.app.state uses a type in rustnet_core.network.process_activity.
- The types involved
rustnet_monitor.app.state.App→rustnet_core.network.process_activity.ProcessActivitySnapshotrustnet_monitor.app.state.App→rustnet_core.network.process_activity.ProcessActivityTracker
- Direction
- rustnet_monitor.app.state uses rustnet_core.network.process_activity, so a change to rustnet_core.network.process_activity can break rustnet_monitor.app.state, while a change to rustnet_monitor.app.state can't break rustnet_core.network.process_activity.
- Position
- Below the diagonal: rustnet_monitor.app.state uses a module listed above it, which is the healthy direction.
31→27 rustnet_monitor.app.state uses rustnet_monitor.app.capture✕
- Connections
- 4 pairs of types, where a type in rustnet_monitor.app.state uses a type in rustnet_monitor.app.capture.
- The types involved
rustnet_monitor.app.state.App→rustnet_monitor.app.capture.CaptureStatusrustnet_monitor.app.state.App→rustnet_monitor.app.capture.OrderedBatchCommitterrustnet_monitor.app.state.App→rustnet_monitor.app.capture.OrderedBatchReceiverrustnet_monitor.app.state.App→rustnet_monitor.app.capture.PreparedCapture
- Direction
- rustnet_monitor.app.state uses rustnet_monitor.app.capture, so a change to rustnet_monitor.app.capture can break rustnet_monitor.app.state, while a change to rustnet_monitor.app.state can't break rustnet_monitor.app.capture.
- Position
- Below the diagonal: rustnet_monitor.app.state uses a module listed above it, which is the healthy direction.
32→4 rustnet_monitor.ui.state uses rustnet_core.network.time_window✕
- Connections
- 1 pair of types, where a type in rustnet_monitor.ui.state uses a type in rustnet_core.network.time_window.
- The types involved
rustnet_monitor.ui.state.UiState→rustnet_core.network.time_window.TimeWindow
- Direction
- rustnet_monitor.ui.state uses rustnet_core.network.time_window, so a change to rustnet_core.network.time_window can break rustnet_monitor.ui.state, while a change to rustnet_monitor.ui.state can't break rustnet_core.network.time_window.
- Position
- Below the diagonal: rustnet_monitor.ui.state uses a module listed above it, which is the healthy direction.
32→25 rustnet_monitor.ui.state uses rustnet_core.network.process_activity✕
- Connections
- 1 pair of types, where a type in rustnet_monitor.ui.state uses a type in rustnet_core.network.process_activity.
- The types involved
rustnet_monitor.ui.state.ActivityTableState→rustnet_core.network.process_activity.ProcessIdentity
- Direction
- rustnet_monitor.ui.state uses rustnet_core.network.process_activity, so a change to rustnet_core.network.process_activity can break rustnet_monitor.ui.state, while a change to rustnet_monitor.ui.state can't break rustnet_core.network.process_activity.
- Position
- Below the diagonal: rustnet_monitor.ui.state uses a module listed above it, which is the healthy direction.
33→6 rustnet_monitor.headless.schema uses rustnet_monitor.app.runtime✕
- Connections
- 4 pairs of types, where a type in rustnet_monitor.headless.schema uses a type in rustnet_monitor.app.runtime.
- The types involved
rustnet_monitor.headless.schema.RuntimePhase→rustnet_monitor.app.runtime.StopReportrustnet_monitor.headless.schema.RuntimeSnapshot→rustnet_monitor.app.runtime.StopReportrustnet_monitor.headless.schema.ShutdownSnapshot→rustnet_monitor.app.runtime.StopReportrustnet_monitor.headless.schema.SnapshotEnvelope→rustnet_monitor.app.runtime.StopReport
- Direction
- rustnet_monitor.headless.schema uses rustnet_monitor.app.runtime, so a change to rustnet_monitor.app.runtime can break rustnet_monitor.headless.schema, while a change to rustnet_monitor.headless.schema can't break rustnet_monitor.app.runtime.
- Position
- Below the diagonal: rustnet_monitor.headless.schema uses a module listed above it, which is the healthy direction.
33→11 rustnet_monitor.headless.schema uses rustnet_core.network.types.connection✕
- Connections
- 2 pairs of types, where a type in rustnet_monitor.headless.schema uses a type in rustnet_core.network.types.connection.
- The types involved
rustnet_monitor.headless.schema.ConnectionSnapshot→rustnet_core.network.types.connection.Connectionrustnet_monitor.headless.schema.schema$module→rustnet_core.network.types.connection.Connection
- Direction
- rustnet_monitor.headless.schema uses rustnet_core.network.types.connection, so a change to rustnet_core.network.types.connection can break rustnet_monitor.headless.schema, while a change to rustnet_monitor.headless.schema can't break rustnet_core.network.types.connection.
- Position
- Below the diagonal: rustnet_monitor.headless.schema uses a module listed above it, which is the healthy direction.
33→24 rustnet_monitor.headless.schema uses rustnet_monitor.app.types✕
- Connections
- 1 pair of types, where a type in rustnet_monitor.headless.schema uses a type in rustnet_monitor.app.types.
- The types involved
rustnet_monitor.headless.schema.StatsSnapshot→rustnet_monitor.app.types.AppStats
- Direction
- rustnet_monitor.headless.schema uses rustnet_monitor.app.types, so a change to rustnet_monitor.app.types can break rustnet_monitor.headless.schema, while a change to rustnet_monitor.headless.schema can't break rustnet_monitor.app.types.
- Position
- Below the diagonal: rustnet_monitor.headless.schema uses a module listed above it, which is the healthy direction.
33→31 rustnet_monitor.headless.schema uses rustnet_monitor.app.state✕
- Connections
- 3 pairs of types, where a type in rustnet_monitor.headless.schema uses a type in rustnet_monitor.app.state.
- The types involved
rustnet_monitor.headless.schema.RuntimeSnapshot→rustnet_monitor.app.state.Apprustnet_monitor.headless.schema.SandboxSnapshot→rustnet_monitor.app.state.Apprustnet_monitor.headless.schema.SnapshotEnvelope→rustnet_monitor.app.state.App
- Direction
- rustnet_monitor.headless.schema uses rustnet_monitor.app.state, so a change to rustnet_monitor.app.state can break rustnet_monitor.headless.schema, while a change to rustnet_monitor.headless.schema can't break rustnet_monitor.app.state.
- Position
- Below the diagonal: rustnet_monitor.headless.schema uses a module listed above it, which is the healthy direction.
34→24 rustnet_monitor.ui.component uses rustnet_monitor.app.types✕
- Connections
- 1 pair of types, where a type in rustnet_monitor.ui.component uses a type in rustnet_monitor.app.types.
- The types involved
rustnet_monitor.ui.component.DrawContext→rustnet_monitor.app.types.AppStats
- Direction
- rustnet_monitor.ui.component uses rustnet_monitor.app.types, so a change to rustnet_monitor.app.types can break rustnet_monitor.ui.component, while a change to rustnet_monitor.ui.component can't break rustnet_monitor.app.types.
- Position
- Below the diagonal: rustnet_monitor.ui.component uses a module listed above it, which is the healthy direction.
34→31 rustnet_monitor.ui.component uses rustnet_monitor.app.state✕
- Connections
- 2 pairs of types, where a type in rustnet_monitor.ui.component uses a type in rustnet_monitor.app.state.
- The types involved
rustnet_monitor.ui.component.DrawContext→rustnet_monitor.app.state.Apprustnet_monitor.ui.component.HandlerContext→rustnet_monitor.app.state.App
- Direction
- rustnet_monitor.ui.component uses rustnet_monitor.app.state, so a change to rustnet_monitor.app.state can break rustnet_monitor.ui.component, while a change to rustnet_monitor.ui.component can't break rustnet_monitor.app.state.
- Position
- Below the diagonal: rustnet_monitor.ui.component uses a module listed above it, which is the healthy direction.
34→32 rustnet_monitor.ui.component uses rustnet_monitor.ui.state✕
- Connections
- 4 pairs of types, where a type in rustnet_monitor.ui.component uses a type in rustnet_monitor.ui.state.
- The types involved
rustnet_monitor.ui.component.Component→rustnet_monitor.ui.state.ClickableRegionsrustnet_monitor.ui.component.DrawContext→rustnet_monitor.ui.state.UiStaterustnet_monitor.ui.component.HandlerContext→rustnet_monitor.ui.state.ClickableRegionsrustnet_monitor.ui.component.HandlerContext→rustnet_monitor.ui.state.UiState
- Direction
- rustnet_monitor.ui.component uses rustnet_monitor.ui.state, so a change to rustnet_monitor.ui.state can break rustnet_monitor.ui.component, while a change to rustnet_monitor.ui.component can't break rustnet_monitor.ui.state.
- Position
- Below the diagonal: rustnet_monitor.ui.component uses a module listed above it, which is the healthy direction.
35→5 rustnet_monitor.ui uses rustnet_core.network.types.protocol_info✕
- Connections
- 1 pair of types, where a type in rustnet_monitor.ui uses a type in rustnet_core.network.types.protocol_info.
- The types involved
rustnet_monitor.ui.ui$module→rustnet_core.network.types.protocol_info.ApplicationProtocol
- Direction
- rustnet_monitor.ui uses rustnet_core.network.types.protocol_info, so a change to rustnet_core.network.types.protocol_info can break rustnet_monitor.ui, while a change to rustnet_monitor.ui can't break rustnet_core.network.types.protocol_info.
- Position
- Below the diagonal: rustnet_monitor.ui uses a module listed above it, which is the healthy direction.
35→11 rustnet_monitor.ui uses rustnet_core.network.types.connection✕
- Connections
- 1 pair of types, where a type in rustnet_monitor.ui uses a type in rustnet_core.network.types.connection.
- The types involved
rustnet_monitor.ui.ui$module→rustnet_core.network.types.connection.Connection
- Direction
- rustnet_monitor.ui uses rustnet_core.network.types.connection, so a change to rustnet_core.network.types.connection can break rustnet_monitor.ui, while a change to rustnet_monitor.ui can't break rustnet_core.network.types.connection.
- Position
- Below the diagonal: rustnet_monitor.ui uses a module listed above it, which is the healthy direction.
35→24 rustnet_monitor.ui uses rustnet_monitor.app.types✕
- Connections
- 1 pair of types, where a type in rustnet_monitor.ui uses a type in rustnet_monitor.app.types.
- The types involved
rustnet_monitor.ui.ui$module→rustnet_monitor.app.types.AppStats
- Direction
- rustnet_monitor.ui uses rustnet_monitor.app.types, so a change to rustnet_monitor.app.types can break rustnet_monitor.ui, while a change to rustnet_monitor.ui can't break rustnet_monitor.app.types.
- Position
- Below the diagonal: rustnet_monitor.ui uses a module listed above it, which is the healthy direction.
35→31 rustnet_monitor.ui uses rustnet_monitor.app.state✕
- Connections
- 1 pair of types, where a type in rustnet_monitor.ui uses a type in rustnet_monitor.app.state.
- The types involved
rustnet_monitor.ui.ui$module→rustnet_monitor.app.state.App
- Direction
- rustnet_monitor.ui uses rustnet_monitor.app.state, so a change to rustnet_monitor.app.state can break rustnet_monitor.ui, while a change to rustnet_monitor.ui can't break rustnet_monitor.app.state.
- Position
- Below the diagonal: rustnet_monitor.ui uses a module listed above it, which is the healthy direction.
35→32 rustnet_monitor.ui uses rustnet_monitor.ui.state✕
- Connections
- 2 pairs of types, where a type in rustnet_monitor.ui uses a type in rustnet_monitor.ui.state.
- The types involved
rustnet_monitor.ui.ui$module→rustnet_monitor.ui.state.ClickableRegionsrustnet_monitor.ui.ui$module→rustnet_monitor.ui.state.UiState
- Direction
- rustnet_monitor.ui uses rustnet_monitor.ui.state, so a change to rustnet_monitor.ui.state can break rustnet_monitor.ui, while a change to rustnet_monitor.ui can't break rustnet_monitor.ui.state.
- Position
- Below the diagonal: rustnet_monitor.ui uses a module listed above it, which is the healthy direction.
35→34 rustnet_monitor.ui uses rustnet_monitor.ui.component✕
- Connections
- 2 pairs of types, where a type in rustnet_monitor.ui uses a type in rustnet_monitor.ui.component.
- The types involved
rustnet_monitor.ui.ui$module→rustnet_monitor.ui.component.Effectrustnet_monitor.ui.ui$module→rustnet_monitor.ui.component.HandlerContext
- Direction
- rustnet_monitor.ui uses rustnet_monitor.ui.component, so a change to rustnet_monitor.ui.component can break rustnet_monitor.ui, while a change to rustnet_monitor.ui can't break rustnet_monitor.ui.component.
- Position
- Below the diagonal: rustnet_monitor.ui uses a module listed above it, which is the healthy direction.
36→25 rustnet_monitor.ui.tabs.activity uses rustnet_core.network.process_activity✕
- Connections
- 3 pairs of types, where a type in rustnet_monitor.ui.tabs.activity uses a type in rustnet_core.network.process_activity.
- The types involved
rustnet_monitor.ui.tabs.activity.activity$module→rustnet_core.network.process_activity.DestinationActivityrustnet_monitor.ui.tabs.activity.activity$module→rustnet_core.network.process_activity.ProcessActivityrustnet_monitor.ui.tabs.activity.activity$module→rustnet_core.network.process_activity.ProcessActivitySnapshot
- Direction
- rustnet_monitor.ui.tabs.activity uses rustnet_core.network.process_activity, so a change to rustnet_core.network.process_activity can break rustnet_monitor.ui.tabs.activity, while a change to rustnet_monitor.ui.tabs.activity can't break rustnet_core.network.process_activity.
- Position
- Below the diagonal: rustnet_monitor.ui.tabs.activity uses a module listed above it, which is the healthy direction.
36→31 rustnet_monitor.ui.tabs.activity uses rustnet_monitor.app.state✕
- Connections
- 1 pair of types, where a type in rustnet_monitor.ui.tabs.activity uses a type in rustnet_monitor.app.state.
- The types involved
rustnet_monitor.ui.tabs.activity.activity$module→rustnet_monitor.app.state.App
- Direction
- rustnet_monitor.ui.tabs.activity uses rustnet_monitor.app.state, so a change to rustnet_monitor.app.state can break rustnet_monitor.ui.tabs.activity, while a change to rustnet_monitor.ui.tabs.activity can't break rustnet_monitor.app.state.
- Position
- Below the diagonal: rustnet_monitor.ui.tabs.activity uses a module listed above it, which is the healthy direction.
36→32 rustnet_monitor.ui.tabs.activity uses rustnet_monitor.ui.state✕
- Connections
- 5 pairs of types, where a type in rustnet_monitor.ui.tabs.activity uses a type in rustnet_monitor.ui.state.
- The types involved
rustnet_monitor.ui.tabs.activity.ActivityTab→rustnet_monitor.ui.state.ClickableRegionsrustnet_monitor.ui.tabs.activity.activity$module→rustnet_monitor.ui.state.ActivityDirectionrustnet_monitor.ui.tabs.activity.activity$module→rustnet_monitor.ui.state.ActivitySortrustnet_monitor.ui.tabs.activity.activity$module→rustnet_monitor.ui.state.ClickableRegionsrustnet_monitor.ui.tabs.activity.activity$module→rustnet_monitor.ui.state.UiState
- Direction
- rustnet_monitor.ui.tabs.activity uses rustnet_monitor.ui.state, so a change to rustnet_monitor.ui.state can break rustnet_monitor.ui.tabs.activity, while a change to rustnet_monitor.ui.tabs.activity can't break rustnet_monitor.ui.state.
- Position
- Below the diagonal: rustnet_monitor.ui.tabs.activity uses a module listed above it, which is the healthy direction.
36→34 rustnet_monitor.ui.tabs.activity uses rustnet_monitor.ui.component✕
- Connections
- 3 pairs of types, where a type in rustnet_monitor.ui.tabs.activity uses a type in rustnet_monitor.ui.component.
- The types involved
rustnet_monitor.ui.tabs.activity.ActivityTab→rustnet_monitor.ui.component.Componentrustnet_monitor.ui.tabs.activity.ActivityTab→rustnet_monitor.ui.component.Effectrustnet_monitor.ui.tabs.activity.ActivityTab→rustnet_monitor.ui.component.HandlerContext
- Direction
- rustnet_monitor.ui.tabs.activity uses rustnet_monitor.ui.component, so a change to rustnet_monitor.ui.component can break rustnet_monitor.ui.tabs.activity, while a change to rustnet_monitor.ui.tabs.activity can't break rustnet_monitor.ui.component.
- Position
- Below the diagonal: rustnet_monitor.ui.tabs.activity uses a module listed above it, which is the healthy direction.
37→1 rustnet_monitor.ui.tabs.details uses rustnet_core.network.dns✕
- Connections
- 1 pair of types, where a type in rustnet_monitor.ui.tabs.details uses a type in rustnet_core.network.dns.
- The types involved
rustnet_monitor.ui.tabs.details.details$module→rustnet_core.network.dns.DnsResolver
- Direction
- rustnet_monitor.ui.tabs.details uses rustnet_core.network.dns, so a change to rustnet_core.network.dns can break rustnet_monitor.ui.tabs.details, while a change to rustnet_monitor.ui.tabs.details can't break rustnet_core.network.dns.
- Position
- Below the diagonal: rustnet_monitor.ui.tabs.details uses a module listed above it, which is the healthy direction.
37→5 rustnet_monitor.ui.tabs.details uses rustnet_core.network.types.protocol_info✕
- Connections
- 3 pairs of types, where a type in rustnet_monitor.ui.tabs.details uses a type in rustnet_core.network.types.protocol_info.
- The types involved
rustnet_monitor.ui.tabs.details.details$module→rustnet_core.network.types.protocol_info.DnsQueryTyperustnet_monitor.ui.tabs.details.details$module→rustnet_core.network.types.protocol_info.HttpInforustnet_monitor.ui.tabs.details.details$module→rustnet_core.network.types.protocol_info.QuicCloseInfo
- Direction
- rustnet_monitor.ui.tabs.details uses rustnet_core.network.types.protocol_info, so a change to rustnet_core.network.types.protocol_info can break rustnet_monitor.ui.tabs.details, while a change to rustnet_monitor.ui.tabs.details can't break rustnet_core.network.types.protocol_info.
- Position
- Below the diagonal: rustnet_monitor.ui.tabs.details uses a module listed above it, which is the healthy direction.
37→11 rustnet_monitor.ui.tabs.details uses rustnet_core.network.types.connection✕
- Connections
- 1 pair of types, where a type in rustnet_monitor.ui.tabs.details uses a type in rustnet_core.network.types.connection.
- The types involved
rustnet_monitor.ui.tabs.details.details$module→rustnet_core.network.types.connection.Connection
- Direction
- rustnet_monitor.ui.tabs.details uses rustnet_core.network.types.connection, so a change to rustnet_core.network.types.connection can break rustnet_monitor.ui.tabs.details, while a change to rustnet_monitor.ui.tabs.details can't break rustnet_core.network.types.connection.
- Position
- Below the diagonal: rustnet_monitor.ui.tabs.details uses a module listed above it, which is the healthy direction.
37→12 rustnet_monitor.ui.tabs.details uses rustnet_core.network.types.identity✕
- Connections
- 2 pairs of types, where a type in rustnet_monitor.ui.tabs.details uses a type in rustnet_core.network.types.identity.
- The types involved
rustnet_monitor.ui.tabs.details.details$module→rustnet_core.network.types.identity.AddrKindrustnet_monitor.ui.tabs.details.details$module→rustnet_core.network.types.identity.ProcessLineage
- Direction
- rustnet_monitor.ui.tabs.details uses rustnet_core.network.types.identity, so a change to rustnet_core.network.types.identity can break rustnet_monitor.ui.tabs.details, while a change to rustnet_monitor.ui.tabs.details can't break rustnet_core.network.types.identity.
- Position
- Below the diagonal: rustnet_monitor.ui.tabs.details uses a module listed above it, which is the healthy direction.
37→32 rustnet_monitor.ui.tabs.details uses rustnet_monitor.ui.state✕
- Connections
- 3 pairs of types, where a type in rustnet_monitor.ui.tabs.details uses a type in rustnet_monitor.ui.state.
- The types involved
rustnet_monitor.ui.tabs.details.DetailsTab→rustnet_monitor.ui.state.ClickableRegionsrustnet_monitor.ui.tabs.details.details$module→rustnet_monitor.ui.state.ClickableRegionsrustnet_monitor.ui.tabs.details.details$module→rustnet_monitor.ui.state.UiState
- Direction
- rustnet_monitor.ui.tabs.details uses rustnet_monitor.ui.state, so a change to rustnet_monitor.ui.state can break rustnet_monitor.ui.tabs.details, while a change to rustnet_monitor.ui.tabs.details can't break rustnet_monitor.ui.state.
- Position
- Below the diagonal: rustnet_monitor.ui.tabs.details uses a module listed above it, which is the healthy direction.
37→34 rustnet_monitor.ui.tabs.details uses rustnet_monitor.ui.component✕
- Connections
- 5 pairs of types, where a type in rustnet_monitor.ui.tabs.details uses a type in rustnet_monitor.ui.component.
- The types involved
rustnet_monitor.ui.tabs.details.DetailsTab→rustnet_monitor.ui.component.Componentrustnet_monitor.ui.tabs.details.DetailsTab→rustnet_monitor.ui.component.Effectrustnet_monitor.ui.tabs.details.DetailsTab→rustnet_monitor.ui.component.HandlerContextrustnet_monitor.ui.tabs.details.details$module→rustnet_monitor.ui.component.Effectrustnet_monitor.ui.tabs.details.details$module→rustnet_monitor.ui.component.HandlerContext
- Direction
- rustnet_monitor.ui.tabs.details uses rustnet_monitor.ui.component, so a change to rustnet_monitor.ui.component can break rustnet_monitor.ui.tabs.details, while a change to rustnet_monitor.ui.tabs.details can't break rustnet_monitor.ui.component.
- Position
- Below the diagonal: rustnet_monitor.ui.tabs.details uses a module listed above it, which is the healthy direction.
38→11 rustnet_monitor.ui.tabs.graph uses rustnet_core.network.types.connection✕
- Connections
- 2 pairs of types, where a type in rustnet_monitor.ui.tabs.graph uses a type in rustnet_core.network.types.connection.
- The types involved
rustnet_monitor.ui.tabs.graph.GraphAnalytics→rustnet_core.network.types.connection.AppProtocolDistributionrustnet_monitor.ui.tabs.graph.graph$module→rustnet_core.network.types.connection.AppProtocolDistribution
- Direction
- rustnet_monitor.ui.tabs.graph uses rustnet_core.network.types.connection, so a change to rustnet_core.network.types.connection can break rustnet_monitor.ui.tabs.graph, while a change to rustnet_monitor.ui.tabs.graph can't break rustnet_core.network.types.connection.
- Position
- Below the diagonal: rustnet_monitor.ui.tabs.graph uses a module listed above it, which is the healthy direction.
38→12 rustnet_monitor.ui.tabs.graph uses rustnet_core.network.types.identity✕
- Connections
- 1 pair of types, where a type in rustnet_monitor.ui.tabs.graph uses a type in rustnet_core.network.types.identity.
- The types involved
rustnet_monitor.ui.tabs.graph.graph$module→rustnet_core.network.types.identity.TcpState
- Direction
- rustnet_monitor.ui.tabs.graph uses rustnet_core.network.types.identity, so a change to rustnet_core.network.types.identity can break rustnet_monitor.ui.tabs.graph, while a change to rustnet_monitor.ui.tabs.graph can't break rustnet_core.network.types.identity.
- Position
- Below the diagonal: rustnet_monitor.ui.tabs.graph uses a module listed above it, which is the healthy direction.
38→31 rustnet_monitor.ui.tabs.graph uses rustnet_monitor.app.state✕
- Connections
- 1 pair of types, where a type in rustnet_monitor.ui.tabs.graph uses a type in rustnet_monitor.app.state.
- The types involved
rustnet_monitor.ui.tabs.graph.graph$module→rustnet_monitor.app.state.App
- Direction
- rustnet_monitor.ui.tabs.graph uses rustnet_monitor.app.state, so a change to rustnet_monitor.app.state can break rustnet_monitor.ui.tabs.graph, while a change to rustnet_monitor.ui.tabs.graph can't break rustnet_monitor.app.state.
- Position
- Below the diagonal: rustnet_monitor.ui.tabs.graph uses a module listed above it, which is the healthy direction.
38→32 rustnet_monitor.ui.tabs.graph uses rustnet_monitor.ui.state✕
- Connections
- 3 pairs of types, where a type in rustnet_monitor.ui.tabs.graph uses a type in rustnet_monitor.ui.state.
- The types involved
rustnet_monitor.ui.tabs.graph.GraphTab→rustnet_monitor.ui.state.ClickableRegionsrustnet_monitor.ui.tabs.graph.graph$module→rustnet_monitor.ui.state.PaneScrollrustnet_monitor.ui.tabs.graph.graph$module→rustnet_monitor.ui.state.UiState
- Direction
- rustnet_monitor.ui.tabs.graph uses rustnet_monitor.ui.state, so a change to rustnet_monitor.ui.state can break rustnet_monitor.ui.tabs.graph, while a change to rustnet_monitor.ui.tabs.graph can't break rustnet_monitor.ui.state.
- Position
- Below the diagonal: rustnet_monitor.ui.tabs.graph uses a module listed above it, which is the healthy direction.
38→34 rustnet_monitor.ui.tabs.graph uses rustnet_monitor.ui.component✕
- Connections
- 3 pairs of types, where a type in rustnet_monitor.ui.tabs.graph uses a type in rustnet_monitor.ui.component.
- The types involved
rustnet_monitor.ui.tabs.graph.GraphTab→rustnet_monitor.ui.component.Componentrustnet_monitor.ui.tabs.graph.GraphTab→rustnet_monitor.ui.component.Effectrustnet_monitor.ui.tabs.graph.GraphTab→rustnet_monitor.ui.component.HandlerContext
- Direction
- rustnet_monitor.ui.tabs.graph uses rustnet_monitor.ui.component, so a change to rustnet_monitor.ui.component can break rustnet_monitor.ui.tabs.graph, while a change to rustnet_monitor.ui.tabs.graph can't break rustnet_monitor.ui.component.
- Position
- Below the diagonal: rustnet_monitor.ui.tabs.graph uses a module listed above it, which is the healthy direction.
39→4 rustnet_monitor.ui.tabs.host uses rustnet_core.network.time_window✕
- Connections
- 1 pair of types, where a type in rustnet_monitor.ui.tabs.host uses a type in rustnet_core.network.time_window.
- The types involved
rustnet_monitor.ui.tabs.host.host$module→rustnet_core.network.time_window.TimeWindow
- Direction
- rustnet_monitor.ui.tabs.host uses rustnet_core.network.time_window, so a change to rustnet_core.network.time_window can break rustnet_monitor.ui.tabs.host, while a change to rustnet_monitor.ui.tabs.host can't break rustnet_core.network.time_window.
- Position
- Below the diagonal: rustnet_monitor.ui.tabs.host uses a module listed above it, which is the healthy direction.
39→10 rustnet_monitor.ui.tabs.host uses rustnet_core.network.types.network_events✕
- Connections
- 1 pair of types, where a type in rustnet_monitor.ui.tabs.host uses a type in rustnet_core.network.types.network_events.
- The types involved
rustnet_monitor.ui.tabs.host.host$module→rustnet_core.network.types.network_events.NetworkEventSnapshot
- Direction
- rustnet_monitor.ui.tabs.host uses rustnet_core.network.types.network_events, so a change to rustnet_core.network.types.network_events can break rustnet_monitor.ui.tabs.host, while a change to rustnet_monitor.ui.tabs.host can't break rustnet_core.network.types.network_events.
- Position
- Below the diagonal: rustnet_monitor.ui.tabs.host uses a module listed above it, which is the healthy direction.
39→13 rustnet_monitor.ui.tabs.host uses rustnet_core.network.dns_analytics✕
- Connections
- 2 pairs of types, where a type in rustnet_monitor.ui.tabs.host uses a type in rustnet_core.network.dns_analytics.
- The types involved
rustnet_monitor.ui.tabs.host.host$module→rustnet_core.network.dns_analytics.DnsAnalyticsSnapshotrustnet_monitor.ui.tabs.host.host$module→rustnet_core.network.dns_analytics.DnsHealth
- Direction
- rustnet_monitor.ui.tabs.host uses rustnet_core.network.dns_analytics, so a change to rustnet_core.network.dns_analytics can break rustnet_monitor.ui.tabs.host, while a change to rustnet_monitor.ui.tabs.host can't break rustnet_core.network.dns_analytics.
- Position
- Below the diagonal: rustnet_monitor.ui.tabs.host uses a module listed above it, which is the healthy direction.
39→32 rustnet_monitor.ui.tabs.host uses rustnet_monitor.ui.state✕
- Connections
- 1 pair of types, where a type in rustnet_monitor.ui.tabs.host uses a type in rustnet_monitor.ui.state.
- The types involved
rustnet_monitor.ui.tabs.host.HostTab→rustnet_monitor.ui.state.ClickableRegions
- Direction
- rustnet_monitor.ui.tabs.host uses rustnet_monitor.ui.state, so a change to rustnet_monitor.ui.state can break rustnet_monitor.ui.tabs.host, while a change to rustnet_monitor.ui.tabs.host can't break rustnet_monitor.ui.state.
- Position
- Below the diagonal: rustnet_monitor.ui.tabs.host uses a module listed above it, which is the healthy direction.
39→34 rustnet_monitor.ui.tabs.host uses rustnet_monitor.ui.component✕
- Connections
- 3 pairs of types, where a type in rustnet_monitor.ui.tabs.host uses a type in rustnet_monitor.ui.component.
- The types involved
rustnet_monitor.ui.tabs.host.HostTab→rustnet_monitor.ui.component.Componentrustnet_monitor.ui.tabs.host.HostTab→rustnet_monitor.ui.component.Effectrustnet_monitor.ui.tabs.host.HostTab→rustnet_monitor.ui.component.HandlerContext
- Direction
- rustnet_monitor.ui.tabs.host uses rustnet_monitor.ui.component, so a change to rustnet_monitor.ui.component can break rustnet_monitor.ui.tabs.host, while a change to rustnet_monitor.ui.tabs.host can't break rustnet_monitor.ui.component.
- Position
- Below the diagonal: rustnet_monitor.ui.tabs.host uses a module listed above it, which is the healthy direction.
40→1 rustnet_monitor.ui.tabs.overview uses rustnet_core.network.dns✕
- Connections
- 1 pair of types, where a type in rustnet_monitor.ui.tabs.overview uses a type in rustnet_core.network.dns.
- The types involved
rustnet_monitor.ui.tabs.overview.overview$module→rustnet_core.network.dns.DnsResolver
- Direction
- rustnet_monitor.ui.tabs.overview uses rustnet_core.network.dns, so a change to rustnet_core.network.dns can break rustnet_monitor.ui.tabs.overview, while a change to rustnet_monitor.ui.tabs.overview can't break rustnet_core.network.dns.
- Position
- Below the diagonal: rustnet_monitor.ui.tabs.overview uses a module listed above it, which is the healthy direction.
40→7 rustnet_monitor.ui.tabs.overview uses rustnet_sandbox✕
- Connections
- 1 pair of types, where a type in rustnet_monitor.ui.tabs.overview uses a type in rustnet_sandbox.
- The types involved
rustnet_monitor.ui.tabs.overview.overview$module→rustnet_sandbox.SandboxStatus
- Direction
- rustnet_monitor.ui.tabs.overview uses rustnet_sandbox, so a change to rustnet_sandbox can break rustnet_monitor.ui.tabs.overview, while a change to rustnet_monitor.ui.tabs.overview can't break rustnet_sandbox.
- Position
- Below the diagonal: rustnet_monitor.ui.tabs.overview uses a module listed above it, which is the healthy direction.
40→13 rustnet_monitor.ui.tabs.overview uses rustnet_core.network.dns_analytics✕
- Connections
- 1 pair of types, where a type in rustnet_monitor.ui.tabs.overview uses a type in rustnet_core.network.dns_analytics.
- The types involved
rustnet_monitor.ui.tabs.overview.overview$module→rustnet_core.network.dns_analytics.DnsAnalyticsSnapshot
- Direction
- rustnet_monitor.ui.tabs.overview uses rustnet_core.network.dns_analytics, so a change to rustnet_core.network.dns_analytics can break rustnet_monitor.ui.tabs.overview, while a change to rustnet_monitor.ui.tabs.overview can't break rustnet_core.network.dns_analytics.
- Position
- Below the diagonal: rustnet_monitor.ui.tabs.overview uses a module listed above it, which is the healthy direction.
40→24 rustnet_monitor.ui.tabs.overview uses rustnet_monitor.app.types✕
- Connections
- 2 pairs of types, where a type in rustnet_monitor.ui.tabs.overview uses a type in rustnet_monitor.app.types.
- The types involved
rustnet_monitor.ui.tabs.overview.overview$module→rustnet_monitor.app.types.AppStatsrustnet_monitor.ui.tabs.overview.overview$module→rustnet_monitor.app.types.ConnectionCounts
- Direction
- rustnet_monitor.ui.tabs.overview uses rustnet_monitor.app.types, so a change to rustnet_monitor.app.types can break rustnet_monitor.ui.tabs.overview, while a change to rustnet_monitor.ui.tabs.overview can't break rustnet_monitor.app.types.
- Position
- Below the diagonal: rustnet_monitor.ui.tabs.overview uses a module listed above it, which is the healthy direction.
40→31 rustnet_monitor.ui.tabs.overview uses rustnet_monitor.app.state✕
- Connections
- 1 pair of types, where a type in rustnet_monitor.ui.tabs.overview uses a type in rustnet_monitor.app.state.
- The types involved
rustnet_monitor.ui.tabs.overview.overview$module→rustnet_monitor.app.state.App
- Direction
- rustnet_monitor.ui.tabs.overview uses rustnet_monitor.app.state, so a change to rustnet_monitor.app.state can break rustnet_monitor.ui.tabs.overview, while a change to rustnet_monitor.ui.tabs.overview can't break rustnet_monitor.app.state.
- Position
- Below the diagonal: rustnet_monitor.ui.tabs.overview uses a module listed above it, which is the healthy direction.
40→32 rustnet_monitor.ui.tabs.overview uses rustnet_monitor.ui.state✕
- Connections
- 5 pairs of types, where a type in rustnet_monitor.ui.tabs.overview uses a type in rustnet_monitor.ui.state.
- The types involved
rustnet_monitor.ui.tabs.overview.OverviewTab→rustnet_monitor.ui.state.ClickableRegionsrustnet_monitor.ui.tabs.overview.overview$module→rustnet_monitor.ui.state.ClickableRegionsrustnet_monitor.ui.tabs.overview.overview$module→rustnet_monitor.ui.state.PaneScrollrustnet_monitor.ui.tabs.overview.overview$module→rustnet_monitor.ui.state.ProcessGroupStatsrustnet_monitor.ui.tabs.overview.overview$module→rustnet_monitor.ui.state.UiState
- Direction
- rustnet_monitor.ui.tabs.overview uses rustnet_monitor.ui.state, so a change to rustnet_monitor.ui.state can break rustnet_monitor.ui.tabs.overview, while a change to rustnet_monitor.ui.tabs.overview can't break rustnet_monitor.ui.state.
- Position
- Below the diagonal: rustnet_monitor.ui.tabs.overview uses a module listed above it, which is the healthy direction.
40→34 rustnet_monitor.ui.tabs.overview uses rustnet_monitor.ui.component✕
- Connections
- 5 pairs of types, where a type in rustnet_monitor.ui.tabs.overview uses a type in rustnet_monitor.ui.component.
- The types involved
rustnet_monitor.ui.tabs.overview.OverviewTab→rustnet_monitor.ui.component.Componentrustnet_monitor.ui.tabs.overview.OverviewTab→rustnet_monitor.ui.component.Effectrustnet_monitor.ui.tabs.overview.OverviewTab→rustnet_monitor.ui.component.HandlerContextrustnet_monitor.ui.tabs.overview.overview$module→rustnet_monitor.ui.component.Effectrustnet_monitor.ui.tabs.overview.overview$module→rustnet_monitor.ui.component.HandlerContext
- Direction
- rustnet_monitor.ui.tabs.overview uses rustnet_monitor.ui.component, so a change to rustnet_monitor.ui.component can break rustnet_monitor.ui.tabs.overview, while a change to rustnet_monitor.ui.tabs.overview can't break rustnet_monitor.ui.component.
- Position
- Below the diagonal: rustnet_monitor.ui.tabs.overview uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 32 | High / Critical |
| A02:2025 — Security Misconfiguration | 5 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 4 | Medium |
Roadmap
Begin by addressing the six static analysis shell injection issues, prioritizing REDACTED and REDACTED, and resolve the twenty-five churn and complexity hotspots starting with mod.rs, details.rs, and connection.rs. Simultaneously, document the single missing architectural decision by creating a concise record in the docs/adr folder. Finally, update the root README to include a clear Testing section that explains how to run the test suite.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +1.6 pts | Low | ADR Quality |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +1.5 pts | Medium | Architecture documentation |
| Resolve the 6 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4), REDACTED (2). | +0.7 pts | Low | Static Analysis (SAST) |
| Resolve the 5 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (5). | +0.7 pts | Low | Static Analysis (SAST) |
| Resolve the 3 High IaC finding(s) in IaC & Container Security — start with REDACTED (2), REDACTED.cross. | +0.6 pts | Low | IaC & Container Security |
| Resolve the 25 Hotspot finding(s) in Churn × Complexity Hotspots — start with mod.rs (3), details.rs, connection.rs. | +0.8 pts | High | Churn × Complexity Hotspots |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +0.4 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +0.4 pts | Low | Supply-chain Provenance & Signing |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 4.1 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.5 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| crates/rustnet-core/src/network/tracker.rs | 5.1 | Mixed | Change Coupling: Boundary-crossing change coupling: tracker.rs ↔ details.rs |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| src/ui/tabs/details.rs | 5.5 | Mixed | Cyclomatic Complexity: rustnet_monitor::ui::tabs::details::draw_connection_details (cyclomatic 91) |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | IaC & Container Security: High IaC: REDACTED |
| crates/rustnet-sandbox/src/linux/landlock.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/ui/tabs/activity.rs | 7.0 | Mixed | Cyclomatic Complexity: ActivityTab::handle_key (cyclomatic 24) |
| src/ui/tabs/overview.rs | 7.0 | Mixed | Cyclomatic Complexity: rustnet_monitor::ui::tabs::overview::draw_stats_panel (cyclomatic 32) |
| src/app/capture.rs | 7.0 | Mixed | Cyclomatic Complexity: App::start_capture_thread (cyclomatic 35) |
| crates/rustnet-core/src/network/merge.rs | 7.0 | Mixed | Cyclomatic Complexity: rustnet_core::network::merge::analyze_tcp_segment (cyclomatic 26) |
| crates/rustnet-core/src/network/dpi/quic/salvage.rs | 7.1 | Mixed | Cyclomatic Complexity: rustnet_core::network::dpi::quic::salvage::try_reconstruct_sni_from_fragments (cyclomatic 26) |
| crates/rustnet-core/src/network/types/connection.rs | 7.1 | Mixed | Cyclomatic Complexity: Connection::state (cyclomatic 52) |
| crates/rustnet-core/src/network/dpi/quic/packet.rs | 7.1 | Mixed | Cyclomatic Complexity: rustnet_core::network::dpi::quic::packet::scan_packet_frames (cyclomatic 36) |
| scripts/pcap_enrich.py | 7.1 | Mixed | Cyclomatic Complexity: pcap_enrich.create_pcapng (cyclomatic 16) |
| src/ui/tabs/graph.rs | 7.1 | Mixed | Cognitive Complexity: rustnet_monitor::ui::tabs::graph::draw_health_chart (cognitive 20) |
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. 58 of 58 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 — 58 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, 242 of 254 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, 143 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.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (12 contributor(s) across 808 commit(s) sampled, automation and bot accounts excluded). One of them holds 92% of the history; the other 11 hold 0.7% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D24 Comment Value — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D27 Navigability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- AX6 Interface segregation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AXR1 Runtime accessibility — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via REDACTED (REDACTED). docker build failed (exit 1) — rixie-slim@sha256:a29215f6a35e51e22adffa17f89e9d2ef06214e64a2bad10d765c46aea49f11f: failed to resolve source metadata for docker.io/library/debian:trixie-slim@sha256:a29215f6a35e51e22adffa17f89e9d2ef06214e64a2bad10d765c46aea49f11f: failed to do request: Head "https://registry-1.docker.io/v2/library/debian/manifests/sha256:a29215f6a35e51e22adffa17f89e9d2ef06214e64a2bad10d765c46aea49f11f": Forbidden; runtime evidence skipped.
- C1 Data Protection — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'mysql' is imported (crates/rustnet-core/src/network/dpi/mod.rs:83), 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. 'mysql' is imported (crates/rustnet-core/src/network/dpi/mod.rs:83), 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. 'mysql' is imported (crates/rustnet-core/src/network/dpi/mod.rs:83), 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. 'mysql' is imported (crates/rustnet-core/src/network/dpi/mod.rs:83), 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 Python, Rust, c is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's Python, Rust, c is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- M4 Documentation accuracy — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9). Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- X16 Unfloored truncation loop — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X18 Disposal-pattern correctness — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- 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 C, Python, Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- 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 REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- 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
41 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was rustnet_monitor::ui::tabs::details::draw_connection_details at 91. A further 13 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 DnsQueryType::from_wire at 48 — they are counted neither in the figure above nor in this dimension's score. 4 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: crates/rustnet-core/src/network/dpi/bittorrent.rs (rustnet_core::network::dpi::bittorrent::decode_client_name at 24), src/ui/theme/definitions.rs (ThemeSpec::set_token at 24), crates/rustnet-core/src/network/dpi/mqtt.rs (rustnet_core::network::dpi::mqtt::analyze_mqtt at 21), crates/rustnet-host/src/lib.rs (DegradationReason::description at 16). 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 2 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with rustnet_monitor::ui::tabs::details::draw_connection_details (cyclomatic 91), rustnet_monitor::tui::run (cyclomatic 68). — 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 2 together lifts Cyclomatic Complexity from 6.1 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
- 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
73 method(s) exceeded the cognitive complexity threshold of 15; the worst was rustnet_monitor::tui::run at 200.
What to do
- Bring the 1 body over 120 down to 120 or less in Cognitive Complexity — start with rustnet_monitor::tui::run (cognitive 200). — Refactoring it lifts Cognitive Complexity from 3.4 to about 4.3/10.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
46 god class(es) detected.
What to do
- Resolve the 16 FileTooLong finding(s) in God Classes — start with state.rs (2), details.rs, overview.rs. — One of this dimension's main actionable groups (16 warning-level).
- Resolve the 14 FunctionTooLong finding(s) in God Classes — start with details.rs (2), activity.rs (2), overview.rs. — One of this dimension's main actionable groups (14 warning-level).
- Resolve the 5 MethodTooLong finding(s) in God Classes — start with capture.rs (2), enrichment.rs, schema.rs. — One of this dimension's main actionable groups (5 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
12 duplicated block group(s) detected. One further row reports members as variants of one another; it aggregates block groups already counted above and is not itself counted.
What to do
- Resolve the 3 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with tracker.rs, loader.rs, graph.rs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with process.rs, details.rs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Members sharing a duplicated core (4 members, 50+ identical tokens) finding(s) in Code Duplication — start with definitions.rs. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
5 production modules (Cargo), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 3 module(s) off the main sequence.
What to do
- Resolve the 3 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (3 warning-level).
- Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
0 of 85 classes have LCOM4 above 3.
D9 · Test Distribution
1458 test methods: 1443 unit, 15 integration, 0 BDD, 0 e2e. The Rust suite contributes 1458 `#[test]` function(s) across 143 file(s) declaring at least one; its unit/integration split is Cargo's own — 5 of those file(s) are integration-test targets under a crate's tests/ directory, and the rest are #[test] functions compiled into the crate they test.
D12 · Dependency Hygiene
2 outdated, 0 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 Cargo.lock there.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 411 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository's Cargo.lock closed over its manifests' `[dependencies]` and `[build-dependencies]`. Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository. This repository publishes itself under Apache-2.0, which is its own choice and is not judged here.
D15 · Churn × Complexity Hotspots
Top hotspots: src/ui/tabs/details.rs (42×91=3822); src/ui/mod.rs (51×18=918); crates/rustnet-core/src/network/types/connection.rs (15×52=780)
What to do
- Resolve the 25 Hotspot finding(s) in Churn × Complexity Hotspots — start with mod.rs (3), details.rs, connection.rs. — One of this dimension's main actionable groups (25 warning-level).
D17 · Explicit Debt
1 deducted task-comment markers across 80993 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 1 TodoComment finding(s) in Explicit Debt — start with landlock.rs. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 12 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
2 of 5 build units (Cargo) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
32 finding(s): 0 critical, 32 high, 0 medium, 0 low. 8 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 1 file(s) — `crates/rustnet-sandbox/src/macos/seatbelt.rs` (line 55, line 64) — 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 11 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 6 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4), REDACTED (2). — One of this dimension's main actionable groups (6 issue-level).
- Resolve the 5 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (5). — One of this dimension's main actionable groups (5 issue-level).
- No action in Static Analysis (SAST) — all 8 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 (8 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
No known-vulnerable dependencies in any ecosystem this repository declares.
D31 · IaC & Container Security
5 finding(s): 0 critical, 3 high, 2 medium, 0 low.
What to do
- Resolve the 3 High IaC finding(s) in IaC & Container Security — start with REDACTED (2), REDACTED.cross. — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 2 Medium IaC finding(s) in IaC & Container Security — start with REDACTED.cross (2). — One of this dimension's main actionable groups (2 warning-level).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 161 of the 183 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: tracker.rs↔details.rs 75%; details.rs↔help.rs 50%
What to do
- Resolve the 1 Boundary-crossing change coupling finding(s) in Change Coupling — start with tracker.rs. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Change coupling finding(s) in Change Coupling — start with details.rs. — One of this dimension's main actionable groups (1 warning-level).
D36 · Supply-chain Provenance & Signing
2/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D37 · Vulnerability-disclosure Policy
A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
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
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.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
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
P6 · Release Hygiene
PF1 · Benchmark discipline
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X17 · Uncapped recursion over a caller-supplied document
X19 · Unrestored process-global state
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
X30 · Support guard that admits what it rejects
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 89% | Adequate — gated by D2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 88% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 80% | Strong | Largest drag on the score — prioritise here. |
| Readiness | 83% | Strong | Solid. |
| Security | 80% | Adequate — gated by D29 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 85% | Strong | Strongest area. |
Unscored — 3 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X9 Subsumed condition operand — 1 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 'mysql' (crates/rustnet-core/src/network/dpi/mod.rs:83) 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 'mysql' (crates/rustnet-core/src/network/dpi/mod.rs:83) 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 'mysql' (crates/rustnet-core/src/network/dpi/mod.rs:83) 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 — 55 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
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — docker build failed (exit 1) — rixie-slim@sha256:a29215f6a35e51e22adffa17f89e9d2ef06214e64a2bad10d765c46aea49f11f: failed to resolve source metadata for docker.io/library/debian:trixie-slim@sha256:a29215f6a35e51e22adffa17f89e9d2ef06214e64a2bad10d765c46aea49f11f: failed to do request: Head "https://registry-1.docker.io/v2/library/debian/manifests/sha256:a29215f6a35e51e22adffa17f89e9d2ef06214e64a2bad10d765c46aea49f11f": Forbidden; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — Not assessed: this repository stores data through 'mysql' (crates/rustnet-core/src/network/dpi/mod.rs:83) 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.
- C2 Access Controls — No access-control surface detected in the analyzed source — this repository starts no server another machine can reach (no actix-web HttpServer, axum::serve, Rocket launch, warp::serve, poem or salvo Server, tonic Server::builder, hyper or tiny_http server outside examples and tests, none bound beyond loopback). Access control is therefore N/A here — a crate is authorized by the application that serves it, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- D10 Test Quality — ~2068 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
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — Naming consistency is measured on C# only; Python, Rust not measured.
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed Rust surface was not measured.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ projects each declaring an entity of their own. Aggregate roots were found in only one source directory (rustnet-core), which is a layered codebase, not two contexts. 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 .py, .rs, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.rs), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- 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): 2 aggregate root(s) (types guarding their own state behind command methods — this language has no AggregateRoot base to inherit); 12 value object(s)
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the Python, Rust source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- 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.
- PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
- S1 Web-Security Posture — No web surface: 173 Rust file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation and obsolete TLS versions, and none was found. This repository serves no HTTP of its own — no HTTP-server crate (actix-web, axum, Rocket, warp, poem, tide, salvo, tonic, a hyper server, …) among its Cargo manifests' run-time dependencies, and no server started in its production source — so HTTPS enforcement, HSTS, cookie flags and input validation are N/A here, as they are for a C# library or worker. If this codebase starts serving HTTP, the dimension reactivates automatically.
- X16 Unfloored truncation loop — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X18 Disposal-pattern correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X2 Cancellation propagation — no C# was loaded; this repository's Python and Rust were read, and no request in it can be cancelled by a caller — a Python request takes no token: asyncio cancels the task and trio or anyio the scope that made it, from outside the call, and requests, httpx, aiohttp and gRPC take a timeout, not a cancellation; a Rust request takes no token: a future is cancelled by dropping it, from outside the call (select!, a timeout, an aborted task), and reqwest, hyper and tonic take none
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Rust was read, and it logs through none: the `log` crate's macros take one finished message (as log4net does in C#; its `kv` values are an opt-in its backends mostly drop), `println!`/`eprintln!` are not loggers, or it makes no log call outside its tests and examples at all. Calls through `tracing` (`tracing::info!`, or `info!` imported from it) would be judged.
- 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.
Appendix A — Findings (grouped)
Critical — 36 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
- Boundary-crossing change coupling: tracker.rs ↔ details.rs crates/rustnet-core/src/network/tracker.rs:1
Serious — 207 finding(s)
- Hotspot: src/ui/tabs/details.rs src/ui/tabs/details.rs:1080
- Hotspot: src/ui/mod.rs src/ui/mod.rs:336
- Hotspot: crates/rustnet-core/src/network/types/connection.rs crates/rustnet-core/src/network/types/connection.rs:558
- Hotspot: crates/rustnet-core/src/network/tracker.rs crates/rustnet-core/src/network/tracker.rs:554
- Hotspot: src/ui/tabs/overview.rs src/ui/tabs/overview.rs:949
- Hotspot: crates/rustnet-core/src/network/merge.rs crates/rustnet-core/src/network/merge.rs:116
- Hotspot: src/app/enrichment.rs src/app/enrichment.rs:180
- Hotspot: src/ui/widgets/status_bar.rs src/ui/widgets/status_bar.rs:112
- Hotspot: src/app/capture.rs src/app/capture.rs:591
- Hotspot: src/ui/connection_table.rs src/ui/connection_table.rs:143
- Hotspot: src/tui.rs src/tui.rs:26
- Hotspot: src/ui/tabs/activity.rs src/ui/tabs/activity.rs:58
- Hotspot: crates/rustnet-core/src/network/types/protocol_info.rs crates/rustnet-core/src/network/types/protocol_info.rs:277
- Hotspot: src/bootstrap.rs src/bootstrap.rs:17
- Hotspot: crates/rustnet-core/src/network/dpi/mod.rs crates/rustnet-core/src/network/dpi/mod.rs:184
- Hotspot: crates/rustnet-sandbox/src/linux/mod.rs crates/rustnet-sandbox/src/linux/mod.rs:69
- Hotspot: crates/rustnet-core/src/network/dpi/quic/packet.rs crates/rustnet-core/src/network/dpi/quic/packet.rs:531
- Hotspot: crates/rustnet-sandbox/src/linux/landlock.rs crates/rustnet-sandbox/src/linux/landlock.rs:138
- Hotspot: src/app/logging.rs src/app/logging.rs:247
- Hotspot: crates/rustnet-core/src/network/filter.rs crates/rustnet-core/src/network/filter.rs:211
- Hotspot: src/ui/widgets/braille_graph.rs src/ui/widgets/braille_graph.rs:323
- Hotspot: src/ui/theme/derive.rs src/ui/theme/derive.rs:102
- Hotspot: crates/rustnet-capture/src/lib.rs crates/rustnet-capture/src/lib.rs:399
- Hotspot: crates/rustnet-core/src/network/dpi/quic/salvage.rs crates/rustnet-core/src/network/dpi/quic/salvage.rs:116
- Hotspot: src/ui/tabs/interfaces.rs src/ui/tabs/interfaces.rs:21
- rustnet_monitor::tui::run (cognitive 200) src/tui.rs:26
- rustnet_monitor::ui::tabs::details::draw_connection_details (cognitive 117) src/ui/tabs/details.rs:1080
- rustnet_monitor::ui::widgets::status_bar::view_hints (cognitive 62) src/ui/widgets/status_bar.rs:112
- rustnet_monitor::bootstrap::run (cognitive 55) src/bootstrap.rs:17
- rustnet_monitor::ui::tabs::overview::draw_stats_panel (cognitive 40) src/ui/tabs/overview.rs:949
- rustnet_monitor::ui::widgets::braille_graph::wave_panel (cognitive 31) src/ui/widgets/braille_graph.rs:323
- rustnet_monitor::app::pcapng_export::build_pcapng_comment (cognitive 26) src/app/pcapng_export.rs:330
- rustnet_monitor::ui::tabs::activity::draw_process_details (cognitive 25) src/ui/tabs/activity.rs:618
- rustnet_monitor::ui::widgets::tabs_bar::draw_tabs (cognitive 24) src/ui/widgets/tabs_bar.rs:87
- rustnet_monitor::ui::tabs::interfaces::draw_interface_stats (cognitive 23) src/ui/tabs/interfaces.rs:21
- rustnet_monitor::ui::tabs::activity::draw_process_table (cognitive 21) src/ui/tabs/activity.rs:871
- rustnet_monitor::ui::tabs::graph::draw_health_chart (cognitive 20) src/ui/tabs/graph.rs:578
- rustnet_monitor::app::unix_output::parent_dir (cognitive 19) src/app/unix_output.rs:112
- rustnet_monitor::ui::tabs::host::draw_dns_evidence (cognitive 19) src/ui/tabs/host.rs:195
- rustnet_monitor::app::logging::log_connection_event (cognitive 18) src/app/logging.rs:247
- rustnet_monitor::ui::connection_table::select_columns (cognitive 18) src/ui/connection_table.rs:143
- rustnet_monitor::ui::tabs::activity::draw_activity (cognitive 17) src/ui/tabs/activity.rs:225
- rustnet_monitor::headless::stream_json_lines (cognitive 16) src/headless/mod.rs:227
- rustnet_monitor::ui::sections::handle_key (cognitive 16) src/ui/sections.rs:83
- rustnet_monitor::ui::tabs::details::draw_traffic (cognitive 16) src/ui/tabs/details.rs:2213
- rustnet_monitor::ui::tabs::overview::draw_overview (cognitive 16) src/ui/tabs/overview.rs:424
- rustnet_core::network::dpi::quic::packet::scan_packet_frames (cognitive 57) crates/rustnet-core/src/network/dpi/quic/packet.rs:531
- rustnet_core::network::dpi::quic::salvage::find_hostname_candidates (cognitive 53) crates/rustnet-core/src/network/dpi/quic/salvage.rs:284
- rustnet_core::network::merge::analyze_tcp_segment (cognitive 53) crates/rustnet-core/src/network/merge.rs:116
- rustnet_core::network::dpi::quic::salvage::try_parse_unencrypted_crypto_frames (cognitive 48) crates/rustnet-core/src/network/dpi/quic/salvage.rs:11
- rustnet_core::network::dpi::quic::salvage::try_reconstruct_sni_from_fragments (cognitive 47) crates/rustnet-core/src/network/dpi/quic/salvage.rs:116
- rustnet_core::network::dpi::analyze_udp_packet (cognitive 37) crates/rustnet-core/src/network/dpi/mod.rs:184
- rustnet_core::network::dpi::tls_common::parse_extensions (cognitive 32) crates/rustnet-core/src/network/dpi/tls_common.rs:388
- rustnet_core::network::dpi::quic::packet::merge_quic_packet_info (cognitive 30) crates/rustnet-core/src/network/dpi/quic/packet.rs:117
- rustnet_core::network::merge::merge_quic_info (cognitive 30) crates/rustnet-core/src/network/merge.rs:737
- rustnet_core::network::merge::apply_packet (cognitive 27) crates/rustnet-core/src/network/merge.rs:326
- rustnet_core::network::dpi::analyze_tcp_packet (cognitive 25) crates/rustnet-core/src/network/dpi/mod.rs:60
- rustnet_core::network::dpi::mysql::analyze_mysql (cognitive 24) crates/rustnet-core/src/network/dpi/mysql.rs:9
- rustnet_core::network::dpi::tls_common::parse_supported_versions (cognitive 22) crates/rustnet-core/src/network/dpi/tls_common.rs:537
- rustnet_core::network::bogon::classify_v4 (cognitive 21) crates/rustnet-core/src/network/bogon.rs:64
- rustnet_core::network::dpi::ssh::analyze_ssh (cognitive 20) crates/rustnet-core/src/network/dpi/ssh.rs:6
- rustnet_core::network::dpi::dns::parse_question (cognitive 19) crates/rustnet-core/src/network/dpi/dns.rs:69
- rustnet_core::network::dpi::ftp::analyze_ftp (cognitive 19) crates/rustnet-core/src/network/dpi/ftp.rs:66
- rustnet_core::network::gateway::parse_route_dump (cognitive 19) crates/rustnet-core/src/network/gateway.rs:250
- rustnet_core::network::dpi::redis::analyze_redis (cognitive 18) crates/rustnet-core/src/network/dpi/redis.rs:6
- rustnet_core::network::protocol::tcp::parse_window_scale (cognitive 18) crates/rustnet-core/src/network/protocol/tcp.rs:56
- rustnet_core::network::dpi::dns::skip_dns_name (cognitive 17) crates/rustnet-core/src/network/dpi/dns.rs:30
- FileTooLong: tabs/details.rs src/ui/tabs/details.rs
- FileTooLong: tabs/overview.rs src/ui/tabs/overview.rs
- FileTooLong: types/protocol_info.rs crates/rustnet-core/src/network/types/protocol_info.rs
- FileTooLong: tabs/activity.rs src/ui/tabs/activity.rs
- FileTooLong: ui/state.rs src/ui/state.rs
- FileTooLong: app/capture.rs src/app/capture.rs
- FileTooLong: tabs/host.rs src/ui/tabs/host.rs
- FileTooLong: network/tracker.rs crates/rustnet-core/src/network/tracker.rs
- FileTooLong: network/process_activity.rs crates/rustnet-core/src/network/process_activity.rs
- FileTooLong: app/state.rs src/app/state.rs
- FileTooLong: tabs/graph.rs src/ui/tabs/graph.rs
- FileTooLong: ui/connection_table.rs src/ui/connection_table.rs
- FileTooLong: types/connection.rs crates/rustnet-core/src/network/types/connection.rs
- FileTooLong: windows/process.rs crates/rustnet-host/src/windows/process.rs
- FileTooLong: src/lib.rs crates/rustnet-host/src/lib.rs
- FileTooLong: network/merge.rs crates/rustnet-core/src/network/merge.rs
- FunctionTooLong: rustnet_monitor::ui::tabs::details::draw_connection_details src/ui/tabs/details.rs:1080
- FunctionTooLong: rustnet_monitor::ui::tabs::overview::draw_stats_panel src/ui/tabs/overview.rs:949
- FunctionTooLong: rustnet_monitor::tui::run src/tui.rs:26
- FunctionTooLong: rustnet_monitor::bootstrap::run src/bootstrap.rs:17
- FunctionTooLong: rustnet_monitor::cli::build_cli src/cli.rs:29
- FunctionTooLong: rustnet_monitor::ui::tabs::activity::draw_process_table src/ui/tabs/activity.rs:871
- FunctionTooLong: rustnet_monitor::ui::tabs::interfaces::draw_interface_stats src/ui/tabs/interfaces.rs:21
- FunctionTooLong: rustnet_monitor::ui::widgets::braille_graph::wave_panel src/ui/widgets/braille_graph.rs:323
- FunctionTooLong: rustnet_monitor::ui::tabs::details::draw_traffic src/ui/tabs/details.rs:2213
- FunctionTooLong: rustnet_monitor::ui::tabs::activity::draw_process_details src/ui/tabs/activity.rs:618
- FunctionTooLong: rustnet_core::network::dpi::quic::packet::scan_packet_frames crates/rustnet-core/src/network/dpi/quic/packet.rs:531
- FunctionTooLong: rustnet_monitor::ui::tabs::host::draw_sockets src/ui/tabs/host.rs:635
- FunctionTooLong: rustnet_monitor::ui::draw src/ui/mod.rs:336
- FunctionTooLong: rustnet_monitor::ui::widgets::status_bar::view_hints src/ui/widgets/status_bar.rs:112
- rustnet_core::network::dpi::analyze_udp_packet (cyclomatic 36) crates/rustnet-core/src/network/dpi/mod.rs:184
- rustnet_core::network::dpi::quic::packet::scan_packet_frames (cyclomatic 36) crates/rustnet-core/src/network/dpi/quic/packet.rs:531
- rustnet_core::network::dpi::quic::salvage::try_reconstruct_sni_from_fragments (cyclomatic 26) crates/rustnet-core/src/network/dpi/quic/salvage.rs:116
- rustnet_core::network::merge::analyze_tcp_segment (cyclomatic 26) crates/rustnet-core/src/network/merge.rs:116
- rustnet_core::network::dpi::analyze_tcp_packet (cyclomatic 24) crates/rustnet-core/src/network/dpi/mod.rs:60
- rustnet_core::network::bogon::classify_v4 (cyclomatic 22) crates/rustnet-core/src/network/bogon.rs:64
- rustnet_core::network::dpi::quic::salvage::try_parse_unencrypted_crypto_frames (cyclomatic 21) crates/rustnet-core/src/network/dpi/quic/salvage.rs:11
- rustnet_core::network::merge::merge_quic_info (cyclomatic 20) crates/rustnet-core/src/network/merge.rs:737
- rustnet_core::network::dpi::mysql::analyze_mysql (cyclomatic 19) crates/rustnet-core/src/network/dpi/mysql.rs:9
- rustnet_core::network::dpi::quic::salvage::find_hostname_candidates (cyclomatic 19) crates/rustnet-core/src/network/dpi/quic/salvage.rs:284
- rustnet_core::network::merge::apply_packet (cyclomatic 18) crates/rustnet-core/src/network/merge.rs:326
- rustnet_core::network::dpi::redis::analyze_redis (cyclomatic 16) crates/rustnet-core/src/network/dpi/redis.rs:6
- rustnet_core::network::dpi::tls_common::parse_extensions (cyclomatic 16) crates/rustnet-core/src/network/dpi/tls_common.rs:388
- rustnet_monitor::ui::tabs::details::draw_connection_details (cyclomatic 91) src/ui/tabs/details.rs:1080
- rustnet_monitor::tui::run (cyclomatic 68) src/tui.rs:26
- rustnet_monitor::bootstrap::run (cyclomatic 44) src/bootstrap.rs:17
- rustnet_monitor::ui::widgets::status_bar::view_hints (cyclomatic 39) src/ui/widgets/status_bar.rs:112
- rustnet_monitor::ui::tabs::overview::draw_stats_panel (cyclomatic 32) src/ui/tabs/overview.rs:949
- rustnet_monitor::ui::widgets::braille_graph::wave_panel (cyclomatic 24) src/ui/widgets/braille_graph.rs:323
- rustnet_monitor::app::pcapng_export::build_pcapng_comment (cyclomatic 21) src/app/pcapng_export.rs:330
- rustnet_monitor::ui::draw (cyclomatic 18) src/ui/mod.rs:336
- rustnet_monitor::ui::tabs::interfaces::draw_interface_stats (cyclomatic 18) src/ui/tabs/interfaces.rs:21
- rustnet_monitor::ui::tabs::activity::draw_process_table (cyclomatic 17) src/ui/tabs/activity.rs:871
- rustnet_monitor::ui::connection_table::select_columns (cyclomatic 16) src/ui/connection_table.rs:143
- MethodTooLong: App.run_process_enrichment src/app/enrichment.rs:180
- MethodTooLong: App.start_capture_thread src/app/capture.rs:591
- MethodTooLong: App.start_packet_processor src/app/capture.rs:867
- MethodTooLong: ConnectionSnapshot.from_connection src/headless/schema.rs:283
- MethodTooLong: OverviewTab.handle_key src/ui/tabs/overview.rs:86
- App::run_process_enrichment (cognitive 118) src/app/enrichment.rs:180
- App::start_capture_thread (cognitive 79) src/app/capture.rs:591
- App::start_packet_processor (cognitive 35) src/app/capture.rs:867
- App::start_interface_stats_thread (cognitive 16) src/app/sampling.rs:284
- TooManyFields: UiState src/ui/state.rs:544
- TooManyFields: Theme src/ui/theme/derive.rs:16
- TooManyFields: Connection crates/rustnet-core/src/network/types/connection.rs:182
- TooManyFields: App src/app/state.rs:68
- App::run_process_enrichment (cyclomatic 49) src/app/enrichment.rs:180
- App::start_capture_thread (cyclomatic 35) src/app/capture.rs:591
- App::start_packet_processor (cyclomatic 18) src/app/capture.rs:867
- TooManyMethods: App src/app/state.rs:68
- TooManyMethods: UiState src/ui/state.rs:544
- TooManyMethods: ConnectionTracker crates/rustnet-core/src/network/tracker.rs:348
- ClassTooLong: ConnectionTracker crates/rustnet-core/src/network/tracker.rs:348
- ClassTooLong: App src/app/state.rs:68
- ClassTooLong: Connection crates/rustnet-core/src/network/types/connection.rs:182
- Duplicated block (7 lines × 2) crates/rustnet-core/src/network/tracker.rs:610
- Duplicated block (7 lines × 2) crates/rustnet-host/src/linux/ebpf/loader.rs:221
- Duplicated block (7 lines × 2) src/ui/tabs/graph.rs:722
- Off the main sequence: rustnet-capture
- Off the main sequence: rustnet-sandbox
- Off the main sequence: rustnet-core
- rustnet_sandbox::linux::apply (cyclomatic 32) crates/rustnet-sandbox/src/linux/mod.rs:69
- rustnet_sandbox::linux::landlock::apply_landlock (cyclomatic 20) crates/rustnet-sandbox/src/linux/landlock.rs:138
- rustnet_sandbox::linux::apply (cognitive 46) crates/rustnet-sandbox/src/linux/mod.rs:69
- rustnet_sandbox::linux::landlock::apply_landlock (cognitive 20) crates/rustnet-sandbox/src/linux/landlock.rs:138
- DnsResolver::start_with_spawner (cognitive 36) crates/rustnet-core/src/network/dns.rs:214
- DnsResolver::stop (cognitive 18) crates/rustnet-core/src/network/dns.rs:427
- ProcessExitTracker::reconcile (cognitive 35) crates/rustnet-host/src/linux/lifecycle.rs:211
- ProcessExitTracker::scan_closed (cognitive 16) crates/rustnet-host/src/linux/lifecycle.rs:105
- rustnet_capture::find_capture_device (cognitive 29) crates/rustnet-capture/src/lib.rs:399
- rustnet_capture::setup_packet_capture (cognitive 23) crates/rustnet-capture/src/lib.rs:214
- LinuxProcessLookup::build_inode_map (cognitive 23) crates/rustnet-host/src/linux/process.rs:618
- LinuxProcessLookup::parse_and_map_content (cognitive 16) crates/rustnet-host/src/linux/process.rs:683
- REDACTED
- REDACTED
- Duplicated block (10 lines × 2) crates/rustnet-host/src/freebsd/process.rs:70
- Duplicated block (10 lines × 2) src/ui/tabs/details.rs:2312
- Connection::state (cyclomatic 52) crates/rustnet-core/src/network/types/connection.rs:558
- OverviewTab::handle_key (cyclomatic 31) src/ui/tabs/overview.rs:86
- ApplicationProtocol::fmt (cyclomatic 26) crates/rustnet-core/src/network/types/protocol_info.rs:277
- ConnectionFilter::matches (cyclomatic 25) crates/rustnet-core/src/network/filter.rs:211
- ConnectionTracker::measure_timings (cyclomatic 24) crates/rustnet-core/src/network/tracker.rs:554
- ActivityTab::handle_key (cyclomatic 24) src/ui/tabs/activity.rs:58
- Theme::resolve (cyclomatic 23) src/ui/theme/derive.rs:102
- ProcessExitTracker::reconcile (cyclomatic 21) crates/rustnet-host/src/linux/lifecycle.rs:211
- DnsResolver::start_with_spawner (cyclomatic 20) crates/rustnet-core/src/network/dns.rs:214
- DnsAnalyticsTracker::record_packet (cyclomatic 18) crates/rustnet-core/src/network/dns_analytics.rs:174
- rustnet_capture::find_capture_device (cyclomatic 17) crates/rustnet-capture/src/lib.rs:399
- pcap_enrich.create_pcapng (cyclomatic 16) scripts/pcap_enrich.py:251
- TodoComment crates/rustnet-sandbox/src/linux/landlock.rs:180
- Connection::state (cognitive 57) crates/rustnet-core/src/network/types/connection.rs:558
- Theme::resolve (cognitive 31) src/ui/theme/derive.rs:102
- pcap_enrich.create_pcapng (cognitive 30) scripts/pcap_enrich.py:251
- ConnectionTracker::measure_timings (cognitive 26) crates/rustnet-core/src/network/tracker.rs:554
- ActivityTab::handle_key (cognitive 26) src/ui/tabs/activity.rs:58
- UiState::get_selected_grouped_index (cognitive 23) src/ui/state.rs:1065
- DnsAnalyticsTracker::record_packet (cognitive 21) crates/rustnet-core/src/network/dns_analytics.rs:174
- ApplicationProtocol::fmt (cognitive 19) crates/rustnet-core/src/network/types/protocol_info.rs:277
- KubernetesSocketTable::build (cognitive 19) src/network/kubernetes.rs:360
- OverviewTab::handle_key (cognitive 19) src/ui/tabs/overview.rs:86
- CryptoFrameReassembler::add_fragment (cognitive 18) crates/rustnet-core/src/network/types/protocol_info.rs:1194
- PacketParser::parse_ipv6_extension_headers (cognitive 17) crates/rustnet-core/src/network/parser.rs:757
- SocketLifecycleTracker::scan_closed (cognitive 17) crates/rustnet-host/src/lifecycle/inventory.rs:40
- pcap_enrich.find_matching_connection (cognitive 17) scripts/pcap_enrich.py:105
- WindowsStatsProvider::get_all_stats (cognitive 16) crates/rustnet-core/src/network/interface_stats/windows.rs:39
- pcap_enrich.load_connections (cognitive 16) scripts/pcap_enrich.py:53
- pcap_enrich.print_table (cognitive 16) scripts/pcap_enrich.py:219
- TooManyFunctions: rustnet_monitor::ui::theme src/ui/theme/mod.rs:56
- Change coupling: details.rs ↔ help.rs src/ui/tabs/details.rs:1
- REDACTED
- REDACTED
- Members sharing a duplicated core (4 members, 50+ identical tokens) src/ui/theme/definitions.rs:459
- Duplicated block (12 lines × 3) src/ui/theme/definitions.rs:475
- Duplicated block (8–9 lines × 2) crates/rustnet-core/src/network/parser.rs:775
- Duplicated block (6 lines × 4) src/ui/theme/definitions.rs:468
- Duplicated block (5 lines × 2) crates/rustnet-core/src/network/dpi/quic/packet.rs:149
- Duplicated block (14 lines × 2) src/ui/tabs/activity.rs:307
- Duplicated block (11 lines × 2) src/ui/tabs/graph.rs:621
- Duplicated block (9 lines × 2) src/ui/tabs/graph.rs:294
Minor — 9 finding(s)
- Duplicated predicate crates/rustnet-sandbox/src/linux/landlock.rs:85
- Duplicated predicate crates/rustnet-host/src/linux/process.rs:709
- No ADRs found
- Projects may be oversized for their cohesion
- REDACTED
- REDACTED
- No ADRs
- Silent fallback default on Err crates/rustnet-core/src/network/neighbors.rs:180
- Subsumed condition operand crates/rustnet-host/src/linux/ebpf/loader.rs:702
Minor — 2 finding(s)
- Outdated: aes
- Outdated: zip
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-8043347a4f8d449c88b2aa1e5a964b80/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-8043347a4f8d449c88b2aa1e5a964b80/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude crates/rustnet-host/resources . | 32 | 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 . | 0 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 5 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |