Executive summary
tower-rs/tower falls short of our standard for a preview release, in part because we found no recorded design decisions and no architecture document or diagram. It scores 61 out of 100 and is rated Adequate, and all 23 of its critical findings are security problems in the build pipeline.
Maturity, at 51, is the weakest lens and counts most in the score. The best first step is improving the documentation, worth about 9 points. Recording design decisions comes next, worth about 8 points. Raising Maturity to 62 would lift the score to about 66.
Twenty-one pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Two secrets can leak from the build pipeline. Pinning each tool to an exact version and limiting each secret to its own step would close both risks.
The product code is 12,306 lines, about €16,000 to rebuild.
If Maturity rose from 51 to 62, the lowest score rated Strong, the score would rise from 61 to about 66.
New since the last survey: 3 findings
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
Fixed since the last survey: 1 finding
- Supply-chain Provenance & Signing REDACTED
Rebuild cost: about €16,000 · Estimate
| Cost to rebuild | €5,200 to €26,000, for 87 to 277 hours of work, about 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 61. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 12,306 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 tower.load | 2 tower.sealed | 3 tower.util.call_all.common | 4 tower.filter.future | 5 tower_service | 6 tower.hedge.delay | 7 tower_layer | 8 tower.filter.layer | 9 tower.hedge | 10 tower.limit.rate.layer | 11 tower.spawn_ready.layer | 12 tower_layer.layer_fn | 13 tower.balance.p2c.service | 14 tower.buffer.future | 15 tower.buffer.worker | 16 tower.filter | 17 tower.limit.concurrency.service | 18 tower.limit.rate.service | 19 tower.load.constant | 20 tower.make.make_service | 21 tower.reconnect | 22 tower.reconnect.future | 23 tower.retry | 24 tower.util.and_then | 25 tower.util.boxed.sync | 26 tower.util.boxed.unsync | 27 tower.util.boxed_clone | 28 tower.util.either | 29 tower.util.map_err | 30 tower.util.map_future | 31 tower.util.map_request | 32 tower.util.map_response | 33 tower.util.map_result | 34 tower.util.then | 35 tower.buffer.service | 36 tower.load.peak_ewma | 37 tower.load.pending_requests | 38 tower.retry.future | 39 tower.spawn_ready.service | 40 tower.util |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 tower.load | ||||||||||||||||||||||||||||||||||||||||
| 2 tower.sealed | ||||||||||||||||||||||||||||||||||||||||
| 3 tower.util.call_all.common | ||||||||||||||||||||||||||||||||||||||||
| 4 tower.filter.future | 1 | |||||||||||||||||||||||||||||||||||||||
| 5 tower_service | 1 | |||||||||||||||||||||||||||||||||||||||
| 6 tower.hedge.delay | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 7 tower_layer | 1 | |||||||||||||||||||||||||||||||||||||||
| 8 tower.filter.layer | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 9 tower.hedge | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 10 tower.limit.rate.layer | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 11 tower.spawn_ready.layer | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 12 tower_layer.layer_fn | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 13 tower.balance.p2c.service | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 14 tower.buffer.future | 1 | |||||||||||||||||||||||||||||||||||||||
| 15 tower.buffer.worker | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 tower.filter | 2 | 2 | 2 | |||||||||||||||||||||||||||||||||||||
| 17 tower.limit.concurrency.service | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 18 tower.limit.rate.service | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 19 tower.load.constant | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 20 tower.make.make_service | 1 | 2 | 3 | |||||||||||||||||||||||||||||||||||||
| 21 tower.reconnect | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 22 tower.reconnect.future | 1 | |||||||||||||||||||||||||||||||||||||||
| 23 tower.retry | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 24 tower.util.and_then | 2 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 25 tower.util.boxed.sync | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 26 tower.util.boxed.unsync | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 27 tower.util.boxed_clone | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 28 tower.util.either | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 29 tower.util.map_err | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 30 tower.util.map_future | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 31 tower.util.map_request | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 32 tower.util.map_response | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 33 tower.util.map_result | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 34 tower.util.then | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 35 tower.buffer.service | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 36 tower.load.peak_ewma | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 37 tower.load.pending_requests | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 38 tower.retry.future | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 39 tower.spawn_ready.service | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 40 tower.util | 1 | 1 | 2 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 |
4→9 tower.filter.future uses tower.hedge part of a loop✕
- Connections
- 1 pair of types, where a type in tower.filter.future uses a type in tower.hedge.
- The types involved
tower.filter.future.AsyncResponseFuture→tower.hedge.Future
- Direction
- tower.filter.future uses tower.hedge, so a change to tower.hedge can break tower.filter.future, while a change to tower.filter.future can't break tower.hedge.
- 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.
5→9 tower_service uses tower.hedge part of a loop✕
- Connections
- 1 pair of types, where a type in tower_service uses a type in tower.hedge.
- The types involved
tower_service.Service→tower.hedge.Future
- Direction
- tower_service uses tower.hedge, so a change to tower.hedge can break tower_service, while a change to tower_service can't break tower.hedge.
- 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.
6→4 tower.hedge.delay uses tower.filter.future✕
- Connections
- 1 pair of types, where a type in tower.hedge.delay uses a type in tower.filter.future.
- The types involved
tower.hedge.delay.ResponseFuture→tower.filter.future.State
- Direction
- tower.hedge.delay uses tower.filter.future, so a change to tower.filter.future can break tower.hedge.delay, while a change to tower.hedge.delay can't break tower.filter.future.
- Position
- Below the diagonal: tower.hedge.delay uses a module listed above it, which is the healthy direction.
6→5 tower.hedge.delay uses tower_service✕
- Connections
- 1 pair of types, where a type in tower.hedge.delay uses a type in tower_service.
- The types involved
tower.hedge.delay.Delay→tower_service.Service
- Direction
- tower.hedge.delay uses tower_service, so a change to tower_service can break tower.hedge.delay, while a change to tower.hedge.delay can't break tower_service.
- Position
- Below the diagonal: tower.hedge.delay uses a module listed above it, which is the healthy direction.
6→9 tower.hedge.delay uses tower.hedge part of a loop✕
- Connections
- 2 pairs of types, where a type in tower.hedge.delay uses a type in tower.hedge.
- The types involved
tower.hedge.delay.Delay→tower.hedge.Futuretower.hedge.delay.ResponseFuture→tower.hedge.Future
- Direction
- tower.hedge.delay uses tower.hedge, so a change to tower.hedge can break tower.hedge.delay, while a change to tower.hedge.delay can't break tower.hedge.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→5 tower_layer uses tower_service✕
- Connections
- 1 pair of types, where a type in tower_layer uses a type in tower_service.
- The types involved
tower_layer.Layer→tower_service.Service
- Direction
- tower_layer uses tower_service, so a change to tower_service can break tower_layer, while a change to tower_layer can't break tower_service.
- Position
- Below the diagonal: tower_layer uses a module listed above it, which is the healthy direction.
8→5 tower.filter.layer uses tower_service✕
- Connections
- 2 pairs of types, where a type in tower.filter.layer uses a type in tower_service.
- The types involved
tower.filter.layer.AsyncFilterLayer→tower_service.Servicetower.filter.layer.FilterLayer→tower_service.Service
- Direction
- tower.filter.layer uses tower_service, so a change to tower_service can break tower.filter.layer, while a change to tower.filter.layer can't break tower_service.
- Position
- Below the diagonal: tower.filter.layer uses a module listed above it, which is the healthy direction.
8→7 tower.filter.layer uses tower_layer✕
- Connections
- 2 pairs of types, where a type in tower.filter.layer uses a type in tower_layer.
- The types involved
tower.filter.layer.AsyncFilterLayer→tower_layer.Layertower.filter.layer.FilterLayer→tower_layer.Layer
- Direction
- tower.filter.layer uses tower_layer, so a change to tower_layer can break tower.filter.layer, while a change to tower.filter.layer can't break tower_layer.
- Position
- Below the diagonal: tower.filter.layer uses a module listed above it, which is the healthy direction.
9→5 tower.hedge uses tower_service✕
- Connections
- 1 pair of types, where a type in tower.hedge uses a type in tower_service.
- The types involved
tower.hedge.Hedge→tower_service.Service
- Direction
- tower.hedge uses tower_service, so a change to tower_service can break tower.hedge, while a change to tower.hedge can't break tower_service.
- Position
- Below the diagonal: tower.hedge uses a module listed above it, which is the healthy direction.
9→6 tower.hedge uses tower.hedge.delay✕
- Connections
- 2 pairs of types, where a type in tower.hedge uses a type in tower.hedge.delay.
- The types involved
tower.hedge.DelayPolicy→tower.hedge.delay.Policytower.hedge.SelectPolicy→tower.hedge.delay.Policy
- Direction
- tower.hedge uses tower.hedge.delay, so a change to tower.hedge.delay can break tower.hedge, while a change to tower.hedge can't break tower.hedge.delay.
- Position
- Below the diagonal: tower.hedge uses a module listed above it, which is the healthy direction.
10→5 tower.limit.rate.layer uses tower_service✕
- Connections
- 1 pair of types, where a type in tower.limit.rate.layer uses a type in tower_service.
- The types involved
tower.limit.rate.layer.RateLimitLayer→tower_service.Service
- Direction
- tower.limit.rate.layer uses tower_service, so a change to tower_service can break tower.limit.rate.layer, while a change to tower.limit.rate.layer can't break tower_service.
- Position
- Below the diagonal: tower.limit.rate.layer uses a module listed above it, which is the healthy direction.
10→7 tower.limit.rate.layer uses tower_layer✕
- Connections
- 1 pair of types, where a type in tower.limit.rate.layer uses a type in tower_layer.
- The types involved
tower.limit.rate.layer.RateLimitLayer→tower_layer.Layer
- Direction
- tower.limit.rate.layer uses tower_layer, so a change to tower_layer can break tower.limit.rate.layer, while a change to tower.limit.rate.layer can't break tower_layer.
- Position
- Below the diagonal: tower.limit.rate.layer uses a module listed above it, which is the healthy direction.
11→5 tower.spawn_ready.layer uses tower_service✕
- Connections
- 1 pair of types, where a type in tower.spawn_ready.layer uses a type in tower_service.
- The types involved
tower.spawn_ready.layer.SpawnReadyLayer→tower_service.Service
- Direction
- tower.spawn_ready.layer uses tower_service, so a change to tower_service can break tower.spawn_ready.layer, while a change to tower.spawn_ready.layer can't break tower_service.
- Position
- Below the diagonal: tower.spawn_ready.layer uses a module listed above it, which is the healthy direction.
11→7 tower.spawn_ready.layer uses tower_layer✕
- Connections
- 1 pair of types, where a type in tower.spawn_ready.layer uses a type in tower_layer.
- The types involved
tower.spawn_ready.layer.SpawnReadyLayer→tower_layer.Layer
- Direction
- tower.spawn_ready.layer uses tower_layer, so a change to tower_layer can break tower.spawn_ready.layer, while a change to tower.spawn_ready.layer can't break tower_layer.
- Position
- Below the diagonal: tower.spawn_ready.layer uses a module listed above it, which is the healthy direction.
12→5 tower_layer.layer_fn uses tower_service✕
- Connections
- 1 pair of types, where a type in tower_layer.layer_fn uses a type in tower_service.
- The types involved
tower_layer.layer_fn.LayerFn→tower_service.Service
- Direction
- tower_layer.layer_fn uses tower_service, so a change to tower_service can break tower_layer.layer_fn, while a change to tower_layer.layer_fn can't break tower_service.
- Position
- Below the diagonal: tower_layer.layer_fn uses a module listed above it, which is the healthy direction.
12→7 tower_layer.layer_fn uses tower_layer✕
- Connections
- 1 pair of types, where a type in tower_layer.layer_fn uses a type in tower_layer.
- The types involved
tower_layer.layer_fn.LayerFn→tower_layer.Layer
- Direction
- tower_layer.layer_fn uses tower_layer, so a change to tower_layer can break tower_layer.layer_fn, while a change to tower_layer.layer_fn can't break tower_layer.
- Position
- Below the diagonal: tower_layer.layer_fn uses a module listed above it, which is the healthy direction.
13→5 tower.balance.p2c.service uses tower_service✕
- Connections
- 1 pair of types, where a type in tower.balance.p2c.service uses a type in tower_service.
- The types involved
tower.balance.p2c.service.Balance→tower_service.Service
- Direction
- tower.balance.p2c.service uses tower_service, so a change to tower_service can break tower.balance.p2c.service, while a change to tower.balance.p2c.service can't break tower_service.
- Position
- Below the diagonal: tower.balance.p2c.service uses a module listed above it, which is the healthy direction.
13→9 tower.balance.p2c.service uses tower.hedge✕
- Connections
- 1 pair of types, where a type in tower.balance.p2c.service uses a type in tower.hedge.
- The types involved
tower.balance.p2c.service.Balance→tower.hedge.Future
- Direction
- tower.balance.p2c.service uses tower.hedge, so a change to tower.hedge can break tower.balance.p2c.service, while a change to tower.balance.p2c.service can't break tower.hedge.
- Position
- Below the diagonal: tower.balance.p2c.service uses a module listed above it, which is the healthy direction.
14→9 tower.buffer.future uses tower.hedge✕
- Connections
- 1 pair of types, where a type in tower.buffer.future uses a type in tower.hedge.
- The types involved
tower.buffer.future.ResponseFuture→tower.hedge.Future
- Direction
- tower.buffer.future uses tower.hedge, so a change to tower.hedge can break tower.buffer.future, while a change to tower.buffer.future can't break tower.hedge.
- Position
- Below the diagonal: tower.buffer.future uses a module listed above it, which is the healthy direction.
15→9 tower.buffer.worker uses tower.hedge✕
- Connections
- 1 pair of types, where a type in tower.buffer.worker uses a type in tower.hedge.
- The types involved
tower.buffer.worker.Worker→tower.hedge.Future
- Direction
- tower.buffer.worker uses tower.hedge, so a change to tower.hedge can break tower.buffer.worker, while a change to tower.buffer.worker can't break tower.hedge.
- Position
- Below the diagonal: tower.buffer.worker uses a module listed above it, which is the healthy direction.
16→5 tower.filter uses tower_service✕
- Connections
- 2 pairs of types, where a type in tower.filter uses a type in tower_service.
- The types involved
tower.filter.AsyncFilter→tower_service.Servicetower.filter.Filter→tower_service.Service
- Direction
- tower.filter uses tower_service, so a change to tower_service can break tower.filter, while a change to tower.filter can't break tower_service.
- Position
- Below the diagonal: tower.filter uses a module listed above it, which is the healthy direction.
16→8 tower.filter uses tower.filter.layer✕
- Connections
- 2 pairs of types, where a type in tower.filter uses a type in tower.filter.layer.
- The types involved
tower.filter.AsyncFilter→tower.filter.layer.FilterLayertower.filter.Filter→tower.filter.layer.FilterLayer
- Direction
- tower.filter uses tower.filter.layer, so a change to tower.filter.layer can break tower.filter, while a change to tower.filter can't break tower.filter.layer.
- Position
- Below the diagonal: tower.filter uses a module listed above it, which is the healthy direction.
16→9 tower.filter uses tower.hedge✕
- Connections
- 2 pairs of types, where a type in tower.filter uses a type in tower.hedge.
- The types involved
tower.filter.AsyncFilter→tower.hedge.Futuretower.filter.Filter→tower.hedge.Future
- Direction
- tower.filter uses tower.hedge, so a change to tower.hedge can break tower.filter, while a change to tower.filter can't break tower.hedge.
- Position
- Below the diagonal: tower.filter uses a module listed above it, which is the healthy direction.
17→1 tower.limit.concurrency.service uses tower.load✕
- Connections
- 1 pair of types, where a type in tower.limit.concurrency.service uses a type in tower.load.
- The types involved
tower.limit.concurrency.service.ConcurrencyLimit→tower.load.Load
- Direction
- tower.limit.concurrency.service uses tower.load, so a change to tower.load can break tower.limit.concurrency.service, while a change to tower.limit.concurrency.service can't break tower.load.
- Position
- Below the diagonal: tower.limit.concurrency.service uses a module listed above it, which is the healthy direction.
17→5 tower.limit.concurrency.service uses tower_service✕
- Connections
- 1 pair of types, where a type in tower.limit.concurrency.service uses a type in tower_service.
- The types involved
tower.limit.concurrency.service.ConcurrencyLimit→tower_service.Service
- Direction
- tower.limit.concurrency.service uses tower_service, so a change to tower_service can break tower.limit.concurrency.service, while a change to tower.limit.concurrency.service can't break tower_service.
- Position
- Below the diagonal: tower.limit.concurrency.service uses a module listed above it, which is the healthy direction.
17→9 tower.limit.concurrency.service uses tower.hedge✕
- Connections
- 1 pair of types, where a type in tower.limit.concurrency.service uses a type in tower.hedge.
- The types involved
tower.limit.concurrency.service.ConcurrencyLimit→tower.hedge.Future
- Direction
- tower.limit.concurrency.service uses tower.hedge, so a change to tower.hedge can break tower.limit.concurrency.service, while a change to tower.limit.concurrency.service can't break tower.hedge.
- Position
- Below the diagonal: tower.limit.concurrency.service uses a module listed above it, which is the healthy direction.
18→1 tower.limit.rate.service uses tower.load✕
- Connections
- 1 pair of types, where a type in tower.limit.rate.service uses a type in tower.load.
- The types involved
tower.limit.rate.service.RateLimit→tower.load.Load
- Direction
- tower.limit.rate.service uses tower.load, so a change to tower.load can break tower.limit.rate.service, while a change to tower.limit.rate.service can't break tower.load.
- Position
- Below the diagonal: tower.limit.rate.service uses a module listed above it, which is the healthy direction.
18→4 tower.limit.rate.service uses tower.filter.future✕
- Connections
- 1 pair of types, where a type in tower.limit.rate.service uses a type in tower.filter.future.
- The types involved
tower.limit.rate.service.RateLimit→tower.filter.future.State
- Direction
- tower.limit.rate.service uses tower.filter.future, so a change to tower.filter.future can break tower.limit.rate.service, while a change to tower.limit.rate.service can't break tower.filter.future.
- Position
- Below the diagonal: tower.limit.rate.service uses a module listed above it, which is the healthy direction.
18→5 tower.limit.rate.service uses tower_service✕
- Connections
- 1 pair of types, where a type in tower.limit.rate.service uses a type in tower_service.
- The types involved
tower.limit.rate.service.RateLimit→tower_service.Service
- Direction
- tower.limit.rate.service uses tower_service, so a change to tower_service can break tower.limit.rate.service, while a change to tower.limit.rate.service can't break tower_service.
- Position
- Below the diagonal: tower.limit.rate.service uses a module listed above it, which is the healthy direction.
18→9 tower.limit.rate.service uses tower.hedge✕
- Connections
- 1 pair of types, where a type in tower.limit.rate.service uses a type in tower.hedge.
- The types involved
tower.limit.rate.service.RateLimit→tower.hedge.Future
- Direction
- tower.limit.rate.service uses tower.hedge, so a change to tower.hedge can break tower.limit.rate.service, while a change to tower.limit.rate.service can't break tower.hedge.
- Position
- Below the diagonal: tower.limit.rate.service uses a module listed above it, which is the healthy direction.
19→1 tower.load.constant uses tower.load✕
- Connections
- 1 pair of types, where a type in tower.load.constant uses a type in tower.load.
- The types involved
tower.load.constant.Constant→tower.load.Load
- Direction
- tower.load.constant uses tower.load, so a change to tower.load can break tower.load.constant, while a change to tower.load.constant can't break tower.load.
- Position
- Below the diagonal: tower.load.constant uses a module listed above it, which is the healthy direction.
19→5 tower.load.constant uses tower_service✕
- Connections
- 1 pair of types, where a type in tower.load.constant uses a type in tower_service.
- The types involved
tower.load.constant.Constant→tower_service.Service
- Direction
- tower.load.constant uses tower_service, so a change to tower_service can break tower.load.constant, while a change to tower.load.constant can't break tower_service.
- Position
- Below the diagonal: tower.load.constant uses a module listed above it, which is the healthy direction.
19→9 tower.load.constant uses tower.hedge✕
- Connections
- 1 pair of types, where a type in tower.load.constant uses a type in tower.hedge.
- The types involved
tower.load.constant.Constant→tower.hedge.Future
- Direction
- tower.load.constant uses tower.hedge, so a change to tower.hedge can break tower.load.constant, while a change to tower.load.constant can't break tower.hedge.
- Position
- Below the diagonal: tower.load.constant uses a module listed above it, which is the healthy direction.
20→2 tower.make.make_service uses tower.sealed✕
- Connections
- 1 pair of types, where a type in tower.make.make_service uses a type in tower.sealed.
- The types involved
tower.make.make_service.MakeService→tower.sealed.Sealed
- Direction
- tower.make.make_service uses tower.sealed, so a change to tower.sealed can break tower.make.make_service, while a change to tower.make.make_service can't break tower.sealed.
- Position
- Below the diagonal: tower.make.make_service uses a module listed above it, which is the healthy direction.
20→5 tower.make.make_service uses tower_service✕
- Connections
- 2 pairs of types, where a type in tower.make.make_service uses a type in tower_service.
- The types involved
tower.make.make_service.AsService→tower_service.Servicetower.make.make_service.IntoService→tower_service.Service
- Direction
- tower.make.make_service uses tower_service, so a change to tower_service can break tower.make.make_service, while a change to tower.make.make_service can't break tower_service.
- Position
- Below the diagonal: tower.make.make_service uses a module listed above it, which is the healthy direction.
20→9 tower.make.make_service uses tower.hedge✕
- Connections
- 3 pairs of types, where a type in tower.make.make_service uses a type in tower.hedge.
- The types involved
tower.make.make_service.AsService→tower.hedge.Futuretower.make.make_service.IntoService→tower.hedge.Futuretower.make.make_service.MakeService→tower.hedge.Future
- Direction
- tower.make.make_service uses tower.hedge, so a change to tower.hedge can break tower.make.make_service, while a change to tower.make.make_service can't break tower.hedge.
- Position
- Below the diagonal: tower.make.make_service uses a module listed above it, which is the healthy direction.
21→4 tower.reconnect uses tower.filter.future✕
- Connections
- 1 pair of types, where a type in tower.reconnect uses a type in tower.filter.future.
- The types involved
tower.reconnect.Reconnect→tower.filter.future.State
- Direction
- tower.reconnect uses tower.filter.future, so a change to tower.filter.future can break tower.reconnect, while a change to tower.reconnect can't break tower.filter.future.
- Position
- Below the diagonal: tower.reconnect uses a module listed above it, which is the healthy direction.
21→5 tower.reconnect uses tower_service✕
- Connections
- 1 pair of types, where a type in tower.reconnect uses a type in tower_service.
- The types involved
tower.reconnect.Reconnect→tower_service.Service
- Direction
- tower.reconnect uses tower_service, so a change to tower_service can break tower.reconnect, while a change to tower.reconnect can't break tower_service.
- Position
- Below the diagonal: tower.reconnect uses a module listed above it, which is the healthy direction.
21→9 tower.reconnect uses tower.hedge✕
- Connections
- 1 pair of types, where a type in tower.reconnect uses a type in tower.hedge.
- The types involved
tower.reconnect.Reconnect→tower.hedge.Future
- Direction
- tower.reconnect uses tower.hedge, so a change to tower.hedge can break tower.reconnect, while a change to tower.reconnect can't break tower.hedge.
- Position
- Below the diagonal: tower.reconnect uses a module listed above it, which is the healthy direction.
22→9 tower.reconnect.future uses tower.hedge✕
- Connections
- 1 pair of types, where a type in tower.reconnect.future uses a type in tower.hedge.
- The types involved
tower.reconnect.future.ResponseFuture→tower.hedge.Future
- Direction
- tower.reconnect.future uses tower.hedge, so a change to tower.hedge can break tower.reconnect.future, while a change to tower.reconnect.future can't break tower.hedge.
- Position
- Below the diagonal: tower.reconnect.future uses a module listed above it, which is the healthy direction.
23→5 tower.retry uses tower_service✕
- Connections
- 1 pair of types, where a type in tower.retry uses a type in tower_service.
- The types involved
tower.retry.Retry→tower_service.Service
- Direction
- tower.retry uses tower_service, so a change to tower_service can break tower.retry, while a change to tower.retry can't break tower_service.
- Position
- Below the diagonal: tower.retry uses a module listed above it, which is the healthy direction.
23→9 tower.retry uses tower.hedge✕
- Connections
- 1 pair of types, where a type in tower.retry uses a type in tower.hedge.
- The types involved
tower.retry.Retry→tower.hedge.Future
- Direction
- tower.retry uses tower.hedge, so a change to tower.hedge can break tower.retry, while a change to tower.retry can't break tower.hedge.
- Position
- Below the diagonal: tower.retry uses a module listed above it, which is the healthy direction.
24→5 tower.util.and_then uses tower_service✕
- Connections
- 2 pairs of types, where a type in tower.util.and_then uses a type in tower_service.
- The types involved
tower.util.and_then.AndThen→tower_service.Servicetower.util.and_then.AndThenLayer→tower_service.Service
- Direction
- tower.util.and_then uses tower_service, so a change to tower_service can break tower.util.and_then, while a change to tower.util.and_then can't break tower_service.
- Position
- Below the diagonal: tower.util.and_then uses a module listed above it, which is the healthy direction.
24→7 tower.util.and_then uses tower_layer✕
- Connections
- 1 pair of types, where a type in tower.util.and_then uses a type in tower_layer.
- The types involved
tower.util.and_then.AndThenLayer→tower_layer.Layer
- Direction
- tower.util.and_then uses tower_layer, so a change to tower_layer can break tower.util.and_then, while a change to tower.util.and_then can't break tower_layer.
- Position
- Below the diagonal: tower.util.and_then uses a module listed above it, which is the healthy direction.
24→9 tower.util.and_then uses tower.hedge✕
- Connections
- 2 pairs of types, where a type in tower.util.and_then uses a type in tower.hedge.
- The types involved
tower.util.and_then.AndThen→tower.hedge.Futuretower.util.and_then.AndThenFuture→tower.hedge.Future
- Direction
- tower.util.and_then uses tower.hedge, so a change to tower.hedge can break tower.util.and_then, while a change to tower.util.and_then can't break tower.hedge.
- Position
- Below the diagonal: tower.util.and_then uses a module listed above it, which is the healthy direction.
25→5 tower.util.boxed.sync uses tower_service✕
- Connections
- 1 pair of types, where a type in tower.util.boxed.sync uses a type in tower_service.
- The types involved
tower.util.boxed.sync.BoxService→tower_service.Service
- Direction
- tower.util.boxed.sync uses tower_service, so a change to tower_service can break tower.util.boxed.sync, while a change to tower.util.boxed.sync can't break tower_service.
- Position
- Below the diagonal: tower.util.boxed.sync uses a module listed above it, which is the healthy direction.
25→12 tower.util.boxed.sync uses tower_layer.layer_fn✕
- Connections
- 1 pair of types, where a type in tower.util.boxed.sync uses a type in tower_layer.layer_fn.
- The types involved
tower.util.boxed.sync.BoxService→tower_layer.layer_fn.LayerFn
- Direction
- tower.util.boxed.sync uses tower_layer.layer_fn, so a change to tower_layer.layer_fn can break tower.util.boxed.sync, while a change to tower.util.boxed.sync can't break tower_layer.layer_fn.
- Position
- Below the diagonal: tower.util.boxed.sync uses a module listed above it, which is the healthy direction.
26→5 tower.util.boxed.unsync uses tower_service✕
- Connections
- 2 pairs of types, where a type in tower.util.boxed.unsync uses a type in tower_service.
- The types involved
tower.util.boxed.unsync.UnsyncBoxService→tower_service.Servicetower.util.boxed.unsync.UnsyncBoxed→tower_service.Service
- Direction
- tower.util.boxed.unsync uses tower_service, so a change to tower_service can break tower.util.boxed.unsync, while a change to tower.util.boxed.unsync can't break tower_service.
- Position
- Below the diagonal: tower.util.boxed.unsync uses a module listed above it, which is the healthy direction.
26→9 tower.util.boxed.unsync uses tower.hedge✕
- Connections
- 1 pair of types, where a type in tower.util.boxed.unsync uses a type in tower.hedge.
- The types involved
tower.util.boxed.unsync.UnsyncBoxed→tower.hedge.Future
- Direction
- tower.util.boxed.unsync uses tower.hedge, so a change to tower.hedge can break tower.util.boxed.unsync, while a change to tower.util.boxed.unsync can't break tower.hedge.
- Position
- Below the diagonal: tower.util.boxed.unsync uses a module listed above it, which is the healthy direction.
26→12 tower.util.boxed.unsync uses tower_layer.layer_fn✕
- Connections
- 1 pair of types, where a type in tower.util.boxed.unsync uses a type in tower_layer.layer_fn.
- The types involved
tower.util.boxed.unsync.UnsyncBoxService→tower_layer.layer_fn.LayerFn
- Direction
- tower.util.boxed.unsync uses tower_layer.layer_fn, so a change to tower_layer.layer_fn can break tower.util.boxed.unsync, while a change to tower.util.boxed.unsync can't break tower_layer.layer_fn.
- Position
- Below the diagonal: tower.util.boxed.unsync uses a module listed above it, which is the healthy direction.
27→5 tower.util.boxed_clone uses tower_service✕
- Connections
- 2 pairs of types, where a type in tower.util.boxed_clone uses a type in tower_service.
- The types involved
tower.util.boxed_clone.BoxCloneService→tower_service.Servicetower.util.boxed_clone.CloneService→tower_service.Service
- Direction
- tower.util.boxed_clone uses tower_service, so a change to tower_service can break tower.util.boxed_clone, while a change to tower.util.boxed_clone can't break tower_service.
- Position
- Below the diagonal: tower.util.boxed_clone uses a module listed above it, which is the healthy direction.
27→9 tower.util.boxed_clone uses tower.hedge✕
- Connections
- 1 pair of types, where a type in tower.util.boxed_clone uses a type in tower.hedge.
- The types involved
tower.util.boxed_clone.BoxCloneService→tower.hedge.Future
- Direction
- tower.util.boxed_clone uses tower.hedge, so a change to tower.hedge can break tower.util.boxed_clone, while a change to tower.util.boxed_clone can't break tower.hedge.
- Position
- Below the diagonal: tower.util.boxed_clone uses a module listed above it, which is the healthy direction.
27→12 tower.util.boxed_clone uses tower_layer.layer_fn✕
- Connections
- 1 pair of types, where a type in tower.util.boxed_clone uses a type in tower_layer.layer_fn.
- The types involved
tower.util.boxed_clone.BoxCloneService→tower_layer.layer_fn.LayerFn
- Direction
- tower.util.boxed_clone uses tower_layer.layer_fn, so a change to tower_layer.layer_fn can break tower.util.boxed_clone, while a change to tower.util.boxed_clone can't break tower_layer.layer_fn.
- Position
- Below the diagonal: tower.util.boxed_clone uses a module listed above it, which is the healthy direction.
28→5 tower.util.either uses tower_service✕
- Connections
- 1 pair of types, where a type in tower.util.either uses a type in tower_service.
- The types involved
tower.util.either.Either→tower_service.Service
- Direction
- tower.util.either uses tower_service, so a change to tower_service can break tower.util.either, while a change to tower.util.either can't break tower_service.
- Position
- Below the diagonal: tower.util.either uses a module listed above it, which is the healthy direction.
28→7 tower.util.either uses tower_layer✕
- Connections
- 1 pair of types, where a type in tower.util.either uses a type in tower_layer.
- The types involved
tower.util.either.Either→tower_layer.Layer
- Direction
- tower.util.either uses tower_layer, so a change to tower_layer can break tower.util.either, while a change to tower.util.either can't break tower_layer.
- Position
- Below the diagonal: tower.util.either uses a module listed above it, which is the healthy direction.
28→9 tower.util.either uses tower.hedge✕
- Connections
- 2 pairs of types, where a type in tower.util.either uses a type in tower.hedge.
- The types involved
tower.util.either.Either→tower.hedge.Futuretower.util.either.EitherResponseFuture→tower.hedge.Future
- Direction
- tower.util.either uses tower.hedge, so a change to tower.hedge can break tower.util.either, while a change to tower.util.either can't break tower.hedge.
- Position
- Below the diagonal: tower.util.either uses a module listed above it, which is the healthy direction.
29→5 tower.util.map_err uses tower_service✕
- Connections
- 2 pairs of types, where a type in tower.util.map_err uses a type in tower_service.
- The types involved
tower.util.map_err.MapErr→tower_service.Servicetower.util.map_err.MapErrLayer→tower_service.Service
- Direction
- tower.util.map_err uses tower_service, so a change to tower_service can break tower.util.map_err, while a change to tower.util.map_err can't break tower_service.
- Position
- Below the diagonal: tower.util.map_err uses a module listed above it, which is the healthy direction.
29→7 tower.util.map_err uses tower_layer✕
- Connections
- 1 pair of types, where a type in tower.util.map_err uses a type in tower_layer.
- The types involved
tower.util.map_err.MapErrLayer→tower_layer.Layer
- Direction
- tower.util.map_err uses tower_layer, so a change to tower_layer can break tower.util.map_err, while a change to tower.util.map_err can't break tower_layer.
- Position
- Below the diagonal: tower.util.map_err uses a module listed above it, which is the healthy direction.
29→9 tower.util.map_err uses tower.hedge✕
- Connections
- 1 pair of types, where a type in tower.util.map_err uses a type in tower.hedge.
- The types involved
tower.util.map_err.MapErr→tower.hedge.Future
- Direction
- tower.util.map_err uses tower.hedge, so a change to tower.hedge can break tower.util.map_err, while a change to tower.util.map_err can't break tower.hedge.
- Position
- Below the diagonal: tower.util.map_err uses a module listed above it, which is the healthy direction.
30→5 tower.util.map_future uses tower_service✕
- Connections
- 2 pairs of types, where a type in tower.util.map_future uses a type in tower_service.
- The types involved
tower.util.map_future.MapFuture→tower_service.Servicetower.util.map_future.MapFutureLayer→tower_service.Service
- Direction
- tower.util.map_future uses tower_service, so a change to tower_service can break tower.util.map_future, while a change to tower.util.map_future can't break tower_service.
- Position
- Below the diagonal: tower.util.map_future uses a module listed above it, which is the healthy direction.
30→7 tower.util.map_future uses tower_layer✕
- Connections
- 1 pair of types, where a type in tower.util.map_future uses a type in tower_layer.
- The types involved
tower.util.map_future.MapFutureLayer→tower_layer.Layer
- Direction
- tower.util.map_future uses tower_layer, so a change to tower_layer can break tower.util.map_future, while a change to tower.util.map_future can't break tower_layer.
- Position
- Below the diagonal: tower.util.map_future uses a module listed above it, which is the healthy direction.
30→9 tower.util.map_future uses tower.hedge✕
- Connections
- 1 pair of types, where a type in tower.util.map_future uses a type in tower.hedge.
- The types involved
tower.util.map_future.MapFuture→tower.hedge.Future
- Direction
- tower.util.map_future uses tower.hedge, so a change to tower.hedge can break tower.util.map_future, while a change to tower.util.map_future can't break tower.hedge.
- Position
- Below the diagonal: tower.util.map_future uses a module listed above it, which is the healthy direction.
31→5 tower.util.map_request uses tower_service✕
- Connections
- 2 pairs of types, where a type in tower.util.map_request uses a type in tower_service.
- The types involved
tower.util.map_request.MapRequest→tower_service.Servicetower.util.map_request.MapRequestLayer→tower_service.Service
- Direction
- tower.util.map_request uses tower_service, so a change to tower_service can break tower.util.map_request, while a change to tower.util.map_request can't break tower_service.
- Position
- Below the diagonal: tower.util.map_request uses a module listed above it, which is the healthy direction.
31→7 tower.util.map_request uses tower_layer✕
- Connections
- 1 pair of types, where a type in tower.util.map_request uses a type in tower_layer.
- The types involved
tower.util.map_request.MapRequestLayer→tower_layer.Layer
- Direction
- tower.util.map_request uses tower_layer, so a change to tower_layer can break tower.util.map_request, while a change to tower.util.map_request can't break tower_layer.
- Position
- Below the diagonal: tower.util.map_request uses a module listed above it, which is the healthy direction.
31→9 tower.util.map_request uses tower.hedge✕
- Connections
- 1 pair of types, where a type in tower.util.map_request uses a type in tower.hedge.
- The types involved
tower.util.map_request.MapRequest→tower.hedge.Future
- Direction
- tower.util.map_request uses tower.hedge, so a change to tower.hedge can break tower.util.map_request, while a change to tower.util.map_request can't break tower.hedge.
- Position
- Below the diagonal: tower.util.map_request uses a module listed above it, which is the healthy direction.
32→5 tower.util.map_response uses tower_service✕
- Connections
- 2 pairs of types, where a type in tower.util.map_response uses a type in tower_service.
- The types involved
tower.util.map_response.MapResponse→tower_service.Servicetower.util.map_response.MapResponseLayer→tower_service.Service
- Direction
- tower.util.map_response uses tower_service, so a change to tower_service can break tower.util.map_response, while a change to tower.util.map_response can't break tower_service.
- Position
- Below the diagonal: tower.util.map_response uses a module listed above it, which is the healthy direction.
32→7 tower.util.map_response uses tower_layer✕
- Connections
- 1 pair of types, where a type in tower.util.map_response uses a type in tower_layer.
- The types involved
tower.util.map_response.MapResponseLayer→tower_layer.Layer
- Direction
- tower.util.map_response uses tower_layer, so a change to tower_layer can break tower.util.map_response, while a change to tower.util.map_response can't break tower_layer.
- Position
- Below the diagonal: tower.util.map_response uses a module listed above it, which is the healthy direction.
32→9 tower.util.map_response uses tower.hedge✕
- Connections
- 1 pair of types, where a type in tower.util.map_response uses a type in tower.hedge.
- The types involved
tower.util.map_response.MapResponse→tower.hedge.Future
- Direction
- tower.util.map_response uses tower.hedge, so a change to tower.hedge can break tower.util.map_response, while a change to tower.util.map_response can't break tower.hedge.
- Position
- Below the diagonal: tower.util.map_response uses a module listed above it, which is the healthy direction.
33→5 tower.util.map_result uses tower_service✕
- Connections
- 2 pairs of types, where a type in tower.util.map_result uses a type in tower_service.
- The types involved
tower.util.map_result.MapResult→tower_service.Servicetower.util.map_result.MapResultLayer→tower_service.Service
- Direction
- tower.util.map_result uses tower_service, so a change to tower_service can break tower.util.map_result, while a change to tower.util.map_result can't break tower_service.
- Position
- Below the diagonal: tower.util.map_result uses a module listed above it, which is the healthy direction.
33→7 tower.util.map_result uses tower_layer✕
- Connections
- 1 pair of types, where a type in tower.util.map_result uses a type in tower_layer.
- The types involved
tower.util.map_result.MapResultLayer→tower_layer.Layer
- Direction
- tower.util.map_result uses tower_layer, so a change to tower_layer can break tower.util.map_result, while a change to tower.util.map_result can't break tower_layer.
- Position
- Below the diagonal: tower.util.map_result uses a module listed above it, which is the healthy direction.
33→9 tower.util.map_result uses tower.hedge✕
- Connections
- 1 pair of types, where a type in tower.util.map_result uses a type in tower.hedge.
- The types involved
tower.util.map_result.MapResult→tower.hedge.Future
- Direction
- tower.util.map_result uses tower.hedge, so a change to tower.hedge can break tower.util.map_result, while a change to tower.util.map_result can't break tower.hedge.
- Position
- Below the diagonal: tower.util.map_result uses a module listed above it, which is the healthy direction.
34→5 tower.util.then uses tower_service✕
- Connections
- 2 pairs of types, where a type in tower.util.then uses a type in tower_service.
- The types involved
tower.util.then.Then→tower_service.Servicetower.util.then.ThenLayer→tower_service.Service
- Direction
- tower.util.then uses tower_service, so a change to tower_service can break tower.util.then, while a change to tower.util.then can't break tower_service.
- Position
- Below the diagonal: tower.util.then uses a module listed above it, which is the healthy direction.
34→7 tower.util.then uses tower_layer✕
- Connections
- 1 pair of types, where a type in tower.util.then uses a type in tower_layer.
- The types involved
tower.util.then.ThenLayer→tower_layer.Layer
- Direction
- tower.util.then uses tower_layer, so a change to tower_layer can break tower.util.then, while a change to tower.util.then can't break tower_layer.
- Position
- Below the diagonal: tower.util.then uses a module listed above it, which is the healthy direction.
34→9 tower.util.then uses tower.hedge✕
- Connections
- 1 pair of types, where a type in tower.util.then uses a type in tower.hedge.
- The types involved
tower.util.then.Then→tower.hedge.Future
- Direction
- tower.util.then uses tower.hedge, so a change to tower.hedge can break tower.util.then, while a change to tower.util.then can't break tower.hedge.
- Position
- Below the diagonal: tower.util.then uses a module listed above it, which is the healthy direction.
35→5 tower.buffer.service uses tower_service✕
- Connections
- 1 pair of types, where a type in tower.buffer.service uses a type in tower_service.
- The types involved
tower.buffer.service.Buffer→tower_service.Service
- Direction
- tower.buffer.service uses tower_service, so a change to tower_service can break tower.buffer.service, while a change to tower.buffer.service can't break tower_service.
- Position
- Below the diagonal: tower.buffer.service uses a module listed above it, which is the healthy direction.
35→9 tower.buffer.service uses tower.hedge✕
- Connections
- 1 pair of types, where a type in tower.buffer.service uses a type in tower.hedge.
- The types involved
tower.buffer.service.Buffer→tower.hedge.Future
- Direction
- tower.buffer.service uses tower.hedge, so a change to tower.hedge can break tower.buffer.service, while a change to tower.buffer.service can't break tower.hedge.
- Position
- Below the diagonal: tower.buffer.service uses a module listed above it, which is the healthy direction.
35→15 tower.buffer.service uses tower.buffer.worker✕
- Connections
- 1 pair of types, where a type in tower.buffer.service uses a type in tower.buffer.worker.
- The types involved
tower.buffer.service.Buffer→tower.buffer.worker.Handle
- Direction
- tower.buffer.service uses tower.buffer.worker, so a change to tower.buffer.worker can break tower.buffer.service, while a change to tower.buffer.service can't break tower.buffer.worker.
- Position
- Below the diagonal: tower.buffer.service uses a module listed above it, which is the healthy direction.
36→1 tower.load.peak_ewma uses tower.load✕
- Connections
- 1 pair of types, where a type in tower.load.peak_ewma uses a type in tower.load.
- The types involved
tower.load.peak_ewma.PeakEwma→tower.load.Load
- Direction
- tower.load.peak_ewma uses tower.load, so a change to tower.load can break tower.load.peak_ewma, while a change to tower.load.peak_ewma can't break tower.load.
- Position
- Below the diagonal: tower.load.peak_ewma uses a module listed above it, which is the healthy direction.
36→5 tower.load.peak_ewma uses tower_service✕
- Connections
- 1 pair of types, where a type in tower.load.peak_ewma uses a type in tower_service.
- The types involved
tower.load.peak_ewma.PeakEwma→tower_service.Service
- Direction
- tower.load.peak_ewma uses tower_service, so a change to tower_service can break tower.load.peak_ewma, while a change to tower.load.peak_ewma can't break tower_service.
- Position
- Below the diagonal: tower.load.peak_ewma uses a module listed above it, which is the healthy direction.
36→9 tower.load.peak_ewma uses tower.hedge✕
- Connections
- 1 pair of types, where a type in tower.load.peak_ewma uses a type in tower.hedge.
- The types involved
tower.load.peak_ewma.PeakEwma→tower.hedge.Future
- Direction
- tower.load.peak_ewma uses tower.hedge, so a change to tower.hedge can break tower.load.peak_ewma, while a change to tower.load.peak_ewma can't break tower.hedge.
- Position
- Below the diagonal: tower.load.peak_ewma uses a module listed above it, which is the healthy direction.
36→15 tower.load.peak_ewma uses tower.buffer.worker✕
- Connections
- 1 pair of types, where a type in tower.load.peak_ewma uses a type in tower.buffer.worker.
- The types involved
tower.load.peak_ewma.PeakEwma→tower.buffer.worker.Handle
- Direction
- tower.load.peak_ewma uses tower.buffer.worker, so a change to tower.buffer.worker can break tower.load.peak_ewma, while a change to tower.load.peak_ewma can't break tower.buffer.worker.
- Position
- Below the diagonal: tower.load.peak_ewma uses a module listed above it, which is the healthy direction.
37→1 tower.load.pending_requests uses tower.load✕
- Connections
- 1 pair of types, where a type in tower.load.pending_requests uses a type in tower.load.
- The types involved
tower.load.pending_requests.PendingRequests→tower.load.Load
- Direction
- tower.load.pending_requests uses tower.load, so a change to tower.load can break tower.load.pending_requests, while a change to tower.load.pending_requests can't break tower.load.
- Position
- Below the diagonal: tower.load.pending_requests uses a module listed above it, which is the healthy direction.
37→5 tower.load.pending_requests uses tower_service✕
- Connections
- 1 pair of types, where a type in tower.load.pending_requests uses a type in tower_service.
- The types involved
tower.load.pending_requests.PendingRequests→tower_service.Service
- Direction
- tower.load.pending_requests uses tower_service, so a change to tower_service can break tower.load.pending_requests, while a change to tower.load.pending_requests can't break tower_service.
- Position
- Below the diagonal: tower.load.pending_requests uses a module listed above it, which is the healthy direction.
37→9 tower.load.pending_requests uses tower.hedge✕
- Connections
- 1 pair of types, where a type in tower.load.pending_requests uses a type in tower.hedge.
- The types involved
tower.load.pending_requests.PendingRequests→tower.hedge.Future
- Direction
- tower.load.pending_requests uses tower.hedge, so a change to tower.hedge can break tower.load.pending_requests, while a change to tower.load.pending_requests can't break tower.hedge.
- Position
- Below the diagonal: tower.load.pending_requests uses a module listed above it, which is the healthy direction.
37→15 tower.load.pending_requests uses tower.buffer.worker✕
- Connections
- 1 pair of types, where a type in tower.load.pending_requests uses a type in tower.buffer.worker.
- The types involved
tower.load.pending_requests.PendingRequests→tower.buffer.worker.Handle
- Direction
- tower.load.pending_requests uses tower.buffer.worker, so a change to tower.buffer.worker can break tower.load.pending_requests, while a change to tower.load.pending_requests can't break tower.buffer.worker.
- Position
- Below the diagonal: tower.load.pending_requests uses a module listed above it, which is the healthy direction.
38→4 tower.retry.future uses tower.filter.future✕
- Connections
- 1 pair of types, where a type in tower.retry.future uses a type in tower.filter.future.
- The types involved
tower.retry.future.ResponseFuture→tower.filter.future.State
- Direction
- tower.retry.future uses tower.filter.future, so a change to tower.filter.future can break tower.retry.future, while a change to tower.retry.future can't break tower.filter.future.
- Position
- Below the diagonal: tower.retry.future uses a module listed above it, which is the healthy direction.
38→9 tower.retry.future uses tower.hedge✕
- Connections
- 1 pair of types, where a type in tower.retry.future uses a type in tower.hedge.
- The types involved
tower.retry.future.ResponseFuture→tower.hedge.Future
- Direction
- tower.retry.future uses tower.hedge, so a change to tower.hedge can break tower.retry.future, while a change to tower.retry.future can't break tower.hedge.
- Position
- Below the diagonal: tower.retry.future uses a module listed above it, which is the healthy direction.
38→14 tower.retry.future uses tower.buffer.future✕
- Connections
- 1 pair of types, where a type in tower.retry.future uses a type in tower.buffer.future.
- The types involved
tower.retry.future.ResponseFuture→tower.buffer.future.ResponseFuture
- Direction
- tower.retry.future uses tower.buffer.future, so a change to tower.buffer.future can break tower.retry.future, while a change to tower.retry.future can't break tower.buffer.future.
- Position
- Below the diagonal: tower.retry.future uses a module listed above it, which is the healthy direction.
38→23 tower.retry.future uses tower.retry✕
- Connections
- 1 pair of types, where a type in tower.retry.future uses a type in tower.retry.
- The types involved
tower.retry.future.ResponseFuture→tower.retry.Retry
- Direction
- tower.retry.future uses tower.retry, so a change to tower.retry can break tower.retry.future, while a change to tower.retry.future can't break tower.retry.
- Position
- Below the diagonal: tower.retry.future uses a module listed above it, which is the healthy direction.
39→5 tower.spawn_ready.service uses tower_service✕
- Connections
- 1 pair of types, where a type in tower.spawn_ready.service uses a type in tower_service.
- The types involved
tower.spawn_ready.service.SpawnReady→tower_service.Service
- Direction
- tower.spawn_ready.service uses tower_service, so a change to tower_service can break tower.spawn_ready.service, while a change to tower.spawn_ready.service can't break tower_service.
- Position
- Below the diagonal: tower.spawn_ready.service uses a module listed above it, which is the healthy direction.
39→9 tower.spawn_ready.service uses tower.hedge✕
- Connections
- 1 pair of types, where a type in tower.spawn_ready.service uses a type in tower.hedge.
- The types involved
tower.spawn_ready.service.SpawnReady→tower.hedge.Future
- Direction
- tower.spawn_ready.service uses tower.hedge, so a change to tower.hedge can break tower.spawn_ready.service, while a change to tower.spawn_ready.service can't break tower.hedge.
- Position
- Below the diagonal: tower.spawn_ready.service uses a module listed above it, which is the healthy direction.
39→11 tower.spawn_ready.service uses tower.spawn_ready.layer✕
- Connections
- 1 pair of types, where a type in tower.spawn_ready.service uses a type in tower.spawn_ready.layer.
- The types involved
tower.spawn_ready.service.SpawnReady→tower.spawn_ready.layer.SpawnReadyLayer
- Direction
- tower.spawn_ready.service uses tower.spawn_ready.layer, so a change to tower.spawn_ready.layer can break tower.spawn_ready.service, while a change to tower.spawn_ready.service can't break tower.spawn_ready.layer.
- Position
- Below the diagonal: tower.spawn_ready.service uses a module listed above it, which is the healthy direction.
39→22 tower.spawn_ready.service uses tower.reconnect.future✕
- Connections
- 1 pair of types, where a type in tower.spawn_ready.service uses a type in tower.reconnect.future.
- The types involved
tower.spawn_ready.service.SpawnReady→tower.reconnect.future.Inner
- Direction
- tower.spawn_ready.service uses tower.reconnect.future, so a change to tower.reconnect.future can break tower.spawn_ready.service, while a change to tower.spawn_ready.service can't break tower.reconnect.future.
- Position
- Below the diagonal: tower.spawn_ready.service uses a module listed above it, which is the healthy direction.
40→3 tower.util uses tower.util.call_all.common✕
- Connections
- 1 pair of types, where a type in tower.util uses a type in tower.util.call_all.common.
- The types involved
tower.util.ServiceExt→tower.util.call_all.common.CallAll
- Direction
- tower.util uses tower.util.call_all.common, so a change to tower.util.call_all.common can break tower.util, while a change to tower.util can't break tower.util.call_all.common.
- Position
- Below the diagonal: tower.util uses a module listed above it, which is the healthy direction.
40→5 tower.util uses tower_service✕
- Connections
- 1 pair of types, where a type in tower.util uses a type in tower_service.
- The types involved
tower.util.ServiceExt→tower_service.Service
- Direction
- tower.util uses tower_service, so a change to tower_service can break tower.util, while a change to tower.util can't break tower_service.
- Position
- Below the diagonal: tower.util uses a module listed above it, which is the healthy direction.
40→16 tower.util uses tower.filter✕
- Connections
- 2 pairs of types, where a type in tower.util uses a type in tower.filter.
- The types involved
tower.util.ServiceExt→tower.filter.AsyncFiltertower.util.ServiceExt→tower.filter.Filter
- Direction
- tower.util uses tower.filter, so a change to tower.filter can break tower.util, while a change to tower.util can't break tower.filter.
- Position
- Below the diagonal: tower.util uses a module listed above it, which is the healthy direction.
40→23 tower.util uses tower.retry✕
- Connections
- 1 pair of types, where a type in tower.util uses a type in tower.retry.
- The types involved
tower.util.ServiceExt→tower.retry.Retry
- Direction
- tower.util uses tower.retry, so a change to tower.retry can break tower.util, while a change to tower.util can't break tower.retry.
- Position
- Below the diagonal: tower.util uses a module listed above it, which is the healthy direction.
40→24 tower.util uses tower.util.and_then✕
- Connections
- 1 pair of types, where a type in tower.util uses a type in tower.util.and_then.
- The types involved
tower.util.ServiceExt→tower.util.and_then.AndThen
- Direction
- tower.util uses tower.util.and_then, so a change to tower.util.and_then can break tower.util, while a change to tower.util can't break tower.util.and_then.
- Position
- Below the diagonal: tower.util uses a module listed above it, which is the healthy direction.
40→25 tower.util uses tower.util.boxed.sync✕
- Connections
- 1 pair of types, where a type in tower.util uses a type in tower.util.boxed.sync.
- The types involved
tower.util.ServiceExt→tower.util.boxed.sync.BoxService
- Direction
- tower.util uses tower.util.boxed.sync, so a change to tower.util.boxed.sync can break tower.util, while a change to tower.util can't break tower.util.boxed.sync.
- Position
- Below the diagonal: tower.util uses a module listed above it, which is the healthy direction.
40→27 tower.util uses tower.util.boxed_clone✕
- Connections
- 1 pair of types, where a type in tower.util uses a type in tower.util.boxed_clone.
- The types involved
tower.util.ServiceExt→tower.util.boxed_clone.BoxCloneService
- Direction
- tower.util uses tower.util.boxed_clone, so a change to tower.util.boxed_clone can break tower.util, while a change to tower.util can't break tower.util.boxed_clone.
- Position
- Below the diagonal: tower.util uses a module listed above it, which is the healthy direction.
40→28 tower.util uses tower.util.either✕
- Connections
- 1 pair of types, where a type in tower.util uses a type in tower.util.either.
- The types involved
tower.util.util$module→tower.util.either.Either
- Direction
- tower.util uses tower.util.either, so a change to tower.util.either can break tower.util, while a change to tower.util can't break tower.util.either.
- Position
- Below the diagonal: tower.util uses a module listed above it, which is the healthy direction.
40→29 tower.util uses tower.util.map_err✕
- Connections
- 1 pair of types, where a type in tower.util uses a type in tower.util.map_err.
- The types involved
tower.util.ServiceExt→tower.util.map_err.MapErr
- Direction
- tower.util uses tower.util.map_err, so a change to tower.util.map_err can break tower.util, while a change to tower.util can't break tower.util.map_err.
- Position
- Below the diagonal: tower.util uses a module listed above it, which is the healthy direction.
40→30 tower.util uses tower.util.map_future✕
- Connections
- 1 pair of types, where a type in tower.util uses a type in tower.util.map_future.
- The types involved
tower.util.ServiceExt→tower.util.map_future.MapFuture
- Direction
- tower.util uses tower.util.map_future, so a change to tower.util.map_future can break tower.util, while a change to tower.util can't break tower.util.map_future.
- Position
- Below the diagonal: tower.util uses a module listed above it, which is the healthy direction.
40→31 tower.util uses tower.util.map_request✕
- Connections
- 1 pair of types, where a type in tower.util uses a type in tower.util.map_request.
- The types involved
tower.util.ServiceExt→tower.util.map_request.MapRequest
- Direction
- tower.util uses tower.util.map_request, so a change to tower.util.map_request can break tower.util, while a change to tower.util can't break tower.util.map_request.
- Position
- Below the diagonal: tower.util uses a module listed above it, which is the healthy direction.
40→32 tower.util uses tower.util.map_response✕
- Connections
- 1 pair of types, where a type in tower.util uses a type in tower.util.map_response.
- The types involved
tower.util.ServiceExt→tower.util.map_response.MapResponse
- Direction
- tower.util uses tower.util.map_response, so a change to tower.util.map_response can break tower.util, while a change to tower.util can't break tower.util.map_response.
- Position
- Below the diagonal: tower.util uses a module listed above it, which is the healthy direction.
40→33 tower.util uses tower.util.map_result✕
- Connections
- 1 pair of types, where a type in tower.util uses a type in tower.util.map_result.
- The types involved
tower.util.ServiceExt→tower.util.map_result.MapResult
- Direction
- tower.util uses tower.util.map_result, so a change to tower.util.map_result can break tower.util, while a change to tower.util can't break tower.util.map_result.
- Position
- Below the diagonal: tower.util uses a module listed above it, which is the healthy direction.
40→34 tower.util uses tower.util.then✕
- Connections
- 1 pair of types, where a type in tower.util uses a type in tower.util.then.
- The types involved
tower.util.ServiceExt→tower.util.then.Then
- Direction
- tower.util uses tower.util.then, so a change to tower.util.then can break tower.util, while a change to tower.util can't break tower.util.then.
- Position
- Below the diagonal: tower.util uses a module listed above it, which is the healthy direction.
40→35 tower.util uses tower.buffer.service✕
- Connections
- 1 pair of types, where a type in tower.util uses a type in tower.buffer.service.
- The types involved
tower.util.ServiceExt→tower.buffer.service.Buffer
- Direction
- tower.util uses tower.buffer.service, so a change to tower.buffer.service can break tower.util, while a change to tower.util can't break tower.buffer.service.
- Position
- Below the diagonal: tower.util 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 | 23 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 8 | Medium |
Roadmap
Begin by resolving the single documentation quality issue in README.md and adding a clear Testing section that explains how to run the test suite. Next, address the 51 orphaned files, prioritizing mod.rs, service.rs, and lib.rs, to improve codebase freshness. Simultaneously, record significant design decisions as individual documents in a docs/adr folder to establish proper architecture documentation. Finally, restrict workflow token permissions in REDACTED, REDACTED, and REDACTED to secure supply-chain provenance.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md. | +9.5 pts | Low | Documentation Quality |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +8.5 pts | Medium | Architecture documentation |
| Resolve the 51 Orphaned file finding(s) in Knowledge Freshness — start with mod.rs (9), service.rs (4), lib.rs (3). | +8.3 pts | Medium | Knowledge Freshness |
| Resolve the 3 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. | +1.8 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. | +1.4 pts | Low | Static Analysis (SAST) |
| Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite. | +1.6 pts | Medium | Documentation (README) |
| 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. | +1.4 pts | Medium | Release Hygiene |
| 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. | +1.2 pts | Medium | Web-Security Posture |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Mixed | Static Analysis (SAST): High: REDACTED |
| tower-test/src/mock/mod.rs | 6.9 | Mixed | Explicit Debt: TodoComment |
| tower/src/builder/mod.rs | 7.3 | Near-clean | Explicit Debt: TodoComment |
| tower/tests/balance/main.rs | 8.2 | Near-clean | Explicit Debt: TodoComment |
| tower/src/util/call_all/ordered.rs | 8.2 | Near-clean | Explicit Debt: TodoComment |
| tower/src/load/mod.rs | 8.2 | Near-clean | Explicit Debt: TodoComment |
| tower/src/hedge/mod.rs | 8.2 | Near-clean | Explicit Debt: TodoComment |
| tower/src/hedge/rotating_histogram.rs | 8.2 | Near-clean | Explicit Debt: TodoComment |
| tower/src/util/call_all/common.rs | 8.5 | Near-clean | Cognitive Complexity: CallAll::poll_next (cognitive 19) |
| tower/src/load/peak_ewma.rs | 8.5 | Near-clean | Code Duplication: Duplicated block (7 lines × 2) |
| tower/src/util/boxed/layer.rs | 8.5 | Near-clean | Code Duplication: Duplicated block (10 lines × 3) |
| README.md | 9.5 | Near-clean | Documentation Quality: Documentation: no build, run or usage example |
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. 45 of 45 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 — 45 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, 99 of 113 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.
- D44 Platform End-of-Life — 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 dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a Dockerfile) is simply not read here yet.
- AX6 Interface segregation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- GD1 Unfinished & placeholder code — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's 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.
- 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.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
0 function(s) exceeded the cyclomatic complexity threshold of 15.
D2 · Cognitive Complexity
1 function(s) exceeded the cognitive complexity threshold of 15; the worst was CallAll::poll_next at 19.
What to do
- Bring the 1 body over 15 down to 15 or less in Cognitive Complexity — start with CallAll::poll_next (cognitive 19). — Refactoring it lifts Cognitive Complexity from 9.7 to about 10.0/10.
- 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
0 over-large unit(s) detected — types, modules or files that carry too much.
D4 · Code Duplication
2 duplicated block group(s) detected.
What to do
- Resolve the 1 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with peak_ewma.rs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (10 lines × 3) finding(s) in Code Duplication — start with layer.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; 1 module(s) off the main sequence.
What to do
- Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
0 of 33 classes have LCOM4 above 3.
D9 · Test Distribution
82 test methods: 20 unit, 62 integration, 0 BDD, 0 e2e. The Rust suite contributes 82 `#[test]` function(s) across 26 file(s) declaring at least one; its unit/integration split is Cargo's own — 16 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, 26 test files): measured (0 flaky).
D12 · Dependency Hygiene
0 outdated, 0 yanked direct Cargo dependencies. Only DIRECT edges are graded: a transitive crate cannot be moved past what its parent's requirement admits, so reporting one would be advice its owner cannot take. A newer release is reported only where this repository's OWN requirement already admits it, so the remedy is `cargo update` and never a manifest edit — which means a release outside the declared range is deliberately NOT charged, because a written-down constraint is a decision rather than a defect. Note that a bare requirement is a CARET, and for a 0.x crate its ceiling is the minor. Whether any crate is UNMAINTAINED is not graded — crates.io publishes no maintenance status, and release age does not stand in for one. Known CVEs in this dependency graph are D30's question, read from Cargo.lock there.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 40 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository commits no Cargo.lock, so its graph was resolved here: its manifests' `[dependencies]` and `[build-dependencies]` closed over the crates.io index, each crate at the newest release its requirement admits (what a fresh `cargo generate-lockfile` picks, not a graph the repository has pinned). Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D16 · Bus Factor
2 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is tower/src/balance/p2c/service.rs. Counted over 56 of the 113 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D17 · Explicit Debt
10 deducted task-comment markers across 12306 LoC (0.1/KLoC) → score 9.9. 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 10 TodoComment finding(s) in Explicit Debt — start with mod.rs (7), main.rs, ordered.rs. — One of this dimension's main actionable groups (10 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
0 of 1 documentation facets pass in full; short on: F2 example. 6 document(s) read across 1 unit(s).
What to do
- Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
1 of 3 build units (Cargo) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
23 finding(s): 0 critical, 23 high, 0 medium, 0 low. 21 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens.
What to do
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
- No action in Static Analysis (SAST) — all 21 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 (21 issue-level, 0 of them charged here).
D34 · Knowledge Freshness
51 of 56 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is tower/src/ready_cache/cache.rs. Counted over 56 of the 113 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 51 Orphaned file finding(s) in Knowledge Freshness — start with mod.rs (9), service.rs (4), lib.rs (3). — One of this dimension's main actionable groups (51 recommendation-level).
- Resolve the 1 Dormant codebase 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 3 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
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
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
P1 · CI/CD gates
P10 · Library API & versioning
- 120/167 types (72%) declared in the published library are public. For a library, every public type is a stability contract — keep implementation types off the surface and expose only the intended API.
What to do
- Keep implementation types off the public surface (Rust: `pub(crate)`, or keep the module private) so internals can change without breaking consumers.
P2 · Observability
What to do
- 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
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.
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
- `trace!` at line 145 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: `trace!(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`. — tower/src/load/peak_ewma.rs:145
- `trace!` at line 256 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: `trace!(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`. — tower/src/load/peak_ewma.rs:256
- `trace!` at line 271 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: `trace!(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`. — tower/src/load/peak_ewma.rs:271
- `error!` at line 217 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`. — tower/src/hedge/mod.rs:217
- `trace!` at line 46 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: `trace!(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`. — tower/src/hedge/rotating_histogram.rs:46
- `trace!` at line 49 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(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`. — tower/src/hedge/rotating_histogram.rs:49
- `trace!` at line 57 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: `trace!(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`. — tower/src/hedge/rotating_histogram.rs:57
What to do
- Interpolated log message defeats structured logging
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 82% | Strong | Solid. |
| Architecture | 92% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 51% | Adequate — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 62% | Strong | Solid. |
| Security | 67% | Adequate — gated by D36 | 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 — 73 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: Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one.
- AX2 Stateful singletons — Not applicable: Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no data at rest for these controls to protect.
- C2 Access Controls — No access-control surface detected in the analyzed source — this repository starts no server another machine can reach (no actix-web HttpServer, axum::serve, Rocket launch, warp::serve, poem or salvo Server, tonic Server::builder, hyper or tiny_http server outside examples and tests, none bound beyond loopback). Access control is therefore N/A here — a crate is authorized by the application that serves it, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~1986 lines of test source are present (.rs) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — Naming consistency is measured on C# only; Rust not measured.
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed Rust surface was not measured.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ projects each declaring an entity of their own. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C# and Visual Basic comments only — this repository's production source is .rs, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.rs), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Cargo manifest — not scanned yet).
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Cargo manifest — not scanned yet).
- D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
- 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 (14 value object(s))
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- M4 Documentation accuracy — Not applicable: the 6 current-state document(s) make no claim of a kind M4 checks. 1 claim(s) of kinds M4 does not check were not checked (path 1); M4 checks only links and versions and artefact counts.
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the Rust source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — 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.
- 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 — 23 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
Serious — 18 finding(s)
- TodoComment tower-test/src/mock/mod.rs:180
- TodoComment tower-test/src/mock/mod.rs:290
- TodoComment tower-test/src/mock/mod.rs:296
- TodoComment tower/tests/balance/main.rs:51
- TodoComment tower/src/util/call_all/ordered.rs:53
- TodoComment tower/src/load/mod.rs:60
- TodoComment tower/src/hedge/mod.rs:201
- TodoComment tower/src/hedge/rotating_histogram.rs:43
- TodoComment tower/src/builder/mod.rs:642
- TodoComment tower/src/builder/mod.rs:647
- REDACTED
- REDACTED
- REDACTED
- CallAll::poll_next (cognitive 19) tower/src/util/call_all/common.rs:92
- REDACTED
- Duplicated block (7 lines × 2) tower/src/load/peak_ewma.rs:125
- Duplicated block (10 lines × 3) tower/src/util/boxed/layer.rs:65
- Off the main sequence: tower-layer
Minor — 72 finding(s)
- Orphaned file tower/src/ready_cache/cache.rs:1
- Orphaned file tower-service/src/lib.rs:1
- Orphaned file tower/src/load/peak_ewma.rs:1
- Orphaned file tower-layer/src/tuple.rs:1
- Orphaned file tower/src/lib.rs:1
- Orphaned file tower/src/buffer/worker.rs:1
- Orphaned file tower/src/hedge/mod.rs:1
- Orphaned file tower/src/retry/budget/tps_budget.rs:1
- Orphaned file tower-test/src/mock/mod.rs:1
- Orphaned file tower/src/make/make_service.rs:1
- Orphaned file tower/src/util/future_service.rs:1
- Orphaned file tower/src/steer/mod.rs:1
- Orphaned file tower/src/load/pending_requests.rs:1
- Orphaned file tower/src/filter/mod.rs:1
- Orphaned file tower/src/util/call_all/ordered.rs:1
- Orphaned file tower/src/util/rng.rs:1
- Orphaned file tower/src/reconnect/mod.rs:1
- Orphaned file tower/src/buffer/service.rs:1
- Orphaned file tower/src/util/boxed/layer_clone_sync.rs:1
- Orphaned file tower/src/util/boxed/layer_clone.rs:1
- Orphaned file tower/src/util/call_all/common.rs:1
- Orphaned file tower/src/make/make_service/shared.rs:1
- Orphaned file tower/src/retry/future.rs:1
- Orphaned file tower/src/util/boxed_clone.rs:1
- Orphaned file tower/src/load/mod.rs:1
- Interpolated log message defeats structured logging tower/src/load/peak_ewma.rs:145
- Interpolated log message defeats structured logging tower/src/load/peak_ewma.rs:256
- Interpolated log message defeats structured logging tower/src/load/peak_ewma.rs:271
- Interpolated log message defeats structured logging tower/src/hedge/mod.rs:217
- Interpolated log message defeats structured logging tower/src/hedge/rotating_histogram.rs:46
- Interpolated log message defeats structured logging tower/src/hedge/rotating_histogram.rs:49
- Interpolated log message defeats structured logging tower/src/hedge/rotating_histogram.rs:57
- Off-boarding risk: anonymized user #1
- Documentation: no build, run or usage example README.md:1
- Projects may be oversized for their cohesion
- Dormant codebase
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Inverted test pyramid
- No ADRs
- No architecture diagram/doc
- Large public API surface
- No release approval gate
- No security response headers detected netlify.toml:1
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-6572c3b11501420e9c6c67daa8db1833/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-6572c3b11501420e9c6c67daa8db1833/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 . | 23 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Cargo manifest — not scanned yet). | 0 | — |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Cargo manifest — not scanned yet). | 0 | — |