Executive summary
Nukesor/pueue falls short of our standard for production, in part because it has pipeline tools referenced by a changeable name. It scores 65 out of 100 and is rated Adequate, and 44 of its 46 critical findings are security problems in the build pipeline and in its automatic dependency updates.
Security and Compliance, at 57, is the weakest lens and counts most in the score. The best first step is fixing the six pipeline jobs with more access than they need, worth about 4 points. Stopping the four pipeline steps that hand secrets to unpinned tools comes next, worth about 3 points. Raising Security and Compliance to 70 would lift the score to about 71.
Thirty-seven pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Five secrets can leak from the build pipeline, and one automatic update takes new releases before a bad one can be spotted. Pinning each tool to an exact version, limiting each secret to its own step and setting a waiting period for automatic updates would close these risks. The pipeline step that installs packages without pinning their versions needs the packages it installs pinned to exact versions. The part of the code nobody has worked on for a long time needs someone to learn and document it before anyone changes it.
The product code is 12,610 lines, about €20,000 to rebuild.
If Security and Compliance rose from 57 to 70, the lowest score rated Strong, the score would rise from 65 to about 71.
New since the last survey: 39 findings
- Code Duplication · Edited copy of a member (60 corresponding lines) pueue_lib/src/network/protocol.rs
- Code Duplication · Edited copy of a member (30 corresponding lines) pueue/src/daemon/network/message_handler/pause.rs
- Code Duplication · Edited copy of a member (26 corresponding lines) pueue/src/client/commands/state/query/filters.rs
- Code Duplication · Edited copies of one member (3 members, 30+ corresponding lines) pueue_lib/src/network/socket/unix.rs
- Code Duplication · Edited copy of a member (34 corresponding lines) pueue/src/process_helper/windows.rs
- Code Duplication · Edited copy of a member (35 corresponding lines) pueue_lib/src/network/client.rs
- Code Duplication · Edited copy of a member (20 corresponding lines) pueue/src/daemon/service.rs
- Code Duplication · Edited copy of a member (22 corresponding lines) pueue_lib/src/network/protocol.rs
- Code Duplication · Edited copy of a member (13 corresponding lines) pueue_lib/src/message/request.rs
- Code Duplication · Edited copy of a member (18 corresponding lines) pueue_lib/src/network/socket/mod.rs
- Code Duplication · Edited copy of a member (10 corresponding lines) pueue_lib/src/network/protocol.rs
- Code Duplication · Edited copy of a member (7 corresponding lines) pueue/src/daemon/internal_state/state.rs
- Code Duplication · Edited copies of one member (3 members, 12+ corresponding lines) pueue/src/client/commands/enqueue.rs
- Code Coverage · Low coverage: pueue/src/client/cli.rs pueue/src/client/cli.rs
- Code Coverage · Low coverage: pueue/src/client/commands/clean.rs pueue/src/client/commands/clean.rs
- Code Coverage · Low coverage: pueue/src/client/commands/kill.rs pueue/src/client/commands/kill.rs
- Code Coverage · Low coverage: pueue/src/client/commands/parallel.rs pueue/src/client/commands/parallel.rs
- Code Coverage · Low coverage: pueue/src/client/commands/pause.rs pueue/src/client/commands/pause.rs
- Code Coverage · Low coverage: pueue/src/client/commands/remove.rs pueue/src/client/commands/remove.rs
- Code Coverage · Low coverage: pueue/src/client/commands/reset.rs pueue/src/client/commands/reset.rs
- Code Coverage · Low coverage: pueue/src/client/commands/send.rs pueue/src/client/commands/send.rs
- Code Coverage · Low coverage: pueue/src/client/commands/shutdown.rs pueue/src/client/commands/shutdown.rs
- Code Coverage · Low coverage: pueue/src/client/commands/start.rs pueue/src/client/commands/start.rs
- Code Coverage · Low coverage: pueue/src/client/commands/stash.rs pueue/src/client/commands/stash.rs
- Code Coverage · Low coverage: pueue/src/client/commands/switch.rs pueue/src/client/commands/switch.rs
- Code Coverage · Low coverage: pueue/src/daemon/network/message_handler/enqueue.rs pueue/src/daemon/network/message_handler/enqueue.rs
- Code Coverage · Low coverage: pueue/src/daemon/network/message_handler/send.rs pueue/src/daemon/network/message_handler/send.rs
- Code Coverage · Low coverage: pueue/src/daemon/network/message_handler/stash.rs pueue/src/daemon/network/message_handler/stash.rs
- Code Coverage · Low coverage: pueue/src/daemon/network/tls.rs pueue/src/daemon/network/tls.rs
- Code Coverage · Low coverage: pueue/src/daemon/pid.rs pueue/src/daemon/pid.rs
- Code Coverage · Low coverage: pueue_lib/src/message/request.rs pueue_lib/src/message/request.rs
- Code Coverage · Low coverage: pueue_lib/src/network/client.rs pueue_lib/src/network/client.rs
- Code Coverage · Low coverage: pueue_lib/src/network/socket/mod.rs pueue_lib/src/network/socket/mod.rs
- Code Coverage · Low coverage: pueue_lib/src/network/socket/unix.rs pueue_lib/src/network/socket/unix.rs
- Code Coverage · Low coverage: pueue_lib/src/network_blocking/client.rs pueue_lib/src/network_blocking/client.rs
- Code Coverage · Low coverage: pueue_lib/src/network_blocking/socket/mod.rs pueue_lib/src/network_blocking/socket/mod.rs
- Code Coverage · Low coverage: pueue_lib/src/network_blocking/socket/unix.rs pueue_lib/src/network_blocking/socket/unix.rs
- Code Coverage · Low coverage: pueue_lib/src/tls.rs pueue_lib/src/tls.rs
- Knowledge Freshness · Orphaned knowledge pueue/src/daemon/service.rs
Fixed since the last survey: 2 findings
- Change Coupling · Change coupling: protocol.rs ↔ unix.rs pueue_lib/src/network/protocol.rs
- Documentation (README) · README may be stale
Rebuild cost: about €20,000 · Estimate
| Cost to rebuild | €6,600 to €33,000, for 110 to 351 hours of work, about 0.1 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 65. 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,610 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 pueue.client.cli | 2 pueue_lib.message.request | 3 pueue_lib.task | 4 pueue.client.commands.state.query | 5 pueue_lib.message.response | 6 pueue_lib.network.socket | 7 pueue_lib.state | 8 pueue_lib.network.client | 9 pueue_lib.settings | 10 pueue.client.style | 11 pueue.daemon.internal_state.state | 12 pueue.daemon.network.message_handler | 13 pueue.daemon.network.message_handler.add | 14 pueue.daemon.network.message_handler.clean | 15 pueue.daemon.network.message_handler.edit | 16 pueue.daemon.network.message_handler.enqueue | 17 pueue.daemon.network.message_handler.env | 18 pueue.daemon.network.message_handler.group | 19 pueue.daemon.network.message_handler.kill | 20 pueue.daemon.network.message_handler.log | 21 pueue.daemon.network.message_handler.pause | 22 pueue.daemon.network.message_handler.reset | 23 pueue.daemon.network.message_handler.restart | 24 pueue.daemon.network.message_handler.start | 25 pueue.daemon.network.message_handler.stash | 26 pueue.daemon.network.message_handler.switch | 27 pueue.process_helper | 28 pueue.client.commands | 29 pueue.client.commands.add | 30 pueue.client.commands.edit | 31 pueue.client.commands.env | 32 pueue.client.commands.follow | 33 pueue.client.commands.group | 34 pueue.client.commands.kill | 35 pueue.client.commands.log | 36 pueue.client.commands.remove | 37 pueue.client.commands.state.table_builder | 38 pueue.client.commands.wait | 39 pueue.daemon.process_handler | 40 pueue.client.commands.state |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 pueue.client.cli | ||||||||||||||||||||||||||||||||||||||||
| 2 pueue_lib.message.request | ||||||||||||||||||||||||||||||||||||||||
| 3 pueue_lib.task | ||||||||||||||||||||||||||||||||||||||||
| 4 pueue.client.commands.state.query | 1 | |||||||||||||||||||||||||||||||||||||||
| 5 pueue_lib.message.response | 1 | |||||||||||||||||||||||||||||||||||||||
| 6 pueue_lib.network.socket | 1 | |||||||||||||||||||||||||||||||||||||||
| 7 pueue_lib.state | 1 | |||||||||||||||||||||||||||||||||||||||
| 8 pueue_lib.network.client | 1 | |||||||||||||||||||||||||||||||||||||||
| 9 pueue_lib.settings | 2 | |||||||||||||||||||||||||||||||||||||||
| 10 pueue.client.style | 1 | |||||||||||||||||||||||||||||||||||||||
| 11 pueue.daemon.internal_state.state | 1 | 2 | 4 | 1 | ||||||||||||||||||||||||||||||||||||
| 12 pueue.daemon.network.message_handler | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 13 pueue.daemon.network.message_handler.add | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 14 pueue.daemon.network.message_handler.clean | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 15 pueue.daemon.network.message_handler.edit | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 16 pueue.daemon.network.message_handler.enqueue | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 17 pueue.daemon.network.message_handler.env | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 18 pueue.daemon.network.message_handler.group | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 19 pueue.daemon.network.message_handler.kill | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 20 pueue.daemon.network.message_handler.log | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 21 pueue.daemon.network.message_handler.pause | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 22 pueue.daemon.network.message_handler.reset | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 23 pueue.daemon.network.message_handler.restart | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 24 pueue.daemon.network.message_handler.start | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 25 pueue.daemon.network.message_handler.stash | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 26 pueue.daemon.network.message_handler.switch | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 27 pueue.process_helper | 1 | |||||||||||||||||||||||||||||||||||||||
| 28 pueue.client.commands | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 29 pueue.client.commands.add | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 30 pueue.client.commands.edit | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 31 pueue.client.commands.env | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 32 pueue.client.commands.follow | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 33 pueue.client.commands.group | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 34 pueue.client.commands.kill | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 35 pueue.client.commands.log | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 36 pueue.client.commands.remove | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 37 pueue.client.commands.state.table_builder | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 38 pueue.client.commands.wait | 1 | 2 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 39 pueue.daemon.process_handler | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 40 pueue.client.commands.state | 1 | 1 | 1 | 1 | 1 | 1 |
4→3 pueue.client.commands.state.query uses pueue_lib.task✕
- Connections
- 1 pair of types, where a type in pueue.client.commands.state.query uses a type in pueue_lib.task.
- The types involved
pueue.client.commands.state.query.QueryResult→pueue_lib.task.Task
- Direction
- pueue.client.commands.state.query uses pueue_lib.task, so a change to pueue_lib.task can break pueue.client.commands.state.query, while a change to pueue.client.commands.state.query can't break pueue_lib.task.
- Position
- Below the diagonal: pueue.client.commands.state.query uses a module listed above it, which is the healthy direction.
5→3 pueue_lib.message.response uses pueue_lib.task✕
- Connections
- 1 pair of types, where a type in pueue_lib.message.response uses a type in pueue_lib.task.
- The types involved
pueue_lib.message.response.TaskLogResponse→pueue_lib.task.Task
- Direction
- pueue_lib.message.response uses pueue_lib.task, so a change to pueue_lib.task can break pueue_lib.message.response, while a change to pueue_lib.message.response can't break pueue_lib.task.
- Position
- Below the diagonal: pueue_lib.message.response uses a module listed above it, which is the healthy direction.
6→9 pueue_lib.network.socket uses pueue_lib.settings part of a loop✕
- Connections
- 1 pair of types, where a type in pueue_lib.network.socket uses a type in pueue_lib.settings.
- The types involved
pueue_lib.network.socket.ConnectionSettings→pueue_lib.settings.Shared
- Direction
- pueue_lib.network.socket uses pueue_lib.settings, so a change to pueue_lib.settings can break pueue_lib.network.socket, while a change to pueue_lib.network.socket can't break pueue_lib.settings.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→3 pueue_lib.state uses pueue_lib.task✕
- Connections
- 1 pair of types, where a type in pueue_lib.state uses a type in pueue_lib.task.
- The types involved
pueue_lib.state.State→pueue_lib.task.Task
- Direction
- pueue_lib.state uses pueue_lib.task, so a change to pueue_lib.task can break pueue_lib.state, while a change to pueue_lib.state can't break pueue_lib.task.
- Position
- Below the diagonal: pueue_lib.state uses a module listed above it, which is the healthy direction.
8→6 pueue_lib.network.client uses pueue_lib.network.socket✕
- Connections
- 1 pair of types, where a type in pueue_lib.network.client uses a type in pueue_lib.network.socket.
- The types involved
pueue_lib.network.client.Client→pueue_lib.network.socket.ConnectionSettings
- Direction
- pueue_lib.network.client uses pueue_lib.network.socket, so a change to pueue_lib.network.socket can break pueue_lib.network.client, while a change to pueue_lib.network.client can't break pueue_lib.network.socket.
- Position
- Below the diagonal: pueue_lib.network.client uses a module listed above it, which is the healthy direction.
9→8 pueue_lib.settings uses pueue_lib.network.client✕
- Connections
- 2 pairs of types, where a type in pueue_lib.settings uses a type in pueue_lib.network.client.
- The types involved
pueue_lib.settings.NestedSettings→pueue_lib.network.client.Clientpueue_lib.settings.Settings→pueue_lib.network.client.Client
- Direction
- pueue_lib.settings uses pueue_lib.network.client, so a change to pueue_lib.network.client can break pueue_lib.settings, while a change to pueue_lib.settings can't break pueue_lib.network.client.
- Position
- Below the diagonal: pueue_lib.settings uses a module listed above it, which is the healthy direction.
10→9 pueue.client.style uses pueue_lib.settings✕
- Connections
- 1 pair of types, where a type in pueue.client.style uses a type in pueue_lib.settings.
- The types involved
pueue.client.style.OutputStyle→pueue_lib.settings.Settings
- Direction
- pueue.client.style uses pueue_lib.settings, so a change to pueue_lib.settings can break pueue.client.style, while a change to pueue.client.style can't break pueue_lib.settings.
- Position
- Below the diagonal: pueue.client.style uses a module listed above it, which is the healthy direction.
11→2 pueue.daemon.internal_state.state uses pueue_lib.message.request✕
- Connections
- 1 pair of types, where a type in pueue.daemon.internal_state.state uses a type in pueue_lib.message.request.
- The types involved
pueue.daemon.internal_state.state.InternalState→pueue_lib.message.request.ShutdownRequest
- Direction
- pueue.daemon.internal_state.state uses pueue_lib.message.request, so a change to pueue_lib.message.request can break pueue.daemon.internal_state.state, while a change to pueue.daemon.internal_state.state can't break pueue_lib.message.request.
- Position
- Below the diagonal: pueue.daemon.internal_state.state uses a module listed above it, which is the healthy direction.
11→3 pueue.daemon.internal_state.state uses pueue_lib.task✕
- Connections
- 2 pairs of types, where a type in pueue.daemon.internal_state.state uses a type in pueue_lib.task.
- The types involved
pueue.daemon.internal_state.state.InternalState→pueue_lib.task.Taskpueue.daemon.internal_state.state.InternalState→pueue_lib.task.TaskStatus
- Direction
- pueue.daemon.internal_state.state uses pueue_lib.task, so a change to pueue_lib.task can break pueue.daemon.internal_state.state, while a change to pueue.daemon.internal_state.state can't break pueue_lib.task.
- Position
- Below the diagonal: pueue.daemon.internal_state.state uses a module listed above it, which is the healthy direction.
11→7 pueue.daemon.internal_state.state uses pueue_lib.state✕
- Connections
- 4 pairs of types, where a type in pueue.daemon.internal_state.state uses a type in pueue_lib.state.
- The types involved
pueue.daemon.internal_state.state.InternalState→pueue_lib.state.FilteredTaskspueue.daemon.internal_state.state.InternalState→pueue_lib.state.Grouppueue.daemon.internal_state.state.InternalState→pueue_lib.state.GroupStatuspueue.daemon.internal_state.state.InternalState→pueue_lib.state.State
- Direction
- pueue.daemon.internal_state.state uses pueue_lib.state, so a change to pueue_lib.state can break pueue.daemon.internal_state.state, while a change to pueue.daemon.internal_state.state can't break pueue_lib.state.
- Position
- Below the diagonal: pueue.daemon.internal_state.state uses a module listed above it, which is the healthy direction.
11→9 pueue.daemon.internal_state.state uses pueue_lib.settings✕
- Connections
- 1 pair of types, where a type in pueue.daemon.internal_state.state uses a type in pueue_lib.settings.
- The types involved
pueue.daemon.internal_state.state.InternalState→pueue_lib.settings.Settings
- Direction
- pueue.daemon.internal_state.state uses pueue_lib.settings, so a change to pueue_lib.settings can break pueue.daemon.internal_state.state, while a change to pueue.daemon.internal_state.state can't break pueue_lib.settings.
- Position
- Below the diagonal: pueue.daemon.internal_state.state uses a module listed above it, which is the healthy direction.
12→2 pueue.daemon.network.message_handler uses pueue_lib.message.request✕
- Connections
- 1 pair of types, where a type in pueue.daemon.network.message_handler uses a type in pueue_lib.message.request.
- The types involved
pueue.daemon.network.message_handler.message_handler$module→pueue_lib.message.request.Request
- Direction
- pueue.daemon.network.message_handler uses pueue_lib.message.request, so a change to pueue_lib.message.request can break pueue.daemon.network.message_handler, while a change to pueue.daemon.network.message_handler can't break pueue_lib.message.request.
- Position
- Below the diagonal: pueue.daemon.network.message_handler uses a module listed above it, which is the healthy direction.
12→5 pueue.daemon.network.message_handler uses pueue_lib.message.response✕
- Connections
- 1 pair of types, where a type in pueue.daemon.network.message_handler uses a type in pueue_lib.message.response.
- The types involved
pueue.daemon.network.message_handler.message_handler$module→pueue_lib.message.response.Response
- Direction
- pueue.daemon.network.message_handler uses pueue_lib.message.response, so a change to pueue_lib.message.response can break pueue.daemon.network.message_handler, while a change to pueue.daemon.network.message_handler can't break pueue_lib.message.response.
- Position
- Below the diagonal: pueue.daemon.network.message_handler uses a module listed above it, which is the healthy direction.
12→9 pueue.daemon.network.message_handler uses pueue_lib.settings✕
- Connections
- 1 pair of types, where a type in pueue.daemon.network.message_handler uses a type in pueue_lib.settings.
- The types involved
pueue.daemon.network.message_handler.message_handler$module→pueue_lib.settings.Settings
- Direction
- pueue.daemon.network.message_handler uses pueue_lib.settings, so a change to pueue_lib.settings can break pueue.daemon.network.message_handler, while a change to pueue.daemon.network.message_handler can't break pueue_lib.settings.
- Position
- Below the diagonal: pueue.daemon.network.message_handler uses a module listed above it, which is the healthy direction.
13→2 pueue.daemon.network.message_handler.add uses pueue_lib.message.request✕
- Connections
- 1 pair of types, where a type in pueue.daemon.network.message_handler.add uses a type in pueue_lib.message.request.
- The types involved
pueue.daemon.network.message_handler.add.add$module→pueue_lib.message.request.AddRequest
- Direction
- pueue.daemon.network.message_handler.add uses pueue_lib.message.request, so a change to pueue_lib.message.request can break pueue.daemon.network.message_handler.add, while a change to pueue.daemon.network.message_handler.add can't break pueue_lib.message.request.
- Position
- Below the diagonal: pueue.daemon.network.message_handler.add uses a module listed above it, which is the healthy direction.
13→5 pueue.daemon.network.message_handler.add uses pueue_lib.message.response✕
- Connections
- 1 pair of types, where a type in pueue.daemon.network.message_handler.add uses a type in pueue_lib.message.response.
- The types involved
pueue.daemon.network.message_handler.add.add$module→pueue_lib.message.response.Response
- Direction
- pueue.daemon.network.message_handler.add uses pueue_lib.message.response, so a change to pueue_lib.message.response can break pueue.daemon.network.message_handler.add, while a change to pueue.daemon.network.message_handler.add can't break pueue_lib.message.response.
- Position
- Below the diagonal: pueue.daemon.network.message_handler.add uses a module listed above it, which is the healthy direction.
13→9 pueue.daemon.network.message_handler.add uses pueue_lib.settings✕
- Connections
- 1 pair of types, where a type in pueue.daemon.network.message_handler.add uses a type in pueue_lib.settings.
- The types involved
pueue.daemon.network.message_handler.add.add$module→pueue_lib.settings.Settings
- Direction
- pueue.daemon.network.message_handler.add uses pueue_lib.settings, so a change to pueue_lib.settings can break pueue.daemon.network.message_handler.add, while a change to pueue.daemon.network.message_handler.add can't break pueue_lib.settings.
- Position
- Below the diagonal: pueue.daemon.network.message_handler.add uses a module listed above it, which is the healthy direction.
14→2 pueue.daemon.network.message_handler.clean uses pueue_lib.message.request✕
- Connections
- 1 pair of types, where a type in pueue.daemon.network.message_handler.clean uses a type in pueue_lib.message.request.
- The types involved
pueue.daemon.network.message_handler.clean.clean$module→pueue_lib.message.request.CleanRequest
- Direction
- pueue.daemon.network.message_handler.clean uses pueue_lib.message.request, so a change to pueue_lib.message.request can break pueue.daemon.network.message_handler.clean, while a change to pueue.daemon.network.message_handler.clean can't break pueue_lib.message.request.
- Position
- Below the diagonal: pueue.daemon.network.message_handler.clean uses a module listed above it, which is the healthy direction.
14→5 pueue.daemon.network.message_handler.clean uses pueue_lib.message.response✕
- Connections
- 1 pair of types, where a type in pueue.daemon.network.message_handler.clean uses a type in pueue_lib.message.response.
- The types involved
pueue.daemon.network.message_handler.clean.clean$module→pueue_lib.message.response.Response
- Direction
- pueue.daemon.network.message_handler.clean uses pueue_lib.message.response, so a change to pueue_lib.message.response can break pueue.daemon.network.message_handler.clean, while a change to pueue.daemon.network.message_handler.clean can't break pueue_lib.message.response.
- Position
- Below the diagonal: pueue.daemon.network.message_handler.clean uses a module listed above it, which is the healthy direction.
14→9 pueue.daemon.network.message_handler.clean uses pueue_lib.settings✕
- Connections
- 1 pair of types, where a type in pueue.daemon.network.message_handler.clean uses a type in pueue_lib.settings.
- The types involved
pueue.daemon.network.message_handler.clean.clean$module→pueue_lib.settings.Settings
- Direction
- pueue.daemon.network.message_handler.clean uses pueue_lib.settings, so a change to pueue_lib.settings can break pueue.daemon.network.message_handler.clean, while a change to pueue.daemon.network.message_handler.clean can't break pueue_lib.settings.
- Position
- Below the diagonal: pueue.daemon.network.message_handler.clean uses a module listed above it, which is the healthy direction.
15→5 pueue.daemon.network.message_handler.edit uses pueue_lib.message.response✕
- Connections
- 1 pair of types, where a type in pueue.daemon.network.message_handler.edit uses a type in pueue_lib.message.response.
- The types involved
pueue.daemon.network.message_handler.edit.edit$module→pueue_lib.message.response.Response
- Direction
- pueue.daemon.network.message_handler.edit uses pueue_lib.message.response, so a change to pueue_lib.message.response can break pueue.daemon.network.message_handler.edit, while a change to pueue.daemon.network.message_handler.edit can't break pueue_lib.message.response.
- Position
- Below the diagonal: pueue.daemon.network.message_handler.edit uses a module listed above it, which is the healthy direction.
15→9 pueue.daemon.network.message_handler.edit uses pueue_lib.settings✕
- Connections
- 1 pair of types, where a type in pueue.daemon.network.message_handler.edit uses a type in pueue_lib.settings.
- The types involved
pueue.daemon.network.message_handler.edit.edit$module→pueue_lib.settings.Settings
- Direction
- pueue.daemon.network.message_handler.edit uses pueue_lib.settings, so a change to pueue_lib.settings can break pueue.daemon.network.message_handler.edit, while a change to pueue.daemon.network.message_handler.edit can't break pueue_lib.settings.
- Position
- Below the diagonal: pueue.daemon.network.message_handler.edit uses a module listed above it, which is the healthy direction.
16→2 pueue.daemon.network.message_handler.enqueue uses pueue_lib.message.request✕
- Connections
- 1 pair of types, where a type in pueue.daemon.network.message_handler.enqueue uses a type in pueue_lib.message.request.
- The types involved
pueue.daemon.network.message_handler.enqueue.enqueue$module→pueue_lib.message.request.EnqueueRequest
- Direction
- pueue.daemon.network.message_handler.enqueue uses pueue_lib.message.request, so a change to pueue_lib.message.request can break pueue.daemon.network.message_handler.enqueue, while a change to pueue.daemon.network.message_handler.enqueue can't break pueue_lib.message.request.
- Position
- Below the diagonal: pueue.daemon.network.message_handler.enqueue uses a module listed above it, which is the healthy direction.
16→5 pueue.daemon.network.message_handler.enqueue uses pueue_lib.message.response✕
- Connections
- 1 pair of types, where a type in pueue.daemon.network.message_handler.enqueue uses a type in pueue_lib.message.response.
- The types involved
pueue.daemon.network.message_handler.enqueue.enqueue$module→pueue_lib.message.response.Response
- Direction
- pueue.daemon.network.message_handler.enqueue uses pueue_lib.message.response, so a change to pueue_lib.message.response can break pueue.daemon.network.message_handler.enqueue, while a change to pueue.daemon.network.message_handler.enqueue can't break pueue_lib.message.response.
- Position
- Below the diagonal: pueue.daemon.network.message_handler.enqueue uses a module listed above it, which is the healthy direction.
16→9 pueue.daemon.network.message_handler.enqueue uses pueue_lib.settings✕
- Connections
- 1 pair of types, where a type in pueue.daemon.network.message_handler.enqueue uses a type in pueue_lib.settings.
- The types involved
pueue.daemon.network.message_handler.enqueue.enqueue$module→pueue_lib.settings.Settings
- Direction
- pueue.daemon.network.message_handler.enqueue uses pueue_lib.settings, so a change to pueue_lib.settings can break pueue.daemon.network.message_handler.enqueue, while a change to pueue.daemon.network.message_handler.enqueue can't break pueue_lib.settings.
- Position
- Below the diagonal: pueue.daemon.network.message_handler.enqueue uses a module listed above it, which is the healthy direction.
17→2 pueue.daemon.network.message_handler.env uses pueue_lib.message.request✕
- Connections
- 1 pair of types, where a type in pueue.daemon.network.message_handler.env uses a type in pueue_lib.message.request.
- The types involved
pueue.daemon.network.message_handler.env.env$module→pueue_lib.message.request.EnvRequest
- Direction
- pueue.daemon.network.message_handler.env uses pueue_lib.message.request, so a change to pueue_lib.message.request can break pueue.daemon.network.message_handler.env, while a change to pueue.daemon.network.message_handler.env can't break pueue_lib.message.request.
- Position
- Below the diagonal: pueue.daemon.network.message_handler.env uses a module listed above it, which is the healthy direction.
17→5 pueue.daemon.network.message_handler.env uses pueue_lib.message.response✕
- Connections
- 1 pair of types, where a type in pueue.daemon.network.message_handler.env uses a type in pueue_lib.message.response.
- The types involved
pueue.daemon.network.message_handler.env.env$module→pueue_lib.message.response.Response
- Direction
- pueue.daemon.network.message_handler.env uses pueue_lib.message.response, so a change to pueue_lib.message.response can break pueue.daemon.network.message_handler.env, while a change to pueue.daemon.network.message_handler.env can't break pueue_lib.message.response.
- Position
- Below the diagonal: pueue.daemon.network.message_handler.env uses a module listed above it, which is the healthy direction.
17→9 pueue.daemon.network.message_handler.env uses pueue_lib.settings✕
- Connections
- 1 pair of types, where a type in pueue.daemon.network.message_handler.env uses a type in pueue_lib.settings.
- The types involved
pueue.daemon.network.message_handler.env.env$module→pueue_lib.settings.Settings
- Direction
- pueue.daemon.network.message_handler.env uses pueue_lib.settings, so a change to pueue_lib.settings can break pueue.daemon.network.message_handler.env, while a change to pueue.daemon.network.message_handler.env can't break pueue_lib.settings.
- Position
- Below the diagonal: pueue.daemon.network.message_handler.env uses a module listed above it, which is the healthy direction.
18→2 pueue.daemon.network.message_handler.group uses pueue_lib.message.request✕
- Connections
- 1 pair of types, where a type in pueue.daemon.network.message_handler.group uses a type in pueue_lib.message.request.
- The types involved
pueue.daemon.network.message_handler.group.group$module→pueue_lib.message.request.GroupRequest
- Direction
- pueue.daemon.network.message_handler.group uses pueue_lib.message.request, so a change to pueue_lib.message.request can break pueue.daemon.network.message_handler.group, while a change to pueue.daemon.network.message_handler.group can't break pueue_lib.message.request.
- Position
- Below the diagonal: pueue.daemon.network.message_handler.group uses a module listed above it, which is the healthy direction.
18→5 pueue.daemon.network.message_handler.group uses pueue_lib.message.response✕
- Connections
- 1 pair of types, where a type in pueue.daemon.network.message_handler.group uses a type in pueue_lib.message.response.
- The types involved
pueue.daemon.network.message_handler.group.group$module→pueue_lib.message.response.Response
- Direction
- pueue.daemon.network.message_handler.group uses pueue_lib.message.response, so a change to pueue_lib.message.response can break pueue.daemon.network.message_handler.group, while a change to pueue.daemon.network.message_handler.group can't break pueue_lib.message.response.
- Position
- Below the diagonal: pueue.daemon.network.message_handler.group uses a module listed above it, which is the healthy direction.
18→9 pueue.daemon.network.message_handler.group uses pueue_lib.settings✕
- Connections
- 1 pair of types, where a type in pueue.daemon.network.message_handler.group uses a type in pueue_lib.settings.
- The types involved
pueue.daemon.network.message_handler.group.group$module→pueue_lib.settings.Settings
- Direction
- pueue.daemon.network.message_handler.group uses pueue_lib.settings, so a change to pueue_lib.settings can break pueue.daemon.network.message_handler.group, while a change to pueue.daemon.network.message_handler.group can't break pueue_lib.settings.
- Position
- Below the diagonal: pueue.daemon.network.message_handler.group uses a module listed above it, which is the healthy direction.
19→2 pueue.daemon.network.message_handler.kill uses pueue_lib.message.request✕
- Connections
- 1 pair of types, where a type in pueue.daemon.network.message_handler.kill uses a type in pueue_lib.message.request.
- The types involved
pueue.daemon.network.message_handler.kill.kill$module→pueue_lib.message.request.KillRequest
- Direction
- pueue.daemon.network.message_handler.kill uses pueue_lib.message.request, so a change to pueue_lib.message.request can break pueue.daemon.network.message_handler.kill, while a change to pueue.daemon.network.message_handler.kill can't break pueue_lib.message.request.
- Position
- Below the diagonal: pueue.daemon.network.message_handler.kill uses a module listed above it, which is the healthy direction.
19→5 pueue.daemon.network.message_handler.kill uses pueue_lib.message.response✕
- Connections
- 1 pair of types, where a type in pueue.daemon.network.message_handler.kill uses a type in pueue_lib.message.response.
- The types involved
pueue.daemon.network.message_handler.kill.kill$module→pueue_lib.message.response.Response
- Direction
- pueue.daemon.network.message_handler.kill uses pueue_lib.message.response, so a change to pueue_lib.message.response can break pueue.daemon.network.message_handler.kill, while a change to pueue.daemon.network.message_handler.kill can't break pueue_lib.message.response.
- Position
- Below the diagonal: pueue.daemon.network.message_handler.kill uses a module listed above it, which is the healthy direction.
19→9 pueue.daemon.network.message_handler.kill uses pueue_lib.settings✕
- Connections
- 1 pair of types, where a type in pueue.daemon.network.message_handler.kill uses a type in pueue_lib.settings.
- The types involved
pueue.daemon.network.message_handler.kill.kill$module→pueue_lib.settings.Settings
- Direction
- pueue.daemon.network.message_handler.kill uses pueue_lib.settings, so a change to pueue_lib.settings can break pueue.daemon.network.message_handler.kill, while a change to pueue.daemon.network.message_handler.kill can't break pueue_lib.settings.
- Position
- Below the diagonal: pueue.daemon.network.message_handler.kill uses a module listed above it, which is the healthy direction.
20→2 pueue.daemon.network.message_handler.log uses pueue_lib.message.request✕
- Connections
- 2 pairs of types, where a type in pueue.daemon.network.message_handler.log uses a type in pueue_lib.message.request.
- The types involved
pueue.daemon.network.message_handler.log.log$module→pueue_lib.message.request.LogRequestpueue.daemon.network.message_handler.log.log$module→pueue_lib.message.request.StreamRequest
- Direction
- pueue.daemon.network.message_handler.log uses pueue_lib.message.request, so a change to pueue_lib.message.request can break pueue.daemon.network.message_handler.log, while a change to pueue.daemon.network.message_handler.log can't break pueue_lib.message.request.
- Position
- Below the diagonal: pueue.daemon.network.message_handler.log uses a module listed above it, which is the healthy direction.
20→5 pueue.daemon.network.message_handler.log uses pueue_lib.message.response✕
- Connections
- 1 pair of types, where a type in pueue.daemon.network.message_handler.log uses a type in pueue_lib.message.response.
- The types involved
pueue.daemon.network.message_handler.log.log$module→pueue_lib.message.response.Response
- Direction
- pueue.daemon.network.message_handler.log uses pueue_lib.message.response, so a change to pueue_lib.message.response can break pueue.daemon.network.message_handler.log, while a change to pueue.daemon.network.message_handler.log can't break pueue_lib.message.response.
- Position
- Below the diagonal: pueue.daemon.network.message_handler.log uses a module listed above it, which is the healthy direction.
20→9 pueue.daemon.network.message_handler.log uses pueue_lib.settings✕
- Connections
- 1 pair of types, where a type in pueue.daemon.network.message_handler.log uses a type in pueue_lib.settings.
- The types involved
pueue.daemon.network.message_handler.log.log$module→pueue_lib.settings.Settings
- Direction
- pueue.daemon.network.message_handler.log uses pueue_lib.settings, so a change to pueue_lib.settings can break pueue.daemon.network.message_handler.log, while a change to pueue.daemon.network.message_handler.log can't break pueue_lib.settings.
- Position
- Below the diagonal: pueue.daemon.network.message_handler.log uses a module listed above it, which is the healthy direction.
21→2 pueue.daemon.network.message_handler.pause uses pueue_lib.message.request✕
- Connections
- 1 pair of types, where a type in pueue.daemon.network.message_handler.pause uses a type in pueue_lib.message.request.
- The types involved
pueue.daemon.network.message_handler.pause.pause$module→pueue_lib.message.request.PauseRequest
- Direction
- pueue.daemon.network.message_handler.pause uses pueue_lib.message.request, so a change to pueue_lib.message.request can break pueue.daemon.network.message_handler.pause, while a change to pueue.daemon.network.message_handler.pause can't break pueue_lib.message.request.
- Position
- Below the diagonal: pueue.daemon.network.message_handler.pause uses a module listed above it, which is the healthy direction.
21→5 pueue.daemon.network.message_handler.pause uses pueue_lib.message.response✕
- Connections
- 1 pair of types, where a type in pueue.daemon.network.message_handler.pause uses a type in pueue_lib.message.response.
- The types involved
pueue.daemon.network.message_handler.pause.pause$module→pueue_lib.message.response.Response
- Direction
- pueue.daemon.network.message_handler.pause uses pueue_lib.message.response, so a change to pueue_lib.message.response can break pueue.daemon.network.message_handler.pause, while a change to pueue.daemon.network.message_handler.pause can't break pueue_lib.message.response.
- Position
- Below the diagonal: pueue.daemon.network.message_handler.pause uses a module listed above it, which is the healthy direction.
21→9 pueue.daemon.network.message_handler.pause uses pueue_lib.settings✕
- Connections
- 1 pair of types, where a type in pueue.daemon.network.message_handler.pause uses a type in pueue_lib.settings.
- The types involved
pueue.daemon.network.message_handler.pause.pause$module→pueue_lib.settings.Settings
- Direction
- pueue.daemon.network.message_handler.pause uses pueue_lib.settings, so a change to pueue_lib.settings can break pueue.daemon.network.message_handler.pause, while a change to pueue.daemon.network.message_handler.pause can't break pueue_lib.settings.
- Position
- Below the diagonal: pueue.daemon.network.message_handler.pause uses a module listed above it, which is the healthy direction.
22→2 pueue.daemon.network.message_handler.reset uses pueue_lib.message.request✕
- Connections
- 1 pair of types, where a type in pueue.daemon.network.message_handler.reset uses a type in pueue_lib.message.request.
- The types involved
pueue.daemon.network.message_handler.reset.reset$module→pueue_lib.message.request.ResetRequest
- Direction
- pueue.daemon.network.message_handler.reset uses pueue_lib.message.request, so a change to pueue_lib.message.request can break pueue.daemon.network.message_handler.reset, while a change to pueue.daemon.network.message_handler.reset can't break pueue_lib.message.request.
- Position
- Below the diagonal: pueue.daemon.network.message_handler.reset uses a module listed above it, which is the healthy direction.
22→5 pueue.daemon.network.message_handler.reset uses pueue_lib.message.response✕
- Connections
- 1 pair of types, where a type in pueue.daemon.network.message_handler.reset uses a type in pueue_lib.message.response.
- The types involved
pueue.daemon.network.message_handler.reset.reset$module→pueue_lib.message.response.Response
- Direction
- pueue.daemon.network.message_handler.reset uses pueue_lib.message.response, so a change to pueue_lib.message.response can break pueue.daemon.network.message_handler.reset, while a change to pueue.daemon.network.message_handler.reset can't break pueue_lib.message.response.
- Position
- Below the diagonal: pueue.daemon.network.message_handler.reset uses a module listed above it, which is the healthy direction.
22→9 pueue.daemon.network.message_handler.reset uses pueue_lib.settings✕
- Connections
- 1 pair of types, where a type in pueue.daemon.network.message_handler.reset uses a type in pueue_lib.settings.
- The types involved
pueue.daemon.network.message_handler.reset.reset$module→pueue_lib.settings.Settings
- Direction
- pueue.daemon.network.message_handler.reset uses pueue_lib.settings, so a change to pueue_lib.settings can break pueue.daemon.network.message_handler.reset, while a change to pueue.daemon.network.message_handler.reset can't break pueue_lib.settings.
- Position
- Below the diagonal: pueue.daemon.network.message_handler.reset uses a module listed above it, which is the healthy direction.
23→2 pueue.daemon.network.message_handler.restart uses pueue_lib.message.request✕
- Connections
- 2 pairs of types, where a type in pueue.daemon.network.message_handler.restart uses a type in pueue_lib.message.request.
- The types involved
pueue.daemon.network.message_handler.restart.restart$module→pueue_lib.message.request.RestartRequestpueue.daemon.network.message_handler.restart.restart$module→pueue_lib.message.request.TaskToRestart
- Direction
- pueue.daemon.network.message_handler.restart uses pueue_lib.message.request, so a change to pueue_lib.message.request can break pueue.daemon.network.message_handler.restart, while a change to pueue.daemon.network.message_handler.restart can't break pueue_lib.message.request.
- Position
- Below the diagonal: pueue.daemon.network.message_handler.restart uses a module listed above it, which is the healthy direction.
23→5 pueue.daemon.network.message_handler.restart uses pueue_lib.message.response✕
- Connections
- 1 pair of types, where a type in pueue.daemon.network.message_handler.restart uses a type in pueue_lib.message.response.
- The types involved
pueue.daemon.network.message_handler.restart.restart$module→pueue_lib.message.response.Response
- Direction
- pueue.daemon.network.message_handler.restart uses pueue_lib.message.response, so a change to pueue_lib.message.response can break pueue.daemon.network.message_handler.restart, while a change to pueue.daemon.network.message_handler.restart can't break pueue_lib.message.response.
- Position
- Below the diagonal: pueue.daemon.network.message_handler.restart uses a module listed above it, which is the healthy direction.
23→9 pueue.daemon.network.message_handler.restart uses pueue_lib.settings✕
- Connections
- 1 pair of types, where a type in pueue.daemon.network.message_handler.restart uses a type in pueue_lib.settings.
- The types involved
pueue.daemon.network.message_handler.restart.restart$module→pueue_lib.settings.Settings
- Direction
- pueue.daemon.network.message_handler.restart uses pueue_lib.settings, so a change to pueue_lib.settings can break pueue.daemon.network.message_handler.restart, while a change to pueue.daemon.network.message_handler.restart can't break pueue_lib.settings.
- Position
- Below the diagonal: pueue.daemon.network.message_handler.restart uses a module listed above it, which is the healthy direction.
24→2 pueue.daemon.network.message_handler.start uses pueue_lib.message.request✕
- Connections
- 1 pair of types, where a type in pueue.daemon.network.message_handler.start uses a type in pueue_lib.message.request.
- The types involved
pueue.daemon.network.message_handler.start.start$module→pueue_lib.message.request.StartRequest
- Direction
- pueue.daemon.network.message_handler.start uses pueue_lib.message.request, so a change to pueue_lib.message.request can break pueue.daemon.network.message_handler.start, while a change to pueue.daemon.network.message_handler.start can't break pueue_lib.message.request.
- Position
- Below the diagonal: pueue.daemon.network.message_handler.start uses a module listed above it, which is the healthy direction.
24→5 pueue.daemon.network.message_handler.start uses pueue_lib.message.response✕
- Connections
- 1 pair of types, where a type in pueue.daemon.network.message_handler.start uses a type in pueue_lib.message.response.
- The types involved
pueue.daemon.network.message_handler.start.start$module→pueue_lib.message.response.Response
- Direction
- pueue.daemon.network.message_handler.start uses pueue_lib.message.response, so a change to pueue_lib.message.response can break pueue.daemon.network.message_handler.start, while a change to pueue.daemon.network.message_handler.start can't break pueue_lib.message.response.
- Position
- Below the diagonal: pueue.daemon.network.message_handler.start uses a module listed above it, which is the healthy direction.
24→9 pueue.daemon.network.message_handler.start uses pueue_lib.settings✕
- Connections
- 1 pair of types, where a type in pueue.daemon.network.message_handler.start uses a type in pueue_lib.settings.
- The types involved
pueue.daemon.network.message_handler.start.start$module→pueue_lib.settings.Settings
- Direction
- pueue.daemon.network.message_handler.start uses pueue_lib.settings, so a change to pueue_lib.settings can break pueue.daemon.network.message_handler.start, while a change to pueue.daemon.network.message_handler.start can't break pueue_lib.settings.
- Position
- Below the diagonal: pueue.daemon.network.message_handler.start uses a module listed above it, which is the healthy direction.
25→2 pueue.daemon.network.message_handler.stash uses pueue_lib.message.request✕
- Connections
- 1 pair of types, where a type in pueue.daemon.network.message_handler.stash uses a type in pueue_lib.message.request.
- The types involved
pueue.daemon.network.message_handler.stash.stash$module→pueue_lib.message.request.StashRequest
- Direction
- pueue.daemon.network.message_handler.stash uses pueue_lib.message.request, so a change to pueue_lib.message.request can break pueue.daemon.network.message_handler.stash, while a change to pueue.daemon.network.message_handler.stash can't break pueue_lib.message.request.
- Position
- Below the diagonal: pueue.daemon.network.message_handler.stash uses a module listed above it, which is the healthy direction.
25→5 pueue.daemon.network.message_handler.stash uses pueue_lib.message.response✕
- Connections
- 1 pair of types, where a type in pueue.daemon.network.message_handler.stash uses a type in pueue_lib.message.response.
- The types involved
pueue.daemon.network.message_handler.stash.stash$module→pueue_lib.message.response.Response
- Direction
- pueue.daemon.network.message_handler.stash uses pueue_lib.message.response, so a change to pueue_lib.message.response can break pueue.daemon.network.message_handler.stash, while a change to pueue.daemon.network.message_handler.stash can't break pueue_lib.message.response.
- Position
- Below the diagonal: pueue.daemon.network.message_handler.stash uses a module listed above it, which is the healthy direction.
25→9 pueue.daemon.network.message_handler.stash uses pueue_lib.settings✕
- Connections
- 1 pair of types, where a type in pueue.daemon.network.message_handler.stash uses a type in pueue_lib.settings.
- The types involved
pueue.daemon.network.message_handler.stash.stash$module→pueue_lib.settings.Settings
- Direction
- pueue.daemon.network.message_handler.stash uses pueue_lib.settings, so a change to pueue_lib.settings can break pueue.daemon.network.message_handler.stash, while a change to pueue.daemon.network.message_handler.stash can't break pueue_lib.settings.
- Position
- Below the diagonal: pueue.daemon.network.message_handler.stash uses a module listed above it, which is the healthy direction.
26→2 pueue.daemon.network.message_handler.switch uses pueue_lib.message.request✕
- Connections
- 1 pair of types, where a type in pueue.daemon.network.message_handler.switch uses a type in pueue_lib.message.request.
- The types involved
pueue.daemon.network.message_handler.switch.switch$module→pueue_lib.message.request.SwitchRequest
- Direction
- pueue.daemon.network.message_handler.switch uses pueue_lib.message.request, so a change to pueue_lib.message.request can break pueue.daemon.network.message_handler.switch, while a change to pueue.daemon.network.message_handler.switch can't break pueue_lib.message.request.
- Position
- Below the diagonal: pueue.daemon.network.message_handler.switch uses a module listed above it, which is the healthy direction.
26→5 pueue.daemon.network.message_handler.switch uses pueue_lib.message.response✕
- Connections
- 1 pair of types, where a type in pueue.daemon.network.message_handler.switch uses a type in pueue_lib.message.response.
- The types involved
pueue.daemon.network.message_handler.switch.switch$module→pueue_lib.message.response.Response
- Direction
- pueue.daemon.network.message_handler.switch uses pueue_lib.message.response, so a change to pueue_lib.message.response can break pueue.daemon.network.message_handler.switch, while a change to pueue.daemon.network.message_handler.switch can't break pueue_lib.message.response.
- Position
- Below the diagonal: pueue.daemon.network.message_handler.switch uses a module listed above it, which is the healthy direction.
26→9 pueue.daemon.network.message_handler.switch uses pueue_lib.settings✕
- Connections
- 1 pair of types, where a type in pueue.daemon.network.message_handler.switch uses a type in pueue_lib.settings.
- The types involved
pueue.daemon.network.message_handler.switch.switch$module→pueue_lib.settings.Settings
- Direction
- pueue.daemon.network.message_handler.switch uses pueue_lib.settings, so a change to pueue_lib.settings can break pueue.daemon.network.message_handler.switch, while a change to pueue.daemon.network.message_handler.switch can't break pueue_lib.settings.
- Position
- Below the diagonal: pueue.daemon.network.message_handler.switch uses a module listed above it, which is the healthy direction.
27→9 pueue.process_helper uses pueue_lib.settings✕
- Connections
- 1 pair of types, where a type in pueue.process_helper uses a type in pueue_lib.settings.
- The types involved
pueue.process_helper.process_helper$module→pueue_lib.settings.Settings
- Direction
- pueue.process_helper uses pueue_lib.settings, so a change to pueue_lib.settings can break pueue.process_helper, while a change to pueue.process_helper can't break pueue_lib.settings.
- Position
- Below the diagonal: pueue.process_helper uses a module listed above it, which is the healthy direction.
28→1 pueue.client.commands uses pueue.client.cli✕
- Connections
- 1 pair of types, where a type in pueue.client.commands uses a type in pueue.client.cli.
- The types involved
pueue.client.commands.commands$module→pueue.client.cli.SubCommand
- Direction
- pueue.client.commands uses pueue.client.cli, so a change to pueue.client.cli can break pueue.client.commands, while a change to pueue.client.commands can't break pueue.client.cli.
- Position
- Below the diagonal: pueue.client.commands uses a module listed above it, which is the healthy direction.
28→2 pueue.client.commands uses pueue_lib.message.request✕
- Connections
- 1 pair of types, where a type in pueue.client.commands uses a type in pueue_lib.message.request.
- The types involved
pueue.client.commands.commands$module→pueue_lib.message.request.TaskSelection
- Direction
- pueue.client.commands uses pueue_lib.message.request, so a change to pueue_lib.message.request can break pueue.client.commands, while a change to pueue.client.commands can't break pueue_lib.message.request.
- Position
- Below the diagonal: pueue.client.commands uses a module listed above it, which is the healthy direction.
28→5 pueue.client.commands uses pueue_lib.message.response✕
- Connections
- 1 pair of types, where a type in pueue.client.commands uses a type in pueue_lib.message.response.
- The types involved
pueue.client.commands.commands$module→pueue_lib.message.response.Response
- Direction
- pueue.client.commands uses pueue_lib.message.response, so a change to pueue_lib.message.response can break pueue.client.commands, while a change to pueue.client.commands can't break pueue_lib.message.response.
- Position
- Below the diagonal: pueue.client.commands uses a module listed above it, which is the healthy direction.
28→8 pueue.client.commands uses pueue_lib.network.client✕
- Connections
- 1 pair of types, where a type in pueue.client.commands uses a type in pueue_lib.network.client.
- The types involved
pueue.client.commands.commands$module→pueue_lib.network.client.Client
- Direction
- pueue.client.commands uses pueue_lib.network.client, so a change to pueue_lib.network.client can break pueue.client.commands, while a change to pueue.client.commands can't break pueue_lib.network.client.
- Position
- Below the diagonal: pueue.client.commands uses a module listed above it, which is the healthy direction.
28→9 pueue.client.commands uses pueue_lib.settings✕
- Connections
- 1 pair of types, where a type in pueue.client.commands uses a type in pueue_lib.settings.
- The types involved
pueue.client.commands.commands$module→pueue_lib.settings.Settings
- Direction
- pueue.client.commands uses pueue_lib.settings, so a change to pueue_lib.settings can break pueue.client.commands, while a change to pueue.client.commands can't break pueue_lib.settings.
- Position
- Below the diagonal: pueue.client.commands uses a module listed above it, which is the healthy direction.
28→10 pueue.client.commands uses pueue.client.style✕
- Connections
- 1 pair of types, where a type in pueue.client.commands uses a type in pueue.client.style.
- The types involved
pueue.client.commands.commands$module→pueue.client.style.OutputStyle
- Direction
- pueue.client.commands uses pueue.client.style, so a change to pueue.client.style can break pueue.client.commands, while a change to pueue.client.commands can't break pueue.client.style.
- Position
- Below the diagonal: pueue.client.commands uses a module listed above it, which is the healthy direction.
29→8 pueue.client.commands.add uses pueue_lib.network.client✕
- Connections
- 1 pair of types, where a type in pueue.client.commands.add uses a type in pueue_lib.network.client.
- The types involved
pueue.client.commands.add.add$module→pueue_lib.network.client.Client
- Direction
- pueue.client.commands.add uses pueue_lib.network.client, so a change to pueue_lib.network.client can break pueue.client.commands.add, while a change to pueue.client.commands.add can't break pueue_lib.network.client.
- Position
- Below the diagonal: pueue.client.commands.add uses a module listed above it, which is the healthy direction.
29→9 pueue.client.commands.add uses pueue_lib.settings✕
- Connections
- 1 pair of types, where a type in pueue.client.commands.add uses a type in pueue_lib.settings.
- The types involved
pueue.client.commands.add.add$module→pueue_lib.settings.Settings
- Direction
- pueue.client.commands.add uses pueue_lib.settings, so a change to pueue_lib.settings can break pueue.client.commands.add, while a change to pueue.client.commands.add can't break pueue_lib.settings.
- Position
- Below the diagonal: pueue.client.commands.add uses a module listed above it, which is the healthy direction.
29→10 pueue.client.commands.add uses pueue.client.style✕
- Connections
- 1 pair of types, where a type in pueue.client.commands.add uses a type in pueue.client.style.
- The types involved
pueue.client.commands.add.add$module→pueue.client.style.OutputStyle
- Direction
- pueue.client.commands.add uses pueue.client.style, so a change to pueue.client.style can break pueue.client.commands.add, while a change to pueue.client.commands.add can't break pueue.client.style.
- Position
- Below the diagonal: pueue.client.commands.add uses a module listed above it, which is the healthy direction.
30→8 pueue.client.commands.edit uses pueue_lib.network.client✕
- Connections
- 1 pair of types, where a type in pueue.client.commands.edit uses a type in pueue_lib.network.client.
- The types involved
pueue.client.commands.edit.edit$module→pueue_lib.network.client.Client
- Direction
- pueue.client.commands.edit uses pueue_lib.network.client, so a change to pueue_lib.network.client can break pueue.client.commands.edit, while a change to pueue.client.commands.edit can't break pueue_lib.network.client.
- Position
- Below the diagonal: pueue.client.commands.edit uses a module listed above it, which is the healthy direction.
30→9 pueue.client.commands.edit uses pueue_lib.settings✕
- Connections
- 1 pair of types, where a type in pueue.client.commands.edit uses a type in pueue_lib.settings.
- The types involved
pueue.client.commands.edit.edit$module→pueue_lib.settings.Settings
- Direction
- pueue.client.commands.edit uses pueue_lib.settings, so a change to pueue_lib.settings can break pueue.client.commands.edit, while a change to pueue.client.commands.edit can't break pueue_lib.settings.
- Position
- Below the diagonal: pueue.client.commands.edit uses a module listed above it, which is the healthy direction.
30→10 pueue.client.commands.edit uses pueue.client.style✕
- Connections
- 1 pair of types, where a type in pueue.client.commands.edit uses a type in pueue.client.style.
- The types involved
pueue.client.commands.edit.edit$module→pueue.client.style.OutputStyle
- Direction
- pueue.client.commands.edit uses pueue.client.style, so a change to pueue.client.style can break pueue.client.commands.edit, while a change to pueue.client.commands.edit can't break pueue.client.style.
- Position
- Below the diagonal: pueue.client.commands.edit uses a module listed above it, which is the healthy direction.
31→1 pueue.client.commands.env uses pueue.client.cli✕
- Connections
- 1 pair of types, where a type in pueue.client.commands.env uses a type in pueue.client.cli.
- The types involved
pueue.client.commands.env.env$module→pueue.client.cli.EnvCommand
- Direction
- pueue.client.commands.env uses pueue.client.cli, so a change to pueue.client.cli can break pueue.client.commands.env, while a change to pueue.client.commands.env can't break pueue.client.cli.
- Position
- Below the diagonal: pueue.client.commands.env uses a module listed above it, which is the healthy direction.
31→8 pueue.client.commands.env uses pueue_lib.network.client✕
- Connections
- 1 pair of types, where a type in pueue.client.commands.env uses a type in pueue_lib.network.client.
- The types involved
pueue.client.commands.env.env$module→pueue_lib.network.client.Client
- Direction
- pueue.client.commands.env uses pueue_lib.network.client, so a change to pueue_lib.network.client can break pueue.client.commands.env, while a change to pueue.client.commands.env can't break pueue_lib.network.client.
- Position
- Below the diagonal: pueue.client.commands.env uses a module listed above it, which is the healthy direction.
31→10 pueue.client.commands.env uses pueue.client.style✕
- Connections
- 1 pair of types, where a type in pueue.client.commands.env uses a type in pueue.client.style.
- The types involved
pueue.client.commands.env.env$module→pueue.client.style.OutputStyle
- Direction
- pueue.client.commands.env uses pueue.client.style, so a change to pueue.client.style can break pueue.client.commands.env, while a change to pueue.client.commands.env can't break pueue.client.style.
- Position
- Below the diagonal: pueue.client.commands.env uses a module listed above it, which is the healthy direction.
32→8 pueue.client.commands.follow uses pueue_lib.network.client✕
- Connections
- 1 pair of types, where a type in pueue.client.commands.follow uses a type in pueue_lib.network.client.
- The types involved
pueue.client.commands.follow.follow$module→pueue_lib.network.client.Client
- Direction
- pueue.client.commands.follow uses pueue_lib.network.client, so a change to pueue_lib.network.client can break pueue.client.commands.follow, while a change to pueue.client.commands.follow can't break pueue_lib.network.client.
- Position
- Below the diagonal: pueue.client.commands.follow uses a module listed above it, which is the healthy direction.
32→9 pueue.client.commands.follow uses pueue_lib.settings✕
- Connections
- 1 pair of types, where a type in pueue.client.commands.follow uses a type in pueue_lib.settings.
- The types involved
pueue.client.commands.follow.follow$module→pueue_lib.settings.Settings
- Direction
- pueue.client.commands.follow uses pueue_lib.settings, so a change to pueue_lib.settings can break pueue.client.commands.follow, while a change to pueue.client.commands.follow can't break pueue_lib.settings.
- Position
- Below the diagonal: pueue.client.commands.follow uses a module listed above it, which is the healthy direction.
32→10 pueue.client.commands.follow uses pueue.client.style✕
- Connections
- 1 pair of types, where a type in pueue.client.commands.follow uses a type in pueue.client.style.
- The types involved
pueue.client.commands.follow.follow$module→pueue.client.style.OutputStyle
- Direction
- pueue.client.commands.follow uses pueue.client.style, so a change to pueue.client.style can break pueue.client.commands.follow, while a change to pueue.client.commands.follow can't break pueue.client.style.
- Position
- Below the diagonal: pueue.client.commands.follow uses a module listed above it, which is the healthy direction.
33→1 pueue.client.commands.group uses pueue.client.cli✕
- Connections
- 1 pair of types, where a type in pueue.client.commands.group uses a type in pueue.client.cli.
- The types involved
pueue.client.commands.group.group$module→pueue.client.cli.GroupCommand
- Direction
- pueue.client.commands.group uses pueue.client.cli, so a change to pueue.client.cli can break pueue.client.commands.group, while a change to pueue.client.commands.group can't break pueue.client.cli.
- Position
- Below the diagonal: pueue.client.commands.group uses a module listed above it, which is the healthy direction.
33→5 pueue.client.commands.group uses pueue_lib.message.response✕
- Connections
- 1 pair of types, where a type in pueue.client.commands.group uses a type in pueue_lib.message.response.
- The types involved
pueue.client.commands.group.group$module→pueue_lib.message.response.GroupResponse
- Direction
- pueue.client.commands.group uses pueue_lib.message.response, so a change to pueue_lib.message.response can break pueue.client.commands.group, while a change to pueue.client.commands.group can't break pueue_lib.message.response.
- Position
- Below the diagonal: pueue.client.commands.group uses a module listed above it, which is the healthy direction.
33→8 pueue.client.commands.group uses pueue_lib.network.client✕
- Connections
- 1 pair of types, where a type in pueue.client.commands.group uses a type in pueue_lib.network.client.
- The types involved
pueue.client.commands.group.group$module→pueue_lib.network.client.Client
- Direction
- pueue.client.commands.group uses pueue_lib.network.client, so a change to pueue_lib.network.client can break pueue.client.commands.group, while a change to pueue.client.commands.group can't break pueue_lib.network.client.
- Position
- Below the diagonal: pueue.client.commands.group uses a module listed above it, which is the healthy direction.
33→10 pueue.client.commands.group uses pueue.client.style✕
- Connections
- 1 pair of types, where a type in pueue.client.commands.group uses a type in pueue.client.style.
- The types involved
pueue.client.commands.group.group$module→pueue.client.style.OutputStyle
- Direction
- pueue.client.commands.group uses pueue.client.style, so a change to pueue.client.style can break pueue.client.commands.group, while a change to pueue.client.commands.group can't break pueue.client.style.
- Position
- Below the diagonal: pueue.client.commands.group uses a module listed above it, which is the healthy direction.
34→2 pueue.client.commands.kill uses pueue_lib.message.request✕
- Connections
- 1 pair of types, where a type in pueue.client.commands.kill uses a type in pueue_lib.message.request.
- The types involved
pueue.client.commands.kill.kill$module→pueue_lib.message.request.Signal
- Direction
- pueue.client.commands.kill uses pueue_lib.message.request, so a change to pueue_lib.message.request can break pueue.client.commands.kill, while a change to pueue.client.commands.kill can't break pueue_lib.message.request.
- Position
- Below the diagonal: pueue.client.commands.kill uses a module listed above it, which is the healthy direction.
34→8 pueue.client.commands.kill uses pueue_lib.network.client✕
- Connections
- 1 pair of types, where a type in pueue.client.commands.kill uses a type in pueue_lib.network.client.
- The types involved
pueue.client.commands.kill.kill$module→pueue_lib.network.client.Client
- Direction
- pueue.client.commands.kill uses pueue_lib.network.client, so a change to pueue_lib.network.client can break pueue.client.commands.kill, while a change to pueue.client.commands.kill can't break pueue_lib.network.client.
- Position
- Below the diagonal: pueue.client.commands.kill uses a module listed above it, which is the healthy direction.
34→9 pueue.client.commands.kill uses pueue_lib.settings✕
- Connections
- 1 pair of types, where a type in pueue.client.commands.kill uses a type in pueue_lib.settings.
- The types involved
pueue.client.commands.kill.kill$module→pueue_lib.settings.Settings
- Direction
- pueue.client.commands.kill uses pueue_lib.settings, so a change to pueue_lib.settings can break pueue.client.commands.kill, while a change to pueue.client.commands.kill can't break pueue_lib.settings.
- Position
- Below the diagonal: pueue.client.commands.kill uses a module listed above it, which is the healthy direction.
34→10 pueue.client.commands.kill uses pueue.client.style✕
- Connections
- 1 pair of types, where a type in pueue.client.commands.kill uses a type in pueue.client.style.
- The types involved
pueue.client.commands.kill.kill$module→pueue.client.style.OutputStyle
- Direction
- pueue.client.commands.kill uses pueue.client.style, so a change to pueue.client.style can break pueue.client.commands.kill, while a change to pueue.client.commands.kill can't break pueue.client.style.
- Position
- Below the diagonal: pueue.client.commands.kill uses a module listed above it, which is the healthy direction.
35→3 pueue.client.commands.log uses pueue_lib.task✕
- Connections
- 1 pair of types, where a type in pueue.client.commands.log uses a type in pueue_lib.task.
- The types involved
pueue.client.commands.log.log$module→pueue_lib.task.Task
- Direction
- pueue.client.commands.log uses pueue_lib.task, so a change to pueue_lib.task can break pueue.client.commands.log, while a change to pueue.client.commands.log can't break pueue_lib.task.
- Position
- Below the diagonal: pueue.client.commands.log uses a module listed above it, which is the healthy direction.
35→5 pueue.client.commands.log uses pueue_lib.message.response✕
- Connections
- 1 pair of types, where a type in pueue.client.commands.log uses a type in pueue_lib.message.response.
- The types involved
pueue.client.commands.log.log$module→pueue_lib.message.response.TaskLogResponse
- Direction
- pueue.client.commands.log uses pueue_lib.message.response, so a change to pueue_lib.message.response can break pueue.client.commands.log, while a change to pueue.client.commands.log can't break pueue_lib.message.response.
- Position
- Below the diagonal: pueue.client.commands.log uses a module listed above it, which is the healthy direction.
35→8 pueue.client.commands.log uses pueue_lib.network.client✕
- Connections
- 1 pair of types, where a type in pueue.client.commands.log uses a type in pueue_lib.network.client.
- The types involved
pueue.client.commands.log.log$module→pueue_lib.network.client.Client
- Direction
- pueue.client.commands.log uses pueue_lib.network.client, so a change to pueue_lib.network.client can break pueue.client.commands.log, while a change to pueue.client.commands.log can't break pueue_lib.network.client.
- Position
- Below the diagonal: pueue.client.commands.log uses a module listed above it, which is the healthy direction.
35→9 pueue.client.commands.log uses pueue_lib.settings✕
- Connections
- 1 pair of types, where a type in pueue.client.commands.log uses a type in pueue_lib.settings.
- The types involved
pueue.client.commands.log.log$module→pueue_lib.settings.Settings
- Direction
- pueue.client.commands.log uses pueue_lib.settings, so a change to pueue_lib.settings can break pueue.client.commands.log, while a change to pueue.client.commands.log can't break pueue_lib.settings.
- Position
- Below the diagonal: pueue.client.commands.log uses a module listed above it, which is the healthy direction.
35→10 pueue.client.commands.log uses pueue.client.style✕
- Connections
- 1 pair of types, where a type in pueue.client.commands.log uses a type in pueue.client.style.
- The types involved
pueue.client.commands.log.log$module→pueue.client.style.OutputStyle
- Direction
- pueue.client.commands.log uses pueue.client.style, so a change to pueue.client.style can break pueue.client.commands.log, while a change to pueue.client.commands.log can't break pueue.client.style.
- Position
- Below the diagonal: pueue.client.commands.log uses a module listed above it, which is the healthy direction.
36→8 pueue.client.commands.remove uses pueue_lib.network.client✕
- Connections
- 1 pair of types, where a type in pueue.client.commands.remove uses a type in pueue_lib.network.client.
- The types involved
pueue.client.commands.remove.remove$module→pueue_lib.network.client.Client
- Direction
- pueue.client.commands.remove uses pueue_lib.network.client, so a change to pueue_lib.network.client can break pueue.client.commands.remove, while a change to pueue.client.commands.remove can't break pueue_lib.network.client.
- Position
- Below the diagonal: pueue.client.commands.remove uses a module listed above it, which is the healthy direction.
36→9 pueue.client.commands.remove uses pueue_lib.settings✕
- Connections
- 1 pair of types, where a type in pueue.client.commands.remove uses a type in pueue_lib.settings.
- The types involved
pueue.client.commands.remove.remove$module→pueue_lib.settings.Settings
- Direction
- pueue.client.commands.remove uses pueue_lib.settings, so a change to pueue_lib.settings can break pueue.client.commands.remove, while a change to pueue.client.commands.remove can't break pueue_lib.settings.
- Position
- Below the diagonal: pueue.client.commands.remove uses a module listed above it, which is the healthy direction.
36→10 pueue.client.commands.remove uses pueue.client.style✕
- Connections
- 1 pair of types, where a type in pueue.client.commands.remove uses a type in pueue.client.style.
- The types involved
pueue.client.commands.remove.remove$module→pueue.client.style.OutputStyle
- Direction
- pueue.client.commands.remove uses pueue.client.style, so a change to pueue.client.style can break pueue.client.commands.remove, while a change to pueue.client.commands.remove can't break pueue.client.style.
- Position
- Below the diagonal: pueue.client.commands.remove uses a module listed above it, which is the healthy direction.
37→9 pueue.client.commands.state.table_builder uses pueue_lib.settings✕
- Connections
- 1 pair of types, where a type in pueue.client.commands.state.table_builder uses a type in pueue_lib.settings.
- The types involved
pueue.client.commands.state.table_builder.TableBuilder→pueue_lib.settings.Settings
- Direction
- pueue.client.commands.state.table_builder uses pueue_lib.settings, so a change to pueue_lib.settings can break pueue.client.commands.state.table_builder, while a change to pueue.client.commands.state.table_builder can't break pueue_lib.settings.
- Position
- Below the diagonal: pueue.client.commands.state.table_builder uses a module listed above it, which is the healthy direction.
37→10 pueue.client.commands.state.table_builder uses pueue.client.style✕
- Connections
- 1 pair of types, where a type in pueue.client.commands.state.table_builder uses a type in pueue.client.style.
- The types involved
pueue.client.commands.state.table_builder.TableBuilder→pueue.client.style.OutputStyle
- Direction
- pueue.client.commands.state.table_builder uses pueue.client.style, so a change to pueue.client.style can break pueue.client.commands.state.table_builder, while a change to pueue.client.commands.state.table_builder can't break pueue.client.style.
- Position
- Below the diagonal: pueue.client.commands.state.table_builder uses a module listed above it, which is the healthy direction.
38→2 pueue.client.commands.wait uses pueue_lib.message.request✕
- Connections
- 1 pair of types, where a type in pueue.client.commands.wait uses a type in pueue_lib.message.request.
- The types involved
pueue.client.commands.wait.wait$module→pueue_lib.message.request.TaskSelection
- Direction
- pueue.client.commands.wait uses pueue_lib.message.request, so a change to pueue_lib.message.request can break pueue.client.commands.wait, while a change to pueue.client.commands.wait can't break pueue_lib.message.request.
- Position
- Below the diagonal: pueue.client.commands.wait uses a module listed above it, which is the healthy direction.
38→3 pueue.client.commands.wait uses pueue_lib.task✕
- Connections
- 2 pairs of types, where a type in pueue.client.commands.wait uses a type in pueue_lib.task.
- The types involved
pueue.client.commands.wait.wait$module→pueue_lib.task.Taskpueue.client.commands.wait.wait$module→pueue_lib.task.TaskStatus
- Direction
- pueue.client.commands.wait uses pueue_lib.task, so a change to pueue_lib.task can break pueue.client.commands.wait, while a change to pueue.client.commands.wait can't break pueue_lib.task.
- Position
- Below the diagonal: pueue.client.commands.wait uses a module listed above it, which is the healthy direction.
38→7 pueue.client.commands.wait uses pueue_lib.state✕
- Connections
- 1 pair of types, where a type in pueue.client.commands.wait uses a type in pueue_lib.state.
- The types involved
pueue.client.commands.wait.wait$module→pueue_lib.state.State
- Direction
- pueue.client.commands.wait uses pueue_lib.state, so a change to pueue_lib.state can break pueue.client.commands.wait, while a change to pueue.client.commands.wait can't break pueue_lib.state.
- Position
- Below the diagonal: pueue.client.commands.wait uses a module listed above it, which is the healthy direction.
38→8 pueue.client.commands.wait uses pueue_lib.network.client✕
- Connections
- 1 pair of types, where a type in pueue.client.commands.wait uses a type in pueue_lib.network.client.
- The types involved
pueue.client.commands.wait.wait$module→pueue_lib.network.client.Client
- Direction
- pueue.client.commands.wait uses pueue_lib.network.client, so a change to pueue_lib.network.client can break pueue.client.commands.wait, while a change to pueue.client.commands.wait can't break pueue_lib.network.client.
- Position
- Below the diagonal: pueue.client.commands.wait uses a module listed above it, which is the healthy direction.
38→10 pueue.client.commands.wait uses pueue.client.style✕
- Connections
- 1 pair of types, where a type in pueue.client.commands.wait uses a type in pueue.client.style.
- The types involved
pueue.client.commands.wait.wait$module→pueue.client.style.OutputStyle
- Direction
- pueue.client.commands.wait uses pueue.client.style, so a change to pueue.client.style can break pueue.client.commands.wait, while a change to pueue.client.commands.wait can't break pueue.client.style.
- Position
- Below the diagonal: pueue.client.commands.wait uses a module listed above it, which is the healthy direction.
39→2 pueue.daemon.process_handler uses pueue_lib.message.request✕
- Connections
- 1 pair of types, where a type in pueue.daemon.process_handler uses a type in pueue_lib.message.request.
- The types involved
pueue.daemon.process_handler.process_handler$module→pueue_lib.message.request.ShutdownRequest
- Direction
- pueue.daemon.process_handler uses pueue_lib.message.request, so a change to pueue_lib.message.request can break pueue.daemon.process_handler, while a change to pueue.daemon.process_handler can't break pueue_lib.message.request.
- Position
- Below the diagonal: pueue.daemon.process_handler uses a module listed above it, which is the healthy direction.
39→9 pueue.daemon.process_handler uses pueue_lib.settings✕
- Connections
- 1 pair of types, where a type in pueue.daemon.process_handler uses a type in pueue_lib.settings.
- The types involved
pueue.daemon.process_handler.process_handler$module→pueue_lib.settings.Settings
- Direction
- pueue.daemon.process_handler uses pueue_lib.settings, so a change to pueue_lib.settings can break pueue.daemon.process_handler, while a change to pueue.daemon.process_handler can't break pueue_lib.settings.
- Position
- Below the diagonal: pueue.daemon.process_handler uses a module listed above it, which is the healthy direction.
39→27 pueue.daemon.process_handler uses pueue.process_helper✕
- Connections
- 1 pair of types, where a type in pueue.daemon.process_handler uses a type in pueue.process_helper.
- The types involved
pueue.daemon.process_handler.process_handler$module→pueue.process_helper.ProcessAction
- Direction
- pueue.daemon.process_handler uses pueue.process_helper, so a change to pueue.process_helper can break pueue.daemon.process_handler, while a change to pueue.daemon.process_handler can't break pueue.process_helper.
- Position
- Below the diagonal: pueue.daemon.process_handler uses a module listed above it, which is the healthy direction.
40→3 pueue.client.commands.state uses pueue_lib.task✕
- Connections
- 1 pair of types, where a type in pueue.client.commands.state uses a type in pueue_lib.task.
- The types involved
pueue.client.commands.state.state$module→pueue_lib.task.Task
- Direction
- pueue.client.commands.state uses pueue_lib.task, so a change to pueue_lib.task can break pueue.client.commands.state, while a change to pueue.client.commands.state can't break pueue_lib.task.
- Position
- Below the diagonal: pueue.client.commands.state uses a module listed above it, which is the healthy direction.
40→7 pueue.client.commands.state uses pueue_lib.state✕
- Connections
- 1 pair of types, where a type in pueue.client.commands.state uses a type in pueue_lib.state.
- The types involved
pueue.client.commands.state.state$module→pueue_lib.state.State
- Direction
- pueue.client.commands.state uses pueue_lib.state, so a change to pueue_lib.state can break pueue.client.commands.state, while a change to pueue.client.commands.state can't break pueue_lib.state.
- Position
- Below the diagonal: pueue.client.commands.state uses a module listed above it, which is the healthy direction.
40→8 pueue.client.commands.state uses pueue_lib.network.client✕
- Connections
- 1 pair of types, where a type in pueue.client.commands.state uses a type in pueue_lib.network.client.
- The types involved
pueue.client.commands.state.state$module→pueue_lib.network.client.Client
- Direction
- pueue.client.commands.state uses pueue_lib.network.client, so a change to pueue_lib.network.client can break pueue.client.commands.state, while a change to pueue.client.commands.state can't break pueue_lib.network.client.
- Position
- Below the diagonal: pueue.client.commands.state uses a module listed above it, which is the healthy direction.
40→9 pueue.client.commands.state uses pueue_lib.settings✕
- Connections
- 1 pair of types, where a type in pueue.client.commands.state uses a type in pueue_lib.settings.
- The types involved
pueue.client.commands.state.state$module→pueue_lib.settings.Settings
- Direction
- pueue.client.commands.state uses pueue_lib.settings, so a change to pueue_lib.settings can break pueue.client.commands.state, while a change to pueue.client.commands.state can't break pueue_lib.settings.
- Position
- Below the diagonal: pueue.client.commands.state uses a module listed above it, which is the healthy direction.
40→10 pueue.client.commands.state uses pueue.client.style✕
- Connections
- 1 pair of types, where a type in pueue.client.commands.state uses a type in pueue.client.style.
- The types involved
pueue.client.commands.state.state$module→pueue.client.style.OutputStyle
- Direction
- pueue.client.commands.state uses pueue.client.style, so a change to pueue.client.style can break pueue.client.commands.state, while a change to pueue.client.commands.state can't break pueue.client.style.
- Position
- Below the diagonal: pueue.client.commands.state uses a module listed above it, which is the healthy direction.
40→37 pueue.client.commands.state uses pueue.client.commands.state.table_builder✕
- Connections
- 1 pair of types, where a type in pueue.client.commands.state uses a type in pueue.client.commands.state.table_builder.
- The types involved
pueue.client.commands.state.state$module→pueue.client.commands.state.table_builder.TableBuilder
- Direction
- pueue.client.commands.state uses pueue.client.commands.state.table_builder, so a change to pueue.client.commands.state.table_builder can break pueue.client.commands.state, while a change to pueue.client.commands.state can't break pueue.client.commands.state.table_builder.
- Position
- Below the diagonal: pueue.client.commands.state uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 45 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 12 | Medium |
Roadmap
Top priorities: Resolve the 6 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED; Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED; Resolve the 1 No ADRs found finding(s) in ADR Quality — start with pueue.rs.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 6 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. | +3.9 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED. | +2.8 pts | Low | Static Analysis (SAST) |
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with pueue.rs. | +2.3 pts | Low | ADR Quality |
| Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. | +1.5 pts | Low | Static Analysis (SAST) |
| Resolve the 1 Orphaned knowledge finding(s) in Knowledge Freshness — start with service.rs. | +1.3 pts | Low | Knowledge Freshness |
| Interpolated log message defeats structured logging | +2.3 pts | Medium | Structured logging |
| 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. | +2.3 pts | Medium | Architecture documentation |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +0.6 pts | Low | Supply-chain Provenance & Signing |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 1.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Slop | Static Analysis (SAST): High: REDACTED |
| pueue/src/daemon/network/message_handler/enqueue.rs | 5.6 | Mixed | Cognitive Complexity: pueue::daemon::network::message_handler::enqueue::enqueue (cognitive 16) |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| pueue_lib/src/network/socket/unix.rs | 6.3 | Mixed | Code Duplication: Edited copies of one member (3 members, 30+ corresponding lines) |
| pueue_lib/src/network/client.rs | 6.3 | Mixed | Code Duplication: Edited copy of a member (35 corresponding lines) |
| pueue_lib/src/network/socket/mod.rs | 6.3 | Mixed | Code Duplication: Edited copy of a member (18 corresponding lines) |
| pueue_lib/src/message/request.rs | 7.0 | Mixed | Code Duplication: Edited copy of a member (13 corresponding lines) |
| pueue_lib/src/network_blocking/socket/unix.rs | 7.0 | Mixed | Code Duplication: Duplicated block (26–27 lines × 2) |
| pueue/src/client/commands/clean.rs | 7.0 | Mixed | Code Duplication: Duplicated block (12 lines × 2) |
| pueue_lib/src/network/protocol.rs | 7.1 | Mixed | Code Duplication: Edited copy of a member (60 corresponding lines) |
| pueue/src/client/commands/state/query/filters.rs | 7.2 | Mixed | Cyclomatic Complexity: pueue::client::commands::state::query::filters::datetime (cyclomatic 23) |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| pueue/src/client/commands/state/table_builder.rs | 7.8 | Mixed | Cyclomatic Complexity: TableBuilder::build_task_rows (cyclomatic 23) |
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 43 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 1.0, the weighted average across measured dimensions.
What we checked — 43 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, 172 of 186 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
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (52 contributor(s) across 2039 commit(s) sampled, automation and bot accounts excluded). One of them holds 89% of the history; the other 51 hold 0.2% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D27 Navigability — not measured this run — 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 Python, Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — 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 Python, Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- 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's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- 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.
- 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.
- X4 Structured logging — 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. 30 further occurrence(s) are not listed individually; the score already reflects all 70.
- 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 Python, Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
6 function(s) exceeded the cyclomatic complexity threshold of 15; the worst was TableBuilder::build_task_rows at 23. A further 2 function(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being pueue::client::commands::handle_command at 22 — they are counted neither in the figure above nor in this dimension's score. 2 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold functions was excluded, so the exclusion is disclosed nowhere in the file itself: pueue/src/client/commands/mod.rs (pueue::client::commands::handle_command at 22), pueue/src/daemon/network/message_handler/mod.rs (pueue::daemon::network::message_handler::handle_request at 22). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 6 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with TableBuilder::build_task_rows (cyclomatic 23), pueue::client::commands::state::query::filters::datetime (cyclomatic 23), pueue::daemon::network::message_handler::log::follow_log (cyclomatic 19). — 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 6 together lifts Cyclomatic Complexity from 9.1 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
8 function(s) exceeded the cognitive complexity threshold of 15; the worst was TableBuilder::build_task_rows at 43.
What to do
- Bring the 8 bodies over 15 down to 15 or less in Cognitive Complexity — start with TableBuilder::build_task_rows (cognitive 43), pueue::client::commands::wait::wait (cognitive 38), pueue::daemon::network::message_handler::log::follow_log (cognitive 28). — 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 8 together lifts Cognitive Complexity from 8.3 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
1 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 1 FunctionTooLong finding(s) in God Classes — start with mod.rs. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
17 duplicated block group(s) detected. 6.5 % of the production lines (818 of 12,610) are in a reported copy. A further 14 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 3 Duplicated block (13 lines × 2) finding(s) in Code Duplication — start with enqueue.rs (2), filters.rs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 Near-duplicate member pair (49 shared lines) finding(s) in Code Duplication — start with enqueue.rs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Edited copy of a member (60 corresponding lines) finding(s) in Code Duplication — start with protocol.rs. — One of this dimension's main actionable groups (1 warning-level).
D5 · Coupling
2 production modules (Cargo), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 1 module(s) off the main sequence.
What to do
- Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
D6 · Cohesion (LCOM4)
0 of 12 classes have LCOM4 above 3.
D8 · Code Coverage
Line coverage 73.8% — 25 file(s) below 50%. Measured from the Rust suite (repository root: `cargo test --workspace` instrumented over 96 production file(s), 8 test binaries and 1 doc-test binaries).
What to do
- Resolve the 25 Low coverage finding(s) in Code Coverage — start with send.rs (2), stash.rs (2), tls.rs (2). — One of this dimension's main actionable groups (25 warning-level).
D11 · Test Reliability
0 flaky across 1 measured tier(s). Rust (repository root, 47 test files): measured (0 flaky).
D12 · Dependency Hygiene
6 outdated, 0 yanked direct Cargo dependencies. Only DIRECT edges are graded: a transitive crate cannot be moved past what its parent's requirement admits, so reporting one would be advice its owner cannot take. A newer release is reported only where this repository's OWN requirement already admits it, so the remedy is `cargo update` and never a manifest edit — which means a release outside the declared range is deliberately NOT charged, because a written-down constraint is a decision rather than a defect. Note that a bare requirement is a CARET, and for a 0.x crate its ceiling is the minor. Whether any crate is UNMAINTAINED is not graded — crates.io publishes no maintenance status, and release age does not stand in for one. Known CVEs in this dependency graph are D30's question, read from Cargo.lock there.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 293 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository's Cargo.lock closed over its manifests' `[dependencies]` and `[build-dependencies]`. Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository. This repository publishes itself under MIT OR Apache-2.0, which is its own choice and is not judged here.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
0 deducted task-comment markers across 12610 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 5 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with pueue.rs. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
1 of 2 build units (Cargo) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
45 finding(s): 0 critical, 44 high, 1 medium, 0 low. 37 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 3 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED. — One of this dimension's main actionable groups (4 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 37 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 (37 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
No known-vulnerable dependencies in any ecosystem this repository declares.
D34 · Knowledge Freshness
1 of 60 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is pueue/src/daemon/service.rs. Counted over 60 of the 111 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 1 Orphaned knowledge finding(s) in Knowledge Freshness — start with service.rs. — One of this dimension's main actionable groups (1 issue-level).
D35 · Change Coupling
Strongest change-coupling: certificate.rs↔secret.rs 50%; secret.rs↔settings.rs 50%
What to do
- Resolve the 1 Boundary-crossing change coupling finding(s) in Change Coupling — start with certificate.rs. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Change coupling finding(s) in Change Coupling — start with secret.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 6 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
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.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
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
- `REDACTED` schedules updates, but no `package-ecosystem` entry covers `cargo`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entry to the `updates:` list. — REDACTED:2
What to do
- Dependabot is configured but does not watch `cargo` — add that `package-ecosystem` entry to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
What to do
- Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
P6 · Release Hygiene
PF1 · Benchmark discipline
PF3 · Async & latency hygiene
X1 · Async correctness
X21 · Side-effecting pattern guard
X30 · Support guard that admits what it rejects
X4 · Structured logging
- `error!` at line 54 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — pueue_lib/src/log.rs:54
- `info!` at line 395 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — pueue_lib/src/settings.rs:395
- `info!` at line 399 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — pueue_lib/src/settings.rs:399
- `warn!` at line 104 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — pueue_lib/src/network_blocking/client.rs:104
- `debug!` at line 49 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. (×2) — pueue_lib/src/network_blocking/protocol.rs:49, pueue_lib/src/network/protocol.rs:49
- `error!` at line 111 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — pueue_lib/src/network_blocking/protocol.rs:111
- `warn!` at line 120 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — pueue_lib/src/network_blocking/protocol.rs:120
- `debug!` at line 190 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — pueue_lib/src/network_blocking/protocol.rs:190
- `warn!` at line 111 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — pueue_lib/src/network/client.rs:111
- `error!` at line 113 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — pueue_lib/src/network/protocol.rs:113
- `warn!` at line 122 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — pueue_lib/src/network/protocol.rs:122
- `debug!` at line 195 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — pueue_lib/src/network/protocol.rs:195
- `info!` at line 14 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — pueue/src/aliasing.rs:14
- `info!` at line 41 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — pueue/src/aliasing.rs:41
- `info!` at line 75 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — pueue/src/process_helper/mod.rs:75
- `info!` at line 69 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — pueue/src/process_helper/unix.rs:69
- `info!` at line 100 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — pueue/src/process_helper/windows.rs:100
- `error!` at line 132 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — pueue/src/process_helper/windows.rs:132
- `error!` at line 170 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — pueue/src/process_helper/windows.rs:170
- `warn!` at line 215 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — pueue/src/process_helper/windows.rs:215
- `warn!` at line 236 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — pueue/src/process_helper/windows.rs:236
- `error!` at line 27 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — pueue/src/daemon/callbacks.rs:27
- `error!` at line 38 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — pueue/src/daemon/callbacks.rs:38
- `debug!` at line 44 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — pueue/src/daemon/callbacks.rs:44
- `error!` at line 135 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — pueue/src/daemon/callbacks.rs:135
- `info!` at line 141 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — pueue/src/daemon/callbacks.rs:141
- `warn!` at line 73 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — pueue/src/daemon/mod.rs:73
- `info!` at line 11 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — pueue/src/daemon/pid.rs:11
- `error!` at line 104 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — pueue/src/daemon/service.rs:104
- `error!` at line 285 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — pueue/src/daemon/service.rs:285
- `error!` at line 354 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — pueue/src/daemon/service.rs:354
- `debug!` at line 718 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — pueue/src/daemon/service.rs:718
- `error!` at line 735 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — pueue/src/daemon/service.rs:735
- `info!` at line 134 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — pueue/src/daemon/task_handler.rs:134
- `error!` at line 30 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — pueue/src/daemon/process_handler/finish.rs:30
- `error!` at line 62 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — pueue/src/daemon/process_handler/finish.rs:62
- `info!` at line 96 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — pueue/src/daemon/process_handler/finish.rs:96
- `info!` at line 60 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — pueue/src/daemon/process_handler/kill.rs:60
- `warn!` at line 95 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — pueue/src/daemon/process_handler/kill.rs:95
What to do
- Interpolated log message defeats structured logging
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 68% | Adequate — gated by X4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 88% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 69% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 77% | Strong | Solid. |
| Security | 57% | Adequate — gated by D29, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 89% | Strong | Strongest area. |
Unscored — 2 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 70 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: this repository's Python imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one.
- AX2 Stateful singletons — 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 — ~4316 lines of test source are present (.rs) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (1208 declarations, no unit with a dominant convention).
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed Rust surface was not measured.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .py, .rs, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.rs), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- 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.
- 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 (1 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 5 current-state document(s) make no claim of a kind M4 checks. 1 claim(s) of kinds M4 does not check were not checked (path 1); M4 checks only links and versions and artefact counts.
- P12 CI test-gate honesty — Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the Python, Rust source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage data present for 96 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.
- 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.
- S1 Web-Security Posture — No web surface: 112 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.
- X12 Unreachable branch — X12 reached only 0% of this repository's production lines — rust (12,567 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X16 Unfloored truncation loop — not 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 applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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 applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — no C# was loaded; this repository's Python and Rust were read, and no request in it can be cancelled by a caller — a Python request takes no token: asyncio cancels the task and trio or anyio the scope that made it, from outside the call, and requests, httpx, aiohttp and gRPC take a timeout, not a cancellation; a Rust request takes no token: a future is cancelled by dropping it, from outside the call (select!, a timeout, an aborted task), and reqwest, hyper and tonic take none
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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 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.
- 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.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 46 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Orphaned knowledge pueue/src/daemon/service.rs:1
- Boundary-crossing change coupling: certificate.rs ↔ secret.rs pueue/src/daemon/network/certificate.rs:1
Serious — 83 finding(s)
- Low coverage: pueue/src/client/cli.rs pueue/src/client/cli.rs:1
- Low coverage: pueue/src/client/commands/clean.rs pueue/src/client/commands/clean.rs:1
- Low coverage: pueue/src/client/commands/kill.rs pueue/src/client/commands/kill.rs:1
- Low coverage: pueue/src/client/commands/parallel.rs pueue/src/client/commands/parallel.rs:1
- Low coverage: pueue/src/client/commands/pause.rs pueue/src/client/commands/pause.rs:1
- Low coverage: pueue/src/client/commands/remove.rs pueue/src/client/commands/remove.rs:1
- Low coverage: pueue/src/client/commands/reset.rs pueue/src/client/commands/reset.rs:1
- Low coverage: pueue/src/client/commands/send.rs pueue/src/client/commands/send.rs:1
- Low coverage: pueue/src/client/commands/shutdown.rs pueue/src/client/commands/shutdown.rs:1
- Low coverage: pueue/src/client/commands/start.rs pueue/src/client/commands/start.rs:1
- Low coverage: pueue/src/client/commands/stash.rs pueue/src/client/commands/stash.rs:1
- Low coverage: pueue/src/client/commands/switch.rs pueue/src/client/commands/switch.rs:1
- Low coverage: pueue/src/daemon/network/message_handler/enqueue.rs pueue/src/daemon/network/message_handler/enqueue.rs:1
- Low coverage: pueue/src/daemon/network/message_handler/send.rs pueue/src/daemon/network/message_handler/send.rs:1
- Low coverage: pueue/src/daemon/network/message_handler/stash.rs pueue/src/daemon/network/message_handler/stash.rs:1
- Low coverage: pueue/src/daemon/network/tls.rs pueue/src/daemon/network/tls.rs:1
- Low coverage: pueue/src/daemon/pid.rs pueue/src/daemon/pid.rs:1
- Low coverage: pueue_lib/src/message/request.rs pueue_lib/src/message/request.rs:1
- Low coverage: pueue_lib/src/network/client.rs pueue_lib/src/network/client.rs:1
- Low coverage: pueue_lib/src/network/socket/mod.rs pueue_lib/src/network/socket/mod.rs:1
- Low coverage: pueue_lib/src/network/socket/unix.rs pueue_lib/src/network/socket/unix.rs:1
- Low coverage: pueue_lib/src/network_blocking/client.rs pueue_lib/src/network_blocking/client.rs:1
- Low coverage: pueue_lib/src/network_blocking/socket/mod.rs pueue_lib/src/network_blocking/socket/mod.rs:1
- Low coverage: pueue_lib/src/network_blocking/socket/unix.rs pueue_lib/src/network_blocking/socket/unix.rs:1
- Low coverage: pueue_lib/src/tls.rs pueue_lib/src/tls.rs:1
- pueue::client::commands::wait::wait (cognitive 38) pueue/src/client/commands/wait.rs:46
- pueue::daemon::network::message_handler::log::follow_log (cognitive 28) pueue/src/daemon/network/message_handler/log.rs:62
- pueue::client::commands::follow::follow_local_task_logs (cognitive 24) pueue/src/client/commands/follow.rs:143
- pueue::client::commands::restart::restart (cognitive 24) pueue/src/client/commands/restart.rs:23
- pueue::client::commands::state::query::filters::datetime (cognitive 19) pueue/src/client/commands/state/query/filters.rs:68
- pueue::daemon::network::message_handler::group::group (cognitive 17) pueue/src/daemon/network/message_handler/group.rs:21
- pueue::daemon::network::message_handler::enqueue::enqueue (cognitive 16) pueue/src/daemon/network/message_handler/enqueue.rs:11
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- pueue::client::commands::state::query::filters::datetime (cyclomatic 23) pueue/src/client/commands/state/query/filters.rs:68
- pueue::daemon::network::message_handler::log::follow_log (cyclomatic 19) pueue/src/daemon/network/message_handler/log.rs:62
- pueue::client::commands::restart::restart (cyclomatic 17) pueue/src/client/commands/restart.rs:23
- pueue::client::commands::wait::wait (cyclomatic 16) pueue/src/client/commands/wait.rs:46
- Duplicated block (13 lines × 2) pueue/src/client/commands/state/query/filters.rs:229
- Duplicated block (13 lines × 2) pueue/src/daemon/network/message_handler/enqueue.rs:12
- Duplicated block (13 lines × 2) pueue/src/daemon/network/message_handler/enqueue.rs:26
- TableBuilder::build_task_rows (cyclomatic 23) pueue/src/client/commands/state/table_builder.rs:189
- QueryResult::order_tasks (cyclomatic 18) pueue/src/client/commands/state/query/mod.rs:65
- TableBuilder::build_task_rows (cognitive 43) pueue/src/client/commands/state/table_builder.rs:189
- REDACTED
- FunctionTooLong: pueue::client::commands::handle_command pueue/src/client/commands/mod.rs:153
- Change coupling: secret.rs ↔ settings.rs pueue_lib/src/secret.rs:1
- REDACTED
- REDACTED
- REDACTED
- Near-duplicate member pair (49 shared lines) pueue/src/daemon/network/message_handler/enqueue.rs:11
- Edited copy of a member (60 corresponding lines) pueue_lib/src/network/protocol.rs:100
- Edited copy of a member (30 corresponding lines) pueue/src/daemon/network/message_handler/pause.rs:7
- Edited copy of a member (26 corresponding lines) pueue/src/client/commands/state/query/filters.rs:228
- Edited copies of one member (3 members, 30+ corresponding lines) pueue_lib/src/network/socket/unix.rs:29
- Edited copy of a member (34 corresponding lines) pueue/src/process_helper/windows.rs:126
- Edited copy of a member (35 corresponding lines) pueue_lib/src/network/client.rs:81
- Edited copy of a member (20 corresponding lines) pueue/src/daemon/service.rs:184
- Edited copy of a member (22 corresponding lines) pueue_lib/src/network/protocol.rs:63
- Edited copy of a member (13 corresponding lines) pueue_lib/src/message/request.rs:112
- Edited copy of a member (18 corresponding lines) pueue_lib/src/network/socket/mod.rs:70
- Edited copy of a member (10 corresponding lines) pueue_lib/src/network/protocol.rs:47
- Edited copy of a member (7 corresponding lines) pueue/src/daemon/internal_state/state.rs:163
- Edited copies of one member (3 members, 12+ corresponding lines) pueue/src/client/commands/enqueue.rs:15
- Duplicated block (38–42 lines × 2) pueue_lib/src/network/protocol.rs:106
- Duplicated block (26–27 lines × 2) pueue_lib/src/network_blocking/socket/unix.rs:32
- Duplicated block (21–22 lines × 2) pueue_lib/src/network/socket/unix.rs:40
- Duplicated block (19 lines × 2) pueue_lib/src/network/protocol.rs:180
- Duplicated block (18 lines × 2) pueue_lib/src/network/client.rs:97
- Duplicated block (16 lines × 2) pueue_lib/src/network/socket/mod.rs:72
- Duplicated block (11 lines × 2) pueue/src/client/commands/state/mod.rs:237
- Duplicated block (10–11 lines × 2) pueue/src/daemon/network/message_handler/pause.rs:8
- Duplicated block (10 lines × 2) pueue/src/process_helper/unix.rs:65
- Duplicated block (9 lines × 2) pueue/src/daemon/network/message_handler/enqueue.rs:40
- Duplicated block (6–8 lines × 2) pueue_lib/src/network/protocol.rs:48
- Duplicated block (12 lines × 2) pueue/src/client/commands/clean.rs:14
- Duplicated block (14 lines × 2) pueue/src/daemon/network/message_handler/enqueue.rs:91
- Duplicated block (5 lines × 2) pueue_lib/src/settings.rs:383
- Off the main sequence: pueue-lib
Minor — 51 finding(s)
- Interpolated log message defeats structured logging pueue_lib/src/log.rs:54
- Interpolated log message defeats structured logging pueue_lib/src/settings.rs:395
- Interpolated log message defeats structured logging pueue_lib/src/settings.rs:399
- Interpolated log message defeats structured logging pueue_lib/src/network_blocking/client.rs:104
- Interpolated log message defeats structured logging pueue_lib/src/network_blocking/protocol.rs:49
- Interpolated log message defeats structured logging pueue_lib/src/network_blocking/protocol.rs:111
- Interpolated log message defeats structured logging pueue_lib/src/network_blocking/protocol.rs:120
- Interpolated log message defeats structured logging pueue_lib/src/network_blocking/protocol.rs:190
- Interpolated log message defeats structured logging pueue_lib/src/network/client.rs:111
- Interpolated log message defeats structured logging pueue_lib/src/network/protocol.rs:49
- Interpolated log message defeats structured logging pueue_lib/src/network/protocol.rs:113
- Interpolated log message defeats structured logging pueue_lib/src/network/protocol.rs:122
- Interpolated log message defeats structured logging pueue_lib/src/network/protocol.rs:195
- Interpolated log message defeats structured logging pueue/src/aliasing.rs:14
- Interpolated log message defeats structured logging pueue/src/aliasing.rs:41
- Interpolated log message defeats structured logging pueue/src/process_helper/mod.rs:75
- Interpolated log message defeats structured logging pueue/src/process_helper/unix.rs:69
- Interpolated log message defeats structured logging pueue/src/process_helper/windows.rs:100
- Interpolated log message defeats structured logging pueue/src/process_helper/windows.rs:132
- Interpolated log message defeats structured logging pueue/src/process_helper/windows.rs:170
- Interpolated log message defeats structured logging pueue/src/process_helper/windows.rs:215
- Interpolated log message defeats structured logging pueue/src/process_helper/windows.rs:236
- Interpolated log message defeats structured logging pueue/src/daemon/callbacks.rs:27
- Interpolated log message defeats structured logging pueue/src/daemon/callbacks.rs:38
- Interpolated log message defeats structured logging pueue/src/daemon/callbacks.rs:44
- Duplicated predicate pueue_lib/src/network/client.rs:110
- Duplicated predicate pueue_lib/src/network/protocol.rs:110
- No ADRs found pueue/src/bin/pueue.rs:1
- Projects may be oversized for their cohesion
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- Dependabot does not watch cargo REDACTED:2
- No release approval gate
- Silent fallback default on Err pueue_lib/src/log.rs:119
Minor — 6 finding(s)
- Outdated: flate2
- Outdated: interim
- Outdated: pest
- Outdated: pest_derive
- Outdated: rustls-connector
- Outdated: toml
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-58e0e6dfc6174819a89774dfc05f7c04/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-58e0e6dfc6174819a89774dfc05f7c04/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 . | 45 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy: 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 | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |