Executive summary
fujiapple852/trippy falls short of our standard for a preview release, in part because we found no recorded design decisions and no architecture document or diagram. It scores 63 out of 100 and is rated Adequate, and all 46 of its critical findings are security problems.
Maturity, at 60, is the weakest lens by a small margin, and the weakest lens counts most in the score. The best first step is recording design decisions, worth about 5 points. Turning on missing-value checks is another step, worth about 3 points.
Thirty-six pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Four settings leave the servers or containers unsafe, and two pipeline steps install packages that can change without warning. Pinning each tool to an exact version, correcting the unsafe settings and pinning what the pipeline installs would close these risks. Setting a waiting period for automatic updates would fix the automatic dependency update that takes a new release at once, and the pipeline step that runs a download without checking it needs each download checked against a known checksum first.
The product code is 28,853 lines, about €34,000 to rebuild.
The weakest lenses score close to each other, so improving any of them moves the score.
New since the last survey: 81 findings
- Code Duplication · Near-duplicate member pair (57 shared lines) crates/trippy-core/src/net/ipv4.rs
- Code Duplication · Edited copy of a member (40 corresponding lines) crates/trippy-tui/src/config/binding.rs
- Code Duplication · Edited copy of a member (40 corresponding lines) crates/trippy-tui/src/frontend/render/header.rs
- Code Duplication · Edited copy of a member (38 corresponding lines) crates/trippy-core/src/net/ipv4.rs
- Code Duplication · Edited copy of a member (41 corresponding lines) crates/trippy-core/src/net/ipv4.rs
- Code Duplication · Edited copy of a member (18 corresponding lines) crates/trippy-core/src/net/ipv4.rs
- Code Duplication · Edited copy of a member (16 corresponding lines) crates/trippy-packet/src/ipv4.rs
- Code Duplication · Edited copy of a member (14 corresponding lines) crates/trippy-core/src/net/ipv4.rs
- Code Duplication · Edited copy of a member (19 corresponding lines) crates/trippy-core/src/net/platform/unix.rs
- Code Duplication · Edited copy of a member (12 corresponding lines) crates/trippy-core/src/net/ipv4.rs
- Code Duplication · Edited copy of a member (13 corresponding lines) crates/trippy-core/src/net/platform/unix.rs
- Code Duplication · Edited copies of one member (3 members, 13+ corresponding lines) crates/trippy-dns/src/lazy_resolver.rs
- Code Duplication · Edited copy of a member (14 corresponding lines) crates/trippy-core/src/net/ipv4.rs
- Code Duplication · Edited copy of a member (14 corresponding lines) crates/trippy-tui/src/config/binding.rs
- Code Duplication · Edited copy of a member (18 corresponding lines) crates/trippy-tui/src/frontend/render/table.rs
- Code Duplication · Edited copy of a member (18 corresponding lines) crates/trippy-tui/src/frontend/tui_app.rs
- Code Duplication · Edited copy of a member (8 corresponding lines) crates/trippy-core/src/tracer.rs
- Code Duplication · Edited copy of a member (11 corresponding lines) crates/trippy-core/src/net/platform/windows.rs
- Code Duplication · Edited copy of a member (9 corresponding lines) crates/trippy-packet/src/icmpv4.rs
- Code Duplication · Edited copy of a member (13 corresponding lines) crates/trippy-core/src/net/platform/windows.rs
- Code Duplication · Edited copy of a member (7 corresponding lines) crates/trippy-core/src/net/channel.rs
- Code Duplication · Edited copy of a member (11 corresponding lines) crates/trippy-core/src/net/platform/unix.rs
- Code Duplication · Edited copy of a member (7 corresponding lines) crates/trippy-core/src/net/platform/unix.rs
- Code Duplication · Edited copies of one member (3 members, 12+ corresponding lines) crates/trippy-core/src/net/platform/unix.rs
- Code Duplication · Edited copy of a member (12 corresponding lines) crates/trippy-tui/src/frontend/tui_app.rs
- Code Duplication · Edited copy of a member (13 corresponding lines) crates/trippy-packet/src/tcp.rs
- Code Duplication · Edited copy of a member (13 corresponding lines) crates/trippy-packet/src/udp.rs
- Code Duplication · Edited copy of a member (14 corresponding lines) crates/trippy-tui/src/frontend/tui_app.rs
- Code Duplication · Edited copy of a member (13 corresponding lines) crates/trippy-core/src/net/ipv4.rs
- Code Duplication · Edited copy of a member (9 corresponding lines) crates/trippy-core/src/net/ipv4.rs
- Code Duplication · Edited copy of a member (8 corresponding lines) crates/trippy-packet/src/ipv4.rs
- Code Duplication · Edited copies of one member (4 members, 4+ corresponding lines) crates/trippy-packet/src/icmp_extension.rs
- Code Duplication · Edited copy of a member (5 corresponding lines) crates/trippy-core/src/net/platform/unix.rs
- Code Duplication · Duplicated block (32 lines × 2) crates/trippy-core/src/net/ipv4.rs
- Code Duplication · Duplicated block (17 lines × 2) crates/trippy-core/src/net/ipv4.rs
- Code Duplication · Duplicated block (12 lines × 2) crates/trippy-dns/src/lazy_resolver.rs
- Code Duplication · Duplicated block (7 lines × 3) crates/trippy-dns/src/lazy_resolver.rs
- Code Coverage · Low coverage: crates/trippy-core/src/error.rs crates/trippy-core/src/error.rs
- Code Coverage · Low coverage: crates/trippy-core/src/net/channel.rs crates/trippy-core/src/net/channel.rs
- Code Coverage · Low coverage: crates/trippy-core/src/net/platform/unix.rs crates/trippy-core/src/net/platform/unix.rs
- Code Coverage · Low coverage: crates/trippy-core/src/types.rs crates/trippy-core/src/types.rs
- Code Coverage · Low coverage: crates/trippy-dns/src/config.rs crates/trippy-dns/src/config.rs
- Code Coverage · Low coverage: crates/trippy-dns/src/lazy_resolver.rs crates/trippy-dns/src/lazy_resolver.rs
- Code Coverage · Low coverage: crates/trippy-dns/src/resolver.rs crates/trippy-dns/src/resolver.rs
- Code Coverage · Low coverage: crates/trippy-tui/src/app.rs crates/trippy-tui/src/app.rs
- Code Coverage · Low coverage: crates/trippy-tui/src/frontend.rs crates/trippy-tui/src/frontend.rs
- Code Coverage · Low coverage: crates/trippy-tui/src/frontend/binding.rs crates/trippy-tui/src/frontend/binding.rs
- Code Coverage · Low coverage: crates/trippy-tui/src/frontend/config.rs crates/trippy-tui/src/frontend/config.rs
- Code Coverage · Low coverage: crates/trippy-tui/src/frontend/render/app.rs crates/trippy-tui/src/frontend/render/app.rs
- Code Coverage · Low coverage: crates/trippy-tui/src/frontend/render/bar.rs crates/trippy-tui/src/frontend/render/bar.rs
- Code Coverage · Low coverage: crates/trippy-tui/src/frontend/render/body.rs crates/trippy-tui/src/frontend/render/body.rs
- Code Coverage · Low coverage: crates/trippy-tui/src/frontend/render/bsod.rs crates/trippy-tui/src/frontend/render/bsod.rs
- Code Coverage · Low coverage: crates/trippy-tui/src/frontend/render/chart.rs crates/trippy-tui/src/frontend/render/chart.rs
- Code Coverage · Low coverage: crates/trippy-tui/src/frontend/render/flows.rs crates/trippy-tui/src/frontend/render/flows.rs
- Code Coverage · Low coverage: crates/trippy-tui/src/frontend/render/footer.rs crates/trippy-tui/src/frontend/render/footer.rs
- Code Coverage · Low coverage: crates/trippy-tui/src/frontend/render/header.rs crates/trippy-tui/src/frontend/render/header.rs
- Code Coverage · Low coverage: crates/trippy-tui/src/frontend/render/help.rs crates/trippy-tui/src/frontend/render/help.rs
- Code Coverage · Low coverage: crates/trippy-tui/src/frontend/render/histogram.rs crates/trippy-tui/src/frontend/render/histogram.rs
- Code Coverage · Low coverage: crates/trippy-tui/src/frontend/render/history.rs crates/trippy-tui/src/frontend/render/history.rs
- Code Coverage · Low coverage: crates/trippy-tui/src/frontend/render/settings.rs crates/trippy-tui/src/frontend/render/settings.rs
- Code Coverage · Low coverage: crates/trippy-tui/src/frontend/render/splash.rs crates/trippy-tui/src/frontend/render/splash.rs
- Code Coverage · Low coverage: crates/trippy-tui/src/frontend/render/table.rs crates/trippy-tui/src/frontend/render/table.rs
- Code Coverage · Low coverage: crates/trippy-tui/src/frontend/render/tabs.rs crates/trippy-tui/src/frontend/render/tabs.rs
- Code Coverage · Low coverage: crates/trippy-tui/src/frontend/render/util.rs crates/trippy-tui/src/frontend/render/util.rs
- Code Coverage · Low coverage: crates/trippy-tui/src/frontend/render/world.rs crates/trippy-tui/src/frontend/render/world.rs
- Code Coverage · Low coverage: crates/trippy-tui/src/frontend/theme.rs crates/trippy-tui/src/frontend/theme.rs
- Code Coverage · Low coverage: crates/trippy-tui/src/frontend/tui_app.rs crates/trippy-tui/src/frontend/tui_app.rs
- Code Coverage · Low coverage: crates/trippy-tui/src/geoip.rs crates/trippy-tui/src/geoip.rs
- Code Coverage · Low coverage: crates/trippy-tui/src/lib.rs crates/trippy-tui/src/lib.rs
- Code Coverage · Low coverage: crates/trippy-tui/src/report.rs crates/trippy-tui/src/report.rs
- Code Coverage · Low coverage: crates/trippy-tui/src/report/csv.rs crates/trippy-tui/src/report/csv.rs
- Code Coverage · Low coverage: crates/trippy-tui/src/report/dot.rs crates/trippy-tui/src/report/dot.rs
- Code Coverage · Low coverage: crates/trippy-tui/src/report/flows.rs crates/trippy-tui/src/report/flows.rs
- Code Coverage · Low coverage: crates/trippy-tui/src/report/json.rs crates/trippy-tui/src/report/json.rs
- Code Coverage · Low coverage: crates/trippy-tui/src/report/silent.rs crates/trippy-tui/src/report/silent.rs
- Code Coverage · Low coverage: crates/trippy-tui/src/report/stream.rs crates/trippy-tui/src/report/stream.rs
- Code Coverage · Low coverage: crates/trippy-tui/src/report/table.rs crates/trippy-tui/src/report/table.rs
- Code Coverage · Low coverage: crates/trippy-tui/src/report/types.rs crates/trippy-tui/src/report/types.rs
- Code Coverage · Low coverage: crates/trippy/src/main.rs crates/trippy/src/main.rs
- Code Coverage · Low coverage: examples/hello-world/src/main.rs examples/hello-world/src/main.rs
- Code Coverage · Low coverage: examples/toy-traceroute/src/main.rs examples/toy-traceroute/src/main.rs
Fixed since the last survey: 5 findings
- Code Duplication · Duplicated block (12 lines × 2) crates/trippy-dns/src/lazy_resolver.rs
- Code Duplication · Duplicated block (10 lines × 2) crates/trippy-core/src/net/ipv4.rs
- Code Duplication · Duplicated block (7 lines × 3) crates/trippy-dns/src/lazy_resolver.rs
- Dependency Vulnerabilities · Medium vulnerability: [GHSA redacted] REDACTED
- Change Coupling · Change coupling: report.rs ↔ main.rs crates/trippy-tui/src/report.rs
Rebuild cost: about €34,000 · Estimate
| Cost to rebuild | €11,000 to €57,000, for 190 to 602 hours of work, about 0.2 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 63. 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: 28,853 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 trippy_core.error | 2 trippy_core.types | 3 trippy_dns.resolver | 4 trippy_packet | 5 trippy_packet.buffer | 6 trippy_tui.config.binding | 7 trippy_tui.config.columns | 8 trippy_tui.config.theme | 9 trippy_tui.geoip | 10 trippy_tui.report.types | 11 trippy_core.config | 12 trippy_core.net.socket | 13 trippy_core.probe | 14 trippy_dns.lazy_resolver | 15 trippy_packet.icmpv4 | 16 trippy_packet.ipv4 | 17 trippy_packet.ipv6 | 18 trippy_tui.config.file | 19 trippy_tui.frontend.columns | 20 trippy_tui.frontend.theme | 21 trippy_core.builder | 22 trippy_core.net.channel | 23 trippy_core.net.ipv4 | 24 trippy_core.net.ipv6 | 25 trippy_core.net.platform.unix.socket | 26 trippy_core.net.platform.windows | 27 trippy_core.strategy.state | 28 trippy_dns.config | 29 trippy_tui.config | 30 trippy_core.strategy | 31 trippy_tui.frontend.config | 32 trippy_core.state | 33 trippy_core.state.state_updater | 34 trippy_core.tracer.inner | 35 trippy_core.tracer | 36 trippy_tui.app | 37 trippy_tui.frontend.tui_app | 38 trippy_tui.frontend | 39 trippy_tui.frontend.render.settings | 40 trippy_tui.frontend.render.table |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 trippy_core.error | ||||||||||||||||||||||||||||||||||||||||
| 2 trippy_core.types | ||||||||||||||||||||||||||||||||||||||||
| 3 trippy_dns.resolver | ||||||||||||||||||||||||||||||||||||||||
| 4 trippy_packet | ||||||||||||||||||||||||||||||||||||||||
| 5 trippy_packet.buffer | ||||||||||||||||||||||||||||||||||||||||
| 6 trippy_tui.config.binding | ||||||||||||||||||||||||||||||||||||||||
| 7 trippy_tui.config.columns | ||||||||||||||||||||||||||||||||||||||||
| 8 trippy_tui.config.theme | ||||||||||||||||||||||||||||||||||||||||
| 9 trippy_tui.geoip | ||||||||||||||||||||||||||||||||||||||||
| 10 trippy_tui.report.types | ||||||||||||||||||||||||||||||||||||||||
| 11 trippy_core.config | 10 | |||||||||||||||||||||||||||||||||||||||
| 12 trippy_core.net.socket | 1 | |||||||||||||||||||||||||||||||||||||||
| 13 trippy_core.probe | 23 | |||||||||||||||||||||||||||||||||||||||
| 14 trippy_dns.lazy_resolver | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 15 trippy_packet.icmpv4 | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 trippy_packet.ipv4 | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 17 trippy_packet.ipv6 | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 18 trippy_tui.config.file | 1 | 1 | 11 | |||||||||||||||||||||||||||||||||||||
| 19 trippy_tui.frontend.columns | 2 | |||||||||||||||||||||||||||||||||||||||
| 20 trippy_tui.frontend.theme | 1 | |||||||||||||||||||||||||||||||||||||||
| 21 trippy_core.builder | 8 | 5 | ||||||||||||||||||||||||||||||||||||||
| 22 trippy_core.net.channel | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 23 trippy_core.net.ipv4 | 6 | 1 | 3 | 1 | 2 | |||||||||||||||||||||||||||||||||||
| 24 trippy_core.net.ipv6 | 6 | 3 | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||
| 25 trippy_core.net.platform.unix.socket | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 26 trippy_core.net.platform.windows | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 27 trippy_core.strategy.state | 4 | 1 | 2 | 2 | ||||||||||||||||||||||||||||||||||||
| 28 trippy_dns.config | 4 | |||||||||||||||||||||||||||||||||||||||
| 29 trippy_tui.config | 2 | 2 | 1 | 10 | 5 | 3 | ||||||||||||||||||||||||||||||||||
| 30 trippy_core.strategy | 10 | 1 | 4 | 1 | ||||||||||||||||||||||||||||||||||||
| 31 trippy_tui.frontend.config | 1 | 1 | 1 | 1 | 1 | 4 | ||||||||||||||||||||||||||||||||||
| 32 trippy_core.state | 5 | 1 | 2 | 2 | ||||||||||||||||||||||||||||||||||||
| 33 trippy_core.state.state_updater | 2 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 34 trippy_core.tracer.inner | 1 | 8 | 8 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 35 trippy_core.tracer | 8 | 5 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 36 trippy_tui.app | 1 | 1 | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||
| 37 trippy_tui.frontend.tui_app | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 38 trippy_tui.frontend | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 39 trippy_tui.frontend.render.settings | 1 | 4 | 1 | |||||||||||||||||||||||||||||||||||||
| 40 trippy_tui.frontend.render.table | 2 | 2 | 2 | 4 | 1 | 1 | 2 | 1 | 1 | 1 | 1 | 1 |
11→2 trippy_core.config uses trippy_core.types✕
- Connections
- 10 pairs of types, where a type in trippy_core.config uses a type in trippy_core.types.
- The types involved
trippy_core.config.ChannelConfig→trippy_core.types.PacketSizetrippy_core.config.ChannelConfig→trippy_core.types.PayloadPatterntrippy_core.config.ChannelConfig→trippy_core.types.Sequencetrippy_core.config.ChannelConfig→trippy_core.types.TypeOfServicetrippy_core.config.PortDirection→trippy_core.types.Porttrippy_core.config.StrategyConfig→trippy_core.types.MaxInflighttrippy_core.config.StrategyConfig→trippy_core.types.MaxRoundstrippy_core.config.StrategyConfig→trippy_core.types.Sequencetrippy_core.config.StrategyConfig→trippy_core.types.TimeToLivetrippy_core.config.StrategyConfig→trippy_core.types.TraceId
- Direction
- trippy_core.config uses trippy_core.types, so a change to trippy_core.types can break trippy_core.config, while a change to trippy_core.config can't break trippy_core.types.
- Position
- Below the diagonal: trippy_core.config uses a module listed above it, which is the healthy direction.
12→25 trippy_core.net.socket uses trippy_core.net.platform.unix.socket part of a loop✕
- Connections
- 1 pair of types, where a type in trippy_core.net.socket uses a type in trippy_core.net.platform.unix.socket.
- The types involved
trippy_core.net.socket.Socket→trippy_core.net.platform.unix.socket.RecvFrom
- Direction
- trippy_core.net.socket uses trippy_core.net.platform.unix.socket, so a change to trippy_core.net.platform.unix.socket can break trippy_core.net.socket, while a change to trippy_core.net.socket can't break trippy_core.net.platform.unix.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.
13→2 trippy_core.probe uses trippy_core.types✕
- Connections
- 23 pairs of types, where a type in trippy_core.probe uses a type in trippy_core.types.
- The types involved
trippy_core.probe.IcmpProtocolResponse→trippy_core.types.TypeOfServicetrippy_core.probe.Probe→trippy_core.types.Checksumtrippy_core.probe.Probe→trippy_core.types.Flagstrippy_core.probe.Probe→trippy_core.types.Porttrippy_core.probe.Probe→trippy_core.types.RoundIdtrippy_core.probe.Probe→trippy_core.types.Sequencetrippy_core.probe.Probe→trippy_core.types.TimeToLivetrippy_core.probe.Probe→trippy_core.types.TraceIdtrippy_core.probe.Probe→trippy_core.types.TypeOfServicetrippy_core.probe.ProbeComplete→trippy_core.types.Checksumtrippy_core.probe.ProbeComplete→trippy_core.types.Porttrippy_core.probe.ProbeComplete→trippy_core.types.RoundIdtrippy_core.probe.ProbeComplete→trippy_core.types.Sequencetrippy_core.probe.ProbeComplete→trippy_core.types.TimeToLivetrippy_core.probe.ProbeComplete→trippy_core.types.TraceIdtrippy_core.probe.ProbeComplete→trippy_core.types.TypeOfServicetrippy_core.probe.ProbeFailed→trippy_core.types.Porttrippy_core.probe.ProbeFailed→trippy_core.types.RoundIdtrippy_core.probe.ProbeFailed→trippy_core.types.Sequencetrippy_core.probe.ProbeFailed→trippy_core.types.TimeToLivetrippy_core.probe.ProbeFailed→trippy_core.types.TraceIdtrippy_core.probe.TcpProtocolResponse→trippy_core.types.TypeOfServicetrippy_core.probe.UdpProtocolResponse→trippy_core.types.TypeOfService
- Direction
- trippy_core.probe uses trippy_core.types, so a change to trippy_core.types can break trippy_core.probe, while a change to trippy_core.probe can't break trippy_core.types.
- Position
- Below the diagonal: trippy_core.probe uses a module listed above it, which is the healthy direction.
14→3 trippy_dns.lazy_resolver uses trippy_dns.resolver✕
- Connections
- 2 pairs of types, where a type in trippy_dns.lazy_resolver uses a type in trippy_dns.resolver.
- The types involved
trippy_dns.lazy_resolver.DnsResolver→trippy_dns.resolver.DnsEntrytrippy_dns.lazy_resolver.DnsResolver→trippy_dns.resolver.Resolver
- Direction
- trippy_dns.lazy_resolver uses trippy_dns.resolver, so a change to trippy_dns.resolver can break trippy_dns.lazy_resolver, while a change to trippy_dns.lazy_resolver can't break trippy_dns.resolver.
- Position
- Below the diagonal: trippy_dns.lazy_resolver uses a module listed above it, which is the healthy direction.
14→28 trippy_dns.lazy_resolver uses trippy_dns.config part of a loop✕
- Connections
- 1 pair of types, where a type in trippy_dns.lazy_resolver uses a type in trippy_dns.config.
- The types involved
trippy_dns.lazy_resolver.DnsResolver→trippy_dns.config.Config
- Direction
- trippy_dns.lazy_resolver uses trippy_dns.config, so a change to trippy_dns.config can break trippy_dns.lazy_resolver, while a change to trippy_dns.lazy_resolver can't break trippy_dns.config.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→5 trippy_packet.icmpv4 uses trippy_packet.buffer✕
- Connections
- 1 pair of types, where a type in trippy_packet.icmpv4 uses a type in trippy_packet.buffer.
- The types involved
trippy_packet.icmpv4.IcmpPacket→trippy_packet.buffer.Buffer
- Direction
- trippy_packet.icmpv4 uses trippy_packet.buffer, so a change to trippy_packet.buffer can break trippy_packet.icmpv4, while a change to trippy_packet.icmpv4 can't break trippy_packet.buffer.
- Position
- Below the diagonal: trippy_packet.icmpv4 uses a module listed above it, which is the healthy direction.
16→4 trippy_packet.ipv4 uses trippy_packet✕
- Connections
- 1 pair of types, where a type in trippy_packet.ipv4 uses a type in trippy_packet.
- The types involved
trippy_packet.ipv4.Ipv4Packet→trippy_packet.IpProtocol
- Direction
- trippy_packet.ipv4 uses trippy_packet, so a change to trippy_packet can break trippy_packet.ipv4, while a change to trippy_packet.ipv4 can't break trippy_packet.
- Position
- Below the diagonal: trippy_packet.ipv4 uses a module listed above it, which is the healthy direction.
16→5 trippy_packet.ipv4 uses trippy_packet.buffer✕
- Connections
- 1 pair of types, where a type in trippy_packet.ipv4 uses a type in trippy_packet.buffer.
- The types involved
trippy_packet.ipv4.Ipv4Packet→trippy_packet.buffer.Buffer
- Direction
- trippy_packet.ipv4 uses trippy_packet.buffer, so a change to trippy_packet.buffer can break trippy_packet.ipv4, while a change to trippy_packet.ipv4 can't break trippy_packet.buffer.
- Position
- Below the diagonal: trippy_packet.ipv4 uses a module listed above it, which is the healthy direction.
17→4 trippy_packet.ipv6 uses trippy_packet✕
- Connections
- 1 pair of types, where a type in trippy_packet.ipv6 uses a type in trippy_packet.
- The types involved
trippy_packet.ipv6.Ipv6Packet→trippy_packet.IpProtocol
- Direction
- trippy_packet.ipv6 uses trippy_packet, so a change to trippy_packet can break trippy_packet.ipv6, while a change to trippy_packet.ipv6 can't break trippy_packet.
- Position
- Below the diagonal: trippy_packet.ipv6 uses a module listed above it, which is the healthy direction.
17→5 trippy_packet.ipv6 uses trippy_packet.buffer✕
- Connections
- 1 pair of types, where a type in trippy_packet.ipv6 uses a type in trippy_packet.buffer.
- The types involved
trippy_packet.ipv6.Ipv6Packet→trippy_packet.buffer.Buffer
- Direction
- trippy_packet.ipv6 uses trippy_packet.buffer, so a change to trippy_packet.buffer can break trippy_packet.ipv6, while a change to trippy_packet.ipv6 can't break trippy_packet.buffer.
- Position
- Below the diagonal: trippy_packet.ipv6 uses a module listed above it, which is the healthy direction.
18→6 trippy_tui.config.file uses trippy_tui.config.binding✕
- Connections
- 1 pair of types, where a type in trippy_tui.config.file uses a type in trippy_tui.config.binding.
- The types involved
trippy_tui.config.file.ConfigBindings→trippy_tui.config.binding.TuiKeyBinding
- Direction
- trippy_tui.config.file uses trippy_tui.config.binding, so a change to trippy_tui.config.binding can break trippy_tui.config.file, while a change to trippy_tui.config.file can't break trippy_tui.config.binding.
- Position
- Below the diagonal: trippy_tui.config.file uses a module listed above it, which is the healthy direction.
18→8 trippy_tui.config.file uses trippy_tui.config.theme✕
- Connections
- 1 pair of types, where a type in trippy_tui.config.file uses a type in trippy_tui.config.theme.
- The types involved
trippy_tui.config.file.ConfigThemeColors→trippy_tui.config.theme.TuiColor
- Direction
- trippy_tui.config.file uses trippy_tui.config.theme, so a change to trippy_tui.config.theme can break trippy_tui.config.file, while a change to trippy_tui.config.file can't break trippy_tui.config.theme.
- Position
- Below the diagonal: trippy_tui.config.file uses a module listed above it, which is the healthy direction.
18→29 trippy_tui.config.file uses trippy_tui.config part of a loop✕
- Connections
- 11 pairs of types, where a type in trippy_tui.config.file uses a type in trippy_tui.config.
- The types involved
trippy_tui.config.file.ConfigDns→trippy_tui.config.DnsResolveMethodConfigtrippy_tui.config.file.ConfigStrategy→trippy_tui.config.AddressFamilyConfigtrippy_tui.config.file.ConfigStrategy→trippy_tui.config.MultipathStrategyConfigtrippy_tui.config.file.ConfigStrategy→trippy_tui.config.ProtocolConfigtrippy_tui.config.file.ConfigTrippy→trippy_tui.config.LogFormattrippy_tui.config.file.ConfigTrippy→trippy_tui.config.LogSpanEventstrippy_tui.config.file.ConfigTrippy→trippy_tui.config.Modetrippy_tui.config.file.ConfigTui→trippy_tui.config.AddressModetrippy_tui.config.file.ConfigTui→trippy_tui.config.AsModetrippy_tui.config.file.ConfigTui→trippy_tui.config.GeoIpModetrippy_tui.config.file.ConfigTui→trippy_tui.config.IcmpExtensionMode
- Direction
- trippy_tui.config.file uses trippy_tui.config, so a change to trippy_tui.config can break trippy_tui.config.file, while a change to trippy_tui.config.file can't break trippy_tui.config.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→7 trippy_tui.frontend.columns uses trippy_tui.config.columns✕
- Connections
- 2 pairs of types, where a type in trippy_tui.frontend.columns uses a type in trippy_tui.config.columns.
- The types involved
trippy_tui.frontend.columns.Column→trippy_tui.config.columns.TuiColumntrippy_tui.frontend.columns.Columns→trippy_tui.config.columns.TuiColumns
- Direction
- trippy_tui.frontend.columns uses trippy_tui.config.columns, so a change to trippy_tui.config.columns can break trippy_tui.frontend.columns, while a change to trippy_tui.frontend.columns can't break trippy_tui.config.columns.
- Position
- Below the diagonal: trippy_tui.frontend.columns uses a module listed above it, which is the healthy direction.
20→8 trippy_tui.frontend.theme uses trippy_tui.config.theme✕
- Connections
- 1 pair of types, where a type in trippy_tui.frontend.theme uses a type in trippy_tui.config.theme.
- The types involved
trippy_tui.frontend.theme.Theme→trippy_tui.config.theme.TuiTheme
- Direction
- trippy_tui.frontend.theme uses trippy_tui.config.theme, so a change to trippy_tui.config.theme can break trippy_tui.frontend.theme, while a change to trippy_tui.frontend.theme can't break trippy_tui.config.theme.
- Position
- Below the diagonal: trippy_tui.frontend.theme uses a module listed above it, which is the healthy direction.
21→2 trippy_core.builder uses trippy_core.types✕
- Connections
- 8 pairs of types, where a type in trippy_core.builder uses a type in trippy_core.types.
- The types involved
trippy_core.builder.Builder→trippy_core.types.MaxInflighttrippy_core.builder.Builder→trippy_core.types.MaxRoundstrippy_core.builder.Builder→trippy_core.types.PacketSizetrippy_core.builder.Builder→trippy_core.types.PayloadPatterntrippy_core.builder.Builder→trippy_core.types.Sequencetrippy_core.builder.Builder→trippy_core.types.TimeToLivetrippy_core.builder.Builder→trippy_core.types.TraceIdtrippy_core.builder.Builder→trippy_core.types.TypeOfService
- Direction
- trippy_core.builder uses trippy_core.types, so a change to trippy_core.types can break trippy_core.builder, while a change to trippy_core.builder can't break trippy_core.types.
- Position
- Below the diagonal: trippy_core.builder uses a module listed above it, which is the healthy direction.
21→11 trippy_core.builder uses trippy_core.config✕
- Connections
- 5 pairs of types, where a type in trippy_core.builder uses a type in trippy_core.config.
- The types involved
trippy_core.builder.Builder→trippy_core.config.IcmpExtensionParseModetrippy_core.builder.Builder→trippy_core.config.MultipathStrategytrippy_core.builder.Builder→trippy_core.config.PortDirectiontrippy_core.builder.Builder→trippy_core.config.PrivilegeModetrippy_core.builder.Builder→trippy_core.config.Protocol
- Direction
- trippy_core.builder uses trippy_core.config, so a change to trippy_core.config can break trippy_core.builder, while a change to trippy_core.builder can't break trippy_core.config.
- Position
- Below the diagonal: trippy_core.builder uses a module listed above it, which is the healthy direction.
22→2 trippy_core.net.channel uses trippy_core.types✕
- Connections
- 1 pair of types, where a type in trippy_core.net.channel uses a type in trippy_core.types.
- The types involved
trippy_core.net.channel.TcpProbe→trippy_core.types.Port
- Direction
- trippy_core.net.channel uses trippy_core.types, so a change to trippy_core.types can break trippy_core.net.channel, while a change to trippy_core.net.channel can't break trippy_core.types.
- Position
- Below the diagonal: trippy_core.net.channel uses a module listed above it, which is the healthy direction.
22→11 trippy_core.net.channel uses trippy_core.config✕
- Connections
- 2 pairs of types, where a type in trippy_core.net.channel uses a type in trippy_core.config.
- The types involved
trippy_core.net.channel.Channel→trippy_core.config.ChannelConfigtrippy_core.net.channel.Channel→trippy_core.config.Protocol
- Direction
- trippy_core.net.channel uses trippy_core.config, so a change to trippy_core.config can break trippy_core.net.channel, while a change to trippy_core.net.channel can't break trippy_core.config.
- Position
- Below the diagonal: trippy_core.net.channel uses a module listed above it, which is the healthy direction.
22→13 trippy_core.net.channel uses trippy_core.probe✕
- Connections
- 1 pair of types, where a type in trippy_core.net.channel uses a type in trippy_core.probe.
- The types involved
trippy_core.net.channel.Channel→trippy_core.probe.Probe
- Direction
- trippy_core.net.channel uses trippy_core.probe, so a change to trippy_core.probe can break trippy_core.net.channel, while a change to trippy_core.net.channel can't break trippy_core.probe.
- Position
- Below the diagonal: trippy_core.net.channel uses a module listed above it, which is the healthy direction.
23→2 trippy_core.net.ipv4 uses trippy_core.types✕
- Connections
- 6 pairs of types, where a type in trippy_core.net.ipv4 uses a type in trippy_core.types.
- The types involved
trippy_core.net.ipv4.Ipv4→trippy_core.types.PacketSizetrippy_core.net.ipv4.Ipv4→trippy_core.types.PayloadPatterntrippy_core.net.ipv4.Ipv4→trippy_core.types.Porttrippy_core.net.ipv4.Ipv4→trippy_core.types.Sequencetrippy_core.net.ipv4.Ipv4→trippy_core.types.TraceIdtrippy_core.net.ipv4.Ipv4→trippy_core.types.TypeOfService
- Direction
- trippy_core.net.ipv4 uses trippy_core.types, so a change to trippy_core.types can break trippy_core.net.ipv4, while a change to trippy_core.net.ipv4 can't break trippy_core.types.
- Position
- Below the diagonal: trippy_core.net.ipv4 uses a module listed above it, which is the healthy direction.
23→4 trippy_core.net.ipv4 uses trippy_packet✕
- Connections
- 1 pair of types, where a type in trippy_core.net.ipv4 uses a type in trippy_packet.
- The types involved
trippy_core.net.ipv4.Ipv4→trippy_packet.IpProtocol
- Direction
- trippy_core.net.ipv4 uses trippy_packet, so a change to trippy_packet can break trippy_core.net.ipv4, while a change to trippy_core.net.ipv4 can't break trippy_packet.
- Position
- Below the diagonal: trippy_core.net.ipv4 uses a module listed above it, which is the healthy direction.
23→11 trippy_core.net.ipv4 uses trippy_core.config✕
- Connections
- 3 pairs of types, where a type in trippy_core.net.ipv4 uses a type in trippy_core.config.
- The types involved
trippy_core.net.ipv4.Ipv4→trippy_core.config.IcmpExtensionParseModetrippy_core.net.ipv4.Ipv4→trippy_core.config.PrivilegeModetrippy_core.net.ipv4.Ipv4→trippy_core.config.Protocol
- Direction
- trippy_core.net.ipv4 uses trippy_core.config, so a change to trippy_core.config can break trippy_core.net.ipv4, while a change to trippy_core.net.ipv4 can't break trippy_core.config.
- Position
- Below the diagonal: trippy_core.net.ipv4 uses a module listed above it, which is the healthy direction.
23→13 trippy_core.net.ipv4 uses trippy_core.probe✕
- Connections
- 1 pair of types, where a type in trippy_core.net.ipv4 uses a type in trippy_core.probe.
- The types involved
trippy_core.net.ipv4.Ipv4→trippy_core.probe.Probe
- Direction
- trippy_core.net.ipv4 uses trippy_core.probe, so a change to trippy_core.probe can break trippy_core.net.ipv4, while a change to trippy_core.net.ipv4 can't break trippy_core.probe.
- Position
- Below the diagonal: trippy_core.net.ipv4 uses a module listed above it, which is the healthy direction.
23→16 trippy_core.net.ipv4 uses trippy_packet.ipv4✕
- Connections
- 2 pairs of types, where a type in trippy_core.net.ipv4 uses a type in trippy_packet.ipv4.
- The types involved
trippy_core.net.ipv4.Ipv4→trippy_packet.ipv4.Ipv4Packettrippy_core.net.ipv4.ipv4$module→trippy_packet.ipv4.Ipv4Packet
- Direction
- trippy_core.net.ipv4 uses trippy_packet.ipv4, so a change to trippy_packet.ipv4 can break trippy_core.net.ipv4, while a change to trippy_core.net.ipv4 can't break trippy_packet.ipv4.
- Position
- Below the diagonal: trippy_core.net.ipv4 uses a module listed above it, which is the healthy direction.
24→2 trippy_core.net.ipv6 uses trippy_core.types✕
- Connections
- 6 pairs of types, where a type in trippy_core.net.ipv6 uses a type in trippy_core.types.
- The types involved
trippy_core.net.ipv6.Ipv6→trippy_core.types.PacketSizetrippy_core.net.ipv6.Ipv6→trippy_core.types.PayloadPatterntrippy_core.net.ipv6.Ipv6→trippy_core.types.Porttrippy_core.net.ipv6.Ipv6→trippy_core.types.Sequencetrippy_core.net.ipv6.Ipv6→trippy_core.types.TraceIdtrippy_core.net.ipv6.Ipv6→trippy_core.types.TypeOfService
- Direction
- trippy_core.net.ipv6 uses trippy_core.types, so a change to trippy_core.types can break trippy_core.net.ipv6, while a change to trippy_core.net.ipv6 can't break trippy_core.types.
- Position
- Below the diagonal: trippy_core.net.ipv6 uses a module listed above it, which is the healthy direction.
24→11 trippy_core.net.ipv6 uses trippy_core.config✕
- Connections
- 3 pairs of types, where a type in trippy_core.net.ipv6 uses a type in trippy_core.config.
- The types involved
trippy_core.net.ipv6.Ipv6→trippy_core.config.IcmpExtensionParseModetrippy_core.net.ipv6.Ipv6→trippy_core.config.PrivilegeModetrippy_core.net.ipv6.Ipv6→trippy_core.config.Protocol
- Direction
- trippy_core.net.ipv6 uses trippy_core.config, so a change to trippy_core.config can break trippy_core.net.ipv6, while a change to trippy_core.net.ipv6 can't break trippy_core.config.
- Position
- Below the diagonal: trippy_core.net.ipv6 uses a module listed above it, which is the healthy direction.
24→13 trippy_core.net.ipv6 uses trippy_core.probe✕
- Connections
- 1 pair of types, where a type in trippy_core.net.ipv6 uses a type in trippy_core.probe.
- The types involved
trippy_core.net.ipv6.Ipv6→trippy_core.probe.Probe
- Direction
- trippy_core.net.ipv6 uses trippy_core.probe, so a change to trippy_core.probe can break trippy_core.net.ipv6, while a change to trippy_core.net.ipv6 can't break trippy_core.probe.
- Position
- Below the diagonal: trippy_core.net.ipv6 uses a module listed above it, which is the healthy direction.
24→15 trippy_core.net.ipv6 uses trippy_packet.icmpv4✕
- Connections
- 1 pair of types, where a type in trippy_core.net.ipv6 uses a type in trippy_packet.icmpv4.
- The types involved
trippy_core.net.ipv6.Ipv6→trippy_packet.icmpv4.IcmpPacket
- Direction
- trippy_core.net.ipv6 uses trippy_packet.icmpv4, so a change to trippy_packet.icmpv4 can break trippy_core.net.ipv6, while a change to trippy_core.net.ipv6 can't break trippy_packet.icmpv4.
- Position
- Below the diagonal: trippy_core.net.ipv6 uses a module listed above it, which is the healthy direction.
24→17 trippy_core.net.ipv6 uses trippy_packet.ipv6✕
- Connections
- 2 pairs of types, where a type in trippy_core.net.ipv6 uses a type in trippy_packet.ipv6.
- The types involved
trippy_core.net.ipv6.Ipv6→trippy_packet.ipv6.Ipv6Packettrippy_core.net.ipv6.ipv6$module→trippy_packet.ipv6.Ipv6Packet
- Direction
- trippy_core.net.ipv6 uses trippy_packet.ipv6, so a change to trippy_packet.ipv6 can break trippy_core.net.ipv6, while a change to trippy_core.net.ipv6 can't break trippy_packet.ipv6.
- Position
- Below the diagonal: trippy_core.net.ipv6 uses a module listed above it, which is the healthy direction.
25→11 trippy_core.net.platform.unix.socket uses trippy_core.config✕
- Connections
- 1 pair of types, where a type in trippy_core.net.platform.unix.socket uses a type in trippy_core.config.
- The types involved
trippy_core.net.platform.unix.socket.SocketImpl→trippy_core.config.Protocol
- Direction
- trippy_core.net.platform.unix.socket uses trippy_core.config, so a change to trippy_core.config can break trippy_core.net.platform.unix.socket, while a change to trippy_core.net.platform.unix.socket can't break trippy_core.config.
- Position
- Below the diagonal: trippy_core.net.platform.unix.socket uses a module listed above it, which is the healthy direction.
25→12 trippy_core.net.platform.unix.socket uses trippy_core.net.socket✕
- Connections
- 1 pair of types, where a type in trippy_core.net.platform.unix.socket uses a type in trippy_core.net.socket.
- The types involved
trippy_core.net.platform.unix.socket.SocketImpl→trippy_core.net.socket.Socket
- Direction
- trippy_core.net.platform.unix.socket uses trippy_core.net.socket, so a change to trippy_core.net.socket can break trippy_core.net.platform.unix.socket, while a change to trippy_core.net.platform.unix.socket can't break trippy_core.net.socket.
- Position
- Below the diagonal: trippy_core.net.platform.unix.socket uses a module listed above it, which is the healthy direction.
26→11 trippy_core.net.platform.windows uses trippy_core.config✕
- Connections
- 1 pair of types, where a type in trippy_core.net.platform.windows uses a type in trippy_core.config.
- The types involved
trippy_core.net.platform.windows.SocketImpl→trippy_core.config.Protocol
- Direction
- trippy_core.net.platform.windows uses trippy_core.config, so a change to trippy_core.config can break trippy_core.net.platform.windows, while a change to trippy_core.net.platform.windows can't break trippy_core.config.
- Position
- Below the diagonal: trippy_core.net.platform.windows uses a module listed above it, which is the healthy direction.
26→12 trippy_core.net.platform.windows uses trippy_core.net.socket✕
- Connections
- 1 pair of types, where a type in trippy_core.net.platform.windows uses a type in trippy_core.net.socket.
- The types involved
trippy_core.net.platform.windows.SocketImpl→trippy_core.net.socket.Socket
- Direction
- trippy_core.net.platform.windows uses trippy_core.net.socket, so a change to trippy_core.net.socket can break trippy_core.net.platform.windows, while a change to trippy_core.net.platform.windows can't break trippy_core.net.socket.
- Position
- Below the diagonal: trippy_core.net.platform.windows uses a module listed above it, which is the healthy direction.
27→2 trippy_core.strategy.state uses trippy_core.types✕
- Connections
- 4 pairs of types, where a type in trippy_core.strategy.state uses a type in trippy_core.types.
- The types involved
trippy_core.strategy.state.TracerState→trippy_core.types.MaxRoundstrippy_core.strategy.state.TracerState→trippy_core.types.RoundIdtrippy_core.strategy.state.TracerState→trippy_core.types.Sequencetrippy_core.strategy.state.TracerState→trippy_core.types.TimeToLive
- Direction
- trippy_core.strategy.state uses trippy_core.types, so a change to trippy_core.types can break trippy_core.strategy.state, while a change to trippy_core.strategy.state can't break trippy_core.types.
- Position
- Below the diagonal: trippy_core.strategy.state uses a module listed above it, which is the healthy direction.
27→11 trippy_core.strategy.state uses trippy_core.config✕
- Connections
- 1 pair of types, where a type in trippy_core.strategy.state uses a type in trippy_core.config.
- The types involved
trippy_core.strategy.state.TracerState→trippy_core.config.StrategyConfig
- Direction
- trippy_core.strategy.state uses trippy_core.config, so a change to trippy_core.config can break trippy_core.strategy.state, while a change to trippy_core.strategy.state can't break trippy_core.config.
- Position
- Below the diagonal: trippy_core.strategy.state uses a module listed above it, which is the healthy direction.
27→13 trippy_core.strategy.state uses trippy_core.probe✕
- Connections
- 2 pairs of types, where a type in trippy_core.strategy.state uses a type in trippy_core.probe.
- The types involved
trippy_core.strategy.state.TracerState→trippy_core.probe.Probetrippy_core.strategy.state.TracerState→trippy_core.probe.ProbeStatus
- Direction
- trippy_core.strategy.state uses trippy_core.probe, so a change to trippy_core.probe can break trippy_core.strategy.state, while a change to trippy_core.strategy.state can't break trippy_core.probe.
- Position
- Below the diagonal: trippy_core.strategy.state uses a module listed above it, which is the healthy direction.
27→30 trippy_core.strategy.state uses trippy_core.strategy part of a loop✕
- Connections
- 2 pairs of types, where a type in trippy_core.strategy.state uses a type in trippy_core.strategy.
- The types involved
trippy_core.strategy.state.TracerState→trippy_core.strategy.Actiontrippy_core.strategy.state.TracerState→trippy_core.strategy.StrategyResponse
- Direction
- trippy_core.strategy.state uses trippy_core.strategy, so a change to trippy_core.strategy can break trippy_core.strategy.state, while a change to trippy_core.strategy.state can't break trippy_core.strategy.
- 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.
28→14 trippy_dns.config uses trippy_dns.lazy_resolver✕
- Connections
- 4 pairs of types, where a type in trippy_dns.config uses a type in trippy_dns.lazy_resolver.
- The types involved
trippy_dns.config.Builder→trippy_dns.lazy_resolver.IpAddrFamilytrippy_dns.config.Builder→trippy_dns.lazy_resolver.ResolveMethodtrippy_dns.config.Config→trippy_dns.lazy_resolver.IpAddrFamilytrippy_dns.config.Config→trippy_dns.lazy_resolver.ResolveMethod
- Direction
- trippy_dns.config uses trippy_dns.lazy_resolver, so a change to trippy_dns.lazy_resolver can break trippy_dns.config, while a change to trippy_dns.config can't break trippy_dns.lazy_resolver.
- Position
- Below the diagonal: trippy_dns.config uses a module listed above it, which is the healthy direction.
29→6 trippy_tui.config uses trippy_tui.config.binding✕
- Connections
- 2 pairs of types, where a type in trippy_tui.config uses a type in trippy_tui.config.binding.
- The types involved
trippy_tui.config.TrippyConfig→trippy_tui.config.binding.TuiBindingstrippy_tui.config.config$module→trippy_tui.config.binding.TuiBindings
- Direction
- trippy_tui.config uses trippy_tui.config.binding, so a change to trippy_tui.config.binding can break trippy_tui.config, while a change to trippy_tui.config can't break trippy_tui.config.binding.
- Position
- Below the diagonal: trippy_tui.config uses a module listed above it, which is the healthy direction.
29→7 trippy_tui.config uses trippy_tui.config.columns✕
- Connections
- 2 pairs of types, where a type in trippy_tui.config uses a type in trippy_tui.config.columns.
- The types involved
trippy_tui.config.TrippyConfig→trippy_tui.config.columns.TuiColumnstrippy_tui.config.config$module→trippy_tui.config.columns.TuiColumns
- Direction
- trippy_tui.config uses trippy_tui.config.columns, so a change to trippy_tui.config.columns can break trippy_tui.config, while a change to trippy_tui.config can't break trippy_tui.config.columns.
- Position
- Below the diagonal: trippy_tui.config uses a module listed above it, which is the healthy direction.
29→8 trippy_tui.config uses trippy_tui.config.theme✕
- Connections
- 1 pair of types, where a type in trippy_tui.config uses a type in trippy_tui.config.theme.
- The types involved
trippy_tui.config.TrippyConfig→trippy_tui.config.theme.TuiTheme
- Direction
- trippy_tui.config uses trippy_tui.config.theme, so a change to trippy_tui.config.theme can break trippy_tui.config, while a change to trippy_tui.config can't break trippy_tui.config.theme.
- Position
- Below the diagonal: trippy_tui.config uses a module listed above it, which is the healthy direction.
29→11 trippy_tui.config uses trippy_core.config✕
- Connections
- 10 pairs of types, where a type in trippy_tui.config uses a type in trippy_core.config.
- The types involved
trippy_tui.config.MultipathStrategyConfig→trippy_core.config.MultipathStrategytrippy_tui.config.ProtocolConfig→trippy_core.config.Protocoltrippy_tui.config.TrippyConfig→trippy_core.config.IcmpExtensionParseModetrippy_tui.config.TrippyConfig→trippy_core.config.MultipathStrategytrippy_tui.config.TrippyConfig→trippy_core.config.PortDirectiontrippy_tui.config.TrippyConfig→trippy_core.config.PrivilegeModetrippy_tui.config.TrippyConfig→trippy_core.config.Protocoltrippy_tui.config.config$module→trippy_core.config.MultipathStrategytrippy_tui.config.config$module→trippy_core.config.PrivilegeModetrippy_tui.config.config$module→trippy_core.config.Protocol
- Direction
- trippy_tui.config uses trippy_core.config, so a change to trippy_core.config can break trippy_tui.config, while a change to trippy_tui.config can't break trippy_core.config.
- Position
- Below the diagonal: trippy_tui.config uses a module listed above it, which is the healthy direction.
29→14 trippy_tui.config uses trippy_dns.lazy_resolver✕
- Connections
- 5 pairs of types, where a type in trippy_tui.config uses a type in trippy_dns.lazy_resolver.
- The types involved
trippy_tui.config.AddressFamilyConfig→trippy_dns.lazy_resolver.IpAddrFamilytrippy_tui.config.TrippyConfig→trippy_dns.lazy_resolver.IpAddrFamilytrippy_tui.config.TrippyConfig→trippy_dns.lazy_resolver.ResolveMethodtrippy_tui.config.config$module→trippy_dns.lazy_resolver.IpAddrFamilytrippy_tui.config.config$module→trippy_dns.lazy_resolver.ResolveMethod
- Direction
- trippy_tui.config uses trippy_dns.lazy_resolver, so a change to trippy_dns.lazy_resolver can break trippy_tui.config, while a change to trippy_tui.config can't break trippy_dns.lazy_resolver.
- Position
- Below the diagonal: trippy_tui.config uses a module listed above it, which is the healthy direction.
29→18 trippy_tui.config uses trippy_tui.config.file✕
- Connections
- 3 pairs of types, where a type in trippy_tui.config uses a type in trippy_tui.config.file.
- The types involved
trippy_tui.config.TrippyConfig→trippy_tui.config.file.ConfigFiletrippy_tui.config.config$module→trippy_tui.config.file.ConfigBindingstrippy_tui.config.config$module→trippy_tui.config.file.ConfigTui
- Direction
- trippy_tui.config uses trippy_tui.config.file, so a change to trippy_tui.config.file can break trippy_tui.config, while a change to trippy_tui.config can't break trippy_tui.config.file.
- Position
- Below the diagonal: trippy_tui.config uses a module listed above it, which is the healthy direction.
30→2 trippy_core.strategy uses trippy_core.types✕
- Connections
- 10 pairs of types, where a type in trippy_core.strategy uses a type in trippy_core.types.
- The types involved
trippy_core.strategy.ProtocolStrategyResponse→trippy_core.types.Checksumtrippy_core.strategy.ProtocolStrategyResponse→trippy_core.types.Sequencetrippy_core.strategy.ProtocolStrategyResponse→trippy_core.types.TraceIdtrippy_core.strategy.ProtocolStrategyResponse→trippy_core.types.TypeOfServicetrippy_core.strategy.Round→trippy_core.types.TimeToLivetrippy_core.strategy.Strategy→trippy_core.types.TraceIdtrippy_core.strategy.StrategyResponse→trippy_core.types.Checksumtrippy_core.strategy.StrategyResponse→trippy_core.types.Sequencetrippy_core.strategy.StrategyResponse→trippy_core.types.TraceIdtrippy_core.strategy.StrategyResponse→trippy_core.types.TypeOfService
- Direction
- trippy_core.strategy uses trippy_core.types, so a change to trippy_core.types can break trippy_core.strategy, while a change to trippy_core.strategy can't break trippy_core.types.
- Position
- Below the diagonal: trippy_core.strategy uses a module listed above it, which is the healthy direction.
30→11 trippy_core.strategy uses trippy_core.config✕
- Connections
- 1 pair of types, where a type in trippy_core.strategy uses a type in trippy_core.config.
- The types involved
trippy_core.strategy.Strategy→trippy_core.config.StrategyConfig
- Direction
- trippy_core.strategy uses trippy_core.config, so a change to trippy_core.config can break trippy_core.strategy, while a change to trippy_core.strategy can't break trippy_core.config.
- Position
- Below the diagonal: trippy_core.strategy uses a module listed above it, which is the healthy direction.
30→13 trippy_core.strategy uses trippy_core.probe✕
- Connections
- 4 pairs of types, where a type in trippy_core.strategy uses a type in trippy_core.probe.
- The types involved
trippy_core.strategy.Strategy→trippy_core.probe.Probetrippy_core.strategy.Strategy→trippy_core.probe.ResponseDatatrippy_core.strategy.StrategyResponse→trippy_core.probe.Extensionstrippy_core.strategy.StrategyResponse→trippy_core.probe.IcmpPacketType
- Direction
- trippy_core.strategy uses trippy_core.probe, so a change to trippy_core.probe can break trippy_core.strategy, while a change to trippy_core.strategy can't break trippy_core.probe.
- Position
- Below the diagonal: trippy_core.strategy uses a module listed above it, which is the healthy direction.
30→27 trippy_core.strategy uses trippy_core.strategy.state✕
- Connections
- 1 pair of types, where a type in trippy_core.strategy uses a type in trippy_core.strategy.state.
- The types involved
trippy_core.strategy.Strategy→trippy_core.strategy.state.TracerState
- Direction
- trippy_core.strategy uses trippy_core.strategy.state, so a change to trippy_core.strategy.state can break trippy_core.strategy, while a change to trippy_core.strategy can't break trippy_core.strategy.state.
- Position
- Below the diagonal: trippy_core.strategy uses a module listed above it, which is the healthy direction.
31→6 trippy_tui.frontend.config uses trippy_tui.config.binding✕
- Connections
- 1 pair of types, where a type in trippy_tui.frontend.config uses a type in trippy_tui.config.binding.
- The types involved
trippy_tui.frontend.config.TuiConfig→trippy_tui.config.binding.TuiBindings
- Direction
- trippy_tui.frontend.config uses trippy_tui.config.binding, so a change to trippy_tui.config.binding can break trippy_tui.frontend.config, while a change to trippy_tui.frontend.config can't break trippy_tui.config.binding.
- Position
- Below the diagonal: trippy_tui.frontend.config uses a module listed above it, which is the healthy direction.
31→7 trippy_tui.frontend.config uses trippy_tui.config.columns✕
- Connections
- 1 pair of types, where a type in trippy_tui.frontend.config uses a type in trippy_tui.config.columns.
- The types involved
trippy_tui.frontend.config.TuiConfig→trippy_tui.config.columns.TuiColumns
- Direction
- trippy_tui.frontend.config uses trippy_tui.config.columns, so a change to trippy_tui.config.columns can break trippy_tui.frontend.config, while a change to trippy_tui.frontend.config can't break trippy_tui.config.columns.
- Position
- Below the diagonal: trippy_tui.frontend.config uses a module listed above it, which is the healthy direction.
31→8 trippy_tui.frontend.config uses trippy_tui.config.theme✕
- Connections
- 1 pair of types, where a type in trippy_tui.frontend.config uses a type in trippy_tui.config.theme.
- The types involved
trippy_tui.frontend.config.TuiConfig→trippy_tui.config.theme.TuiTheme
- Direction
- trippy_tui.frontend.config uses trippy_tui.config.theme, so a change to trippy_tui.config.theme can break trippy_tui.frontend.config, while a change to trippy_tui.frontend.config can't break trippy_tui.config.theme.
- Position
- Below the diagonal: trippy_tui.frontend.config uses a module listed above it, which is the healthy direction.
31→19 trippy_tui.frontend.config uses trippy_tui.frontend.columns✕
- Connections
- 1 pair of types, where a type in trippy_tui.frontend.config uses a type in trippy_tui.frontend.columns.
- The types involved
trippy_tui.frontend.config.TuiConfig→trippy_tui.frontend.columns.Columns
- Direction
- trippy_tui.frontend.config uses trippy_tui.frontend.columns, so a change to trippy_tui.frontend.columns can break trippy_tui.frontend.config, while a change to trippy_tui.frontend.config can't break trippy_tui.frontend.columns.
- Position
- Below the diagonal: trippy_tui.frontend.config uses a module listed above it, which is the healthy direction.
31→20 trippy_tui.frontend.config uses trippy_tui.frontend.theme✕
- Connections
- 1 pair of types, where a type in trippy_tui.frontend.config uses a type in trippy_tui.frontend.theme.
- The types involved
trippy_tui.frontend.config.TuiConfig→trippy_tui.frontend.theme.Theme
- Direction
- trippy_tui.frontend.config uses trippy_tui.frontend.theme, so a change to trippy_tui.frontend.theme can break trippy_tui.frontend.config, while a change to trippy_tui.frontend.config can't break trippy_tui.frontend.theme.
- Position
- Below the diagonal: trippy_tui.frontend.config uses a module listed above it, which is the healthy direction.
31→29 trippy_tui.frontend.config uses trippy_tui.config✕
- Connections
- 4 pairs of types, where a type in trippy_tui.frontend.config uses a type in trippy_tui.config.
- The types involved
trippy_tui.frontend.config.TuiConfig→trippy_tui.config.AddressModetrippy_tui.frontend.config.TuiConfig→trippy_tui.config.AsModetrippy_tui.frontend.config.TuiConfig→trippy_tui.config.GeoIpModetrippy_tui.frontend.config.TuiConfig→trippy_tui.config.IcmpExtensionMode
- Direction
- trippy_tui.frontend.config uses trippy_tui.config, so a change to trippy_tui.config can break trippy_tui.frontend.config, while a change to trippy_tui.frontend.config can't break trippy_tui.config.
- Position
- Below the diagonal: trippy_tui.frontend.config uses a module listed above it, which is the healthy direction.
32→2 trippy_core.state uses trippy_core.types✕
- Connections
- 5 pairs of types, where a type in trippy_core.state uses a type in trippy_core.types.
- The types involved
trippy_core.state.FlowState→trippy_core.types.RoundIdtrippy_core.state.FlowState→trippy_core.types.TimeToLivetrippy_core.state.Hop→trippy_core.types.Dscptrippy_core.state.Hop→trippy_core.types.Ecntrippy_core.state.Hop→trippy_core.types.TypeOfService
- Direction
- trippy_core.state uses trippy_core.types, so a change to trippy_core.types can break trippy_core.state, while a change to trippy_core.state can't break trippy_core.types.
- Position
- Below the diagonal: trippy_core.state uses a module listed above it, which is the healthy direction.
32→11 trippy_core.state uses trippy_core.config✕
- Connections
- 1 pair of types, where a type in trippy_core.state uses a type in trippy_core.config.
- The types involved
trippy_core.state.State→trippy_core.config.StateConfig
- Direction
- trippy_core.state uses trippy_core.config, so a change to trippy_core.config can break trippy_core.state, while a change to trippy_core.state can't break trippy_core.config.
- Position
- Below the diagonal: trippy_core.state uses a module listed above it, which is the healthy direction.
32→13 trippy_core.state uses trippy_core.probe✕
- Connections
- 2 pairs of types, where a type in trippy_core.state uses a type in trippy_core.probe.
- The types involved
trippy_core.state.Hop→trippy_core.probe.Extensionstrippy_core.state.Hop→trippy_core.probe.IcmpPacketType
- Direction
- trippy_core.state uses trippy_core.probe, so a change to trippy_core.probe can break trippy_core.state, while a change to trippy_core.state can't break trippy_core.probe.
- Position
- Below the diagonal: trippy_core.state uses a module listed above it, which is the healthy direction.
32→30 trippy_core.state uses trippy_core.strategy✕
- Connections
- 2 pairs of types, where a type in trippy_core.state uses a type in trippy_core.strategy.
- The types involved
trippy_core.state.FlowState→trippy_core.strategy.Roundtrippy_core.state.State→trippy_core.strategy.Round
- Direction
- trippy_core.state uses trippy_core.strategy, so a change to trippy_core.strategy can break trippy_core.state, while a change to trippy_core.state can't break trippy_core.strategy.
- Position
- Below the diagonal: trippy_core.state uses a module listed above it, which is the healthy direction.
33→2 trippy_core.state.state_updater uses trippy_core.types✕
- Connections
- 2 pairs of types, where a type in trippy_core.state.state_updater uses a type in trippy_core.types.
- The types involved
trippy_core.state.state_updater.state_updater$module→trippy_core.types.Checksumtrippy_core.state.state_updater.state_updater$module→trippy_core.types.TimeToLive
- Direction
- trippy_core.state.state_updater uses trippy_core.types, so a change to trippy_core.types can break trippy_core.state.state_updater, while a change to trippy_core.state.state_updater can't break trippy_core.types.
- Position
- Below the diagonal: trippy_core.state.state_updater uses a module listed above it, which is the healthy direction.
33→13 trippy_core.state.state_updater uses trippy_core.probe✕
- Connections
- 1 pair of types, where a type in trippy_core.state.state_updater uses a type in trippy_core.probe.
- The types involved
trippy_core.state.state_updater.StateUpdater→trippy_core.probe.ProbeStatus
- Direction
- trippy_core.state.state_updater uses trippy_core.probe, so a change to trippy_core.probe can break trippy_core.state.state_updater, while a change to trippy_core.state.state_updater can't break trippy_core.probe.
- Position
- Below the diagonal: trippy_core.state.state_updater uses a module listed above it, which is the healthy direction.
33→30 trippy_core.state.state_updater uses trippy_core.strategy✕
- Connections
- 1 pair of types, where a type in trippy_core.state.state_updater uses a type in trippy_core.strategy.
- The types involved
trippy_core.state.state_updater.StateUpdater→trippy_core.strategy.Round
- Direction
- trippy_core.state.state_updater uses trippy_core.strategy, so a change to trippy_core.strategy can break trippy_core.state.state_updater, while a change to trippy_core.state.state_updater can't break trippy_core.strategy.
- Position
- Below the diagonal: trippy_core.state.state_updater uses a module listed above it, which is the healthy direction.
33→32 trippy_core.state.state_updater uses trippy_core.state✕
- Connections
- 1 pair of types, where a type in trippy_core.state.state_updater uses a type in trippy_core.state.
- The types involved
trippy_core.state.state_updater.StateUpdater→trippy_core.state.FlowState
- Direction
- trippy_core.state.state_updater uses trippy_core.state, so a change to trippy_core.state can break trippy_core.state.state_updater, while a change to trippy_core.state.state_updater can't break trippy_core.state.
- Position
- Below the diagonal: trippy_core.state.state_updater uses a module listed above it, which is the healthy direction.
34→1 trippy_core.tracer.inner uses trippy_core.error✕
- Connections
- 1 pair of types, where a type in trippy_core.tracer.inner uses a type in trippy_core.error.
- The types involved
trippy_core.tracer.inner.TracerInner→trippy_core.error.Error
- Direction
- trippy_core.tracer.inner uses trippy_core.error, so a change to trippy_core.error can break trippy_core.tracer.inner, while a change to trippy_core.tracer.inner can't break trippy_core.error.
- Position
- Below the diagonal: trippy_core.tracer.inner uses a module listed above it, which is the healthy direction.
34→2 trippy_core.tracer.inner uses trippy_core.types✕
- Connections
- 8 pairs of types, where a type in trippy_core.tracer.inner uses a type in trippy_core.types.
- The types involved
trippy_core.tracer.inner.TracerInner→trippy_core.types.MaxInflighttrippy_core.tracer.inner.TracerInner→trippy_core.types.MaxRoundstrippy_core.tracer.inner.TracerInner→trippy_core.types.PacketSizetrippy_core.tracer.inner.TracerInner→trippy_core.types.PayloadPatterntrippy_core.tracer.inner.TracerInner→trippy_core.types.Sequencetrippy_core.tracer.inner.TracerInner→trippy_core.types.TimeToLivetrippy_core.tracer.inner.TracerInner→trippy_core.types.TraceIdtrippy_core.tracer.inner.TracerInner→trippy_core.types.TypeOfService
- Direction
- trippy_core.tracer.inner uses trippy_core.types, so a change to trippy_core.types can break trippy_core.tracer.inner, while a change to trippy_core.tracer.inner can't break trippy_core.types.
- Position
- Below the diagonal: trippy_core.tracer.inner uses a module listed above it, which is the healthy direction.
34→11 trippy_core.tracer.inner uses trippy_core.config✕
- Connections
- 8 pairs of types, where a type in trippy_core.tracer.inner uses a type in trippy_core.config.
- The types involved
trippy_core.tracer.inner.TracerInner→trippy_core.config.ChannelConfigtrippy_core.tracer.inner.TracerInner→trippy_core.config.IcmpExtensionParseModetrippy_core.tracer.inner.TracerInner→trippy_core.config.MultipathStrategytrippy_core.tracer.inner.TracerInner→trippy_core.config.PortDirectiontrippy_core.tracer.inner.TracerInner→trippy_core.config.PrivilegeModetrippy_core.tracer.inner.TracerInner→trippy_core.config.Protocoltrippy_core.tracer.inner.TracerInner→trippy_core.config.StateConfigtrippy_core.tracer.inner.TracerInner→trippy_core.config.StrategyConfig
- Direction
- trippy_core.tracer.inner uses trippy_core.config, so a change to trippy_core.config can break trippy_core.tracer.inner, while a change to trippy_core.tracer.inner can't break trippy_core.config.
- Position
- Below the diagonal: trippy_core.tracer.inner uses a module listed above it, which is the healthy direction.
34→30 trippy_core.tracer.inner uses trippy_core.strategy✕
- Connections
- 1 pair of types, where a type in trippy_core.tracer.inner uses a type in trippy_core.strategy.
- The types involved
trippy_core.tracer.inner.TracerInner→trippy_core.strategy.Round
- Direction
- trippy_core.tracer.inner uses trippy_core.strategy, so a change to trippy_core.strategy can break trippy_core.tracer.inner, while a change to trippy_core.tracer.inner can't break trippy_core.strategy.
- Position
- Below the diagonal: trippy_core.tracer.inner uses a module listed above it, which is the healthy direction.
34→32 trippy_core.tracer.inner uses trippy_core.state✕
- Connections
- 1 pair of types, where a type in trippy_core.tracer.inner uses a type in trippy_core.state.
- The types involved
trippy_core.tracer.inner.TracerInner→trippy_core.state.State
- Direction
- trippy_core.tracer.inner uses trippy_core.state, so a change to trippy_core.state can break trippy_core.tracer.inner, while a change to trippy_core.tracer.inner can't break trippy_core.state.
- Position
- Below the diagonal: trippy_core.tracer.inner uses a module listed above it, which is the healthy direction.
35→2 trippy_core.tracer uses trippy_core.types✕
- Connections
- 8 pairs of types, where a type in trippy_core.tracer uses a type in trippy_core.types.
- The types involved
trippy_core.tracer.Tracer→trippy_core.types.MaxInflighttrippy_core.tracer.Tracer→trippy_core.types.MaxRoundstrippy_core.tracer.Tracer→trippy_core.types.PacketSizetrippy_core.tracer.Tracer→trippy_core.types.PayloadPatterntrippy_core.tracer.Tracer→trippy_core.types.Sequencetrippy_core.tracer.Tracer→trippy_core.types.TimeToLivetrippy_core.tracer.Tracer→trippy_core.types.TraceIdtrippy_core.tracer.Tracer→trippy_core.types.TypeOfService
- Direction
- trippy_core.tracer uses trippy_core.types, so a change to trippy_core.types can break trippy_core.tracer, while a change to trippy_core.tracer can't break trippy_core.types.
- Position
- Below the diagonal: trippy_core.tracer uses a module listed above it, which is the healthy direction.
35→11 trippy_core.tracer uses trippy_core.config✕
- Connections
- 5 pairs of types, where a type in trippy_core.tracer uses a type in trippy_core.config.
- The types involved
trippy_core.tracer.Tracer→trippy_core.config.IcmpExtensionParseModetrippy_core.tracer.Tracer→trippy_core.config.MultipathStrategytrippy_core.tracer.Tracer→trippy_core.config.PortDirectiontrippy_core.tracer.Tracer→trippy_core.config.PrivilegeModetrippy_core.tracer.Tracer→trippy_core.config.Protocol
- Direction
- trippy_core.tracer uses trippy_core.config, so a change to trippy_core.config can break trippy_core.tracer, while a change to trippy_core.tracer can't break trippy_core.config.
- Position
- Below the diagonal: trippy_core.tracer uses a module listed above it, which is the healthy direction.
35→32 trippy_core.tracer uses trippy_core.state✕
- Connections
- 1 pair of types, where a type in trippy_core.tracer uses a type in trippy_core.state.
- The types involved
trippy_core.tracer.Tracer→trippy_core.state.State
- Direction
- trippy_core.tracer uses trippy_core.state, so a change to trippy_core.state can break trippy_core.tracer, while a change to trippy_core.tracer can't break trippy_core.state.
- Position
- Below the diagonal: trippy_core.tracer uses a module listed above it, which is the healthy direction.
35→34 trippy_core.tracer uses trippy_core.tracer.inner✕
- Connections
- 1 pair of types, where a type in trippy_core.tracer uses a type in trippy_core.tracer.inner.
- The types involved
trippy_core.tracer.Tracer→trippy_core.tracer.inner.TracerInner
- Direction
- trippy_core.tracer uses trippy_core.tracer.inner, so a change to trippy_core.tracer.inner can break trippy_core.tracer, while a change to trippy_core.tracer can't break trippy_core.tracer.inner.
- Position
- Below the diagonal: trippy_core.tracer uses a module listed above it, which is the healthy direction.
36→9 trippy_tui.app uses trippy_tui.geoip✕
- Connections
- 1 pair of types, where a type in trippy_tui.app uses a type in trippy_tui.geoip.
- The types involved
trippy_tui.app.app$module→trippy_tui.geoip.GeoIpLookup
- Direction
- trippy_tui.app uses trippy_tui.geoip, so a change to trippy_tui.geoip can break trippy_tui.app, while a change to trippy_tui.app can't break trippy_tui.geoip.
- Position
- Below the diagonal: trippy_tui.app uses a module listed above it, which is the healthy direction.
36→14 trippy_tui.app uses trippy_dns.lazy_resolver✕
- Connections
- 1 pair of types, where a type in trippy_tui.app uses a type in trippy_dns.lazy_resolver.
- The types involved
trippy_tui.app.app$module→trippy_dns.lazy_resolver.DnsResolver
- Direction
- trippy_tui.app uses trippy_dns.lazy_resolver, so a change to trippy_dns.lazy_resolver can break trippy_tui.app, while a change to trippy_tui.app can't break trippy_dns.lazy_resolver.
- Position
- Below the diagonal: trippy_tui.app uses a module listed above it, which is the healthy direction.
36→29 trippy_tui.app uses trippy_tui.config✕
- Connections
- 1 pair of types, where a type in trippy_tui.app uses a type in trippy_tui.config.
- The types involved
trippy_tui.app.app$module→trippy_tui.config.TrippyConfig
- Direction
- trippy_tui.app uses trippy_tui.config, so a change to trippy_tui.config can break trippy_tui.app, while a change to trippy_tui.app can't break trippy_tui.config.
- Position
- Below the diagonal: trippy_tui.app uses a module listed above it, which is the healthy direction.
36→31 trippy_tui.app uses trippy_tui.frontend.config✕
- Connections
- 1 pair of types, where a type in trippy_tui.app uses a type in trippy_tui.frontend.config.
- The types involved
trippy_tui.app.app$module→trippy_tui.frontend.config.TuiConfig
- Direction
- trippy_tui.app uses trippy_tui.frontend.config, so a change to trippy_tui.frontend.config can break trippy_tui.app, while a change to trippy_tui.app can't break trippy_tui.frontend.config.
- Position
- Below the diagonal: trippy_tui.app uses a module listed above it, which is the healthy direction.
36→35 trippy_tui.app uses trippy_core.tracer✕
- Connections
- 2 pairs of types, where a type in trippy_tui.app uses a type in trippy_core.tracer.
- The types involved
trippy_tui.app.TraceInfo→trippy_core.tracer.Tracertrippy_tui.app.app$module→trippy_core.tracer.Tracer
- Direction
- trippy_tui.app uses trippy_core.tracer, so a change to trippy_core.tracer can break trippy_tui.app, while a change to trippy_tui.app can't break trippy_core.tracer.
- Position
- Below the diagonal: trippy_tui.app uses a module listed above it, which is the healthy direction.
37→9 trippy_tui.frontend.tui_app uses trippy_tui.geoip✕
- Connections
- 1 pair of types, where a type in trippy_tui.frontend.tui_app uses a type in trippy_tui.geoip.
- The types involved
trippy_tui.frontend.tui_app.TuiApp→trippy_tui.geoip.GeoIpLookup
- Direction
- trippy_tui.frontend.tui_app uses trippy_tui.geoip, so a change to trippy_tui.geoip can break trippy_tui.frontend.tui_app, while a change to trippy_tui.frontend.tui_app can't break trippy_tui.geoip.
- Position
- Below the diagonal: trippy_tui.frontend.tui_app uses a module listed above it, which is the healthy direction.
37→10 trippy_tui.frontend.tui_app uses trippy_tui.report.types✕
- Connections
- 1 pair of types, where a type in trippy_tui.frontend.tui_app uses a type in trippy_tui.report.types.
- The types involved
trippy_tui.frontend.tui_app.TuiApp→trippy_tui.report.types.Hop
- Direction
- trippy_tui.frontend.tui_app uses trippy_tui.report.types, so a change to trippy_tui.report.types can break trippy_tui.frontend.tui_app, while a change to trippy_tui.frontend.tui_app can't break trippy_tui.report.types.
- Position
- Below the diagonal: trippy_tui.frontend.tui_app uses a module listed above it, which is the healthy direction.
37→14 trippy_tui.frontend.tui_app uses trippy_dns.lazy_resolver✕
- Connections
- 1 pair of types, where a type in trippy_tui.frontend.tui_app uses a type in trippy_dns.lazy_resolver.
- The types involved
trippy_tui.frontend.tui_app.TuiApp→trippy_dns.lazy_resolver.DnsResolver
- Direction
- trippy_tui.frontend.tui_app uses trippy_dns.lazy_resolver, so a change to trippy_dns.lazy_resolver can break trippy_tui.frontend.tui_app, while a change to trippy_tui.frontend.tui_app can't break trippy_dns.lazy_resolver.
- Position
- Below the diagonal: trippy_tui.frontend.tui_app uses a module listed above it, which is the healthy direction.
37→31 trippy_tui.frontend.tui_app uses trippy_tui.frontend.config✕
- Connections
- 1 pair of types, where a type in trippy_tui.frontend.tui_app uses a type in trippy_tui.frontend.config.
- The types involved
trippy_tui.frontend.tui_app.TuiApp→trippy_tui.frontend.config.TuiConfig
- Direction
- trippy_tui.frontend.tui_app uses trippy_tui.frontend.config, so a change to trippy_tui.frontend.config can break trippy_tui.frontend.tui_app, while a change to trippy_tui.frontend.tui_app can't break trippy_tui.frontend.config.
- Position
- Below the diagonal: trippy_tui.frontend.tui_app uses a module listed above it, which is the healthy direction.
37→32 trippy_tui.frontend.tui_app uses trippy_core.state✕
- Connections
- 1 pair of types, where a type in trippy_tui.frontend.tui_app uses a type in trippy_core.state.
- The types involved
trippy_tui.frontend.tui_app.TuiApp→trippy_core.state.State
- Direction
- trippy_tui.frontend.tui_app uses trippy_core.state, so a change to trippy_core.state can break trippy_tui.frontend.tui_app, while a change to trippy_tui.frontend.tui_app can't break trippy_core.state.
- Position
- Below the diagonal: trippy_tui.frontend.tui_app uses a module listed above it, which is the healthy direction.
37→36 trippy_tui.frontend.tui_app uses trippy_tui.app✕
- Connections
- 1 pair of types, where a type in trippy_tui.frontend.tui_app uses a type in trippy_tui.app.
- The types involved
trippy_tui.frontend.tui_app.TuiApp→trippy_tui.app.TraceInfo
- Direction
- trippy_tui.frontend.tui_app uses trippy_tui.app, so a change to trippy_tui.app can break trippy_tui.frontend.tui_app, while a change to trippy_tui.frontend.tui_app can't break trippy_tui.app.
- Position
- Below the diagonal: trippy_tui.frontend.tui_app uses a module listed above it, which is the healthy direction.
38→9 trippy_tui.frontend uses trippy_tui.geoip✕
- Connections
- 1 pair of types, where a type in trippy_tui.frontend uses a type in trippy_tui.geoip.
- The types involved
trippy_tui.frontend.frontend$module→trippy_tui.geoip.GeoIpLookup
- Direction
- trippy_tui.frontend uses trippy_tui.geoip, so a change to trippy_tui.geoip can break trippy_tui.frontend, while a change to trippy_tui.frontend can't break trippy_tui.geoip.
- Position
- Below the diagonal: trippy_tui.frontend uses a module listed above it, which is the healthy direction.
38→14 trippy_tui.frontend uses trippy_dns.lazy_resolver✕
- Connections
- 1 pair of types, where a type in trippy_tui.frontend uses a type in trippy_dns.lazy_resolver.
- The types involved
trippy_tui.frontend.frontend$module→trippy_dns.lazy_resolver.DnsResolver
- Direction
- trippy_tui.frontend uses trippy_dns.lazy_resolver, so a change to trippy_dns.lazy_resolver can break trippy_tui.frontend, while a change to trippy_tui.frontend can't break trippy_dns.lazy_resolver.
- Position
- Below the diagonal: trippy_tui.frontend uses a module listed above it, which is the healthy direction.
38→31 trippy_tui.frontend uses trippy_tui.frontend.config✕
- Connections
- 1 pair of types, where a type in trippy_tui.frontend uses a type in trippy_tui.frontend.config.
- The types involved
trippy_tui.frontend.frontend$module→trippy_tui.frontend.config.TuiConfig
- Direction
- trippy_tui.frontend uses trippy_tui.frontend.config, so a change to trippy_tui.frontend.config can break trippy_tui.frontend, while a change to trippy_tui.frontend can't break trippy_tui.frontend.config.
- Position
- Below the diagonal: trippy_tui.frontend uses a module listed above it, which is the healthy direction.
38→36 trippy_tui.frontend uses trippy_tui.app✕
- Connections
- 1 pair of types, where a type in trippy_tui.frontend uses a type in trippy_tui.app.
- The types involved
trippy_tui.frontend.frontend$module→trippy_tui.app.TraceInfo
- Direction
- trippy_tui.frontend uses trippy_tui.app, so a change to trippy_tui.app can break trippy_tui.frontend, while a change to trippy_tui.frontend can't break trippy_tui.app.
- Position
- Below the diagonal: trippy_tui.frontend uses a module listed above it, which is the healthy direction.
38→37 trippy_tui.frontend uses trippy_tui.frontend.tui_app✕
- Connections
- 1 pair of types, where a type in trippy_tui.frontend uses a type in trippy_tui.frontend.tui_app.
- The types involved
trippy_tui.frontend.frontend$module→trippy_tui.frontend.tui_app.TuiApp
- Direction
- trippy_tui.frontend uses trippy_tui.frontend.tui_app, so a change to trippy_tui.frontend.tui_app can break trippy_tui.frontend, while a change to trippy_tui.frontend can't break trippy_tui.frontend.tui_app.
- Position
- Below the diagonal: trippy_tui.frontend uses a module listed above it, which is the healthy direction.
39→14 trippy_tui.frontend.render.settings uses trippy_dns.lazy_resolver✕
- Connections
- 1 pair of types, where a type in trippy_tui.frontend.render.settings uses a type in trippy_dns.lazy_resolver.
- The types involved
trippy_tui.frontend.render.settings.settings$module→trippy_dns.lazy_resolver.ResolveMethod
- Direction
- trippy_tui.frontend.render.settings uses trippy_dns.lazy_resolver, so a change to trippy_dns.lazy_resolver can break trippy_tui.frontend.render.settings, while a change to trippy_tui.frontend.render.settings can't break trippy_dns.lazy_resolver.
- Position
- Below the diagonal: trippy_tui.frontend.render.settings uses a module listed above it, which is the healthy direction.
39→29 trippy_tui.frontend.render.settings uses trippy_tui.config✕
- Connections
- 4 pairs of types, where a type in trippy_tui.frontend.render.settings uses a type in trippy_tui.config.
- The types involved
trippy_tui.frontend.render.settings.settings$module→trippy_tui.config.AddressModetrippy_tui.frontend.render.settings.settings$module→trippy_tui.config.AsModetrippy_tui.frontend.render.settings.settings$module→trippy_tui.config.GeoIpModetrippy_tui.frontend.render.settings.settings$module→trippy_tui.config.IcmpExtensionMode
- Direction
- trippy_tui.frontend.render.settings uses trippy_tui.config, so a change to trippy_tui.config can break trippy_tui.frontend.render.settings, while a change to trippy_tui.frontend.render.settings can't break trippy_tui.config.
- Position
- Below the diagonal: trippy_tui.frontend.render.settings uses a module listed above it, which is the healthy direction.
39→37 trippy_tui.frontend.render.settings uses trippy_tui.frontend.tui_app✕
- Connections
- 1 pair of types, where a type in trippy_tui.frontend.render.settings uses a type in trippy_tui.frontend.tui_app.
- The types involved
trippy_tui.frontend.render.settings.settings$module→trippy_tui.frontend.tui_app.TuiApp
- Direction
- trippy_tui.frontend.render.settings uses trippy_tui.frontend.tui_app, so a change to trippy_tui.frontend.tui_app can break trippy_tui.frontend.render.settings, while a change to trippy_tui.frontend.render.settings can't break trippy_tui.frontend.tui_app.
- Position
- Below the diagonal: trippy_tui.frontend.render.settings uses a module listed above it, which is the healthy direction.
40→2 trippy_tui.frontend.render.table uses trippy_core.types✕
- Connections
- 2 pairs of types, where a type in trippy_tui.frontend.render.table uses a type in trippy_core.types.
- The types involved
trippy_tui.frontend.render.table.table$module→trippy_core.types.Dscptrippy_tui.frontend.render.table.table$module→trippy_core.types.Ecn
- Direction
- trippy_tui.frontend.render.table uses trippy_core.types, so a change to trippy_core.types can break trippy_tui.frontend.render.table, while a change to trippy_tui.frontend.render.table can't break trippy_core.types.
- Position
- Below the diagonal: trippy_tui.frontend.render.table uses a module listed above it, which is the healthy direction.
40→3 trippy_tui.frontend.render.table uses trippy_dns.resolver✕
- Connections
- 2 pairs of types, where a type in trippy_tui.frontend.render.table uses a type in trippy_dns.resolver.
- The types involved
trippy_tui.frontend.render.table.table$module→trippy_dns.resolver.AsInfotrippy_tui.frontend.render.table.table$module→trippy_dns.resolver.DnsEntry
- Direction
- trippy_tui.frontend.render.table uses trippy_dns.resolver, so a change to trippy_dns.resolver can break trippy_tui.frontend.render.table, while a change to trippy_tui.frontend.render.table can't break trippy_dns.resolver.
- Position
- Below the diagonal: trippy_tui.frontend.render.table uses a module listed above it, which is the healthy direction.
40→9 trippy_tui.frontend.render.table uses trippy_tui.geoip✕
- Connections
- 2 pairs of types, where a type in trippy_tui.frontend.render.table uses a type in trippy_tui.geoip.
- The types involved
trippy_tui.frontend.render.table.table$module→trippy_tui.geoip.GeoIpCitytrippy_tui.frontend.render.table.table$module→trippy_tui.geoip.GeoIpLookup
- Direction
- trippy_tui.frontend.render.table uses trippy_tui.geoip, so a change to trippy_tui.geoip can break trippy_tui.frontend.render.table, while a change to trippy_tui.frontend.render.table can't break trippy_tui.geoip.
- Position
- Below the diagonal: trippy_tui.frontend.render.table uses a module listed above it, which is the healthy direction.
40→10 trippy_tui.frontend.render.table uses trippy_tui.report.types✕
- Connections
- 4 pairs of types, where a type in trippy_tui.frontend.render.table uses a type in trippy_tui.report.types.
- The types involved
trippy_tui.frontend.render.table.table$module→trippy_tui.report.types.Extensionstrippy_tui.frontend.render.table.table$module→trippy_tui.report.types.Hoptrippy_tui.frontend.render.table.table$module→trippy_tui.report.types.MplsLabelStackMembertrippy_tui.frontend.render.table.table$module→trippy_tui.report.types.UnknownExtension
- Direction
- trippy_tui.frontend.render.table uses trippy_tui.report.types, so a change to trippy_tui.report.types can break trippy_tui.frontend.render.table, while a change to trippy_tui.frontend.render.table can't break trippy_tui.report.types.
- Position
- Below the diagonal: trippy_tui.frontend.render.table uses a module listed above it, which is the healthy direction.
40→13 trippy_tui.frontend.render.table uses trippy_core.probe✕
- Connections
- 1 pair of types, where a type in trippy_tui.frontend.render.table uses a type in trippy_core.probe.
- The types involved
trippy_tui.frontend.render.table.table$module→trippy_core.probe.IcmpPacketType
- Direction
- trippy_tui.frontend.render.table uses trippy_core.probe, so a change to trippy_core.probe can break trippy_tui.frontend.render.table, while a change to trippy_tui.frontend.render.table can't break trippy_core.probe.
- Position
- Below the diagonal: trippy_tui.frontend.render.table uses a module listed above it, which is the healthy direction.
40→14 trippy_tui.frontend.render.table uses trippy_dns.lazy_resolver✕
- Connections
- 1 pair of types, where a type in trippy_tui.frontend.render.table uses a type in trippy_dns.lazy_resolver.
- The types involved
trippy_tui.frontend.render.table.table$module→trippy_dns.lazy_resolver.DnsResolver
- Direction
- trippy_tui.frontend.render.table uses trippy_dns.lazy_resolver, so a change to trippy_dns.lazy_resolver can break trippy_tui.frontend.render.table, while a change to trippy_tui.frontend.render.table can't break trippy_dns.lazy_resolver.
- Position
- Below the diagonal: trippy_tui.frontend.render.table uses a module listed above it, which is the healthy direction.
40→19 trippy_tui.frontend.render.table uses trippy_tui.frontend.columns✕
- Connections
- 2 pairs of types, where a type in trippy_tui.frontend.render.table uses a type in trippy_tui.frontend.columns.
- The types involved
trippy_tui.frontend.render.table.table$module→trippy_tui.frontend.columns.ColumnTypetrippy_tui.frontend.render.table.table$module→trippy_tui.frontend.columns.Columns
- Direction
- trippy_tui.frontend.render.table uses trippy_tui.frontend.columns, so a change to trippy_tui.frontend.columns can break trippy_tui.frontend.render.table, while a change to trippy_tui.frontend.render.table can't break trippy_tui.frontend.columns.
- Position
- Below the diagonal: trippy_tui.frontend.render.table uses a module listed above it, which is the healthy direction.
40→20 trippy_tui.frontend.render.table uses trippy_tui.frontend.theme✕
- Connections
- 1 pair of types, where a type in trippy_tui.frontend.render.table uses a type in trippy_tui.frontend.theme.
- The types involved
trippy_tui.frontend.render.table.table$module→trippy_tui.frontend.theme.Theme
- Direction
- trippy_tui.frontend.render.table uses trippy_tui.frontend.theme, so a change to trippy_tui.frontend.theme can break trippy_tui.frontend.render.table, while a change to trippy_tui.frontend.render.table can't break trippy_tui.frontend.theme.
- Position
- Below the diagonal: trippy_tui.frontend.render.table uses a module listed above it, which is the healthy direction.
40→29 trippy_tui.frontend.render.table uses trippy_tui.config✕
- Connections
- 1 pair of types, where a type in trippy_tui.frontend.render.table uses a type in trippy_tui.config.
- The types involved
trippy_tui.frontend.render.table.table$module→trippy_tui.config.AsMode
- Direction
- trippy_tui.frontend.render.table uses trippy_tui.config, so a change to trippy_tui.config can break trippy_tui.frontend.render.table, while a change to trippy_tui.frontend.render.table can't break trippy_tui.config.
- Position
- Below the diagonal: trippy_tui.frontend.render.table uses a module listed above it, which is the healthy direction.
40→31 trippy_tui.frontend.render.table uses trippy_tui.frontend.config✕
- Connections
- 1 pair of types, where a type in trippy_tui.frontend.render.table uses a type in trippy_tui.frontend.config.
- The types involved
trippy_tui.frontend.render.table.table$module→trippy_tui.frontend.config.TuiConfig
- Direction
- trippy_tui.frontend.render.table uses trippy_tui.frontend.config, so a change to trippy_tui.frontend.config can break trippy_tui.frontend.render.table, while a change to trippy_tui.frontend.render.table can't break trippy_tui.frontend.config.
- Position
- Below the diagonal: trippy_tui.frontend.render.table uses a module listed above it, which is the healthy direction.
40→32 trippy_tui.frontend.render.table uses trippy_core.state✕
- Connections
- 1 pair of types, where a type in trippy_tui.frontend.render.table uses a type in trippy_core.state.
- The types involved
trippy_tui.frontend.render.table.table$module→trippy_core.state.NatStatus
- Direction
- trippy_tui.frontend.render.table uses trippy_core.state, so a change to trippy_core.state can break trippy_tui.frontend.render.table, while a change to trippy_tui.frontend.render.table can't break trippy_core.state.
- Position
- Below the diagonal: trippy_tui.frontend.render.table uses a module listed above it, which is the healthy direction.
40→37 trippy_tui.frontend.render.table uses trippy_tui.frontend.tui_app✕
- Connections
- 1 pair of types, where a type in trippy_tui.frontend.render.table uses a type in trippy_tui.frontend.tui_app.
- The types involved
trippy_tui.frontend.render.table.table$module→trippy_tui.frontend.tui_app.TuiApp
- Direction
- trippy_tui.frontend.render.table uses trippy_tui.frontend.tui_app, so a change to trippy_tui.frontend.tui_app can break trippy_tui.frontend.render.table, while a change to trippy_tui.frontend.render.table can't break trippy_tui.frontend.tui_app.
- Position
- Below the diagonal: trippy_tui.frontend.render.table 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
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 47 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 10 | Medium |
| A02:2025 — Security Misconfiguration | 7 | High / Critical |
Roadmap
Top priorities: Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Cargo.toml; Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them; The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Cargo.toml. | +4.7 pts | Low | ADR Quality |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +4.5 pts | Medium | Architecture documentation |
| The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`). | +2.7 pts | Medium | Nullable reference types |
| 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. | +1.4 pts | Medium | Documentation (README) |
| Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. | +0.6 pts | Low | Static Analysis (SAST) |
| Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). | +0.6 pts | Low | Static Analysis (SAST) |
| Resolve the 4 High IaC finding(s) in IaC & Container Security — start with REDACTED (4). | +0.6 pts | Low | IaC & Container Security |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. | +0.5 pts | Low | Supply-chain Provenance & Signing |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.7 | Mixed | IaC & Container Security: High IaC: REDACTED |
| crates/trippy-core/src/net/platform/unix.rs | 4.0 | Mixed | Code Duplication: Edited copy of a member (19 corresponding lines) |
| crates/trippy-tui/src/frontend/tui_app.rs | 4.2 | Mixed | God Classes: TooManyMethods: TuiApp |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| crates/trippy-core/src/net/ipv4.rs | 5.5 | Mixed | Code Duplication: Near-duplicate member pair (57 shared lines) |
| crates/trippy-dns/src/lazy_resolver.rs | 5.6 | Mixed | Cognitive Complexity: DnsResolver::lookup (cognitive 20) |
| crates/trippy-tui/src/frontend.rs | 5.7 | Mixed | Cyclomatic Complexity: trippy_tui::frontend::run_app (cyclomatic 74) |
| crates/trippy-tui/src/frontend/render/header.rs | 5.7 | Mixed | God Classes: FunctionTooLong: trippy_tui::frontend::render::header::render |
| crates/trippy-core/src/net/platform/windows.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| crates/trippy-tui/src/frontend/render/table.rs | 6.3 | Mixed | God Classes: FileTooLong: render/table.rs |
| crates/trippy-tui/src/report/csv.rs | 6.3 | Mixed | Code Duplication: Duplicated block (9 lines × 2) |
| crates/trippy-tui/src/frontend/binding.rs | 7.0 | Near-clean | God Classes: TooManyFields: Bindings |
| crates/trippy-tui/src/frontend/theme.rs | 7.0 | Near-clean | God Classes: TooManyFields: Theme |
| crates/trippy-packet/src/icmpv4.rs | 7.0 | Near-clean | Code Duplication: Members sharing a duplicated core (4 members, 50+ identical tokens) |
| crates/trippy-core/src/net/channel.rs | 7.0 | Near-clean | Code Duplication: Edited copy of a member (7 corresponding lines) |
| crates/trippy-tui/src/frontend/render/flows.rs | 7.0 | Near-clean | Code Duplication: Duplicated block (7 lines × 4) |
| crates/trippy-tui/src/frontend/render/bsod.rs | 7.0 | Near-clean | Code Duplication: Duplicated block (7 lines × 2) |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 42 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 1.0, the weighted average across measured dimensions.
What we checked — 42 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, 232 of 244 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares package.json, but the licence verdict published here was taken over its crate dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (23 contributor(s) across 2183 commit(s) sampled, automation and bot accounts excluded). One of them holds 97% of the history; the other 22 hold 0.1% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- D27 Navigability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AXB2 Runtime readiness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. (rule: no-root-manifest). The renderer reported: the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DevServer (dev). the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and this repository's Rust is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and this repository's Rust is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- X17 Uncapped recursion over a caller-supplied document — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X3 Exception handling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go and JavaScript/TypeScript source only, and no C# was loaded and no PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go, JavaScript or TypeScript was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
2 function(s) exceeded the cyclomatic complexity threshold of 15; the worst was trippy_tui::frontend::run_app at 74. A further 13 function(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being TuiColor::try_from at 146 — they are counted neither in the figure above nor in this dimension's score. 9 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold functions was excluded, so the exclusion is disclosed nowhere in the file itself: crates/trippy-tui/src/config/theme.rs (TuiColor::try_from at 146), crates/trippy-tui/src/frontend/render/table.rs (trippy_tui::frontend::render::table::new_cell at 30), crates/trippy-tui/src/config/columns.rs (TuiColumn::try_from at 29), crates/trippy-core/src/types.rs (TypeOfService::split at 28), crates/trippy-tui/src/frontend/columns.rs (Column::from at 28), and 4 more not listed here. 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 1 body over 30 down to 30 or less in Cyclomatic Complexity — start with trippy_tui::frontend::run_app (cyclomatic 74). — Refactoring it lifts Cyclomatic Complexity from 8.2 to about 9.1/10.
D2 · Cognitive Complexity
5 function(s) exceeded the cognitive complexity threshold of 15; the worst was trippy_tui::frontend::run_app at 91.
What to do
- Bring the 1 body over 30 down to 30 or less in Cognitive Complexity — start with trippy_tui::frontend::run_app (cognitive 91). — Refactoring it lifts Cognitive Complexity from 7.7 to about 8.9/10.
D3 · God Classes
25 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 8 TooManyFields finding(s) in God Classes — start with file.rs (2), binding.rs (2), theme.rs (2). — One of this dimension's main actionable groups (8 warning-level).
- Resolve the 5 FileTooLong finding(s) in God Classes — start with config.rs, windows.rs, theme.rs. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 5 TooManyMethods finding(s) in God Classes — start with tracer.rs (2), tui_app.rs, ipv4.rs. — One of this dimension's main actionable groups (5 warning-level).
D4 · Code Duplication
50 duplicated block group(s) detected. 6.9 % of the production lines (1,993 of 28,853) are in a reported copy. A further 34 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
What to do
- Resolve the 11 Duplicated block (12 lines × 2) finding(s) in Code Duplication — start with icmpv4.rs (10), lazy_resolver.rs. — One of this dimension's main actionable groups (11 warning-level).
- Resolve the 5 Edited copy of a member (13 corresponding lines) finding(s) in Code Duplication — start with unix.rs, windows.rs, tcp.rs. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 5 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with icmpv4.rs (3), windows.rs, csv.rs. — One of this dimension's main actionable groups (5 warning-level).
D5 · Coupling
6 production modules (Cargo), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 3 module(s) off the main sequence, with abstractness counted on 5 of the 6 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What to do
- Resolve the 3 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (3 warning-level).
D6 · Cohesion (LCOM4)
1 of 30 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with tui_app.rs. — One of this dimension's main actionable groups (1 warning-level).
D8 · Code Coverage
Line coverage 49.9% — 44 file(s) below 50%. Measured from the Rust suite (repository root: `cargo test --workspace` instrumented over 78 production file(s), 10 test binaries and 1 doc-test binaries).
What to do
- Resolve the 44 Low coverage finding(s) in Code Coverage — start with main.rs (3), types.rs (2), config.rs (2). — One of this dimension's main actionable groups (44 warning-level).
D11 · Test Reliability
0 flaky across 1 measured tier(s). Rust (repository root, 33 test files): measured (0 flaky).
D12 · Dependency Hygiene
0 outdated, 0 yanked direct Cargo dependencies. Only DIRECT edges are graded: a transitive crate cannot be moved past what its parent's requirement admits, so reporting one would be advice its owner cannot take. A newer release is reported only where this repository's OWN requirement already admits it, so the remedy is `cargo update` and never a manifest edit — which means a release outside the declared range is deliberately NOT charged, because a written-down constraint is a decision rather than a defect. Note that a bare requirement is a CARET, and for a 0.x crate its ceiling is the minor. Whether any crate is UNMAINTAINED is not graded — crates.io publishes no maintenance status, and release age does not stand in for one. Known CVEs in this dependency graph are D30's question, read from REDACTED there.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 355 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository's REDACTED closed over its manifests' `[dependencies]` and `[build-dependencies]`. Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository. This repository publishes itself under Apache-2.0, which is its own choice and is not judged here. ★ COVERAGE OF THIS VERDICT: it grades this repository's crate dependencies and nothing else. The repository also declares package.json, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
7 deducted task-comment markers across 28853 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 7 TodoComment finding(s) in Explicit Debt — start with windows.rs (7). — One of this dimension's main actionable groups (7 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 61 document(s) read across 2 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Cargo.toml. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
0 of 6 build units (Cargo) flagged as possibly oversized/incoherent.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
47 finding(s): 0 critical, 42 high, 5 medium, 0 low. 36 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. Separately, one or more rules could not re-parse an embedded snippet in 2 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 36 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 (36 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
3 finding(s): 0 critical, 0 high, 0 medium, 0 low.
D31 · IaC & Container Security
7 finding(s): 0 critical, 4 high, 3 medium, 0 low.
What to do
- Resolve the 4 High IaC finding(s) in IaC & Container Security — start with REDACTED (4). — One of this dimension's main actionable groups (4 issue-level).
- Resolve the 3 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (3). — One of this dimension's main actionable groups (3 warning-level).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 65 of the 88 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
Strongest change-coupling: ipv4.rs↔ipv6.rs 60%; config.rs↔main.rs 51%; unix.rs↔source.rs 50%
What to do
- Resolve the 3 Change coupling finding(s) in Change Coupling — start with ipv4.rs, config.rs, unix.rs. — One of this dimension's main actionable groups (3 warning-level).
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX9 · CQS / query purity
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
- Only 2/3 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `crates/trippy`.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
P3 · Security & performance tooling
- `REDACTED` schedules updates, but no `package-ecosystem` entry covers `github-actions`, `npm`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entries to the `updates:` list. — REDACTED:2
What to do
- Dependabot is configured but does not watch `github-actions`, `npm` — add those `package-ecosystem` entries to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
What to do
- Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where we can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it.
P6 · Release Hygiene
X14 · Bypassable address classification
X21 · Side-effecting pattern guard
X4 · Structured logging
X5 · Nullable reference types
- This repository commits no tsconfig, so whatever type-checks it uses tsc's own defaults, in which `strict` and `strictNullChecks` are OFF: `string` admits `null` and `undefined`, and a value that is null is compiled through to the property access that throws. If the build passes `--strict` on a command line instead, put it in a committed tsconfig — this check reads configuration, and configuration is all it can read.
What to do
- The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 64% | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 90% | Exemplary | Strongest area. |
| Maturity | 60% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 73% | Strong | Solid. |
| Security | 62% | Adequate — gated by D29, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 75 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one.
- AX2 Stateful singletons — Not applicable: Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered. This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no data at rest for these controls to protect.
- 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 — ~1163 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.
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (3230 declarations, no unit with a dominant convention).
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed Rust surface was not measured.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .rs source were not judged.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.rs), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (18 value object(s))
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- M4 Documentation accuracy — Not applicable: the 61 current-state document(s) make no claim of a kind M4 checks. 25 claim(s) of kinds M4 does not check were not checked (path 16, command argument 4, environment variable 4, cd 1); M4 checks only links and versions and artefact counts.
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript, Rust source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage data present for 78 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `#[bench]`, criterion's `bench_function`/`bench_with_input`, `#[divan::bench]` or `#[library_benchmark]` in any `.rs` file, or criterion, divan, iai or a `[[bench]]` target in a Cargo.toml, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- 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: 88 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.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X12 Unreachable branch — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X16 Unfloored truncation loop — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — no C# was loaded; this repository's Rust was read, and no request in it can be cancelled by a caller — a Rust request takes no token: a future is cancelled by dropping it, from outside the call (select!, a timeout, an aborted task), and reqwest, hyper and tonic take none
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. Rust's compiler refuses the unsynchronised version: a collection shared between a callback's thread and the waiting body must be `Sync`, which a `Vec`, `VecDeque` or `HashMap` is only behind a `Mutex`/`RwLock`, so the race this check looks for cannot be written in safe Rust. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
- X27 Collection changed while being enumerated — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X3 Exception handling — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- 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 — 46 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 185 finding(s)
- Low coverage: crates/trippy-core/src/error.rs crates/trippy-core/src/error.rs:1
- Low coverage: crates/trippy-core/src/net/channel.rs crates/trippy-core/src/net/channel.rs:1
- Low coverage: crates/trippy-core/src/net/platform/unix.rs crates/trippy-core/src/net/platform/unix.rs:1
- Low coverage: crates/trippy-core/src/types.rs crates/trippy-core/src/types.rs:1
- Low coverage: crates/trippy-dns/src/config.rs crates/trippy-dns/src/config.rs:1
- Low coverage: crates/trippy-dns/src/lazy_resolver.rs crates/trippy-dns/src/lazy_resolver.rs:1
- Low coverage: crates/trippy-dns/src/resolver.rs crates/trippy-dns/src/resolver.rs:1
- Low coverage: crates/trippy-tui/src/app.rs crates/trippy-tui/src/app.rs:1
- Low coverage: crates/trippy-tui/src/frontend.rs crates/trippy-tui/src/frontend.rs:1
- Low coverage: crates/trippy-tui/src/frontend/binding.rs crates/trippy-tui/src/frontend/binding.rs:1
- Low coverage: crates/trippy-tui/src/frontend/config.rs crates/trippy-tui/src/frontend/config.rs:1
- Low coverage: crates/trippy-tui/src/frontend/render/app.rs crates/trippy-tui/src/frontend/render/app.rs:1
- Low coverage: crates/trippy-tui/src/frontend/render/bar.rs crates/trippy-tui/src/frontend/render/bar.rs:1
- Low coverage: crates/trippy-tui/src/frontend/render/body.rs crates/trippy-tui/src/frontend/render/body.rs:1
- Low coverage: crates/trippy-tui/src/frontend/render/bsod.rs crates/trippy-tui/src/frontend/render/bsod.rs:1
- Low coverage: crates/trippy-tui/src/frontend/render/chart.rs crates/trippy-tui/src/frontend/render/chart.rs:1
- Low coverage: crates/trippy-tui/src/frontend/render/flows.rs crates/trippy-tui/src/frontend/render/flows.rs:1
- Low coverage: crates/trippy-tui/src/frontend/render/footer.rs crates/trippy-tui/src/frontend/render/footer.rs:1
- Low coverage: crates/trippy-tui/src/frontend/render/header.rs crates/trippy-tui/src/frontend/render/header.rs:1
- Low coverage: crates/trippy-tui/src/frontend/render/help.rs crates/trippy-tui/src/frontend/render/help.rs:1
- Low coverage: crates/trippy-tui/src/frontend/render/histogram.rs crates/trippy-tui/src/frontend/render/histogram.rs:1
- Low coverage: crates/trippy-tui/src/frontend/render/history.rs crates/trippy-tui/src/frontend/render/history.rs:1
- Low coverage: crates/trippy-tui/src/frontend/render/settings.rs crates/trippy-tui/src/frontend/render/settings.rs:1
- Low coverage: crates/trippy-tui/src/frontend/render/splash.rs crates/trippy-tui/src/frontend/render/splash.rs:1
- Low coverage: crates/trippy-tui/src/frontend/render/table.rs crates/trippy-tui/src/frontend/render/table.rs:1
- Duplicated block (12 lines × 2) crates/trippy-dns/src/lazy_resolver.rs:440
- Duplicated block (12 lines × 2) crates/trippy-packet/src/icmpv4.rs:85
- Duplicated block (12 lines × 2) crates/trippy-packet/src/icmpv4.rs:99
- Duplicated block (12 lines × 2) crates/trippy-packet/src/icmpv4.rs:262
- Duplicated block (12 lines × 2) crates/trippy-packet/src/icmpv4.rs:276
- Duplicated block (12 lines × 2) crates/trippy-packet/src/icmpv4.rs:514
- Duplicated block (12 lines × 2) crates/trippy-packet/src/icmpv4.rs:528
- Duplicated block (12 lines × 2) crates/trippy-packet/src/icmpv4.rs:766
- Duplicated block (12 lines × 2) crates/trippy-packet/src/icmpv4.rs:780
- Duplicated block (12 lines × 2) crates/trippy-packet/src/icmpv4.rs:1027
- Duplicated block (12 lines × 2) crates/trippy-packet/src/icmpv4.rs:1041
- TooManyFields: Args crates/trippy-tui/src/config/cmd.rs:19
- TooManyFields: TrippyConfig crates/trippy-tui/src/config.rs:290
- TooManyFields: ConfigBindings crates/trippy-tui/src/config/file.rs:380
- TooManyFields: TuiBindings crates/trippy-tui/src/config/binding.rs:12
- TooManyFields: ConfigThemeColors crates/trippy-tui/src/config/file.rs:285
- TooManyFields: TuiTheme crates/trippy-tui/src/config/theme.rs:9
- TooManyFields: Bindings crates/trippy-tui/src/frontend/binding.rs:8
- TooManyFields: Theme crates/trippy-tui/src/frontend/theme.rs:6
- TodoComment crates/trippy-core/src/net/platform/windows.rs:216
- TodoComment crates/trippy-core/src/net/platform/windows.rs:672
- TodoComment crates/trippy-core/src/net/platform/windows.rs:688
- TodoComment crates/trippy-core/src/net/platform/windows.rs:698
- TodoComment crates/trippy-core/src/net/platform/windows.rs:701
- TodoComment crates/trippy-core/src/net/platform/windows.rs:704
- TodoComment crates/trippy-core/src/net/platform/windows.rs:700
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- FileTooLong: src/config.rs crates/trippy-tui/src/config.rs
- FileTooLong: platform/windows.rs crates/trippy-core/src/net/platform/windows.rs
- FileTooLong: config/theme.rs crates/trippy-tui/src/config/theme.rs
- FileTooLong: render/table.rs crates/trippy-tui/src/frontend/render/table.rs
- FileTooLong: src/strategy.rs crates/trippy-core/src/strategy.rs
- TooManyMethods: TuiApp crates/trippy-tui/src/frontend/tui_app.rs:13
- TooManyMethods: TracerInner crates/trippy-core/src/tracer.rs:507
- TooManyMethods: Ipv4Packet crates/trippy-packet/src/ipv4.rs:24
- TooManyMethods: Hop crates/trippy-core/src/state.rs:167
- TooManyMethods: Tracer crates/trippy-core/src/tracer.rs:20
- Edited copy of a member (13 corresponding lines) crates/trippy-core/src/net/platform/unix.rs:111
- Edited copy of a member (13 corresponding lines) crates/trippy-core/src/net/platform/windows.rs:493
- Edited copy of a member (13 corresponding lines) crates/trippy-packet/src/tcp.rs:26
- Edited copy of a member (13 corresponding lines) crates/trippy-packet/src/udp.rs:20
- Edited copy of a member (13 corresponding lines) crates/trippy-core/src/net/ipv4.rs:68
- Duplicated block (9 lines × 2) crates/trippy-core/src/net/platform/windows.rs:306
- Duplicated block (9 lines × 2) crates/trippy-packet/src/icmpv4.rs:1141
- Duplicated block (9 lines × 2) crates/trippy-tui/src/report/csv.rs:85
- Duplicated block (9 lines × 2) crates/trippy-packet/src/icmpv4.rs:17
- Duplicated block (9 lines × 2) crates/trippy-packet/src/icmpv4.rs:29
- Duplicated block (8 lines × 2) crates/trippy-core/src/net/ipv4.rs:292
- Duplicated block (8 lines × 2) crates/trippy-core/src/state.rs:654
- Duplicated block (8 lines × 2) crates/trippy-packet/src/icmpv4.rs:874
- Duplicated block (8 lines × 2) crates/trippy-core/src/net/ipv4.rs:408
- Duplicated block (8 lines × 2) crates/trippy-core/src/net/ipv4.rs:190
- Duplicated block (7 lines × 2) crates/trippy-core/src/net/ipv6.rs:169
- Duplicated block (7 lines × 2) crates/trippy-tui/src/frontend/render/bsod.rs:10
- Duplicated block (7 lines × 2) crates/trippy-packet/src/icmpv4.rs:62
- Duplicated block (7 lines × 2) crates/trippy-packet/src/icmpv4.rs:151
- Duplicated block (7 lines × 2) crates/trippy-core/src/net/platform/unix.rs:223
- MethodTooLong: TrippyConfig.build_config crates/trippy-tui/src/config.rs:362
- MethodTooLong: TuiBindings.from crates/trippy-tui/src/config/binding.rs:187
- MethodTooLong: TuiTheme.from crates/trippy-tui/src/config/theme.rs:141
- MethodTooLong: TuiColor.try_from crates/trippy-tui/src/config/theme.rs:547
- Edited copy of a member (14 corresponding lines) crates/trippy-core/src/net/ipv4.rs:186
- Edited copy of a member (14 corresponding lines) crates/trippy-core/src/net/ipv4.rs:427
- Edited copy of a member (14 corresponding lines) crates/trippy-tui/src/config/binding.rs:114
- Edited copy of a member (14 corresponding lines) crates/trippy-tui/src/frontend/tui_app.rs:254
- Duplicated block (6 lines × 2) crates/trippy-core/src/net/ipv4.rs:428
- Duplicated block (6 lines × 2) crates/trippy-core/src/strategy.rs:1136
- Duplicated block (6 lines × 2) crates/trippy-core/src/net/platform/unix.rs:382
- Duplicated block (6 lines × 2) crates/trippy-tui/src/report/csv.rs:71
- REDACTED
- REDACTED
- REDACTED
- Change coupling: ipv4.rs ↔ ipv6.rs crates/trippy-core/src/net/ipv4.rs:1
- Change coupling: config.rs ↔ main.rs crates/trippy-core/src/config.rs:1
- Change coupling: unix.rs ↔ source.rs crates/trippy-core/src/net/platform/unix.rs:1
- Edited copy of a member (18 corresponding lines) crates/trippy-core/src/net/ipv4.rs:204
- Edited copy of a member (18 corresponding lines) crates/trippy-tui/src/frontend/render/table.rs:519
- Edited copy of a member (18 corresponding lines) crates/trippy-tui/src/frontend/tui_app.rs:143
- Duplicated block (11 lines × 2) crates/trippy-core/src/net/ipv4.rs:92
- Duplicated block (11 lines × 2) crates/trippy-core/src/net/ipv4.rs:157
- Duplicated block (11 lines × 2) crates/trippy-core/src/net/platform/windows.rs:495
- Off the main sequence: trippy-packet
- Off the main sequence: trippy-privilege
- Off the main sequence: trippy-dns
- FunctionTooLong: trippy_tui::frontend::run_app crates/trippy-tui/src/frontend.rs:72
- FunctionTooLong: trippy_tui::frontend::render::header::render crates/trippy-tui/src/frontend/render/header.rs:18
- Edited copy of a member (40 corresponding lines) crates/trippy-tui/src/config/binding.rs:517
- Edited copy of a member (40 corresponding lines) crates/trippy-tui/src/frontend/render/header.rs:155
- Edited copy of a member (12 corresponding lines) crates/trippy-core/src/net/ipv4.rs:407
- Edited copy of a member (12 corresponding lines) crates/trippy-tui/src/frontend/tui_app.rs:214
- Edited copy of a member (8 corresponding lines) crates/trippy-core/src/tracer.rs:239
- Edited copy of a member (8 corresponding lines) crates/trippy-packet/src/ipv4.rs:128
- Edited copy of a member (11 corresponding lines) crates/trippy-core/src/net/platform/windows.rs:351
- Edited copy of a member (11 corresponding lines) crates/trippy-core/src/net/platform/unix.rs:429
- Edited copy of a member (9 corresponding lines) crates/trippy-packet/src/icmpv4.rs:873
- Edited copy of a member (9 corresponding lines) crates/trippy-core/src/net/ipv4.rs:510
- Edited copy of a member (7 corresponding lines) crates/trippy-core/src/net/channel.rs:120
- Edited copy of a member (7 corresponding lines) crates/trippy-core/src/net/platform/unix.rs:381
- Duplicated block (16 lines × 2) crates/trippy-core/src/net/ipv4.rs:270
- Duplicated block (16 lines × 2) crates/trippy-tui/src/config/binding.rs:536
- Duplicated block (13 lines × 2) crates/trippy-core/src/net/ipv4.rs:127
- Duplicated block (13 lines × 2) crates/trippy-tui/src/frontend/render/header.rs:42
- Duplicated block (12 lines × 18) crates/trippy-packet/src/icmp_extension.rs:17
- Duplicated block (12 lines × 18) crates/trippy-packet/src/icmp_extension.rs:31
- trippy_tui::frontend::run_app (cyclomatic 74) crates/trippy-tui/src/frontend.rs:72
- TrippyConfig::build_config (cyclomatic 25) crates/trippy-tui/src/config.rs:362
- trippy_tui::frontend::run_app (cognitive 91) crates/trippy-tui/src/frontend.rs:72
- Strategy::send_request (cognitive 23) crates/trippy-core/src/strategy.rs:107
- DnsResolver::lookup (cognitive 20) crates/trippy-dns/src/lazy_resolver.rs:216
- trippy_dns::lazy_resolver::inner::reverse_lookup (cognitive 17) crates/trippy-dns/src/lazy_resolver.rs:364
- trippy_packet::icmp_extension::extension_splitter::split (cognitive 16) crates/trippy-packet/src/icmp_extension.rs:896
- ClassTooLong: TrippyConfig crates/trippy-tui/src/config.rs:290
- REDACTED
- REDACTED
- REDACTED
- Near-duplicate member pair (57 shared lines) crates/trippy-core/src/net/ipv4.rs:288
- Members sharing a duplicated core (4 members, 50+ identical tokens) crates/trippy-packet/src/icmpv4.rs:357
- Edited copy of a member (38 corresponding lines) crates/trippy-core/src/net/ipv4.rs:248
- Edited copy of a member (41 corresponding lines) crates/trippy-core/src/net/ipv4.rs:358
- Edited copy of a member (16 corresponding lines) crates/trippy-packet/src/ipv4.rs:224
- Edited copy of a member (19 corresponding lines) crates/trippy-core/src/net/platform/unix.rs:389
- Edited copies of one member (3 members, 13+ corresponding lines) crates/trippy-dns/src/lazy_resolver.rs:436
- Edited copies of one member (3 members, 12+ corresponding lines) crates/trippy-core/src/net/platform/unix.rs:234
- Edited copies of one member (4 members, 4+ corresponding lines) crates/trippy-packet/src/icmp_extension.rs:252
- Edited copy of a member (5 corresponding lines) crates/trippy-core/src/net/platform/unix.rs:368
- Duplicated block (32 lines × 2) crates/trippy-core/src/net/ipv4.rs:324
- Duplicated block (18 lines × 2) crates/trippy-core/src/net/ipv4.rs:251
- Duplicated block (17 lines × 2) crates/trippy-core/src/net/ipv4.rs:306
- Duplicated block (15 lines × 2) crates/trippy-tui/src/frontend.rs:122
- Duplicated block (10 lines × 2) crates/trippy-core/src/net/platform/unix.rs:398
- Duplicated block (7 lines × 4) crates/trippy-tui/src/frontend/render/flows.rs:18
- Duplicated block (7 lines × 3) crates/trippy-dns/src/lazy_resolver.rs:440
- Duplicated block (6 lines × 4) crates/trippy-packet/src/icmpv4.rs:361
- Duplicated block (5 lines × 2) crates/trippy-core/src/net/ipv6.rs:100
- Duplicated block (5 lines × 4) crates/trippy-packet/src/icmpv4.rs:862
- Duplicated block (14 lines × 3) crates/trippy-tui/src/frontend/render/header.rs:41
- Low cohesion: TuiApp (LCOM4 4) crates/trippy-tui/src/frontend/tui_app.rs:13
Minor — 13 finding(s)
- No ADRs found crates/trippy/Cargo.toml:16
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- Logging is not universal
- Dependabot does not watch github-actions/npm REDACTED:2
- Strict null checking is not enabled everywhere the repository type-checks
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-8d24bc56e7a04e75952f995a1f588503/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-8d24bc56e7a04e75952f995a1f588503/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 47 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 3 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 7 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |