Executive summary
crossbeam-rs/crossbeam meets our standard for a preview release, though we found no recorded design decisions and no architecture document or diagram. It scores 74 out of 100 and is rated Strong, and it has no critical findings.
Maturity, at 61, is the weakest lens and counts most in the score. The best first step for the work it takes is fixing the part of the code only one person knows, worth about 6 points. Recording design decisions comes next, worth about 11 points.
Most of the 144 serious findings are in Code Health.
The product code is 25,037 lines, about €60,000 to rebuild.
If Maturity rose from 61 to 62, the lowest score rated Strong, the score would rise from 74 to about 74.
Rebuild cost: about €60,000 · Estimate
| Cost to rebuild | €20,000 to €99,000, for 330 to 1,047 hours of work, about 0.4 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 | ×1.1 at a score of 74. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Medium: 25,037 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 crossbeam_channel.counter | 2 crossbeam_channel.err | 3 crossbeam_channel.utils | 4 crossbeam_epoch.deferred | 5 crossbeam_epoch.epoch | 6 crossbeam_epoch.primitive.cell | 7 crossbeam_epoch.sealed | 8 crossbeam_utils.atomic.seq_lock | 9 crossbeam_utils.cache_padded | 10 crossbeam_channel.waker | 11 crossbeam_deque.deque | 12 crossbeam_epoch.sync.queue | 13 crossbeam_utils.atomic.atomic_cell | 14 crossbeam_utils.atomic.seq_lock_wide | 15 crossbeam_utils.sync.once_lock | 16 crossbeam_utils.sync.sharded_lock | 17 crossbeam_utils.thread.unix | 18 crossbeam_channel.flavors.array | 19 crossbeam_channel.flavors.list | 20 crossbeam_channel.flavors.zero | 21 crossbeam_channel.select | 22 crossbeam_channel.context | 23 crossbeam_channel.channel | 24 crossbeam_channel.flavors.at | 25 crossbeam_channel.flavors.never | 26 crossbeam_channel.flavors.tick | 27 crossbeam_utils.sync.parker | 28 crossbeam_utils.sync.wait_group | 29 crossbeam_epoch.sync.list | 30 crossbeam_queue.array_queue | 31 crossbeam_queue.seg_queue | 32 crossbeam_utils.thread | 33 crossbeam_epoch.internal | 34 crossbeam_epoch.collector | 35 crossbeam_epoch.guard | 36 crossbeam_epoch.atomic | 37 crossbeam_epoch.default | 38 crossbeam_skiplist.base | 39 crossbeam_skiplist.map | 40 crossbeam_skiplist.set |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 crossbeam_channel.counter | ||||||||||||||||||||||||||||||||||||||||
| 2 crossbeam_channel.err | ||||||||||||||||||||||||||||||||||||||||
| 3 crossbeam_channel.utils | ||||||||||||||||||||||||||||||||||||||||
| 4 crossbeam_epoch.deferred | ||||||||||||||||||||||||||||||||||||||||
| 5 crossbeam_epoch.epoch | ||||||||||||||||||||||||||||||||||||||||
| 6 crossbeam_epoch.primitive.cell | ||||||||||||||||||||||||||||||||||||||||
| 7 crossbeam_epoch.sealed | ||||||||||||||||||||||||||||||||||||||||
| 8 crossbeam_utils.atomic.seq_lock | ||||||||||||||||||||||||||||||||||||||||
| 9 crossbeam_utils.cache_padded | ||||||||||||||||||||||||||||||||||||||||
| 10 crossbeam_channel.waker | 3 | 3 | ||||||||||||||||||||||||||||||||||||||
| 11 crossbeam_deque.deque | 1 | 4 | ||||||||||||||||||||||||||||||||||||||
| 12 crossbeam_epoch.sync.queue | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 13 crossbeam_utils.atomic.atomic_cell | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 14 crossbeam_utils.atomic.seq_lock_wide | 2 | |||||||||||||||||||||||||||||||||||||||
| 15 crossbeam_utils.sync.once_lock | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 crossbeam_utils.sync.sharded_lock | 2 | |||||||||||||||||||||||||||||||||||||||
| 17 crossbeam_utils.thread.unix | 1 | |||||||||||||||||||||||||||||||||||||||
| 18 crossbeam_channel.flavors.array | 1 | 1 | 1 | 7 | 2 | 2 | ||||||||||||||||||||||||||||||||||
| 19 crossbeam_channel.flavors.list | 1 | 1 | 1 | 2 | 7 | 2 | 2 | |||||||||||||||||||||||||||||||||
| 20 crossbeam_channel.flavors.zero | 1 | 1 | 2 | 7 | 3 | 2 | ||||||||||||||||||||||||||||||||||
| 21 crossbeam_channel.select | 1 | 1 | 1 | 1 | 6 | |||||||||||||||||||||||||||||||||||
| 22 crossbeam_channel.context | 1 | |||||||||||||||||||||||||||||||||||||||
| 23 crossbeam_channel.channel | 7 | 2 | ||||||||||||||||||||||||||||||||||||||
| 24 crossbeam_channel.flavors.at | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 25 crossbeam_channel.flavors.never | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 26 crossbeam_channel.flavors.tick | 1 | 3 | 1 | |||||||||||||||||||||||||||||||||||||
| 27 crossbeam_utils.sync.parker | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 28 crossbeam_utils.sync.wait_group | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 29 crossbeam_epoch.sync.list | 1 | 4 | 5 | |||||||||||||||||||||||||||||||||||||
| 30 crossbeam_queue.array_queue | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 31 crossbeam_queue.seg_queue | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 32 crossbeam_utils.thread | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 33 crossbeam_epoch.internal | 2 | 3 | 1 | 2 | 1 | 1 | 2 | 2 | 2 | |||||||||||||||||||||||||||||||
| 34 crossbeam_epoch.collector | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 35 crossbeam_epoch.guard | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 36 crossbeam_epoch.atomic | 3 | 2 | ||||||||||||||||||||||||||||||||||||||
| 37 crossbeam_epoch.default | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 38 crossbeam_skiplist.base | 1 | 1 | 1 | 1 | 2 | 1 | 8 | 6 | ||||||||||||||||||||||||||||||||
| 39 crossbeam_skiplist.map | 3 | 3 | 5 | |||||||||||||||||||||||||||||||||||||
| 40 crossbeam_skiplist.set | 2 | 4 | 2 | 1 |
10→21 crossbeam_channel.waker uses crossbeam_channel.select part of a loop✕
- Connections
- 3 pairs of types, where a type in crossbeam_channel.waker uses a type in crossbeam_channel.select.
- The types involved
crossbeam_channel.waker.Entry→crossbeam_channel.select.Operationcrossbeam_channel.waker.SyncWaker→crossbeam_channel.select.Operationcrossbeam_channel.waker.Waker→crossbeam_channel.select.Operation
- Direction
- crossbeam_channel.waker uses crossbeam_channel.select, so a change to crossbeam_channel.select can break crossbeam_channel.waker, while a change to crossbeam_channel.waker can't break crossbeam_channel.select.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→22 crossbeam_channel.waker uses crossbeam_channel.context part of a loop✕
- Connections
- 3 pairs of types, where a type in crossbeam_channel.waker uses a type in crossbeam_channel.context.
- The types involved
crossbeam_channel.waker.Entry→crossbeam_channel.context.Contextcrossbeam_channel.waker.SyncWaker→crossbeam_channel.context.Contextcrossbeam_channel.waker.Waker→crossbeam_channel.context.Context
- Direction
- crossbeam_channel.waker uses crossbeam_channel.context, so a change to crossbeam_channel.context can break crossbeam_channel.waker, while a change to crossbeam_channel.waker can't break crossbeam_channel.context.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→6 crossbeam_deque.deque uses crossbeam_epoch.primitive.cell✕
- Connections
- 1 pair of types, where a type in crossbeam_deque.deque uses a type in crossbeam_epoch.primitive.cell.
- The types involved
crossbeam_deque.deque.Slot→crossbeam_epoch.primitive.cell.UnsafeCell
- Direction
- crossbeam_deque.deque uses crossbeam_epoch.primitive.cell, so a change to crossbeam_epoch.primitive.cell can break crossbeam_deque.deque, while a change to crossbeam_deque.deque can't break crossbeam_epoch.primitive.cell.
- Position
- Below the diagonal: crossbeam_deque.deque uses a module listed above it, which is the healthy direction.
11→9 crossbeam_deque.deque uses crossbeam_utils.cache_padded✕
- Connections
- 4 pairs of types, where a type in crossbeam_deque.deque uses a type in crossbeam_utils.cache_padded.
- The types involved
crossbeam_deque.deque.Injector→crossbeam_utils.cache_padded.CachePaddedcrossbeam_deque.deque.Inner→crossbeam_utils.cache_padded.CachePaddedcrossbeam_deque.deque.Stealer→crossbeam_utils.cache_padded.CachePaddedcrossbeam_deque.deque.Worker→crossbeam_utils.cache_padded.CachePadded
- Direction
- crossbeam_deque.deque uses crossbeam_utils.cache_padded, so a change to crossbeam_utils.cache_padded can break crossbeam_deque.deque, while a change to crossbeam_deque.deque can't break crossbeam_utils.cache_padded.
- Position
- Below the diagonal: crossbeam_deque.deque uses a module listed above it, which is the healthy direction.
12→9 crossbeam_epoch.sync.queue uses crossbeam_utils.cache_padded✕
- Connections
- 1 pair of types, where a type in crossbeam_epoch.sync.queue uses a type in crossbeam_utils.cache_padded.
- The types involved
crossbeam_epoch.sync.queue.Queue→crossbeam_utils.cache_padded.CachePadded
- Direction
- crossbeam_epoch.sync.queue uses crossbeam_utils.cache_padded, so a change to crossbeam_utils.cache_padded can break crossbeam_epoch.sync.queue, while a change to crossbeam_epoch.sync.queue can't break crossbeam_utils.cache_padded.
- Position
- Below the diagonal: crossbeam_epoch.sync.queue uses a module listed above it, which is the healthy direction.
12→35 crossbeam_epoch.sync.queue uses crossbeam_epoch.guard part of a loop✕
- Connections
- 1 pair of types, where a type in crossbeam_epoch.sync.queue uses a type in crossbeam_epoch.guard.
- The types involved
crossbeam_epoch.sync.queue.Queue→crossbeam_epoch.guard.Guard
- Direction
- crossbeam_epoch.sync.queue uses crossbeam_epoch.guard, so a change to crossbeam_epoch.guard can break crossbeam_epoch.sync.queue, while a change to crossbeam_epoch.sync.queue can't break crossbeam_epoch.guard.
- 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.
12→36 crossbeam_epoch.sync.queue uses crossbeam_epoch.atomic part of a loop✕
- Connections
- 2 pairs of types, where a type in crossbeam_epoch.sync.queue uses a type in crossbeam_epoch.atomic.
- The types involved
crossbeam_epoch.sync.queue.Node→crossbeam_epoch.atomic.Atomiccrossbeam_epoch.sync.queue.Queue→crossbeam_epoch.atomic.Shared
- Direction
- crossbeam_epoch.sync.queue uses crossbeam_epoch.atomic, so a change to crossbeam_epoch.atomic can break crossbeam_epoch.sync.queue, while a change to crossbeam_epoch.sync.queue can't break crossbeam_epoch.atomic.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→6 crossbeam_utils.atomic.atomic_cell uses crossbeam_epoch.primitive.cell✕
- Connections
- 1 pair of types, where a type in crossbeam_utils.atomic.atomic_cell uses a type in crossbeam_epoch.primitive.cell.
- The types involved
crossbeam_utils.atomic.atomic_cell.AtomicCell→crossbeam_epoch.primitive.cell.UnsafeCell
- Direction
- crossbeam_utils.atomic.atomic_cell uses crossbeam_epoch.primitive.cell, so a change to crossbeam_epoch.primitive.cell can break crossbeam_utils.atomic.atomic_cell, while a change to crossbeam_utils.atomic.atomic_cell can't break crossbeam_epoch.primitive.cell.
- Position
- Below the diagonal: crossbeam_utils.atomic.atomic_cell uses a module listed above it, which is the healthy direction.
13→8 crossbeam_utils.atomic.atomic_cell uses crossbeam_utils.atomic.seq_lock✕
- Connections
- 1 pair of types, where a type in crossbeam_utils.atomic.atomic_cell uses a type in crossbeam_utils.atomic.seq_lock.
- The types involved
crossbeam_utils.atomic.atomic_cell.atomic_cell$module→crossbeam_utils.atomic.seq_lock.SeqLock
- Direction
- crossbeam_utils.atomic.atomic_cell uses crossbeam_utils.atomic.seq_lock, so a change to crossbeam_utils.atomic.seq_lock can break crossbeam_utils.atomic.atomic_cell, while a change to crossbeam_utils.atomic.atomic_cell can't break crossbeam_utils.atomic.seq_lock.
- Position
- Below the diagonal: crossbeam_utils.atomic.atomic_cell uses a module listed above it, which is the healthy direction.
14→8 crossbeam_utils.atomic.seq_lock_wide uses crossbeam_utils.atomic.seq_lock✕
- Connections
- 2 pairs of types, where a type in crossbeam_utils.atomic.seq_lock_wide uses a type in crossbeam_utils.atomic.seq_lock.
- The types involved
crossbeam_utils.atomic.seq_lock_wide.SeqLock→crossbeam_utils.atomic.seq_lock.SeqLockWriteGuardcrossbeam_utils.atomic.seq_lock_wide.SeqLockWriteGuard→crossbeam_utils.atomic.seq_lock.SeqLock
- Direction
- crossbeam_utils.atomic.seq_lock_wide uses crossbeam_utils.atomic.seq_lock, so a change to crossbeam_utils.atomic.seq_lock can break crossbeam_utils.atomic.seq_lock_wide, while a change to crossbeam_utils.atomic.seq_lock_wide can't break crossbeam_utils.atomic.seq_lock.
- Position
- Below the diagonal: crossbeam_utils.atomic.seq_lock_wide uses a module listed above it, which is the healthy direction.
15→6 crossbeam_utils.sync.once_lock uses crossbeam_epoch.primitive.cell✕
- Connections
- 1 pair of types, where a type in crossbeam_utils.sync.once_lock uses a type in crossbeam_epoch.primitive.cell.
- The types involved
crossbeam_utils.sync.once_lock.OnceLock→crossbeam_epoch.primitive.cell.UnsafeCell
- Direction
- crossbeam_utils.sync.once_lock uses crossbeam_epoch.primitive.cell, so a change to crossbeam_epoch.primitive.cell can break crossbeam_utils.sync.once_lock, while a change to crossbeam_utils.sync.once_lock can't break crossbeam_epoch.primitive.cell.
- Position
- Below the diagonal: crossbeam_utils.sync.once_lock uses a module listed above it, which is the healthy direction.
16→6 crossbeam_utils.sync.sharded_lock uses crossbeam_epoch.primitive.cell✕
- Connections
- 2 pairs of types, where a type in crossbeam_utils.sync.sharded_lock uses a type in crossbeam_epoch.primitive.cell.
- The types involved
crossbeam_utils.sync.sharded_lock.Shard→crossbeam_epoch.primitive.cell.UnsafeCellcrossbeam_utils.sync.sharded_lock.ShardedLock→crossbeam_epoch.primitive.cell.UnsafeCell
- Direction
- crossbeam_utils.sync.sharded_lock uses crossbeam_epoch.primitive.cell, so a change to crossbeam_epoch.primitive.cell can break crossbeam_utils.sync.sharded_lock, while a change to crossbeam_utils.sync.sharded_lock can't break crossbeam_epoch.primitive.cell.
- Position
- Below the diagonal: crossbeam_utils.sync.sharded_lock uses a module listed above it, which is the healthy direction.
17→7 crossbeam_utils.thread.unix uses crossbeam_epoch.sealed✕
- Connections
- 1 pair of types, where a type in crossbeam_utils.thread.unix uses a type in crossbeam_epoch.sealed.
- The types involved
crossbeam_utils.thread.unix.JoinHandleExt→crossbeam_epoch.sealed.Sealed
- Direction
- crossbeam_utils.thread.unix uses crossbeam_epoch.sealed, so a change to crossbeam_epoch.sealed can break crossbeam_utils.thread.unix, while a change to crossbeam_utils.thread.unix can't break crossbeam_epoch.sealed.
- Position
- Below the diagonal: crossbeam_utils.thread.unix uses a module listed above it, which is the healthy direction.
18→6 crossbeam_channel.flavors.array uses crossbeam_epoch.primitive.cell✕
- Connections
- 1 pair of types, where a type in crossbeam_channel.flavors.array uses a type in crossbeam_epoch.primitive.cell.
- The types involved
crossbeam_channel.flavors.array.Slot→crossbeam_epoch.primitive.cell.UnsafeCell
- Direction
- crossbeam_channel.flavors.array uses crossbeam_epoch.primitive.cell, so a change to crossbeam_epoch.primitive.cell can break crossbeam_channel.flavors.array, while a change to crossbeam_channel.flavors.array can't break crossbeam_epoch.primitive.cell.
- Position
- Below the diagonal: crossbeam_channel.flavors.array uses a module listed above it, which is the healthy direction.
18→9 crossbeam_channel.flavors.array uses crossbeam_utils.cache_padded✕
- Connections
- 1 pair of types, where a type in crossbeam_channel.flavors.array uses a type in crossbeam_utils.cache_padded.
- The types involved
crossbeam_channel.flavors.array.Channel→crossbeam_utils.cache_padded.CachePadded
- Direction
- crossbeam_channel.flavors.array uses crossbeam_utils.cache_padded, so a change to crossbeam_utils.cache_padded can break crossbeam_channel.flavors.array, while a change to crossbeam_channel.flavors.array can't break crossbeam_utils.cache_padded.
- Position
- Below the diagonal: crossbeam_channel.flavors.array uses a module listed above it, which is the healthy direction.
18→10 crossbeam_channel.flavors.array uses crossbeam_channel.waker✕
- Connections
- 1 pair of types, where a type in crossbeam_channel.flavors.array uses a type in crossbeam_channel.waker.
- The types involved
crossbeam_channel.flavors.array.Channel→crossbeam_channel.waker.SyncWaker
- Direction
- crossbeam_channel.flavors.array uses crossbeam_channel.waker, so a change to crossbeam_channel.waker can break crossbeam_channel.flavors.array, while a change to crossbeam_channel.flavors.array can't break crossbeam_channel.waker.
- Position
- Below the diagonal: crossbeam_channel.flavors.array uses a module listed above it, which is the healthy direction.
18→21 crossbeam_channel.flavors.array uses crossbeam_channel.select part of a loop✕
- Connections
- 7 pairs of types, where a type in crossbeam_channel.flavors.array uses a type in crossbeam_channel.select.
- The types involved
crossbeam_channel.flavors.array.Channel→crossbeam_channel.select.Tokencrossbeam_channel.flavors.array.Receiver→crossbeam_channel.select.Operationcrossbeam_channel.flavors.array.Receiver→crossbeam_channel.select.SelectHandlecrossbeam_channel.flavors.array.Receiver→crossbeam_channel.select.Tokencrossbeam_channel.flavors.array.Sender→crossbeam_channel.select.Operationcrossbeam_channel.flavors.array.Sender→crossbeam_channel.select.SelectHandlecrossbeam_channel.flavors.array.Sender→crossbeam_channel.select.Token
- Direction
- crossbeam_channel.flavors.array uses crossbeam_channel.select, so a change to crossbeam_channel.select can break crossbeam_channel.flavors.array, while a change to crossbeam_channel.flavors.array can't break crossbeam_channel.select.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→22 crossbeam_channel.flavors.array uses crossbeam_channel.context part of a loop✕
- Connections
- 2 pairs of types, where a type in crossbeam_channel.flavors.array uses a type in crossbeam_channel.context.
- The types involved
crossbeam_channel.flavors.array.Receiver→crossbeam_channel.context.Contextcrossbeam_channel.flavors.array.Sender→crossbeam_channel.context.Context
- Direction
- crossbeam_channel.flavors.array uses crossbeam_channel.context, so a change to crossbeam_channel.context can break crossbeam_channel.flavors.array, while a change to crossbeam_channel.flavors.array can't break crossbeam_channel.context.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→23 crossbeam_channel.flavors.array uses crossbeam_channel.channel part of a loop✕
- Connections
- 2 pairs of types, where a type in crossbeam_channel.flavors.array uses a type in crossbeam_channel.channel.
- The types involved
crossbeam_channel.flavors.array.Channel→crossbeam_channel.channel.Receivercrossbeam_channel.flavors.array.Channel→crossbeam_channel.channel.Sender
- Direction
- crossbeam_channel.flavors.array uses crossbeam_channel.channel, so a change to crossbeam_channel.channel can break crossbeam_channel.flavors.array, while a change to crossbeam_channel.flavors.array can't break crossbeam_channel.channel.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→6 crossbeam_channel.flavors.list uses crossbeam_epoch.primitive.cell✕
- Connections
- 1 pair of types, where a type in crossbeam_channel.flavors.list uses a type in crossbeam_epoch.primitive.cell.
- The types involved
crossbeam_channel.flavors.list.Slot→crossbeam_epoch.primitive.cell.UnsafeCell
- Direction
- crossbeam_channel.flavors.list uses crossbeam_epoch.primitive.cell, so a change to crossbeam_epoch.primitive.cell can break crossbeam_channel.flavors.list, while a change to crossbeam_channel.flavors.list can't break crossbeam_epoch.primitive.cell.
- Position
- Below the diagonal: crossbeam_channel.flavors.list uses a module listed above it, which is the healthy direction.
19→9 crossbeam_channel.flavors.list uses crossbeam_utils.cache_padded✕
- Connections
- 1 pair of types, where a type in crossbeam_channel.flavors.list uses a type in crossbeam_utils.cache_padded.
- The types involved
crossbeam_channel.flavors.list.Channel→crossbeam_utils.cache_padded.CachePadded
- Direction
- crossbeam_channel.flavors.list uses crossbeam_utils.cache_padded, so a change to crossbeam_utils.cache_padded can break crossbeam_channel.flavors.list, while a change to crossbeam_channel.flavors.list can't break crossbeam_utils.cache_padded.
- Position
- Below the diagonal: crossbeam_channel.flavors.list uses a module listed above it, which is the healthy direction.
19→10 crossbeam_channel.flavors.list uses crossbeam_channel.waker✕
- Connections
- 1 pair of types, where a type in crossbeam_channel.flavors.list uses a type in crossbeam_channel.waker.
- The types involved
crossbeam_channel.flavors.list.Channel→crossbeam_channel.waker.SyncWaker
- Direction
- crossbeam_channel.flavors.list uses crossbeam_channel.waker, so a change to crossbeam_channel.waker can break crossbeam_channel.flavors.list, while a change to crossbeam_channel.flavors.list can't break crossbeam_channel.waker.
- Position
- Below the diagonal: crossbeam_channel.flavors.list uses a module listed above it, which is the healthy direction.
19→18 crossbeam_channel.flavors.list uses crossbeam_channel.flavors.array✕
- Connections
- 2 pairs of types, where a type in crossbeam_channel.flavors.list uses a type in crossbeam_channel.flavors.array.
- The types involved
crossbeam_channel.flavors.list.Receiver→crossbeam_channel.flavors.array.Channelcrossbeam_channel.flavors.list.Sender→crossbeam_channel.flavors.array.Channel
- Direction
- crossbeam_channel.flavors.list uses crossbeam_channel.flavors.array, so a change to crossbeam_channel.flavors.array can break crossbeam_channel.flavors.list, while a change to crossbeam_channel.flavors.list can't break crossbeam_channel.flavors.array.
- Position
- Below the diagonal: crossbeam_channel.flavors.list uses a module listed above it, which is the healthy direction.
19→21 crossbeam_channel.flavors.list uses crossbeam_channel.select part of a loop✕
- Connections
- 7 pairs of types, where a type in crossbeam_channel.flavors.list uses a type in crossbeam_channel.select.
- The types involved
crossbeam_channel.flavors.list.Channel→crossbeam_channel.select.Tokencrossbeam_channel.flavors.list.Receiver→crossbeam_channel.select.Operationcrossbeam_channel.flavors.list.Receiver→crossbeam_channel.select.SelectHandlecrossbeam_channel.flavors.list.Receiver→crossbeam_channel.select.Tokencrossbeam_channel.flavors.list.Sender→crossbeam_channel.select.Operationcrossbeam_channel.flavors.list.Sender→crossbeam_channel.select.SelectHandlecrossbeam_channel.flavors.list.Sender→crossbeam_channel.select.Token
- Direction
- crossbeam_channel.flavors.list uses crossbeam_channel.select, so a change to crossbeam_channel.select can break crossbeam_channel.flavors.list, while a change to crossbeam_channel.flavors.list can't break crossbeam_channel.select.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→22 crossbeam_channel.flavors.list uses crossbeam_channel.context part of a loop✕
- Connections
- 2 pairs of types, where a type in crossbeam_channel.flavors.list uses a type in crossbeam_channel.context.
- The types involved
crossbeam_channel.flavors.list.Receiver→crossbeam_channel.context.Contextcrossbeam_channel.flavors.list.Sender→crossbeam_channel.context.Context
- Direction
- crossbeam_channel.flavors.list uses crossbeam_channel.context, so a change to crossbeam_channel.context can break crossbeam_channel.flavors.list, while a change to crossbeam_channel.flavors.list can't break crossbeam_channel.context.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→23 crossbeam_channel.flavors.list uses crossbeam_channel.channel part of a loop✕
- Connections
- 2 pairs of types, where a type in crossbeam_channel.flavors.list uses a type in crossbeam_channel.channel.
- The types involved
crossbeam_channel.flavors.list.Channel→crossbeam_channel.channel.Receivercrossbeam_channel.flavors.list.Channel→crossbeam_channel.channel.Sender
- Direction
- crossbeam_channel.flavors.list uses crossbeam_channel.channel, so a change to crossbeam_channel.channel can break crossbeam_channel.flavors.list, while a change to crossbeam_channel.flavors.list can't break crossbeam_channel.channel.
- 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.
20→6 crossbeam_channel.flavors.zero uses crossbeam_epoch.primitive.cell✕
- Connections
- 1 pair of types, where a type in crossbeam_channel.flavors.zero uses a type in crossbeam_epoch.primitive.cell.
- The types involved
crossbeam_channel.flavors.zero.Packet→crossbeam_epoch.primitive.cell.UnsafeCell
- Direction
- crossbeam_channel.flavors.zero uses crossbeam_epoch.primitive.cell, so a change to crossbeam_epoch.primitive.cell can break crossbeam_channel.flavors.zero, while a change to crossbeam_channel.flavors.zero can't break crossbeam_epoch.primitive.cell.
- Position
- Below the diagonal: crossbeam_channel.flavors.zero uses a module listed above it, which is the healthy direction.
20→10 crossbeam_channel.flavors.zero uses crossbeam_channel.waker✕
- Connections
- 1 pair of types, where a type in crossbeam_channel.flavors.zero uses a type in crossbeam_channel.waker.
- The types involved
crossbeam_channel.flavors.zero.Inner→crossbeam_channel.waker.Waker
- Direction
- crossbeam_channel.flavors.zero uses crossbeam_channel.waker, so a change to crossbeam_channel.waker can break crossbeam_channel.flavors.zero, while a change to crossbeam_channel.flavors.zero can't break crossbeam_channel.waker.
- Position
- Below the diagonal: crossbeam_channel.flavors.zero uses a module listed above it, which is the healthy direction.
20→18 crossbeam_channel.flavors.zero uses crossbeam_channel.flavors.array✕
- Connections
- 2 pairs of types, where a type in crossbeam_channel.flavors.zero uses a type in crossbeam_channel.flavors.array.
- The types involved
crossbeam_channel.flavors.zero.Receiver→crossbeam_channel.flavors.array.Channelcrossbeam_channel.flavors.zero.Sender→crossbeam_channel.flavors.array.Channel
- Direction
- crossbeam_channel.flavors.zero uses crossbeam_channel.flavors.array, so a change to crossbeam_channel.flavors.array can break crossbeam_channel.flavors.zero, while a change to crossbeam_channel.flavors.zero can't break crossbeam_channel.flavors.array.
- Position
- Below the diagonal: crossbeam_channel.flavors.zero uses a module listed above it, which is the healthy direction.
20→21 crossbeam_channel.flavors.zero uses crossbeam_channel.select part of a loop✕
- Connections
- 7 pairs of types, where a type in crossbeam_channel.flavors.zero uses a type in crossbeam_channel.select.
- The types involved
crossbeam_channel.flavors.zero.Channel→crossbeam_channel.select.Tokencrossbeam_channel.flavors.zero.Receiver→crossbeam_channel.select.Operationcrossbeam_channel.flavors.zero.Receiver→crossbeam_channel.select.SelectHandlecrossbeam_channel.flavors.zero.Receiver→crossbeam_channel.select.Tokencrossbeam_channel.flavors.zero.Sender→crossbeam_channel.select.Operationcrossbeam_channel.flavors.zero.Sender→crossbeam_channel.select.SelectHandlecrossbeam_channel.flavors.zero.Sender→crossbeam_channel.select.Token
- Direction
- crossbeam_channel.flavors.zero uses crossbeam_channel.select, so a change to crossbeam_channel.select can break crossbeam_channel.flavors.zero, while a change to crossbeam_channel.flavors.zero can't break crossbeam_channel.select.
- 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.
20→22 crossbeam_channel.flavors.zero uses crossbeam_channel.context part of a loop✕
- Connections
- 3 pairs of types, where a type in crossbeam_channel.flavors.zero uses a type in crossbeam_channel.context.
- The types involved
crossbeam_channel.flavors.zero.Channel→crossbeam_channel.context.Innercrossbeam_channel.flavors.zero.Receiver→crossbeam_channel.context.Contextcrossbeam_channel.flavors.zero.Sender→crossbeam_channel.context.Context
- Direction
- crossbeam_channel.flavors.zero uses crossbeam_channel.context, so a change to crossbeam_channel.context can break crossbeam_channel.flavors.zero, while a change to crossbeam_channel.flavors.zero can't break crossbeam_channel.context.
- 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.
20→23 crossbeam_channel.flavors.zero uses crossbeam_channel.channel part of a loop✕
- Connections
- 2 pairs of types, where a type in crossbeam_channel.flavors.zero uses a type in crossbeam_channel.channel.
- The types involved
crossbeam_channel.flavors.zero.Channel→crossbeam_channel.channel.Receivercrossbeam_channel.flavors.zero.Channel→crossbeam_channel.channel.Sender
- Direction
- crossbeam_channel.flavors.zero uses crossbeam_channel.channel, so a change to crossbeam_channel.channel can break crossbeam_channel.flavors.zero, while a change to crossbeam_channel.flavors.zero can't break crossbeam_channel.channel.
- 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.
21→18 crossbeam_channel.select uses crossbeam_channel.flavors.array✕
- Connections
- 1 pair of types, where a type in crossbeam_channel.select uses a type in crossbeam_channel.flavors.array.
- The types involved
crossbeam_channel.select.Token→crossbeam_channel.flavors.array.ArrayToken
- Direction
- crossbeam_channel.select uses crossbeam_channel.flavors.array, so a change to crossbeam_channel.flavors.array can break crossbeam_channel.select, while a change to crossbeam_channel.select can't break crossbeam_channel.flavors.array.
- Position
- Below the diagonal: crossbeam_channel.select uses a module listed above it, which is the healthy direction.
21→19 crossbeam_channel.select uses crossbeam_channel.flavors.list✕
- Connections
- 1 pair of types, where a type in crossbeam_channel.select uses a type in crossbeam_channel.flavors.list.
- The types involved
crossbeam_channel.select.Token→crossbeam_channel.flavors.list.ListToken
- Direction
- crossbeam_channel.select uses crossbeam_channel.flavors.list, so a change to crossbeam_channel.flavors.list can break crossbeam_channel.select, while a change to crossbeam_channel.select can't break crossbeam_channel.flavors.list.
- Position
- Below the diagonal: crossbeam_channel.select uses a module listed above it, which is the healthy direction.
21→20 crossbeam_channel.select uses crossbeam_channel.flavors.zero✕
- Connections
- 1 pair of types, where a type in crossbeam_channel.select uses a type in crossbeam_channel.flavors.zero.
- The types involved
crossbeam_channel.select.Token→crossbeam_channel.flavors.zero.ZeroToken
- Direction
- crossbeam_channel.select uses crossbeam_channel.flavors.zero, so a change to crossbeam_channel.flavors.zero can break crossbeam_channel.select, while a change to crossbeam_channel.select can't break crossbeam_channel.flavors.zero.
- Position
- Below the diagonal: crossbeam_channel.select uses a module listed above it, which is the healthy direction.
21→22 crossbeam_channel.select uses crossbeam_channel.context part of a loop✕
- Connections
- 1 pair of types, where a type in crossbeam_channel.select uses a type in crossbeam_channel.context.
- The types involved
crossbeam_channel.select.SelectHandle→crossbeam_channel.context.Context
- Direction
- crossbeam_channel.select uses crossbeam_channel.context, so a change to crossbeam_channel.context can break crossbeam_channel.select, while a change to crossbeam_channel.select can't break crossbeam_channel.context.
- 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.
21→23 crossbeam_channel.select uses crossbeam_channel.channel part of a loop✕
- Connections
- 6 pairs of types, where a type in crossbeam_channel.select uses a type in crossbeam_channel.channel.
- The types involved
crossbeam_channel.select.Select→crossbeam_channel.channel.Receivercrossbeam_channel.select.Select→crossbeam_channel.channel.Sendercrossbeam_channel.select.SelectedOperation→crossbeam_channel.channel.Receivercrossbeam_channel.select.SelectedOperation→crossbeam_channel.channel.Sendercrossbeam_channel.select.select$module→crossbeam_channel.channel.Receivercrossbeam_channel.select.select$module→crossbeam_channel.channel.Sender
- Direction
- crossbeam_channel.select uses crossbeam_channel.channel, so a change to crossbeam_channel.channel can break crossbeam_channel.select, while a change to crossbeam_channel.select can't break crossbeam_channel.channel.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
22→21 crossbeam_channel.context uses crossbeam_channel.select✕
- Connections
- 1 pair of types, where a type in crossbeam_channel.context uses a type in crossbeam_channel.select.
- The types involved
crossbeam_channel.context.Context→crossbeam_channel.select.Selected
- Direction
- crossbeam_channel.context uses crossbeam_channel.select, so a change to crossbeam_channel.select can break crossbeam_channel.context, while a change to crossbeam_channel.context can't break crossbeam_channel.select.
- Position
- Below the diagonal: crossbeam_channel.context uses a module listed above it, which is the healthy direction.
23→21 crossbeam_channel.channel uses crossbeam_channel.select✕
- Connections
- 7 pairs of types, where a type in crossbeam_channel.channel uses a type in crossbeam_channel.select.
- The types involved
crossbeam_channel.channel.Receiver→crossbeam_channel.select.Operationcrossbeam_channel.channel.Receiver→crossbeam_channel.select.SelectHandlecrossbeam_channel.channel.Receiver→crossbeam_channel.select.Tokencrossbeam_channel.channel.Sender→crossbeam_channel.select.Operationcrossbeam_channel.channel.Sender→crossbeam_channel.select.SelectHandlecrossbeam_channel.channel.Sender→crossbeam_channel.select.Tokencrossbeam_channel.channel.channel$module→crossbeam_channel.select.Token
- Direction
- crossbeam_channel.channel uses crossbeam_channel.select, so a change to crossbeam_channel.select can break crossbeam_channel.channel, while a change to crossbeam_channel.channel can't break crossbeam_channel.select.
- Position
- Below the diagonal: crossbeam_channel.channel uses a module listed above it, which is the healthy direction.
23→22 crossbeam_channel.channel uses crossbeam_channel.context✕
- Connections
- 2 pairs of types, where a type in crossbeam_channel.channel uses a type in crossbeam_channel.context.
- The types involved
crossbeam_channel.channel.Receiver→crossbeam_channel.context.Contextcrossbeam_channel.channel.Sender→crossbeam_channel.context.Context
- Direction
- crossbeam_channel.channel uses crossbeam_channel.context, so a change to crossbeam_channel.context can break crossbeam_channel.channel, while a change to crossbeam_channel.channel can't break crossbeam_channel.context.
- Position
- Below the diagonal: crossbeam_channel.channel uses a module listed above it, which is the healthy direction.
24→21 crossbeam_channel.flavors.at uses crossbeam_channel.select✕
- Connections
- 3 pairs of types, where a type in crossbeam_channel.flavors.at uses a type in crossbeam_channel.select.
- The types involved
crossbeam_channel.flavors.at.Channel→crossbeam_channel.select.Operationcrossbeam_channel.flavors.at.Channel→crossbeam_channel.select.SelectHandlecrossbeam_channel.flavors.at.Channel→crossbeam_channel.select.Token
- Direction
- crossbeam_channel.flavors.at uses crossbeam_channel.select, so a change to crossbeam_channel.select can break crossbeam_channel.flavors.at, while a change to crossbeam_channel.flavors.at can't break crossbeam_channel.select.
- Position
- Below the diagonal: crossbeam_channel.flavors.at uses a module listed above it, which is the healthy direction.
24→22 crossbeam_channel.flavors.at uses crossbeam_channel.context✕
- Connections
- 1 pair of types, where a type in crossbeam_channel.flavors.at uses a type in crossbeam_channel.context.
- The types involved
crossbeam_channel.flavors.at.Channel→crossbeam_channel.context.Context
- Direction
- crossbeam_channel.flavors.at uses crossbeam_channel.context, so a change to crossbeam_channel.context can break crossbeam_channel.flavors.at, while a change to crossbeam_channel.flavors.at can't break crossbeam_channel.context.
- Position
- Below the diagonal: crossbeam_channel.flavors.at uses a module listed above it, which is the healthy direction.
25→21 crossbeam_channel.flavors.never uses crossbeam_channel.select✕
- Connections
- 3 pairs of types, where a type in crossbeam_channel.flavors.never uses a type in crossbeam_channel.select.
- The types involved
crossbeam_channel.flavors.never.Channel→crossbeam_channel.select.Operationcrossbeam_channel.flavors.never.Channel→crossbeam_channel.select.SelectHandlecrossbeam_channel.flavors.never.Channel→crossbeam_channel.select.Token
- Direction
- crossbeam_channel.flavors.never uses crossbeam_channel.select, so a change to crossbeam_channel.select can break crossbeam_channel.flavors.never, while a change to crossbeam_channel.flavors.never can't break crossbeam_channel.select.
- Position
- Below the diagonal: crossbeam_channel.flavors.never uses a module listed above it, which is the healthy direction.
25→22 crossbeam_channel.flavors.never uses crossbeam_channel.context✕
- Connections
- 1 pair of types, where a type in crossbeam_channel.flavors.never uses a type in crossbeam_channel.context.
- The types involved
crossbeam_channel.flavors.never.Channel→crossbeam_channel.context.Context
- Direction
- crossbeam_channel.flavors.never uses crossbeam_channel.context, so a change to crossbeam_channel.context can break crossbeam_channel.flavors.never, while a change to crossbeam_channel.flavors.never can't break crossbeam_channel.context.
- Position
- Below the diagonal: crossbeam_channel.flavors.never uses a module listed above it, which is the healthy direction.
26→13 crossbeam_channel.flavors.tick uses crossbeam_utils.atomic.atomic_cell✕
- Connections
- 1 pair of types, where a type in crossbeam_channel.flavors.tick uses a type in crossbeam_utils.atomic.atomic_cell.
- The types involved
crossbeam_channel.flavors.tick.Channel→crossbeam_utils.atomic.atomic_cell.AtomicCell
- Direction
- crossbeam_channel.flavors.tick uses crossbeam_utils.atomic.atomic_cell, so a change to crossbeam_utils.atomic.atomic_cell can break crossbeam_channel.flavors.tick, while a change to crossbeam_channel.flavors.tick can't break crossbeam_utils.atomic.atomic_cell.
- Position
- Below the diagonal: crossbeam_channel.flavors.tick uses a module listed above it, which is the healthy direction.
26→21 crossbeam_channel.flavors.tick uses crossbeam_channel.select✕
- Connections
- 3 pairs of types, where a type in crossbeam_channel.flavors.tick uses a type in crossbeam_channel.select.
- The types involved
crossbeam_channel.flavors.tick.Channel→crossbeam_channel.select.Operationcrossbeam_channel.flavors.tick.Channel→crossbeam_channel.select.SelectHandlecrossbeam_channel.flavors.tick.Channel→crossbeam_channel.select.Token
- Direction
- crossbeam_channel.flavors.tick uses crossbeam_channel.select, so a change to crossbeam_channel.select can break crossbeam_channel.flavors.tick, while a change to crossbeam_channel.flavors.tick can't break crossbeam_channel.select.
- Position
- Below the diagonal: crossbeam_channel.flavors.tick uses a module listed above it, which is the healthy direction.
26→22 crossbeam_channel.flavors.tick uses crossbeam_channel.context✕
- Connections
- 1 pair of types, where a type in crossbeam_channel.flavors.tick uses a type in crossbeam_channel.context.
- The types involved
crossbeam_channel.flavors.tick.Channel→crossbeam_channel.context.Context
- Direction
- crossbeam_channel.flavors.tick uses crossbeam_channel.context, so a change to crossbeam_channel.context can break crossbeam_channel.flavors.tick, while a change to crossbeam_channel.flavors.tick can't break crossbeam_channel.context.
- Position
- Below the diagonal: crossbeam_channel.flavors.tick uses a module listed above it, which is the healthy direction.
27→3 crossbeam_utils.sync.parker uses crossbeam_channel.utils✕
- Connections
- 1 pair of types, where a type in crossbeam_utils.sync.parker uses a type in crossbeam_channel.utils.
- The types involved
crossbeam_utils.sync.parker.Inner→crossbeam_channel.utils.Mutex
- Direction
- crossbeam_utils.sync.parker uses crossbeam_channel.utils, so a change to crossbeam_channel.utils can break crossbeam_utils.sync.parker, while a change to crossbeam_utils.sync.parker can't break crossbeam_channel.utils.
- Position
- Below the diagonal: crossbeam_utils.sync.parker uses a module listed above it, which is the healthy direction.
27→22 crossbeam_utils.sync.parker uses crossbeam_channel.context✕
- Connections
- 1 pair of types, where a type in crossbeam_utils.sync.parker uses a type in crossbeam_channel.context.
- The types involved
crossbeam_utils.sync.parker.Unparker→crossbeam_channel.context.Inner
- Direction
- crossbeam_utils.sync.parker uses crossbeam_channel.context, so a change to crossbeam_channel.context can break crossbeam_utils.sync.parker, while a change to crossbeam_utils.sync.parker can't break crossbeam_channel.context.
- Position
- Below the diagonal: crossbeam_utils.sync.parker uses a module listed above it, which is the healthy direction.
28→3 crossbeam_utils.sync.wait_group uses crossbeam_channel.utils✕
- Connections
- 1 pair of types, where a type in crossbeam_utils.sync.wait_group uses a type in crossbeam_channel.utils.
- The types involved
crossbeam_utils.sync.wait_group.Inner→crossbeam_channel.utils.Mutex
- Direction
- crossbeam_utils.sync.wait_group uses crossbeam_channel.utils, so a change to crossbeam_channel.utils can break crossbeam_utils.sync.wait_group, while a change to crossbeam_utils.sync.wait_group can't break crossbeam_channel.utils.
- Position
- Below the diagonal: crossbeam_utils.sync.wait_group uses a module listed above it, which is the healthy direction.
28→22 crossbeam_utils.sync.wait_group uses crossbeam_channel.context✕
- Connections
- 1 pair of types, where a type in crossbeam_utils.sync.wait_group uses a type in crossbeam_channel.context.
- The types involved
crossbeam_utils.sync.wait_group.WaitGroup→crossbeam_channel.context.Inner
- Direction
- crossbeam_utils.sync.wait_group uses crossbeam_channel.context, so a change to crossbeam_channel.context can break crossbeam_utils.sync.wait_group, while a change to crossbeam_utils.sync.wait_group can't break crossbeam_channel.context.
- Position
- Below the diagonal: crossbeam_utils.sync.wait_group uses a module listed above it, which is the healthy direction.
29→23 crossbeam_epoch.sync.list uses crossbeam_channel.channel✕
- Connections
- 1 pair of types, where a type in crossbeam_epoch.sync.list uses a type in crossbeam_channel.channel.
- The types involved
crossbeam_epoch.sync.list.List→crossbeam_channel.channel.Iter
- Direction
- crossbeam_epoch.sync.list uses crossbeam_channel.channel, so a change to crossbeam_channel.channel can break crossbeam_epoch.sync.list, while a change to crossbeam_epoch.sync.list can't break crossbeam_channel.channel.
- Position
- Below the diagonal: crossbeam_epoch.sync.list uses a module listed above it, which is the healthy direction.
29→35 crossbeam_epoch.sync.list uses crossbeam_epoch.guard part of a loop✕
- Connections
- 4 pairs of types, where a type in crossbeam_epoch.sync.list uses a type in crossbeam_epoch.guard.
- The types involved
crossbeam_epoch.sync.list.Entry→crossbeam_epoch.guard.Guardcrossbeam_epoch.sync.list.IsElement→crossbeam_epoch.guard.Guardcrossbeam_epoch.sync.list.Iter→crossbeam_epoch.guard.Guardcrossbeam_epoch.sync.list.List→crossbeam_epoch.guard.Guard
- Direction
- crossbeam_epoch.sync.list uses crossbeam_epoch.guard, so a change to crossbeam_epoch.guard can break crossbeam_epoch.sync.list, while a change to crossbeam_epoch.sync.list can't break crossbeam_epoch.guard.
- 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.
29→36 crossbeam_epoch.sync.list uses crossbeam_epoch.atomic part of a loop✕
- Connections
- 5 pairs of types, where a type in crossbeam_epoch.sync.list uses a type in crossbeam_epoch.atomic.
- The types involved
crossbeam_epoch.sync.list.Entry→crossbeam_epoch.atomic.Atomiccrossbeam_epoch.sync.list.Iter→crossbeam_epoch.atomic.Atomiccrossbeam_epoch.sync.list.Iter→crossbeam_epoch.atomic.Sharedcrossbeam_epoch.sync.list.List→crossbeam_epoch.atomic.Atomiccrossbeam_epoch.sync.list.List→crossbeam_epoch.atomic.Shared
- Direction
- crossbeam_epoch.sync.list uses crossbeam_epoch.atomic, so a change to crossbeam_epoch.atomic can break crossbeam_epoch.sync.list, while a change to crossbeam_epoch.sync.list can't break crossbeam_epoch.atomic.
- 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.
30→6 crossbeam_queue.array_queue uses crossbeam_epoch.primitive.cell✕
- Connections
- 1 pair of types, where a type in crossbeam_queue.array_queue uses a type in crossbeam_epoch.primitive.cell.
- The types involved
crossbeam_queue.array_queue.Slot→crossbeam_epoch.primitive.cell.UnsafeCell
- Direction
- crossbeam_queue.array_queue uses crossbeam_epoch.primitive.cell, so a change to crossbeam_epoch.primitive.cell can break crossbeam_queue.array_queue, while a change to crossbeam_queue.array_queue can't break crossbeam_epoch.primitive.cell.
- Position
- Below the diagonal: crossbeam_queue.array_queue uses a module listed above it, which is the healthy direction.
30→9 crossbeam_queue.array_queue uses crossbeam_utils.cache_padded✕
- Connections
- 1 pair of types, where a type in crossbeam_queue.array_queue uses a type in crossbeam_utils.cache_padded.
- The types involved
crossbeam_queue.array_queue.ArrayQueue→crossbeam_utils.cache_padded.CachePadded
- Direction
- crossbeam_queue.array_queue uses crossbeam_utils.cache_padded, so a change to crossbeam_utils.cache_padded can break crossbeam_queue.array_queue, while a change to crossbeam_queue.array_queue can't break crossbeam_utils.cache_padded.
- Position
- Below the diagonal: crossbeam_queue.array_queue uses a module listed above it, which is the healthy direction.
30→23 crossbeam_queue.array_queue uses crossbeam_channel.channel✕
- Connections
- 1 pair of types, where a type in crossbeam_queue.array_queue uses a type in crossbeam_channel.channel.
- The types involved
crossbeam_queue.array_queue.ArrayQueue→crossbeam_channel.channel.IntoIter
- Direction
- crossbeam_queue.array_queue uses crossbeam_channel.channel, so a change to crossbeam_channel.channel can break crossbeam_queue.array_queue, while a change to crossbeam_queue.array_queue can't break crossbeam_channel.channel.
- Position
- Below the diagonal: crossbeam_queue.array_queue uses a module listed above it, which is the healthy direction.
31→6 crossbeam_queue.seg_queue uses crossbeam_epoch.primitive.cell✕
- Connections
- 1 pair of types, where a type in crossbeam_queue.seg_queue uses a type in crossbeam_epoch.primitive.cell.
- The types involved
crossbeam_queue.seg_queue.Slot→crossbeam_epoch.primitive.cell.UnsafeCell
- Direction
- crossbeam_queue.seg_queue uses crossbeam_epoch.primitive.cell, so a change to crossbeam_epoch.primitive.cell can break crossbeam_queue.seg_queue, while a change to crossbeam_queue.seg_queue can't break crossbeam_epoch.primitive.cell.
- Position
- Below the diagonal: crossbeam_queue.seg_queue uses a module listed above it, which is the healthy direction.
31→9 crossbeam_queue.seg_queue uses crossbeam_utils.cache_padded✕
- Connections
- 1 pair of types, where a type in crossbeam_queue.seg_queue uses a type in crossbeam_utils.cache_padded.
- The types involved
crossbeam_queue.seg_queue.SegQueue→crossbeam_utils.cache_padded.CachePadded
- Direction
- crossbeam_queue.seg_queue uses crossbeam_utils.cache_padded, so a change to crossbeam_utils.cache_padded can break crossbeam_queue.seg_queue, while a change to crossbeam_queue.seg_queue can't break crossbeam_utils.cache_padded.
- Position
- Below the diagonal: crossbeam_queue.seg_queue uses a module listed above it, which is the healthy direction.
31→23 crossbeam_queue.seg_queue uses crossbeam_channel.channel✕
- Connections
- 1 pair of types, where a type in crossbeam_queue.seg_queue uses a type in crossbeam_channel.channel.
- The types involved
crossbeam_queue.seg_queue.SegQueue→crossbeam_channel.channel.IntoIter
- Direction
- crossbeam_queue.seg_queue uses crossbeam_channel.channel, so a change to crossbeam_channel.channel can break crossbeam_queue.seg_queue, while a change to crossbeam_queue.seg_queue can't break crossbeam_channel.channel.
- Position
- Below the diagonal: crossbeam_queue.seg_queue uses a module listed above it, which is the healthy direction.
32→7 crossbeam_utils.thread uses crossbeam_epoch.sealed✕
- Connections
- 1 pair of types, where a type in crossbeam_utils.thread uses a type in crossbeam_epoch.sealed.
- The types involved
crossbeam_utils.thread.ScopedJoinHandle→crossbeam_epoch.sealed.Sealed
- Direction
- crossbeam_utils.thread uses crossbeam_epoch.sealed, so a change to crossbeam_epoch.sealed can break crossbeam_utils.thread, while a change to crossbeam_utils.thread can't break crossbeam_epoch.sealed.
- Position
- Below the diagonal: crossbeam_utils.thread uses a module listed above it, which is the healthy direction.
32→17 crossbeam_utils.thread uses crossbeam_utils.thread.unix✕
- Connections
- 1 pair of types, where a type in crossbeam_utils.thread uses a type in crossbeam_utils.thread.unix.
- The types involved
crossbeam_utils.thread.ScopedJoinHandle→crossbeam_utils.thread.unix.JoinHandleExt
- Direction
- crossbeam_utils.thread uses crossbeam_utils.thread.unix, so a change to crossbeam_utils.thread.unix can break crossbeam_utils.thread, while a change to crossbeam_utils.thread can't break crossbeam_utils.thread.unix.
- Position
- Below the diagonal: crossbeam_utils.thread uses a module listed above it, which is the healthy direction.
32→28 crossbeam_utils.thread uses crossbeam_utils.sync.wait_group✕
- Connections
- 1 pair of types, where a type in crossbeam_utils.thread uses a type in crossbeam_utils.sync.wait_group.
- The types involved
crossbeam_utils.thread.Scope→crossbeam_utils.sync.wait_group.WaitGroup
- Direction
- crossbeam_utils.thread uses crossbeam_utils.sync.wait_group, so a change to crossbeam_utils.sync.wait_group can break crossbeam_utils.thread, while a change to crossbeam_utils.thread can't break crossbeam_utils.sync.wait_group.
- Position
- Below the diagonal: crossbeam_utils.thread uses a module listed above it, which is the healthy direction.
33→4 crossbeam_epoch.internal uses crossbeam_epoch.deferred✕
- Connections
- 2 pairs of types, where a type in crossbeam_epoch.internal uses a type in crossbeam_epoch.deferred.
- The types involved
crossbeam_epoch.internal.Bag→crossbeam_epoch.deferred.Deferredcrossbeam_epoch.internal.Local→crossbeam_epoch.deferred.Deferred
- Direction
- crossbeam_epoch.internal uses crossbeam_epoch.deferred, so a change to crossbeam_epoch.deferred can break crossbeam_epoch.internal, while a change to crossbeam_epoch.internal can't break crossbeam_epoch.deferred.
- Position
- Below the diagonal: crossbeam_epoch.internal uses a module listed above it, which is the healthy direction.
33→5 crossbeam_epoch.internal uses crossbeam_epoch.epoch✕
- Connections
- 3 pairs of types, where a type in crossbeam_epoch.internal uses a type in crossbeam_epoch.epoch.
- The types involved
crossbeam_epoch.internal.Bag→crossbeam_epoch.epoch.Epochcrossbeam_epoch.internal.Global→crossbeam_epoch.epoch.Epochcrossbeam_epoch.internal.SealedBag→crossbeam_epoch.epoch.Epoch
- Direction
- crossbeam_epoch.internal uses crossbeam_epoch.epoch, so a change to crossbeam_epoch.epoch can break crossbeam_epoch.internal, while a change to crossbeam_epoch.internal can't break crossbeam_epoch.epoch.
- Position
- Below the diagonal: crossbeam_epoch.internal uses a module listed above it, which is the healthy direction.
33→6 crossbeam_epoch.internal uses crossbeam_epoch.primitive.cell✕
- Connections
- 1 pair of types, where a type in crossbeam_epoch.internal uses a type in crossbeam_epoch.primitive.cell.
- The types involved
crossbeam_epoch.internal.Local→crossbeam_epoch.primitive.cell.UnsafeCell
- Direction
- crossbeam_epoch.internal uses crossbeam_epoch.primitive.cell, so a change to crossbeam_epoch.primitive.cell can break crossbeam_epoch.internal, while a change to crossbeam_epoch.internal can't break crossbeam_epoch.primitive.cell.
- Position
- Below the diagonal: crossbeam_epoch.internal uses a module listed above it, which is the healthy direction.
33→9 crossbeam_epoch.internal uses crossbeam_utils.cache_padded✕
- Connections
- 2 pairs of types, where a type in crossbeam_epoch.internal uses a type in crossbeam_utils.cache_padded.
- The types involved
crossbeam_epoch.internal.Global→crossbeam_utils.cache_padded.CachePaddedcrossbeam_epoch.internal.Local→crossbeam_utils.cache_padded.CachePadded
- Direction
- crossbeam_epoch.internal uses crossbeam_utils.cache_padded, so a change to crossbeam_utils.cache_padded can break crossbeam_epoch.internal, while a change to crossbeam_epoch.internal can't break crossbeam_utils.cache_padded.
- Position
- Below the diagonal: crossbeam_epoch.internal uses a module listed above it, which is the healthy direction.
33→10 crossbeam_epoch.internal uses crossbeam_channel.waker✕
- Connections
- 1 pair of types, where a type in crossbeam_epoch.internal uses a type in crossbeam_channel.waker.
- The types involved
crossbeam_epoch.internal.Local→crossbeam_channel.waker.Entry
- Direction
- crossbeam_epoch.internal uses crossbeam_channel.waker, so a change to crossbeam_channel.waker can break crossbeam_epoch.internal, while a change to crossbeam_epoch.internal can't break crossbeam_channel.waker.
- Position
- Below the diagonal: crossbeam_epoch.internal uses a module listed above it, which is the healthy direction.
33→12 crossbeam_epoch.internal uses crossbeam_epoch.sync.queue✕
- Connections
- 1 pair of types, where a type in crossbeam_epoch.internal uses a type in crossbeam_epoch.sync.queue.
- The types involved
crossbeam_epoch.internal.Global→crossbeam_epoch.sync.queue.Queue
- Direction
- crossbeam_epoch.internal uses crossbeam_epoch.sync.queue, so a change to crossbeam_epoch.sync.queue can break crossbeam_epoch.internal, while a change to crossbeam_epoch.internal can't break crossbeam_epoch.sync.queue.
- Position
- Below the diagonal: crossbeam_epoch.internal uses a module listed above it, which is the healthy direction.
33→29 crossbeam_epoch.internal uses crossbeam_epoch.sync.list✕
- Connections
- 2 pairs of types, where a type in crossbeam_epoch.internal uses a type in crossbeam_epoch.sync.list.
- The types involved
crossbeam_epoch.internal.Global→crossbeam_epoch.sync.list.Listcrossbeam_epoch.internal.Local→crossbeam_epoch.sync.list.IsElement
- Direction
- crossbeam_epoch.internal uses crossbeam_epoch.sync.list, so a change to crossbeam_epoch.sync.list can break crossbeam_epoch.internal, while a change to crossbeam_epoch.internal can't break crossbeam_epoch.sync.list.
- Position
- Below the diagonal: crossbeam_epoch.internal uses a module listed above it, which is the healthy direction.
33→34 crossbeam_epoch.internal uses crossbeam_epoch.collector part of a loop✕
- Connections
- 2 pairs of types, where a type in crossbeam_epoch.internal uses a type in crossbeam_epoch.collector.
- The types involved
crossbeam_epoch.internal.Local→crossbeam_epoch.collector.Collectorcrossbeam_epoch.internal.Local→crossbeam_epoch.collector.LocalHandle
- Direction
- crossbeam_epoch.internal uses crossbeam_epoch.collector, so a change to crossbeam_epoch.collector can break crossbeam_epoch.internal, while a change to crossbeam_epoch.internal can't break crossbeam_epoch.collector.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
33→35 crossbeam_epoch.internal uses crossbeam_epoch.guard part of a loop✕
- Connections
- 2 pairs of types, where a type in crossbeam_epoch.internal uses a type in crossbeam_epoch.guard.
- The types involved
crossbeam_epoch.internal.Global→crossbeam_epoch.guard.Guardcrossbeam_epoch.internal.Local→crossbeam_epoch.guard.Guard
- Direction
- crossbeam_epoch.internal uses crossbeam_epoch.guard, so a change to crossbeam_epoch.guard can break crossbeam_epoch.internal, while a change to crossbeam_epoch.internal can't break crossbeam_epoch.guard.
- 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.
34→33 crossbeam_epoch.collector uses crossbeam_epoch.internal✕
- Connections
- 1 pair of types, where a type in crossbeam_epoch.collector uses a type in crossbeam_epoch.internal.
- The types involved
crossbeam_epoch.collector.Collector→crossbeam_epoch.internal.Global
- Direction
- crossbeam_epoch.collector uses crossbeam_epoch.internal, so a change to crossbeam_epoch.internal can break crossbeam_epoch.collector, while a change to crossbeam_epoch.collector can't break crossbeam_epoch.internal.
- Position
- Below the diagonal: crossbeam_epoch.collector uses a module listed above it, which is the healthy direction.
34→35 crossbeam_epoch.collector uses crossbeam_epoch.guard part of a loop✕
- Connections
- 1 pair of types, where a type in crossbeam_epoch.collector uses a type in crossbeam_epoch.guard.
- The types involved
crossbeam_epoch.collector.LocalHandle→crossbeam_epoch.guard.Guard
- Direction
- crossbeam_epoch.collector uses crossbeam_epoch.guard, so a change to crossbeam_epoch.guard can break crossbeam_epoch.collector, while a change to crossbeam_epoch.collector can't break crossbeam_epoch.guard.
- 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.
35→34 crossbeam_epoch.guard uses crossbeam_epoch.collector✕
- Connections
- 1 pair of types, where a type in crossbeam_epoch.guard uses a type in crossbeam_epoch.collector.
- The types involved
crossbeam_epoch.guard.Guard→crossbeam_epoch.collector.Collector
- Direction
- crossbeam_epoch.guard uses crossbeam_epoch.collector, so a change to crossbeam_epoch.collector can break crossbeam_epoch.guard, while a change to crossbeam_epoch.guard can't break crossbeam_epoch.collector.
- Position
- Below the diagonal: crossbeam_epoch.guard uses a module listed above it, which is the healthy direction.
35→36 crossbeam_epoch.guard uses crossbeam_epoch.atomic part of a loop✕
- Connections
- 1 pair of types, where a type in crossbeam_epoch.guard uses a type in crossbeam_epoch.atomic.
- The types involved
crossbeam_epoch.guard.Guard→crossbeam_epoch.atomic.Shared
- Direction
- crossbeam_epoch.guard uses crossbeam_epoch.atomic, so a change to crossbeam_epoch.atomic can break crossbeam_epoch.guard, while a change to crossbeam_epoch.guard can't break crossbeam_epoch.atomic.
- 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.
36→7 crossbeam_epoch.atomic uses crossbeam_epoch.sealed✕
- Connections
- 3 pairs of types, where a type in crossbeam_epoch.atomic uses a type in crossbeam_epoch.sealed.
- The types involved
crossbeam_epoch.atomic.Owned→crossbeam_epoch.sealed.Sealedcrossbeam_epoch.atomic.Pointer→crossbeam_epoch.sealed.Sealedcrossbeam_epoch.atomic.Shared→crossbeam_epoch.sealed.Sealed
- Direction
- crossbeam_epoch.atomic uses crossbeam_epoch.sealed, so a change to crossbeam_epoch.sealed can break crossbeam_epoch.atomic, while a change to crossbeam_epoch.atomic can't break crossbeam_epoch.sealed.
- Position
- Below the diagonal: crossbeam_epoch.atomic uses a module listed above it, which is the healthy direction.
36→35 crossbeam_epoch.atomic uses crossbeam_epoch.guard✕
- Connections
- 2 pairs of types, where a type in crossbeam_epoch.atomic uses a type in crossbeam_epoch.guard.
- The types involved
crossbeam_epoch.atomic.Atomic→crossbeam_epoch.guard.Guardcrossbeam_epoch.atomic.Owned→crossbeam_epoch.guard.Guard
- Direction
- crossbeam_epoch.atomic uses crossbeam_epoch.guard, so a change to crossbeam_epoch.guard can break crossbeam_epoch.atomic, while a change to crossbeam_epoch.atomic can't break crossbeam_epoch.guard.
- Position
- Below the diagonal: crossbeam_epoch.atomic uses a module listed above it, which is the healthy direction.
37→34 crossbeam_epoch.default uses crossbeam_epoch.collector✕
- Connections
- 1 pair of types, where a type in crossbeam_epoch.default uses a type in crossbeam_epoch.collector.
- The types involved
crossbeam_epoch.default.default$module→crossbeam_epoch.collector.Collector
- Direction
- crossbeam_epoch.default uses crossbeam_epoch.collector, so a change to crossbeam_epoch.collector can break crossbeam_epoch.default, while a change to crossbeam_epoch.default can't break crossbeam_epoch.collector.
- Position
- Below the diagonal: crossbeam_epoch.default uses a module listed above it, which is the healthy direction.
37→35 crossbeam_epoch.default uses crossbeam_epoch.guard✕
- Connections
- 1 pair of types, where a type in crossbeam_epoch.default uses a type in crossbeam_epoch.guard.
- The types involved
crossbeam_epoch.default.default$module→crossbeam_epoch.guard.Guard
- Direction
- crossbeam_epoch.default uses crossbeam_epoch.guard, so a change to crossbeam_epoch.guard can break crossbeam_epoch.default, while a change to crossbeam_epoch.default can't break crossbeam_epoch.guard.
- Position
- Below the diagonal: crossbeam_epoch.default uses a module listed above it, which is the healthy direction.
38→9 crossbeam_skiplist.base uses crossbeam_utils.cache_padded✕
- Connections
- 1 pair of types, where a type in crossbeam_skiplist.base uses a type in crossbeam_utils.cache_padded.
- The types involved
crossbeam_skiplist.base.SkipList→crossbeam_utils.cache_padded.CachePadded
- Direction
- crossbeam_skiplist.base uses crossbeam_utils.cache_padded, so a change to crossbeam_utils.cache_padded can break crossbeam_skiplist.base, while a change to crossbeam_skiplist.base can't break crossbeam_utils.cache_padded.
- Position
- Below the diagonal: crossbeam_skiplist.base uses a module listed above it, which is the healthy direction.
38→10 crossbeam_skiplist.base uses crossbeam_channel.waker✕
- Connections
- 1 pair of types, where a type in crossbeam_skiplist.base uses a type in crossbeam_channel.waker.
- The types involved
crossbeam_skiplist.base.SkipList→crossbeam_channel.waker.Entry
- Direction
- crossbeam_skiplist.base uses crossbeam_channel.waker, so a change to crossbeam_channel.waker can break crossbeam_skiplist.base, while a change to crossbeam_skiplist.base can't break crossbeam_channel.waker.
- Position
- Below the diagonal: crossbeam_skiplist.base uses a module listed above it, which is the healthy direction.
38→12 crossbeam_skiplist.base uses crossbeam_epoch.sync.queue✕
- Connections
- 1 pair of types, where a type in crossbeam_skiplist.base uses a type in crossbeam_epoch.sync.queue.
- The types involved
crossbeam_skiplist.base.NodeRef→crossbeam_epoch.sync.queue.Node
- Direction
- crossbeam_skiplist.base uses crossbeam_epoch.sync.queue, so a change to crossbeam_epoch.sync.queue can break crossbeam_skiplist.base, while a change to crossbeam_skiplist.base can't break crossbeam_epoch.sync.queue.
- Position
- Below the diagonal: crossbeam_skiplist.base uses a module listed above it, which is the healthy direction.
38→19 crossbeam_skiplist.base uses crossbeam_channel.flavors.list✕
- Connections
- 1 pair of types, where a type in crossbeam_skiplist.base uses a type in crossbeam_channel.flavors.list.
- The types involved
crossbeam_skiplist.base.SkipList→crossbeam_channel.flavors.list.Position
- Direction
- crossbeam_skiplist.base uses crossbeam_channel.flavors.list, so a change to crossbeam_channel.flavors.list can break crossbeam_skiplist.base, while a change to crossbeam_skiplist.base can't break crossbeam_channel.flavors.list.
- Position
- Below the diagonal: crossbeam_skiplist.base uses a module listed above it, which is the healthy direction.
38→23 crossbeam_skiplist.base uses crossbeam_channel.channel✕
- Connections
- 2 pairs of types, where a type in crossbeam_skiplist.base uses a type in crossbeam_channel.channel.
- The types involved
crossbeam_skiplist.base.SkipList→crossbeam_channel.channel.IntoItercrossbeam_skiplist.base.SkipList→crossbeam_channel.channel.Iter
- Direction
- crossbeam_skiplist.base uses crossbeam_channel.channel, so a change to crossbeam_channel.channel can break crossbeam_skiplist.base, while a change to crossbeam_skiplist.base can't break crossbeam_channel.channel.
- Position
- Below the diagonal: crossbeam_skiplist.base uses a module listed above it, which is the healthy direction.
38→34 crossbeam_skiplist.base uses crossbeam_epoch.collector✕
- Connections
- 1 pair of types, where a type in crossbeam_skiplist.base uses a type in crossbeam_epoch.collector.
- The types involved
crossbeam_skiplist.base.SkipList→crossbeam_epoch.collector.Collector
- Direction
- crossbeam_skiplist.base uses crossbeam_epoch.collector, so a change to crossbeam_epoch.collector can break crossbeam_skiplist.base, while a change to crossbeam_skiplist.base can't break crossbeam_epoch.collector.
- Position
- Below the diagonal: crossbeam_skiplist.base uses a module listed above it, which is the healthy direction.
38→35 crossbeam_skiplist.base uses crossbeam_epoch.guard✕
- Connections
- 8 pairs of types, where a type in crossbeam_skiplist.base uses a type in crossbeam_epoch.guard.
- The types involved
crossbeam_skiplist.base.Entry→crossbeam_epoch.guard.Guardcrossbeam_skiplist.base.Iter→crossbeam_epoch.guard.Guardcrossbeam_skiplist.base.NodeRef→crossbeam_epoch.guard.Guardcrossbeam_skiplist.base.Range→crossbeam_epoch.guard.Guardcrossbeam_skiplist.base.RefEntry→crossbeam_epoch.guard.Guardcrossbeam_skiplist.base.RefIter→crossbeam_epoch.guard.Guardcrossbeam_skiplist.base.RefRange→crossbeam_epoch.guard.Guardcrossbeam_skiplist.base.SkipList→crossbeam_epoch.guard.Guard
- Direction
- crossbeam_skiplist.base uses crossbeam_epoch.guard, so a change to crossbeam_epoch.guard can break crossbeam_skiplist.base, while a change to crossbeam_skiplist.base can't break crossbeam_epoch.guard.
- Position
- Below the diagonal: crossbeam_skiplist.base uses a module listed above it, which is the healthy direction.
38→36 crossbeam_skiplist.base uses crossbeam_epoch.atomic✕
- Connections
- 6 pairs of types, where a type in crossbeam_skiplist.base uses a type in crossbeam_epoch.atomic.
- The types involved
crossbeam_skiplist.base.Head→crossbeam_epoch.atomic.Atomiccrossbeam_skiplist.base.NodeRef→crossbeam_epoch.atomic.Atomiccrossbeam_skiplist.base.NodeRef→crossbeam_epoch.atomic.Sharedcrossbeam_skiplist.base.SkipList→crossbeam_epoch.atomic.Atomiccrossbeam_skiplist.base.SkipList→crossbeam_epoch.atomic.Sharedcrossbeam_skiplist.base.TowerRef→crossbeam_epoch.atomic.Atomic
- Direction
- crossbeam_skiplist.base uses crossbeam_epoch.atomic, so a change to crossbeam_epoch.atomic can break crossbeam_skiplist.base, while a change to crossbeam_skiplist.base can't break crossbeam_epoch.atomic.
- Position
- Below the diagonal: crossbeam_skiplist.base uses a module listed above it, which is the healthy direction.
39→10 crossbeam_skiplist.map uses crossbeam_channel.waker✕
- Connections
- 3 pairs of types, where a type in crossbeam_skiplist.map uses a type in crossbeam_channel.waker.
- The types involved
crossbeam_skiplist.map.Iter→crossbeam_channel.waker.Entrycrossbeam_skiplist.map.Range→crossbeam_channel.waker.Entrycrossbeam_skiplist.map.SkipMap→crossbeam_channel.waker.Entry
- Direction
- crossbeam_skiplist.map uses crossbeam_channel.waker, so a change to crossbeam_channel.waker can break crossbeam_skiplist.map, while a change to crossbeam_skiplist.map can't break crossbeam_channel.waker.
- Position
- Below the diagonal: crossbeam_skiplist.map uses a module listed above it, which is the healthy direction.
39→23 crossbeam_skiplist.map uses crossbeam_channel.channel✕
- Connections
- 3 pairs of types, where a type in crossbeam_skiplist.map uses a type in crossbeam_channel.channel.
- The types involved
crossbeam_skiplist.map.IntoIter→crossbeam_channel.channel.IntoItercrossbeam_skiplist.map.SkipMap→crossbeam_channel.channel.IntoItercrossbeam_skiplist.map.SkipMap→crossbeam_channel.channel.Iter
- Direction
- crossbeam_skiplist.map uses crossbeam_channel.channel, so a change to crossbeam_channel.channel can break crossbeam_skiplist.map, while a change to crossbeam_skiplist.map can't break crossbeam_channel.channel.
- Position
- Below the diagonal: crossbeam_skiplist.map uses a module listed above it, which is the healthy direction.
39→38 crossbeam_skiplist.map uses crossbeam_skiplist.base✕
- Connections
- 5 pairs of types, where a type in crossbeam_skiplist.map uses a type in crossbeam_skiplist.base.
- The types involved
crossbeam_skiplist.map.Entry→crossbeam_skiplist.base.RefEntrycrossbeam_skiplist.map.Iter→crossbeam_skiplist.base.RefItercrossbeam_skiplist.map.Range→crossbeam_skiplist.base.RefRangecrossbeam_skiplist.map.SkipMap→crossbeam_skiplist.base.Rangecrossbeam_skiplist.map.SkipMap→crossbeam_skiplist.base.SkipList
- Direction
- crossbeam_skiplist.map uses crossbeam_skiplist.base, so a change to crossbeam_skiplist.base can break crossbeam_skiplist.map, while a change to crossbeam_skiplist.map can't break crossbeam_skiplist.base.
- Position
- Below the diagonal: crossbeam_skiplist.map uses a module listed above it, which is the healthy direction.
40→10 crossbeam_skiplist.set uses crossbeam_channel.waker✕
- Connections
- 2 pairs of types, where a type in crossbeam_skiplist.set uses a type in crossbeam_channel.waker.
- The types involved
crossbeam_skiplist.set.Entry→crossbeam_channel.waker.Entrycrossbeam_skiplist.set.SkipSet→crossbeam_channel.waker.Entry
- Direction
- crossbeam_skiplist.set uses crossbeam_channel.waker, so a change to crossbeam_channel.waker can break crossbeam_skiplist.set, while a change to crossbeam_skiplist.set can't break crossbeam_channel.waker.
- Position
- Below the diagonal: crossbeam_skiplist.set uses a module listed above it, which is the healthy direction.
40→23 crossbeam_skiplist.set uses crossbeam_channel.channel✕
- Connections
- 4 pairs of types, where a type in crossbeam_skiplist.set uses a type in crossbeam_channel.channel.
- The types involved
crossbeam_skiplist.set.IntoIter→crossbeam_channel.channel.IntoItercrossbeam_skiplist.set.Iter→crossbeam_channel.channel.Itercrossbeam_skiplist.set.SkipSet→crossbeam_channel.channel.IntoItercrossbeam_skiplist.set.SkipSet→crossbeam_channel.channel.Iter
- Direction
- crossbeam_skiplist.set uses crossbeam_channel.channel, so a change to crossbeam_channel.channel can break crossbeam_skiplist.set, while a change to crossbeam_skiplist.set can't break crossbeam_channel.channel.
- Position
- Below the diagonal: crossbeam_skiplist.set uses a module listed above it, which is the healthy direction.
40→38 crossbeam_skiplist.set uses crossbeam_skiplist.base✕
- Connections
- 2 pairs of types, where a type in crossbeam_skiplist.set uses a type in crossbeam_skiplist.base.
- The types involved
crossbeam_skiplist.set.Range→crossbeam_skiplist.base.Rangecrossbeam_skiplist.set.SkipSet→crossbeam_skiplist.base.Range
- Direction
- crossbeam_skiplist.set uses crossbeam_skiplist.base, so a change to crossbeam_skiplist.base can break crossbeam_skiplist.set, while a change to crossbeam_skiplist.set can't break crossbeam_skiplist.base.
- Position
- Below the diagonal: crossbeam_skiplist.set uses a module listed above it, which is the healthy direction.
40→39 crossbeam_skiplist.set uses crossbeam_skiplist.map✕
- Connections
- 1 pair of types, where a type in crossbeam_skiplist.set uses a type in crossbeam_skiplist.map.
- The types involved
crossbeam_skiplist.set.SkipSet→crossbeam_skiplist.map.SkipMap
- Direction
- crossbeam_skiplist.set uses crossbeam_skiplist.map, so a change to crossbeam_skiplist.map can break crossbeam_skiplist.set, while a change to crossbeam_skiplist.set can't break crossbeam_skiplist.map.
- Position
- Below the diagonal: crossbeam_skiplist.set 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 |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 3 | Medium |
Roadmap
Begin by documenting significant design decisions in a dedicated folder to establish clear architectural context. Next, mitigate off-boarding risks by addressing bus factor gaps and resolving orphaned files, prioritizing backoff.rs, seq_lock_wide.rs, and crossbeam-channel.rs. Finally, secure the supply chain by generating a software bill of materials and implementing artifact signing.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 Off-boarding risk finding(s) in Bus Factor. | +5.5 pts | Low | Bus Factor |
| 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. | +11.0 pts | Medium | Architecture documentation |
| Resolve the 14 Orphaned file finding(s) in Knowledge Freshness — start with backoff.rs, seq_lock_wide.rs, crossbeam-channel.rs. | +3.5 pts | Medium | Knowledge Freshness |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +1.3 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +1.3 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +1.3 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 1 Inverted test pyramid finding(s) in Test Distribution. | +0.4 pts | Low | Test Distribution |
| Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. | +0.3 pts | Low | Knowledge Freshness |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| crossbeam-channel/src/select.rs | 6.0 | Mixed | Explicit Debt: FixmeComment |
| crossbeam-deque/src/deque.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| crossbeam-skiplist/src/base.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| crossbeam-channel/src/flavors/list.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| crossbeam-queue/src/seg_queue.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| crossbeam-channel/src/flavors/array.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| crossbeam-utils/src/atomic/atomic_cell.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| crossbeam-channel/src/select_macro.rs | 6.5 | Mixed | Explicit Debt: TodoComment |
| crossbeam-channel/tests/golang.rs | 6.6 | Mixed | Explicit Debt: TodoComment |
| crossbeam-channel/tests/select.rs | 6.6 | Mixed | Explicit Debt: TodoComment |
| crossbeam-channel/src/channel.rs | 6.7 | Mixed | Explicit Debt: HackComment |
| crossbeam-epoch/src/atomic.rs | 6.7 | Mixed | Explicit Debt: FixmeComment |
| crossbeam-queue/src/array_queue.rs | 6.7 | Mixed | Explicit Debt: TodoComment |
| crossbeam-epoch/src/internal.rs | 6.9 | Mixed | Explicit Debt: TodoComment |
| crossbeam-channel/tests/tick.rs | 6.9 | Mixed | Explicit Debt: TodoComment |
| crossbeam-utils/src/lib.rs | 8.2 | Near-clean | Explicit Debt: FixmeComment |
| crossbeam-epoch/src/lib.rs | 8.2 | Near-clean | Explicit Debt: FixmeComment |
| crossbeam-utils/src/atomic/consume.rs | 8.2 | Near-clean | Explicit Debt: TodoComment |
| crossbeam-utils/src/atomic/mod.rs | 8.2 | Near-clean | Explicit Debt: TodoComment |
| crossbeam-epoch/src/epoch.rs | 8.2 | Near-clean | Explicit Debt: TodoComment |
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. 43 of 43 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 — 43 dimensions across the health lenses
- Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 160 of 170 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.
- 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.
- M4 Documentation accuracy — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9). Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- X12 Unreachable branch — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X13 Undrained process stream — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X16 Unfloored truncation loop — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X17 Uncapped recursion over a caller-supplied document — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X18 Disposal-pattern correctness — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X19 Unrestored process-global state — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X22 Contradicted release guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Java, TypeScript/JavaScript, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X23 Unguarded diagnostic materialisation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X24 Document value interpolated into markup unescaped — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X25 Inert configuration knob — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart and Ruby source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart or Ruby was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X3 Exception handling — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go and JavaScript/TypeScript source only, and no C# was loaded and no PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go, JavaScript or TypeScript was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X5 Nullable reference types — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax and MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, and Kotlin source only, and no C# was loaded, no TypeScript was found, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D11 Test Reliability: Flakiness is inferred from history/markers — Watchdog runs the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- 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.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
- 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
7 function(s) exceeded the cyclomatic complexity threshold of 15; the worst was crossbeam_channel::select::run_select at 35.
What to do
- Bring the 7 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with crossbeam_channel::select::run_select (cyclomatic 35), crossbeam_channel::select::run_ready (cyclomatic 29), Stealer::steal_batch_with_limit (cyclomatic 20). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 7 together lifts Cyclomatic Complexity from 8.6 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
22 function(s) exceeded the cognitive complexity threshold of 15; the worst was crossbeam_channel::select::run_select at 73.
What to do
- Bring the 1 body over 60 down to 60 or less in Cognitive Complexity — start with crossbeam_channel::select::run_select (cognitive 73). — Refactoring it lifts Cognitive Complexity from 6.5 to about 6.8/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
4 god class(es) detected.
What to do
- Resolve the 2 FileTooLong finding(s) in God Classes — start with base.rs, deque.rs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 TooManyMethods finding(s) in God Classes — start with atomic_cell.rs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 ClassTooLong finding(s) in God Classes — start with base.rs. — One of this dimension's main actionable groups (1 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
53 duplicated block group(s) detected. A further 4 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.
What to do
- Resolve the 6 Duplicated block (12 lines × 2) finding(s) in Code Duplication — start with atomic_cell.rs (4), list.rs, atomic.rs. — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 4 Duplicated block (14 lines × 2) finding(s) in Code Duplication — start with base.rs (2), array.rs, deque.rs. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 3 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with list.rs, deque.rs, array.rs. — One of this dimension's main actionable groups (3 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
7 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, with abstractness counted on 6 of the 7 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What to do
- Resolve the 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 68 classes have LCOM4 above 3.
D9 · Test Distribution
653 test methods: 47 unit, 606 integration, 0 BDD, 0 e2e. The Rust suite contributes 653 `#[test]` function(s) across 41 file(s) declaring at least one; its unit/integration split is Cargo's own — 31 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.
What to do
- Resolve the 1 Inverted test pyramid finding(s) in Test Distribution. — One of this dimension's main actionable groups (1 recommendation-level).
D11 · Test Reliability
0 flaky across 1 measured tier(s). Rust (repository root, 41 test files): measured (0 flaky).
D12 · Dependency Hygiene
0 outdated, 0 yanked direct Cargo dependencies. 8 of 9 direct crates were graded against crates.io (0 not published there, 1 not resolved by a committed Cargo.lock). 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.
What to do
- Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 77 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. A further 1 crate(s) in the closure resolve from git, a path or a private registry and publish no licence this pass can read; they are outside this verdict. This repository publishes itself under MIT OR Apache-2.0, which is its own choice and is not judged here.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D16 · Bus Factor
20 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is crossbeam-utils/src/atomic/atomic_cell.rs. Counted over 56 of the 73 production source files in this repository: 16 are under the ~2,400-byte size floor this dimension measures over, and the remaining 1 have no attributable history left to measure.
What to do
- Resolve the 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
D17 · Explicit Debt
53 deducted task-comment markers across 25037 LoC (0.2/KLoC) → score 9.6. 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 43 TodoComment finding(s) in Explicit Debt — start with base.rs (9), select_macro.rs (7), golang.rs (4). — One of this dimension's main actionable groups (43 warning-level).
- Resolve the 5 FixmeComment finding(s) in Explicit Debt — start with lib.rs (2), atomic.rs, default.rs. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 5 HackComment finding(s) in Explicit Debt — start with base.rs (2), atomic_cell.rs, channel.rs. — One of this dimension's main actionable groups (5 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 8 document(s) read across 1 unit(s).
D26 · Project Cohesion
0 of 7 build units (Cargo) flagged as possibly oversized/incoherent.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
semgrep found no security issues. semgrep hit a parse error in 1 file(s) — `tools/publish.sh` (line 12) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
D34 · Knowledge Freshness
14 of 57 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is crossbeam-utils/src/backoff.rs. Counted over 57 of the 73 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 14 Orphaned file finding(s) in Knowledge Freshness — start with backoff.rs, seq_lock_wide.rs, crossbeam-channel.rs. — One of this dimension's main actionable groups (14 recommendation-level).
- Resolve the 1 Orphaned files with no living knowledge 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
1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
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.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
- A CI pipeline exists but no build step was matched — changes may merge without the build ever running. A build step may be invoked directly as a command, or declared as a task that a runner named in the pipeline resolves.
What to do
- Add an explicit build step to your CI pipeline — your stack's own build command, or, if the pipeline delegates to a task runner, a build task that runner executes in CI — so every change is built before merge.
P10 · Library API & versioning
P3 · Security & performance tooling
What to do
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene
PF1 · Benchmark discipline
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
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 92% | Exemplary | Solid. |
| Architecture | 99% | Exemplary | Strongest area. |
| Maturity | 61% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 87% | Exemplary | Solid. |
| Security | 81% | Adequate — gated by D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 85% | Exemplary | Solid. |
Unscored — 1 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 3 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 2 control(s) we could not find positive evidence for
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 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 — No container singleton was found, so there is no shared instance for concurrent requests to race on. No Go request handler (a net/http, Gin, Echo, Fiber or fasthttp handler, or a gRPC service method) is declared as a method or function, and no handler function literal writes a value captured from outside it, so no state is shared between request goroutines. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. 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 — ~16287 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; Go, Python, 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 .go, .py, .rs, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.rs), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- 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).
- 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 — applicable but not scored (1 of 2 signals for this style — below the bar we score at): 13 value object(s)
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P2 Observability — This repository's Rust source (7 module(s), 59 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
- 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
- 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.
- PF3 Async & latency hygiene — Not applicable: Go has no async/await function colour, so there is no asynchronous code for a blocking call to stall.
- S1 Web-Security Posture — No web surface: 59 Rust file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation and obsolete TLS versions, and none was found. This repository serves no HTTP of its own — no HTTP-server crate (actix-web, axum, Rocket, warp, poem, tide, salvo, tonic, a hyper server, …) among its Cargo manifests' run-time dependencies, and no server started in its production source — so HTTPS enforcement, HSTS, cookie flags and input validation are N/A here, as they are for a C# library or worker. If this codebase starts serving HTTP, the dimension reactivates automatically.
- X12 Unreachable branch — 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.
- X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Rust was read, and it logs through none: the `log` crate's macros take one finished message (as log4net does in C#; its `kv` values are an opt-in its backends mostly drop), `println!`/`eprintln!` are not loggers, or it makes no log call outside its tests and examples at all. Calls through `tracing` (`tracing::info!`, or `info!` imported from it) would be judged.
- X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Serious — 144 finding(s)
- TodoComment crossbeam-utils/src/atomic/atomic_cell.rs:704
- TodoComment crossbeam-utils/src/atomic/consume.rs:1
- TodoComment crossbeam-utils/src/atomic/mod.rs:24
- TodoComment crossbeam-skiplist/src/base.rs:334
- TodoComment crossbeam-skiplist/src/base.rs:1075
- TodoComment crossbeam-skiplist/src/base.rs:1182
- TodoComment crossbeam-skiplist/src/base.rs:1196
- TodoComment crossbeam-skiplist/src/base.rs:1309
- TodoComment crossbeam-skiplist/src/base.rs:456
- TodoComment crossbeam-skiplist/src/base.rs:1143
- TodoComment crossbeam-skiplist/src/base.rs:1226
- TodoComment crossbeam-skiplist/src/base.rs:1305
- TodoComment crossbeam-queue/src/array_queue.rs:19
- TodoComment crossbeam-queue/src/seg_queue.rs:19
- TodoComment crossbeam-epoch/src/epoch.rs:14
- TodoComment crossbeam-channel/src/flavors/array.rs:31
- TodoComment crossbeam-channel/src/flavors/list.rs:26
- TodoComment crossbeam-epoch/src/collector.rs:216
- TodoComment crossbeam-epoch/src/internal.rs:251
- TodoComment crossbeam-epoch/src/internal.rs:330
- TodoComment crossbeam-deque/src/deque.rs:19
- TodoComment crossbeam-deque/src/deque.rs:1791
- TodoComment crossbeam-channel/tests/after.rs:3
- TodoComment crossbeam-channel/tests/tick.rs:3
- TodoComment crossbeam-channel/tests/golang.rs:771
- Channel::start_recv (cognitive 27) crossbeam-channel/src/flavors/list.rs:334
- Channel::start_recv (cognitive 20) crossbeam-channel/src/flavors/array.rs:251
- Channel::send (cognitive 20) crossbeam-channel/src/flavors/array.rs:352
- Channel::recv (cognitive 20) crossbeam-channel/src/flavors/array.rs:416
- Channel::recv (cognitive 20) crossbeam-channel/src/flavors/list.rs:479
- Channel::start_send (cognitive 19) crossbeam-channel/src/flavors/list.rs:232
- Channel::start_send (cognitive 17) crossbeam-channel/src/flavors/array.rs:161
- Duplicated block (12 lines × 2) crossbeam-channel/src/flavors/list.rs:301
- Duplicated block (12 lines × 2) crossbeam-epoch/src/atomic.rs:475
- Duplicated block (12 lines × 2) crossbeam-utils/src/atomic/atomic_cell.rs:450
- Duplicated block (12 lines × 2) crossbeam-utils/src/atomic/atomic_cell.rs:487
- Duplicated block (12 lines × 2) crossbeam-utils/src/atomic/atomic_cell.rs:524
- Duplicated block (12 lines × 2) crossbeam-utils/src/atomic/atomic_cell.rs:561
- FixmeComment crossbeam-utils/src/lib.rs:60
- FixmeComment crossbeam-epoch/src/lib.rs:81
- FixmeComment crossbeam-epoch/src/atomic.rs:87
- FixmeComment crossbeam-epoch/src/default.rs:23
- FixmeComment crossbeam-channel/src/select.rs:1206
- HackComment crossbeam-utils/src/atomic/atomic_cell.rs:1135
- HackComment crossbeam-channel/src/channel.rs:1574
- HackComment crossbeam-skiplist/src/base.rs:1029
- HackComment crossbeam-skiplist/src/base.rs:1279
- HackComment crossbeam-epoch/src/internal.rs:425
- Duplicated block (14 lines × 2) crossbeam-channel/src/flavors/array.rs:451
- Duplicated block (14 lines × 2) crossbeam-deque/src/deque.rs:1687
- Duplicated block (14 lines × 2) crossbeam-skiplist/src/base.rs:2163
- Duplicated block (14 lines × 2) crossbeam-skiplist/src/base.rs:2211
- SkipList::insert_internal (cognitive 41) crossbeam-skiplist/src/base.rs:1013
- SkipList::search_bound (cognitive 32) crossbeam-skiplist/src/base.rs:833
- SkipList::search_position (cognitive 26) crossbeam-skiplist/src/base.rs:923
- Duplicated block (9 lines × 2) crossbeam-channel/src/flavors/list.rs:207
- Duplicated block (9 lines × 2) crossbeam-deque/src/deque.rs:802
- Duplicated block (9 lines × 2) crossbeam-channel/src/flavors/array.rs:405
- crossbeam_channel::select::run_select (cyclomatic 35) crossbeam-channel/src/select.rs:176
- crossbeam_channel::select::run_ready (cyclomatic 29) crossbeam-channel/src/select.rs:327
- Stealer::steal_batch_with_limit (cyclomatic 20) crossbeam-deque/src/deque.rs:767
- Stealer::steal_batch_with_limit_and_pop (cyclomatic 19) crossbeam-deque/src/deque.rs:1010
- Injector::steal_batch_with_limit (cyclomatic 16) crossbeam-deque/src/deque.rs:1622
- Injector::steal_batch_with_limit_and_pop (cyclomatic 16) crossbeam-deque/src/deque.rs:1829
- crossbeam_channel::select::run_select (cognitive 73) crossbeam-channel/src/select.rs:176
- crossbeam_channel::select::run_ready (cognitive 58) crossbeam-channel/src/select.rs:327
- Stealer::steal_batch_with_limit (cognitive 40) crossbeam-deque/src/deque.rs:767
- Stealer::steal_batch_with_limit_and_pop (cognitive 35) crossbeam-deque/src/deque.rs:1010
- Injector::steal_batch_with_limit (cognitive 29) crossbeam-deque/src/deque.rs:1622
- Injector::steal_batch_with_limit_and_pop (cognitive 29) crossbeam-deque/src/deque.rs:1829
- SegQueue::pop (cognitive 26) crossbeam-queue/src/seg_queue.rs:377
- SegQueue::push (cognitive 17) crossbeam-queue/src/seg_queue.rs:227
- RefRange::next (cognitive 21) crossbeam-skiplist/src/base.rs:2152
- RefRange::next_back (cognitive 21) crossbeam-skiplist/src/base.rs:2200
- FileTooLong: src/base.rs crossbeam-skiplist/src/base.rs
- FileTooLong: src/deque.rs crossbeam-deque/src/deque.rs
- Duplicated block (19 lines × 2) crossbeam-channel/src/select.rs:181
- Duplicated block (19 lines × 2) crossbeam-deque/src/deque.rs:1436
- Duplicated block (15 lines × 2) crossbeam-channel/src/channel.rs:1592
- Duplicated block (15 lines × 2) crossbeam-epoch/src/sync/queue.rs:126
- Duplicated block (13 lines × 3) crossbeam-channel/src/flavors/list.rs:246
- Duplicated block (13 lines × 3) crossbeam-channel/src/flavors/list.rs:283
- Duplicated block (6 lines × 2) crossbeam-utils/src/sync/sharded_lock.rs:363
- Duplicated block (6 lines × 2) crossbeam-skiplist/src/base.rs:1562
- SkipList::insert_internal (cyclomatic 18) crossbeam-skiplist/src/base.rs:1013
- Worker::pop (cognitive 23) crossbeam-deque/src/deque.rs:471
- Inner::park (cognitive 18) crossbeam-utils/src/sync/parker.rs:340
- TooManyMethods: AtomicCell crossbeam-utils/src/atomic/atomic_cell.rs:33
- ClassTooLong: SkipList crossbeam-skiplist/src/base.rs:468
- Near-duplicate member family (3 members, 40 shared lines) crossbeam-deque/src/deque.rs:1485
- Near-duplicate member pair (79 shared lines) crossbeam-deque/src/deque.rs:767
- Members sharing a duplicated core (5 members, 50+ identical tokens) crossbeam-channel/src/flavors/list.rs:232
- Members sharing a duplicated core (4 members, 50+ identical tokens) crossbeam-channel/src/flavors/array.rs:161
- Duplicated block (60–61 lines × 2) crossbeam-deque/src/deque.rs:1623
- Duplicated block (43–44 lines × 2) crossbeam-channel/src/flavors/list.rs:251
- Duplicated block (40 lines × 2) crossbeam-deque/src/deque.rs:1724
- Duplicated block (33 lines × 3) crossbeam-channel/src/flavors/list.rs:532
- Duplicated block (31 lines × 2) crossbeam-skiplist/src/base.rs:863
- Duplicated block (26 lines × 2) crossbeam-deque/src/deque.rs:917
- Duplicated block (23 lines × 2) crossbeam-deque/src/deque.rs:880
- Duplicated block (22 lines × 2) crossbeam-channel/src/flavors/array.rs:427
- Duplicated block (21 lines × 2) crossbeam-deque/src/deque.rs:778
- Duplicated block (20 lines × 2) crossbeam-channel/src/flavors/array.rs:184
- Duplicated block (19 lines × 3) crossbeam-deque/src/deque.rs:1486
- Duplicated block (18 lines × 2) crossbeam-channel/src/flavors/list.rs:378
- Duplicated block (17 lines × 2) crossbeam-channel/src/flavors/list.rs:335
- Duplicated block (16 lines × 2) crossbeam-channel/src/flavors/list.rs:707
- Duplicated block (13–14 lines × 3) crossbeam-channel/src/flavors/list.rs:137
- Duplicated block (14 lines × 3) crossbeam-channel/src/flavors/list.rs:688
- Duplicated block (12–13 lines × 3) crossbeam-deque/src/deque.rs:1508
- Duplicated block (7–12 lines × 2) crossbeam-queue/src/array_queue.rs:152
- Duplicated block (11 lines × 4) crossbeam-channel/src/flavors/list.rs:339
- Duplicated block (11 lines × 3) crossbeam-deque/src/deque.rs:1538
- Duplicated block (11 lines × 2) crossbeam-deque/src/deque.rs:250
- Duplicated block (10 lines × 2) crossbeam-deque/src/deque.rs:1712
- Duplicated block (9 lines × 4) crossbeam-deque/src/deque.rs:1536
- Duplicated block (9 lines × 3) crossbeam-channel/src/flavors/array.rs:258
- Duplicated block (8 lines × 2) crossbeam-skiplist/src/base.rs:1968
- Duplicated block (7 lines × 2) crossbeam-channel/src/counter.rs:71
- Duplicated block (6 lines × 4) crossbeam-channel/src/flavors/array.rs:175
- Duplicated block (5 lines × 2) crossbeam-skiplist/src/base.rs:1823
- Duplicated block (6 lines × 3) crossbeam-channel/src/flavors/list.rs:73
- Duplicated block (16 lines × 3) crossbeam-channel/src/flavors/list.rs:103
- Duplicated block (10 lines × 3) crossbeam-channel/src/flavors/list.rs:121
- Duplicated block (5 lines × 3) crossbeam-channel/src/flavors/list.rs:674
- Off the main sequence: crossbeam-utils
Minor — 26 finding(s)
- Orphaned file crossbeam-utils/src/backoff.rs:1
- Orphaned file crossbeam-utils/src/atomic/seq_lock_wide.rs:1
- Orphaned file crossbeam-channel/benchmarks/crossbeam-channel.rs:1
- Orphaned file crossbeam-channel/src/context.rs:1
- Orphaned file crossbeam-channel/benchmarks/go.go:1
- Orphaned file crossbeam-channel/benchmarks/flume.rs:1
- Orphaned file crossbeam-channel/benchmarks/plot.py:1
- Orphaned file crossbeam-channel/benchmarks/mpsc.rs:1
- Orphaned file crossbeam-channel/benchmarks/atomicring.rs:1
- Orphaned file crossbeam-skiplist/src/comparator.rs:1
- Orphaned file crossbeam-channel/benchmarks/mpmc.rs:1
- Orphaned file crossbeam-utils/src/atomic/seq_lock.rs:1
- Orphaned file crossbeam-channel/benchmarks/atomicringqueue.rs:1
- Orphaned file crossbeam-channel/benchmarks/segqueue.rs:1
- Duplicated predicate crossbeam-channel/src/flavors/array.rs:654
- Duplicated predicate crossbeam-channel/src/flavors/array.rs:446
- Duplicated predicate crossbeam-channel/src/flavors/list.rs:258
- Off-boarding risk: anonymized user #1
- Orphaned files with no living knowledge
- REDACTED
- REDACTED
- REDACTED
- Inverted test pyramid
- No ADRs
- No architecture diagram/doc
- CI build step not evidenced
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-b086245fc5454cf1a96edd899506d5a9/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-b086245fc5454cf1a96edd899506d5a9/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 . | 0 | 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 | — |