Executive summary
smoltcp-rs/smoltcp meets our standard for a preview release, though we found no recorded design decisions and no architecture document or diagram. It scores 67 out of 100 and is rated Strong, and 17 of its 26 critical findings are security problems.
Maturity, at 51, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 11 points. Fixing the file that changes often and is hard to read comes next, worth about 3 points. Raising Maturity to 62 would lift the score to about 72.
Fourteen pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. One pipeline step installs packages that can change without warning, and nine parts of the code are no longer understood by anyone working on it. Pinning each tool to an exact version, pinning what the pipeline installs and having someone learn the forgotten files would close these risks. Giving the pull-request workflow read-only access would fix the pipeline that outsiders can trigger with write access, and limiting each secret to its own step would deal with the secret exposed to more of the pipeline than needed.
The product code is 48,673 lines, about €67,000 to rebuild.
If Maturity rose from 51 to 62, the lowest score rated Strong, the score would rise from 67 to about 72.
New since the last survey: 9 findings
- Churn × Complexity Hotspots · Hotspot: src/socket/tcp.rs src/socket/tcp.rs
- Knowledge Freshness · Orphaned knowledge src/socket/dhcpv4.rs
- Knowledge Freshness · Orphaned knowledge src/wire/ndiscoption.rs
- Knowledge Freshness · Orphaned knowledge src/wire/ipv6routing.rs
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
Fixed since the last survey: 2 findings
- Supply-chain Provenance & Signing REDACTED
- Supply-chain Provenance & Signing REDACTED
Rebuild cost: about €67,000 · Estimate
| Cost to rebuild | €22,000 to €110,000, for 371 to 1,177 hours of work, about 0.5 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.9 at a score of 67. 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: 48,673 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: which parts of the code depend on which
| uses → | 1 iface.rpl.parents | 2 socket.waker | 3 storage.packet_buffer | 4 time | 5 wire.pretty_print | 6 iface.interface.multicast | 7 iface.route | 8 phy.sys | 9 socket.dhcpv4 | 10 socket.tcp.congestion | 11 wire.ethernet | 12 iface.packet | 13 iface.slaac | 14 socket | 15 iface.socket_meta | 16 wire.dns | 17 wire.icmpv4 | 18 iface.socket_set | 19 wire.igmp | 20 iface.interface | 21 phy.fault_injector | 22 phy | 23 phy.fuzz_injector | 24 phy.loopback | 25 phy.pcap_writer | 26 phy.sys.raw_socket | 27 phy.tuntap_interface | 28 wire | 29 wire.ipv4 | 30 iface.fragmentation | 31 phy.raw_socket | 32 socket.dns | 33 socket.icmp | 34 socket.raw | 35 socket.tcp | 36 socket.udp | 37 wire.ipv6 | 38 wire.ndiscoption | 39 wire.ip | 40 wire.arp |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 iface.rpl.parents | ||||||||||||||||||||||||||||||||||||||||
| 2 socket.waker | ||||||||||||||||||||||||||||||||||||||||
| 3 storage.packet_buffer | ||||||||||||||||||||||||||||||||||||||||
| 4 time | ||||||||||||||||||||||||||||||||||||||||
| 5 wire.pretty_print | ||||||||||||||||||||||||||||||||||||||||
| 6 iface.interface.multicast | 1 | |||||||||||||||||||||||||||||||||||||||
| 7 iface.route | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 8 phy.sys | 1 | |||||||||||||||||||||||||||||||||||||||
| 9 socket.dhcpv4 | 1 | 6 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 10 socket.tcp.congestion | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 11 wire.ethernet | 2 | |||||||||||||||||||||||||||||||||||||||
| 12 iface.packet | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 13 iface.slaac | 4 | 1 | ||||||||||||||||||||||||||||||||||||||
| 14 socket | 2 | |||||||||||||||||||||||||||||||||||||||
| 15 iface.socket_meta | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 16 wire.dns | 2 | |||||||||||||||||||||||||||||||||||||||
| 17 wire.icmpv4 | 2 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 18 iface.socket_set | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 19 wire.igmp | 1 | 2 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 20 iface.interface | 3 | 1 | 2 | 3 | 1 | 2 | 1 | 4 | 3 | 4 | ||||||||||||||||||||||||||||||
| 21 phy.fault_injector | 5 | 2 | 3 | 4 | ||||||||||||||||||||||||||||||||||||
| 22 phy | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 23 phy.fuzz_injector | 1 | 3 | 4 | |||||||||||||||||||||||||||||||||||||
| 24 phy.loopback | 1 | 3 | 3 | |||||||||||||||||||||||||||||||||||||
| 25 phy.pcap_writer | 4 | 3 | 4 | |||||||||||||||||||||||||||||||||||||
| 26 phy.sys.raw_socket | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 27 phy.tuntap_interface | 1 | 3 | 3 | |||||||||||||||||||||||||||||||||||||
| 28 wire | 2 | |||||||||||||||||||||||||||||||||||||||
| 29 wire.ipv4 | 2 | 4 | 2 | 1 | 4 | |||||||||||||||||||||||||||||||||||
| 30 iface.fragmentation | 3 | 2 | ||||||||||||||||||||||||||||||||||||||
| 31 phy.raw_socket | 1 | 3 | 3 | 2 | ||||||||||||||||||||||||||||||||||||
| 32 socket.dns | 1 | 2 | 1 | 1 | 1 | 2 | 2 | |||||||||||||||||||||||||||||||||
| 33 socket.icmp | 1 | 1 | 1 | 1 | 3 | |||||||||||||||||||||||||||||||||||
| 34 socket.raw | 1 | 1 | 1 | 1 | 3 | |||||||||||||||||||||||||||||||||||
| 35 socket.tcp | 1 | 7 | 1 | 1 | 1 | 2 | 4 | |||||||||||||||||||||||||||||||||
| 36 socket.udp | 1 | 1 | 1 | 1 | 2 | 3 | ||||||||||||||||||||||||||||||||||
| 37 wire.ipv6 | 2 | 4 | 2 | 2 | 4 | |||||||||||||||||||||||||||||||||||
| 38 wire.ndiscoption | 2 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 39 wire.ip | 1 | 5 | 2 | 1 | 1 | 1 | 2 | 1 | 1 | |||||||||||||||||||||||||||||||
| 40 wire.arp | 2 | 2 | 1 |
6→28 iface.interface.multicast uses wire part of a loop✕
- Connections
- 1 pair of types, where a type in iface.interface.multicast uses a type in wire.
- The types involved
smoltcp.iface.interface.multicast.MulticastError→smoltcp.wire.Error
- Direction
- iface.interface.multicast uses wire, so a change to wire can break iface.interface.multicast, while a change to iface.interface.multicast can't break wire.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→4 iface.route uses time✕
- Connections
- 2 pairs of types, where a type in iface.route uses a type in time.
- The types involved
smoltcp.iface.route.Route→smoltcp.time.Instantsmoltcp.iface.route.Routes→smoltcp.time.Instant
- Direction
- iface.route uses time, so a change to time can break iface.route, while a change to iface.route can't break time.
- Position
- Below the diagonal: iface.route uses a module listed above it, which is the healthy direction.
7→28 iface.route uses wire part of a loop✕
- Connections
- 1 pair of types, where a type in iface.route uses a type in wire.
- The types involved
smoltcp.iface.route.RouteTableFull→smoltcp.wire.Error
- Direction
- iface.route uses wire, so a change to wire can break iface.route, while a change to iface.route can't break wire.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→4 phy.sys uses time✕
- Connections
- 1 pair of types, where a type in phy.sys uses a type in time.
- The types involved
smoltcp.phy.sys.sys$module→smoltcp.time.Duration
- Direction
- phy.sys uses time, so a change to time can break phy.sys, while a change to phy.sys can't break time.
- Position
- Below the diagonal: phy.sys uses a module listed above it, which is the healthy direction.
9→2 socket.dhcpv4 uses socket.waker✕
- Connections
- 1 pair of types, where a type in socket.dhcpv4 uses a type in socket.waker.
- The types involved
smoltcp.socket.dhcpv4.Socket→smoltcp.socket.waker.WakerRegistration
- Direction
- socket.dhcpv4 uses socket.waker, so a change to socket.waker can break socket.dhcpv4, while a change to socket.dhcpv4 can't break socket.waker.
- Position
- Below the diagonal: socket.dhcpv4 uses a module listed above it, which is the healthy direction.
9→4 socket.dhcpv4 uses time✕
- Connections
- 6 pairs of types, where a type in socket.dhcpv4 uses a type in time.
- The types involved
smoltcp.socket.dhcpv4.DiscoverState→smoltcp.time.Instantsmoltcp.socket.dhcpv4.RenewState→smoltcp.time.Instantsmoltcp.socket.dhcpv4.RequestState→smoltcp.time.Instantsmoltcp.socket.dhcpv4.RetryConfig→smoltcp.time.Durationsmoltcp.socket.dhcpv4.Socket→smoltcp.time.Durationsmoltcp.socket.dhcpv4.Socket→smoltcp.time.Instant
- Direction
- socket.dhcpv4 uses time, so a change to time can break socket.dhcpv4, while a change to socket.dhcpv4 can't break time.
- Position
- Below the diagonal: socket.dhcpv4 uses a module listed above it, which is the healthy direction.
9→14 socket.dhcpv4 uses socket part of a loop✕
- Connections
- 1 pair of types, where a type in socket.dhcpv4 uses a type in socket.
- The types involved
smoltcp.socket.dhcpv4.Socket→smoltcp.socket.PollAt
- Direction
- socket.dhcpv4 uses socket, so a change to socket can break socket.dhcpv4, while a change to socket.dhcpv4 can't break socket.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→20 socket.dhcpv4 uses iface.interface part of a loop✕
- Connections
- 1 pair of types, where a type in socket.dhcpv4 uses a type in iface.interface.
- The types involved
smoltcp.socket.dhcpv4.RenewState→smoltcp.iface.interface.Config
- Direction
- socket.dhcpv4 uses iface.interface, so a change to iface.interface can break socket.dhcpv4, while a change to socket.dhcpv4 can't break iface.interface.
- 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 socket.tcp.congestion uses time✕
- Connections
- 1 pair of types, where a type in socket.tcp.congestion uses a type in time.
- The types involved
smoltcp.socket.tcp.congestion.Controller→smoltcp.time.Instant
- Direction
- socket.tcp.congestion uses time, so a change to time can break socket.tcp.congestion, while a change to socket.tcp.congestion can't break time.
- Position
- Below the diagonal: socket.tcp.congestion uses a module listed above it, which is the healthy direction.
10→35 socket.tcp.congestion uses socket.tcp part of a loop✕
- Connections
- 1 pair of types, where a type in socket.tcp.congestion uses a type in socket.tcp.
- The types involved
smoltcp.socket.tcp.congestion.Controller→smoltcp.socket.tcp.RttEstimator
- Direction
- socket.tcp.congestion uses socket.tcp, so a change to socket.tcp can break socket.tcp.congestion, while a change to socket.tcp.congestion can't break socket.tcp.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→5 wire.ethernet uses wire.pretty_print✕
- Connections
- 2 pairs of types, where a type in wire.ethernet uses a type in wire.pretty_print.
- The types involved
smoltcp.wire.ethernet.Frame→smoltcp.wire.pretty_print.PrettyIndentsmoltcp.wire.ethernet.Frame→smoltcp.wire.pretty_print.PrettyPrint
- Direction
- wire.ethernet uses wire.pretty_print, so a change to wire.pretty_print can break wire.ethernet, while a change to wire.ethernet can't break wire.pretty_print.
- Position
- Below the diagonal: wire.ethernet uses a module listed above it, which is the healthy direction.
12→4 iface.packet uses time✕
- Connections
- 1 pair of types, where a type in iface.packet uses a type in time.
- The types involved
smoltcp.iface.packet.Packet→smoltcp.time.Duration
- Direction
- iface.packet uses time, so a change to time can break iface.packet, while a change to iface.packet can't break time.
- Position
- Below the diagonal: iface.packet uses a module listed above it, which is the healthy direction.
12→11 iface.packet uses wire.ethernet✕
- Connections
- 1 pair of types, where a type in iface.packet uses a type in wire.ethernet.
- The types involved
smoltcp.iface.packet.Packet→smoltcp.wire.ethernet.Address
- Direction
- iface.packet uses wire.ethernet, so a change to wire.ethernet can break iface.packet, while a change to iface.packet can't break wire.ethernet.
- Position
- Below the diagonal: iface.packet uses a module listed above it, which is the healthy direction.
12→22 iface.packet uses phy part of a loop✕
- Connections
- 1 pair of types, where a type in iface.packet uses a type in phy.
- The types involved
smoltcp.iface.packet.Packet→smoltcp.phy.DeviceCapabilities
- Direction
- iface.packet uses phy, so a change to phy can break iface.packet, while a change to iface.packet can't break phy.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→4 iface.slaac uses time✕
- Connections
- 4 pairs of types, where a type in iface.slaac uses a type in time.
- The types involved
smoltcp.iface.slaac.PrefixInfo→smoltcp.time.Instantsmoltcp.iface.slaac.Route→smoltcp.time.Instantsmoltcp.iface.slaac.Slaac→smoltcp.time.Durationsmoltcp.iface.slaac.Slaac→smoltcp.time.Instant
- Direction
- iface.slaac uses time, so a change to time can break iface.slaac, while a change to iface.slaac can't break time.
- Position
- Below the diagonal: iface.slaac uses a module listed above it, which is the healthy direction.
13→7 iface.slaac uses iface.route✕
- Connections
- 1 pair of types, where a type in iface.slaac uses a type in iface.route.
- The types involved
smoltcp.iface.slaac.Slaac→smoltcp.iface.route.Route
- Direction
- iface.slaac uses iface.route, so a change to iface.route can break iface.slaac, while a change to iface.slaac can't break iface.route.
- Position
- Below the diagonal: iface.slaac uses a module listed above it, which is the healthy direction.
14→9 socket uses socket.dhcpv4✕
- Connections
- 2 pairs of types, where a type in socket uses a type in socket.dhcpv4.
- The types involved
smoltcp.socket.AnySocket→smoltcp.socket.dhcpv4.Socketsmoltcp.socket.Socket→smoltcp.socket.dhcpv4.Socket
- Direction
- socket uses socket.dhcpv4, so a change to socket.dhcpv4 can break socket, while a change to socket can't break socket.dhcpv4.
- Position
- Below the diagonal: socket uses a module listed above it, which is the healthy direction.
15→4 iface.socket_meta uses time✕
- Connections
- 1 pair of types, where a type in iface.socket_meta uses a type in time.
- The types involved
smoltcp.iface.socket_meta.Meta→smoltcp.time.Instant
- Direction
- iface.socket_meta uses time, so a change to time can break iface.socket_meta, while a change to iface.socket_meta can't break time.
- Position
- Below the diagonal: iface.socket_meta uses a module listed above it, which is the healthy direction.
15→14 iface.socket_meta uses socket✕
- Connections
- 1 pair of types, where a type in iface.socket_meta uses a type in socket.
- The types involved
smoltcp.iface.socket_meta.Meta→smoltcp.socket.PollAt
- Direction
- iface.socket_meta uses socket, so a change to socket can break iface.socket_meta, while a change to iface.socket_meta can't break socket.
- Position
- Below the diagonal: iface.socket_meta uses a module listed above it, which is the healthy direction.
15→18 iface.socket_meta uses iface.socket_set part of a loop✕
- Connections
- 1 pair of types, where a type in iface.socket_meta uses a type in iface.socket_set.
- The types involved
smoltcp.iface.socket_meta.Meta→smoltcp.iface.socket_set.SocketHandle
- Direction
- iface.socket_meta uses iface.socket_set, so a change to iface.socket_set can break iface.socket_meta, while a change to iface.socket_meta can't break iface.socket_set.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→12 wire.dns uses iface.packet✕
- Connections
- 2 pairs of types, where a type in wire.dns uses a type in iface.packet.
- The types involved
smoltcp.wire.dns.Packet→smoltcp.iface.packet.Packetsmoltcp.wire.dns.Repr→smoltcp.iface.packet.Packet
- Direction
- wire.dns uses iface.packet, so a change to iface.packet can break wire.dns, while a change to wire.dns can't break iface.packet.
- Position
- Below the diagonal: wire.dns uses a module listed above it, which is the healthy direction.
17→5 wire.icmpv4 uses wire.pretty_print✕
- Connections
- 2 pairs of types, where a type in wire.icmpv4 uses a type in wire.pretty_print.
- The types involved
smoltcp.wire.icmpv4.Packet→smoltcp.wire.pretty_print.PrettyIndentsmoltcp.wire.icmpv4.Packet→smoltcp.wire.pretty_print.PrettyPrint
- Direction
- wire.icmpv4 uses wire.pretty_print, so a change to wire.pretty_print can break wire.icmpv4, while a change to wire.icmpv4 can't break wire.pretty_print.
- Position
- Below the diagonal: wire.icmpv4 uses a module listed above it, which is the healthy direction.
17→12 wire.icmpv4 uses iface.packet✕
- Connections
- 2 pairs of types, where a type in wire.icmpv4 uses a type in iface.packet.
- The types involved
smoltcp.wire.icmpv4.Packet→smoltcp.iface.packet.Packetsmoltcp.wire.icmpv4.Repr→smoltcp.iface.packet.Packet
- Direction
- wire.icmpv4 uses iface.packet, so a change to iface.packet can break wire.icmpv4, while a change to wire.icmpv4 can't break iface.packet.
- Position
- Below the diagonal: wire.icmpv4 uses a module listed above it, which is the healthy direction.
17→22 wire.icmpv4 uses phy part of a loop✕
- Connections
- 1 pair of types, where a type in wire.icmpv4 uses a type in phy.
- The types involved
smoltcp.wire.icmpv4.Repr→smoltcp.phy.ChecksumCapabilities
- Direction
- wire.icmpv4 uses phy, so a change to phy can break wire.icmpv4, while a change to wire.icmpv4 can't break phy.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→9 iface.socket_set uses socket.dhcpv4✕
- Connections
- 2 pairs of types, where a type in iface.socket_set uses a type in socket.dhcpv4.
- The types involved
smoltcp.iface.socket_set.Item→smoltcp.socket.dhcpv4.Socketsmoltcp.iface.socket_set.SocketSet→smoltcp.socket.dhcpv4.Socket
- Direction
- iface.socket_set uses socket.dhcpv4, so a change to socket.dhcpv4 can break iface.socket_set, while a change to iface.socket_set can't break socket.dhcpv4.
- Position
- Below the diagonal: iface.socket_set uses a module listed above it, which is the healthy direction.
18→15 iface.socket_set uses iface.socket_meta✕
- Connections
- 1 pair of types, where a type in iface.socket_set uses a type in iface.socket_meta.
- The types involved
smoltcp.iface.socket_set.Item→smoltcp.iface.socket_meta.Meta
- Direction
- iface.socket_set uses iface.socket_meta, so a change to iface.socket_meta can break iface.socket_set, while a change to iface.socket_set can't break iface.socket_meta.
- Position
- Below the diagonal: iface.socket_set uses a module listed above it, which is the healthy direction.
19→4 wire.igmp uses time✕
- Connections
- 1 pair of types, where a type in wire.igmp uses a type in time.
- The types involved
smoltcp.wire.igmp.igmp$module→smoltcp.time.Duration
- Direction
- wire.igmp uses time, so a change to time can break wire.igmp, while a change to wire.igmp can't break time.
- Position
- Below the diagonal: wire.igmp uses a module listed above it, which is the healthy direction.
19→5 wire.igmp uses wire.pretty_print✕
- Connections
- 2 pairs of types, where a type in wire.igmp uses a type in wire.pretty_print.
- The types involved
smoltcp.wire.igmp.Packet→smoltcp.wire.pretty_print.PrettyIndentsmoltcp.wire.igmp.Packet→smoltcp.wire.pretty_print.PrettyPrint
- Direction
- wire.igmp uses wire.pretty_print, so a change to wire.pretty_print can break wire.igmp, while a change to wire.igmp can't break wire.pretty_print.
- Position
- Below the diagonal: wire.igmp uses a module listed above it, which is the healthy direction.
19→12 wire.igmp uses iface.packet✕
- Connections
- 2 pairs of types, where a type in wire.igmp uses a type in iface.packet.
- The types involved
smoltcp.wire.igmp.Packet→smoltcp.iface.packet.Packetsmoltcp.wire.igmp.Repr→smoltcp.iface.packet.Packet
- Direction
- wire.igmp uses iface.packet, so a change to iface.packet can break wire.igmp, while a change to wire.igmp can't break iface.packet.
- Position
- Below the diagonal: wire.igmp uses a module listed above it, which is the healthy direction.
19→17 wire.igmp uses wire.icmpv4✕
- Connections
- 1 pair of types, where a type in wire.igmp uses a type in wire.icmpv4.
- The types involved
smoltcp.wire.igmp.Packet→smoltcp.wire.icmpv4.Message
- Direction
- wire.igmp uses wire.icmpv4, so a change to wire.icmpv4 can break wire.igmp, while a change to wire.igmp can't break wire.icmpv4.
- Position
- Below the diagonal: wire.igmp uses a module listed above it, which is the healthy direction.
20→4 iface.interface uses time✕
- Connections
- 3 pairs of types, where a type in iface.interface uses a type in time.
- The types involved
smoltcp.iface.interface.Interface→smoltcp.time.Durationsmoltcp.iface.interface.Interface→smoltcp.time.Instantsmoltcp.iface.interface.InterfaceInner→smoltcp.time.Instant
- Direction
- iface.interface uses time, so a change to time can break iface.interface, while a change to iface.interface can't break time.
- Position
- Below the diagonal: iface.interface uses a module listed above it, which is the healthy direction.
20→6 iface.interface uses iface.interface.multicast✕
- Connections
- 1 pair of types, where a type in iface.interface uses a type in iface.interface.multicast.
- The types involved
smoltcp.iface.interface.InterfaceInner→smoltcp.iface.interface.multicast.State
- Direction
- iface.interface uses iface.interface.multicast, so a change to iface.interface.multicast can break iface.interface, while a change to iface.interface can't break iface.interface.multicast.
- Position
- Below the diagonal: iface.interface uses a module listed above it, which is the healthy direction.
20→7 iface.interface uses iface.route✕
- Connections
- 2 pairs of types, where a type in iface.interface uses a type in iface.route.
- The types involved
smoltcp.iface.interface.Interface→smoltcp.iface.route.Routessmoltcp.iface.interface.InterfaceInner→smoltcp.iface.route.Routes
- Direction
- iface.interface uses iface.route, so a change to iface.route can break iface.interface, while a change to iface.interface can't break iface.route.
- Position
- Below the diagonal: iface.interface uses a module listed above it, which is the healthy direction.
20→12 iface.interface uses iface.packet✕
- Connections
- 3 pairs of types, where a type in iface.interface uses a type in iface.packet.
- The types involved
smoltcp.iface.interface.InterfaceInner→smoltcp.iface.packet.EthernetPacketsmoltcp.iface.interface.InterfaceInner→smoltcp.iface.packet.Packetsmoltcp.iface.interface.InterfaceInner→smoltcp.iface.packet.PacketV6
- Direction
- iface.interface uses iface.packet, so a change to iface.packet can break iface.interface, while a change to iface.interface can't break iface.packet.
- Position
- Below the diagonal: iface.interface uses a module listed above it, which is the healthy direction.
20→13 iface.interface uses iface.slaac✕
- Connections
- 1 pair of types, where a type in iface.interface uses a type in iface.slaac.
- The types involved
smoltcp.iface.interface.InterfaceInner→smoltcp.iface.slaac.Slaac
- Direction
- iface.interface uses iface.slaac, so a change to iface.slaac can break iface.interface, while a change to iface.interface can't break iface.slaac.
- Position
- Below the diagonal: iface.interface uses a module listed above it, which is the healthy direction.
20→18 iface.interface uses iface.socket_set✕
- Connections
- 2 pairs of types, where a type in iface.interface uses a type in iface.socket_set.
- The types involved
smoltcp.iface.interface.Interface→smoltcp.iface.socket_set.SocketSetsmoltcp.iface.interface.InterfaceInner→smoltcp.iface.socket_set.SocketSet
- Direction
- iface.interface uses iface.socket_set, so a change to iface.socket_set can break iface.interface, while a change to iface.interface can't break iface.socket_set.
- Position
- Below the diagonal: iface.interface uses a module listed above it, which is the healthy direction.
20→19 iface.interface uses wire.igmp✕
- Connections
- 1 pair of types, where a type in iface.interface uses a type in wire.igmp.
- The types involved
smoltcp.iface.interface.InterfaceInner→smoltcp.wire.igmp.IgmpVersion
- Direction
- iface.interface uses wire.igmp, so a change to wire.igmp can break iface.interface, while a change to iface.interface can't break wire.igmp.
- Position
- Below the diagonal: iface.interface uses a module listed above it, which is the healthy direction.
20→22 iface.interface uses phy part of a loop✕
- Connections
- 4 pairs of types, where a type in iface.interface uses a type in phy.
- The types involved
smoltcp.iface.interface.InterfaceInner→smoltcp.phy.ChecksumCapabilitiessmoltcp.iface.interface.InterfaceInner→smoltcp.phy.DeviceCapabilitiessmoltcp.iface.interface.InterfaceInner→smoltcp.phy.PacketMetasmoltcp.iface.interface.InterfaceInner→smoltcp.phy.SegmentationCapabilities
- Direction
- iface.interface uses phy, so a change to phy can break iface.interface, while a change to iface.interface can't break phy.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→28 iface.interface uses wire part of a loop✕
- Connections
- 3 pairs of types, where a type in iface.interface uses a type in wire.
- The types involved
smoltcp.iface.interface.Config→smoltcp.wire.HardwareAddresssmoltcp.iface.interface.Interface→smoltcp.wire.HardwareAddresssmoltcp.iface.interface.InterfaceInner→smoltcp.wire.HardwareAddress
- Direction
- iface.interface uses wire, so a change to wire can break iface.interface, while a change to iface.interface can't break wire.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→30 iface.interface uses iface.fragmentation part of a loop✕
- Connections
- 4 pairs of types, where a type in iface.interface uses a type in iface.fragmentation.
- The types involved
smoltcp.iface.interface.Interface→smoltcp.iface.fragmentation.Fragmentersmoltcp.iface.interface.Interface→smoltcp.iface.fragmentation.FragmentsBuffersmoltcp.iface.interface.InterfaceInner→smoltcp.iface.fragmentation.Fragmentersmoltcp.iface.interface.InterfaceInner→smoltcp.iface.fragmentation.FragmentsBuffer
- Direction
- iface.interface uses iface.fragmentation, so a change to iface.fragmentation can break iface.interface, while a change to iface.interface can't break iface.fragmentation.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
21→4 phy.fault_injector uses time✕
- Connections
- 5 pairs of types, where a type in phy.fault_injector uses a type in time.
- The types involved
smoltcp.phy.fault_injector.Config→smoltcp.time.Durationsmoltcp.phy.fault_injector.FaultInjector→smoltcp.time.Durationsmoltcp.phy.fault_injector.FaultInjector→smoltcp.time.Instantsmoltcp.phy.fault_injector.State→smoltcp.time.Instantsmoltcp.phy.fault_injector.TxToken→smoltcp.time.Instant
- Direction
- phy.fault_injector uses time, so a change to time can break phy.fault_injector, while a change to phy.fault_injector can't break time.
- Position
- Below the diagonal: phy.fault_injector uses a module listed above it, which is the healthy direction.
21→6 phy.fault_injector uses iface.interface.multicast✕
- Connections
- 2 pairs of types, where a type in phy.fault_injector uses a type in iface.interface.multicast.
- The types involved
smoltcp.phy.fault_injector.FaultInjector→smoltcp.iface.interface.multicast.Statesmoltcp.phy.fault_injector.TxToken→smoltcp.iface.interface.multicast.State
- Direction
- phy.fault_injector uses iface.interface.multicast, so a change to iface.interface.multicast can break phy.fault_injector, while a change to phy.fault_injector can't break iface.interface.multicast.
- Position
- Below the diagonal: phy.fault_injector uses a module listed above it, which is the healthy direction.
21→20 phy.fault_injector uses iface.interface✕
- Connections
- 3 pairs of types, where a type in phy.fault_injector uses a type in iface.interface.
- The types involved
smoltcp.phy.fault_injector.FaultInjector→smoltcp.iface.interface.Configsmoltcp.phy.fault_injector.State→smoltcp.iface.interface.Configsmoltcp.phy.fault_injector.TxToken→smoltcp.iface.interface.Config
- Direction
- phy.fault_injector uses iface.interface, so a change to iface.interface can break phy.fault_injector, while a change to phy.fault_injector can't break iface.interface.
- Position
- Below the diagonal: phy.fault_injector uses a module listed above it, which is the healthy direction.
21→22 phy.fault_injector uses phy part of a loop✕
- Connections
- 4 pairs of types, where a type in phy.fault_injector uses a type in phy.
- The types involved
smoltcp.phy.fault_injector.FaultInjector→smoltcp.phy.Devicesmoltcp.phy.fault_injector.FaultInjector→smoltcp.phy.DeviceCapabilitiessmoltcp.phy.fault_injector.RxToken→smoltcp.phy.PacketMetasmoltcp.phy.fault_injector.TxToken→smoltcp.phy.PacketMeta
- Direction
- phy.fault_injector uses phy, so a change to phy can break phy.fault_injector, while a change to phy.fault_injector can't break phy.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
22→4 phy uses time✕
- Connections
- 1 pair of types, where a type in phy uses a type in time.
- The types involved
smoltcp.phy.Device→smoltcp.time.Instant
- Direction
- phy uses time, so a change to time can break phy, while a change to phy can't break time.
- Position
- Below the diagonal: phy uses a module listed above it, which is the healthy direction.
22→21 phy uses phy.fault_injector✕
- Connections
- 1 pair of types, where a type in phy uses a type in phy.fault_injector.
- The types involved
smoltcp.phy.Device→smoltcp.phy.fault_injector.TxToken
- Direction
- phy uses phy.fault_injector, so a change to phy.fault_injector can break phy, while a change to phy can't break phy.fault_injector.
- Position
- Below the diagonal: phy uses a module listed above it, which is the healthy direction.
23→4 phy.fuzz_injector uses time✕
- Connections
- 1 pair of types, where a type in phy.fuzz_injector uses a type in time.
- The types involved
smoltcp.phy.fuzz_injector.FuzzInjector→smoltcp.time.Instant
- Direction
- phy.fuzz_injector uses time, so a change to time can break phy.fuzz_injector, while a change to phy.fuzz_injector can't break time.
- Position
- Below the diagonal: phy.fuzz_injector uses a module listed above it, which is the healthy direction.
23→21 phy.fuzz_injector uses phy.fault_injector✕
- Connections
- 3 pairs of types, where a type in phy.fuzz_injector uses a type in phy.fault_injector.
- The types involved
smoltcp.phy.fuzz_injector.FuzzInjector→smoltcp.phy.fault_injector.TxTokensmoltcp.phy.fuzz_injector.RxToken→smoltcp.phy.fault_injector.RxTokensmoltcp.phy.fuzz_injector.TxToken→smoltcp.phy.fault_injector.TxToken
- Direction
- phy.fuzz_injector uses phy.fault_injector, so a change to phy.fault_injector can break phy.fuzz_injector, while a change to phy.fuzz_injector can't break phy.fault_injector.
- Position
- Below the diagonal: phy.fuzz_injector uses a module listed above it, which is the healthy direction.
23→22 phy.fuzz_injector uses phy✕
- Connections
- 4 pairs of types, where a type in phy.fuzz_injector uses a type in phy.
- The types involved
smoltcp.phy.fuzz_injector.FuzzInjector→smoltcp.phy.Devicesmoltcp.phy.fuzz_injector.FuzzInjector→smoltcp.phy.DeviceCapabilitiessmoltcp.phy.fuzz_injector.RxToken→smoltcp.phy.PacketMetasmoltcp.phy.fuzz_injector.TxToken→smoltcp.phy.PacketMeta
- Direction
- phy.fuzz_injector uses phy, so a change to phy can break phy.fuzz_injector, while a change to phy.fuzz_injector can't break phy.
- Position
- Below the diagonal: phy.fuzz_injector uses a module listed above it, which is the healthy direction.
24→4 phy.loopback uses time✕
- Connections
- 1 pair of types, where a type in phy.loopback uses a type in time.
- The types involved
smoltcp.phy.loopback.Loopback→smoltcp.time.Instant
- Direction
- phy.loopback uses time, so a change to time can break phy.loopback, while a change to phy.loopback can't break time.
- Position
- Below the diagonal: phy.loopback uses a module listed above it, which is the healthy direction.
24→21 phy.loopback uses phy.fault_injector✕
- Connections
- 3 pairs of types, where a type in phy.loopback uses a type in phy.fault_injector.
- The types involved
smoltcp.phy.loopback.Loopback→smoltcp.phy.fault_injector.TxTokensmoltcp.phy.loopback.RxToken→smoltcp.phy.fault_injector.RxTokensmoltcp.phy.loopback.TxToken→smoltcp.phy.fault_injector.TxToken
- Direction
- phy.loopback uses phy.fault_injector, so a change to phy.fault_injector can break phy.loopback, while a change to phy.loopback can't break phy.fault_injector.
- Position
- Below the diagonal: phy.loopback uses a module listed above it, which is the healthy direction.
24→22 phy.loopback uses phy✕
- Connections
- 3 pairs of types, where a type in phy.loopback uses a type in phy.
- The types involved
smoltcp.phy.loopback.Loopback→smoltcp.phy.Devicesmoltcp.phy.loopback.Loopback→smoltcp.phy.DeviceCapabilitiessmoltcp.phy.loopback.Loopback→smoltcp.phy.Medium
- Direction
- phy.loopback uses phy, so a change to phy can break phy.loopback, while a change to phy.loopback can't break phy.
- Position
- Below the diagonal: phy.loopback uses a module listed above it, which is the healthy direction.
25→4 phy.pcap_writer uses time✕
- Connections
- 4 pairs of types, where a type in phy.pcap_writer uses a type in time.
- The types involved
smoltcp.phy.pcap_writer.PcapSink→smoltcp.time.Instantsmoltcp.phy.pcap_writer.PcapWriter→smoltcp.time.Instantsmoltcp.phy.pcap_writer.RxToken→smoltcp.time.Instantsmoltcp.phy.pcap_writer.TxToken→smoltcp.time.Instant
- Direction
- phy.pcap_writer uses time, so a change to time can break phy.pcap_writer, while a change to phy.pcap_writer can't break time.
- Position
- Below the diagonal: phy.pcap_writer uses a module listed above it, which is the healthy direction.
25→21 phy.pcap_writer uses phy.fault_injector✕
- Connections
- 3 pairs of types, where a type in phy.pcap_writer uses a type in phy.fault_injector.
- The types involved
smoltcp.phy.pcap_writer.PcapWriter→smoltcp.phy.fault_injector.TxTokensmoltcp.phy.pcap_writer.RxToken→smoltcp.phy.fault_injector.RxTokensmoltcp.phy.pcap_writer.TxToken→smoltcp.phy.fault_injector.TxToken
- Direction
- phy.pcap_writer uses phy.fault_injector, so a change to phy.fault_injector can break phy.pcap_writer, while a change to phy.pcap_writer can't break phy.fault_injector.
- Position
- Below the diagonal: phy.pcap_writer uses a module listed above it, which is the healthy direction.
25→22 phy.pcap_writer uses phy✕
- Connections
- 4 pairs of types, where a type in phy.pcap_writer uses a type in phy.
- The types involved
smoltcp.phy.pcap_writer.PcapWriter→smoltcp.phy.Devicesmoltcp.phy.pcap_writer.PcapWriter→smoltcp.phy.DeviceCapabilitiessmoltcp.phy.pcap_writer.RxToken→smoltcp.phy.PacketMetasmoltcp.phy.pcap_writer.TxToken→smoltcp.phy.PacketMeta
- Direction
- phy.pcap_writer uses phy, so a change to phy can break phy.pcap_writer, while a change to phy.pcap_writer can't break phy.
- Position
- Below the diagonal: phy.pcap_writer uses a module listed above it, which is the healthy direction.
26→8 phy.sys.raw_socket uses phy.sys✕
- Connections
- 1 pair of types, where a type in phy.sys.raw_socket uses a type in phy.sys.
- The types involved
smoltcp.phy.sys.raw_socket.RawSocketDesc→smoltcp.phy.sys.ifreq
- Direction
- phy.sys.raw_socket uses phy.sys, so a change to phy.sys can break phy.sys.raw_socket, while a change to phy.sys.raw_socket can't break phy.sys.
- Position
- Below the diagonal: phy.sys.raw_socket uses a module listed above it, which is the healthy direction.
26→22 phy.sys.raw_socket uses phy✕
- Connections
- 1 pair of types, where a type in phy.sys.raw_socket uses a type in phy.
- The types involved
smoltcp.phy.sys.raw_socket.RawSocketDesc→smoltcp.phy.Medium
- Direction
- phy.sys.raw_socket uses phy, so a change to phy can break phy.sys.raw_socket, while a change to phy.sys.raw_socket can't break phy.
- Position
- Below the diagonal: phy.sys.raw_socket uses a module listed above it, which is the healthy direction.
27→4 phy.tuntap_interface uses time✕
- Connections
- 1 pair of types, where a type in phy.tuntap_interface uses a type in time.
- The types involved
smoltcp.phy.tuntap_interface.TunTapInterface→smoltcp.time.Instant
- Direction
- phy.tuntap_interface uses time, so a change to time can break phy.tuntap_interface, while a change to phy.tuntap_interface can't break time.
- Position
- Below the diagonal: phy.tuntap_interface uses a module listed above it, which is the healthy direction.
27→21 phy.tuntap_interface uses phy.fault_injector✕
- Connections
- 3 pairs of types, where a type in phy.tuntap_interface uses a type in phy.fault_injector.
- The types involved
smoltcp.phy.tuntap_interface.RxToken→smoltcp.phy.fault_injector.RxTokensmoltcp.phy.tuntap_interface.TunTapInterface→smoltcp.phy.fault_injector.TxTokensmoltcp.phy.tuntap_interface.TxToken→smoltcp.phy.fault_injector.TxToken
- Direction
- phy.tuntap_interface uses phy.fault_injector, so a change to phy.fault_injector can break phy.tuntap_interface, while a change to phy.tuntap_interface can't break phy.fault_injector.
- Position
- Below the diagonal: phy.tuntap_interface uses a module listed above it, which is the healthy direction.
27→22 phy.tuntap_interface uses phy✕
- Connections
- 3 pairs of types, where a type in phy.tuntap_interface uses a type in phy.
- The types involved
smoltcp.phy.tuntap_interface.TunTapInterface→smoltcp.phy.Devicesmoltcp.phy.tuntap_interface.TunTapInterface→smoltcp.phy.DeviceCapabilitiessmoltcp.phy.tuntap_interface.TunTapInterface→smoltcp.phy.Medium
- Direction
- phy.tuntap_interface uses phy, so a change to phy can break phy.tuntap_interface, while a change to phy.tuntap_interface can't break phy.
- Position
- Below the diagonal: phy.tuntap_interface uses a module listed above it, which is the healthy direction.
28→22 wire uses phy✕
- Connections
- 2 pairs of types, where a type in wire uses a type in phy.
- The types involved
smoltcp.wire.HardwareAddress→smoltcp.phy.Mediumsmoltcp.wire.RawHardwareAddress→smoltcp.phy.Medium
- Direction
- wire uses phy, so a change to phy can break wire, while a change to wire can't break phy.
- Position
- Below the diagonal: wire uses a module listed above it, which is the healthy direction.
29→5 wire.ipv4 uses wire.pretty_print✕
- Connections
- 2 pairs of types, where a type in wire.ipv4 uses a type in wire.pretty_print.
- The types involved
smoltcp.wire.ipv4.Packet→smoltcp.wire.pretty_print.PrettyIndentsmoltcp.wire.ipv4.Packet→smoltcp.wire.pretty_print.PrettyPrint
- Direction
- wire.ipv4 uses wire.pretty_print, so a change to wire.pretty_print can break wire.ipv4, while a change to wire.ipv4 can't break wire.pretty_print.
- Position
- Below the diagonal: wire.ipv4 uses a module listed above it, which is the healthy direction.
29→11 wire.ipv4 uses wire.ethernet✕
- Connections
- 4 pairs of types, where a type in wire.ipv4 uses a type in wire.ethernet.
- The types involved
smoltcp.wire.ipv4.Cidr→smoltcp.wire.ethernet.Addresssmoltcp.wire.ipv4.Key→smoltcp.wire.ethernet.Addresssmoltcp.wire.ipv4.Packet→smoltcp.wire.ethernet.Addresssmoltcp.wire.ipv4.Repr→smoltcp.wire.ethernet.Address
- Direction
- wire.ipv4 uses wire.ethernet, so a change to wire.ethernet can break wire.ipv4, while a change to wire.ipv4 can't break wire.ethernet.
- Position
- Below the diagonal: wire.ipv4 uses a module listed above it, which is the healthy direction.
29→12 wire.ipv4 uses iface.packet✕
- Connections
- 2 pairs of types, where a type in wire.ipv4 uses a type in iface.packet.
- The types involved
smoltcp.wire.ipv4.Packet→smoltcp.iface.packet.Packetsmoltcp.wire.ipv4.Repr→smoltcp.iface.packet.Packet
- Direction
- wire.ipv4 uses iface.packet, so a change to iface.packet can break wire.ipv4, while a change to wire.ipv4 can't break iface.packet.
- Position
- Below the diagonal: wire.ipv4 uses a module listed above it, which is the healthy direction.
29→22 wire.ipv4 uses phy✕
- Connections
- 1 pair of types, where a type in wire.ipv4 uses a type in phy.
- The types involved
smoltcp.wire.ipv4.Repr→smoltcp.phy.ChecksumCapabilities
- Direction
- wire.ipv4 uses phy, so a change to phy can break wire.ipv4, while a change to wire.ipv4 can't break phy.
- Position
- Below the diagonal: wire.ipv4 uses a module listed above it, which is the healthy direction.
29→39 wire.ipv4 uses wire.ip part of a loop✕
- Connections
- 4 pairs of types, where a type in wire.ipv4 uses a type in wire.ip.
- The types involved
smoltcp.wire.ipv4.Cidr→smoltcp.wire.ip.Cidrsmoltcp.wire.ipv4.Key→smoltcp.wire.ip.Protocolsmoltcp.wire.ipv4.Packet→smoltcp.wire.ip.Protocolsmoltcp.wire.ipv4.Repr→smoltcp.wire.ip.Protocol
- Direction
- wire.ipv4 uses wire.ip, so a change to wire.ip can break wire.ipv4, while a change to wire.ipv4 can't break wire.ip.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
30→4 iface.fragmentation uses time✕
- Connections
- 3 pairs of types, where a type in iface.fragmentation uses a type in time.
- The types involved
smoltcp.iface.fragmentation.FragmentsBuffer→smoltcp.time.Durationsmoltcp.iface.fragmentation.PacketAssembler→smoltcp.time.Instantsmoltcp.iface.fragmentation.PacketAssemblerSet→smoltcp.time.Instant
- Direction
- iface.fragmentation uses time, so a change to time can break iface.fragmentation, while a change to iface.fragmentation can't break time.
- Position
- Below the diagonal: iface.fragmentation uses a module listed above it, which is the healthy direction.
30→28 iface.fragmentation uses wire✕
- Connections
- 2 pairs of types, where a type in iface.fragmentation uses a type in wire.
- The types involved
smoltcp.iface.fragmentation.AssemblerError→smoltcp.wire.Errorsmoltcp.iface.fragmentation.AssemblerFullError→smoltcp.wire.Error
- Direction
- iface.fragmentation uses wire, so a change to wire can break iface.fragmentation, while a change to iface.fragmentation can't break wire.
- Position
- Below the diagonal: iface.fragmentation uses a module listed above it, which is the healthy direction.
31→4 phy.raw_socket uses time✕
- Connections
- 1 pair of types, where a type in phy.raw_socket uses a type in time.
- The types involved
smoltcp.phy.raw_socket.RawSocket→smoltcp.time.Instant
- Direction
- phy.raw_socket uses time, so a change to time can break phy.raw_socket, while a change to phy.raw_socket can't break time.
- Position
- Below the diagonal: phy.raw_socket uses a module listed above it, which is the healthy direction.
31→21 phy.raw_socket uses phy.fault_injector✕
- Connections
- 3 pairs of types, where a type in phy.raw_socket uses a type in phy.fault_injector.
- The types involved
smoltcp.phy.raw_socket.RawSocket→smoltcp.phy.fault_injector.TxTokensmoltcp.phy.raw_socket.RxToken→smoltcp.phy.fault_injector.RxTokensmoltcp.phy.raw_socket.TxToken→smoltcp.phy.fault_injector.TxToken
- Direction
- phy.raw_socket uses phy.fault_injector, so a change to phy.fault_injector can break phy.raw_socket, while a change to phy.raw_socket can't break phy.fault_injector.
- Position
- Below the diagonal: phy.raw_socket uses a module listed above it, which is the healthy direction.
31→22 phy.raw_socket uses phy✕
- Connections
- 3 pairs of types, where a type in phy.raw_socket uses a type in phy.
- The types involved
smoltcp.phy.raw_socket.RawSocket→smoltcp.phy.Devicesmoltcp.phy.raw_socket.RawSocket→smoltcp.phy.DeviceCapabilitiessmoltcp.phy.raw_socket.RawSocket→smoltcp.phy.Medium
- Direction
- phy.raw_socket uses phy, so a change to phy can break phy.raw_socket, while a change to phy.raw_socket can't break phy.
- Position
- Below the diagonal: phy.raw_socket uses a module listed above it, which is the healthy direction.
31→26 phy.raw_socket uses phy.sys.raw_socket✕
- Connections
- 2 pairs of types, where a type in phy.raw_socket uses a type in phy.sys.raw_socket.
- The types involved
smoltcp.phy.raw_socket.RawSocket→smoltcp.phy.sys.raw_socket.RawSocketDescsmoltcp.phy.raw_socket.TxToken→smoltcp.phy.sys.raw_socket.RawSocketDesc
- Direction
- phy.raw_socket uses phy.sys.raw_socket, so a change to phy.sys.raw_socket can break phy.raw_socket, while a change to phy.raw_socket can't break phy.sys.raw_socket.
- Position
- Below the diagonal: phy.raw_socket uses a module listed above it, which is the healthy direction.
32→2 socket.dns uses socket.waker✕
- Connections
- 1 pair of types, where a type in socket.dns uses a type in socket.waker.
- The types involved
smoltcp.socket.dns.DnsQuery→smoltcp.socket.waker.WakerRegistration
- Direction
- socket.dns uses socket.waker, so a change to socket.waker can break socket.dns, while a change to socket.dns can't break socket.waker.
- Position
- Below the diagonal: socket.dns uses a module listed above it, which is the healthy direction.
32→4 socket.dns uses time✕
- Connections
- 2 pairs of types, where a type in socket.dns uses a type in time.
- The types involved
smoltcp.socket.dns.PendingQuery→smoltcp.time.Durationsmoltcp.socket.dns.PendingQuery→smoltcp.time.Instant
- Direction
- socket.dns uses time, so a change to time can break socket.dns, while a change to socket.dns can't break time.
- Position
- Below the diagonal: socket.dns uses a module listed above it, which is the healthy direction.
32→6 socket.dns uses iface.interface.multicast✕
- Connections
- 1 pair of types, where a type in socket.dns uses a type in iface.interface.multicast.
- The types involved
smoltcp.socket.dns.DnsQuery→smoltcp.iface.interface.multicast.State
- Direction
- socket.dns uses iface.interface.multicast, so a change to iface.interface.multicast can break socket.dns, while a change to socket.dns can't break iface.interface.multicast.
- Position
- Below the diagonal: socket.dns uses a module listed above it, which is the healthy direction.
32→9 socket.dns uses socket.dhcpv4✕
- Connections
- 1 pair of types, where a type in socket.dns uses a type in socket.dhcpv4.
- The types involved
smoltcp.socket.dns.Socket→smoltcp.socket.dhcpv4.Socket
- Direction
- socket.dns uses socket.dhcpv4, so a change to socket.dhcpv4 can break socket.dns, while a change to socket.dns can't break socket.dhcpv4.
- Position
- Below the diagonal: socket.dns uses a module listed above it, which is the healthy direction.
32→14 socket.dns uses socket✕
- Connections
- 1 pair of types, where a type in socket.dns uses a type in socket.
- The types involved
smoltcp.socket.dns.Socket→smoltcp.socket.PollAt
- Direction
- socket.dns uses socket, so a change to socket can break socket.dns, while a change to socket.dns can't break socket.
- Position
- Below the diagonal: socket.dns uses a module listed above it, which is the healthy direction.
32→16 socket.dns uses wire.dns✕
- Connections
- 2 pairs of types, where a type in socket.dns uses a type in wire.dns.
- The types involved
smoltcp.socket.dns.PendingQuery→smoltcp.wire.dns.Typesmoltcp.socket.dns.Socket→smoltcp.wire.dns.Type
- Direction
- socket.dns uses wire.dns, so a change to wire.dns can break socket.dns, while a change to socket.dns can't break wire.dns.
- Position
- Below the diagonal: socket.dns uses a module listed above it, which is the healthy direction.
32→28 socket.dns uses wire✕
- Connections
- 2 pairs of types, where a type in socket.dns uses a type in wire.
- The types involved
smoltcp.socket.dns.GetQueryResultError→smoltcp.wire.Errorsmoltcp.socket.dns.StartQueryError→smoltcp.wire.Error
- Direction
- socket.dns uses wire, so a change to wire can break socket.dns, while a change to socket.dns can't break wire.
- Position
- Below the diagonal: socket.dns uses a module listed above it, which is the healthy direction.
33→2 socket.icmp uses socket.waker✕
- Connections
- 1 pair of types, where a type in socket.icmp uses a type in socket.waker.
- The types involved
smoltcp.socket.icmp.Socket→smoltcp.socket.waker.WakerRegistration
- Direction
- socket.icmp uses socket.waker, so a change to socket.waker can break socket.icmp, while a change to socket.icmp can't break socket.waker.
- Position
- Below the diagonal: socket.icmp uses a module listed above it, which is the healthy direction.
33→3 socket.icmp uses storage.packet_buffer✕
- Connections
- 1 pair of types, where a type in socket.icmp uses a type in storage.packet_buffer.
- The types involved
smoltcp.socket.icmp.Socket→smoltcp.storage.packet_buffer.PacketBuffer
- Direction
- socket.icmp uses storage.packet_buffer, so a change to storage.packet_buffer can break socket.icmp, while a change to socket.icmp can't break storage.packet_buffer.
- Position
- Below the diagonal: socket.icmp uses a module listed above it, which is the healthy direction.
33→9 socket.icmp uses socket.dhcpv4✕
- Connections
- 1 pair of types, where a type in socket.icmp uses a type in socket.dhcpv4.
- The types involved
smoltcp.socket.icmp.Socket→smoltcp.socket.dhcpv4.Socket
- Direction
- socket.icmp uses socket.dhcpv4, so a change to socket.dhcpv4 can break socket.icmp, while a change to socket.icmp can't break socket.dhcpv4.
- Position
- Below the diagonal: socket.icmp uses a module listed above it, which is the healthy direction.
33→14 socket.icmp uses socket✕
- Connections
- 1 pair of types, where a type in socket.icmp uses a type in socket.
- The types involved
smoltcp.socket.icmp.Socket→smoltcp.socket.PollAt
- Direction
- socket.icmp uses socket, so a change to socket can break socket.icmp, while a change to socket.icmp can't break socket.
- Position
- Below the diagonal: socket.icmp uses a module listed above it, which is the healthy direction.
33→28 socket.icmp uses wire✕
- Connections
- 3 pairs of types, where a type in socket.icmp uses a type in wire.
- The types involved
smoltcp.socket.icmp.BindError→smoltcp.wire.Errorsmoltcp.socket.icmp.RecvError→smoltcp.wire.Errorsmoltcp.socket.icmp.SendError→smoltcp.wire.Error
- Direction
- socket.icmp uses wire, so a change to wire can break socket.icmp, while a change to socket.icmp can't break wire.
- Position
- Below the diagonal: socket.icmp uses a module listed above it, which is the healthy direction.
34→2 socket.raw uses socket.waker✕
- Connections
- 1 pair of types, where a type in socket.raw uses a type in socket.waker.
- The types involved
smoltcp.socket.raw.Socket→smoltcp.socket.waker.WakerRegistration
- Direction
- socket.raw uses socket.waker, so a change to socket.waker can break socket.raw, while a change to socket.raw can't break socket.waker.
- Position
- Below the diagonal: socket.raw uses a module listed above it, which is the healthy direction.
34→3 socket.raw uses storage.packet_buffer✕
- Connections
- 1 pair of types, where a type in socket.raw uses a type in storage.packet_buffer.
- The types involved
smoltcp.socket.raw.Socket→smoltcp.storage.packet_buffer.PacketBuffer
- Direction
- socket.raw uses storage.packet_buffer, so a change to storage.packet_buffer can break socket.raw, while a change to socket.raw can't break storage.packet_buffer.
- Position
- Below the diagonal: socket.raw uses a module listed above it, which is the healthy direction.
34→9 socket.raw uses socket.dhcpv4✕
- Connections
- 1 pair of types, where a type in socket.raw uses a type in socket.dhcpv4.
- The types involved
smoltcp.socket.raw.Socket→smoltcp.socket.dhcpv4.Socket
- Direction
- socket.raw uses socket.dhcpv4, so a change to socket.dhcpv4 can break socket.raw, while a change to socket.raw can't break socket.dhcpv4.
- Position
- Below the diagonal: socket.raw uses a module listed above it, which is the healthy direction.
34→14 socket.raw uses socket✕
- Connections
- 1 pair of types, where a type in socket.raw uses a type in socket.
- The types involved
smoltcp.socket.raw.Socket→smoltcp.socket.PollAt
- Direction
- socket.raw uses socket, so a change to socket can break socket.raw, while a change to socket.raw can't break socket.
- Position
- Below the diagonal: socket.raw uses a module listed above it, which is the healthy direction.
34→28 socket.raw uses wire✕
- Connections
- 3 pairs of types, where a type in socket.raw uses a type in wire.
- The types involved
smoltcp.socket.raw.BindError→smoltcp.wire.Errorsmoltcp.socket.raw.RecvError→smoltcp.wire.Errorsmoltcp.socket.raw.SendError→smoltcp.wire.Error
- Direction
- socket.raw uses wire, so a change to wire can break socket.raw, while a change to socket.raw can't break wire.
- Position
- Below the diagonal: socket.raw uses a module listed above it, which is the healthy direction.
35→2 socket.tcp uses socket.waker✕
- Connections
- 1 pair of types, where a type in socket.tcp uses a type in socket.waker.
- The types involved
smoltcp.socket.tcp.Socket→smoltcp.socket.waker.WakerRegistration
- Direction
- socket.tcp uses socket.waker, so a change to socket.waker can break socket.tcp, while a change to socket.tcp can't break socket.waker.
- Position
- Below the diagonal: socket.tcp uses a module listed above it, which is the healthy direction.
35→4 socket.tcp uses time✕
- Connections
- 7 pairs of types, where a type in socket.tcp uses a type in time.
- The types involved
smoltcp.socket.tcp.RttEstimator→smoltcp.time.Durationsmoltcp.socket.tcp.RttEstimator→smoltcp.time.Instantsmoltcp.socket.tcp.Socket→smoltcp.time.Durationsmoltcp.socket.tcp.Socket→smoltcp.time.Instantsmoltcp.socket.tcp.Timer→smoltcp.time.Durationsmoltcp.socket.tcp.Timer→smoltcp.time.Instantsmoltcp.socket.tcp.tcp$module→smoltcp.time.Duration
- Direction
- socket.tcp uses time, so a change to time can break socket.tcp, while a change to socket.tcp can't break time.
- Position
- Below the diagonal: socket.tcp uses a module listed above it, which is the healthy direction.
35→6 socket.tcp uses iface.interface.multicast✕
- Connections
- 1 pair of types, where a type in socket.tcp uses a type in iface.interface.multicast.
- The types involved
smoltcp.socket.tcp.Socket→smoltcp.iface.interface.multicast.State
- Direction
- socket.tcp uses iface.interface.multicast, so a change to iface.interface.multicast can break socket.tcp, while a change to socket.tcp can't break iface.interface.multicast.
- Position
- Below the diagonal: socket.tcp uses a module listed above it, which is the healthy direction.
35→9 socket.tcp uses socket.dhcpv4✕
- Connections
- 1 pair of types, where a type in socket.tcp uses a type in socket.dhcpv4.
- The types involved
smoltcp.socket.tcp.Socket→smoltcp.socket.dhcpv4.Socket
- Direction
- socket.tcp uses socket.dhcpv4, so a change to socket.dhcpv4 can break socket.tcp, while a change to socket.tcp can't break socket.dhcpv4.
- Position
- Below the diagonal: socket.tcp uses a module listed above it, which is the healthy direction.
35→10 socket.tcp uses socket.tcp.congestion✕
- Connections
- 1 pair of types, where a type in socket.tcp uses a type in socket.tcp.congestion.
- The types involved
smoltcp.socket.tcp.Socket→smoltcp.socket.tcp.congestion.AnyController
- Direction
- socket.tcp uses socket.tcp.congestion, so a change to socket.tcp.congestion can break socket.tcp, while a change to socket.tcp can't break socket.tcp.congestion.
- Position
- Below the diagonal: socket.tcp uses a module listed above it, which is the healthy direction.
35→14 socket.tcp uses socket✕
- Connections
- 2 pairs of types, where a type in socket.tcp uses a type in socket.
- The types involved
smoltcp.socket.tcp.Socket→smoltcp.socket.PollAtsmoltcp.socket.tcp.Timer→smoltcp.socket.PollAt
- Direction
- socket.tcp uses socket, so a change to socket can break socket.tcp, while a change to socket.tcp can't break socket.
- Position
- Below the diagonal: socket.tcp uses a module listed above it, which is the healthy direction.
35→28 socket.tcp uses wire✕
- Connections
- 4 pairs of types, where a type in socket.tcp uses a type in wire.
- The types involved
smoltcp.socket.tcp.ConnectError→smoltcp.wire.Errorsmoltcp.socket.tcp.ListenError→smoltcp.wire.Errorsmoltcp.socket.tcp.RecvError→smoltcp.wire.Errorsmoltcp.socket.tcp.SendError→smoltcp.wire.Error
- Direction
- socket.tcp uses wire, so a change to wire can break socket.tcp, while a change to socket.tcp can't break wire.
- Position
- Below the diagonal: socket.tcp uses a module listed above it, which is the healthy direction.
36→2 socket.udp uses socket.waker✕
- Connections
- 1 pair of types, where a type in socket.udp uses a type in socket.waker.
- The types involved
smoltcp.socket.udp.Socket→smoltcp.socket.waker.WakerRegistration
- Direction
- socket.udp uses socket.waker, so a change to socket.waker can break socket.udp, while a change to socket.udp can't break socket.waker.
- Position
- Below the diagonal: socket.udp uses a module listed above it, which is the healthy direction.
36→3 socket.udp uses storage.packet_buffer✕
- Connections
- 1 pair of types, where a type in socket.udp uses a type in storage.packet_buffer.
- The types involved
smoltcp.socket.udp.Socket→smoltcp.storage.packet_buffer.PacketBuffer
- Direction
- socket.udp uses storage.packet_buffer, so a change to storage.packet_buffer can break socket.udp, while a change to socket.udp can't break storage.packet_buffer.
- Position
- Below the diagonal: socket.udp uses a module listed above it, which is the healthy direction.
36→9 socket.udp uses socket.dhcpv4✕
- Connections
- 1 pair of types, where a type in socket.udp uses a type in socket.dhcpv4.
- The types involved
smoltcp.socket.udp.Socket→smoltcp.socket.dhcpv4.Socket
- Direction
- socket.udp uses socket.dhcpv4, so a change to socket.dhcpv4 can break socket.udp, while a change to socket.udp can't break socket.dhcpv4.
- Position
- Below the diagonal: socket.udp uses a module listed above it, which is the healthy direction.
36→14 socket.udp uses socket✕
- Connections
- 1 pair of types, where a type in socket.udp uses a type in socket.
- The types involved
smoltcp.socket.udp.Socket→smoltcp.socket.PollAt
- Direction
- socket.udp uses socket, so a change to socket can break socket.udp, while a change to socket.udp can't break socket.
- Position
- Below the diagonal: socket.udp uses a module listed above it, which is the healthy direction.
36→22 socket.udp uses phy✕
- Connections
- 2 pairs of types, where a type in socket.udp uses a type in phy.
- The types involved
smoltcp.socket.udp.Socket→smoltcp.phy.PacketMetasmoltcp.socket.udp.UdpMetadata→smoltcp.phy.PacketMeta
- Direction
- socket.udp uses phy, so a change to phy can break socket.udp, while a change to socket.udp can't break phy.
- Position
- Below the diagonal: socket.udp uses a module listed above it, which is the healthy direction.
36→28 socket.udp uses wire✕
- Connections
- 3 pairs of types, where a type in socket.udp uses a type in wire.
- The types involved
smoltcp.socket.udp.BindError→smoltcp.wire.Errorsmoltcp.socket.udp.RecvError→smoltcp.wire.Errorsmoltcp.socket.udp.SendError→smoltcp.wire.Error
- Direction
- socket.udp uses wire, so a change to wire can break socket.udp, while a change to socket.udp can't break wire.
- Position
- Below the diagonal: socket.udp uses a module listed above it, which is the healthy direction.
37→5 wire.ipv6 uses wire.pretty_print✕
- Connections
- 2 pairs of types, where a type in wire.ipv6 uses a type in wire.pretty_print.
- The types involved
smoltcp.wire.ipv6.Packet→smoltcp.wire.pretty_print.PrettyIndentsmoltcp.wire.ipv6.Packet→smoltcp.wire.pretty_print.PrettyPrint
- Direction
- wire.ipv6 uses wire.pretty_print, so a change to wire.pretty_print can break wire.ipv6, while a change to wire.ipv6 can't break wire.pretty_print.
- Position
- Below the diagonal: wire.ipv6 uses a module listed above it, which is the healthy direction.
37→11 wire.ipv6 uses wire.ethernet✕
- Connections
- 4 pairs of types, where a type in wire.ipv6 uses a type in wire.ethernet.
- The types involved
smoltcp.wire.ipv6.AddressExt→smoltcp.wire.ethernet.Addresssmoltcp.wire.ipv6.Cidr→smoltcp.wire.ethernet.Addresssmoltcp.wire.ipv6.Packet→smoltcp.wire.ethernet.Addresssmoltcp.wire.ipv6.Repr→smoltcp.wire.ethernet.Address
- Direction
- wire.ipv6 uses wire.ethernet, so a change to wire.ethernet can break wire.ipv6, while a change to wire.ipv6 can't break wire.ethernet.
- Position
- Below the diagonal: wire.ipv6 uses a module listed above it, which is the healthy direction.
37→12 wire.ipv6 uses iface.packet✕
- Connections
- 2 pairs of types, where a type in wire.ipv6 uses a type in iface.packet.
- The types involved
smoltcp.wire.ipv6.Packet→smoltcp.iface.packet.Packetsmoltcp.wire.ipv6.Repr→smoltcp.iface.packet.Packet
- Direction
- wire.ipv6 uses iface.packet, so a change to iface.packet can break wire.ipv6, while a change to wire.ipv6 can't break iface.packet.
- Position
- Below the diagonal: wire.ipv6 uses a module listed above it, which is the healthy direction.
37→28 wire.ipv6 uses wire✕
- Connections
- 2 pairs of types, where a type in wire.ipv6 uses a type in wire.
- The types involved
smoltcp.wire.ipv6.AddressExt→smoltcp.wire.HardwareAddresssmoltcp.wire.ipv6.Cidr→smoltcp.wire.HardwareAddress
- Direction
- wire.ipv6 uses wire, so a change to wire can break wire.ipv6, while a change to wire.ipv6 can't break wire.
- Position
- Below the diagonal: wire.ipv6 uses a module listed above it, which is the healthy direction.
37→39 wire.ipv6 uses wire.ip part of a loop✕
- Connections
- 4 pairs of types, where a type in wire.ipv6 uses a type in wire.ip.
- The types involved
smoltcp.wire.ipv6.AddressExt→smoltcp.wire.ip.Cidrsmoltcp.wire.ipv6.Cidr→smoltcp.wire.ip.Cidrsmoltcp.wire.ipv6.Packet→smoltcp.wire.ip.Protocolsmoltcp.wire.ipv6.Repr→smoltcp.wire.ip.Protocol
- Direction
- wire.ipv6 uses wire.ip, so a change to wire.ip can break wire.ipv6, while a change to wire.ipv6 can't break wire.ip.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
38→4 wire.ndiscoption uses time✕
- Connections
- 2 pairs of types, where a type in wire.ndiscoption uses a type in time.
- The types involved
smoltcp.wire.ndiscoption.NdiscOption→smoltcp.time.Durationsmoltcp.wire.ndiscoption.PrefixInformation→smoltcp.time.Duration
- Direction
- wire.ndiscoption uses time, so a change to time can break wire.ndiscoption, while a change to wire.ndiscoption can't break time.
- Position
- Below the diagonal: wire.ndiscoption uses a module listed above it, which is the healthy direction.
38→5 wire.ndiscoption uses wire.pretty_print✕
- Connections
- 2 pairs of types, where a type in wire.ndiscoption uses a type in wire.pretty_print.
- The types involved
smoltcp.wire.ndiscoption.NdiscOption→smoltcp.wire.pretty_print.PrettyIndentsmoltcp.wire.ndiscoption.NdiscOption→smoltcp.wire.pretty_print.PrettyPrint
- Direction
- wire.ndiscoption uses wire.pretty_print, so a change to wire.pretty_print can break wire.ndiscoption, while a change to wire.ndiscoption can't break wire.pretty_print.
- Position
- Below the diagonal: wire.ndiscoption uses a module listed above it, which is the healthy direction.
38→16 wire.ndiscoption uses wire.dns✕
- Connections
- 1 pair of types, where a type in wire.ndiscoption uses a type in wire.dns.
- The types involved
smoltcp.wire.ndiscoption.NdiscOption→smoltcp.wire.dns.Type
- Direction
- wire.ndiscoption uses wire.dns, so a change to wire.dns can break wire.ndiscoption, while a change to wire.ndiscoption can't break wire.dns.
- Position
- Below the diagonal: wire.ndiscoption uses a module listed above it, which is the healthy direction.
38→28 wire.ndiscoption uses wire✕
- Connections
- 1 pair of types, where a type in wire.ndiscoption uses a type in wire.
- The types involved
smoltcp.wire.ndiscoption.NdiscOption→smoltcp.wire.RawHardwareAddress
- Direction
- wire.ndiscoption uses wire, so a change to wire can break wire.ndiscoption, while a change to wire.ndiscoption can't break wire.
- Position
- Below the diagonal: wire.ndiscoption uses a module listed above it, which is the healthy direction.
39→5 wire.ip uses wire.pretty_print✕
- Connections
- 1 pair of types, where a type in wire.ip uses a type in wire.pretty_print.
- The types involved
smoltcp.wire.ip.ip$module→smoltcp.wire.pretty_print.PrettyIndent
- Direction
- wire.ip uses wire.pretty_print, so a change to wire.pretty_print can break wire.ip, while a change to wire.ip can't break wire.pretty_print.
- Position
- Below the diagonal: wire.ip uses a module listed above it, which is the healthy direction.
39→11 wire.ip uses wire.ethernet✕
- Connections
- 5 pairs of types, where a type in wire.ip uses a type in wire.ethernet.
- The types involved
smoltcp.wire.ip.Address→smoltcp.wire.ethernet.Addresssmoltcp.wire.ip.Cidr→smoltcp.wire.ethernet.Addresssmoltcp.wire.ip.Endpoint→smoltcp.wire.ethernet.Addresssmoltcp.wire.ip.ListenEndpoint→smoltcp.wire.ethernet.Addresssmoltcp.wire.ip.Repr→smoltcp.wire.ethernet.Address
- Direction
- wire.ip uses wire.ethernet, so a change to wire.ethernet can break wire.ip, while a change to wire.ip can't break wire.ethernet.
- Position
- Below the diagonal: wire.ip uses a module listed above it, which is the healthy direction.
39→12 wire.ip uses iface.packet✕
- Connections
- 2 pairs of types, where a type in wire.ip uses a type in iface.packet.
- The types involved
smoltcp.wire.ip.Packet→smoltcp.iface.packet.Packetsmoltcp.wire.ip.Repr→smoltcp.iface.packet.Packet
- Direction
- wire.ip uses iface.packet, so a change to iface.packet can break wire.ip, while a change to wire.ip can't break iface.packet.
- Position
- Below the diagonal: wire.ip uses a module listed above it, which is the healthy direction.
39→22 wire.ip uses phy✕
- Connections
- 1 pair of types, where a type in wire.ip uses a type in phy.
- The types involved
smoltcp.wire.ip.Repr→smoltcp.phy.ChecksumCapabilities
- Direction
- wire.ip uses phy, so a change to phy can break wire.ip, while a change to wire.ip can't break phy.
- Position
- Below the diagonal: wire.ip uses a module listed above it, which is the healthy direction.
39→28 wire.ip uses wire✕
- Connections
- 1 pair of types, where a type in wire.ip uses a type in wire.
- The types involved
smoltcp.wire.ip.Address→smoltcp.wire.HardwareAddress
- Direction
- wire.ip uses wire, so a change to wire can break wire.ip, while a change to wire.ip can't break wire.
- Position
- Below the diagonal: wire.ip uses a module listed above it, which is the healthy direction.
39→29 wire.ip uses wire.ipv4✕
- Connections
- 1 pair of types, where a type in wire.ip uses a type in wire.ipv4.
- The types involved
smoltcp.wire.ip.Address→smoltcp.wire.ipv4.AddressExt
- Direction
- wire.ip uses wire.ipv4, so a change to wire.ipv4 can break wire.ip, while a change to wire.ip can't break wire.ipv4.
- Position
- Below the diagonal: wire.ip uses a module listed above it, which is the healthy direction.
39→33 wire.ip uses socket.icmp✕
- Connections
- 2 pairs of types, where a type in wire.ip uses a type in socket.icmp.
- The types involved
smoltcp.wire.ip.Endpoint→smoltcp.socket.icmp.Endpointsmoltcp.wire.ip.ListenEndpoint→smoltcp.socket.icmp.Endpoint
- Direction
- wire.ip uses socket.icmp, so a change to socket.icmp can break wire.ip, while a change to wire.ip can't break socket.icmp.
- Position
- Below the diagonal: wire.ip uses a module listed above it, which is the healthy direction.
39→37 wire.ip uses wire.ipv6✕
- Connections
- 1 pair of types, where a type in wire.ip uses a type in wire.ipv6.
- The types involved
smoltcp.wire.ip.Address→smoltcp.wire.ipv6.MulticastScope
- Direction
- wire.ip uses wire.ipv6, so a change to wire.ipv6 can break wire.ip, while a change to wire.ip can't break wire.ipv6.
- Position
- Below the diagonal: wire.ip uses a module listed above it, which is the healthy direction.
39→40 wire.ip uses wire.arp part of a loop✕
- Connections
- 1 pair of types, where a type in wire.ip uses a type in wire.arp.
- The types involved
smoltcp.wire.ip.Repr→smoltcp.wire.arp.Repr
- Direction
- wire.ip uses wire.arp, so a change to wire.arp can break wire.ip, while a change to wire.ip can't break wire.arp.
- 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.
40→5 wire.arp uses wire.pretty_print✕
- Connections
- 2 pairs of types, where a type in wire.arp uses a type in wire.pretty_print.
- The types involved
smoltcp.wire.arp.Packet→smoltcp.wire.pretty_print.PrettyIndentsmoltcp.wire.arp.Packet→smoltcp.wire.pretty_print.PrettyPrint
- Direction
- wire.arp uses wire.pretty_print, so a change to wire.pretty_print can break wire.arp, while a change to wire.arp can't break wire.pretty_print.
- Position
- Below the diagonal: wire.arp uses a module listed above it, which is the healthy direction.
40→12 wire.arp uses iface.packet✕
- Connections
- 2 pairs of types, where a type in wire.arp uses a type in iface.packet.
- The types involved
smoltcp.wire.arp.Packet→smoltcp.iface.packet.Packetsmoltcp.wire.arp.Repr→smoltcp.iface.packet.Packet
- Direction
- wire.arp uses iface.packet, so a change to iface.packet can break wire.arp, while a change to wire.arp can't break iface.packet.
- Position
- Below the diagonal: wire.arp uses a module listed above it, which is the healthy direction.
40→39 wire.arp uses wire.ip✕
- Connections
- 1 pair of types, where a type in wire.arp uses a type in wire.ip.
- The types involved
smoltcp.wire.arp.Packet→smoltcp.wire.ip.Protocol
- Direction
- wire.arp uses wire.ip, so a change to wire.ip can break wire.arp, while a change to wire.arp can't break wire.ip.
- Position
- Below the diagonal: wire.arp uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Event Sourcing
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 16 | High / Critical |
Roadmap
Begin by documenting significant design decisions in the docs/adr folder and updating the root README with clear instructions for running the test suite. Next, address knowledge freshness by resolving orphaned files, prioritizing mod.rs, igmp.rs, and packet.rs, followed by dhcpv4.rs, ieee802154.rs, and iphc.rs. Finally, resolve the identified churn and complexity hotspot in tcp.rs to stabilize the codebase.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| 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. | +11.4 pts | Medium | Architecture documentation |
| Resolve the 1 Hotspot finding(s) in Churn × Complexity Hotspots — start with tcp.rs. | +3.1 pts | Medium | Churn × Complexity Hotspots |
| Resolve the 9 Orphaned knowledge finding(s) in Knowledge Freshness — start with dhcpv4.rs (2), ieee802154.rs, iphc.rs. | +3.0 pts | Low | Knowledge Freshness |
| 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. | +4.8 pts | Medium | Documentation (README) |
| Resolve the 20 Orphaned file finding(s) in Knowledge Freshness — start with mod.rs, igmp.rs, packet.rs. | +3.6 pts | Medium | Knowledge Freshness |
| Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. | +0.8 pts | Low | Bus Factor |
| Resolve the 1 Off-boarding risk finding(s) in Bus Factor. | +0.8 pts | Low | Bus Factor |
| Keep implementation types off the public surface (Rust: `pub(crate)`, or keep the module private) so internals can change without breaking consumers. | +1.5 pts | Medium | Library API & versioning |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| src/socket/tcp.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/iface/interface/multicast.rs | 6.0 | Mixed | Explicit Debt: FixmeComment |
| src/iface/interface/ipv4.rs | 6.0 | Mixed | Explicit Debt: FixmeComment |
| src/socket/dhcpv4.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/iface/interface/ipv6.rs | 6.0 | Mixed | Explicit Debt: FixmeComment |
| src/wire/dhcpv4.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/wire/sixlowpan/iphc.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/wire/icmpv6.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/iface/interface/mod.rs | 6.0 | Mixed | Explicit Debt: XxxComment |
| src/wire/ieee802154.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/wire/rpl.rs | 6.0 | Mixed | Explicit Debt: FixmeComment |
| src/iface/interface/sixlowpan.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/wire/sixlowpan/nhc.rs | 6.0 | Mixed | Explicit Debt: XxxComment |
| src/socket/tcp/congestion/cubic.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/wire/ndiscoption.rs | 6.7 | Mixed | Explicit Debt: TodoComment |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 54 of 54 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.8 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
What we checked — 54 dimensions across the health lenses
- Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 208 of 218 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 | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ 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 READ here — but this repository measures it: a Codecov configuration (.github/codecov.yml) and a coverage step in CI (`codecov/codecov-action`) shows that coverage is collected and tracked in your own CI. The built-in collector has no runner for this ecosystem (.rs), so the analyzer could not read the number — a gap in the analyzer's language coverage, not an unmeasured repo. Not scored. To have the real number 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.
- 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.
- GD1 Unfinished & placeholder code — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Python, Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's Python, Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- M4 Documentation accuracy — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- 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 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.
- 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.
- D11 Test Reliability: Flakiness is inferred from history/markers — Watchdog runs the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- 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").
- 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.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
- 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
20 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was Socket::process at 106. A further 4 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 Frame::addr_present_flags at 21 — they are counted neither in the figure above nor in this dimension's score. 3 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: src/wire/ieee802154.rs (Frame::addr_present_flags at 21), src/wire/rpl.rs (Packet::options at 18), src/wire/icmpv4.rs (DstUnreachable::fmt at 17). 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 30 down to 30 or less in Cyclomatic Complexity — start with Socket::process (cyclomatic 106), Socket::dispatch (cyclomatic 55). — 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.4 to about 7.7/10, projected with the scoring formula itself and assuming each lands exactly at 30; 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
24 method(s) exceeded the cognitive complexity threshold of 15; the worst was Socket::process at 130.
What to do
- Bring the 2 bodies over 60 down to 60 or less in Cognitive Complexity — start with Socket::process (cognitive 130), Socket::dispatch (cognitive 70). — 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 Cognitive Complexity from 5.8 to about 6.6/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
28 god class(es) detected.
What to do
- Resolve the 9 FileTooLong finding(s) in God Classes — start with tcp.rs (2), rpl.rs, mod.rs. — One of this dimension's main actionable groups (9 warning-level).
- Resolve the 9 TooManyMethods finding(s) in God Classes — start with tcp.rs (2), mod.rs (2), rpl.rs. — One of this dimension's main actionable groups (9 warning-level).
- Resolve the 7 MethodTooLong finding(s) in God Classes — start with tcp.rs (2), mod.rs (2), multicast.rs. — One of this dimension's main actionable groups (7 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
45 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 8 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with icmpv4.rs (3), mod.rs, raw.rs. — One of this dimension's main actionable groups (8 warning-level).
- Resolve the 6 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with ipv6option.rs (2), icmpv4.rs, icmpv6.rs. — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 3 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with dhcpv4.rs, rpl.rs, icmp.rs. — One of this dimension's main actionable groups (3 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
0 of 101 classes have LCOM4 above 3.
D9 · Test Distribution
656 test methods: 654 unit, 2 integration, 0 BDD, 0 e2e. The Rust suite contributes 656 `#[test]` function(s) across 59 file(s) declaring at least one; its unit/integration split is Cargo's own — 1 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.
D11 · Test Reliability
0 flaky across 1 measured tier(s). Rust (repository root, 59 test files): measured (0 flaky).
D12 · Dependency Hygiene
0 outdated, 0 yanked direct Cargo dependencies. 9 of 12 direct crates were graded against crates.io (0 not published there, 3 not resolved by a committed Cargo.lock). 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.
What to do
- Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 44 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository commits no Cargo.lock, so its graph was resolved here: its manifests' `[dependencies]` and `[build-dependencies]` closed over the crates.io index, each crate at the newest release its requirement admits (what a fresh `cargo generate-lockfile` picks, not a graph the repository has pinned). 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 0BSD, which is its own choice and is not judged here.
D15 · Churn × Complexity Hotspots
Top hotspots: src/socket/tcp.rs (7×55=385)
What to do
- Resolve the 1 Hotspot finding(s) in Churn × Complexity Hotspots — start with tcp.rs. — One of this dimension's main actionable groups (1 warning-level).
D16 · Bus Factor
9 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is src/wire/rpl.rs. Counted over 82 of the 98 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
D17 · Explicit Debt
39 deducted task-comment markers across 48673 LoC (0.1/KLoC) → score 9.8. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 28 TodoComment finding(s) in Explicit Debt — start with ipv6.rs (7), icmpv6.rs (4), mod.rs (4). — One of this dimension's main actionable groups (28 warning-level).
- Resolve the 7 FixmeComment finding(s) in Explicit Debt — start with ipv6.rs (2), icmpv6.rs, rpl.rs. — One of this dimension's main actionable groups (7 warning-level).
- Resolve the 4 XxxComment finding(s) in Explicit Debt — start with nhc.rs (2), tracer.rs, mod.rs. — One of this dimension's main actionable groups (4 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. 1 document(s) read across 1 unit(s).
D26 · Project Cohesion
1 of 1 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)
16 finding(s): 0 critical, 16 high, 0 medium, 0 low. 14 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.
What to do
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 14 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 (14 issue-level, 0 of them charged here).
D34 · Knowledge Freshness
29 of 82 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/wire/dhcpv4.rs. Counted over 82 of the 98 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 20 Orphaned file finding(s) in Knowledge Freshness — start with mod.rs, igmp.rs, packet.rs. — One of this dimension's main actionable groups (20 recommendation-level).
- Resolve the 9 Orphaned knowledge finding(s) in Knowledge Freshness — start with dhcpv4.rs (2), ieee802154.rs, iphc.rs. — One of this dimension's main actionable groups (9 issue-level).
- Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
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
ES1 · Fold determinism
ES2 · Immutable events
M1 · Documentation (README)
- 35 code files changed in the last 6 months but the README was not touched — it may no longer reflect the system.
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.
- Add a README to the 1 of 1 project(s) that lack one — worth up to 2 pts.
- Review the README against recent changes; refresh the parts that drifted.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
- 206/293 types (70%) declared in the published library are public. For a library, every public type is a stability contract — keep implementation types off the surface and expose only the intended API.
What to do
- Keep implementation types off the public surface (Rust: `pub(crate)`, or keep the module private) so internals can change without breaking consumers.
P2 · Observability
P3 · Security & performance tooling
What to do
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
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 | 91% | Exemplary | Solid. |
| Architecture | 88% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 51% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 73% | Strong | Solid. |
| Security | 90% | Exemplary | Solid. |
| Event Sourcing | 100% | Exemplary | Strongest area. |
| Performance | 80% | Strong | Solid. |
Unscored — 2 check(s) recorded observations but carry no score
- D36 Supply-chain Provenance & Signing — 5 observation(s) recorded · The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
- P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
Not evidenced — 2 control(s) we could not find positive evidence for
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 62 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: this repository's Python imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one.
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No 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
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no data at rest for these controls to protect.
- C2 Access Controls — No access-control surface detected in the analyzed source — this repository starts no server another machine can reach (no actix-web HttpServer, axum::serve, Rocket launch, warp::serve, poem or salvo Server, tonic Server::builder, hyper or tiny_http server outside examples and tests, none bound beyond loopback). Access control is therefore N/A here — a crate is authorized by the application that serves it, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~6461 lines of test source are present (.rs) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- 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. 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.
- D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Cargo manifest — not scanned yet).
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- 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.
- D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Cargo manifest — not scanned yet).
- D5 Coupling — Not applicable — this Cargo build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
- 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): 27 value object(s); 1 domain event(s); its domain events are published by services or handlers — no domain entity raises one
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- 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: 91 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.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X16 Unfloored truncation loop — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X18 Disposal-pattern correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X2 Cancellation propagation — no C# was loaded; this repository's Python and Rust were read, and no request in it can be cancelled by a caller — a Python request takes no token: asyncio cancels the task and trio or anyio the scope that made it, from outside the call, and requests, httpx, aiohttp and gRPC take a timeout, not a cancellation; a Rust request takes no token: a future is cancelled by dropping it, from outside the call (select!, a timeout, an aborted task), and reqwest, hyper and tonic take none
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- 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.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 26 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Orphaned knowledge src/wire/dhcpv4.rs:1
- Orphaned knowledge src/socket/dhcpv4.rs:1
- Orphaned knowledge src/wire/ieee802154.rs:1
- Orphaned knowledge src/wire/sixlowpan/iphc.rs:1
- Orphaned knowledge src/wire/sixlowpan/nhc.rs:1
- Orphaned knowledge src/wire/ndiscoption.rs:1
- Orphaned knowledge src/wire/dns.rs:1
- Orphaned knowledge src/wire/ipv6option.rs:1
- Orphaned knowledge src/wire/ipv6routing.rs:1
- REDACTED
- REDACTED
- REDACTED
Serious — 164 finding(s)
- TodoComment src/wire/dhcpv4.rs:446
- TodoComment src/wire/icmpv6.rs:303
- TodoComment src/wire/icmpv6.rs:309
- TodoComment src/wire/icmpv6.rs:315
- TodoComment src/wire/icmpv6.rs:321
- TodoComment src/wire/ieee802154.rs:51
- TodoComment src/wire/ipv6.rs:675
- TodoComment src/wire/ndiscoption.rs:566
- TodoComment src/wire/sixlowpan/iphc.rs:689
- TodoComment src/socket/dhcpv4.rs:1373
- TodoComment src/socket/tcp.rs:2169
- TodoComment src/socket/tcp.rs:3002
- TodoComment src/socket/tcp/congestion/cubic.rs:175
- TodoComment src/socket/tcp/congestion/cubic.rs:199
- TodoComment src/phy/mod.rs:68
- TodoComment src/phy/mod.rs:83
- TodoComment src/phy/mod.rs:336
- TodoComment src/iface/fragmentation.rs:240
- TodoComment src/iface/interface/sixlowpan.rs:5
- TodoComment src/iface/interface/ipv6.rs:130
- TodoComment src/iface/interface/ipv6.rs:131
- TodoComment src/iface/interface/ipv6.rs:132
- TodoComment src/iface/interface/ipv6.rs:133
- TodoComment src/iface/interface/ipv6.rs:134
- TodoComment src/iface/interface/ipv6.rs:135
- FileTooLong: socket/tcp.rs src/socket/tcp.rs
- FileTooLong: wire/rpl.rs src/wire/rpl.rs
- FileTooLong: interface/mod.rs src/iface/interface/mod.rs
- FileTooLong: wire/tcp.rs src/wire/tcp.rs
- FileTooLong: wire/ieee802154.rs src/wire/ieee802154.rs
- FileTooLong: wire/ip.rs src/wire/ip.rs
- FileTooLong: sixlowpan/iphc.rs src/wire/sixlowpan/iphc.rs
- FileTooLong: wire/dhcpv4.rs src/wire/dhcpv4.rs
- FileTooLong: wire/icmpv6.rs src/wire/icmpv6.rs
- TooManyMethods: Packet src/wire/rpl.rs:876
- TooManyMethods: Packet src/iface/packet.rs:16
- TooManyMethods: Socket src/socket/tcp.rs:495
- TooManyMethods: InterfaceInner src/iface/interface/mod.rs:128
- TooManyMethods: Packet src/wire/tcp.rs:88
- TooManyMethods: Frame src/wire/ieee802154.rs:228
- TooManyMethods: Interface src/iface/interface/mod.rs:115
- TooManyMethods: Packet src/wire/ipv4.rs:192
- TooManyMethods: Packet src/wire/dhcpv4.rs:116
- Duplicated block (8 lines × 2) src/iface/interface/mod.rs:319
- Duplicated block (8 lines × 2) src/socket/raw.rs:281
- Duplicated block (8 lines × 2) src/socket/udp.rs:411
- Duplicated block (8 lines × 2) src/wire/icmpv4.rs:423
- Duplicated block (8 lines × 2) src/wire/sixlowpan/iphc.rs:445
- Duplicated block (8 lines × 2) src/wire/dns.rs:103
- Duplicated block (8 lines × 2) src/wire/icmpv4.rs:277
- Duplicated block (8 lines × 2) src/wire/icmpv4.rs:339
- FixmeComment src/wire/icmpv6.rs:751
- FixmeComment src/wire/rpl.rs:1945
- FixmeComment src/wire/sixlowpan/iphc.rs:857
- FixmeComment src/iface/interface/ipv4.rs:367
- FixmeComment src/iface/interface/ipv6.rs:444
- FixmeComment src/iface/interface/multicast.rs:407
- FixmeComment src/iface/interface/tests/ipv6.rs:1808
- Socket::process (cognitive 130) src/socket/tcp.rs:1662
- Socket::dispatch (cognitive 70) src/socket/tcp.rs:2512
- Socket::process (cognitive 57) src/socket/dns.rs:378
- Socket::process (cognitive 26) src/socket/dhcpv4.rs:305
- Socket::dispatch (cognitive 26) src/socket/dns.rs:532
- Socket::dispatch (cognitive 19) src/socket/dhcpv4.rs:563
- Socket::dispatch (cognitive 17) src/socket/raw.rs:384
- MethodTooLong: Socket.process src/socket/tcp.rs:1662
- MethodTooLong: Socket.dispatch src/socket/tcp.rs:2512
- MethodTooLong: Interface.multicast_egress src/iface/interface/multicast.rs:186
- MethodTooLong: InterfaceInner.dispatch_ip src/iface/interface/mod.rs:1214
- MethodTooLong: Socket.dispatch src/socket/dhcpv4.rs:563
- MethodTooLong: Repr.emit src/wire/rpl.rs:2174
- MethodTooLong: InterfaceInner.lookup_hardware_addr src/iface/interface/mod.rs:1062
- Duplicated block (5 lines × 2) src/wire/icmpv4.rs:500
- Duplicated block (5 lines × 2) src/wire/icmpv6.rs:811
- Duplicated block (5 lines × 2) src/socket/tcp/congestion/cubic.rs:181
- Duplicated block (5 lines × 2) src/wire/ipv6option.rs:217
- Duplicated block (5 lines × 2) src/wire/ipv6option.rs:249
- Duplicated block (5 lines × 2) src/wire/ipv4.rs:446
- InterfaceInner::process_ipv4 (cyclomatic 23) src/iface/interface/ipv4.rs:95
- InterfaceInner::get_source_address_ipv6 (cyclomatic 21) src/iface/interface/ipv6.rs:30
- InterfaceInner::process_ndisc (cyclomatic 17) src/iface/interface/ipv6.rs:451
- InterfaceInner::lookup_hardware_addr (cyclomatic 16) src/iface/interface/mod.rs:1062
- InterfaceInner::dispatch_ip (cyclomatic 16) src/iface/interface/mod.rs:1214
- InterfaceInner::dispatch_ip (cognitive 32) src/iface/interface/mod.rs:1214
- InterfaceInner::get_source_address_ipv6 (cognitive 28) src/iface/interface/ipv6.rs:30
- InterfaceInner::process_ipv4 (cognitive 27) src/iface/interface/ipv4.rs:95
- InterfaceInner::process_ndisc (cognitive 25) src/iface/interface/ipv6.rs:451
- InterfaceInner::process_igmp (cognitive 16) src/iface/interface/multicast.rs:397
- Socket::process (cyclomatic 106) src/socket/tcp.rs:1662
- Socket::dispatch (cyclomatic 55) src/socket/tcp.rs:2512
- Socket::process (cyclomatic 25) src/socket/dns.rs:378
- Socket::process (cyclomatic 22) src/socket/dhcpv4.rs:305
- XxxComment src/wire/sixlowpan/nhc.rs:625
- XxxComment src/wire/sixlowpan/nhc.rs:735
- XxxComment src/phy/tracer.rs:207
- XxxComment src/iface/interface/mod.rs:1134
- Repr::buffer_len (cognitive 31) src/wire/sixlowpan/iphc.rs:755
- Repr::parse (cognitive 19) src/wire/dhcpv4.rs:706
- Repr::parse (cognitive 19) src/wire/ndiscoption.rs:440
- Repr::emit (cognitive 17) src/wire/ndisc.rs:347
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Repr::parse (cyclomatic 21) src/wire/dhcpv4.rs:706
- Repr::buffer_len (cyclomatic 21) src/wire/sixlowpan/iphc.rs:755
- Repr::parse (cyclomatic 20) src/wire/tcp.rs:898
- Packet::check_len (cyclomatic 20) src/wire/icmpv6.rs:275
- Packet::fmt (cyclomatic 19) src/wire/tcp.rs:1114
- Packet::dst_addr (cyclomatic 18) src/wire/sixlowpan/iphc.rs:278
- Duplicated block (6 lines × 2) src/wire/dhcpv4.rs:401
- Duplicated block (6 lines × 2) src/wire/rpl.rs:787
- Duplicated block (6 lines × 2) src/socket/icmp.rs:48
- Duplicated block (6 lines × 3) src/socket/icmp.rs:29
- Duplicated block (6 lines × 3) src/socket/icmp.rs:67
- Duplicated block (6 lines × 3) src/wire/arp.rs:382
- Packet::check_len (cognitive 23) src/wire/icmpv6.rs:275
- Packet::set_dst_address (cognitive 17) src/wire/sixlowpan/iphc.rs:587
- ClassTooLong: Socket src/socket/tcp.rs:495
- ClassTooLong: Frame src/wire/ieee802154.rs:228
- Duplicated block (13 lines × 2) src/iface/interface/multicast.rs:199
- Duplicated block (13 lines × 2) src/socket/udp.rs:308
- Duplicated block (12 lines × 2) src/phy/raw_socket.rs:127
- Duplicated block (12 lines × 2) src/wire/sixlowpan/mod.rs:101
- Duplicated block (11 lines × 2) src/wire/ip.rs:931
- Duplicated block (11 lines × 2) src/wire/sixlowpan/nhc.rs:527
- Duplicated block (7 lines × 2) src/wire/icmpv4.rs:525
- Duplicated block (7 lines × 2) src/wire/sixlowpan/iphc.rs:604
- Interface::multicast_egress (cyclomatic 28) src/iface/interface/multicast.rs:186
- UnresolvedAddress::resolve (cyclomatic 23) src/wire/sixlowpan/mod.rs:65
- Parser::accept_ipv6_part (cyclomatic 20) src/parsers.rs:163
- Assembler::add (cyclomatic 16) src/storage/assembler.rs:196
- TcpOption::parse (cyclomatic 16) src/wire/tcp.rs:678
- Hotspot: src/socket/tcp.rs src/socket/tcp.rs:2512
- Interface::multicast_egress (cognitive 60) src/iface/interface/multicast.rs:186
- Assembler::add (cognitive 23) src/storage/assembler.rs:196
- SequenceCounter::partial_cmp (cognitive 21) src/iface/rpl/lollipop.rs:76
- Parser::accept_ipv6_part (cognitive 20) src/parsers.rs:163
- UnresolvedAddress::resolve (cognitive 17) src/wire/sixlowpan/mod.rs:65
- Frame::check_len (cognitive 16) src/wire/ieee802154.rs:307
- TooManyFields: Socket src/socket/tcp.rs:495
- Members sharing a duplicated core (4 members, 50+ identical tokens) src/socket/raw.rs:279
- Duplicated block (28 lines × 2) src/iface/interface/sixlowpan.rs:428
- Duplicated block (22 lines × 2) src/wire/ipv4.rs:63
- Duplicated block (21 lines × 2) src/storage/packet_buffer.rs:91
- Duplicated block (20 lines × 2) src/wire/ieee802154.rs:502
- Duplicated block (13–18 lines × 2) src/iface/interface/multicast.rs:213
- Duplicated block (18 lines × 2) src/socket/icmp.rs:444
- Duplicated block (17 lines × 2) src/socket/icmp.rs:265
- Duplicated block (12–17 lines × 2) src/socket/icmp.rs:464
- Duplicated block (13–17 lines × 2) src/wire/sixlowpan/iphc.rs:533
- Duplicated block (15 lines × 2) src/phy/raw_socket.rs:80
- Duplicated block (11 lines × 3) src/socket/icmp.rs:675
- Duplicated block (10–11 lines × 2) src/iface/interface/mod.rs:1394
- Duplicated block (10 lines × 2) src/wire/ip.rs:822
- Duplicated block (9 lines × 2) src/wire/icmpv4.rs:506
- Duplicated block (8 lines × 4) src/wire/sixlowpan/iphc.rs:539
- Duplicated block (6 lines × 4) src/socket/raw.rs:281
- Duplicated block (5 lines × 3) src/wire/ieee802154.rs:736
- README may be stale
- Coverage collected but not gated
Minor — 28 finding(s)
- Orphaned file src/wire/sixlowpan/mod.rs:1
- Orphaned file src/wire/igmp.rs:1
- Orphaned file src/iface/packet.rs:1
- Orphaned file src/wire/sixlowpan/frag.rs:1
- Orphaned file src/iface/rpl/trickle.rs:1
- Orphaned file src/wire/ipv6ext_header.rs:1
- Orphaned file src/wire/ipv6fragment.rs:1
- Orphaned file src/iface/rpl/lollipop.rs:1
- Orphaned file src/phy/sys/bpf.rs:1
- Orphaned file src/wire/ipsec_esp.rs:1
- Orphaned file src/wire/ipv6hbh.rs:1
- Orphaned file fuzz/fuzz_targets/iface.rs:1
- Orphaned file src/iface/rpl/parents.rs:1
- Orphaned file src/iface/rpl/relations.rs:1
- Orphaned file src/phy/fuzz_injector.rs:1
- Orphaned file src/iface/interface/ieee802154.rs:1
- Orphaned file src/iface/rpl/rank.rs:1
- Orphaned file src/iface/rpl/of0.rs:1
- Orphaned file gen_config.py:1
- Orphaned file src/iface/interface/udp.rs:1
- Off-boarding risk: anonymized user #1
- Further sole-owners (lower concentration)
- Projects may be oversized for their cohesion
- Further orphaned files (smaller)
- REDACTED
- No ADRs
- No architecture diagram/doc
- Large public API surface
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-c14c39db5b89463da902df88a5cc00b7/history.json --exit-code 0 --source . | 1 | 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-c14c39db5b89463da902df88a5cc00b7/tree.json --exit-code 0 --source . | 1 | 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 . | 16 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Cargo manifest — not scanned yet). | 0 | — |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Cargo manifest — not scanned yet). | 0 | — |