Executive summary
tokio-rs/console falls short of our standard for a preview release, in part because we found no access checks on the code's endpoints or handlers. It scores 53 out of 100 and is rated Adequate, and all 53 of its critical findings are security problems in the build pipeline.
Security and Compliance, at 37, is the weakest lens and counts most in the score. The best first step is adding access checks, worth about 12 points. Recording design decisions comes next, worth about 6 points. Raising Security and Compliance to 68 would lift the score to about 65.
Forty-four pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Six secrets can leak from the build pipeline, and two pipeline steps run downloads nobody checks. Pinning each tool to an exact version, limiting each secret to its own step and checking each download against a checksum would close these risks. Passing outside input through environment variables would fix the pipeline step that puts outside input straight into a shell command.
The product code is 11,546 lines, about €13,000 to rebuild.
If Security and Compliance rose from 37 to 68, the lowest score rated Strong, the score would rise from 53 to about 65.
New since the last survey: 4 findings
- Dependency Vulnerabilities · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
Fixed since the last survey: 2 findings
- Supply-chain Provenance & Signing REDACTED
- Supply-chain Provenance & Signing REDACTED
Rebuild cost: about €13,000 · Estimate
| Cost to rebuild | €4,300 to €22,000, for 72 to 228 hours of work, under 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.7 at a score of 53. 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: 11,546 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 console_api.generated.rs.tokio.console.common.field | 2 console_api.generated.rs.tokio.console.common.metadata | 3 console_api.generated.rs.tokio.console.tasks.task_details | 4 console_subscriber.aggregator.shrink | 5 console_subscriber.builder | 6 tokio_console.intern | 7 console_api.generated.rs.tokio.console.common.register_metadata | 8 console_api.generated.rs.tokio.console.resources | 9 console_api.generated.rs.tokio.console.tasks | 10 console_api.generated.rs.tokio.console.instrument | 11 console_api.generated.rs.tokio.console.common | 12 console_api.generated.rs.tokio.console.async_ops | 13 console_api.generated.rs.tokio.console.trace.trace_event | 14 console_subscriber.attribute | 15 console_subscriber.callsites | 16 console_subscriber.stack | 17 tokio_console.state.store | 18 tokio_console.view.styles | 19 console_api.generated.rs.tokio.console.trace | 20 console_subscriber.record | 21 console_subscriber.stats | 22 tokio_console.config | 23 tokio_console.view.help | 24 console_subscriber.aggregator.id_data | 25 tokio_console.state.async_ops | 26 tokio_console.state.histogram | 27 tokio_console.view.table | 28 tokio_console.view.task | 29 tokio_console.warnings | 30 console_subscriber.aggregator | 31 tokio_console.state.resources | 32 tokio_console.state.tasks | 33 tokio_console.view | 34 tokio_console.view.async_ops | 35 tokio_console.view.resource | 36 tokio_console.view.resources | 37 tokio_console.view.tasks | 38 console_subscriber | 39 tokio_console.state | 40 console_subscriber.visitors |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 console_api.generated.rs.tokio.console.common.field | ||||||||||||||||||||||||||||||||||||||||
| 2 console_api.generated.rs.tokio.console.common.metadata | ||||||||||||||||||||||||||||||||||||||||
| 3 console_api.generated.rs.tokio.console.tasks.task_details | ||||||||||||||||||||||||||||||||||||||||
| 4 console_subscriber.aggregator.shrink | ||||||||||||||||||||||||||||||||||||||||
| 5 console_subscriber.builder | ||||||||||||||||||||||||||||||||||||||||
| 6 tokio_console.intern | ||||||||||||||||||||||||||||||||||||||||
| 7 console_api.generated.rs.tokio.console.common.register_metadata | 2 | |||||||||||||||||||||||||||||||||||||||
| 8 console_api.generated.rs.tokio.console.resources | 1 | 6 | ||||||||||||||||||||||||||||||||||||||
| 9 console_api.generated.rs.tokio.console.tasks | 1 | 7 | ||||||||||||||||||||||||||||||||||||||
| 10 console_api.generated.rs.tokio.console.instrument | 1 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 11 console_api.generated.rs.tokio.console.common | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 12 console_api.generated.rs.tokio.console.async_ops | 5 | |||||||||||||||||||||||||||||||||||||||
| 13 console_api.generated.rs.tokio.console.trace.trace_event | 3 | |||||||||||||||||||||||||||||||||||||||
| 14 console_subscriber.attribute | 1 | 2 | 4 | |||||||||||||||||||||||||||||||||||||
| 15 console_subscriber.callsites | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 console_subscriber.stack | 2 | |||||||||||||||||||||||||||||||||||||||
| 17 tokio_console.state.store | 4 | 1 | ||||||||||||||||||||||||||||||||||||||
| 18 tokio_console.view.styles | 1 | 3 | ||||||||||||||||||||||||||||||||||||||
| 19 console_api.generated.rs.tokio.console.trace | 1 | |||||||||||||||||||||||||||||||||||||||
| 20 console_subscriber.record | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 21 console_subscriber.stats | 1 | 2 | 1 | 4 | 1 | 5 | ||||||||||||||||||||||||||||||||||
| 22 tokio_console.config | 2 | |||||||||||||||||||||||||||||||||||||||
| 23 tokio_console.view.help | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 24 console_subscriber.aggregator.id_data | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 25 tokio_console.state.async_ops | 4 | 4 | 2 | 3 | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 26 tokio_console.state.histogram | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 27 tokio_console.view.table | 2 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 28 tokio_console.view.task | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 29 tokio_console.warnings | 5 | 1 | ||||||||||||||||||||||||||||||||||||||
| 30 console_subscriber.aggregator | 1 | 2 | 1 | 1 | 2 | 1 | 1 | 9 | 1 | 2 | 1 | 7 | 2 | 5 | ||||||||||||||||||||||||||
| 31 tokio_console.state.resources | 1 | 4 | 1 | 5 | 1 | 2 | 3 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||
| 32 tokio_console.state.tasks | 2 | 2 | 6 | 1 | 2 | 2 | 1 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||
| 33 tokio_console.view | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 34 tokio_console.view.async_ops | 1 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 35 tokio_console.view.resource | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 36 tokio_console.view.resources | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 37 tokio_console.view.tasks | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 38 console_subscriber | 2 | 3 | 1 | 1 | 1 | 1 | 1 | 2 | 3 | |||||||||||||||||||||||||||||||
| 39 tokio_console.state | 1 | 5 | 1 | 4 | 7 | 3 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||
| 40 console_subscriber.visitors | 2 | 1 | 12 | 1 | 1 |
7→11 console_api.generated.rs.tokio.console.common.register_metadata uses console_api.generated.rs.tokio.console.common part of a loop✕
- Connections
- 2 pairs of types, where a type in console_api.generated.rs.tokio.console.common.register_metadata uses a type in console_api.generated.rs.tokio.console.common.
- The types involved
console_api.generated.rs.tokio.console.common.register_metadata.NewMetadata→console_api.generated.rs.tokio.console.common.MetaIdconsole_api.generated.rs.tokio.console.common.register_metadata.NewMetadata→console_api.generated.rs.tokio.console.common.Metadata
- Direction
- console_api.generated.rs.tokio.console.common.register_metadata uses console_api.generated.rs.tokio.console.common, so a change to console_api.generated.rs.tokio.console.common can break console_api.generated.rs.tokio.console.common.register_metadata, while a change to console_api.generated.rs.tokio.console.common.register_metadata can't break console_api.generated.rs.tokio.console.common.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→2 console_api.generated.rs.tokio.console.resources uses console_api.generated.rs.tokio.console.common.metadata✕
- Connections
- 1 pair of types, where a type in console_api.generated.rs.tokio.console.resources uses a type in console_api.generated.rs.tokio.console.common.metadata.
- The types involved
console_api.generated.rs.tokio.console.resources.Resource→console_api.generated.rs.tokio.console.common.metadata.Kind
- Direction
- console_api.generated.rs.tokio.console.resources uses console_api.generated.rs.tokio.console.common.metadata, so a change to console_api.generated.rs.tokio.console.common.metadata can break console_api.generated.rs.tokio.console.resources, while a change to console_api.generated.rs.tokio.console.resources can't break console_api.generated.rs.tokio.console.common.metadata.
- Position
- Below the diagonal: console_api.generated.rs.tokio.console.resources uses a module listed above it, which is the healthy direction.
8→11 console_api.generated.rs.tokio.console.resources uses console_api.generated.rs.tokio.console.common part of a loop✕
- Connections
- 6 pairs of types, where a type in console_api.generated.rs.tokio.console.resources uses a type in console_api.generated.rs.tokio.console.common.
- The types involved
console_api.generated.rs.tokio.console.resources.PollOp→console_api.generated.rs.tokio.console.common.Idconsole_api.generated.rs.tokio.console.resources.PollOp→console_api.generated.rs.tokio.console.common.MetaIdconsole_api.generated.rs.tokio.console.resources.Resource→console_api.generated.rs.tokio.console.common.Idconsole_api.generated.rs.tokio.console.resources.Resource→console_api.generated.rs.tokio.console.common.Locationconsole_api.generated.rs.tokio.console.resources.Resource→console_api.generated.rs.tokio.console.common.MetaIdconsole_api.generated.rs.tokio.console.resources.Stats→console_api.generated.rs.tokio.console.common.Attribute
- Direction
- console_api.generated.rs.tokio.console.resources uses console_api.generated.rs.tokio.console.common, so a change to console_api.generated.rs.tokio.console.common can break console_api.generated.rs.tokio.console.resources, while a change to console_api.generated.rs.tokio.console.resources can't break console_api.generated.rs.tokio.console.common.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→3 console_api.generated.rs.tokio.console.tasks uses console_api.generated.rs.tokio.console.tasks.task_details✕
- Connections
- 1 pair of types, where a type in console_api.generated.rs.tokio.console.tasks uses a type in console_api.generated.rs.tokio.console.tasks.task_details.
- The types involved
console_api.generated.rs.tokio.console.tasks.TaskDetails→console_api.generated.rs.tokio.console.tasks.task_details.PollTimesHistogram
- Direction
- console_api.generated.rs.tokio.console.tasks uses console_api.generated.rs.tokio.console.tasks.task_details, so a change to console_api.generated.rs.tokio.console.tasks.task_details can break console_api.generated.rs.tokio.console.tasks, while a change to console_api.generated.rs.tokio.console.tasks can't break console_api.generated.rs.tokio.console.tasks.task_details.
- Position
- Below the diagonal: console_api.generated.rs.tokio.console.tasks uses a module listed above it, which is the healthy direction.
9→11 console_api.generated.rs.tokio.console.tasks uses console_api.generated.rs.tokio.console.common part of a loop✕
- Connections
- 7 pairs of types, where a type in console_api.generated.rs.tokio.console.tasks uses a type in console_api.generated.rs.tokio.console.common.
- The types involved
console_api.generated.rs.tokio.console.tasks.Stats→console_api.generated.rs.tokio.console.common.PollStatsconsole_api.generated.rs.tokio.console.tasks.Task→console_api.generated.rs.tokio.console.common.Fieldconsole_api.generated.rs.tokio.console.tasks.Task→console_api.generated.rs.tokio.console.common.Idconsole_api.generated.rs.tokio.console.tasks.Task→console_api.generated.rs.tokio.console.common.Locationconsole_api.generated.rs.tokio.console.tasks.Task→console_api.generated.rs.tokio.console.common.MetaIdconsole_api.generated.rs.tokio.console.tasks.Task→console_api.generated.rs.tokio.console.common.SpanIdconsole_api.generated.rs.tokio.console.tasks.TaskDetails→console_api.generated.rs.tokio.console.common.Id
- Direction
- console_api.generated.rs.tokio.console.tasks uses console_api.generated.rs.tokio.console.common, so a change to console_api.generated.rs.tokio.console.common can break console_api.generated.rs.tokio.console.tasks, while a change to console_api.generated.rs.tokio.console.tasks can't break console_api.generated.rs.tokio.console.common.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→8 console_api.generated.rs.tokio.console.instrument uses console_api.generated.rs.tokio.console.resources✕
- Connections
- 1 pair of types, where a type in console_api.generated.rs.tokio.console.instrument uses a type in console_api.generated.rs.tokio.console.resources.
- The types involved
console_api.generated.rs.tokio.console.instrument.Update→console_api.generated.rs.tokio.console.resources.ResourceUpdate
- Direction
- console_api.generated.rs.tokio.console.instrument uses console_api.generated.rs.tokio.console.resources, so a change to console_api.generated.rs.tokio.console.resources can break console_api.generated.rs.tokio.console.instrument, while a change to console_api.generated.rs.tokio.console.instrument can't break console_api.generated.rs.tokio.console.resources.
- Position
- Below the diagonal: console_api.generated.rs.tokio.console.instrument uses a module listed above it, which is the healthy direction.
10→9 console_api.generated.rs.tokio.console.instrument uses console_api.generated.rs.tokio.console.tasks✕
- Connections
- 1 pair of types, where a type in console_api.generated.rs.tokio.console.instrument uses a type in console_api.generated.rs.tokio.console.tasks.
- The types involved
console_api.generated.rs.tokio.console.instrument.Update→console_api.generated.rs.tokio.console.tasks.TaskUpdate
- Direction
- console_api.generated.rs.tokio.console.instrument uses console_api.generated.rs.tokio.console.tasks, so a change to console_api.generated.rs.tokio.console.tasks can break console_api.generated.rs.tokio.console.instrument, while a change to console_api.generated.rs.tokio.console.instrument can't break console_api.generated.rs.tokio.console.tasks.
- Position
- Below the diagonal: console_api.generated.rs.tokio.console.instrument uses a module listed above it, which is the healthy direction.
10→11 console_api.generated.rs.tokio.console.instrument uses console_api.generated.rs.tokio.console.common part of a loop✕
- Connections
- 2 pairs of types, where a type in console_api.generated.rs.tokio.console.instrument uses a type in console_api.generated.rs.tokio.console.common.
- The types involved
console_api.generated.rs.tokio.console.instrument.TaskDetailsRequest→console_api.generated.rs.tokio.console.common.Idconsole_api.generated.rs.tokio.console.instrument.Update→console_api.generated.rs.tokio.console.common.RegisterMetadata
- Direction
- console_api.generated.rs.tokio.console.instrument uses console_api.generated.rs.tokio.console.common, so a change to console_api.generated.rs.tokio.console.common can break console_api.generated.rs.tokio.console.instrument, while a change to console_api.generated.rs.tokio.console.instrument can't break console_api.generated.rs.tokio.console.common.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→12 console_api.generated.rs.tokio.console.instrument uses console_api.generated.rs.tokio.console.async_ops part of a loop✕
- Connections
- 1 pair of types, where a type in console_api.generated.rs.tokio.console.instrument uses a type in console_api.generated.rs.tokio.console.async_ops.
- The types involved
console_api.generated.rs.tokio.console.instrument.Update→console_api.generated.rs.tokio.console.async_ops.AsyncOpUpdate
- Direction
- console_api.generated.rs.tokio.console.instrument uses console_api.generated.rs.tokio.console.async_ops, so a change to console_api.generated.rs.tokio.console.async_ops can break console_api.generated.rs.tokio.console.instrument, while a change to console_api.generated.rs.tokio.console.instrument can't break console_api.generated.rs.tokio.console.async_ops.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→1 console_api.generated.rs.tokio.console.common uses console_api.generated.rs.tokio.console.common.field✕
- Connections
- 2 pairs of types, where a type in console_api.generated.rs.tokio.console.common uses a type in console_api.generated.rs.tokio.console.common.field.
- The types involved
console_api.generated.rs.tokio.console.common.Field→console_api.generated.rs.tokio.console.common.field.Nameconsole_api.generated.rs.tokio.console.common.Field→console_api.generated.rs.tokio.console.common.field.Value
- Direction
- console_api.generated.rs.tokio.console.common uses console_api.generated.rs.tokio.console.common.field, so a change to console_api.generated.rs.tokio.console.common.field can break console_api.generated.rs.tokio.console.common, while a change to console_api.generated.rs.tokio.console.common can't break console_api.generated.rs.tokio.console.common.field.
- Position
- Below the diagonal: console_api.generated.rs.tokio.console.common uses a module listed above it, which is the healthy direction.
11→7 console_api.generated.rs.tokio.console.common uses console_api.generated.rs.tokio.console.common.register_metadata✕
- Connections
- 1 pair of types, where a type in console_api.generated.rs.tokio.console.common uses a type in console_api.generated.rs.tokio.console.common.register_metadata.
- The types involved
console_api.generated.rs.tokio.console.common.RegisterMetadata→console_api.generated.rs.tokio.console.common.register_metadata.NewMetadata
- Direction
- console_api.generated.rs.tokio.console.common uses console_api.generated.rs.tokio.console.common.register_metadata, so a change to console_api.generated.rs.tokio.console.common.register_metadata can break console_api.generated.rs.tokio.console.common, while a change to console_api.generated.rs.tokio.console.common can't break console_api.generated.rs.tokio.console.common.register_metadata.
- Position
- Below the diagonal: console_api.generated.rs.tokio.console.common uses a module listed above it, which is the healthy direction.
11→10 console_api.generated.rs.tokio.console.common uses console_api.generated.rs.tokio.console.instrument✕
- Connections
- 1 pair of types, where a type in console_api.generated.rs.tokio.console.common uses a type in console_api.generated.rs.tokio.console.instrument.
- The types involved
console_api.generated.rs.tokio.console.common.Attribute→console_api.generated.rs.tokio.console.instrument.Update
- Direction
- console_api.generated.rs.tokio.console.common uses console_api.generated.rs.tokio.console.instrument, so a change to console_api.generated.rs.tokio.console.instrument can break console_api.generated.rs.tokio.console.common, while a change to console_api.generated.rs.tokio.console.common can't break console_api.generated.rs.tokio.console.instrument.
- Position
- Below the diagonal: console_api.generated.rs.tokio.console.common uses a module listed above it, which is the healthy direction.
12→11 console_api.generated.rs.tokio.console.async_ops uses console_api.generated.rs.tokio.console.common✕
- Connections
- 5 pairs of types, where a type in console_api.generated.rs.tokio.console.async_ops uses a type in console_api.generated.rs.tokio.console.common.
- The types involved
console_api.generated.rs.tokio.console.async_ops.AsyncOp→console_api.generated.rs.tokio.console.common.Idconsole_api.generated.rs.tokio.console.async_ops.AsyncOp→console_api.generated.rs.tokio.console.common.MetaIdconsole_api.generated.rs.tokio.console.async_ops.Stats→console_api.generated.rs.tokio.console.common.Attributeconsole_api.generated.rs.tokio.console.async_ops.Stats→console_api.generated.rs.tokio.console.common.Idconsole_api.generated.rs.tokio.console.async_ops.Stats→console_api.generated.rs.tokio.console.common.PollStats
- Direction
- console_api.generated.rs.tokio.console.async_ops uses console_api.generated.rs.tokio.console.common, so a change to console_api.generated.rs.tokio.console.common can break console_api.generated.rs.tokio.console.async_ops, while a change to console_api.generated.rs.tokio.console.async_ops can't break console_api.generated.rs.tokio.console.common.
- Position
- Below the diagonal: console_api.generated.rs.tokio.console.async_ops uses a module listed above it, which is the healthy direction.
13→11 console_api.generated.rs.tokio.console.trace.trace_event uses console_api.generated.rs.tokio.console.common✕
- Connections
- 3 pairs of types, where a type in console_api.generated.rs.tokio.console.trace.trace_event uses a type in console_api.generated.rs.tokio.console.common.
- The types involved
console_api.generated.rs.tokio.console.trace.trace_event.Close→console_api.generated.rs.tokio.console.common.SpanIdconsole_api.generated.rs.tokio.console.trace.trace_event.Enter→console_api.generated.rs.tokio.console.common.SpanIdconsole_api.generated.rs.tokio.console.trace.trace_event.Exit→console_api.generated.rs.tokio.console.common.SpanId
- Direction
- console_api.generated.rs.tokio.console.trace.trace_event uses console_api.generated.rs.tokio.console.common, so a change to console_api.generated.rs.tokio.console.common can break console_api.generated.rs.tokio.console.trace.trace_event, while a change to console_api.generated.rs.tokio.console.trace.trace_event can't break console_api.generated.rs.tokio.console.common.
- Position
- Below the diagonal: console_api.generated.rs.tokio.console.trace.trace_event uses a module listed above it, which is the healthy direction.
14→1 console_subscriber.attribute uses console_api.generated.rs.tokio.console.common.field✕
- Connections
- 1 pair of types, where a type in console_subscriber.attribute uses a type in console_api.generated.rs.tokio.console.common.field.
- The types involved
console_subscriber.attribute.FieldKey→console_api.generated.rs.tokio.console.common.field.Name
- Direction
- console_subscriber.attribute uses console_api.generated.rs.tokio.console.common.field, so a change to console_api.generated.rs.tokio.console.common.field can break console_subscriber.attribute, while a change to console_subscriber.attribute can't break console_api.generated.rs.tokio.console.common.field.
- Position
- Below the diagonal: console_subscriber.attribute uses a module listed above it, which is the healthy direction.
14→10 console_subscriber.attribute uses console_api.generated.rs.tokio.console.instrument✕
- Connections
- 2 pairs of types, where a type in console_subscriber.attribute uses a type in console_api.generated.rs.tokio.console.instrument.
- The types involved
console_subscriber.attribute.Attributes→console_api.generated.rs.tokio.console.instrument.Updateconsole_subscriber.attribute.attribute$module→console_api.generated.rs.tokio.console.instrument.Update
- Direction
- console_subscriber.attribute uses console_api.generated.rs.tokio.console.instrument, so a change to console_api.generated.rs.tokio.console.instrument can break console_subscriber.attribute, while a change to console_subscriber.attribute can't break console_api.generated.rs.tokio.console.instrument.
- Position
- Below the diagonal: console_subscriber.attribute uses a module listed above it, which is the healthy direction.
14→11 console_subscriber.attribute uses console_api.generated.rs.tokio.console.common✕
- Connections
- 4 pairs of types, where a type in console_subscriber.attribute uses a type in console_api.generated.rs.tokio.console.common.
- The types involved
console_subscriber.attribute.Attributes→console_api.generated.rs.tokio.console.common.Idconsole_subscriber.attribute.FieldKey→console_api.generated.rs.tokio.console.common.Idconsole_subscriber.attribute.Update→console_api.generated.rs.tokio.console.common.Fieldconsole_subscriber.attribute.attribute$module→console_api.generated.rs.tokio.console.common.Attribute
- Direction
- console_subscriber.attribute uses console_api.generated.rs.tokio.console.common, so a change to console_api.generated.rs.tokio.console.common can break console_subscriber.attribute, while a change to console_subscriber.attribute can't break console_api.generated.rs.tokio.console.common.
- Position
- Below the diagonal: console_subscriber.attribute uses a module listed above it, which is the healthy direction.
15→11 console_subscriber.callsites uses console_api.generated.rs.tokio.console.common✕
- Connections
- 1 pair of types, where a type in console_subscriber.callsites uses a type in console_api.generated.rs.tokio.console.common.
- The types involved
console_subscriber.callsites.Callsites→console_api.generated.rs.tokio.console.common.Metadata
- Direction
- console_subscriber.callsites uses console_api.generated.rs.tokio.console.common, so a change to console_api.generated.rs.tokio.console.common can break console_subscriber.callsites, while a change to console_subscriber.callsites can't break console_api.generated.rs.tokio.console.common.
- Position
- Below the diagonal: console_subscriber.callsites uses a module listed above it, which is the healthy direction.
16→11 console_subscriber.stack uses console_api.generated.rs.tokio.console.common✕
- Connections
- 2 pairs of types, where a type in console_subscriber.stack uses a type in console_api.generated.rs.tokio.console.common.
- The types involved
console_subscriber.stack.ContextId→console_api.generated.rs.tokio.console.common.Idconsole_subscriber.stack.SpanStack→console_api.generated.rs.tokio.console.common.Id
- Direction
- console_subscriber.stack uses console_api.generated.rs.tokio.console.common, so a change to console_api.generated.rs.tokio.console.common can break console_subscriber.stack, while a change to console_subscriber.stack can't break console_api.generated.rs.tokio.console.common.
- Position
- Below the diagonal: console_subscriber.stack uses a module listed above it, which is the healthy direction.
17→11 tokio_console.state.store uses console_api.generated.rs.tokio.console.common✕
- Connections
- 4 pairs of types, where a type in tokio_console.state.store uses a type in console_api.generated.rs.tokio.console.common.
- The types involved
tokio_console.state.store.Ids→console_api.generated.rs.tokio.console.common.Idtokio_console.state.store.Ids→console_api.generated.rs.tokio.console.common.SpanIdtokio_console.state.store.Store→console_api.generated.rs.tokio.console.common.Idtokio_console.state.store.Store→console_api.generated.rs.tokio.console.common.SpanId
- Direction
- tokio_console.state.store uses console_api.generated.rs.tokio.console.common, so a change to console_api.generated.rs.tokio.console.common can break tokio_console.state.store, while a change to tokio_console.state.store can't break console_api.generated.rs.tokio.console.common.
- Position
- Below the diagonal: tokio_console.state.store uses a module listed above it, which is the healthy direction.
17→39 tokio_console.state.store uses tokio_console.state part of a loop✕
- Connections
- 1 pair of types, where a type in tokio_console.state.store uses a type in tokio_console.state.
- The types involved
tokio_console.state.store.Store→tokio_console.state.Visibility
- Direction
- tokio_console.state.store uses tokio_console.state, so a change to tokio_console.state can break tokio_console.state.store, while a change to tokio_console.state.store can't break tokio_console.state.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→11 tokio_console.view.styles uses console_api.generated.rs.tokio.console.common✕
- Connections
- 1 pair of types, where a type in tokio_console.view.styles uses a type in console_api.generated.rs.tokio.console.common.
- The types involved
tokio_console.view.styles.Styles→console_api.generated.rs.tokio.console.common.Span
- Direction
- tokio_console.view.styles uses console_api.generated.rs.tokio.console.common, so a change to console_api.generated.rs.tokio.console.common can break tokio_console.view.styles, while a change to tokio_console.view.styles can't break console_api.generated.rs.tokio.console.common.
- Position
- Below the diagonal: tokio_console.view.styles uses a module listed above it, which is the healthy direction.
18→22 tokio_console.view.styles uses tokio_console.config part of a loop✕
- Connections
- 3 pairs of types, where a type in tokio_console.view.styles uses a type in tokio_console.config.
- The types involved
tokio_console.view.styles.Styles→tokio_console.config.ColorTogglestokio_console.view.styles.Styles→tokio_console.config.Configtokio_console.view.styles.Styles→tokio_console.config.ViewOptions
- Direction
- tokio_console.view.styles uses tokio_console.config, so a change to tokio_console.config can break tokio_console.view.styles, while a change to tokio_console.view.styles can't break tokio_console.config.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→13 console_api.generated.rs.tokio.console.trace uses console_api.generated.rs.tokio.console.trace.trace_event✕
- Connections
- 1 pair of types, where a type in console_api.generated.rs.tokio.console.trace uses a type in console_api.generated.rs.tokio.console.trace.trace_event.
- The types involved
console_api.generated.rs.tokio.console.trace.TraceEvent→console_api.generated.rs.tokio.console.trace.trace_event.Event
- Direction
- console_api.generated.rs.tokio.console.trace uses console_api.generated.rs.tokio.console.trace.trace_event, so a change to console_api.generated.rs.tokio.console.trace.trace_event can break console_api.generated.rs.tokio.console.trace, while a change to console_api.generated.rs.tokio.console.trace can't break console_api.generated.rs.tokio.console.trace.trace_event.
- Position
- Below the diagonal: console_api.generated.rs.tokio.console.trace uses a module listed above it, which is the healthy direction.
20→11 console_subscriber.record uses console_api.generated.rs.tokio.console.common✕
- Connections
- 2 pairs of types, where a type in console_subscriber.record uses a type in console_api.generated.rs.tokio.console.common.
- The types involved
console_subscriber.record.SerializeField→console_api.generated.rs.tokio.console.common.Fieldconsole_subscriber.record.SerializeFields→console_api.generated.rs.tokio.console.common.Field
- Direction
- console_subscriber.record uses console_api.generated.rs.tokio.console.common, so a change to console_api.generated.rs.tokio.console.common can break console_subscriber.record, while a change to console_subscriber.record can't break console_api.generated.rs.tokio.console.common.
- Position
- Below the diagonal: console_subscriber.record uses a module listed above it, which is the healthy direction.
20→13 console_subscriber.record uses console_api.generated.rs.tokio.console.trace.trace_event✕
- Connections
- 1 pair of types, where a type in console_subscriber.record uses a type in console_api.generated.rs.tokio.console.trace.trace_event.
- The types involved
console_subscriber.record.Recorder→console_api.generated.rs.tokio.console.trace.trace_event.Event
- Direction
- console_subscriber.record uses console_api.generated.rs.tokio.console.trace.trace_event, so a change to console_api.generated.rs.tokio.console.trace.trace_event can break console_subscriber.record, while a change to console_subscriber.record can't break console_api.generated.rs.tokio.console.trace.trace_event.
- Position
- Below the diagonal: console_subscriber.record uses a module listed above it, which is the healthy direction.
21→3 console_subscriber.stats uses console_api.generated.rs.tokio.console.tasks.task_details✕
- Connections
- 1 pair of types, where a type in console_subscriber.stats uses a type in console_api.generated.rs.tokio.console.tasks.task_details.
- The types involved
console_subscriber.stats.TaskStats→console_api.generated.rs.tokio.console.tasks.task_details.PollTimesHistogram
- Direction
- console_subscriber.stats uses console_api.generated.rs.tokio.console.tasks.task_details, so a change to console_api.generated.rs.tokio.console.tasks.task_details can break console_subscriber.stats, while a change to console_subscriber.stats can't break console_api.generated.rs.tokio.console.tasks.task_details.
- Position
- Below the diagonal: console_subscriber.stats uses a module listed above it, which is the healthy direction.
21→9 console_subscriber.stats uses console_api.generated.rs.tokio.console.tasks✕
- Connections
- 2 pairs of types, where a type in console_subscriber.stats uses a type in console_api.generated.rs.tokio.console.tasks.
- The types involved
console_subscriber.stats.Histogram→console_api.generated.rs.tokio.console.tasks.DurationHistogramconsole_subscriber.stats.TaskStats→console_api.generated.rs.tokio.console.tasks.DurationHistogram
- Direction
- console_subscriber.stats uses console_api.generated.rs.tokio.console.tasks, so a change to console_api.generated.rs.tokio.console.tasks can break console_subscriber.stats, while a change to console_subscriber.stats can't break console_api.generated.rs.tokio.console.tasks.
- Position
- Below the diagonal: console_subscriber.stats uses a module listed above it, which is the healthy direction.
21→10 console_subscriber.stats uses console_api.generated.rs.tokio.console.instrument✕
- Connections
- 1 pair of types, where a type in console_subscriber.stats uses a type in console_api.generated.rs.tokio.console.instrument.
- The types involved
console_subscriber.stats.ResourceStats→console_api.generated.rs.tokio.console.instrument.Update
- Direction
- console_subscriber.stats uses console_api.generated.rs.tokio.console.instrument, so a change to console_api.generated.rs.tokio.console.instrument can break console_subscriber.stats, while a change to console_subscriber.stats can't break console_api.generated.rs.tokio.console.instrument.
- Position
- Below the diagonal: console_subscriber.stats uses a module listed above it, which is the healthy direction.
21→11 console_subscriber.stats uses console_api.generated.rs.tokio.console.common✕
- Connections
- 4 pairs of types, where a type in console_subscriber.stats uses a type in console_api.generated.rs.tokio.console.common.
- The types involved
console_subscriber.stats.AsyncOpStats→console_api.generated.rs.tokio.console.common.Idconsole_subscriber.stats.AsyncOpStats→console_api.generated.rs.tokio.console.common.PollStatsconsole_subscriber.stats.ResourceStats→console_api.generated.rs.tokio.console.common.Idconsole_subscriber.stats.TaskStats→console_api.generated.rs.tokio.console.common.PollStats
- Direction
- console_subscriber.stats uses console_api.generated.rs.tokio.console.common, so a change to console_api.generated.rs.tokio.console.common can break console_subscriber.stats, while a change to console_subscriber.stats can't break console_api.generated.rs.tokio.console.common.
- Position
- Below the diagonal: console_subscriber.stats uses a module listed above it, which is the healthy direction.
21→14 console_subscriber.stats uses console_subscriber.attribute✕
- Connections
- 1 pair of types, where a type in console_subscriber.stats uses a type in console_subscriber.attribute.
- The types involved
console_subscriber.stats.ResourceStats→console_subscriber.attribute.Attributes
- Direction
- console_subscriber.stats uses console_subscriber.attribute, so a change to console_subscriber.attribute can break console_subscriber.stats, while a change to console_subscriber.stats can't break console_subscriber.attribute.
- Position
- Below the diagonal: console_subscriber.stats uses a module listed above it, which is the healthy direction.
21→38 console_subscriber.stats uses console_subscriber part of a loop✕
- Connections
- 5 pairs of types, where a type in console_subscriber.stats uses a type in console_subscriber.
- The types involved
console_subscriber.stats.AsyncOpStats→console_subscriber.ToProtoconsole_subscriber.stats.PollStats→console_subscriber.ToProtoconsole_subscriber.stats.ResourceStats→console_subscriber.ToProtoconsole_subscriber.stats.TaskStats→console_subscriber.ToProtoconsole_subscriber.stats.TaskStats→console_subscriber.WakeOp
- Direction
- console_subscriber.stats uses console_subscriber, so a change to console_subscriber can break console_subscriber.stats, while a change to console_subscriber.stats can't break console_subscriber.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
22→18 tokio_console.config uses tokio_console.view.styles✕
- Connections
- 2 pairs of types, where a type in tokio_console.config uses a type in tokio_console.view.styles.
- The types involved
tokio_console.config.ColorsConfig→tokio_console.view.styles.Palettetokio_console.config.ViewOptions→tokio_console.view.styles.Palette
- Direction
- tokio_console.config uses tokio_console.view.styles, so a change to tokio_console.view.styles can break tokio_console.config, while a change to tokio_console.config can't break tokio_console.view.styles.
- Position
- Below the diagonal: tokio_console.config uses a module listed above it, which is the healthy direction.
23→10 tokio_console.view.help uses console_api.generated.rs.tokio.console.instrument✕
- Connections
- 1 pair of types, where a type in tokio_console.view.help uses a type in console_api.generated.rs.tokio.console.instrument.
- The types involved
tokio_console.view.help.HelpView→console_api.generated.rs.tokio.console.instrument.State
- Direction
- tokio_console.view.help uses console_api.generated.rs.tokio.console.instrument, so a change to console_api.generated.rs.tokio.console.instrument can break tokio_console.view.help, while a change to tokio_console.view.help can't break console_api.generated.rs.tokio.console.instrument.
- Position
- Below the diagonal: tokio_console.view.help uses a module listed above it, which is the healthy direction.
23→18 tokio_console.view.help uses tokio_console.view.styles✕
- Connections
- 2 pairs of types, where a type in tokio_console.view.help uses a type in tokio_console.view.styles.
- The types involved
tokio_console.view.help.HelpText→tokio_console.view.styles.Stylestokio_console.view.help.HelpView→tokio_console.view.styles.Styles
- Direction
- tokio_console.view.help uses tokio_console.view.styles, so a change to tokio_console.view.styles can break tokio_console.view.help, while a change to tokio_console.view.help can't break tokio_console.view.styles.
- Position
- Below the diagonal: tokio_console.view.help uses a module listed above it, which is the healthy direction.
24→4 console_subscriber.aggregator.id_data uses console_subscriber.aggregator.shrink✕
- Connections
- 1 pair of types, where a type in console_subscriber.aggregator.id_data uses a type in console_subscriber.aggregator.shrink.
- The types involved
console_subscriber.aggregator.id_data.IdData→console_subscriber.aggregator.shrink.ShrinkMap
- Direction
- console_subscriber.aggregator.id_data uses console_subscriber.aggregator.shrink, so a change to console_subscriber.aggregator.shrink can break console_subscriber.aggregator.id_data, while a change to console_subscriber.aggregator.id_data can't break console_subscriber.aggregator.shrink.
- Position
- Below the diagonal: console_subscriber.aggregator.id_data uses a module listed above it, which is the healthy direction.
24→11 console_subscriber.aggregator.id_data uses console_api.generated.rs.tokio.console.common✕
- Connections
- 1 pair of types, where a type in console_subscriber.aggregator.id_data uses a type in console_api.generated.rs.tokio.console.common.
- The types involved
console_subscriber.aggregator.id_data.IdData→console_api.generated.rs.tokio.console.common.Id
- Direction
- console_subscriber.aggregator.id_data uses console_api.generated.rs.tokio.console.common, so a change to console_api.generated.rs.tokio.console.common can break console_subscriber.aggregator.id_data, while a change to console_subscriber.aggregator.id_data can't break console_api.generated.rs.tokio.console.common.
- Position
- Below the diagonal: console_subscriber.aggregator.id_data uses a module listed above it, which is the healthy direction.
24→21 console_subscriber.aggregator.id_data uses console_subscriber.stats✕
- Connections
- 1 pair of types, where a type in console_subscriber.aggregator.id_data uses a type in console_subscriber.stats.
- The types involved
console_subscriber.aggregator.id_data.IdData→console_subscriber.stats.TimeAnchor
- Direction
- console_subscriber.aggregator.id_data uses console_subscriber.stats, so a change to console_subscriber.stats can break console_subscriber.aggregator.id_data, while a change to console_subscriber.aggregator.id_data can't break console_subscriber.stats.
- Position
- Below the diagonal: console_subscriber.aggregator.id_data uses a module listed above it, which is the healthy direction.
25→6 tokio_console.state.async_ops uses tokio_console.intern✕
- Connections
- 4 pairs of types, where a type in tokio_console.state.async_ops uses a type in tokio_console.intern.
- The types involved
tokio_console.state.async_ops.AsyncOp→tokio_console.intern.InternedStrtokio_console.state.async_ops.AsyncOpStats→tokio_console.intern.InternedStrtokio_console.state.async_ops.AsyncOpStats→tokio_console.intern.Stringstokio_console.state.async_ops.AsyncOpsState→tokio_console.intern.Strings
- Direction
- tokio_console.state.async_ops uses tokio_console.intern, so a change to tokio_console.intern can break tokio_console.state.async_ops, while a change to tokio_console.state.async_ops can't break tokio_console.intern.
- Position
- Below the diagonal: tokio_console.state.async_ops uses a module listed above it, which is the healthy direction.
25→11 tokio_console.state.async_ops uses console_api.generated.rs.tokio.console.common✕
- Connections
- 4 pairs of types, where a type in tokio_console.state.async_ops uses a type in console_api.generated.rs.tokio.console.common.
- The types involved
tokio_console.state.async_ops.AsyncOp→console_api.generated.rs.tokio.console.common.Idtokio_console.state.async_ops.AsyncOpStats→console_api.generated.rs.tokio.console.common.Idtokio_console.state.async_ops.AsyncOpStats→console_api.generated.rs.tokio.console.common.Metadatatokio_console.state.async_ops.AsyncOpStats→console_api.generated.rs.tokio.console.common.Span
- Direction
- tokio_console.state.async_ops uses console_api.generated.rs.tokio.console.common, so a change to console_api.generated.rs.tokio.console.common can break tokio_console.state.async_ops, while a change to tokio_console.state.async_ops can't break console_api.generated.rs.tokio.console.common.
- Position
- Below the diagonal: tokio_console.state.async_ops uses a module listed above it, which is the healthy direction.
25→12 tokio_console.state.async_ops uses console_api.generated.rs.tokio.console.async_ops✕
- Connections
- 2 pairs of types, where a type in tokio_console.state.async_ops uses a type in console_api.generated.rs.tokio.console.async_ops.
- The types involved
tokio_console.state.async_ops.AsyncOpStats→console_api.generated.rs.tokio.console.async_ops.Statstokio_console.state.async_ops.AsyncOpsState→console_api.generated.rs.tokio.console.async_ops.AsyncOpUpdate
- Direction
- tokio_console.state.async_ops uses console_api.generated.rs.tokio.console.async_ops, so a change to console_api.generated.rs.tokio.console.async_ops can break tokio_console.state.async_ops, while a change to tokio_console.state.async_ops can't break console_api.generated.rs.tokio.console.async_ops.
- Position
- Below the diagonal: tokio_console.state.async_ops uses a module listed above it, which is the healthy direction.
25→17 tokio_console.state.async_ops uses tokio_console.state.store✕
- Connections
- 3 pairs of types, where a type in tokio_console.state.async_ops uses a type in tokio_console.state.store.
- The types involved
tokio_console.state.async_ops.AsyncOpStats→tokio_console.state.store.Idstokio_console.state.async_ops.AsyncOpsState→tokio_console.state.store.Idstokio_console.state.async_ops.AsyncOpsState→tokio_console.state.store.Store
- Direction
- tokio_console.state.async_ops uses tokio_console.state.store, so a change to tokio_console.state.store can break tokio_console.state.async_ops, while a change to tokio_console.state.async_ops can't break tokio_console.state.store.
- Position
- Below the diagonal: tokio_console.state.async_ops uses a module listed above it, which is the healthy direction.
25→18 tokio_console.state.async_ops uses tokio_console.view.styles✕
- Connections
- 2 pairs of types, where a type in tokio_console.state.async_ops uses a type in tokio_console.view.styles.
- The types involved
tokio_console.state.async_ops.AsyncOpStats→tokio_console.view.styles.Stylestokio_console.state.async_ops.AsyncOpsState→tokio_console.view.styles.Styles
- Direction
- tokio_console.state.async_ops uses tokio_console.view.styles, so a change to tokio_console.view.styles can break tokio_console.state.async_ops, while a change to tokio_console.state.async_ops can't break tokio_console.view.styles.
- Position
- Below the diagonal: tokio_console.state.async_ops uses a module listed above it, which is the healthy direction.
25→21 tokio_console.state.async_ops uses console_subscriber.stats✕
- Connections
- 1 pair of types, where a type in tokio_console.state.async_ops uses a type in console_subscriber.stats.
- The types involved
tokio_console.state.async_ops.AsyncOp→console_subscriber.stats.AsyncOpStats
- Direction
- tokio_console.state.async_ops uses console_subscriber.stats, so a change to console_subscriber.stats can break tokio_console.state.async_ops, while a change to tokio_console.state.async_ops can't break console_subscriber.stats.
- Position
- Below the diagonal: tokio_console.state.async_ops uses a module listed above it, which is the healthy direction.
25→39 tokio_console.state.async_ops uses tokio_console.state part of a loop✕
- Connections
- 1 pair of types, where a type in tokio_console.state.async_ops uses a type in tokio_console.state.
- The types involved
tokio_console.state.async_ops.AsyncOpsState→tokio_console.state.Visibility
- Direction
- tokio_console.state.async_ops uses tokio_console.state, so a change to tokio_console.state can break tokio_console.state.async_ops, while a change to tokio_console.state.async_ops can't break tokio_console.state.
- 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.
26→3 tokio_console.state.histogram uses console_api.generated.rs.tokio.console.tasks.task_details✕
- Connections
- 1 pair of types, where a type in tokio_console.state.histogram uses a type in console_api.generated.rs.tokio.console.tasks.task_details.
- The types involved
tokio_console.state.histogram.DurationHistogram→console_api.generated.rs.tokio.console.tasks.task_details.PollTimesHistogram
- Direction
- tokio_console.state.histogram uses console_api.generated.rs.tokio.console.tasks.task_details, so a change to console_api.generated.rs.tokio.console.tasks.task_details can break tokio_console.state.histogram, while a change to tokio_console.state.histogram can't break console_api.generated.rs.tokio.console.tasks.task_details.
- Position
- Below the diagonal: tokio_console.state.histogram uses a module listed above it, which is the healthy direction.
26→9 tokio_console.state.histogram uses console_api.generated.rs.tokio.console.tasks✕
- Connections
- 1 pair of types, where a type in tokio_console.state.histogram uses a type in console_api.generated.rs.tokio.console.tasks.
- The types involved
tokio_console.state.histogram.DurationHistogram→console_api.generated.rs.tokio.console.tasks.DurationHistogram
- Direction
- tokio_console.state.histogram uses console_api.generated.rs.tokio.console.tasks, so a change to console_api.generated.rs.tokio.console.tasks can break tokio_console.state.histogram, while a change to tokio_console.state.histogram can't break console_api.generated.rs.tokio.console.tasks.
- Position
- Below the diagonal: tokio_console.state.histogram uses a module listed above it, which is the healthy direction.
26→21 tokio_console.state.histogram uses console_subscriber.stats✕
- Connections
- 2 pairs of types, where a type in tokio_console.state.histogram uses a type in console_subscriber.stats.
- The types involved
tokio_console.state.histogram.DurationHistogram→console_subscriber.stats.Histogramtokio_console.state.histogram.histogram$module→console_subscriber.stats.Histogram
- Direction
- tokio_console.state.histogram uses console_subscriber.stats, so a change to console_subscriber.stats can break tokio_console.state.histogram, while a change to tokio_console.state.histogram can't break console_subscriber.stats.
- Position
- Below the diagonal: tokio_console.state.histogram uses a module listed above it, which is the healthy direction.
27→10 tokio_console.view.table uses console_api.generated.rs.tokio.console.instrument✕
- Connections
- 2 pairs of types, where a type in tokio_console.view.table uses a type in console_api.generated.rs.tokio.console.instrument.
- The types involved
tokio_console.view.table.TableList→console_api.generated.rs.tokio.console.instrument.Statetokio_console.view.table.TableListState→console_api.generated.rs.tokio.console.instrument.State
- Direction
- tokio_console.view.table uses console_api.generated.rs.tokio.console.instrument, so a change to console_api.generated.rs.tokio.console.instrument can break tokio_console.view.table, while a change to tokio_console.view.table can't break console_api.generated.rs.tokio.console.instrument.
- Position
- Below the diagonal: tokio_console.view.table uses a module listed above it, which is the healthy direction.
27→13 tokio_console.view.table uses console_api.generated.rs.tokio.console.trace.trace_event✕
- Connections
- 1 pair of types, where a type in tokio_console.view.table uses a type in console_api.generated.rs.tokio.console.trace.trace_event.
- The types involved
tokio_console.view.table.TableListState→console_api.generated.rs.tokio.console.trace.trace_event.Event
- Direction
- tokio_console.view.table uses console_api.generated.rs.tokio.console.trace.trace_event, so a change to console_api.generated.rs.tokio.console.trace.trace_event can break tokio_console.view.table, while a change to tokio_console.view.table can't break console_api.generated.rs.tokio.console.trace.trace_event.
- Position
- Below the diagonal: tokio_console.view.table uses a module listed above it, which is the healthy direction.
27→18 tokio_console.view.table uses tokio_console.view.styles✕
- Connections
- 2 pairs of types, where a type in tokio_console.view.table uses a type in tokio_console.view.styles.
- The types involved
tokio_console.view.table.TableList→tokio_console.view.styles.Stylestokio_console.view.table.TableListState→tokio_console.view.styles.Styles
- Direction
- tokio_console.view.table uses tokio_console.view.styles, so a change to tokio_console.view.styles can break tokio_console.view.table, while a change to tokio_console.view.table can't break tokio_console.view.styles.
- Position
- Below the diagonal: tokio_console.view.table uses a module listed above it, which is the healthy direction.
27→23 tokio_console.view.table uses tokio_console.view.help✕
- Connections
- 1 pair of types, where a type in tokio_console.view.table uses a type in tokio_console.view.help.
- The types involved
tokio_console.view.table.TableListState→tokio_console.view.help.HelpText
- Direction
- tokio_console.view.table uses tokio_console.view.help, so a change to tokio_console.view.help can break tokio_console.view.table, while a change to tokio_console.view.table can't break tokio_console.view.help.
- Position
- Below the diagonal: tokio_console.view.table uses a module listed above it, which is the healthy direction.
28→9 tokio_console.view.task uses console_api.generated.rs.tokio.console.tasks✕
- Connections
- 1 pair of types, where a type in tokio_console.view.task uses a type in console_api.generated.rs.tokio.console.tasks.
- The types involved
tokio_console.view.task.TaskView→console_api.generated.rs.tokio.console.tasks.Task
- Direction
- tokio_console.view.task uses console_api.generated.rs.tokio.console.tasks, so a change to console_api.generated.rs.tokio.console.tasks can break tokio_console.view.task, while a change to tokio_console.view.task can't break console_api.generated.rs.tokio.console.tasks.
- Position
- Below the diagonal: tokio_console.view.task uses a module listed above it, which is the healthy direction.
28→13 tokio_console.view.task uses console_api.generated.rs.tokio.console.trace.trace_event✕
- Connections
- 1 pair of types, where a type in tokio_console.view.task uses a type in console_api.generated.rs.tokio.console.trace.trace_event.
- The types involved
tokio_console.view.task.TaskView→console_api.generated.rs.tokio.console.trace.trace_event.Event
- Direction
- tokio_console.view.task uses console_api.generated.rs.tokio.console.trace.trace_event, so a change to console_api.generated.rs.tokio.console.trace.trace_event can break tokio_console.view.task, while a change to tokio_console.view.task can't break console_api.generated.rs.tokio.console.trace.trace_event.
- Position
- Below the diagonal: tokio_console.view.task uses a module listed above it, which is the healthy direction.
28→18 tokio_console.view.task uses tokio_console.view.styles✕
- Connections
- 1 pair of types, where a type in tokio_console.view.task uses a type in tokio_console.view.styles.
- The types involved
tokio_console.view.task.TaskView→tokio_console.view.styles.Styles
- Direction
- tokio_console.view.task uses tokio_console.view.styles, so a change to tokio_console.view.styles can break tokio_console.view.task, while a change to tokio_console.view.task can't break tokio_console.view.styles.
- Position
- Below the diagonal: tokio_console.view.task uses a module listed above it, which is the healthy direction.
28→23 tokio_console.view.task uses tokio_console.view.help✕
- Connections
- 1 pair of types, where a type in tokio_console.view.task uses a type in tokio_console.view.help.
- The types involved
tokio_console.view.task.TaskView→tokio_console.view.help.HelpText
- Direction
- tokio_console.view.task uses tokio_console.view.help, so a change to tokio_console.view.help can break tokio_console.view.task, while a change to tokio_console.view.task can't break tokio_console.view.help.
- Position
- Below the diagonal: tokio_console.view.task uses a module listed above it, which is the healthy direction.
29→9 tokio_console.warnings uses console_api.generated.rs.tokio.console.tasks✕
- Connections
- 5 pairs of types, where a type in tokio_console.warnings uses a type in console_api.generated.rs.tokio.console.tasks.
- The types involved
tokio_console.warnings.AutoBoxedFuture→console_api.generated.rs.tokio.console.tasks.Tasktokio_console.warnings.LargeFuture→console_api.generated.rs.tokio.console.tasks.Tasktokio_console.warnings.LostWaker→console_api.generated.rs.tokio.console.tasks.Tasktokio_console.warnings.NeverYielded→console_api.generated.rs.tokio.console.tasks.Tasktokio_console.warnings.SelfWakePercent→console_api.generated.rs.tokio.console.tasks.Task
- Direction
- tokio_console.warnings uses console_api.generated.rs.tokio.console.tasks, so a change to console_api.generated.rs.tokio.console.tasks can break tokio_console.warnings, while a change to tokio_console.warnings can't break console_api.generated.rs.tokio.console.tasks.
- Position
- Below the diagonal: tokio_console.warnings uses a module listed above it, which is the healthy direction.
29→22 tokio_console.warnings uses tokio_console.config✕
- Connections
- 1 pair of types, where a type in tokio_console.warnings uses a type in tokio_console.config.
- The types involved
tokio_console.warnings.Linter→tokio_console.config.KnownWarnings
- Direction
- tokio_console.warnings uses tokio_console.config, so a change to tokio_console.config can break tokio_console.warnings, while a change to tokio_console.warnings can't break tokio_console.config.
- Position
- Below the diagonal: tokio_console.warnings uses a module listed above it, which is the healthy direction.
30→2 console_subscriber.aggregator uses console_api.generated.rs.tokio.console.common.metadata✕
- Connections
- 1 pair of types, where a type in console_subscriber.aggregator uses a type in console_api.generated.rs.tokio.console.common.metadata.
- The types involved
console_subscriber.aggregator.Resource→console_api.generated.rs.tokio.console.common.metadata.Kind
- Direction
- console_subscriber.aggregator uses console_api.generated.rs.tokio.console.common.metadata, so a change to console_api.generated.rs.tokio.console.common.metadata can break console_subscriber.aggregator, while a change to console_subscriber.aggregator can't break console_api.generated.rs.tokio.console.common.metadata.
- Position
- Below the diagonal: console_subscriber.aggregator uses a module listed above it, which is the healthy direction.
30→4 console_subscriber.aggregator uses console_subscriber.aggregator.shrink✕
- Connections
- 2 pairs of types, where a type in console_subscriber.aggregator uses a type in console_subscriber.aggregator.shrink.
- The types involved
console_subscriber.aggregator.Aggregator→console_subscriber.aggregator.shrink.ShrinkMapconsole_subscriber.aggregator.Aggregator→console_subscriber.aggregator.shrink.ShrinkVec
- Direction
- console_subscriber.aggregator uses console_subscriber.aggregator.shrink, so a change to console_subscriber.aggregator.shrink can break console_subscriber.aggregator, while a change to console_subscriber.aggregator can't break console_subscriber.aggregator.shrink.
- Position
- Below the diagonal: console_subscriber.aggregator uses a module listed above it, which is the healthy direction.
30→5 console_subscriber.aggregator uses console_subscriber.builder✕
- Connections
- 1 pair of types, where a type in console_subscriber.aggregator uses a type in console_subscriber.builder.
- The types involved
console_subscriber.aggregator.Aggregator→console_subscriber.builder.Builder
- Direction
- console_subscriber.aggregator uses console_subscriber.builder, so a change to console_subscriber.builder can break console_subscriber.aggregator, while a change to console_subscriber.aggregator can't break console_subscriber.builder.
- Position
- Below the diagonal: console_subscriber.aggregator uses a module listed above it, which is the healthy direction.
30→7 console_subscriber.aggregator uses console_api.generated.rs.tokio.console.common.register_metadata✕
- Connections
- 1 pair of types, where a type in console_subscriber.aggregator uses a type in console_api.generated.rs.tokio.console.common.register_metadata.
- The types involved
console_subscriber.aggregator.Aggregator→console_api.generated.rs.tokio.console.common.register_metadata.NewMetadata
- Direction
- console_subscriber.aggregator uses console_api.generated.rs.tokio.console.common.register_metadata, so a change to console_api.generated.rs.tokio.console.common.register_metadata can break console_subscriber.aggregator, while a change to console_subscriber.aggregator can't break console_api.generated.rs.tokio.console.common.register_metadata.
- Position
- Below the diagonal: console_subscriber.aggregator uses a module listed above it, which is the healthy direction.
30→8 console_subscriber.aggregator uses console_api.generated.rs.tokio.console.resources✕
- Connections
- 2 pairs of types, where a type in console_subscriber.aggregator uses a type in console_api.generated.rs.tokio.console.resources.
- The types involved
console_subscriber.aggregator.Aggregator→console_api.generated.rs.tokio.console.resources.PollOpconsole_subscriber.aggregator.Aggregator→console_api.generated.rs.tokio.console.resources.ResourceUpdate
- Direction
- console_subscriber.aggregator uses console_api.generated.rs.tokio.console.resources, so a change to console_api.generated.rs.tokio.console.resources can break console_subscriber.aggregator, while a change to console_subscriber.aggregator can't break console_api.generated.rs.tokio.console.resources.
- Position
- Below the diagonal: console_subscriber.aggregator uses a module listed above it, which is the healthy direction.
30→9 console_subscriber.aggregator uses console_api.generated.rs.tokio.console.tasks✕
- Connections
- 1 pair of types, where a type in console_subscriber.aggregator uses a type in console_api.generated.rs.tokio.console.tasks.
- The types involved
console_subscriber.aggregator.Aggregator→console_api.generated.rs.tokio.console.tasks.TaskUpdate
- Direction
- console_subscriber.aggregator uses console_api.generated.rs.tokio.console.tasks, so a change to console_api.generated.rs.tokio.console.tasks can break console_subscriber.aggregator, while a change to console_subscriber.aggregator can't break console_api.generated.rs.tokio.console.tasks.
- Position
- Below the diagonal: console_subscriber.aggregator uses a module listed above it, which is the healthy direction.
30→10 console_subscriber.aggregator uses console_api.generated.rs.tokio.console.instrument✕
- Connections
- 1 pair of types, where a type in console_subscriber.aggregator uses a type in console_api.generated.rs.tokio.console.instrument.
- The types involved
console_subscriber.aggregator.Aggregator→console_api.generated.rs.tokio.console.instrument.Temporality
- Direction
- console_subscriber.aggregator uses console_api.generated.rs.tokio.console.instrument, so a change to console_api.generated.rs.tokio.console.instrument can break console_subscriber.aggregator, while a change to console_subscriber.aggregator can't break console_api.generated.rs.tokio.console.instrument.
- Position
- Below the diagonal: console_subscriber.aggregator uses a module listed above it, which is the healthy direction.
30→11 console_subscriber.aggregator uses console_api.generated.rs.tokio.console.common✕
- Connections
- 9 pairs of types, where a type in console_subscriber.aggregator uses a type in console_api.generated.rs.tokio.console.common.
- The types involved
console_subscriber.aggregator.AsyncOp→console_api.generated.rs.tokio.console.common.Idconsole_subscriber.aggregator.AsyncOp→console_api.generated.rs.tokio.console.common.Metadataconsole_subscriber.aggregator.Resource→console_api.generated.rs.tokio.console.common.Idconsole_subscriber.aggregator.Resource→console_api.generated.rs.tokio.console.common.Locationconsole_subscriber.aggregator.Resource→console_api.generated.rs.tokio.console.common.Metadataconsole_subscriber.aggregator.Task→console_api.generated.rs.tokio.console.common.Fieldconsole_subscriber.aggregator.Task→console_api.generated.rs.tokio.console.common.Idconsole_subscriber.aggregator.Task→console_api.generated.rs.tokio.console.common.Locationconsole_subscriber.aggregator.Task→console_api.generated.rs.tokio.console.common.Metadata
- Direction
- console_subscriber.aggregator uses console_api.generated.rs.tokio.console.common, so a change to console_api.generated.rs.tokio.console.common can break console_subscriber.aggregator, while a change to console_subscriber.aggregator can't break console_api.generated.rs.tokio.console.common.
- Position
- Below the diagonal: console_subscriber.aggregator uses a module listed above it, which is the healthy direction.
30→12 console_subscriber.aggregator uses console_api.generated.rs.tokio.console.async_ops✕
- Connections
- 1 pair of types, where a type in console_subscriber.aggregator uses a type in console_api.generated.rs.tokio.console.async_ops.
- The types involved
console_subscriber.aggregator.Aggregator→console_api.generated.rs.tokio.console.async_ops.AsyncOpUpdate
- Direction
- console_subscriber.aggregator uses console_api.generated.rs.tokio.console.async_ops, so a change to console_api.generated.rs.tokio.console.async_ops can break console_subscriber.aggregator, while a change to console_subscriber.aggregator can't break console_api.generated.rs.tokio.console.async_ops.
- Position
- Below the diagonal: console_subscriber.aggregator uses a module listed above it, which is the healthy direction.
30→13 console_subscriber.aggregator uses console_api.generated.rs.tokio.console.trace.trace_event✕
- Connections
- 2 pairs of types, where a type in console_subscriber.aggregator uses a type in console_api.generated.rs.tokio.console.trace.trace_event.
- The types involved
console_subscriber.aggregator.Aggregator→console_api.generated.rs.tokio.console.trace.trace_event.Eventconsole_subscriber.aggregator.EventCounts→console_api.generated.rs.tokio.console.trace.trace_event.Event
- Direction
- console_subscriber.aggregator uses console_api.generated.rs.tokio.console.trace.trace_event, so a change to console_api.generated.rs.tokio.console.trace.trace_event can break console_subscriber.aggregator, while a change to console_subscriber.aggregator can't break console_api.generated.rs.tokio.console.trace.trace_event.
- Position
- Below the diagonal: console_subscriber.aggregator uses a module listed above it, which is the healthy direction.
30→19 console_subscriber.aggregator uses console_api.generated.rs.tokio.console.trace✕
- Connections
- 1 pair of types, where a type in console_subscriber.aggregator uses a type in console_api.generated.rs.tokio.console.trace.
- The types involved
console_subscriber.aggregator.Aggregator→console_api.generated.rs.tokio.console.trace.WatchRequest
- Direction
- console_subscriber.aggregator uses console_api.generated.rs.tokio.console.trace, so a change to console_api.generated.rs.tokio.console.trace can break console_subscriber.aggregator, while a change to console_subscriber.aggregator can't break console_api.generated.rs.tokio.console.trace.
- Position
- Below the diagonal: console_subscriber.aggregator uses a module listed above it, which is the healthy direction.
30→21 console_subscriber.aggregator uses console_subscriber.stats✕
- Connections
- 7 pairs of types, where a type in console_subscriber.aggregator uses a type in console_subscriber.stats.
- The types involved
console_subscriber.aggregator.Aggregator→console_subscriber.stats.TimeAnchorconsole_subscriber.aggregator.AsyncOp→console_subscriber.stats.TimeAnchorconsole_subscriber.aggregator.AsyncOp→console_subscriber.stats.Unsentconsole_subscriber.aggregator.Resource→console_subscriber.stats.TimeAnchorconsole_subscriber.aggregator.Resource→console_subscriber.stats.Unsentconsole_subscriber.aggregator.Task→console_subscriber.stats.TimeAnchorconsole_subscriber.aggregator.Task→console_subscriber.stats.Unsent
- Direction
- console_subscriber.aggregator uses console_subscriber.stats, so a change to console_subscriber.stats can break console_subscriber.aggregator, while a change to console_subscriber.aggregator can't break console_subscriber.stats.
- Position
- Below the diagonal: console_subscriber.aggregator uses a module listed above it, which is the healthy direction.
30→24 console_subscriber.aggregator uses console_subscriber.aggregator.id_data✕
- Connections
- 2 pairs of types, where a type in console_subscriber.aggregator uses a type in console_subscriber.aggregator.id_data.
- The types involved
console_subscriber.aggregator.Aggregator→console_subscriber.aggregator.id_data.IdDataconsole_subscriber.aggregator.Aggregator→console_subscriber.aggregator.id_data.Include
- Direction
- console_subscriber.aggregator uses console_subscriber.aggregator.id_data, so a change to console_subscriber.aggregator.id_data can break console_subscriber.aggregator, while a change to console_subscriber.aggregator can't break console_subscriber.aggregator.id_data.
- Position
- Below the diagonal: console_subscriber.aggregator uses a module listed above it, which is the healthy direction.
30→38 console_subscriber.aggregator uses console_subscriber part of a loop✕
- Connections
- 5 pairs of types, where a type in console_subscriber.aggregator uses a type in console_subscriber.
- The types involved
console_subscriber.aggregator.Aggregator→console_subscriber.Sharedconsole_subscriber.aggregator.Aggregator→console_subscriber.Watchconsole_subscriber.aggregator.AsyncOp→console_subscriber.ToProtoconsole_subscriber.aggregator.Resource→console_subscriber.ToProtoconsole_subscriber.aggregator.Task→console_subscriber.ToProto
- Direction
- console_subscriber.aggregator uses console_subscriber, so a change to console_subscriber can break console_subscriber.aggregator, while a change to console_subscriber.aggregator can't break console_subscriber.
- 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.
31→2 tokio_console.state.resources uses console_api.generated.rs.tokio.console.common.metadata✕
- Connections
- 1 pair of types, where a type in tokio_console.state.resources uses a type in console_api.generated.rs.tokio.console.common.metadata.
- The types involved
tokio_console.state.resources.resources$module→console_api.generated.rs.tokio.console.common.metadata.Kind
- Direction
- tokio_console.state.resources uses console_api.generated.rs.tokio.console.common.metadata, so a change to console_api.generated.rs.tokio.console.common.metadata can break tokio_console.state.resources, while a change to tokio_console.state.resources can't break console_api.generated.rs.tokio.console.common.metadata.
- Position
- Below the diagonal: tokio_console.state.resources uses a module listed above it, which is the healthy direction.
31→6 tokio_console.state.resources uses tokio_console.intern✕
- Connections
- 4 pairs of types, where a type in tokio_console.state.resources uses a type in tokio_console.intern.
- The types involved
tokio_console.state.resources.Resource→tokio_console.intern.InternedStrtokio_console.state.resources.ResourceStats→tokio_console.intern.Stringstokio_console.state.resources.ResourcesState→tokio_console.intern.Stringstokio_console.state.resources.resources$module→tokio_console.intern.Strings
- Direction
- tokio_console.state.resources uses tokio_console.intern, so a change to tokio_console.intern can break tokio_console.state.resources, while a change to tokio_console.state.resources can't break tokio_console.intern.
- Position
- Below the diagonal: tokio_console.state.resources uses a module listed above it, which is the healthy direction.
31→8 tokio_console.state.resources uses console_api.generated.rs.tokio.console.resources✕
- Connections
- 1 pair of types, where a type in tokio_console.state.resources uses a type in console_api.generated.rs.tokio.console.resources.
- The types involved
tokio_console.state.resources.ResourcesState→console_api.generated.rs.tokio.console.resources.ResourceUpdate
- Direction
- tokio_console.state.resources uses console_api.generated.rs.tokio.console.resources, so a change to console_api.generated.rs.tokio.console.resources can break tokio_console.state.resources, while a change to tokio_console.state.resources can't break console_api.generated.rs.tokio.console.resources.
- Position
- Below the diagonal: tokio_console.state.resources uses a module listed above it, which is the healthy direction.
31→11 tokio_console.state.resources uses console_api.generated.rs.tokio.console.common✕
- Connections
- 5 pairs of types, where a type in tokio_console.state.resources uses a type in console_api.generated.rs.tokio.console.common.
- The types involved
tokio_console.state.resources.Resource→console_api.generated.rs.tokio.console.common.Idtokio_console.state.resources.Resource→console_api.generated.rs.tokio.console.common.SpanIdtokio_console.state.resources.ResourceStats→console_api.generated.rs.tokio.console.common.Metadatatokio_console.state.resources.ResourceStats→console_api.generated.rs.tokio.console.common.Spantokio_console.state.resources.TypeVisibility→console_api.generated.rs.tokio.console.common.Span
- Direction
- tokio_console.state.resources uses console_api.generated.rs.tokio.console.common, so a change to console_api.generated.rs.tokio.console.common can break tokio_console.state.resources, while a change to tokio_console.state.resources can't break console_api.generated.rs.tokio.console.common.
- Position
- Below the diagonal: tokio_console.state.resources uses a module listed above it, which is the healthy direction.
31→12 tokio_console.state.resources uses console_api.generated.rs.tokio.console.async_ops✕
- Connections
- 1 pair of types, where a type in tokio_console.state.resources uses a type in console_api.generated.rs.tokio.console.async_ops.
- The types involved
tokio_console.state.resources.ResourceStats→console_api.generated.rs.tokio.console.async_ops.Stats
- Direction
- tokio_console.state.resources uses console_api.generated.rs.tokio.console.async_ops, so a change to console_api.generated.rs.tokio.console.async_ops can break tokio_console.state.resources, while a change to tokio_console.state.resources can't break console_api.generated.rs.tokio.console.async_ops.
- Position
- Below the diagonal: tokio_console.state.resources uses a module listed above it, which is the healthy direction.
31→17 tokio_console.state.resources uses tokio_console.state.store✕
- Connections
- 2 pairs of types, where a type in tokio_console.state.resources uses a type in tokio_console.state.store.
- The types involved
tokio_console.state.resources.ResourcesState→tokio_console.state.store.Idstokio_console.state.resources.ResourcesState→tokio_console.state.store.Store
- Direction
- tokio_console.state.resources uses tokio_console.state.store, so a change to tokio_console.state.store can break tokio_console.state.resources, while a change to tokio_console.state.resources can't break tokio_console.state.store.
- Position
- Below the diagonal: tokio_console.state.resources uses a module listed above it, which is the healthy direction.
31→18 tokio_console.state.resources uses tokio_console.view.styles✕
- Connections
- 3 pairs of types, where a type in tokio_console.state.resources uses a type in tokio_console.view.styles.
- The types involved
tokio_console.state.resources.ResourceStats→tokio_console.view.styles.Stylestokio_console.state.resources.ResourcesState→tokio_console.view.styles.Stylestokio_console.state.resources.TypeVisibility→tokio_console.view.styles.Styles
- Direction
- tokio_console.state.resources uses tokio_console.view.styles, so a change to tokio_console.view.styles can break tokio_console.state.resources, while a change to tokio_console.state.resources can't break tokio_console.view.styles.
- Position
- Below the diagonal: tokio_console.state.resources uses a module listed above it, which is the healthy direction.
31→21 tokio_console.state.resources uses console_subscriber.stats✕
- Connections
- 1 pair of types, where a type in tokio_console.state.resources uses a type in console_subscriber.stats.
- The types involved
tokio_console.state.resources.Resource→console_subscriber.stats.ResourceStats
- Direction
- tokio_console.state.resources uses console_subscriber.stats, so a change to console_subscriber.stats can break tokio_console.state.resources, while a change to tokio_console.state.resources can't break console_subscriber.stats.
- Position
- Below the diagonal: tokio_console.state.resources uses a module listed above it, which is the healthy direction.
31→25 tokio_console.state.resources uses tokio_console.state.async_ops✕
- Connections
- 1 pair of types, where a type in tokio_console.state.resources uses a type in tokio_console.state.async_ops.
- The types involved
tokio_console.state.resources.SortBy→tokio_console.state.async_ops.SortBy
- Direction
- tokio_console.state.resources uses tokio_console.state.async_ops, so a change to tokio_console.state.async_ops can break tokio_console.state.resources, while a change to tokio_console.state.resources can't break tokio_console.state.async_ops.
- Position
- Below the diagonal: tokio_console.state.resources uses a module listed above it, which is the healthy direction.
31→39 tokio_console.state.resources uses tokio_console.state part of a loop✕
- Connections
- 1 pair of types, where a type in tokio_console.state.resources uses a type in tokio_console.state.
- The types involved
tokio_console.state.resources.ResourcesState→tokio_console.state.Visibility
- Direction
- tokio_console.state.resources uses tokio_console.state, so a change to tokio_console.state can break tokio_console.state.resources, while a change to tokio_console.state.resources can't break tokio_console.state.
- 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.
32→6 tokio_console.state.tasks uses tokio_console.intern✕
- Connections
- 2 pairs of types, where a type in tokio_console.state.tasks uses a type in tokio_console.intern.
- The types involved
tokio_console.state.tasks.Task→tokio_console.intern.InternedStrtokio_console.state.tasks.TasksState→tokio_console.intern.Strings
- Direction
- tokio_console.state.tasks uses tokio_console.intern, so a change to tokio_console.intern can break tokio_console.state.tasks, while a change to tokio_console.state.tasks can't break tokio_console.intern.
- Position
- Below the diagonal: tokio_console.state.tasks uses a module listed above it, which is the healthy direction.
32→9 tokio_console.state.tasks uses console_api.generated.rs.tokio.console.tasks✕
- Connections
- 2 pairs of types, where a type in tokio_console.state.tasks uses a type in console_api.generated.rs.tokio.console.tasks.
- The types involved
tokio_console.state.tasks.Details→console_api.generated.rs.tokio.console.tasks.DurationHistogramtokio_console.state.tasks.TasksState→console_api.generated.rs.tokio.console.tasks.TaskUpdate
- Direction
- tokio_console.state.tasks uses console_api.generated.rs.tokio.console.tasks, so a change to console_api.generated.rs.tokio.console.tasks can break tokio_console.state.tasks, while a change to tokio_console.state.tasks can't break console_api.generated.rs.tokio.console.tasks.
- Position
- Below the diagonal: tokio_console.state.tasks uses a module listed above it, which is the healthy direction.
32→11 tokio_console.state.tasks uses console_api.generated.rs.tokio.console.common✕
- Connections
- 6 pairs of types, where a type in tokio_console.state.tasks uses a type in console_api.generated.rs.tokio.console.common.
- The types involved
tokio_console.state.tasks.Details→console_api.generated.rs.tokio.console.common.SpanIdtokio_console.state.tasks.Task→console_api.generated.rs.tokio.console.common.Idtokio_console.state.tasks.Task→console_api.generated.rs.tokio.console.common.Spantokio_console.state.tasks.Task→console_api.generated.rs.tokio.console.common.SpanIdtokio_console.state.tasks.TaskState→console_api.generated.rs.tokio.console.common.Spantokio_console.state.tasks.TasksState→console_api.generated.rs.tokio.console.common.Id
- Direction
- tokio_console.state.tasks uses console_api.generated.rs.tokio.console.common, so a change to console_api.generated.rs.tokio.console.common can break tokio_console.state.tasks, while a change to tokio_console.state.tasks can't break console_api.generated.rs.tokio.console.common.
- Position
- Below the diagonal: tokio_console.state.tasks uses a module listed above it, which is the healthy direction.
32→12 tokio_console.state.tasks uses console_api.generated.rs.tokio.console.async_ops✕
- Connections
- 1 pair of types, where a type in tokio_console.state.tasks uses a type in console_api.generated.rs.tokio.console.async_ops.
- The types involved
tokio_console.state.tasks.TaskStats→console_api.generated.rs.tokio.console.async_ops.Stats
- Direction
- tokio_console.state.tasks uses console_api.generated.rs.tokio.console.async_ops, so a change to console_api.generated.rs.tokio.console.async_ops can break tokio_console.state.tasks, while a change to tokio_console.state.tasks can't break console_api.generated.rs.tokio.console.async_ops.
- Position
- Below the diagonal: tokio_console.state.tasks uses a module listed above it, which is the healthy direction.
32→17 tokio_console.state.tasks uses tokio_console.state.store✕
- Connections
- 2 pairs of types, where a type in tokio_console.state.tasks uses a type in tokio_console.state.store.
- The types involved
tokio_console.state.tasks.TasksState→tokio_console.state.store.Idstokio_console.state.tasks.TasksState→tokio_console.state.store.Store
- Direction
- tokio_console.state.tasks uses tokio_console.state.store, so a change to tokio_console.state.store can break tokio_console.state.tasks, while a change to tokio_console.state.tasks can't break tokio_console.state.store.
- Position
- Below the diagonal: tokio_console.state.tasks uses a module listed above it, which is the healthy direction.
32→18 tokio_console.state.tasks uses tokio_console.view.styles✕
- Connections
- 2 pairs of types, where a type in tokio_console.state.tasks uses a type in tokio_console.view.styles.
- The types involved
tokio_console.state.tasks.TaskState→tokio_console.view.styles.Stylestokio_console.state.tasks.TasksState→tokio_console.view.styles.Styles
- Direction
- tokio_console.state.tasks uses tokio_console.view.styles, so a change to tokio_console.view.styles can break tokio_console.state.tasks, while a change to tokio_console.state.tasks can't break tokio_console.view.styles.
- Position
- Below the diagonal: tokio_console.state.tasks uses a module listed above it, which is the healthy direction.
32→21 tokio_console.state.tasks uses console_subscriber.stats✕
- Connections
- 1 pair of types, where a type in tokio_console.state.tasks uses a type in console_subscriber.stats.
- The types involved
tokio_console.state.tasks.Task→console_subscriber.stats.TaskStats
- Direction
- tokio_console.state.tasks uses console_subscriber.stats, so a change to console_subscriber.stats can break tokio_console.state.tasks, while a change to tokio_console.state.tasks can't break console_subscriber.stats.
- Position
- Below the diagonal: tokio_console.state.tasks uses a module listed above it, which is the healthy direction.
32→25 tokio_console.state.tasks uses tokio_console.state.async_ops✕
- Connections
- 1 pair of types, where a type in tokio_console.state.tasks uses a type in tokio_console.state.async_ops.
- The types involved
tokio_console.state.tasks.SortBy→tokio_console.state.async_ops.SortBy
- Direction
- tokio_console.state.tasks uses tokio_console.state.async_ops, so a change to tokio_console.state.async_ops can break tokio_console.state.tasks, while a change to tokio_console.state.tasks can't break tokio_console.state.async_ops.
- Position
- Below the diagonal: tokio_console.state.tasks uses a module listed above it, which is the healthy direction.
32→29 tokio_console.state.tasks uses tokio_console.warnings✕
- Connections
- 2 pairs of types, where a type in tokio_console.state.tasks uses a type in tokio_console.warnings.
- The types involved
tokio_console.state.tasks.Task→tokio_console.warnings.Lintertokio_console.state.tasks.TasksState→tokio_console.warnings.Linter
- Direction
- tokio_console.state.tasks uses tokio_console.warnings, so a change to tokio_console.warnings can break tokio_console.state.tasks, while a change to tokio_console.state.tasks can't break tokio_console.warnings.
- Position
- Below the diagonal: tokio_console.state.tasks uses a module listed above it, which is the healthy direction.
32→39 tokio_console.state.tasks uses tokio_console.state part of a loop✕
- Connections
- 1 pair of types, where a type in tokio_console.state.tasks uses a type in tokio_console.state.
- The types involved
tokio_console.state.tasks.TasksState→tokio_console.state.Visibility
- Direction
- tokio_console.state.tasks uses tokio_console.state, so a change to tokio_console.state can break tokio_console.state.tasks, while a change to tokio_console.state.tasks can't break tokio_console.state.
- 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.
33→10 tokio_console.view uses console_api.generated.rs.tokio.console.instrument✕
- Connections
- 1 pair of types, where a type in tokio_console.view uses a type in console_api.generated.rs.tokio.console.instrument.
- The types involved
tokio_console.view.View→console_api.generated.rs.tokio.console.instrument.State
- Direction
- tokio_console.view uses console_api.generated.rs.tokio.console.instrument, so a change to console_api.generated.rs.tokio.console.instrument can break tokio_console.view, while a change to tokio_console.view can't break console_api.generated.rs.tokio.console.instrument.
- Position
- Below the diagonal: tokio_console.view uses a module listed above it, which is the healthy direction.
33→11 tokio_console.view uses console_api.generated.rs.tokio.console.common✕
- Connections
- 1 pair of types, where a type in tokio_console.view uses a type in console_api.generated.rs.tokio.console.common.
- The types involved
tokio_console.view.view$module→console_api.generated.rs.tokio.console.common.Span
- Direction
- tokio_console.view uses console_api.generated.rs.tokio.console.common, so a change to console_api.generated.rs.tokio.console.common can break tokio_console.view, while a change to tokio_console.view can't break console_api.generated.rs.tokio.console.common.
- Position
- Below the diagonal: tokio_console.view uses a module listed above it, which is the healthy direction.
33→13 tokio_console.view uses console_api.generated.rs.tokio.console.trace.trace_event✕
- Connections
- 1 pair of types, where a type in tokio_console.view uses a type in console_api.generated.rs.tokio.console.trace.trace_event.
- The types involved
tokio_console.view.View→console_api.generated.rs.tokio.console.trace.trace_event.Event
- Direction
- tokio_console.view uses console_api.generated.rs.tokio.console.trace.trace_event, so a change to console_api.generated.rs.tokio.console.trace.trace_event can break tokio_console.view, while a change to tokio_console.view can't break console_api.generated.rs.tokio.console.trace.trace_event.
- Position
- Below the diagonal: tokio_console.view uses a module listed above it, which is the healthy direction.
33→18 tokio_console.view uses tokio_console.view.styles✕
- Connections
- 1 pair of types, where a type in tokio_console.view uses a type in tokio_console.view.styles.
- The types involved
tokio_console.view.View→tokio_console.view.styles.Styles
- Direction
- tokio_console.view uses tokio_console.view.styles, so a change to tokio_console.view.styles can break tokio_console.view, while a change to tokio_console.view can't break tokio_console.view.styles.
- Position
- Below the diagonal: tokio_console.view uses a module listed above it, which is the healthy direction.
33→27 tokio_console.view uses tokio_console.view.table✕
- Connections
- 1 pair of types, where a type in tokio_console.view uses a type in tokio_console.view.table.
- The types involved
tokio_console.view.View→tokio_console.view.table.TableListState
- Direction
- tokio_console.view uses tokio_console.view.table, so a change to tokio_console.view.table can break tokio_console.view, while a change to tokio_console.view can't break tokio_console.view.table.
- Position
- Below the diagonal: tokio_console.view uses a module listed above it, which is the healthy direction.
34→10 tokio_console.view.async_ops uses console_api.generated.rs.tokio.console.instrument✕
- Connections
- 1 pair of types, where a type in tokio_console.view.async_ops uses a type in console_api.generated.rs.tokio.console.instrument.
- The types involved
tokio_console.view.async_ops.AsyncOpsTable→console_api.generated.rs.tokio.console.instrument.State
- Direction
- tokio_console.view.async_ops uses console_api.generated.rs.tokio.console.instrument, so a change to console_api.generated.rs.tokio.console.instrument can break tokio_console.view.async_ops, while a change to tokio_console.view.async_ops can't break console_api.generated.rs.tokio.console.instrument.
- Position
- Below the diagonal: tokio_console.view.async_ops uses a module listed above it, which is the healthy direction.
34→11 tokio_console.view.async_ops uses console_api.generated.rs.tokio.console.common✕
- Connections
- 1 pair of types, where a type in tokio_console.view.async_ops uses a type in console_api.generated.rs.tokio.console.common.
- The types involved
tokio_console.view.async_ops.AsyncOpsTableCtx→console_api.generated.rs.tokio.console.common.Id
- Direction
- tokio_console.view.async_ops uses console_api.generated.rs.tokio.console.common, so a change to console_api.generated.rs.tokio.console.common can break tokio_console.view.async_ops, while a change to tokio_console.view.async_ops can't break console_api.generated.rs.tokio.console.common.
- Position
- Below the diagonal: tokio_console.view.async_ops uses a module listed above it, which is the healthy direction.
34→18 tokio_console.view.async_ops uses tokio_console.view.styles✕
- Connections
- 1 pair of types, where a type in tokio_console.view.async_ops uses a type in tokio_console.view.styles.
- The types involved
tokio_console.view.async_ops.AsyncOpsTable→tokio_console.view.styles.Styles
- Direction
- tokio_console.view.async_ops uses tokio_console.view.styles, so a change to tokio_console.view.styles can break tokio_console.view.async_ops, while a change to tokio_console.view.async_ops can't break tokio_console.view.styles.
- Position
- Below the diagonal: tokio_console.view.async_ops uses a module listed above it, which is the healthy direction.
34→27 tokio_console.view.async_ops uses tokio_console.view.table✕
- Connections
- 2 pairs of types, where a type in tokio_console.view.async_ops uses a type in tokio_console.view.table.
- The types involved
tokio_console.view.async_ops.AsyncOpsTable→tokio_console.view.table.TableListtokio_console.view.async_ops.AsyncOpsTable→tokio_console.view.table.TableListState
- Direction
- tokio_console.view.async_ops uses tokio_console.view.table, so a change to tokio_console.view.table can break tokio_console.view.async_ops, while a change to tokio_console.view.async_ops can't break tokio_console.view.table.
- Position
- Below the diagonal: tokio_console.view.async_ops uses a module listed above it, which is the healthy direction.
35→8 tokio_console.view.resource uses console_api.generated.rs.tokio.console.resources✕
- Connections
- 1 pair of types, where a type in tokio_console.view.resource uses a type in console_api.generated.rs.tokio.console.resources.
- The types involved
tokio_console.view.resource.ResourceView→console_api.generated.rs.tokio.console.resources.Resource
- Direction
- tokio_console.view.resource uses console_api.generated.rs.tokio.console.resources, so a change to console_api.generated.rs.tokio.console.resources can break tokio_console.view.resource, while a change to tokio_console.view.resource can't break console_api.generated.rs.tokio.console.resources.
- Position
- Below the diagonal: tokio_console.view.resource uses a module listed above it, which is the healthy direction.
35→10 tokio_console.view.resource uses console_api.generated.rs.tokio.console.instrument✕
- Connections
- 1 pair of types, where a type in tokio_console.view.resource uses a type in console_api.generated.rs.tokio.console.instrument.
- The types involved
tokio_console.view.resource.ResourceView→console_api.generated.rs.tokio.console.instrument.State
- Direction
- tokio_console.view.resource uses console_api.generated.rs.tokio.console.instrument, so a change to console_api.generated.rs.tokio.console.instrument can break tokio_console.view.resource, while a change to tokio_console.view.resource can't break console_api.generated.rs.tokio.console.instrument.
- Position
- Below the diagonal: tokio_console.view.resource uses a module listed above it, which is the healthy direction.
35→13 tokio_console.view.resource uses console_api.generated.rs.tokio.console.trace.trace_event✕
- Connections
- 1 pair of types, where a type in tokio_console.view.resource uses a type in console_api.generated.rs.tokio.console.trace.trace_event.
- The types involved
tokio_console.view.resource.ResourceView→console_api.generated.rs.tokio.console.trace.trace_event.Event
- Direction
- tokio_console.view.resource uses console_api.generated.rs.tokio.console.trace.trace_event, so a change to console_api.generated.rs.tokio.console.trace.trace_event can break tokio_console.view.resource, while a change to tokio_console.view.resource can't break console_api.generated.rs.tokio.console.trace.trace_event.
- Position
- Below the diagonal: tokio_console.view.resource uses a module listed above it, which is the healthy direction.
35→18 tokio_console.view.resource uses tokio_console.view.styles✕
- Connections
- 1 pair of types, where a type in tokio_console.view.resource uses a type in tokio_console.view.styles.
- The types involved
tokio_console.view.resource.ResourceView→tokio_console.view.styles.Styles
- Direction
- tokio_console.view.resource uses tokio_console.view.styles, so a change to tokio_console.view.styles can break tokio_console.view.resource, while a change to tokio_console.view.resource can't break tokio_console.view.styles.
- Position
- Below the diagonal: tokio_console.view.resource uses a module listed above it, which is the healthy direction.
35→23 tokio_console.view.resource uses tokio_console.view.help✕
- Connections
- 1 pair of types, where a type in tokio_console.view.resource uses a type in tokio_console.view.help.
- The types involved
tokio_console.view.resource.ResourceView→tokio_console.view.help.HelpText
- Direction
- tokio_console.view.resource uses tokio_console.view.help, so a change to tokio_console.view.help can break tokio_console.view.resource, while a change to tokio_console.view.resource can't break tokio_console.view.help.
- Position
- Below the diagonal: tokio_console.view.resource uses a module listed above it, which is the healthy direction.
35→27 tokio_console.view.resource uses tokio_console.view.table✕
- Connections
- 1 pair of types, where a type in tokio_console.view.resource uses a type in tokio_console.view.table.
- The types involved
tokio_console.view.resource.ResourceView→tokio_console.view.table.TableListState
- Direction
- tokio_console.view.resource uses tokio_console.view.table, so a change to tokio_console.view.table can break tokio_console.view.resource, while a change to tokio_console.view.resource can't break tokio_console.view.table.
- Position
- Below the diagonal: tokio_console.view.resource uses a module listed above it, which is the healthy direction.
36→10 tokio_console.view.resources uses console_api.generated.rs.tokio.console.instrument✕
- Connections
- 1 pair of types, where a type in tokio_console.view.resources uses a type in console_api.generated.rs.tokio.console.instrument.
- The types involved
tokio_console.view.resources.ResourcesTable→console_api.generated.rs.tokio.console.instrument.State
- Direction
- tokio_console.view.resources uses console_api.generated.rs.tokio.console.instrument, so a change to console_api.generated.rs.tokio.console.instrument can break tokio_console.view.resources, while a change to tokio_console.view.resources can't break console_api.generated.rs.tokio.console.instrument.
- Position
- Below the diagonal: tokio_console.view.resources uses a module listed above it, which is the healthy direction.
36→18 tokio_console.view.resources uses tokio_console.view.styles✕
- Connections
- 1 pair of types, where a type in tokio_console.view.resources uses a type in tokio_console.view.styles.
- The types involved
tokio_console.view.resources.ResourcesTable→tokio_console.view.styles.Styles
- Direction
- tokio_console.view.resources uses tokio_console.view.styles, so a change to tokio_console.view.styles can break tokio_console.view.resources, while a change to tokio_console.view.resources can't break tokio_console.view.styles.
- Position
- Below the diagonal: tokio_console.view.resources uses a module listed above it, which is the healthy direction.
36→27 tokio_console.view.resources uses tokio_console.view.table✕
- Connections
- 2 pairs of types, where a type in tokio_console.view.resources uses a type in tokio_console.view.table.
- The types involved
tokio_console.view.resources.ResourcesTable→tokio_console.view.table.TableListtokio_console.view.resources.ResourcesTable→tokio_console.view.table.TableListState
- Direction
- tokio_console.view.resources uses tokio_console.view.table, so a change to tokio_console.view.table can break tokio_console.view.resources, while a change to tokio_console.view.resources can't break tokio_console.view.table.
- Position
- Below the diagonal: tokio_console.view.resources uses a module listed above it, which is the healthy direction.
37→10 tokio_console.view.tasks uses console_api.generated.rs.tokio.console.instrument✕
- Connections
- 1 pair of types, where a type in tokio_console.view.tasks uses a type in console_api.generated.rs.tokio.console.instrument.
- The types involved
tokio_console.view.tasks.TasksTable→console_api.generated.rs.tokio.console.instrument.State
- Direction
- tokio_console.view.tasks uses console_api.generated.rs.tokio.console.instrument, so a change to console_api.generated.rs.tokio.console.instrument can break tokio_console.view.tasks, while a change to tokio_console.view.tasks can't break console_api.generated.rs.tokio.console.instrument.
- Position
- Below the diagonal: tokio_console.view.tasks uses a module listed above it, which is the healthy direction.
37→18 tokio_console.view.tasks uses tokio_console.view.styles✕
- Connections
- 1 pair of types, where a type in tokio_console.view.tasks uses a type in tokio_console.view.styles.
- The types involved
tokio_console.view.tasks.TasksTable→tokio_console.view.styles.Styles
- Direction
- tokio_console.view.tasks uses tokio_console.view.styles, so a change to tokio_console.view.styles can break tokio_console.view.tasks, while a change to tokio_console.view.tasks can't break tokio_console.view.styles.
- Position
- Below the diagonal: tokio_console.view.tasks uses a module listed above it, which is the healthy direction.
37→27 tokio_console.view.tasks uses tokio_console.view.table✕
- Connections
- 2 pairs of types, where a type in tokio_console.view.tasks uses a type in tokio_console.view.table.
- The types involved
tokio_console.view.tasks.TasksTable→tokio_console.view.table.TableListtokio_console.view.tasks.TasksTable→tokio_console.view.table.TableListState
- Direction
- tokio_console.view.tasks uses tokio_console.view.table, so a change to tokio_console.view.table can break tokio_console.view.tasks, while a change to tokio_console.view.tasks can't break tokio_console.view.table.
- Position
- Below the diagonal: tokio_console.view.tasks uses a module listed above it, which is the healthy direction.
38→5 console_subscriber uses console_subscriber.builder✕
- Connections
- 2 pairs of types, where a type in console_subscriber uses a type in console_subscriber.builder.
- The types involved
console_subscriber.ConsoleLayer→console_subscriber.builder.Builderconsole_subscriber.Server→console_subscriber.builder.ServerAddr
- Direction
- console_subscriber uses console_subscriber.builder, so a change to console_subscriber.builder can break console_subscriber, while a change to console_subscriber can't break console_subscriber.builder.
- Position
- Below the diagonal: console_subscriber uses a module listed above it, which is the healthy direction.
38→11 console_subscriber uses console_api.generated.rs.tokio.console.common✕
- Connections
- 3 pairs of types, where a type in console_subscriber uses a type in console_api.generated.rs.tokio.console.common.
- The types involved
console_subscriber.ConsoleLayer→console_api.generated.rs.tokio.console.common.Idconsole_subscriber.ConsoleLayer→console_api.generated.rs.tokio.console.common.Metadataconsole_subscriber.WatchRequest→console_api.generated.rs.tokio.console.common.Id
- Direction
- console_subscriber uses console_api.generated.rs.tokio.console.common, so a change to console_api.generated.rs.tokio.console.common can break console_subscriber, while a change to console_subscriber can't break console_api.generated.rs.tokio.console.common.
- Position
- Below the diagonal: console_subscriber uses a module listed above it, which is the healthy direction.
38→13 console_subscriber uses console_api.generated.rs.tokio.console.trace.trace_event✕
- Connections
- 1 pair of types, where a type in console_subscriber uses a type in console_api.generated.rs.tokio.console.trace.trace_event.
- The types involved
console_subscriber.ConsoleLayer→console_api.generated.rs.tokio.console.trace.trace_event.Event
- Direction
- console_subscriber uses console_api.generated.rs.tokio.console.trace.trace_event, so a change to console_api.generated.rs.tokio.console.trace.trace_event can break console_subscriber, while a change to console_subscriber can't break console_api.generated.rs.tokio.console.trace.trace_event.
- Position
- Below the diagonal: console_subscriber uses a module listed above it, which is the healthy direction.
38→14 console_subscriber uses console_subscriber.attribute✕
- Connections
- 1 pair of types, where a type in console_subscriber uses a type in console_subscriber.attribute.
- The types involved
console_subscriber.ConsoleLayer→console_subscriber.attribute.Attributes
- Direction
- console_subscriber uses console_subscriber.attribute, so a change to console_subscriber.attribute can break console_subscriber, while a change to console_subscriber can't break console_subscriber.attribute.
- Position
- Below the diagonal: console_subscriber uses a module listed above it, which is the healthy direction.
38→15 console_subscriber uses console_subscriber.callsites✕
- Connections
- 1 pair of types, where a type in console_subscriber uses a type in console_subscriber.callsites.
- The types involved
console_subscriber.ConsoleLayer→console_subscriber.callsites.Callsites
- Direction
- console_subscriber uses console_subscriber.callsites, so a change to console_subscriber.callsites can break console_subscriber, while a change to console_subscriber can't break console_subscriber.callsites.
- Position
- Below the diagonal: console_subscriber uses a module listed above it, which is the healthy direction.
38→16 console_subscriber uses console_subscriber.stack✕
- Connections
- 1 pair of types, where a type in console_subscriber uses a type in console_subscriber.stack.
- The types involved
console_subscriber.ConsoleLayer→console_subscriber.stack.SpanStack
- Direction
- console_subscriber uses console_subscriber.stack, so a change to console_subscriber.stack can break console_subscriber, while a change to console_subscriber can't break console_subscriber.stack.
- Position
- Below the diagonal: console_subscriber uses a module listed above it, which is the healthy direction.
38→20 console_subscriber uses console_subscriber.record✕
- Connections
- 1 pair of types, where a type in console_subscriber uses a type in console_subscriber.record.
- The types involved
console_subscriber.ConsoleLayer→console_subscriber.record.Recorder
- Direction
- console_subscriber uses console_subscriber.record, so a change to console_subscriber.record can break console_subscriber, while a change to console_subscriber can't break console_subscriber.record.
- Position
- Below the diagonal: console_subscriber uses a module listed above it, which is the healthy direction.
38→21 console_subscriber uses console_subscriber.stats✕
- Connections
- 2 pairs of types, where a type in console_subscriber uses a type in console_subscriber.stats.
- The types involved
console_subscriber.ConsoleLayer→console_subscriber.stats.TimeAnchorconsole_subscriber.ToProto→console_subscriber.stats.TimeAnchor
- Direction
- console_subscriber uses console_subscriber.stats, so a change to console_subscriber.stats can break console_subscriber, while a change to console_subscriber can't break console_subscriber.stats.
- Position
- Below the diagonal: console_subscriber uses a module listed above it, which is the healthy direction.
38→30 console_subscriber uses console_subscriber.aggregator✕
- Connections
- 3 pairs of types, where a type in console_subscriber uses a type in console_subscriber.aggregator.
- The types involved
console_subscriber.Server→console_subscriber.aggregator.Aggregatorconsole_subscriber.ServerParts→console_subscriber.aggregator.Aggregatorconsole_subscriber.Shared→console_subscriber.aggregator.Flush
- Direction
- console_subscriber uses console_subscriber.aggregator, so a change to console_subscriber.aggregator can break console_subscriber, while a change to console_subscriber can't break console_subscriber.aggregator.
- Position
- Below the diagonal: console_subscriber uses a module listed above it, which is the healthy direction.
39→1 tokio_console.state uses console_api.generated.rs.tokio.console.common.field✕
- Connections
- 1 pair of types, where a type in tokio_console.state uses a type in console_api.generated.rs.tokio.console.common.field.
- The types involved
tokio_console.state.FieldValue→console_api.generated.rs.tokio.console.common.field.Value
- Direction
- tokio_console.state uses console_api.generated.rs.tokio.console.common.field, so a change to console_api.generated.rs.tokio.console.common.field can break tokio_console.state, while a change to tokio_console.state can't break console_api.generated.rs.tokio.console.common.field.
- Position
- Below the diagonal: tokio_console.state uses a module listed above it, which is the healthy direction.
39→6 tokio_console.state uses tokio_console.intern✕
- Connections
- 5 pairs of types, where a type in tokio_console.state uses a type in tokio_console.intern.
- The types involved
tokio_console.state.Field→tokio_console.intern.InternedStrtokio_console.state.Field→tokio_console.intern.Stringstokio_console.state.Metadata→tokio_console.intern.InternedStrtokio_console.state.Metadata→tokio_console.intern.Stringstokio_console.state.State→tokio_console.intern.Strings
- Direction
- tokio_console.state uses tokio_console.intern, so a change to tokio_console.intern can break tokio_console.state, while a change to tokio_console.state can't break tokio_console.intern.
- Position
- Below the diagonal: tokio_console.state uses a module listed above it, which is the healthy direction.
39→9 tokio_console.state uses console_api.generated.rs.tokio.console.tasks✕
- Connections
- 1 pair of types, where a type in tokio_console.state uses a type in console_api.generated.rs.tokio.console.tasks.
- The types involved
tokio_console.state.State→console_api.generated.rs.tokio.console.tasks.TaskDetails
- Direction
- tokio_console.state uses console_api.generated.rs.tokio.console.tasks, so a change to console_api.generated.rs.tokio.console.tasks can break tokio_console.state, while a change to tokio_console.state can't break console_api.generated.rs.tokio.console.tasks.
- Position
- Below the diagonal: tokio_console.state uses a module listed above it, which is the healthy direction.
39→10 tokio_console.state uses console_api.generated.rs.tokio.console.instrument✕
- Connections
- 4 pairs of types, where a type in tokio_console.state uses a type in console_api.generated.rs.tokio.console.instrument.
- The types involved
tokio_console.state.State→console_api.generated.rs.tokio.console.instrument.Statetokio_console.state.State→console_api.generated.rs.tokio.console.instrument.Temporalitytokio_console.state.State→console_api.generated.rs.tokio.console.instrument.Updatetokio_console.state.Temporality→console_api.generated.rs.tokio.console.instrument.Temporality
- Direction
- tokio_console.state uses console_api.generated.rs.tokio.console.instrument, so a change to console_api.generated.rs.tokio.console.instrument can break tokio_console.state, while a change to tokio_console.state can't break console_api.generated.rs.tokio.console.instrument.
- Position
- Below the diagonal: tokio_console.state uses a module listed above it, which is the healthy direction.
39→11 tokio_console.state uses console_api.generated.rs.tokio.console.common✕
- Connections
- 7 pairs of types, where a type in tokio_console.state uses a type in console_api.generated.rs.tokio.console.common.
- The types involved
tokio_console.state.Attribute→console_api.generated.rs.tokio.console.common.Fieldtokio_console.state.Attribute→console_api.generated.rs.tokio.console.common.Spantokio_console.state.Field→console_api.generated.rs.tokio.console.common.Fieldtokio_console.state.Field→console_api.generated.rs.tokio.console.common.Metadatatokio_console.state.Field→console_api.generated.rs.tokio.console.common.Spantokio_console.state.Metadata→console_api.generated.rs.tokio.console.common.Metadatatokio_console.state.state$module→console_api.generated.rs.tokio.console.common.Location
- Direction
- tokio_console.state uses console_api.generated.rs.tokio.console.common, so a change to console_api.generated.rs.tokio.console.common can break tokio_console.state, while a change to tokio_console.state can't break console_api.generated.rs.tokio.console.common.
- Position
- Below the diagonal: tokio_console.state uses a module listed above it, which is the healthy direction.
39→18 tokio_console.state uses tokio_console.view.styles✕
- Connections
- 3 pairs of types, where a type in tokio_console.state uses a type in tokio_console.view.styles.
- The types involved
tokio_console.state.Attribute→tokio_console.view.styles.Stylestokio_console.state.Field→tokio_console.view.styles.Stylestokio_console.state.State→tokio_console.view.styles.Styles
- Direction
- tokio_console.state uses tokio_console.view.styles, so a change to tokio_console.view.styles can break tokio_console.state, while a change to tokio_console.state can't break tokio_console.view.styles.
- Position
- Below the diagonal: tokio_console.state uses a module listed above it, which is the healthy direction.
39→25 tokio_console.state uses tokio_console.state.async_ops✕
- Connections
- 1 pair of types, where a type in tokio_console.state uses a type in tokio_console.state.async_ops.
- The types involved
tokio_console.state.State→tokio_console.state.async_ops.AsyncOpsState
- Direction
- tokio_console.state uses tokio_console.state.async_ops, so a change to tokio_console.state.async_ops can break tokio_console.state, while a change to tokio_console.state can't break tokio_console.state.async_ops.
- Position
- Below the diagonal: tokio_console.state uses a module listed above it, which is the healthy direction.
39→31 tokio_console.state uses tokio_console.state.resources✕
- Connections
- 1 pair of types, where a type in tokio_console.state uses a type in tokio_console.state.resources.
- The types involved
tokio_console.state.State→tokio_console.state.resources.ResourcesState
- Direction
- tokio_console.state uses tokio_console.state.resources, so a change to tokio_console.state.resources can break tokio_console.state, while a change to tokio_console.state can't break tokio_console.state.resources.
- Position
- Below the diagonal: tokio_console.state uses a module listed above it, which is the healthy direction.
39→32 tokio_console.state uses tokio_console.state.tasks✕
- Connections
- 1 pair of types, where a type in tokio_console.state uses a type in tokio_console.state.tasks.
- The types involved
tokio_console.state.State→tokio_console.state.tasks.TasksState
- Direction
- tokio_console.state uses tokio_console.state.tasks, so a change to tokio_console.state.tasks can break tokio_console.state, while a change to tokio_console.state can't break tokio_console.state.tasks.
- Position
- Below the diagonal: tokio_console.state uses a module listed above it, which is the healthy direction.
39→33 tokio_console.state uses tokio_console.view✕
- Connections
- 1 pair of types, where a type in tokio_console.state uses a type in tokio_console.view.
- The types involved
tokio_console.state.State→tokio_console.view.ViewState
- Direction
- tokio_console.state uses tokio_console.view, so a change to tokio_console.view can break tokio_console.state, while a change to tokio_console.state can't break tokio_console.view.
- Position
- Below the diagonal: tokio_console.state uses a module listed above it, which is the healthy direction.
40→2 console_subscriber.visitors uses console_api.generated.rs.tokio.console.common.metadata✕
- Connections
- 2 pairs of types, where a type in console_subscriber.visitors uses a type in console_api.generated.rs.tokio.console.common.metadata.
- The types involved
console_subscriber.visitors.ResourceVisitor→console_api.generated.rs.tokio.console.common.metadata.Kindconsole_subscriber.visitors.ResourceVisitorResult→console_api.generated.rs.tokio.console.common.metadata.Kind
- Direction
- console_subscriber.visitors uses console_api.generated.rs.tokio.console.common.metadata, so a change to console_api.generated.rs.tokio.console.common.metadata can break console_subscriber.visitors, while a change to console_subscriber.visitors can't break console_api.generated.rs.tokio.console.common.metadata.
- Position
- Below the diagonal: console_subscriber.visitors uses a module listed above it, which is the healthy direction.
40→10 console_subscriber.visitors uses console_api.generated.rs.tokio.console.instrument✕
- Connections
- 1 pair of types, where a type in console_subscriber.visitors uses a type in console_api.generated.rs.tokio.console.instrument.
- The types involved
console_subscriber.visitors.StateUpdateVisitor→console_api.generated.rs.tokio.console.instrument.Update
- Direction
- console_subscriber.visitors uses console_api.generated.rs.tokio.console.instrument, so a change to console_api.generated.rs.tokio.console.instrument can break console_subscriber.visitors, while a change to console_subscriber.visitors can't break console_api.generated.rs.tokio.console.instrument.
- Position
- Below the diagonal: console_subscriber.visitors uses a module listed above it, which is the healthy direction.
40→11 console_subscriber.visitors uses console_api.generated.rs.tokio.console.common✕
- Connections
- 12 pairs of types, where a type in console_subscriber.visitors uses a type in console_api.generated.rs.tokio.console.common.
- The types involved
console_subscriber.visitors.AsyncOpVisitor→console_api.generated.rs.tokio.console.common.Fieldconsole_subscriber.visitors.FieldVisitor→console_api.generated.rs.tokio.console.common.Fieldconsole_subscriber.visitors.FieldVisitor→console_api.generated.rs.tokio.console.common.MetaIdconsole_subscriber.visitors.PollOpVisitor→console_api.generated.rs.tokio.console.common.Fieldconsole_subscriber.visitors.ResourceVisitor→console_api.generated.rs.tokio.console.common.Fieldconsole_subscriber.visitors.ResourceVisitorResult→console_api.generated.rs.tokio.console.common.Locationconsole_subscriber.visitors.StateUpdateVisitor→console_api.generated.rs.tokio.console.common.Fieldconsole_subscriber.visitors.StateUpdateVisitor→console_api.generated.rs.tokio.console.common.MetaIdconsole_subscriber.visitors.TaskVisitor→console_api.generated.rs.tokio.console.common.Fieldconsole_subscriber.visitors.TaskVisitor→console_api.generated.rs.tokio.console.common.MetaIdconsole_subscriber.visitors.WakerVisitor→console_api.generated.rs.tokio.console.common.Fieldconsole_subscriber.visitors.WakerVisitor→console_api.generated.rs.tokio.console.common.Id
- Direction
- console_subscriber.visitors uses console_api.generated.rs.tokio.console.common, so a change to console_api.generated.rs.tokio.console.common can break console_subscriber.visitors, while a change to console_subscriber.visitors can't break console_api.generated.rs.tokio.console.common.
- Position
- Below the diagonal: console_subscriber.visitors uses a module listed above it, which is the healthy direction.
40→14 console_subscriber.visitors uses console_subscriber.attribute✕
- Connections
- 1 pair of types, where a type in console_subscriber.visitors uses a type in console_subscriber.attribute.
- The types involved
console_subscriber.visitors.StateUpdateVisitor→console_subscriber.attribute.UpdateOp
- Direction
- console_subscriber.visitors uses console_subscriber.attribute, so a change to console_subscriber.attribute can break console_subscriber.visitors, while a change to console_subscriber.visitors can't break console_subscriber.attribute.
- Position
- Below the diagonal: console_subscriber.visitors uses a module listed above it, which is the healthy direction.
40→38 console_subscriber.visitors uses console_subscriber✕
- Connections
- 1 pair of types, where a type in console_subscriber.visitors uses a type in console_subscriber.
- The types involved
console_subscriber.visitors.WakerVisitor→console_subscriber.WakeOp
- Direction
- console_subscriber.visitors uses console_subscriber, so a change to console_subscriber can break console_subscriber.visitors, while a change to console_subscriber.visitors can't break console_subscriber.
- Position
- Below the diagonal: console_subscriber.visitors 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 | 54 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 12 | Medium |
Roadmap
First, implement a global authentication guard with explicit public opt-outs and named role rules to protect all endpoints by default. Next, secure the deployment by adding essential security headers, prioritizing Content-Security-Policy, directly within the build container or server configuration. Then, address the thirty orphaned files to ensure codebase freshness, starting with mod.rs, resources.rs, and async_ops.rs. Finally, document significant design decisions in a dedicated ADR folder to establish clear architectural context.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Protect endpoints by default-deny: a global authentication guard or middleware with explicit public opt-outs, or a guard on every route, plus named role/permission rules for what an authenticated caller may do. | +12.2 pts | Medium | Access Controls |
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +5.7 pts | Low | ADR Quality |
| Resolve the 6 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4), REDACTED, REDACTED. | +3.2 pts | Low | Static Analysis (SAST) |
| Set security response headers on the surface this repository serves: an `add_header` directive per header in the nginx/Caddy/Apache config, a `_headers` / `vercel.json` / `netlify.toml` entry for a static host, or `helmet()` in the HTTP server. `Content-Security-Policy` is the one that pays for itself first — it is what contains an injected script once one reaches the page — followed by `X-Content-Type-Options: nosniff` and a frame policy (`X-Frame-Options: DENY`, or CSP `frame-ancestors`). Where the app is served from a build container, the header configuration belongs in the image beside the built assets, so it ships with them rather than depending on where it lands. | +5.0 pts | Medium | Web-Security Posture |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +4.7 pts | Medium | Architecture documentation |
| Resolve the 30 Orphaned file finding(s) in Knowledge Freshness — start with mod.rs (2), resources.rs (2), async_ops.rs (2). | +4.6 pts | Medium | Knowledge Freshness |
| Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). | +1.3 pts | Low | Static Analysis (SAST) |
| Improve Dependency Hygiene — currently 8.6/10. | +2.0 pts | Medium | Dependency Hygiene |
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 | 3.0 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| console-subscriber/src/aggregator/mod.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| console-subscriber/src/lib.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| tokio-console/src/view/tasks.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| tokio-console/src/view/task.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| REDACTED | 6.1 | Mixed | Dependency Vulnerabilities: Medium advisory (unsound): REDACTED |
| tokio-console/src/view/async_ops.rs | 7.1 | Near-clean | God Classes: MethodTooLong: AsyncOpsTable.render |
| tokio-console/src/main.rs | 7.2 | Near-clean | Cyclomatic Complexity: tokio_console::main (cyclomatic 24) |
| tokio-console/src/state/tasks.rs | 7.2 | Near-clean | Cyclomatic Complexity: TasksState::update_tasks (cyclomatic 21) |
| tokio-console/src/state/async_ops.rs | 7.2 | Near-clean | Code Duplication: Duplicated block (13–14 lines × 2) |
| tokio-console/src/state/mod.rs | 7.3 | Near-clean | Explicit Debt: TodoComment |
| console-subscriber/src/record.rs | 7.3 | Near-clean | Explicit Debt: TodoComment |
| console-subscriber/src/stats.rs | 7.3 | Near-clean | Explicit Debt: TodoComment |
| console-subscriber/src/visitors.rs | 7.4 | Near-clean | Code Duplication: Members sharing a duplicated core (4 members, 50+ identical tokens) |
| tokio-console/src/view/mini_histogram.rs | 7.8 | Near-clean | Cyclomatic Complexity: MiniHistogram::render_bars (cyclomatic 17) |
| tokio-console/src/view/mod.rs | 7.8 | Near-clean | Cyclomatic Complexity: View::update_input (cyclomatic 17) |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 52 of 52 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
What we checked — 52 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, 173 of 214 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Watchdog duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
| LLM (sampled · advisory) | Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement | — | ◐ LLM · sampled · advisory |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.rs) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage read, produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
- D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D24 Comment Value — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D27 Navigability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- AXR1 Runtime accessibility — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DevServer (dev). the dev server did not expose a crawlable HTTP endpoint in time — no runtime evidence.
- GD1 Unfinished & placeholder code — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- M4 Documentation accuracy — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- X12 Unreachable branch — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X13 Undrained process stream — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X16 Unfloored truncation loop — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X17 Uncapped recursion over a caller-supplied document — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X18 Disposal-pattern correctness — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X19 Unrestored process-global state — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X22 Contradicted release guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Java, TypeScript/JavaScript, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X23 Unguarded diagnostic materialisation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X24 Document value interpolated into markup unescaped — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X25 Inert configuration knob — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart and Ruby source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart or Ruby was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X3 Exception handling — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go and JavaScript/TypeScript source only, and no C# was loaded and no PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go, JavaScript or TypeScript was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X5 Nullable reference types — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax and MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, and Kotlin source only, and no C# was loaded, no TypeScript was found, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D11 Test Reliability: Flakiness is inferred from history/markers — Watchdog runs the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- 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.
- M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
6 function(s) exceeded the cyclomatic complexity threshold of 15; the worst was tokio_console::main at 24. A further 1 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 Styles::time_units at 24 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold functions was excluded, so the exclusion is disclosed nowhere in the file itself: tokio-console/src/view/styles.rs (Styles::time_units at 24). 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 tokio_console::main (cyclomatic 24), TasksState::update_tasks (cyclomatic 21), MiniHistogram::render_bars (cyclomatic 17). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 6 together lifts Cyclomatic Complexity from 9.0 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
10 function(s) exceeded the cognitive complexity threshold of 15; the worst was ConsoleLayer::on_event at 42.
What to do
- Bring the 10 bodies over 15 down to 15 or less in Cognitive Complexity — start with ConsoleLayer::on_event (cognitive 42), tokio_console::main (cognitive 41), View::update_input (cognitive 30). — 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 10 together lifts Cognitive Complexity from 8.1 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
10 god class(es) detected.
What to do
- Resolve the 5 MethodTooLong finding(s) in God Classes — start with tasks.rs (2), task.rs, async_ops.rs. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 2 FileTooLong finding(s) in God Classes — start with lib.rs, config.rs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 FunctionTooLong finding(s) in God Classes — start with main.rs. — One of this dimension's main actionable groups (1 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
13 duplicated block group(s) detected. A further 2 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.
What to do
- Resolve the 1 Near-duplicate member family (3 members, 67 shared lines) finding(s) in Code Duplication — start with async_ops.rs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Members sharing a duplicated core (4 members, 50+ identical tokens) finding(s) in Code Duplication — start with visitors.rs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (34–35 lines × 3) finding(s) in Code Duplication — start with async_ops.rs. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
4 production modules (Cargo), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 0 module(s) off the main sequence, with abstractness counted on 3 of the 4 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
D6 · Cohesion (LCOM4)
0 of 49 classes have LCOM4 above 3.
D9 · Test Distribution
25 test methods: 6 unit, 19 integration, 0 BDD, 0 e2e. The Rust suite contributes 25 `#[test]` function(s) across 9 file(s) declaring at least one; its unit/integration split is Cargo's own — 6 of those file(s) are integration-test targets under a crate's tests/ directory, and the rest are #[test] functions compiled into the crate they test.
D11 · Test Reliability
0 flaky across 1 measured tier(s). Rust (repository root, 9 test files): measured (0 flaky).
D12 · Dependency Hygiene
29 outdated, 0 yanked direct Cargo dependencies. Only DIRECT edges are graded: a transitive crate cannot be moved past what its parent's requirement admits, so reporting one would be advice its owner cannot take. A newer release is reported only where this repository's OWN requirement already admits it, so the remedy is `cargo update` and never a manifest edit — which means a release outside the declared range is deliberately NOT charged, because a written-down constraint is a decision rather than a defect. Note that a bare requirement is a CARET, and for a 0.x crate its ceiling is the minor. Whether any crate is UNMAINTAINED is not graded — crates.io publishes no maintenance status, and release age does not stand in for one. Known CVEs in this dependency graph are D30's question, read from REDACTED there.
What to do
- Improve Dependency Hygiene — currently 8.6/10. — 29 outdated, 0 yanked direct Cargo dependencies. Only DIRECT edges are graded: a transitive crate cannot be moved past what its parent's requirement admits, so reporting one would be advice its owner cannot take. A newer release is reported only where this repository's OWN requirement already admits it, so the remedy is `cargo update` and never a manifest edit — which means a release outside the declared range is deliberately NOT charged, because a written-down constraint is a decision rather than a defect. Note that a bare requirement is a CARET, and for a 0.x crate its ceiling is the minor. Whether any crate is UNMAINTAINED is not graded — crates.io publishes no maintenance status, and release age does not stand in for one. Known CVEs in this dependency graph are D30's question, read from REDACTED there.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 274 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository's REDACTED closed over its manifests' `[dependencies]` and `[build-dependencies]`. Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D16 · Bus Factor
No source file's living knowledge is concentrated in a single author. Counted over 35 of the 48 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D17 · Explicit Debt
31 deducted task-comment markers across 11546 LoC (0.2/KLoC) → score 9.5. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 25 TodoComment finding(s) in Explicit Debt — start with lib.rs (7), mod.rs (5), task.rs (2). — One of this dimension's main actionable groups (25 warning-level).
- Resolve the 4 XxxComment finding(s) in Explicit Debt — start with lib.rs (4). — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 2 FixmeComment finding(s) in Explicit Debt — start with resources.rs, subscriber.rs. — One of this dimension's main actionable groups (2 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 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. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
0 of 4 build units (Cargo) flagged as possibly oversized/incoherent.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
54 finding(s): 0 critical, 53 high, 1 medium, 0 low. 44 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. Separately, one or more rules could not re-parse an embedded snippet in 2 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 6 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4), REDACTED, REDACTED. — One of this dimension's main actionable groups (6 issue-level).
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- No action in Static Analysis (SAST) — all 44 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 (44 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
4 finding(s): 0 critical, 0 high, 4 medium, 0 low.
What to do
- Resolve the 2 Medium advisory (unsound) finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Medium vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
D34 · Knowledge Freshness
33 of 35 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is console-subscriber/src/lib.rs. Counted over 35 of the 48 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 30 Orphaned file finding(s) in Knowledge Freshness — start with mod.rs (2), resources.rs (2), async_ops.rs (2). — One of this dimension's main actionable groups (30 recommendation-level).
- Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with lib.rs, mod.rs, tasks.rs. — One of this dimension's main actionable groups (3 recommendation-level).
- Resolve the 1 Concentrated knowledge decay finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D37 · Vulnerability-disclosure Policy
A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX4 · Dependency direction
AX9 · CQS / query purity
C2 · Access Controls
- This repository serves requests — a server (Server::builder()) (console-subscriber/src/builder.rs:552) — and no route guard, auth-gate middleware, global guard or imperative check that refuses a caller (401/403, an Unauthorized/Forbidden error) was found: its endpoints may be unprotected. — console-subscriber/src/builder.rs:552
What to do
- Protect endpoints by default-deny: a global authentication guard or middleware with explicit public opt-outs, or a guard on every route, plus named role/permission rules for what an authenticated caller may do.
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Add a README to the 1 of 5 project(s) that lack one — worth up to 0.4 pts.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
- Only 2/3 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `xtask`.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
- Consider OpenTelemetry tracing/metrics (opentelemetry with tracing-opentelemetry) and a health-check endpoint (a /health route on your axum/actix router) for operability.
P3 · Security & performance tooling
What to do
- Enable Dependabot/Renovate or a dependency-review gate.
- 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
What to do
- Stamp a version in your build/package manifest (e.g. csproj <Version>, package.json, pyproject.toml, Cargo.toml, or a VERSION file) or tag releases with semver so builds and releases are traceable.
PF3 · Async & latency hygiene
S1 · Web-Security Posture
- None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. This is reported because `netlify.toml` configures this repository's static hosting, including its response headers, so the configuration that would carry these headers is in this repository and was read in full. (−2.0 on this card.) — netlify.toml:1
- This repository starts an HTTP server and nothing in its Rust source or committed `Rocket.toml` secures the transport: no TLS served (actix-web `bind_rustls`/`bind_openssl`, axum-server `bind_rustls` with a `RustlsConfig`, tonic `ServerTlsConfig`, a `TlsAcceptor`, Rocket's `[default.tls]`), no `Strict-Transport-Security` header, no `X-Forwarded-Proto` read from a TLS-terminating proxy — so its traffic may cross the network in clear text. (−2.0 on this card.) The server: `Server::builder()` (console-subscriber/src/builder.rs:552).
What to do
- Set security response headers on the surface this repository serves: an `add_header` directive per header in the nginx/Caddy/Apache config, a `_headers` / `vercel.json` / `netlify.toml` entry for a static host, or `helmet()` in the HTTP server. `Content-Security-Policy` is the one that pays for itself first — it is what contains an injected script once one reaches the page — followed by `X-Content-Type-Options: nosniff` and a frame policy (`X-Frame-Options: DENY`, or CSP `frame-ancestors`). Where the app is served from a build container, the header configuration belongs in the image beside the built assets, so it ships with them rather than depending on where it lands.
- Secure the server's transport: serve TLS itself (`HttpServer::bind_rustls_0_23(addr, config)` in actix-web, `axum_server::bind_rustls(addr, RustlsConfig::from_pem_file(…))`, tonic's `Server::builder().tls_config(ServerTlsConfig::new().identity(…))`, Rocket's `[default.tls]`), or run it behind a TLS-terminating proxy and check `X-Forwarded-Proto`; send `Strict-Transport-Security` once it is HTTPS-only.
X1 · Async correctness
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X21 · Side-effecting pattern guard
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X30 · Support guard that admits what it rejects
X4 · Structured logging
- `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`. — tokio-console/src/conn.rs:170
- `warn!` at line 80 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`. — console-subscriber/src/attribute.rs:80
- `warn!` at line 93 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`. — console-subscriber/src/attribute.rs:93
- `warn!` 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: `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`. — console-subscriber/src/attribute.rs:100
What to do
- Interpolated log message defeats structured logging
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 82% | Strong | Solid. |
| Architecture | 97% | Exemplary | Solid. |
| Maturity | 56% | Adequate — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 64% | Strong | Solid. |
| Security | 37% | Weak — gated by D29, D36, C2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
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 — 68 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: this repository's JavaScript 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; this repository's TypeScript 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.
- 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. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- 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 — no exported interface declares behaviour
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — the dev server did not expose a crawlable HTTP endpoint in time — no runtime evidence This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no data at rest for these controls to protect.
- 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 — ~1763 lines of test source are present (.rs) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — Naming consistency is measured on C# only; Rust, TypeScript not measured.
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed Rust surface was not measured.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ projects each declaring an entity of their own. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C# and Visual Basic comments only — this repository's production source is .rs, .tsx, 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.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (10 value object(s))
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HTTP client call or construction in the Rust source (service entry point: console-subscriber/src/builder.rs:552 (tonic::transport::Server))
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `#[bench]`, criterion's `bench_function`/`bench_with_input`, `#[divan::bench]` or `#[library_benchmark]` in any `.rs` file, or criterion, divan, iai or a `[[bench]]` target in a Cargo.toml, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not applicable: Rust spells out every heap allocation and makes borrowed slices (&[T], &str) its ordinary parameter types, so the allocation-aware style this card rewards elsewhere is the language's baseline rather than a rung to climb.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X12 Unreachable branch — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X13 Undrained process stream — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X16 Unfloored truncation loop — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X17 Uncapped recursion over a caller-supplied document — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X18 Disposal-pattern correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X19 Unrestored process-global state — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X2 Cancellation propagation — no C# was loaded; this repository's Rust was read, and no request in it can be cancelled by a caller — a Rust request takes no token: a future is cancelled by dropping it, from outside the call (select!, a timeout, an aborted task), and reqwest, hyper and tonic take none
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X22 Contradicted release guard — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X23 Unguarded diagnostic materialisation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X24 Document value interpolated into markup unescaped — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X25 Inert configuration knob — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. Rust's compiler refuses the unsynchronised version: a collection shared between a callback's thread and the waiting body must be `Sync`, which a `Vec`, `VecDeque` or `HashMap` is only behind a `Mutex`/`RwLock`, so the race this check looks for cannot be written in safe Rust. Not a gap in the analyzer and not a finding about your code.
- X3 Exception handling — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- 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.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 53 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 83 finding(s)
- TodoComment tokio-console/src/input.rs:1
- TodoComment tokio-console/src/warnings.rs:48
- TodoComment tokio-console/src/view/styles.rs:342
- TodoComment tokio-console/src/view/table.rs:65
- TodoComment tokio-console/src/view/task.rs:35
- TodoComment tokio-console/src/view/task.rs:65
- TodoComment tokio-console/src/view/tasks.rs:206
- TodoComment tokio-console/src/state/mod.rs:56
- TodoComment tokio-console/src/state/mod.rs:477
- TodoComment tokio-console/src/state/store.rs:107
- TodoComment console-subscriber/src/lib.rs:90
- TodoComment console-subscriber/src/lib.rs:95
- TodoComment console-subscriber/src/lib.rs:100
- TodoComment console-subscriber/src/lib.rs:105
- TodoComment console-subscriber/src/lib.rs:110
- TodoComment console-subscriber/src/lib.rs:115
- TodoComment console-subscriber/src/lib.rs:760
- TodoComment console-subscriber/src/record.rs:19
- TodoComment console-subscriber/src/record.rs:103
- TodoComment console-subscriber/src/stats.rs:239
- TodoComment console-subscriber/src/stats.rs:435
- TodoComment console-subscriber/src/aggregator/mod.rs:487
- TodoComment console-subscriber/src/aggregator/mod.rs:658
- TodoComment console-subscriber/src/aggregator/mod.rs:661
- TodoComment console-subscriber/src/aggregator/shrink.rs:148
- MethodTooLong: TasksTable.render tokio-console/src/view/tasks.rs:48
- MethodTooLong: TaskView.render tokio-console/src/view/task.rs:38
- MethodTooLong: AsyncOpsTable.render tokio-console/src/view/async_ops.rs:59
- MethodTooLong: ResourcesTable.render tokio-console/src/view/resources.rs:53
- MethodTooLong: TasksState.update_tasks tokio-console/src/state/tasks.rs:151
- XxxComment console-subscriber/src/lib.rs:503
- XxxComment console-subscriber/src/lib.rs:511
- XxxComment console-subscriber/src/lib.rs:693
- XxxComment console-subscriber/src/lib.rs:885
- FixmeComment tokio-console/src/state/resources.rs:104
- FixmeComment console-subscriber/tests/support/subscriber.rs:334
- ConsoleLayer::on_event (cognitive 42) console-subscriber/src/lib.rs:687
- ConsoleLayer::on_new_span (cognitive 19) console-subscriber/src/lib.rs:577
- tokio_console::main (cognitive 41) tokio-console/src/main.rs:30
- tokio_console::watch_details_stream (cognitive 18) tokio-console/src/main.rs:212
- FileTooLong: src/lib.rs console-subscriber/src/lib.rs
- FileTooLong: src/config.rs tokio-console/src/config.rs
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No authorization console-subscriber/src/builder.rs:552
- tokio_console::main (cyclomatic 24) tokio-console/src/main.rs:30
- TasksState::update_tasks (cyclomatic 21) tokio-console/src/state/tasks.rs:151
- MiniHistogram::render_bars (cyclomatic 17) tokio-console/src/view/mini_histogram.rs:124
- View::update_input (cyclomatic 17) tokio-console/src/view/mod.rs:110
- Aggregator::run (cyclomatic 16) console-subscriber/src/aggregator/mod.rs:174
- ConsoleLayer::on_event (cyclomatic 16) console-subscriber/src/lib.rs:687
- View::update_input (cognitive 30) tokio-console/src/view/mod.rs:110
- Connection::connect (cognitive 22) tokio-console/src/conn.rs:87
- Aggregator::run (cognitive 21) console-subscriber/src/aggregator/mod.rs:174
- TasksState::update_tasks (cognitive 21) tokio-console/src/state/tasks.rs:151
- MiniHistogram::render_bars (cognitive 20) tokio-console/src/view/mini_histogram.rs:124
- TasksTable::render (cognitive 18) tokio-console/src/view/tasks.rs:48
- REDACTED
- FunctionTooLong: tokio_console::main tokio-console/src/main.rs:30
- TooManyMethods: Task tokio-console/src/state/tasks.rs:78
- ClassTooLong: ConsoleLayer console-subscriber/src/lib.rs:66
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Near-duplicate member family (3 members, 67 shared lines) tokio-console/src/view/async_ops.rs:66
- Members sharing a duplicated core (4 members, 50+ identical tokens) console-subscriber/src/visitors.rs:469
- Duplicated block (34–35 lines × 3) tokio-console/src/view/async_ops.rs:158
- Duplicated block (18–27 lines × 2) tokio-console/src/view/task.rs:91
- Duplicated block (22–25 lines × 2) tokio-console/src/view/resources.rs:185
- Duplicated block (20–23 lines × 3) tokio-console/src/view/async_ops.rs:198
- Duplicated block (21 lines × 2) console-subscriber/src/lib.rs:950
- Duplicated block (13–14 lines × 2) tokio-console/src/state/async_ops.rs:289
- Duplicated block (12 lines × 3) tokio-console/src/view/async_ops.rs:114
- Duplicated block (11 lines × 2) console-subscriber/src/attribute.rs:74
- Duplicated block (10 lines × 4) console-subscriber/src/visitors.rs:470
- Duplicated block (10 lines × 2) console-subscriber/src/visitors.rs:179
- Duplicated block (5 lines × 2) tokio-console/src/state/async_ops.rs:307
- Duplicated block (6 lines × 2) tokio-console/src/state/async_ops.rs:244
- Duplicated block (6 lines × 3) tokio-console/src/state/async_ops.rs:304
Minor — 49 finding(s)
- Orphaned file tokio-console/src/config.rs:1
- Orphaned file tokio-console/src/state/mod.rs:1
- Orphaned file console-subscriber/src/stats.rs:1
- Orphaned file console-subscriber/src/visitors.rs:1
- Orphaned file tokio-console/src/view/styles.rs:1
- Orphaned file tokio-console/src/state/resources.rs:1
- Orphaned file tokio-console/src/conn.rs:1
- Orphaned file tokio-console/src/view/tasks.rs:1
- Orphaned file tokio-console/src/view/task.rs:1
- Orphaned file tokio-console/src/state/async_ops.rs:1
- Orphaned file tokio-console/src/warnings.rs:1
- Orphaned file tokio-console/src/view/mod.rs:1
- Orphaned file tokio-console/src/main.rs:1
- Orphaned file tokio-console/src/view/table.rs:1
- Orphaned file tokio-console/src/view/async_ops.rs:1
- Orphaned file tokio-console/src/view/resources.rs:1
- Orphaned file tokio-console/src/state/store.rs:1
- Orphaned file console-api/src/common.rs:1
- Orphaned file console-subscriber/src/aggregator/shrink.rs:1
- Orphaned file tokio-console/src/view/controls.rs:1
- Orphaned file console-subscriber/src/callsites.rs:1
- Orphaned file tokio-console/src/view/resource.rs:1
- Orphaned file console-subscriber/src/record.rs:1
- Orphaned file xtask/src/main.rs:1
- Orphaned file tokio-console/src/view/durations.rs:1
- Interpolated log message defeats structured logging tokio-console/src/conn.rs:170
- Interpolated log message defeats structured logging console-subscriber/src/attribute.rs:80
- Interpolated log message defeats structured logging console-subscriber/src/attribute.rs:93
- Interpolated log message defeats structured logging console-subscriber/src/attribute.rs:100
- Most significant orphaned file console-subscriber/src/lib.rs:1
- Most significant orphaned file console-subscriber/src/aggregator/mod.rs:1
- Most significant orphaned file tokio-console/src/state/tasks.rs:1
- No ADRs found
- Concentrated knowledge decay
- REDACTED
- REDACTED
- REDACTED
- Inverted test pyramid
- No ADRs
- No architecture diagram/doc
- Logging is not universal
- No release approval gate
- No security response headers detected netlify.toml:1
- No app-layer HTTPS enforcement detected
Minor — 29 finding(s)
- Outdated: cfg-if
- Outdated: clap
- Outdated: clap_complete
- Outdated: crossbeam-channel
- Outdated: crossbeam-utils
- Outdated: futures
- Outdated: futures-core
- Outdated: futures-task
- Outdated: h2
- Outdated: hdrhistogram
- Outdated: humantime
- Outdated: hyper-util
- Outdated: once_cell
- Outdated: prost
- Outdated: prost-types
- Outdated: regex
- Outdated: serde
- Outdated: serde_json
- Outdated: thread_local
- Outdated: tokio
- Outdated: tokio-stream
- Outdated: tonic
- Outdated: tonic-prost
- Outdated: tonic-prost-build
- Outdated: tower
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-bd0b4ddc1a2b442b94a186344e819e06/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-bd0b4ddc1a2b442b94a186344e819e06/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude console-api/src/generated --exclude console-subscriber/examples/grpc_web/app/src/gen . | 54 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 4 | artifacts/raw/trivy-fs.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 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 0 | artifacts/raw/trivy-fs.json |