Executive summary
tokio-rs/mio falls short of our standard for production because we found no recorded design decisions and no architecture document or diagram. It scores 66 out of 100 and is rated Adequate, and 42 of its 44 critical findings are security problems in the build pipeline.
Maturity, at 53, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 11 points. Adding tests for untested code comes next, worth about 5 points. Raising Maturity to 70 would lift the score to about 73.
Forty-two pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. One set of files in separate parts keeps changing together, which points to a hidden dependency. Pinning each tool to an exact version and making the hidden dependencies explicit would close both risks. The test the project itself marks as unreliable needs fixing or deleting.
The product code is 12,194 lines, about €24,000 to rebuild.
If Maturity rose from 53 to 70, the lowest score rated Strong, the score would rise from 66 to about 73.
New since the last survey: 21 findings
- Code Duplication · Edited copy of a member (26 corresponding lines) src/sys/unix/selector/kqueue.rs
- Code Duplication · Edited copy of a member (17 corresponding lines) src/sys/windows/named_pipe.rs
- Code Duplication · Edited copy of a member (10 corresponding lines) src/sys/unix/waker/eventfd.rs
- Code Duplication · Edited copy of a member (13 corresponding lines) src/io_source.rs
- Code Duplication · Edited copy of a member (12 corresponding lines) src/sys/windows/named_pipe.rs
- Code Duplication · Edited copy of a member (5 corresponding lines) src/sys/unix/tcp.rs
- Code Duplication · Edited copy of a member (8 corresponding lines) src/sys/unix/selector/epoll.rs
- Code Duplication · Edited copy of a member (13 corresponding lines) src/sys/unix/selector/event_ports.rs
- Code Duplication · Duplicated block (11–15 lines × 2) src/sys/unix/selector/event_ports.rs
- Code Duplication · Duplicated block (8 lines × 3) src/sys/unix/selector/event_ports.rs
- Code Duplication · Duplicated block (5 lines × 2) src/sys/windows/named_pipe.rs
- Code Coverage · Low coverage: src/event/event.rs src/event/event.rs
- Code Coverage · Low coverage: src/event/events.rs src/event/events.rs
- Code Coverage · Low coverage: src/event/source.rs src/event/source.rs
- Code Coverage · Low coverage: src/poll.rs src/poll.rs
- Code Coverage · Low coverage: src/sys/shell/selector.rs src/sys/shell/selector.rs
- Code Coverage · Low coverage: src/sys/shell/waker.rs src/sys/shell/waker.rs
- Code Coverage · Low coverage: src/token.rs src/token.rs
- Code Coverage · Low coverage: src/waker.rs src/waker.rs
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
Fixed since the last survey: 9 findings
- Code Duplication · Duplicated block (11–15 lines × 2) src/sys/unix/selector/event_ports.rs
- Code Duplication · Duplicated block (14 lines × 2) src/sys/windows/named_pipe.rs
- Code Duplication · Duplicated block (8 lines × 3) src/sys/unix/selector/event_ports.rs
- Code Duplication · Duplicated block (8 lines × 2) src/sys/unix/selector/epoll.rs
- Secrets (history) · Secret: aws-access-token REDACTED
- Secrets (history) · Secret: aws-access-token REDACTED
- Secrets (history) · Secret: aws-access-token REDACTED
- Static Analysis (SAST) · High: REDACTED REDACTED
- Change Coupling · Change coupling: stream.rs ↔ udp.rs src/net/tcp/stream.rs
Rebuild cost: about €24,000 · Estimate
| Cost to rebuild | €8,000 to €40,000, for 134 to 425 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 66. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 12,194 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture: which parts of the code depend on which
| uses → | 1 event.events | 2 interest | 3 sys.windows.handle | 4 token | 5 event.event | 6 sys.shell.selector | 7 sys.unix.selector.epoll | 8 sys.windows.iocp | 9 poll | 10 sys.shell.selector.event | 11 sys.shell.waker | 12 sys.unix.selector.epoll.event | 13 sys.unix.selector.event_ports | 14 sys.unix.selector.event_ports.event | 15 sys.unix.selector.kqueue | 16 sys.unix.selector.kqueue.event | 17 sys.unix.selector.poll.event | 18 sys.unix.waker.eventfd | 19 sys.unix.waker.pipe | 20 sys.unix.waker.selector | 21 sys.wasip1 | 22 sys.wasip1.event | 23 sys.windows.event | 24 sys.windows.selector | 25 sys.windows.waker | 26 event.source | 27 sys.unix.selector.poll | 28 sys.unix.selector.stateless_io_source | 29 waker | 30 io_source | 31 sys.unix.sourcefd | 32 sys.windows.named_pipe | 33 net.tcp.listener | 34 net.tcp.stream | 35 net.udp | 36 net.uds.datagram | 37 net.uds.listener | 38 net.uds.stream | 39 sys.shell.tcp | 40 sys.unix.tcp |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 event.events | ||||||||||||||||||||||||||||||||||||||||
| 2 interest | ||||||||||||||||||||||||||||||||||||||||
| 3 sys.windows.handle | ||||||||||||||||||||||||||||||||||||||||
| 4 token | ||||||||||||||||||||||||||||||||||||||||
| 5 event.event | 1 | |||||||||||||||||||||||||||||||||||||||
| 6 sys.shell.selector | 1 | |||||||||||||||||||||||||||||||||||||||
| 7 sys.unix.selector.epoll | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 8 sys.windows.iocp | 1 | |||||||||||||||||||||||||||||||||||||||
| 9 poll | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 10 sys.shell.selector.event | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 11 sys.shell.waker | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 12 sys.unix.selector.epoll.event | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 13 sys.unix.selector.event_ports | 4 | 2 | 4 | 1 | ||||||||||||||||||||||||||||||||||||
| 14 sys.unix.selector.event_ports.event | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 15 sys.unix.selector.kqueue | 2 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 16 sys.unix.selector.kqueue.event | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 17 sys.unix.selector.poll.event | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 18 sys.unix.waker.eventfd | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 19 sys.unix.waker.pipe | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 20 sys.unix.waker.selector | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 21 sys.wasip1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 22 sys.wasip1.event | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 23 sys.windows.event | 1 | 2 | 3 | 1 | ||||||||||||||||||||||||||||||||||||
| 24 sys.windows.selector | 2 | 2 | 3 | |||||||||||||||||||||||||||||||||||||
| 25 sys.windows.waker | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 26 event.source | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 27 sys.unix.selector.poll | 2 | 3 | 5 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 28 sys.unix.selector.stateless_io_source | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 29 waker | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 30 io_source | 1 | 1 | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 31 sys.unix.sourcefd | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 32 sys.windows.named_pipe | 1 | 1 | 2 | 3 | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||
| 33 net.tcp.listener | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 34 net.tcp.stream | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 35 net.udp | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 36 net.uds.datagram | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 37 net.uds.listener | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 38 net.uds.stream | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 39 sys.shell.tcp | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 40 sys.unix.tcp | 1 | 1 |
5→4 event.event uses token✕
- Connections
- 1 pair of types, where a type in event.event uses a type in token.
- The types involved
mio.event.event.Event→mio.token.Token
- Direction
- event.event uses token, so a change to token can break event.event, while a change to event.event can't break token.
- Position
- Below the diagonal: event.event uses a module listed above it, which is the healthy direction.
6→1 sys.shell.selector uses event.events✕
- Connections
- 1 pair of types, where a type in sys.shell.selector uses a type in event.events.
- The types involved
mio.sys.shell.selector.Selector→mio.event.events.Events
- Direction
- sys.shell.selector uses event.events, so a change to event.events can break sys.shell.selector, while a change to sys.shell.selector can't break event.events.
- Position
- Below the diagonal: sys.shell.selector uses a module listed above it, which is the healthy direction.
7→1 sys.unix.selector.epoll uses event.events✕
- Connections
- 1 pair of types, where a type in sys.unix.selector.epoll uses a type in event.events.
- The types involved
mio.sys.unix.selector.epoll.Selector→mio.event.events.Events
- Direction
- sys.unix.selector.epoll uses event.events, so a change to event.events can break sys.unix.selector.epoll, while a change to sys.unix.selector.epoll can't break event.events.
- Position
- Below the diagonal: sys.unix.selector.epoll uses a module listed above it, which is the healthy direction.
7→2 sys.unix.selector.epoll uses interest✕
- Connections
- 2 pairs of types, where a type in sys.unix.selector.epoll uses a type in interest.
- The types involved
mio.sys.unix.selector.epoll.Selector→mio.interest.Interestmio.sys.unix.selector.epoll.epoll$module→mio.interest.Interest
- Direction
- sys.unix.selector.epoll uses interest, so a change to interest can break sys.unix.selector.epoll, while a change to sys.unix.selector.epoll can't break interest.
- Position
- Below the diagonal: sys.unix.selector.epoll uses a module listed above it, which is the healthy direction.
7→4 sys.unix.selector.epoll uses token✕
- Connections
- 1 pair of types, where a type in sys.unix.selector.epoll uses a type in token.
- The types involved
mio.sys.unix.selector.epoll.Selector→mio.token.Token
- Direction
- sys.unix.selector.epoll uses token, so a change to token can break sys.unix.selector.epoll, while a change to sys.unix.selector.epoll can't break token.
- Position
- Below the diagonal: sys.unix.selector.epoll uses a module listed above it, which is the healthy direction.
8→3 sys.windows.iocp uses sys.windows.handle✕
- Connections
- 1 pair of types, where a type in sys.windows.iocp uses a type in sys.windows.handle.
- The types involved
mio.sys.windows.iocp.CompletionPort→mio.sys.windows.handle.Handle
- Direction
- sys.windows.iocp uses sys.windows.handle, so a change to sys.windows.handle can break sys.windows.iocp, while a change to sys.windows.iocp can't break sys.windows.handle.
- Position
- Below the diagonal: sys.windows.iocp uses a module listed above it, which is the healthy direction.
9→1 poll uses event.events✕
- Connections
- 1 pair of types, where a type in poll uses a type in event.events.
- The types involved
mio.poll.Poll→mio.event.events.Events
- Direction
- poll uses event.events, so a change to event.events can break poll, while a change to poll can't break event.events.
- Position
- Below the diagonal: poll uses a module listed above it, which is the healthy direction.
9→2 poll uses interest✕
- Connections
- 1 pair of types, where a type in poll uses a type in interest.
- The types involved
mio.poll.Registry→mio.interest.Interest
- Direction
- poll uses interest, so a change to interest can break poll, while a change to poll can't break interest.
- Position
- Below the diagonal: poll uses a module listed above it, which is the healthy direction.
9→4 poll uses token✕
- Connections
- 1 pair of types, where a type in poll uses a type in token.
- The types involved
mio.poll.Registry→mio.token.Token
- Direction
- poll uses token, so a change to token can break poll, while a change to poll can't break token.
- Position
- Below the diagonal: poll uses a module listed above it, which is the healthy direction.
9→6 poll uses sys.shell.selector✕
- Connections
- 1 pair of types, where a type in poll uses a type in sys.shell.selector.
- The types involved
mio.poll.Registry→mio.sys.shell.selector.Selector
- Direction
- poll uses sys.shell.selector, so a change to sys.shell.selector can break poll, while a change to poll can't break sys.shell.selector.
- Position
- Below the diagonal: poll uses a module listed above it, which is the healthy direction.
10→4 sys.shell.selector.event uses token✕
- Connections
- 1 pair of types, where a type in sys.shell.selector.event uses a type in token.
- The types involved
mio.sys.shell.selector.event.event$module→mio.token.Token
- Direction
- sys.shell.selector.event uses token, so a change to token can break sys.shell.selector.event, while a change to sys.shell.selector.event can't break token.
- Position
- Below the diagonal: sys.shell.selector.event uses a module listed above it, which is the healthy direction.
10→5 sys.shell.selector.event uses event.event✕
- Connections
- 1 pair of types, where a type in sys.shell.selector.event uses a type in event.event.
- The types involved
mio.sys.shell.selector.event.event$module→mio.event.event.Event
- Direction
- sys.shell.selector.event uses event.event, so a change to event.event can break sys.shell.selector.event, while a change to sys.shell.selector.event can't break event.event.
- Position
- Below the diagonal: sys.shell.selector.event uses a module listed above it, which is the healthy direction.
11→4 sys.shell.waker uses token✕
- Connections
- 1 pair of types, where a type in sys.shell.waker uses a type in token.
- The types involved
mio.sys.shell.waker.Waker→mio.token.Token
- Direction
- sys.shell.waker uses token, so a change to token can break sys.shell.waker, while a change to sys.shell.waker can't break token.
- Position
- Below the diagonal: sys.shell.waker uses a module listed above it, which is the healthy direction.
11→6 sys.shell.waker uses sys.shell.selector✕
- Connections
- 1 pair of types, where a type in sys.shell.waker uses a type in sys.shell.selector.
- The types involved
mio.sys.shell.waker.Waker→mio.sys.shell.selector.Selector
- Direction
- sys.shell.waker uses sys.shell.selector, so a change to sys.shell.selector can break sys.shell.waker, while a change to sys.shell.waker can't break sys.shell.selector.
- Position
- Below the diagonal: sys.shell.waker uses a module listed above it, which is the healthy direction.
12→4 sys.unix.selector.epoll.event uses token✕
- Connections
- 1 pair of types, where a type in sys.unix.selector.epoll.event uses a type in token.
- The types involved
mio.sys.unix.selector.epoll.event.event$module→mio.token.Token
- Direction
- sys.unix.selector.epoll.event uses token, so a change to token can break sys.unix.selector.epoll.event, while a change to sys.unix.selector.epoll.event can't break token.
- Position
- Below the diagonal: sys.unix.selector.epoll.event uses a module listed above it, which is the healthy direction.
12→5 sys.unix.selector.epoll.event uses event.event✕
- Connections
- 1 pair of types, where a type in sys.unix.selector.epoll.event uses a type in event.event.
- The types involved
mio.sys.unix.selector.epoll.event.event$module→mio.event.event.Event
- Direction
- sys.unix.selector.epoll.event uses event.event, so a change to event.event can break sys.unix.selector.epoll.event, while a change to sys.unix.selector.epoll.event can't break event.event.
- Position
- Below the diagonal: sys.unix.selector.epoll.event uses a module listed above it, which is the healthy direction.
13→1 sys.unix.selector.event_ports uses event.events✕
- Connections
- 4 pairs of types, where a type in sys.unix.selector.event_ports uses a type in event.events.
- The types involved
mio.sys.unix.selector.event_ports.Events→mio.event.events.Eventsmio.sys.unix.selector.event_ports.Selector→mio.event.events.Eventsmio.sys.unix.selector.event_ports.SelectorState→mio.event.events.Eventsmio.sys.unix.selector.event_ports.event_ports$module→mio.event.events.Events
- Direction
- sys.unix.selector.event_ports uses event.events, so a change to event.events can break sys.unix.selector.event_ports, while a change to sys.unix.selector.event_ports can't break event.events.
- Position
- Below the diagonal: sys.unix.selector.event_ports uses a module listed above it, which is the healthy direction.
13→2 sys.unix.selector.event_ports uses interest✕
- Connections
- 2 pairs of types, where a type in sys.unix.selector.event_ports uses a type in interest.
- The types involved
mio.sys.unix.selector.event_ports.FdData→mio.interest.Interestmio.sys.unix.selector.event_ports.event_ports$module→mio.interest.Interest
- Direction
- sys.unix.selector.event_ports uses interest, so a change to interest can break sys.unix.selector.event_ports, while a change to sys.unix.selector.event_ports can't break interest.
- Position
- Below the diagonal: sys.unix.selector.event_ports uses a module listed above it, which is the healthy direction.
13→4 sys.unix.selector.event_ports uses token✕
- Connections
- 4 pairs of types, where a type in sys.unix.selector.event_ports uses a type in token.
- The types involved
mio.sys.unix.selector.event_ports.FdData→mio.token.Tokenmio.sys.unix.selector.event_ports.Selector→mio.token.Tokenmio.sys.unix.selector.event_ports.SelectorState→mio.token.Tokenmio.sys.unix.selector.event_ports.event_ports$module→mio.token.Token
- Direction
- sys.unix.selector.event_ports uses token, so a change to token can break sys.unix.selector.event_ports, while a change to sys.unix.selector.event_ports can't break token.
- Position
- Below the diagonal: sys.unix.selector.event_ports uses a module listed above it, which is the healthy direction.
13→5 sys.unix.selector.event_ports uses event.event✕
- Connections
- 1 pair of types, where a type in sys.unix.selector.event_ports uses a type in event.event.
- The types involved
mio.sys.unix.selector.event_ports.Events→mio.event.event.Event
- Direction
- sys.unix.selector.event_ports uses event.event, so a change to event.event can break sys.unix.selector.event_ports, while a change to sys.unix.selector.event_ports can't break event.event.
- Position
- Below the diagonal: sys.unix.selector.event_ports uses a module listed above it, which is the healthy direction.
14→4 sys.unix.selector.event_ports.event uses token✕
- Connections
- 1 pair of types, where a type in sys.unix.selector.event_ports.event uses a type in token.
- The types involved
mio.sys.unix.selector.event_ports.event.event$module→mio.token.Token
- Direction
- sys.unix.selector.event_ports.event uses token, so a change to token can break sys.unix.selector.event_ports.event, while a change to sys.unix.selector.event_ports.event can't break token.
- Position
- Below the diagonal: sys.unix.selector.event_ports.event uses a module listed above it, which is the healthy direction.
14→5 sys.unix.selector.event_ports.event uses event.event✕
- Connections
- 1 pair of types, where a type in sys.unix.selector.event_ports.event uses a type in event.event.
- The types involved
mio.sys.unix.selector.event_ports.event.event$module→mio.event.event.Event
- Direction
- sys.unix.selector.event_ports.event uses event.event, so a change to event.event can break sys.unix.selector.event_ports.event, while a change to sys.unix.selector.event_ports.event can't break event.event.
- Position
- Below the diagonal: sys.unix.selector.event_ports.event uses a module listed above it, which is the healthy direction.
15→1 sys.unix.selector.kqueue uses event.events✕
- Connections
- 2 pairs of types, where a type in sys.unix.selector.kqueue uses a type in event.events.
- The types involved
mio.sys.unix.selector.kqueue.Events→mio.event.events.Eventsmio.sys.unix.selector.kqueue.Selector→mio.event.events.Events
- Direction
- sys.unix.selector.kqueue uses event.events, so a change to event.events can break sys.unix.selector.kqueue, while a change to sys.unix.selector.kqueue can't break event.events.
- Position
- Below the diagonal: sys.unix.selector.kqueue uses a module listed above it, which is the healthy direction.
15→2 sys.unix.selector.kqueue uses interest✕
- Connections
- 1 pair of types, where a type in sys.unix.selector.kqueue uses a type in interest.
- The types involved
mio.sys.unix.selector.kqueue.Selector→mio.interest.Interest
- Direction
- sys.unix.selector.kqueue uses interest, so a change to interest can break sys.unix.selector.kqueue, while a change to sys.unix.selector.kqueue can't break interest.
- Position
- Below the diagonal: sys.unix.selector.kqueue uses a module listed above it, which is the healthy direction.
15→4 sys.unix.selector.kqueue uses token✕
- Connections
- 1 pair of types, where a type in sys.unix.selector.kqueue uses a type in token.
- The types involved
mio.sys.unix.selector.kqueue.Selector→mio.token.Token
- Direction
- sys.unix.selector.kqueue uses token, so a change to token can break sys.unix.selector.kqueue, while a change to sys.unix.selector.kqueue can't break token.
- Position
- Below the diagonal: sys.unix.selector.kqueue uses a module listed above it, which is the healthy direction.
15→5 sys.unix.selector.kqueue uses event.event✕
- Connections
- 1 pair of types, where a type in sys.unix.selector.kqueue uses a type in event.event.
- The types involved
mio.sys.unix.selector.kqueue.Events→mio.event.event.Event
- Direction
- sys.unix.selector.kqueue uses event.event, so a change to event.event can break sys.unix.selector.kqueue, while a change to sys.unix.selector.kqueue can't break event.event.
- Position
- Below the diagonal: sys.unix.selector.kqueue uses a module listed above it, which is the healthy direction.
16→4 sys.unix.selector.kqueue.event uses token✕
- Connections
- 1 pair of types, where a type in sys.unix.selector.kqueue.event uses a type in token.
- The types involved
mio.sys.unix.selector.kqueue.event.event$module→mio.token.Token
- Direction
- sys.unix.selector.kqueue.event uses token, so a change to token can break sys.unix.selector.kqueue.event, while a change to sys.unix.selector.kqueue.event can't break token.
- Position
- Below the diagonal: sys.unix.selector.kqueue.event uses a module listed above it, which is the healthy direction.
16→5 sys.unix.selector.kqueue.event uses event.event✕
- Connections
- 1 pair of types, where a type in sys.unix.selector.kqueue.event uses a type in event.event.
- The types involved
mio.sys.unix.selector.kqueue.event.event$module→mio.event.event.Event
- Direction
- sys.unix.selector.kqueue.event uses event.event, so a change to event.event can break sys.unix.selector.kqueue.event, while a change to sys.unix.selector.kqueue.event can't break event.event.
- Position
- Below the diagonal: sys.unix.selector.kqueue.event uses a module listed above it, which is the healthy direction.
17→4 sys.unix.selector.poll.event uses token✕
- Connections
- 1 pair of types, where a type in sys.unix.selector.poll.event uses a type in token.
- The types involved
mio.sys.unix.selector.poll.event.event$module→mio.token.Token
- Direction
- sys.unix.selector.poll.event uses token, so a change to token can break sys.unix.selector.poll.event, while a change to sys.unix.selector.poll.event can't break token.
- Position
- Below the diagonal: sys.unix.selector.poll.event uses a module listed above it, which is the healthy direction.
17→5 sys.unix.selector.poll.event uses event.event✕
- Connections
- 1 pair of types, where a type in sys.unix.selector.poll.event uses a type in event.event.
- The types involved
mio.sys.unix.selector.poll.event.event$module→mio.event.event.Event
- Direction
- sys.unix.selector.poll.event uses event.event, so a change to event.event can break sys.unix.selector.poll.event, while a change to sys.unix.selector.poll.event can't break event.event.
- Position
- Below the diagonal: sys.unix.selector.poll.event uses a module listed above it, which is the healthy direction.
18→4 sys.unix.waker.eventfd uses token✕
- Connections
- 1 pair of types, where a type in sys.unix.waker.eventfd uses a type in token.
- The types involved
mio.sys.unix.waker.eventfd.Waker→mio.token.Token
- Direction
- sys.unix.waker.eventfd uses token, so a change to token can break sys.unix.waker.eventfd, while a change to sys.unix.waker.eventfd can't break token.
- Position
- Below the diagonal: sys.unix.waker.eventfd uses a module listed above it, which is the healthy direction.
18→6 sys.unix.waker.eventfd uses sys.shell.selector✕
- Connections
- 1 pair of types, where a type in sys.unix.waker.eventfd uses a type in sys.shell.selector.
- The types involved
mio.sys.unix.waker.eventfd.Waker→mio.sys.shell.selector.Selector
- Direction
- sys.unix.waker.eventfd uses sys.shell.selector, so a change to sys.shell.selector can break sys.unix.waker.eventfd, while a change to sys.unix.waker.eventfd can't break sys.shell.selector.
- Position
- Below the diagonal: sys.unix.waker.eventfd uses a module listed above it, which is the healthy direction.
19→4 sys.unix.waker.pipe uses token✕
- Connections
- 1 pair of types, where a type in sys.unix.waker.pipe uses a type in token.
- The types involved
mio.sys.unix.waker.pipe.Waker→mio.token.Token
- Direction
- sys.unix.waker.pipe uses token, so a change to token can break sys.unix.waker.pipe, while a change to sys.unix.waker.pipe can't break token.
- Position
- Below the diagonal: sys.unix.waker.pipe uses a module listed above it, which is the healthy direction.
19→6 sys.unix.waker.pipe uses sys.shell.selector✕
- Connections
- 1 pair of types, where a type in sys.unix.waker.pipe uses a type in sys.shell.selector.
- The types involved
mio.sys.unix.waker.pipe.Waker→mio.sys.shell.selector.Selector
- Direction
- sys.unix.waker.pipe uses sys.shell.selector, so a change to sys.shell.selector can break sys.unix.waker.pipe, while a change to sys.unix.waker.pipe can't break sys.shell.selector.
- Position
- Below the diagonal: sys.unix.waker.pipe uses a module listed above it, which is the healthy direction.
20→4 sys.unix.waker.selector uses token✕
- Connections
- 1 pair of types, where a type in sys.unix.waker.selector uses a type in token.
- The types involved
mio.sys.unix.waker.selector.Waker→mio.token.Token
- Direction
- sys.unix.waker.selector uses token, so a change to token can break sys.unix.waker.selector, while a change to sys.unix.waker.selector can't break token.
- Position
- Below the diagonal: sys.unix.waker.selector uses a module listed above it, which is the healthy direction.
20→6 sys.unix.waker.selector uses sys.shell.selector✕
- Connections
- 1 pair of types, where a type in sys.unix.waker.selector uses a type in sys.shell.selector.
- The types involved
mio.sys.unix.waker.selector.Waker→mio.sys.shell.selector.Selector
- Direction
- sys.unix.waker.selector uses sys.shell.selector, so a change to sys.shell.selector can break sys.unix.waker.selector, while a change to sys.unix.waker.selector can't break sys.shell.selector.
- Position
- Below the diagonal: sys.unix.waker.selector uses a module listed above it, which is the healthy direction.
21→1 sys.wasip1 uses event.events✕
- Connections
- 1 pair of types, where a type in sys.wasip1 uses a type in event.events.
- The types involved
mio.sys.wasip1.Selector→mio.event.events.Events
- Direction
- sys.wasip1 uses event.events, so a change to event.events can break sys.wasip1, while a change to sys.wasip1 can't break event.events.
- Position
- Below the diagonal: sys.wasip1 uses a module listed above it, which is the healthy direction.
21→5 sys.wasip1 uses event.event✕
- Connections
- 1 pair of types, where a type in sys.wasip1 uses a type in event.event.
- The types involved
mio.sys.wasip1.wasip1$module→mio.event.event.Event
- Direction
- sys.wasip1 uses event.event, so a change to event.event can break sys.wasip1, while a change to sys.wasip1 can't break event.event.
- Position
- Below the diagonal: sys.wasip1 uses a module listed above it, which is the healthy direction.
22→4 sys.wasip1.event uses token✕
- Connections
- 1 pair of types, where a type in sys.wasip1.event uses a type in token.
- The types involved
mio.sys.wasip1.event.event$module→mio.token.Token
- Direction
- sys.wasip1.event uses token, so a change to token can break sys.wasip1.event, while a change to sys.wasip1.event can't break token.
- Position
- Below the diagonal: sys.wasip1.event uses a module listed above it, which is the healthy direction.
22→5 sys.wasip1.event uses event.event✕
- Connections
- 1 pair of types, where a type in sys.wasip1.event uses a type in event.event.
- The types involved
mio.sys.wasip1.event.event$module→mio.event.event.Event
- Direction
- sys.wasip1.event uses event.event, so a change to event.event can break sys.wasip1.event, while a change to sys.wasip1.event can't break event.event.
- Position
- Below the diagonal: sys.wasip1.event uses a module listed above it, which is the healthy direction.
23→1 sys.windows.event uses event.events✕
- Connections
- 1 pair of types, where a type in sys.windows.event uses a type in event.events.
- The types involved
mio.sys.windows.event.Events→mio.event.events.Events
- Direction
- sys.windows.event uses event.events, so a change to event.events can break sys.windows.event, while a change to sys.windows.event can't break event.events.
- Position
- Below the diagonal: sys.windows.event uses a module listed above it, which is the healthy direction.
23→4 sys.windows.event uses token✕
- Connections
- 2 pairs of types, where a type in sys.windows.event uses a type in token.
- The types involved
mio.sys.windows.event.Event→mio.token.Tokenmio.sys.windows.event.event$module→mio.token.Token
- Direction
- sys.windows.event uses token, so a change to token can break sys.windows.event, while a change to sys.windows.event can't break token.
- Position
- Below the diagonal: sys.windows.event uses a module listed above it, which is the healthy direction.
23→5 sys.windows.event uses event.event✕
- Connections
- 3 pairs of types, where a type in sys.windows.event uses a type in event.event.
- The types involved
mio.sys.windows.event.Event→mio.event.event.Eventmio.sys.windows.event.Events→mio.event.event.Eventmio.sys.windows.event.event$module→mio.event.event.Event
- Direction
- sys.windows.event uses event.event, so a change to event.event can break sys.windows.event, while a change to sys.windows.event can't break event.event.
- Position
- Below the diagonal: sys.windows.event uses a module listed above it, which is the healthy direction.
23→8 sys.windows.event uses sys.windows.iocp✕
- Connections
- 1 pair of types, where a type in sys.windows.event uses a type in sys.windows.iocp.
- The types involved
mio.sys.windows.event.Event→mio.sys.windows.iocp.CompletionStatus
- Direction
- sys.windows.event uses sys.windows.iocp, so a change to sys.windows.iocp can break sys.windows.event, while a change to sys.windows.event can't break sys.windows.iocp.
- Position
- Below the diagonal: sys.windows.event uses a module listed above it, which is the healthy direction.
24→1 sys.windows.selector uses event.events✕
- Connections
- 2 pairs of types, where a type in sys.windows.selector uses a type in event.events.
- The types involved
mio.sys.windows.selector.Selector→mio.event.events.Eventsmio.sys.windows.selector.SelectorInner→mio.event.events.Events
- Direction
- sys.windows.selector uses event.events, so a change to event.events can break sys.windows.selector, while a change to sys.windows.selector can't break event.events.
- Position
- Below the diagonal: sys.windows.selector uses a module listed above it, which is the healthy direction.
24→5 sys.windows.selector uses event.event✕
- Connections
- 2 pairs of types, where a type in sys.windows.selector uses a type in event.event.
- The types involved
mio.sys.windows.selector.SelectorInner→mio.event.event.Eventmio.sys.windows.selector.SockState→mio.event.event.Event
- Direction
- sys.windows.selector uses event.event, so a change to event.event can break sys.windows.selector, while a change to sys.windows.selector can't break event.event.
- Position
- Below the diagonal: sys.windows.selector uses a module listed above it, which is the healthy direction.
24→8 sys.windows.selector uses sys.windows.iocp✕
- Connections
- 3 pairs of types, where a type in sys.windows.selector uses a type in sys.windows.iocp.
- The types involved
mio.sys.windows.selector.AfdGroup→mio.sys.windows.iocp.CompletionPortmio.sys.windows.selector.Selector→mio.sys.windows.iocp.CompletionPortmio.sys.windows.selector.SelectorInner→mio.sys.windows.iocp.CompletionPort
- Direction
- sys.windows.selector uses sys.windows.iocp, so a change to sys.windows.iocp can break sys.windows.selector, while a change to sys.windows.selector can't break sys.windows.iocp.
- Position
- Below the diagonal: sys.windows.selector uses a module listed above it, which is the healthy direction.
25→4 sys.windows.waker uses token✕
- Connections
- 1 pair of types, where a type in sys.windows.waker uses a type in token.
- The types involved
mio.sys.windows.waker.Waker→mio.token.Token
- Direction
- sys.windows.waker uses token, so a change to token can break sys.windows.waker, while a change to sys.windows.waker can't break token.
- Position
- Below the diagonal: sys.windows.waker uses a module listed above it, which is the healthy direction.
25→6 sys.windows.waker uses sys.shell.selector✕
- Connections
- 1 pair of types, where a type in sys.windows.waker uses a type in sys.shell.selector.
- The types involved
mio.sys.windows.waker.Waker→mio.sys.shell.selector.Selector
- Direction
- sys.windows.waker uses sys.shell.selector, so a change to sys.shell.selector can break sys.windows.waker, while a change to sys.windows.waker can't break sys.shell.selector.
- Position
- Below the diagonal: sys.windows.waker uses a module listed above it, which is the healthy direction.
25→8 sys.windows.waker uses sys.windows.iocp✕
- Connections
- 1 pair of types, where a type in sys.windows.waker uses a type in sys.windows.iocp.
- The types involved
mio.sys.windows.waker.Waker→mio.sys.windows.iocp.CompletionPort
- Direction
- sys.windows.waker uses sys.windows.iocp, so a change to sys.windows.iocp can break sys.windows.waker, while a change to sys.windows.waker can't break sys.windows.iocp.
- Position
- Below the diagonal: sys.windows.waker uses a module listed above it, which is the healthy direction.
26→2 event.source uses interest✕
- Connections
- 1 pair of types, where a type in event.source uses a type in interest.
- The types involved
mio.event.source.Source→mio.interest.Interest
- Direction
- event.source uses interest, so a change to interest can break event.source, while a change to event.source can't break interest.
- Position
- Below the diagonal: event.source uses a module listed above it, which is the healthy direction.
26→4 event.source uses token✕
- Connections
- 1 pair of types, where a type in event.source uses a type in token.
- The types involved
mio.event.source.Source→mio.token.Token
- Direction
- event.source uses token, so a change to token can break event.source, while a change to event.source can't break token.
- Position
- Below the diagonal: event.source uses a module listed above it, which is the healthy direction.
26→9 event.source uses poll✕
- Connections
- 1 pair of types, where a type in event.source uses a type in poll.
- The types involved
mio.event.source.Source→mio.poll.Registry
- Direction
- event.source uses poll, so a change to poll can break event.source, while a change to event.source can't break poll.
- Position
- Below the diagonal: event.source uses a module listed above it, which is the healthy direction.
27→1 sys.unix.selector.poll uses event.events✕
- Connections
- 2 pairs of types, where a type in sys.unix.selector.poll uses a type in event.events.
- The types involved
mio.sys.unix.selector.poll.Selector→mio.event.events.Eventsmio.sys.unix.selector.poll.SelectorState→mio.event.events.Events
- Direction
- sys.unix.selector.poll uses event.events, so a change to event.events can break sys.unix.selector.poll, while a change to sys.unix.selector.poll can't break event.events.
- Position
- Below the diagonal: sys.unix.selector.poll uses a module listed above it, which is the healthy direction.
27→2 sys.unix.selector.poll uses interest✕
- Connections
- 3 pairs of types, where a type in sys.unix.selector.poll uses a type in interest.
- The types involved
mio.sys.unix.selector.poll.Selector→mio.interest.Interestmio.sys.unix.selector.poll.SelectorState→mio.interest.Interestmio.sys.unix.selector.poll.poll$module→mio.interest.Interest
- Direction
- sys.unix.selector.poll uses interest, so a change to interest can break sys.unix.selector.poll, while a change to sys.unix.selector.poll can't break interest.
- Position
- Below the diagonal: sys.unix.selector.poll uses a module listed above it, which is the healthy direction.
27→4 sys.unix.selector.poll uses token✕
- Connections
- 5 pairs of types, where a type in sys.unix.selector.poll uses a type in token.
- The types involved
mio.sys.unix.selector.poll.Event→mio.token.Tokenmio.sys.unix.selector.poll.FdData→mio.token.Tokenmio.sys.unix.selector.poll.Selector→mio.token.Tokenmio.sys.unix.selector.poll.SelectorState→mio.token.Tokenmio.sys.unix.selector.poll.Waker→mio.token.Token
- Direction
- sys.unix.selector.poll uses token, so a change to token can break sys.unix.selector.poll, while a change to sys.unix.selector.poll can't break token.
- Position
- Below the diagonal: sys.unix.selector.poll uses a module listed above it, which is the healthy direction.
27→6 sys.unix.selector.poll uses sys.shell.selector✕
- Connections
- 1 pair of types, where a type in sys.unix.selector.poll uses a type in sys.shell.selector.
- The types involved
mio.sys.unix.selector.poll.Waker→mio.sys.shell.selector.Selector
- Direction
- sys.unix.selector.poll uses sys.shell.selector, so a change to sys.shell.selector can break sys.unix.selector.poll, while a change to sys.unix.selector.poll can't break sys.shell.selector.
- Position
- Below the diagonal: sys.unix.selector.poll uses a module listed above it, which is the healthy direction.
27→13 sys.unix.selector.poll uses sys.unix.selector.event_ports✕
- Connections
- 1 pair of types, where a type in sys.unix.selector.poll uses a type in sys.unix.selector.event_ports.
- The types involved
mio.sys.unix.selector.poll.Selector→mio.sys.unix.selector.event_ports.SelectorState
- Direction
- sys.unix.selector.poll uses sys.unix.selector.event_ports, so a change to sys.unix.selector.event_ports can break sys.unix.selector.poll, while a change to sys.unix.selector.poll can't break sys.unix.selector.event_ports.
- Position
- Below the diagonal: sys.unix.selector.poll uses a module listed above it, which is the healthy direction.
28→2 sys.unix.selector.stateless_io_source uses interest✕
- Connections
- 1 pair of types, where a type in sys.unix.selector.stateless_io_source uses a type in interest.
- The types involved
mio.sys.unix.selector.stateless_io_source.IoSourceState→mio.interest.Interest
- Direction
- sys.unix.selector.stateless_io_source uses interest, so a change to interest can break sys.unix.selector.stateless_io_source, while a change to sys.unix.selector.stateless_io_source can't break interest.
- Position
- Below the diagonal: sys.unix.selector.stateless_io_source uses a module listed above it, which is the healthy direction.
28→4 sys.unix.selector.stateless_io_source uses token✕
- Connections
- 1 pair of types, where a type in sys.unix.selector.stateless_io_source uses a type in token.
- The types involved
mio.sys.unix.selector.stateless_io_source.IoSourceState→mio.token.Token
- Direction
- sys.unix.selector.stateless_io_source uses token, so a change to token can break sys.unix.selector.stateless_io_source, while a change to sys.unix.selector.stateless_io_source can't break token.
- Position
- Below the diagonal: sys.unix.selector.stateless_io_source uses a module listed above it, which is the healthy direction.
28→9 sys.unix.selector.stateless_io_source uses poll✕
- Connections
- 1 pair of types, where a type in sys.unix.selector.stateless_io_source uses a type in poll.
- The types involved
mio.sys.unix.selector.stateless_io_source.IoSourceState→mio.poll.Registry
- Direction
- sys.unix.selector.stateless_io_source uses poll, so a change to poll can break sys.unix.selector.stateless_io_source, while a change to sys.unix.selector.stateless_io_source can't break poll.
- Position
- Below the diagonal: sys.unix.selector.stateless_io_source uses a module listed above it, which is the healthy direction.
29→4 waker uses token✕
- Connections
- 1 pair of types, where a type in waker uses a type in token.
- The types involved
mio.waker.Waker→mio.token.Token
- Direction
- waker uses token, so a change to token can break waker, while a change to waker can't break token.
- Position
- Below the diagonal: waker uses a module listed above it, which is the healthy direction.
29→9 waker uses poll✕
- Connections
- 1 pair of types, where a type in waker uses a type in poll.
- The types involved
mio.waker.Waker→mio.poll.Registry
- Direction
- waker uses poll, so a change to poll can break waker, while a change to waker can't break poll.
- Position
- Below the diagonal: waker uses a module listed above it, which is the healthy direction.
29→11 waker uses sys.shell.waker✕
- Connections
- 1 pair of types, where a type in waker uses a type in sys.shell.waker.
- The types involved
mio.waker.Waker→mio.sys.shell.waker.Waker
- Direction
- waker uses sys.shell.waker, so a change to sys.shell.waker can break waker, while a change to waker can't break sys.shell.waker.
- Position
- Below the diagonal: waker uses a module listed above it, which is the healthy direction.
30→2 io_source uses interest✕
- Connections
- 1 pair of types, where a type in io_source uses a type in interest.
- The types involved
mio.io_source.IoSource→mio.interest.Interest
- Direction
- io_source uses interest, so a change to interest can break io_source, while a change to io_source can't break interest.
- Position
- Below the diagonal: io_source uses a module listed above it, which is the healthy direction.
30→4 io_source uses token✕
- Connections
- 1 pair of types, where a type in io_source uses a type in token.
- The types involved
mio.io_source.IoSource→mio.token.Token
- Direction
- io_source uses token, so a change to token can break io_source, while a change to io_source can't break token.
- Position
- Below the diagonal: io_source uses a module listed above it, which is the healthy direction.
30→9 io_source uses poll✕
- Connections
- 2 pairs of types, where a type in io_source uses a type in poll.
- The types involved
mio.io_source.IoSource→mio.poll.Registrymio.io_source.SelectorId→mio.poll.Registry
- Direction
- io_source uses poll, so a change to poll can break io_source, while a change to io_source can't break poll.
- Position
- Below the diagonal: io_source uses a module listed above it, which is the healthy direction.
30→26 io_source uses event.source✕
- Connections
- 1 pair of types, where a type in io_source uses a type in event.source.
- The types involved
mio.io_source.IoSource→mio.event.source.Source
- Direction
- io_source uses event.source, so a change to event.source can break io_source, while a change to io_source can't break event.source.
- Position
- Below the diagonal: io_source uses a module listed above it, which is the healthy direction.
30→28 io_source uses sys.unix.selector.stateless_io_source✕
- Connections
- 1 pair of types, where a type in io_source uses a type in sys.unix.selector.stateless_io_source.
- The types involved
mio.io_source.IoSource→mio.sys.unix.selector.stateless_io_source.IoSourceState
- Direction
- io_source uses sys.unix.selector.stateless_io_source, so a change to sys.unix.selector.stateless_io_source can break io_source, while a change to io_source can't break sys.unix.selector.stateless_io_source.
- Position
- Below the diagonal: io_source uses a module listed above it, which is the healthy direction.
31→2 sys.unix.sourcefd uses interest✕
- Connections
- 1 pair of types, where a type in sys.unix.sourcefd uses a type in interest.
- The types involved
mio.sys.unix.sourcefd.SourceFd→mio.interest.Interest
- Direction
- sys.unix.sourcefd uses interest, so a change to interest can break sys.unix.sourcefd, while a change to sys.unix.sourcefd can't break interest.
- Position
- Below the diagonal: sys.unix.sourcefd uses a module listed above it, which is the healthy direction.
31→4 sys.unix.sourcefd uses token✕
- Connections
- 1 pair of types, where a type in sys.unix.sourcefd uses a type in token.
- The types involved
mio.sys.unix.sourcefd.SourceFd→mio.token.Token
- Direction
- sys.unix.sourcefd uses token, so a change to token can break sys.unix.sourcefd, while a change to sys.unix.sourcefd can't break token.
- Position
- Below the diagonal: sys.unix.sourcefd uses a module listed above it, which is the healthy direction.
31→9 sys.unix.sourcefd uses poll✕
- Connections
- 1 pair of types, where a type in sys.unix.sourcefd uses a type in poll.
- The types involved
mio.sys.unix.sourcefd.SourceFd→mio.poll.Registry
- Direction
- sys.unix.sourcefd uses poll, so a change to poll can break sys.unix.sourcefd, while a change to sys.unix.sourcefd can't break poll.
- Position
- Below the diagonal: sys.unix.sourcefd uses a module listed above it, which is the healthy direction.
31→26 sys.unix.sourcefd uses event.source✕
- Connections
- 1 pair of types, where a type in sys.unix.sourcefd uses a type in event.source.
- The types involved
mio.sys.unix.sourcefd.SourceFd→mio.event.source.Source
- Direction
- sys.unix.sourcefd uses event.source, so a change to event.source can break sys.unix.sourcefd, while a change to sys.unix.sourcefd can't break event.source.
- Position
- Below the diagonal: sys.unix.sourcefd uses a module listed above it, which is the healthy direction.
32→2 sys.windows.named_pipe uses interest✕
- Connections
- 1 pair of types, where a type in sys.windows.named_pipe uses a type in interest.
- The types involved
mio.sys.windows.named_pipe.NamedPipe→mio.interest.Interest
- Direction
- sys.windows.named_pipe uses interest, so a change to interest can break sys.windows.named_pipe, while a change to sys.windows.named_pipe can't break interest.
- Position
- Below the diagonal: sys.windows.named_pipe uses a module listed above it, which is the healthy direction.
32→3 sys.windows.named_pipe uses sys.windows.handle✕
- Connections
- 1 pair of types, where a type in sys.windows.named_pipe uses a type in sys.windows.handle.
- The types involved
mio.sys.windows.named_pipe.Inner→mio.sys.windows.handle.Handle
- Direction
- sys.windows.named_pipe uses sys.windows.handle, so a change to sys.windows.handle can break sys.windows.named_pipe, while a change to sys.windows.named_pipe can't break sys.windows.handle.
- Position
- Below the diagonal: sys.windows.named_pipe uses a module listed above it, which is the healthy direction.
32→4 sys.windows.named_pipe uses token✕
- Connections
- 2 pairs of types, where a type in sys.windows.named_pipe uses a type in token.
- The types involved
mio.sys.windows.named_pipe.Io→mio.token.Tokenmio.sys.windows.named_pipe.NamedPipe→mio.token.Token
- Direction
- sys.windows.named_pipe uses token, so a change to token can break sys.windows.named_pipe, while a change to sys.windows.named_pipe can't break token.
- Position
- Below the diagonal: sys.windows.named_pipe uses a module listed above it, which is the healthy direction.
32→5 sys.windows.named_pipe uses event.event✕
- Connections
- 3 pairs of types, where a type in sys.windows.named_pipe uses a type in event.event.
- The types involved
mio.sys.windows.named_pipe.Inner→mio.event.event.Eventmio.sys.windows.named_pipe.Io→mio.event.event.Eventmio.sys.windows.named_pipe.named_pipe$module→mio.event.event.Event
- Direction
- sys.windows.named_pipe uses event.event, so a change to event.event can break sys.windows.named_pipe, while a change to sys.windows.named_pipe can't break event.event.
- Position
- Below the diagonal: sys.windows.named_pipe uses a module listed above it, which is the healthy direction.
32→8 sys.windows.named_pipe uses sys.windows.iocp✕
- Connections
- 1 pair of types, where a type in sys.windows.named_pipe uses a type in sys.windows.iocp.
- The types involved
mio.sys.windows.named_pipe.Io→mio.sys.windows.iocp.CompletionPort
- Direction
- sys.windows.named_pipe uses sys.windows.iocp, so a change to sys.windows.iocp can break sys.windows.named_pipe, while a change to sys.windows.named_pipe can't break sys.windows.iocp.
- Position
- Below the diagonal: sys.windows.named_pipe uses a module listed above it, which is the healthy direction.
32→9 sys.windows.named_pipe uses poll✕
- Connections
- 2 pairs of types, where a type in sys.windows.named_pipe uses a type in poll.
- The types involved
mio.sys.windows.named_pipe.Io→mio.poll.Registrymio.sys.windows.named_pipe.NamedPipe→mio.poll.Registry
- Direction
- sys.windows.named_pipe uses poll, so a change to poll can break sys.windows.named_pipe, while a change to sys.windows.named_pipe can't break poll.
- Position
- Below the diagonal: sys.windows.named_pipe uses a module listed above it, which is the healthy direction.
32→26 sys.windows.named_pipe uses event.source✕
- Connections
- 1 pair of types, where a type in sys.windows.named_pipe uses a type in event.source.
- The types involved
mio.sys.windows.named_pipe.NamedPipe→mio.event.source.Source
- Direction
- sys.windows.named_pipe uses event.source, so a change to event.source can break sys.windows.named_pipe, while a change to sys.windows.named_pipe can't break event.source.
- Position
- Below the diagonal: sys.windows.named_pipe uses a module listed above it, which is the healthy direction.
33→2 net.tcp.listener uses interest✕
- Connections
- 1 pair of types, where a type in net.tcp.listener uses a type in interest.
- The types involved
mio.net.tcp.listener.TcpListener→mio.interest.Interest
- Direction
- net.tcp.listener uses interest, so a change to interest can break net.tcp.listener, while a change to net.tcp.listener can't break interest.
- Position
- Below the diagonal: net.tcp.listener uses a module listed above it, which is the healthy direction.
33→4 net.tcp.listener uses token✕
- Connections
- 1 pair of types, where a type in net.tcp.listener uses a type in token.
- The types involved
mio.net.tcp.listener.TcpListener→mio.token.Token
- Direction
- net.tcp.listener uses token, so a change to token can break net.tcp.listener, while a change to net.tcp.listener can't break token.
- Position
- Below the diagonal: net.tcp.listener uses a module listed above it, which is the healthy direction.
33→9 net.tcp.listener uses poll✕
- Connections
- 1 pair of types, where a type in net.tcp.listener uses a type in poll.
- The types involved
mio.net.tcp.listener.TcpListener→mio.poll.Registry
- Direction
- net.tcp.listener uses poll, so a change to poll can break net.tcp.listener, while a change to net.tcp.listener can't break poll.
- Position
- Below the diagonal: net.tcp.listener uses a module listed above it, which is the healthy direction.
33→26 net.tcp.listener uses event.source✕
- Connections
- 1 pair of types, where a type in net.tcp.listener uses a type in event.source.
- The types involved
mio.net.tcp.listener.TcpListener→mio.event.source.Source
- Direction
- net.tcp.listener uses event.source, so a change to event.source can break net.tcp.listener, while a change to net.tcp.listener can't break event.source.
- Position
- Below the diagonal: net.tcp.listener uses a module listed above it, which is the healthy direction.
33→30 net.tcp.listener uses io_source✕
- Connections
- 1 pair of types, where a type in net.tcp.listener uses a type in io_source.
- The types involved
mio.net.tcp.listener.TcpListener→mio.io_source.IoSource
- Direction
- net.tcp.listener uses io_source, so a change to io_source can break net.tcp.listener, while a change to net.tcp.listener can't break io_source.
- Position
- Below the diagonal: net.tcp.listener uses a module listed above it, which is the healthy direction.
34→2 net.tcp.stream uses interest✕
- Connections
- 1 pair of types, where a type in net.tcp.stream uses a type in interest.
- The types involved
mio.net.tcp.stream.TcpStream→mio.interest.Interest
- Direction
- net.tcp.stream uses interest, so a change to interest can break net.tcp.stream, while a change to net.tcp.stream can't break interest.
- Position
- Below the diagonal: net.tcp.stream uses a module listed above it, which is the healthy direction.
34→4 net.tcp.stream uses token✕
- Connections
- 1 pair of types, where a type in net.tcp.stream uses a type in token.
- The types involved
mio.net.tcp.stream.TcpStream→mio.token.Token
- Direction
- net.tcp.stream uses token, so a change to token can break net.tcp.stream, while a change to net.tcp.stream can't break token.
- Position
- Below the diagonal: net.tcp.stream uses a module listed above it, which is the healthy direction.
34→9 net.tcp.stream uses poll✕
- Connections
- 1 pair of types, where a type in net.tcp.stream uses a type in poll.
- The types involved
mio.net.tcp.stream.TcpStream→mio.poll.Registry
- Direction
- net.tcp.stream uses poll, so a change to poll can break net.tcp.stream, while a change to net.tcp.stream can't break poll.
- Position
- Below the diagonal: net.tcp.stream uses a module listed above it, which is the healthy direction.
34→26 net.tcp.stream uses event.source✕
- Connections
- 1 pair of types, where a type in net.tcp.stream uses a type in event.source.
- The types involved
mio.net.tcp.stream.TcpStream→mio.event.source.Source
- Direction
- net.tcp.stream uses event.source, so a change to event.source can break net.tcp.stream, while a change to net.tcp.stream can't break event.source.
- Position
- Below the diagonal: net.tcp.stream uses a module listed above it, which is the healthy direction.
34→30 net.tcp.stream uses io_source✕
- Connections
- 1 pair of types, where a type in net.tcp.stream uses a type in io_source.
- The types involved
mio.net.tcp.stream.TcpStream→mio.io_source.IoSource
- Direction
- net.tcp.stream uses io_source, so a change to io_source can break net.tcp.stream, while a change to net.tcp.stream can't break io_source.
- Position
- Below the diagonal: net.tcp.stream uses a module listed above it, which is the healthy direction.
35→2 net.udp uses interest✕
- Connections
- 1 pair of types, where a type in net.udp uses a type in interest.
- The types involved
mio.net.udp.UdpSocket→mio.interest.Interest
- Direction
- net.udp uses interest, so a change to interest can break net.udp, while a change to net.udp can't break interest.
- Position
- Below the diagonal: net.udp uses a module listed above it, which is the healthy direction.
35→4 net.udp uses token✕
- Connections
- 1 pair of types, where a type in net.udp uses a type in token.
- The types involved
mio.net.udp.UdpSocket→mio.token.Token
- Direction
- net.udp uses token, so a change to token can break net.udp, while a change to net.udp can't break token.
- Position
- Below the diagonal: net.udp uses a module listed above it, which is the healthy direction.
35→9 net.udp uses poll✕
- Connections
- 1 pair of types, where a type in net.udp uses a type in poll.
- The types involved
mio.net.udp.UdpSocket→mio.poll.Registry
- Direction
- net.udp uses poll, so a change to poll can break net.udp, while a change to net.udp can't break poll.
- Position
- Below the diagonal: net.udp uses a module listed above it, which is the healthy direction.
35→26 net.udp uses event.source✕
- Connections
- 1 pair of types, where a type in net.udp uses a type in event.source.
- The types involved
mio.net.udp.UdpSocket→mio.event.source.Source
- Direction
- net.udp uses event.source, so a change to event.source can break net.udp, while a change to net.udp can't break event.source.
- Position
- Below the diagonal: net.udp uses a module listed above it, which is the healthy direction.
35→30 net.udp uses io_source✕
- Connections
- 1 pair of types, where a type in net.udp uses a type in io_source.
- The types involved
mio.net.udp.UdpSocket→mio.io_source.IoSource
- Direction
- net.udp uses io_source, so a change to io_source can break net.udp, while a change to net.udp can't break io_source.
- Position
- Below the diagonal: net.udp uses a module listed above it, which is the healthy direction.
36→2 net.uds.datagram uses interest✕
- Connections
- 1 pair of types, where a type in net.uds.datagram uses a type in interest.
- The types involved
mio.net.uds.datagram.UnixDatagram→mio.interest.Interest
- Direction
- net.uds.datagram uses interest, so a change to interest can break net.uds.datagram, while a change to net.uds.datagram can't break interest.
- Position
- Below the diagonal: net.uds.datagram uses a module listed above it, which is the healthy direction.
36→4 net.uds.datagram uses token✕
- Connections
- 1 pair of types, where a type in net.uds.datagram uses a type in token.
- The types involved
mio.net.uds.datagram.UnixDatagram→mio.token.Token
- Direction
- net.uds.datagram uses token, so a change to token can break net.uds.datagram, while a change to net.uds.datagram can't break token.
- Position
- Below the diagonal: net.uds.datagram uses a module listed above it, which is the healthy direction.
36→9 net.uds.datagram uses poll✕
- Connections
- 1 pair of types, where a type in net.uds.datagram uses a type in poll.
- The types involved
mio.net.uds.datagram.UnixDatagram→mio.poll.Registry
- Direction
- net.uds.datagram uses poll, so a change to poll can break net.uds.datagram, while a change to net.uds.datagram can't break poll.
- Position
- Below the diagonal: net.uds.datagram uses a module listed above it, which is the healthy direction.
36→26 net.uds.datagram uses event.source✕
- Connections
- 1 pair of types, where a type in net.uds.datagram uses a type in event.source.
- The types involved
mio.net.uds.datagram.UnixDatagram→mio.event.source.Source
- Direction
- net.uds.datagram uses event.source, so a change to event.source can break net.uds.datagram, while a change to net.uds.datagram can't break event.source.
- Position
- Below the diagonal: net.uds.datagram uses a module listed above it, which is the healthy direction.
36→30 net.uds.datagram uses io_source✕
- Connections
- 1 pair of types, where a type in net.uds.datagram uses a type in io_source.
- The types involved
mio.net.uds.datagram.UnixDatagram→mio.io_source.IoSource
- Direction
- net.uds.datagram uses io_source, so a change to io_source can break net.uds.datagram, while a change to net.uds.datagram can't break io_source.
- Position
- Below the diagonal: net.uds.datagram uses a module listed above it, which is the healthy direction.
37→2 net.uds.listener uses interest✕
- Connections
- 1 pair of types, where a type in net.uds.listener uses a type in interest.
- The types involved
mio.net.uds.listener.UnixListener→mio.interest.Interest
- Direction
- net.uds.listener uses interest, so a change to interest can break net.uds.listener, while a change to net.uds.listener can't break interest.
- Position
- Below the diagonal: net.uds.listener uses a module listed above it, which is the healthy direction.
37→4 net.uds.listener uses token✕
- Connections
- 1 pair of types, where a type in net.uds.listener uses a type in token.
- The types involved
mio.net.uds.listener.UnixListener→mio.token.Token
- Direction
- net.uds.listener uses token, so a change to token can break net.uds.listener, while a change to net.uds.listener can't break token.
- Position
- Below the diagonal: net.uds.listener uses a module listed above it, which is the healthy direction.
37→9 net.uds.listener uses poll✕
- Connections
- 1 pair of types, where a type in net.uds.listener uses a type in poll.
- The types involved
mio.net.uds.listener.UnixListener→mio.poll.Registry
- Direction
- net.uds.listener uses poll, so a change to poll can break net.uds.listener, while a change to net.uds.listener can't break poll.
- Position
- Below the diagonal: net.uds.listener uses a module listed above it, which is the healthy direction.
37→26 net.uds.listener uses event.source✕
- Connections
- 1 pair of types, where a type in net.uds.listener uses a type in event.source.
- The types involved
mio.net.uds.listener.UnixListener→mio.event.source.Source
- Direction
- net.uds.listener uses event.source, so a change to event.source can break net.uds.listener, while a change to net.uds.listener can't break event.source.
- Position
- Below the diagonal: net.uds.listener uses a module listed above it, which is the healthy direction.
37→30 net.uds.listener uses io_source✕
- Connections
- 1 pair of types, where a type in net.uds.listener uses a type in io_source.
- The types involved
mio.net.uds.listener.UnixListener→mio.io_source.IoSource
- Direction
- net.uds.listener uses io_source, so a change to io_source can break net.uds.listener, while a change to net.uds.listener can't break io_source.
- Position
- Below the diagonal: net.uds.listener uses a module listed above it, which is the healthy direction.
38→2 net.uds.stream uses interest✕
- Connections
- 1 pair of types, where a type in net.uds.stream uses a type in interest.
- The types involved
mio.net.uds.stream.UnixStream→mio.interest.Interest
- Direction
- net.uds.stream uses interest, so a change to interest can break net.uds.stream, while a change to net.uds.stream can't break interest.
- Position
- Below the diagonal: net.uds.stream uses a module listed above it, which is the healthy direction.
38→4 net.uds.stream uses token✕
- Connections
- 1 pair of types, where a type in net.uds.stream uses a type in token.
- The types involved
mio.net.uds.stream.UnixStream→mio.token.Token
- Direction
- net.uds.stream uses token, so a change to token can break net.uds.stream, while a change to net.uds.stream can't break token.
- Position
- Below the diagonal: net.uds.stream uses a module listed above it, which is the healthy direction.
38→9 net.uds.stream uses poll✕
- Connections
- 1 pair of types, where a type in net.uds.stream uses a type in poll.
- The types involved
mio.net.uds.stream.UnixStream→mio.poll.Registry
- Direction
- net.uds.stream uses poll, so a change to poll can break net.uds.stream, while a change to net.uds.stream can't break poll.
- Position
- Below the diagonal: net.uds.stream uses a module listed above it, which is the healthy direction.
38→26 net.uds.stream uses event.source✕
- Connections
- 1 pair of types, where a type in net.uds.stream uses a type in event.source.
- The types involved
mio.net.uds.stream.UnixStream→mio.event.source.Source
- Direction
- net.uds.stream uses event.source, so a change to event.source can break net.uds.stream, while a change to net.uds.stream can't break event.source.
- Position
- Below the diagonal: net.uds.stream uses a module listed above it, which is the healthy direction.
38→30 net.uds.stream uses io_source✕
- Connections
- 1 pair of types, where a type in net.uds.stream uses a type in io_source.
- The types involved
mio.net.uds.stream.UnixStream→mio.io_source.IoSource
- Direction
- net.uds.stream uses io_source, so a change to io_source can break net.uds.stream, while a change to net.uds.stream can't break io_source.
- Position
- Below the diagonal: net.uds.stream uses a module listed above it, which is the healthy direction.
39→33 sys.shell.tcp uses net.tcp.listener✕
- Connections
- 1 pair of types, where a type in sys.shell.tcp uses a type in net.tcp.listener.
- The types involved
mio.sys.shell.tcp.tcp$module→mio.net.tcp.listener.TcpListener
- Direction
- sys.shell.tcp uses net.tcp.listener, so a change to net.tcp.listener can break sys.shell.tcp, while a change to sys.shell.tcp can't break net.tcp.listener.
- Position
- Below the diagonal: sys.shell.tcp uses a module listed above it, which is the healthy direction.
39→34 sys.shell.tcp uses net.tcp.stream✕
- Connections
- 1 pair of types, where a type in sys.shell.tcp uses a type in net.tcp.stream.
- The types involved
mio.sys.shell.tcp.tcp$module→mio.net.tcp.stream.TcpStream
- Direction
- sys.shell.tcp uses net.tcp.stream, so a change to net.tcp.stream can break sys.shell.tcp, while a change to sys.shell.tcp can't break net.tcp.stream.
- Position
- Below the diagonal: sys.shell.tcp uses a module listed above it, which is the healthy direction.
40→33 sys.unix.tcp uses net.tcp.listener✕
- Connections
- 1 pair of types, where a type in sys.unix.tcp uses a type in net.tcp.listener.
- The types involved
mio.sys.unix.tcp.tcp$module→mio.net.tcp.listener.TcpListener
- Direction
- sys.unix.tcp uses net.tcp.listener, so a change to net.tcp.listener can break sys.unix.tcp, while a change to sys.unix.tcp can't break net.tcp.listener.
- Position
- Below the diagonal: sys.unix.tcp uses a module listed above it, which is the healthy direction.
40→34 sys.unix.tcp uses net.tcp.stream✕
- Connections
- 1 pair of types, where a type in sys.unix.tcp uses a type in net.tcp.stream.
- The types involved
mio.sys.unix.tcp.tcp$module→mio.net.tcp.stream.TcpStream
- Direction
- sys.unix.tcp uses net.tcp.stream, so a change to net.tcp.stream can break sys.unix.tcp, while a change to sys.unix.tcp can't break net.tcp.stream.
- Position
- Below the diagonal: sys.unix.tcp 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 | 42 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 5 | Medium |
| A07:2025 — Authentication Failures | 3 | Medium |
Roadmap
Top priorities: 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; Resolve the 8 Low coverage finding(s) in Code Coverage — start with waker.rs (2), event.rs, events.rs; 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.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +10.6 pts | Medium | Architecture documentation |
| Resolve the 8 Low coverage finding(s) in Code Coverage — start with waker.rs (2), event.rs, events.rs. | +4.6 pts | Low | Code Coverage |
| Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite. | +4.1 pts | Medium | Documentation (README) |
| Resolve the 3 Orphaned file finding(s) in Knowledge Freshness — start with mod.rs, token.rs, selector.rs. | +0.9 pts | Low | Knowledge Freshness |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +0.7 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +0.7 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +0.7 pts | Low | Supply-chain Provenance & Signing |
| Add a health-check endpoint (a /health route on your axum/actix router) so orchestrators and load balancers can probe liveness/readiness. | +1.3 pts | Medium | Observability |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| tests/tcp_stream.rs | 5.3 | Mixed | Test Reliability: Test declared unreliable: shutdown_write |
| src/sys/windows/selector.rs | 6.7 | Mixed | Explicit Debt: FixmeComment |
| src/io_source.rs | 6.7 | Mixed | Explicit Debt: TodoComment repeated across 12 files |
| src/sys/shell/selector.rs | 7.0 | Mixed | Code Duplication: Duplicated block (27 lines × 2) |
| src/sys/unix/selector/event_ports.rs | 7.0 | Mixed | Cyclomatic Complexity: SelectorState::process_events (cyclomatic 17) |
| src/sys/unix/selector/kqueue.rs | 7.2 | Mixed | God Classes: FunctionTooLong: mio::sys::unix::selector::kqueue::event::debug_details |
| src/sys/windows/named_pipe.rs | 7.2 | Mixed | God Classes: FileTooLong: windows/named_pipe.rs |
| src/sys/unix/selector/poll.rs | 7.8 | Mixed | Cyclomatic Complexity: SelectorState::select (cyclomatic 17) |
| src/net/tcp/stream.rs | 8.0 | Near-clean | Change Coupling: Boundary-crossing change coupling: stream.rs ↔ sourcefd.rs |
| tests/udp_socket.rs | 8.2 | Near-clean | Explicit Debt: TodoComment |
| tests/util/mod.rs | 8.2 | Near-clean | Explicit Debt: TodoComment |
| src/sys/wasip1/mod.rs | 8.2 | Near-clean | Explicit Debt: TodoComment |
| src/sys/unix/waker/eventfd.rs | 8.5 | Near-clean | Code Duplication: Edited copy of a member (10 corresponding lines) |
| src/sys/unix/tcp.rs | 8.5 | Near-clean | Code Duplication: Edited copy of a member (5 corresponding lines) |
| src/sys/unix/selector/epoll.rs | 8.5 | Near-clean | Code Duplication: Edited copy of a member (8 corresponding lines) |
| src/sys/unix/net.rs | 8.5 | Near-clean | Code Duplication: Duplicated block (15 lines × 2) |
| src/sys/unix/uds/listener.rs | 8.5 | Near-clean | Code Duplication: Duplicated block (14–15 lines × 2) |
| src/net/tcp/listener.rs | 8.5 | Near-clean | Code Duplication: Duplicated block (15 lines × 2) |
| src/event/event.rs | 8.5 | Near-clean | Code Coverage: Low coverage: src/event/event.rs |
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 32 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 32 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, 95 of 105 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 | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D11 Test Reliability — 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 repository declares 1 of its own test(s) unreliable. The built-in reliability runner does not support this repository's ecosystem (.rs), so the suite was not re-run and no reliability score is given — these are the repository's own declarations, not our measurement.
- D12 Dependency Hygiene — 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. Not scored — 4 direct Cargo declaration(s) were read, but the outdated signal needs crates.io, and no committed Cargo.lock resolves them to versions, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
- 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.
- D21 Naming 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. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- 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. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D26 Project Cohesion — 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. `(repository root)` (12194 LoC, 75 module-visible types across 11 directories) is over its size bounds, and whether one unit is a coherent whole or a grab-bag is read from its type references: the parts of it that reach the rest only through its shared core. Those are read over the C#/VB code model, which this unit's source did not supply. Its size alone is no verdict on its cohesion, so none is published.
- 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.
- 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 no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — 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 no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- X12 Unreachable branch — not measured this run — 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.
- X13 Undrained process stream — 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.
- X16 Unfloored truncation loop — 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, PHP, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X17 Uncapped recursion over a caller-supplied document — not measured this run — 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.
- X18 Disposal-pattern correctness — 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, Kotlin, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X19 Unrestored process-global state — not measured this run — 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, Kotlin, Python, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X22 Contradicted release guard — not measured this run — 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 Java, TypeScript/JavaScript, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X23 Unguarded diagnostic materialisation — not measured this run — 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, F#, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X24 Document value interpolated into markup unescaped — not measured this run — 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.
- X25 Inert configuration knob — 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, Kotlin, Scala, PHP, Erlang, Python, Dart and Ruby source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart or Ruby was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X3 Exception handling — not measured this run — 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.
- X5 Nullable reference types — 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 MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, and Kotlin source only, and no C# was loaded, no TypeScript was found, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
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.
- 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.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- 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 SelectorState::process_events at 17.
What to do
- Bring the 2 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with SelectorState::process_events (cyclomatic 17), SelectorState::select (cyclomatic 17). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cyclomatic Complexity from 9.7 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
5 function(s) exceeded the cognitive complexity threshold of 15; the worst was SelectorState::select at 48.
What to do
- Bring the 5 bodies over 15 down to 15 or less in Cognitive Complexity — start with SelectorState::select (cognitive 48), SelectorState::process_events (cognitive 37), SelectorState::select (cognitive 26). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 5 together lifts Cognitive Complexity from 8.4 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
5 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 2 FileTooLong finding(s) in God Classes — start with kqueue.rs, named_pipe.rs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 FunctionTooLong finding(s) in God Classes — start with kqueue.rs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 ClassTooLong finding(s) in God Classes — start with kqueue.rs. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
7 duplicated block group(s) detected. 3.0 % of the production lines (366 of 12,194) are in a reported copy. A further 8 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 2 Edited copy of a member (13 corresponding lines) finding(s) in Code Duplication — start with io_source.rs, event_ports.rs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Duplicated block (15 lines × 2) finding(s) in Code Duplication — start with net.rs, listener.rs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Edited copy of a member (26 corresponding lines) finding(s) in Code Duplication — start with kqueue.rs. — One of this dimension's main actionable groups (1 warning-level).
D6 · Cohesion (LCOM4)
0 of 20 classes have LCOM4 above 3.
D8 · Code Coverage
Line coverage 26.8% — 8 file(s) below 50%. Measured from the Rust suite (repository root: `cargo test --workspace` instrumented over 9 production file(s), 18 test binaries and 5 doc-test binaries).
What to do
- Resolve the 8 Low coverage finding(s) in Code Coverage — start with waker.rs (2), event.rs, events.rs. — One of this dimension's main actionable groups (8 warning-level).
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 5 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository commits no Cargo.lock, so its graph was resolved here: its manifests' `[dependencies]` and `[build-dependencies]` closed over the crates.io index, each crate at the newest release its requirement admits (what a fresh `cargo generate-lockfile` picks, not a graph the repository has pinned). Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository. This repository publishes itself under MIT, which is its own choice and is not judged here.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D16 · Bus Factor
3 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is src/sys/unix/selector/event_ports.rs. Counted over 39 of the 61 production source files in this repository: 21 are under the ~2,400-byte size floor this dimension measures over, and the remaining 1 have no attributable history left to measure.
D17 · Explicit Debt
18 deducted task-comment markers across 12194 LoC (0.1/KLoC) → score 9.7. 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 4 TodoComment finding(s) in Explicit Debt — start with mod.rs (2), tcp_stream.rs, udp_socket.rs. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 2 FixmeComment finding(s) in Explicit Debt — start with tcp_stream.rs, selector.rs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 TodoComment repeated across 12 files finding(s) in Explicit Debt — start with io_source.rs. — One of this dimension's main actionable groups (1 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 1 document(s) read across 1 unit(s).
D28 · Secrets (history)
3 finding(s): 0 critical, 0 high, 0 medium, 0 low.
D29 · Static Analysis (SAST)
42 finding(s): 0 critical, 42 high, 0 medium, 0 low. 42 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 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- No action in Static Analysis (SAST) — all 42 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 (42 issue-level, 0 of them charged here).
D34 · Knowledge Freshness
3 of 40 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/sys/wasip1/mod.rs. Counted over 40 of the 61 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: datagram.rs↔stream.rs 90%; udp.rs↔datagram.rs 70%; stream.rs↔datagram.rs 60%
What to do
- Resolve the 1 Boundary-crossing change coupling finding(s) in Change Coupling — start with stream.rs. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 2 Change coupling finding(s) in Change Coupling — start with udp.rs, mod.rs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Change-coupling hub finding(s) in Change Coupling — start with datagram.rs. — One of this dimension's main actionable groups (1 warning-level).
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
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
What to do
- Add a health-check endpoint (a /health route on your axum/actix router) so orchestrators and load balancers can probe liveness/readiness.
P3 · Security & performance tooling
What to do
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene
X14 · Bypassable address classification
X21 · Side-effecting pattern guard
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 93% | Exemplary | Solid. |
| Architecture | 98% | Exemplary | Strongest area. |
| Maturity | 53% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 69% | Adequate | Acceptable, with room to improve. |
| Security | 75% | Adequate — gated by D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
Unscored — 1 check(s) recorded observations but carry no score
- D11 Test Reliability — 1 observation(s) recorded · This repository declares 1 of its own test(s) unreliable. The built-in reliability runner does not support this repository's ecosystem (.rs), so the suite was not re-run and no reliability score is given — these are the repository's own declarations, not our measurement.
Not evidenced — 2 control(s) we could not find positive evidence for
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 81 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
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no data at rest for these controls to protect.
- C2 Access Controls — No access-control surface detected in the analyzed source — this repository starts no server another machine can reach (no actix-web HttpServer, axum::serve, Rocket launch, warp::serve, poem or salvo Server, tonic Server::builder, hyper or tiny_http server outside examples and tests, none bound beyond loopback). Access control is therefore N/A here — a crate is authorized by the application that serves it, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~8167 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.
- D12 Dependency Hygiene — Not scored — 4 direct Cargo declaration(s) were read, but the outdated signal needs crates.io, and no committed Cargo.lock resolves them to versions, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — D21 withholds its sibling member alignment rows: 1 candidate(s) found and not reported.
- 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 — this repository's production source is .rs, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D26 Project Cohesion — D26 could not read how the parts of this repository's one build unit reference each other, so its cohesion was not measured. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.rs), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Cargo manifest — not scanned yet).
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Cargo manifest — not scanned yet).
- D5 Coupling — Not applicable — this Cargo build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (12 value object(s))
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- M4 Documentation accuracy — Not applicable: the 1 current-state document(s) make no claim of a kind M4 checks.
- 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 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 9 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: 61 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.
- 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 analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X13 Undrained process stream — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- 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 analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X17 Uncapped recursion over a caller-supplied document — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X18 Disposal-pattern correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X19 Unrestored process-global state — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X2 Cancellation propagation — no C# was loaded; this repository's Rust was read, and no request in it can be cancelled by a caller — a Rust request takes no token: a future is cancelled by dropping it, from outside the call (select!, a timeout, an aborted task), and reqwest, hyper and tonic take none
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X22 Contradicted release guard — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X23 Unguarded diagnostic materialisation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X24 Document value interpolated into markup unescaped — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X25 Inert configuration knob — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. Rust's compiler refuses the unsynchronised version: a collection shared between a callback's thread and the waiting body must be `Sync`, which a `Vec`, `VecDeque` or `HashMap` is only behind a `Mutex`/`RwLock`, so the race this check looks for cannot be written in safe Rust. Not a gap in the analyzer and not a finding about your code.
- 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.
- X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Rust was read, and it logs through none: the `log` crate's macros take one finished message (as log4net does in C#; its `kv` values are an opt-in its backends mostly drop), `println!`/`eprintln!` are not loggers, or it makes no log call outside its tests and examples at all. Calls through `tracing` (`tracing::info!`, or `info!` imported from it) would be judged.
- X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 44 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
- Test declared unreliable: shutdown_write tests/tcp_stream.rs:384
- Boundary-crossing change coupling: stream.rs ↔ sourcefd.rs src/net/tcp/stream.rs:1
Serious — 46 finding(s)
- Low coverage: src/event/event.rs src/event/event.rs:1
- Low coverage: src/event/events.rs src/event/events.rs:1
- Low coverage: src/event/source.rs src/event/source.rs:1
- Low coverage: src/poll.rs src/poll.rs:1
- Low coverage: src/sys/shell/selector.rs src/sys/shell/selector.rs:1
- Low coverage: src/sys/shell/waker.rs src/sys/shell/waker.rs:1
- Low coverage: src/token.rs src/token.rs:1
- Low coverage: src/waker.rs src/waker.rs:1
- TodoComment tests/tcp_stream.rs:31
- TodoComment tests/udp_socket.rs:1036
- TodoComment tests/util/mod.rs:370
- TodoComment src/sys/wasip1/mod.rs:251
- SelectorState::select (cognitive 48) src/sys/unix/selector/poll.rs:194
- SelectorState::process_events (cognitive 37) src/sys/unix/selector/event_ports.rs:224
- SelectorState::select (cognitive 26) src/sys/unix/selector/event_ports.rs:141
- SelectorState::poll_registered_fds (cognitive 21) src/sys/unix/selector/event_ports.rs:365
- SelectorState::process_events (cyclomatic 17) src/sys/unix/selector/event_ports.rs:224
- SelectorState::select (cyclomatic 17) src/sys/unix/selector/poll.rs:194
- FixmeComment tests/tcp_stream.rs:409
- FixmeComment src/sys/windows/selector.rs:582
- FileTooLong: selector/kqueue.rs src/sys/unix/selector/kqueue.rs
- FileTooLong: windows/named_pipe.rs src/sys/windows/named_pipe.rs
- Change coupling: udp.rs ↔ stream.rs src/net/udp.rs:1
- Change coupling: mod.rs ↔ mod.rs src/sys/shell/mod.rs:1
- Edited copy of a member (13 corresponding lines) src/io_source.rs:251
- Edited copy of a member (13 corresponding lines) src/sys/unix/selector/event_ports.rs:567
- Duplicated block (15 lines × 2) src/sys/unix/net.rs:123
- Duplicated block (15 lines × 2) src/net/tcp/listener.rs:295
- TodoComment repeated across 12 files src/io_source.rs:4
- SockState::update (cognitive 21) src/sys/windows/selector.rs:115
- FunctionTooLong: mio::sys::unix::selector::kqueue::event::debug_details src/sys/unix/selector/kqueue.rs:495
- ClassTooLong: Events src/sys/unix/selector/kqueue.rs:353
- MethodTooLong: SelectorState.process_events src/sys/unix/selector/event_ports.rs:224
- Change-coupling hub: datagram.rs → stream.rs, udp.rs, listener.rs, stream.rs src/net/uds/datagram.rs
- REDACTED
- Edited copy of a member (26 corresponding lines) src/sys/unix/selector/kqueue.rs:395
- Edited copy of a member (17 corresponding lines) src/sys/windows/named_pipe.rs:152
- Edited copy of a member (10 corresponding lines) src/sys/unix/waker/eventfd.rs:44
- Edited copy of a member (12 corresponding lines) src/sys/windows/named_pipe.rs:1111
- Edited copy of a member (5 corresponding lines) src/sys/unix/tcp.rs:21
- Edited copy of a member (8 corresponding lines) src/sys/unix/selector/epoll.rs:37
- Duplicated block (11–15 lines × 2) src/sys/unix/selector/event_ports.rs:299
- Duplicated block (14–15 lines × 2) src/sys/unix/uds/listener.rs:66
- Duplicated block (8 lines × 3) src/sys/unix/selector/event_ports.rs:289
- Duplicated block (5 lines × 2) src/sys/windows/named_pipe.rs:527
- Duplicated block (27 lines × 2) src/sys/shell/selector.rs:14
Minor — 15 finding(s)
- REDACTED
- REDACTED
- REDACTED
- Orphaned file src/sys/wasip1/mod.rs:1
- Orphaned file src/token.rs:1
- Orphaned file src/sys/shell/selector.rs:1
- Off-boarding risk: anonymized user #1
- Further sole-owners (lower concentration)
- Orphaned files with no living knowledge
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
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-77d01ea1647148f29689e519e39b554a/history.json --exit-code 0 --source . | 4 | 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-77d01ea1647148f29689e519e39b554a/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 . | 42 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Cargo manifest — not scanned yet). | 0 | — |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Cargo manifest — not scanned yet). | 0 | — |