Executive summary
rayon-rs/rayon falls short of our standard for production, held back most by its Maturity lens, the way the project is documented and understood. It scores 66 out of 100 and is rated Adequate, and 24 of its 25 critical findings are security problems in the build pipeline and in its automatic dependency updates.
Maturity, at 56, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 7 points. Fixing the part of the code only one person knows comes next, worth about 3 points. Raising Maturity to 70 would lift the score to about 70.
Twenty-two pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. One automatic update takes new releases before a bad one can be spotted, and one pipeline step runs a download nobody checks. Pinning each tool to an exact version, setting a waiting period for automatic updates and checking the download against a checksum would close these risks. The set of files in separate parts that keep changing together needs that dependency made explicit.
The product code is 34,818 lines, about €44,000 to rebuild.
If Maturity rose from 56 to 70, the lowest score rated Strong, the score would rise from 66 to about 70.
New since the last survey: 5 findings
- Change Coupling · Change coupling: mod.rs ↔ mod.rs rayon-core/src/broadcast/mod.rs
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Documentation (README) · README may be stale
Fixed since the last survey: 2 findings
- Code Duplication · Duplicated block (10 lines × 2) rayon-core/src/scope/mod.rs
- Supply-chain Provenance & Signing REDACTED
Rebuild cost: about €44,000 · Estimate
| Cost to rebuild | €15,000 to €73,000, for 242 to 769 hours of work, about 0.3 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.9 at a score of 66. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Medium: 34,818 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 rayon_demo.tsp.weight | 2 rayon.collections.binary_heap | 3 rayon.iter.plumbing | 4 rayon_core.registry | 5 rayon_demo.tsp.graph | 6 rayon.iter.blocks | 7 rayon.iter.chain | 8 rayon.iter.chunks | 9 rayon.iter.cloned | 10 rayon.iter.copied | 11 rayon.iter.enumerate | 12 rayon.iter.inspect | 13 rayon.iter.len | 14 rayon.iter.map | 15 rayon.iter.map_with | 16 rayon.iter.panic_fuse | 17 rayon.iter.rev | 18 rayon.iter.step_by | 19 rayon.iter.update | 20 rayon.iter.zip | 21 rayon_core.latch | 22 rayon_demo.tsp.tour | 23 rayon.iter.interleave | 24 rayon.iter.intersperse | 25 rayon_core.scope | 26 rayon_demo.tsp.solver | 27 rayon.iter | 28 rayon_demo.tsp.step | 29 rayon.array | 30 rayon.iter.par_bridge | 31 rayon.iter.splitter | 32 rayon.collections.vec_deque | 33 rayon.iter.repeat | 34 rayon.range | 35 rayon.slice.chunks | 36 rayon.slice.rchunks | 37 rayon.slice.windows | 38 rayon.vec | 39 rayon.slice | 40 rayon.str |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 rayon_demo.tsp.weight | ||||||||||||||||||||||||||||||||||||||||
| 2 rayon.collections.binary_heap | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 3 rayon.iter.plumbing | 1 | |||||||||||||||||||||||||||||||||||||||
| 4 rayon_core.registry | 3 | |||||||||||||||||||||||||||||||||||||||
| 5 rayon_demo.tsp.graph | 2 | |||||||||||||||||||||||||||||||||||||||
| 6 rayon.iter.blocks | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 7 rayon.iter.chain | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 8 rayon.iter.chunks | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 9 rayon.iter.cloned | 6 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 10 rayon.iter.copied | 6 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 11 rayon.iter.enumerate | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 12 rayon.iter.inspect | 6 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 13 rayon.iter.len | 2 | 4 | 2 | |||||||||||||||||||||||||||||||||||||
| 14 rayon.iter.map | 6 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 15 rayon.iter.map_with | 11 | 4 | 2 | |||||||||||||||||||||||||||||||||||||
| 16 rayon.iter.panic_fuse | 7 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 17 rayon.iter.rev | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 18 rayon.iter.step_by | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 19 rayon.iter.update | 6 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 20 rayon.iter.zip | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 21 rayon_core.latch | 4 | |||||||||||||||||||||||||||||||||||||||
| 22 rayon_demo.tsp.tour | 2 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 23 rayon.iter.interleave | 1 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 24 rayon.iter.intersperse | 6 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 25 rayon_core.scope | 7 | 1 | ||||||||||||||||||||||||||||||||||||||
| 26 rayon_demo.tsp.solver | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 27 rayon.iter | 5 | 2 | 1 | 1 | 1 | 1 | 1 | 1 | 2 | 1 | 2 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||
| 28 rayon_demo.tsp.step | 1 | 3 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 29 rayon.array | 2 | |||||||||||||||||||||||||||||||||||||||
| 30 rayon.iter.par_bridge | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 31 rayon.iter.splitter | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 32 rayon.collections.vec_deque | 2 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 33 rayon.iter.repeat | 2 | 1 | 3 | 1 | ||||||||||||||||||||||||||||||||||||
| 34 rayon.range | 2 | 2 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 35 rayon.slice.chunks | 4 | 8 | 4 | |||||||||||||||||||||||||||||||||||||
| 36 rayon.slice.rchunks | 4 | 8 | 4 | |||||||||||||||||||||||||||||||||||||
| 37 rayon.slice.windows | 1 | 4 | 1 | |||||||||||||||||||||||||||||||||||||
| 38 rayon.vec | 1 | 4 | 1 | |||||||||||||||||||||||||||||||||||||
| 39 rayon.slice | 2 | 1 | 8 | 2 | 1 | 3 | 4 | 2 | ||||||||||||||||||||||||||||||||
| 40 rayon.str | 7 | 12 | 2 | 1 |
2→27 rayon.collections.binary_heap uses rayon.iter part of a loop✕
- Connections
- 2 pairs of types, where a type in rayon.collections.binary_heap uses a type in rayon.iter.
- The types involved
rayon.collections.binary_heap.Drain→rayon.iter.IndexedParallelIteratorrayon.collections.binary_heap.Drain→rayon.iter.ParallelIterator
- Direction
- rayon.collections.binary_heap uses rayon.iter, so a change to rayon.iter can break rayon.collections.binary_heap, while a change to rayon.collections.binary_heap can't break rayon.iter.
- 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.
2→29 rayon.collections.binary_heap uses rayon.array part of a loop✕
- Connections
- 1 pair of types, where a type in rayon.collections.binary_heap uses a type in rayon.array.
- The types involved
rayon.collections.binary_heap.IntoIter→rayon.array.IntoIter
- Direction
- rayon.collections.binary_heap uses rayon.array, so a change to rayon.array can break rayon.collections.binary_heap, while a change to rayon.collections.binary_heap can't break rayon.array.
- 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.
3→29 rayon.iter.plumbing uses rayon.array part of a loop✕
- Connections
- 1 pair of types, where a type in rayon.iter.plumbing uses a type in rayon.array.
- The types involved
rayon.iter.plumbing.Producer→rayon.array.IntoIter
- Direction
- rayon.iter.plumbing uses rayon.array, so a change to rayon.array can break rayon.iter.plumbing, while a change to rayon.iter.plumbing can't break rayon.array.
- 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.
4→21 rayon_core.registry uses rayon_core.latch part of a loop✕
- Connections
- 3 pairs of types, where a type in rayon_core.registry uses a type in rayon_core.latch.
- The types involved
rayon_core.registry.ThreadInfo→rayon_core.latch.LockLatchrayon_core.registry.ThreadInfo→rayon_core.latch.OnceLatchrayon_core.registry.WorkerThread→rayon_core.latch.CoreLatch
- Direction
- rayon_core.registry uses rayon_core.latch, so a change to rayon_core.latch can break rayon_core.registry, while a change to rayon_core.registry can't break rayon_core.latch.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
5→1 rayon_demo.tsp.graph uses rayon_demo.tsp.weight✕
- Connections
- 2 pairs of types, where a type in rayon_demo.tsp.graph uses a type in rayon_demo.tsp.weight.
- The types involved
rayon_demo.tsp.graph.Edge→rayon_demo.tsp.weight.Weightrayon_demo.tsp.graph.Graph→rayon_demo.tsp.weight.Weight
- Direction
- rayon_demo.tsp.graph uses rayon_demo.tsp.weight, so a change to rayon_demo.tsp.weight can break rayon_demo.tsp.graph, while a change to rayon_demo.tsp.graph can't break rayon_demo.tsp.weight.
- Position
- Below the diagonal: rayon_demo.tsp.graph uses a module listed above it, which is the healthy direction.
6→3 rayon.iter.blocks uses rayon.iter.plumbing✕
- Connections
- 1 pair of types, where a type in rayon.iter.blocks uses a type in rayon.iter.plumbing.
- The types involved
rayon.iter.blocks.BlocksCallback→rayon.iter.plumbing.ProducerCallback
- Direction
- rayon.iter.blocks uses rayon.iter.plumbing, so a change to rayon.iter.plumbing can break rayon.iter.blocks, while a change to rayon.iter.blocks can't break rayon.iter.plumbing.
- Position
- Below the diagonal: rayon.iter.blocks uses a module listed above it, which is the healthy direction.
6→27 rayon.iter.blocks uses rayon.iter part of a loop✕
- Connections
- 2 pairs of types, where a type in rayon.iter.blocks uses a type in rayon.iter.
- The types involved
rayon.iter.blocks.ExponentialBlocks→rayon.iter.ParallelIteratorrayon.iter.blocks.UniformBlocks→rayon.iter.ParallelIterator
- Direction
- rayon.iter.blocks uses rayon.iter, so a change to rayon.iter can break rayon.iter.blocks, while a change to rayon.iter.blocks can't break rayon.iter.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→3 rayon.iter.chain uses rayon.iter.plumbing✕
- Connections
- 1 pair of types, where a type in rayon.iter.chain uses a type in rayon.iter.plumbing.
- The types involved
rayon.iter.chain.ChainProducer→rayon.iter.plumbing.Producer
- Direction
- rayon.iter.chain uses rayon.iter.plumbing, so a change to rayon.iter.plumbing can break rayon.iter.chain, while a change to rayon.iter.chain can't break rayon.iter.plumbing.
- Position
- Below the diagonal: rayon.iter.chain uses a module listed above it, which is the healthy direction.
7→27 rayon.iter.chain uses rayon.iter part of a loop✕
- Connections
- 2 pairs of types, where a type in rayon.iter.chain uses a type in rayon.iter.
- The types involved
rayon.iter.chain.Chain→rayon.iter.IndexedParallelIteratorrayon.iter.chain.Chain→rayon.iter.ParallelIterator
- Direction
- rayon.iter.chain uses rayon.iter, so a change to rayon.iter can break rayon.iter.chain, while a change to rayon.iter.chain can't break rayon.iter.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→29 rayon.iter.chain uses rayon.array part of a loop✕
- Connections
- 1 pair of types, where a type in rayon.iter.chain uses a type in rayon.array.
- The types involved
rayon.iter.chain.ChainProducer→rayon.array.IntoIter
- Direction
- rayon.iter.chain uses rayon.array, so a change to rayon.array can break rayon.iter.chain, while a change to rayon.iter.chain can't break rayon.array.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→3 rayon.iter.chunks uses rayon.iter.plumbing✕
- Connections
- 1 pair of types, where a type in rayon.iter.chunks uses a type in rayon.iter.plumbing.
- The types involved
rayon.iter.chunks.ChunkProducer→rayon.iter.plumbing.Producer
- Direction
- rayon.iter.chunks uses rayon.iter.plumbing, so a change to rayon.iter.plumbing can break rayon.iter.chunks, while a change to rayon.iter.chunks can't break rayon.iter.plumbing.
- Position
- Below the diagonal: rayon.iter.chunks uses a module listed above it, which is the healthy direction.
8→27 rayon.iter.chunks uses rayon.iter part of a loop✕
- Connections
- 2 pairs of types, where a type in rayon.iter.chunks uses a type in rayon.iter.
- The types involved
rayon.iter.chunks.Chunks→rayon.iter.IndexedParallelIteratorrayon.iter.chunks.Chunks→rayon.iter.ParallelIterator
- Direction
- rayon.iter.chunks uses rayon.iter, so a change to rayon.iter can break rayon.iter.chunks, while a change to rayon.iter.chunks can't break rayon.iter.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→29 rayon.iter.chunks uses rayon.array part of a loop✕
- Connections
- 1 pair of types, where a type in rayon.iter.chunks uses a type in rayon.array.
- The types involved
rayon.iter.chunks.ChunkProducer→rayon.array.IntoIter
- Direction
- rayon.iter.chunks uses rayon.array, so a change to rayon.array can break rayon.iter.chunks, while a change to rayon.iter.chunks can't break rayon.array.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→3 rayon.iter.cloned uses rayon.iter.plumbing✕
- Connections
- 6 pairs of types, where a type in rayon.iter.cloned uses a type in rayon.iter.plumbing.
- The types involved
rayon.iter.cloned.ClonedConsumer→rayon.iter.plumbing.Consumerrayon.iter.cloned.ClonedConsumer→rayon.iter.plumbing.Folderrayon.iter.cloned.ClonedConsumer→rayon.iter.plumbing.Reducerrayon.iter.cloned.ClonedConsumer→rayon.iter.plumbing.UnindexedConsumerrayon.iter.cloned.ClonedFolder→rayon.iter.plumbing.Folderrayon.iter.cloned.ClonedProducer→rayon.iter.plumbing.Producer
- Direction
- rayon.iter.cloned uses rayon.iter.plumbing, so a change to rayon.iter.plumbing can break rayon.iter.cloned, while a change to rayon.iter.cloned can't break rayon.iter.plumbing.
- Position
- Below the diagonal: rayon.iter.cloned uses a module listed above it, which is the healthy direction.
9→27 rayon.iter.cloned uses rayon.iter part of a loop✕
- Connections
- 2 pairs of types, where a type in rayon.iter.cloned uses a type in rayon.iter.
- The types involved
rayon.iter.cloned.Cloned→rayon.iter.IndexedParallelIteratorrayon.iter.cloned.Cloned→rayon.iter.ParallelIterator
- Direction
- rayon.iter.cloned uses rayon.iter, so a change to rayon.iter can break rayon.iter.cloned, while a change to rayon.iter.cloned can't break rayon.iter.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→29 rayon.iter.cloned uses rayon.array part of a loop✕
- Connections
- 1 pair of types, where a type in rayon.iter.cloned uses a type in rayon.array.
- The types involved
rayon.iter.cloned.ClonedProducer→rayon.array.IntoIter
- Direction
- rayon.iter.cloned uses rayon.array, so a change to rayon.array can break rayon.iter.cloned, while a change to rayon.iter.cloned can't break rayon.array.
- 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→3 rayon.iter.copied uses rayon.iter.plumbing✕
- Connections
- 6 pairs of types, where a type in rayon.iter.copied uses a type in rayon.iter.plumbing.
- The types involved
rayon.iter.copied.CopiedConsumer→rayon.iter.plumbing.Consumerrayon.iter.copied.CopiedConsumer→rayon.iter.plumbing.Folderrayon.iter.copied.CopiedConsumer→rayon.iter.plumbing.Reducerrayon.iter.copied.CopiedConsumer→rayon.iter.plumbing.UnindexedConsumerrayon.iter.copied.CopiedFolder→rayon.iter.plumbing.Folderrayon.iter.copied.CopiedProducer→rayon.iter.plumbing.Producer
- Direction
- rayon.iter.copied uses rayon.iter.plumbing, so a change to rayon.iter.plumbing can break rayon.iter.copied, while a change to rayon.iter.copied can't break rayon.iter.plumbing.
- Position
- Below the diagonal: rayon.iter.copied uses a module listed above it, which is the healthy direction.
10→27 rayon.iter.copied uses rayon.iter part of a loop✕
- Connections
- 2 pairs of types, where a type in rayon.iter.copied uses a type in rayon.iter.
- The types involved
rayon.iter.copied.Copied→rayon.iter.IndexedParallelIteratorrayon.iter.copied.Copied→rayon.iter.ParallelIterator
- Direction
- rayon.iter.copied uses rayon.iter, so a change to rayon.iter can break rayon.iter.copied, while a change to rayon.iter.copied can't break rayon.iter.
- 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→29 rayon.iter.copied uses rayon.array part of a loop✕
- Connections
- 1 pair of types, where a type in rayon.iter.copied uses a type in rayon.array.
- The types involved
rayon.iter.copied.CopiedProducer→rayon.array.IntoIter
- Direction
- rayon.iter.copied uses rayon.array, so a change to rayon.array can break rayon.iter.copied, while a change to rayon.iter.copied can't break rayon.array.
- 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→3 rayon.iter.enumerate uses rayon.iter.plumbing✕
- Connections
- 1 pair of types, where a type in rayon.iter.enumerate uses a type in rayon.iter.plumbing.
- The types involved
rayon.iter.enumerate.EnumerateProducer→rayon.iter.plumbing.Producer
- Direction
- rayon.iter.enumerate uses rayon.iter.plumbing, so a change to rayon.iter.plumbing can break rayon.iter.enumerate, while a change to rayon.iter.enumerate can't break rayon.iter.plumbing.
- Position
- Below the diagonal: rayon.iter.enumerate uses a module listed above it, which is the healthy direction.
11→27 rayon.iter.enumerate uses rayon.iter part of a loop✕
- Connections
- 2 pairs of types, where a type in rayon.iter.enumerate uses a type in rayon.iter.
- The types involved
rayon.iter.enumerate.Enumerate→rayon.iter.IndexedParallelIteratorrayon.iter.enumerate.Enumerate→rayon.iter.ParallelIterator
- Direction
- rayon.iter.enumerate uses rayon.iter, so a change to rayon.iter can break rayon.iter.enumerate, while a change to rayon.iter.enumerate can't break rayon.iter.
- 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→29 rayon.iter.enumerate uses rayon.array part of a loop✕
- Connections
- 1 pair of types, where a type in rayon.iter.enumerate uses a type in rayon.array.
- The types involved
rayon.iter.enumerate.EnumerateProducer→rayon.array.IntoIter
- Direction
- rayon.iter.enumerate uses rayon.array, so a change to rayon.array can break rayon.iter.enumerate, while a change to rayon.iter.enumerate can't break rayon.array.
- 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→3 rayon.iter.inspect uses rayon.iter.plumbing✕
- Connections
- 6 pairs of types, where a type in rayon.iter.inspect uses a type in rayon.iter.plumbing.
- The types involved
rayon.iter.inspect.InspectConsumer→rayon.iter.plumbing.Consumerrayon.iter.inspect.InspectConsumer→rayon.iter.plumbing.Folderrayon.iter.inspect.InspectConsumer→rayon.iter.plumbing.Reducerrayon.iter.inspect.InspectConsumer→rayon.iter.plumbing.UnindexedConsumerrayon.iter.inspect.InspectFolder→rayon.iter.plumbing.Folderrayon.iter.inspect.InspectProducer→rayon.iter.plumbing.Producer
- Direction
- rayon.iter.inspect uses rayon.iter.plumbing, so a change to rayon.iter.plumbing can break rayon.iter.inspect, while a change to rayon.iter.inspect can't break rayon.iter.plumbing.
- Position
- Below the diagonal: rayon.iter.inspect uses a module listed above it, which is the healthy direction.
12→27 rayon.iter.inspect uses rayon.iter part of a loop✕
- Connections
- 2 pairs of types, where a type in rayon.iter.inspect uses a type in rayon.iter.
- The types involved
rayon.iter.inspect.Inspect→rayon.iter.IndexedParallelIteratorrayon.iter.inspect.Inspect→rayon.iter.ParallelIterator
- Direction
- rayon.iter.inspect uses rayon.iter, so a change to rayon.iter can break rayon.iter.inspect, while a change to rayon.iter.inspect can't break rayon.iter.
- 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→29 rayon.iter.inspect uses rayon.array part of a loop✕
- Connections
- 1 pair of types, where a type in rayon.iter.inspect uses a type in rayon.array.
- The types involved
rayon.iter.inspect.InspectProducer→rayon.array.IntoIter
- Direction
- rayon.iter.inspect uses rayon.array, so a change to rayon.array can break rayon.iter.inspect, while a change to rayon.iter.inspect can't break rayon.array.
- 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→3 rayon.iter.len uses rayon.iter.plumbing✕
- Connections
- 2 pairs of types, where a type in rayon.iter.len uses a type in rayon.iter.plumbing.
- The types involved
rayon.iter.len.MaxLenProducer→rayon.iter.plumbing.Producerrayon.iter.len.MinLenProducer→rayon.iter.plumbing.Producer
- Direction
- rayon.iter.len uses rayon.iter.plumbing, so a change to rayon.iter.plumbing can break rayon.iter.len, while a change to rayon.iter.len can't break rayon.iter.plumbing.
- Position
- Below the diagonal: rayon.iter.len uses a module listed above it, which is the healthy direction.
13→27 rayon.iter.len uses rayon.iter part of a loop✕
- Connections
- 4 pairs of types, where a type in rayon.iter.len uses a type in rayon.iter.
- The types involved
rayon.iter.len.MaxLen→rayon.iter.IndexedParallelIteratorrayon.iter.len.MaxLen→rayon.iter.ParallelIteratorrayon.iter.len.MinLen→rayon.iter.IndexedParallelIteratorrayon.iter.len.MinLen→rayon.iter.ParallelIterator
- Direction
- rayon.iter.len uses rayon.iter, so a change to rayon.iter can break rayon.iter.len, while a change to rayon.iter.len can't break rayon.iter.
- 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→29 rayon.iter.len uses rayon.array part of a loop✕
- Connections
- 2 pairs of types, where a type in rayon.iter.len uses a type in rayon.array.
- The types involved
rayon.iter.len.MaxLenProducer→rayon.array.IntoIterrayon.iter.len.MinLenProducer→rayon.array.IntoIter
- Direction
- rayon.iter.len uses rayon.array, so a change to rayon.array can break rayon.iter.len, while a change to rayon.iter.len can't break rayon.array.
- 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.
14→3 rayon.iter.map uses rayon.iter.plumbing✕
- Connections
- 6 pairs of types, where a type in rayon.iter.map uses a type in rayon.iter.plumbing.
- The types involved
rayon.iter.map.MapConsumer→rayon.iter.plumbing.Consumerrayon.iter.map.MapConsumer→rayon.iter.plumbing.Folderrayon.iter.map.MapConsumer→rayon.iter.plumbing.Reducerrayon.iter.map.MapConsumer→rayon.iter.plumbing.UnindexedConsumerrayon.iter.map.MapFolder→rayon.iter.plumbing.Folderrayon.iter.map.MapProducer→rayon.iter.plumbing.Producer
- Direction
- rayon.iter.map uses rayon.iter.plumbing, so a change to rayon.iter.plumbing can break rayon.iter.map, while a change to rayon.iter.map can't break rayon.iter.plumbing.
- Position
- Below the diagonal: rayon.iter.map uses a module listed above it, which is the healthy direction.
14→27 rayon.iter.map uses rayon.iter part of a loop✕
- Connections
- 2 pairs of types, where a type in rayon.iter.map uses a type in rayon.iter.
- The types involved
rayon.iter.map.Map→rayon.iter.IndexedParallelIteratorrayon.iter.map.Map→rayon.iter.ParallelIterator
- Direction
- rayon.iter.map uses rayon.iter, so a change to rayon.iter can break rayon.iter.map, while a change to rayon.iter.map can't break rayon.iter.
- 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.
14→29 rayon.iter.map uses rayon.array part of a loop✕
- Connections
- 1 pair of types, where a type in rayon.iter.map uses a type in rayon.array.
- The types involved
rayon.iter.map.MapProducer→rayon.array.IntoIter
- Direction
- rayon.iter.map uses rayon.array, so a change to rayon.array can break rayon.iter.map, while a change to rayon.iter.map can't break rayon.array.
- 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.
15→3 rayon.iter.map_with uses rayon.iter.plumbing✕
- Connections
- 11 pairs of types, where a type in rayon.iter.map_with uses a type in rayon.iter.plumbing.
- The types involved
rayon.iter.map_with.MapInitConsumer→rayon.iter.plumbing.Consumerrayon.iter.map_with.MapInitConsumer→rayon.iter.plumbing.Folderrayon.iter.map_with.MapInitConsumer→rayon.iter.plumbing.Reducerrayon.iter.map_with.MapInitConsumer→rayon.iter.plumbing.UnindexedConsumerrayon.iter.map_with.MapInitProducer→rayon.iter.plumbing.Producerrayon.iter.map_with.MapWithConsumer→rayon.iter.plumbing.Consumerrayon.iter.map_with.MapWithConsumer→rayon.iter.plumbing.Folderrayon.iter.map_with.MapWithConsumer→rayon.iter.plumbing.Reducerrayon.iter.map_with.MapWithConsumer→rayon.iter.plumbing.UnindexedConsumerrayon.iter.map_with.MapWithFolder→rayon.iter.plumbing.Folderrayon.iter.map_with.MapWithProducer→rayon.iter.plumbing.Producer
- Direction
- rayon.iter.map_with uses rayon.iter.plumbing, so a change to rayon.iter.plumbing can break rayon.iter.map_with, while a change to rayon.iter.map_with can't break rayon.iter.plumbing.
- Position
- Below the diagonal: rayon.iter.map_with uses a module listed above it, which is the healthy direction.
15→27 rayon.iter.map_with uses rayon.iter part of a loop✕
- Connections
- 4 pairs of types, where a type in rayon.iter.map_with uses a type in rayon.iter.
- The types involved
rayon.iter.map_with.MapInit→rayon.iter.IndexedParallelIteratorrayon.iter.map_with.MapInit→rayon.iter.ParallelIteratorrayon.iter.map_with.MapWith→rayon.iter.IndexedParallelIteratorrayon.iter.map_with.MapWith→rayon.iter.ParallelIterator
- Direction
- rayon.iter.map_with uses rayon.iter, so a change to rayon.iter can break rayon.iter.map_with, while a change to rayon.iter.map_with can't break rayon.iter.
- 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.
15→29 rayon.iter.map_with uses rayon.array part of a loop✕
- Connections
- 2 pairs of types, where a type in rayon.iter.map_with uses a type in rayon.array.
- The types involved
rayon.iter.map_with.MapInitProducer→rayon.array.IntoIterrayon.iter.map_with.MapWithProducer→rayon.array.IntoIter
- Direction
- rayon.iter.map_with uses rayon.array, so a change to rayon.array can break rayon.iter.map_with, while a change to rayon.iter.map_with can't break rayon.array.
- 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.
16→3 rayon.iter.panic_fuse uses rayon.iter.plumbing✕
- Connections
- 7 pairs of types, where a type in rayon.iter.panic_fuse uses a type in rayon.iter.plumbing.
- The types involved
rayon.iter.panic_fuse.PanicFuseConsumer→rayon.iter.plumbing.Consumerrayon.iter.panic_fuse.PanicFuseConsumer→rayon.iter.plumbing.Folderrayon.iter.panic_fuse.PanicFuseConsumer→rayon.iter.plumbing.Reducerrayon.iter.panic_fuse.PanicFuseConsumer→rayon.iter.plumbing.UnindexedConsumerrayon.iter.panic_fuse.PanicFuseFolder→rayon.iter.plumbing.Folderrayon.iter.panic_fuse.PanicFuseProducer→rayon.iter.plumbing.Producerrayon.iter.panic_fuse.PanicFuseReducer→rayon.iter.plumbing.Reducer
- Direction
- rayon.iter.panic_fuse uses rayon.iter.plumbing, so a change to rayon.iter.plumbing can break rayon.iter.panic_fuse, while a change to rayon.iter.panic_fuse can't break rayon.iter.plumbing.
- Position
- Below the diagonal: rayon.iter.panic_fuse uses a module listed above it, which is the healthy direction.
16→27 rayon.iter.panic_fuse uses rayon.iter part of a loop✕
- Connections
- 2 pairs of types, where a type in rayon.iter.panic_fuse uses a type in rayon.iter.
- The types involved
rayon.iter.panic_fuse.PanicFuse→rayon.iter.IndexedParallelIteratorrayon.iter.panic_fuse.PanicFuse→rayon.iter.ParallelIterator
- Direction
- rayon.iter.panic_fuse uses rayon.iter, so a change to rayon.iter can break rayon.iter.panic_fuse, while a change to rayon.iter.panic_fuse can't break rayon.iter.
- 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.
16→29 rayon.iter.panic_fuse uses rayon.array part of a loop✕
- Connections
- 1 pair of types, where a type in rayon.iter.panic_fuse uses a type in rayon.array.
- The types involved
rayon.iter.panic_fuse.PanicFuseProducer→rayon.array.IntoIter
- Direction
- rayon.iter.panic_fuse uses rayon.array, so a change to rayon.array can break rayon.iter.panic_fuse, while a change to rayon.iter.panic_fuse can't break rayon.array.
- 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.
17→3 rayon.iter.rev uses rayon.iter.plumbing✕
- Connections
- 1 pair of types, where a type in rayon.iter.rev uses a type in rayon.iter.plumbing.
- The types involved
rayon.iter.rev.RevProducer→rayon.iter.plumbing.Producer
- Direction
- rayon.iter.rev uses rayon.iter.plumbing, so a change to rayon.iter.plumbing can break rayon.iter.rev, while a change to rayon.iter.rev can't break rayon.iter.plumbing.
- Position
- Below the diagonal: rayon.iter.rev uses a module listed above it, which is the healthy direction.
17→27 rayon.iter.rev uses rayon.iter part of a loop✕
- Connections
- 2 pairs of types, where a type in rayon.iter.rev uses a type in rayon.iter.
- The types involved
rayon.iter.rev.Rev→rayon.iter.IndexedParallelIteratorrayon.iter.rev.Rev→rayon.iter.ParallelIterator
- Direction
- rayon.iter.rev uses rayon.iter, so a change to rayon.iter can break rayon.iter.rev, while a change to rayon.iter.rev can't break rayon.iter.
- 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.
17→29 rayon.iter.rev uses rayon.array part of a loop✕
- Connections
- 1 pair of types, where a type in rayon.iter.rev uses a type in rayon.array.
- The types involved
rayon.iter.rev.RevProducer→rayon.array.IntoIter
- Direction
- rayon.iter.rev uses rayon.array, so a change to rayon.array can break rayon.iter.rev, while a change to rayon.iter.rev can't break rayon.array.
- 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→3 rayon.iter.step_by uses rayon.iter.plumbing✕
- Connections
- 1 pair of types, where a type in rayon.iter.step_by uses a type in rayon.iter.plumbing.
- The types involved
rayon.iter.step_by.StepByProducer→rayon.iter.plumbing.Producer
- Direction
- rayon.iter.step_by uses rayon.iter.plumbing, so a change to rayon.iter.plumbing can break rayon.iter.step_by, while a change to rayon.iter.step_by can't break rayon.iter.plumbing.
- Position
- Below the diagonal: rayon.iter.step_by uses a module listed above it, which is the healthy direction.
18→27 rayon.iter.step_by uses rayon.iter part of a loop✕
- Connections
- 2 pairs of types, where a type in rayon.iter.step_by uses a type in rayon.iter.
- The types involved
rayon.iter.step_by.StepBy→rayon.iter.IndexedParallelIteratorrayon.iter.step_by.StepBy→rayon.iter.ParallelIterator
- Direction
- rayon.iter.step_by uses rayon.iter, so a change to rayon.iter can break rayon.iter.step_by, while a change to rayon.iter.step_by can't break rayon.iter.
- 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→29 rayon.iter.step_by uses rayon.array part of a loop✕
- Connections
- 1 pair of types, where a type in rayon.iter.step_by uses a type in rayon.array.
- The types involved
rayon.iter.step_by.StepByProducer→rayon.array.IntoIter
- Direction
- rayon.iter.step_by uses rayon.array, so a change to rayon.array can break rayon.iter.step_by, while a change to rayon.iter.step_by can't break rayon.array.
- 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→3 rayon.iter.update uses rayon.iter.plumbing✕
- Connections
- 6 pairs of types, where a type in rayon.iter.update uses a type in rayon.iter.plumbing.
- The types involved
rayon.iter.update.UpdateConsumer→rayon.iter.plumbing.Consumerrayon.iter.update.UpdateConsumer→rayon.iter.plumbing.Folderrayon.iter.update.UpdateConsumer→rayon.iter.plumbing.Reducerrayon.iter.update.UpdateConsumer→rayon.iter.plumbing.UnindexedConsumerrayon.iter.update.UpdateFolder→rayon.iter.plumbing.Folderrayon.iter.update.UpdateProducer→rayon.iter.plumbing.Producer
- Direction
- rayon.iter.update uses rayon.iter.plumbing, so a change to rayon.iter.plumbing can break rayon.iter.update, while a change to rayon.iter.update can't break rayon.iter.plumbing.
- Position
- Below the diagonal: rayon.iter.update uses a module listed above it, which is the healthy direction.
19→27 rayon.iter.update uses rayon.iter part of a loop✕
- Connections
- 2 pairs of types, where a type in rayon.iter.update uses a type in rayon.iter.
- The types involved
rayon.iter.update.Update→rayon.iter.IndexedParallelIteratorrayon.iter.update.Update→rayon.iter.ParallelIterator
- Direction
- rayon.iter.update uses rayon.iter, so a change to rayon.iter can break rayon.iter.update, while a change to rayon.iter.update can't break rayon.iter.
- 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→29 rayon.iter.update uses rayon.array part of a loop✕
- Connections
- 1 pair of types, where a type in rayon.iter.update uses a type in rayon.array.
- The types involved
rayon.iter.update.UpdateProducer→rayon.array.IntoIter
- Direction
- rayon.iter.update uses rayon.array, so a change to rayon.array can break rayon.iter.update, while a change to rayon.iter.update can't break rayon.array.
- 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→3 rayon.iter.zip uses rayon.iter.plumbing✕
- Connections
- 1 pair of types, where a type in rayon.iter.zip uses a type in rayon.iter.plumbing.
- The types involved
rayon.iter.zip.ZipProducer→rayon.iter.plumbing.Producer
- Direction
- rayon.iter.zip uses rayon.iter.plumbing, so a change to rayon.iter.plumbing can break rayon.iter.zip, while a change to rayon.iter.zip can't break rayon.iter.plumbing.
- Position
- Below the diagonal: rayon.iter.zip uses a module listed above it, which is the healthy direction.
20→27 rayon.iter.zip uses rayon.iter part of a loop✕
- Connections
- 2 pairs of types, where a type in rayon.iter.zip uses a type in rayon.iter.
- The types involved
rayon.iter.zip.Zip→rayon.iter.IndexedParallelIteratorrayon.iter.zip.Zip→rayon.iter.ParallelIterator
- Direction
- rayon.iter.zip uses rayon.iter, so a change to rayon.iter can break rayon.iter.zip, while a change to rayon.iter.zip can't break rayon.iter.
- 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→29 rayon.iter.zip uses rayon.array part of a loop✕
- Connections
- 1 pair of types, where a type in rayon.iter.zip uses a type in rayon.array.
- The types involved
rayon.iter.zip.ZipProducer→rayon.array.IntoIter
- Direction
- rayon.iter.zip uses rayon.array, so a change to rayon.array can break rayon.iter.zip, while a change to rayon.iter.zip can't break rayon.array.
- 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→4 rayon_core.latch uses rayon_core.registry✕
- Connections
- 4 pairs of types, where a type in rayon_core.latch uses a type in rayon_core.registry.
- The types involved
rayon_core.latch.CountLatch→rayon_core.registry.WorkerThreadrayon_core.latch.OnceLatch→rayon_core.registry.Registryrayon_core.latch.SpinLatch→rayon_core.registry.Registryrayon_core.latch.SpinLatch→rayon_core.registry.WorkerThread
- Direction
- rayon_core.latch uses rayon_core.registry, so a change to rayon_core.registry can break rayon_core.latch, while a change to rayon_core.latch can't break rayon_core.registry.
- Position
- Below the diagonal: rayon_core.latch uses a module listed above it, which is the healthy direction.
22→1 rayon_demo.tsp.tour uses rayon_demo.tsp.weight✕
- Connections
- 2 pairs of types, where a type in rayon_demo.tsp.tour uses a type in rayon_demo.tsp.weight.
- The types involved
rayon_demo.tsp.tour.TourPrefix→rayon_demo.tsp.weight.Priorityrayon_demo.tsp.tour.TourPrefix→rayon_demo.tsp.weight.Weight
- Direction
- rayon_demo.tsp.tour uses rayon_demo.tsp.weight, so a change to rayon_demo.tsp.weight can break rayon_demo.tsp.tour, while a change to rayon_demo.tsp.tour can't break rayon_demo.tsp.weight.
- Position
- Below the diagonal: rayon_demo.tsp.tour uses a module listed above it, which is the healthy direction.
22→5 rayon_demo.tsp.tour uses rayon_demo.tsp.graph✕
- Connections
- 2 pairs of types, where a type in rayon_demo.tsp.tour uses a type in rayon_demo.tsp.graph.
- The types involved
rayon_demo.tsp.tour.TourPrefix→rayon_demo.tsp.graph.Noderayon_demo.tsp.tour.TourPrefix→rayon_demo.tsp.graph.NodeSet
- Direction
- rayon_demo.tsp.tour uses rayon_demo.tsp.graph, so a change to rayon_demo.tsp.graph can break rayon_demo.tsp.tour, while a change to rayon_demo.tsp.tour can't break rayon_demo.tsp.graph.
- Position
- Below the diagonal: rayon_demo.tsp.tour uses a module listed above it, which is the healthy direction.
22→26 rayon_demo.tsp.tour uses rayon_demo.tsp.solver part of a loop✕
- Connections
- 1 pair of types, where a type in rayon_demo.tsp.tour uses a type in rayon_demo.tsp.solver.
- The types involved
rayon_demo.tsp.tour.TourPrefix→rayon_demo.tsp.solver.TourId
- Direction
- rayon_demo.tsp.tour uses rayon_demo.tsp.solver, so a change to rayon_demo.tsp.solver can break rayon_demo.tsp.tour, while a change to rayon_demo.tsp.tour can't break rayon_demo.tsp.solver.
- 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.
23→3 rayon.iter.interleave uses rayon.iter.plumbing✕
- Connections
- 1 pair of types, where a type in rayon.iter.interleave uses a type in rayon.iter.plumbing.
- The types involved
rayon.iter.interleave.InterleaveProducer→rayon.iter.plumbing.Producer
- Direction
- rayon.iter.interleave uses rayon.iter.plumbing, so a change to rayon.iter.plumbing can break rayon.iter.interleave, while a change to rayon.iter.interleave can't break rayon.iter.plumbing.
- Position
- Below the diagonal: rayon.iter.interleave uses a module listed above it, which is the healthy direction.
23→16 rayon.iter.interleave uses rayon.iter.panic_fuse✕
- Connections
- 1 pair of types, where a type in rayon.iter.interleave uses a type in rayon.iter.panic_fuse.
- The types involved
rayon.iter.interleave.InterleaveSeq→rayon.iter.panic_fuse.Fuse
- Direction
- rayon.iter.interleave uses rayon.iter.panic_fuse, so a change to rayon.iter.panic_fuse can break rayon.iter.interleave, while a change to rayon.iter.interleave can't break rayon.iter.panic_fuse.
- Position
- Below the diagonal: rayon.iter.interleave uses a module listed above it, which is the healthy direction.
23→27 rayon.iter.interleave uses rayon.iter part of a loop✕
- Connections
- 2 pairs of types, where a type in rayon.iter.interleave uses a type in rayon.iter.
- The types involved
rayon.iter.interleave.Interleave→rayon.iter.IndexedParallelIteratorrayon.iter.interleave.Interleave→rayon.iter.ParallelIterator
- Direction
- rayon.iter.interleave uses rayon.iter, so a change to rayon.iter can break rayon.iter.interleave, while a change to rayon.iter.interleave can't break rayon.iter.
- 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.
23→29 rayon.iter.interleave uses rayon.array part of a loop✕
- Connections
- 1 pair of types, where a type in rayon.iter.interleave uses a type in rayon.array.
- The types involved
rayon.iter.interleave.InterleaveProducer→rayon.array.IntoIter
- Direction
- rayon.iter.interleave uses rayon.array, so a change to rayon.array can break rayon.iter.interleave, while a change to rayon.iter.interleave can't break rayon.array.
- 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.
24→3 rayon.iter.intersperse uses rayon.iter.plumbing✕
- Connections
- 6 pairs of types, where a type in rayon.iter.intersperse uses a type in rayon.iter.plumbing.
- The types involved
rayon.iter.intersperse.IntersperseConsumer→rayon.iter.plumbing.Consumerrayon.iter.intersperse.IntersperseConsumer→rayon.iter.plumbing.Folderrayon.iter.intersperse.IntersperseConsumer→rayon.iter.plumbing.Reducerrayon.iter.intersperse.IntersperseConsumer→rayon.iter.plumbing.UnindexedConsumerrayon.iter.intersperse.IntersperseFolder→rayon.iter.plumbing.Folderrayon.iter.intersperse.IntersperseProducer→rayon.iter.plumbing.Producer
- Direction
- rayon.iter.intersperse uses rayon.iter.plumbing, so a change to rayon.iter.plumbing can break rayon.iter.intersperse, while a change to rayon.iter.intersperse can't break rayon.iter.plumbing.
- Position
- Below the diagonal: rayon.iter.intersperse uses a module listed above it, which is the healthy direction.
24→16 rayon.iter.intersperse uses rayon.iter.panic_fuse✕
- Connections
- 1 pair of types, where a type in rayon.iter.intersperse uses a type in rayon.iter.panic_fuse.
- The types involved
rayon.iter.intersperse.IntersperseIter→rayon.iter.panic_fuse.Fuse
- Direction
- rayon.iter.intersperse uses rayon.iter.panic_fuse, so a change to rayon.iter.panic_fuse can break rayon.iter.intersperse, while a change to rayon.iter.intersperse can't break rayon.iter.panic_fuse.
- Position
- Below the diagonal: rayon.iter.intersperse uses a module listed above it, which is the healthy direction.
24→27 rayon.iter.intersperse uses rayon.iter part of a loop✕
- Connections
- 2 pairs of types, where a type in rayon.iter.intersperse uses a type in rayon.iter.
- The types involved
rayon.iter.intersperse.Intersperse→rayon.iter.IndexedParallelIteratorrayon.iter.intersperse.Intersperse→rayon.iter.ParallelIterator
- Direction
- rayon.iter.intersperse uses rayon.iter, so a change to rayon.iter can break rayon.iter.intersperse, while a change to rayon.iter.intersperse can't break rayon.iter.
- 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.
24→29 rayon.iter.intersperse uses rayon.array part of a loop✕
- Connections
- 1 pair of types, where a type in rayon.iter.intersperse uses a type in rayon.array.
- The types involved
rayon.iter.intersperse.IntersperseProducer→rayon.array.IntoIter
- Direction
- rayon.iter.intersperse uses rayon.array, so a change to rayon.array can break rayon.iter.intersperse, while a change to rayon.iter.intersperse can't break rayon.array.
- 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.
25→4 rayon_core.scope uses rayon_core.registry✕
- Connections
- 7 pairs of types, where a type in rayon_core.scope uses a type in rayon_core.registry.
- The types involved
rayon_core.scope.Scope→rayon_core.registry.Registryrayon_core.scope.Scope→rayon_core.registry.WorkerThreadrayon_core.scope.ScopeBase→rayon_core.registry.Registryrayon_core.scope.ScopeBase→rayon_core.registry.WorkerThreadrayon_core.scope.ScopeFifo→rayon_core.registry.Registryrayon_core.scope.ScopeFifo→rayon_core.registry.WorkerThreadrayon_core.scope.scope$module→rayon_core.registry.Registry
- Direction
- rayon_core.scope uses rayon_core.registry, so a change to rayon_core.registry can break rayon_core.scope, while a change to rayon_core.scope can't break rayon_core.registry.
- Position
- Below the diagonal: rayon_core.scope uses a module listed above it, which is the healthy direction.
25→21 rayon_core.scope uses rayon_core.latch✕
- Connections
- 1 pair of types, where a type in rayon_core.scope uses a type in rayon_core.latch.
- The types involved
rayon_core.scope.ScopeBase→rayon_core.latch.CountLatch
- Direction
- rayon_core.scope uses rayon_core.latch, so a change to rayon_core.latch can break rayon_core.scope, while a change to rayon_core.scope can't break rayon_core.latch.
- Position
- Below the diagonal: rayon_core.scope uses a module listed above it, which is the healthy direction.
26→1 rayon_demo.tsp.solver uses rayon_demo.tsp.weight✕
- Connections
- 1 pair of types, where a type in rayon_demo.tsp.solver uses a type in rayon_demo.tsp.weight.
- The types involved
rayon_demo.tsp.solver.SolverCx→rayon_demo.tsp.weight.Weight
- Direction
- rayon_demo.tsp.solver uses rayon_demo.tsp.weight, so a change to rayon_demo.tsp.weight can break rayon_demo.tsp.solver, while a change to rayon_demo.tsp.solver can't break rayon_demo.tsp.weight.
- Position
- Below the diagonal: rayon_demo.tsp.solver uses a module listed above it, which is the healthy direction.
26→5 rayon_demo.tsp.solver uses rayon_demo.tsp.graph✕
- Connections
- 2 pairs of types, where a type in rayon_demo.tsp.solver uses a type in rayon_demo.tsp.graph.
- The types involved
rayon_demo.tsp.solver.SolverCx→rayon_demo.tsp.graph.Graphrayon_demo.tsp.solver.SolverCx→rayon_demo.tsp.graph.Node
- Direction
- rayon_demo.tsp.solver uses rayon_demo.tsp.graph, so a change to rayon_demo.tsp.graph can break rayon_demo.tsp.solver, while a change to rayon_demo.tsp.solver can't break rayon_demo.tsp.graph.
- Position
- Below the diagonal: rayon_demo.tsp.solver uses a module listed above it, which is the healthy direction.
26→22 rayon_demo.tsp.solver uses rayon_demo.tsp.tour✕
- Connections
- 1 pair of types, where a type in rayon_demo.tsp.solver uses a type in rayon_demo.tsp.tour.
- The types involved
rayon_demo.tsp.solver.SolverCx→rayon_demo.tsp.tour.TourPrefix
- Direction
- rayon_demo.tsp.solver uses rayon_demo.tsp.tour, so a change to rayon_demo.tsp.tour can break rayon_demo.tsp.solver, while a change to rayon_demo.tsp.solver can't break rayon_demo.tsp.tour.
- Position
- Below the diagonal: rayon_demo.tsp.solver uses a module listed above it, which is the healthy direction.
27→2 rayon.iter uses rayon.collections.binary_heap✕
- Connections
- 5 pairs of types, where a type in rayon.iter uses a type in rayon.collections.binary_heap.
- The types involved
rayon.iter.IntoParallelIterator→rayon.collections.binary_heap.Iterrayon.iter.IntoParallelRefIterator→rayon.collections.binary_heap.Iterrayon.iter.IntoParallelRefMutIterator→rayon.collections.binary_heap.Iterrayon.iter.ParallelDrainFull→rayon.collections.binary_heap.Iterrayon.iter.ParallelDrainRange→rayon.collections.binary_heap.Iter
- Direction
- rayon.iter uses rayon.collections.binary_heap, so a change to rayon.collections.binary_heap can break rayon.iter, while a change to rayon.iter can't break rayon.collections.binary_heap.
- Position
- Below the diagonal: rayon.iter uses a module listed above it, which is the healthy direction.
27→6 rayon.iter uses rayon.iter.blocks✕
- Connections
- 2 pairs of types, where a type in rayon.iter uses a type in rayon.iter.blocks.
- The types involved
rayon.iter.IndexedParallelIterator→rayon.iter.blocks.ExponentialBlocksrayon.iter.IndexedParallelIterator→rayon.iter.blocks.UniformBlocks
- Direction
- rayon.iter uses rayon.iter.blocks, so a change to rayon.iter.blocks can break rayon.iter, while a change to rayon.iter can't break rayon.iter.blocks.
- Position
- Below the diagonal: rayon.iter uses a module listed above it, which is the healthy direction.
27→7 rayon.iter uses rayon.iter.chain✕
- Connections
- 1 pair of types, where a type in rayon.iter uses a type in rayon.iter.chain.
- The types involved
rayon.iter.ParallelIterator→rayon.iter.chain.Chain
- Direction
- rayon.iter uses rayon.iter.chain, so a change to rayon.iter.chain can break rayon.iter, while a change to rayon.iter can't break rayon.iter.chain.
- Position
- Below the diagonal: rayon.iter uses a module listed above it, which is the healthy direction.
27→8 rayon.iter uses rayon.iter.chunks✕
- Connections
- 1 pair of types, where a type in rayon.iter uses a type in rayon.iter.chunks.
- The types involved
rayon.iter.IndexedParallelIterator→rayon.iter.chunks.Chunks
- Direction
- rayon.iter uses rayon.iter.chunks, so a change to rayon.iter.chunks can break rayon.iter, while a change to rayon.iter can't break rayon.iter.chunks.
- Position
- Below the diagonal: rayon.iter uses a module listed above it, which is the healthy direction.
27→9 rayon.iter uses rayon.iter.cloned✕
- Connections
- 1 pair of types, where a type in rayon.iter uses a type in rayon.iter.cloned.
- The types involved
rayon.iter.ParallelIterator→rayon.iter.cloned.Cloned
- Direction
- rayon.iter uses rayon.iter.cloned, so a change to rayon.iter.cloned can break rayon.iter, while a change to rayon.iter can't break rayon.iter.cloned.
- Position
- Below the diagonal: rayon.iter uses a module listed above it, which is the healthy direction.
27→10 rayon.iter uses rayon.iter.copied✕
- Connections
- 1 pair of types, where a type in rayon.iter uses a type in rayon.iter.copied.
- The types involved
rayon.iter.ParallelIterator→rayon.iter.copied.Copied
- Direction
- rayon.iter uses rayon.iter.copied, so a change to rayon.iter.copied can break rayon.iter, while a change to rayon.iter can't break rayon.iter.copied.
- Position
- Below the diagonal: rayon.iter uses a module listed above it, which is the healthy direction.
27→11 rayon.iter uses rayon.iter.enumerate✕
- Connections
- 1 pair of types, where a type in rayon.iter uses a type in rayon.iter.enumerate.
- The types involved
rayon.iter.IndexedParallelIterator→rayon.iter.enumerate.Enumerate
- Direction
- rayon.iter uses rayon.iter.enumerate, so a change to rayon.iter.enumerate can break rayon.iter, while a change to rayon.iter can't break rayon.iter.enumerate.
- Position
- Below the diagonal: rayon.iter uses a module listed above it, which is the healthy direction.
27→12 rayon.iter uses rayon.iter.inspect✕
- Connections
- 1 pair of types, where a type in rayon.iter uses a type in rayon.iter.inspect.
- The types involved
rayon.iter.ParallelIterator→rayon.iter.inspect.Inspect
- Direction
- rayon.iter uses rayon.iter.inspect, so a change to rayon.iter.inspect can break rayon.iter, while a change to rayon.iter can't break rayon.iter.inspect.
- Position
- Below the diagonal: rayon.iter uses a module listed above it, which is the healthy direction.
27→13 rayon.iter uses rayon.iter.len✕
- Connections
- 2 pairs of types, where a type in rayon.iter uses a type in rayon.iter.len.
- The types involved
rayon.iter.IndexedParallelIterator→rayon.iter.len.MaxLenrayon.iter.IndexedParallelIterator→rayon.iter.len.MinLen
- Direction
- rayon.iter uses rayon.iter.len, so a change to rayon.iter.len can break rayon.iter, while a change to rayon.iter can't break rayon.iter.len.
- Position
- Below the diagonal: rayon.iter uses a module listed above it, which is the healthy direction.
27→14 rayon.iter uses rayon.iter.map✕
- Connections
- 1 pair of types, where a type in rayon.iter uses a type in rayon.iter.map.
- The types involved
rayon.iter.ParallelIterator→rayon.iter.map.Map
- Direction
- rayon.iter uses rayon.iter.map, so a change to rayon.iter.map can break rayon.iter, while a change to rayon.iter can't break rayon.iter.map.
- Position
- Below the diagonal: rayon.iter uses a module listed above it, which is the healthy direction.
27→15 rayon.iter uses rayon.iter.map_with✕
- Connections
- 2 pairs of types, where a type in rayon.iter uses a type in rayon.iter.map_with.
- The types involved
rayon.iter.ParallelIterator→rayon.iter.map_with.MapInitrayon.iter.ParallelIterator→rayon.iter.map_with.MapWith
- Direction
- rayon.iter uses rayon.iter.map_with, so a change to rayon.iter.map_with can break rayon.iter, while a change to rayon.iter can't break rayon.iter.map_with.
- Position
- Below the diagonal: rayon.iter uses a module listed above it, which is the healthy direction.
27→16 rayon.iter uses rayon.iter.panic_fuse✕
- Connections
- 1 pair of types, where a type in rayon.iter uses a type in rayon.iter.panic_fuse.
- The types involved
rayon.iter.ParallelIterator→rayon.iter.panic_fuse.PanicFuse
- Direction
- rayon.iter uses rayon.iter.panic_fuse, so a change to rayon.iter.panic_fuse can break rayon.iter, while a change to rayon.iter can't break rayon.iter.panic_fuse.
- Position
- Below the diagonal: rayon.iter uses a module listed above it, which is the healthy direction.
27→17 rayon.iter uses rayon.iter.rev✕
- Connections
- 1 pair of types, where a type in rayon.iter uses a type in rayon.iter.rev.
- The types involved
rayon.iter.IndexedParallelIterator→rayon.iter.rev.Rev
- Direction
- rayon.iter uses rayon.iter.rev, so a change to rayon.iter.rev can break rayon.iter, while a change to rayon.iter can't break rayon.iter.rev.
- Position
- Below the diagonal: rayon.iter uses a module listed above it, which is the healthy direction.
27→18 rayon.iter uses rayon.iter.step_by✕
- Connections
- 1 pair of types, where a type in rayon.iter uses a type in rayon.iter.step_by.
- The types involved
rayon.iter.IndexedParallelIterator→rayon.iter.step_by.StepBy
- Direction
- rayon.iter uses rayon.iter.step_by, so a change to rayon.iter.step_by can break rayon.iter, while a change to rayon.iter can't break rayon.iter.step_by.
- Position
- Below the diagonal: rayon.iter uses a module listed above it, which is the healthy direction.
27→19 rayon.iter uses rayon.iter.update✕
- Connections
- 1 pair of types, where a type in rayon.iter uses a type in rayon.iter.update.
- The types involved
rayon.iter.ParallelIterator→rayon.iter.update.Update
- Direction
- rayon.iter uses rayon.iter.update, so a change to rayon.iter.update can break rayon.iter, while a change to rayon.iter can't break rayon.iter.update.
- Position
- Below the diagonal: rayon.iter uses a module listed above it, which is the healthy direction.
27→20 rayon.iter uses rayon.iter.zip✕
- Connections
- 1 pair of types, where a type in rayon.iter uses a type in rayon.iter.zip.
- The types involved
rayon.iter.IndexedParallelIterator→rayon.iter.zip.Zip
- Direction
- rayon.iter uses rayon.iter.zip, so a change to rayon.iter.zip can break rayon.iter, while a change to rayon.iter can't break rayon.iter.zip.
- Position
- Below the diagonal: rayon.iter uses a module listed above it, which is the healthy direction.
27→23 rayon.iter uses rayon.iter.interleave✕
- Connections
- 1 pair of types, where a type in rayon.iter uses a type in rayon.iter.interleave.
- The types involved
rayon.iter.IndexedParallelIterator→rayon.iter.interleave.Interleave
- Direction
- rayon.iter uses rayon.iter.interleave, so a change to rayon.iter.interleave can break rayon.iter, while a change to rayon.iter can't break rayon.iter.interleave.
- Position
- Below the diagonal: rayon.iter uses a module listed above it, which is the healthy direction.
27→24 rayon.iter uses rayon.iter.intersperse✕
- Connections
- 1 pair of types, where a type in rayon.iter uses a type in rayon.iter.intersperse.
- The types involved
rayon.iter.ParallelIterator→rayon.iter.intersperse.Intersperse
- Direction
- rayon.iter uses rayon.iter.intersperse, so a change to rayon.iter.intersperse can break rayon.iter, while a change to rayon.iter can't break rayon.iter.intersperse.
- Position
- Below the diagonal: rayon.iter uses a module listed above it, which is the healthy direction.
28→1 rayon_demo.tsp.step uses rayon_demo.tsp.weight✕
- Connections
- 1 pair of types, where a type in rayon_demo.tsp.step uses a type in rayon_demo.tsp.weight.
- The types involved
rayon_demo.tsp.step.step$module→rayon_demo.tsp.weight.Weight
- Direction
- rayon_demo.tsp.step uses rayon_demo.tsp.weight, so a change to rayon_demo.tsp.weight can break rayon_demo.tsp.step, while a change to rayon_demo.tsp.step can't break rayon_demo.tsp.weight.
- Position
- Below the diagonal: rayon_demo.tsp.step uses a module listed above it, which is the healthy direction.
28→5 rayon_demo.tsp.step uses rayon_demo.tsp.graph✕
- Connections
- 3 pairs of types, where a type in rayon_demo.tsp.step uses a type in rayon_demo.tsp.graph.
- The types involved
rayon_demo.tsp.step.step$module→rayon_demo.tsp.graph.Graphrayon_demo.tsp.step.step$module→rayon_demo.tsp.graph.Noderayon_demo.tsp.step.step$module→rayon_demo.tsp.graph.NodeSet
- Direction
- rayon_demo.tsp.step uses rayon_demo.tsp.graph, so a change to rayon_demo.tsp.graph can break rayon_demo.tsp.step, while a change to rayon_demo.tsp.step can't break rayon_demo.tsp.graph.
- Position
- Below the diagonal: rayon_demo.tsp.step uses a module listed above it, which is the healthy direction.
28→22 rayon_demo.tsp.step uses rayon_demo.tsp.tour✕
- Connections
- 1 pair of types, where a type in rayon_demo.tsp.step uses a type in rayon_demo.tsp.tour.
- The types involved
rayon_demo.tsp.step.step$module→rayon_demo.tsp.tour.TourPrefix
- Direction
- rayon_demo.tsp.step uses rayon_demo.tsp.tour, so a change to rayon_demo.tsp.tour can break rayon_demo.tsp.step, while a change to rayon_demo.tsp.step can't break rayon_demo.tsp.tour.
- Position
- Below the diagonal: rayon_demo.tsp.step uses a module listed above it, which is the healthy direction.
28→25 rayon_demo.tsp.step uses rayon_core.scope✕
- Connections
- 1 pair of types, where a type in rayon_demo.tsp.step uses a type in rayon_core.scope.
- The types involved
rayon_demo.tsp.step.step$module→rayon_core.scope.Scope
- Direction
- rayon_demo.tsp.step uses rayon_core.scope, so a change to rayon_core.scope can break rayon_demo.tsp.step, while a change to rayon_demo.tsp.step can't break rayon_core.scope.
- Position
- Below the diagonal: rayon_demo.tsp.step uses a module listed above it, which is the healthy direction.
28→26 rayon_demo.tsp.step uses rayon_demo.tsp.solver✕
- Connections
- 1 pair of types, where a type in rayon_demo.tsp.step uses a type in rayon_demo.tsp.solver.
- The types involved
rayon_demo.tsp.step.step$module→rayon_demo.tsp.solver.SolverCx
- Direction
- rayon_demo.tsp.step uses rayon_demo.tsp.solver, so a change to rayon_demo.tsp.solver can break rayon_demo.tsp.step, while a change to rayon_demo.tsp.step can't break rayon_demo.tsp.solver.
- Position
- Below the diagonal: rayon_demo.tsp.step uses a module listed above it, which is the healthy direction.
29→27 rayon.array uses rayon.iter✕
- Connections
- 2 pairs of types, where a type in rayon.array uses a type in rayon.iter.
- The types involved
rayon.array.IntoIter→rayon.iter.IndexedParallelIteratorrayon.array.IntoIter→rayon.iter.ParallelIterator
- Direction
- rayon.array uses rayon.iter, so a change to rayon.iter can break rayon.array, while a change to rayon.array can't break rayon.iter.
- Position
- Below the diagonal: rayon.array uses a module listed above it, which is the healthy direction.
30→2 rayon.iter.par_bridge uses rayon.collections.binary_heap✕
- Connections
- 1 pair of types, where a type in rayon.iter.par_bridge uses a type in rayon.collections.binary_heap.
- The types involved
rayon.iter.par_bridge.IterBridge→rayon.collections.binary_heap.Iter
- Direction
- rayon.iter.par_bridge uses rayon.collections.binary_heap, so a change to rayon.collections.binary_heap can break rayon.iter.par_bridge, while a change to rayon.iter.par_bridge can't break rayon.collections.binary_heap.
- Position
- Below the diagonal: rayon.iter.par_bridge uses a module listed above it, which is the healthy direction.
30→3 rayon.iter.par_bridge uses rayon.iter.plumbing✕
- Connections
- 1 pair of types, where a type in rayon.iter.par_bridge uses a type in rayon.iter.plumbing.
- The types involved
rayon.iter.par_bridge.IterParallelProducer→rayon.iter.plumbing.UnindexedProducer
- Direction
- rayon.iter.par_bridge uses rayon.iter.plumbing, so a change to rayon.iter.plumbing can break rayon.iter.par_bridge, while a change to rayon.iter.par_bridge can't break rayon.iter.plumbing.
- Position
- Below the diagonal: rayon.iter.par_bridge uses a module listed above it, which is the healthy direction.
30→16 rayon.iter.par_bridge uses rayon.iter.panic_fuse✕
- Connections
- 1 pair of types, where a type in rayon.iter.par_bridge uses a type in rayon.iter.panic_fuse.
- The types involved
rayon.iter.par_bridge.IterParallelProducer→rayon.iter.panic_fuse.Fuse
- Direction
- rayon.iter.par_bridge uses rayon.iter.panic_fuse, so a change to rayon.iter.panic_fuse can break rayon.iter.par_bridge, while a change to rayon.iter.par_bridge can't break rayon.iter.panic_fuse.
- Position
- Below the diagonal: rayon.iter.par_bridge uses a module listed above it, which is the healthy direction.
30→27 rayon.iter.par_bridge uses rayon.iter✕
- Connections
- 1 pair of types, where a type in rayon.iter.par_bridge uses a type in rayon.iter.
- The types involved
rayon.iter.par_bridge.IterBridge→rayon.iter.ParallelIterator
- Direction
- rayon.iter.par_bridge uses rayon.iter, so a change to rayon.iter can break rayon.iter.par_bridge, while a change to rayon.iter.par_bridge can't break rayon.iter.
- Position
- Below the diagonal: rayon.iter.par_bridge uses a module listed above it, which is the healthy direction.
31→3 rayon.iter.splitter uses rayon.iter.plumbing✕
- Connections
- 1 pair of types, where a type in rayon.iter.splitter uses a type in rayon.iter.plumbing.
- The types involved
rayon.iter.splitter.SplitProducer→rayon.iter.plumbing.UnindexedProducer
- Direction
- rayon.iter.splitter uses rayon.iter.plumbing, so a change to rayon.iter.plumbing can break rayon.iter.splitter, while a change to rayon.iter.splitter can't break rayon.iter.plumbing.
- Position
- Below the diagonal: rayon.iter.splitter uses a module listed above it, which is the healthy direction.
31→27 rayon.iter.splitter uses rayon.iter✕
- Connections
- 1 pair of types, where a type in rayon.iter.splitter uses a type in rayon.iter.
- The types involved
rayon.iter.splitter.Split→rayon.iter.ParallelIterator
- Direction
- rayon.iter.splitter uses rayon.iter, so a change to rayon.iter can break rayon.iter.splitter, while a change to rayon.iter.splitter can't break rayon.iter.
- Position
- Below the diagonal: rayon.iter.splitter uses a module listed above it, which is the healthy direction.
32→7 rayon.collections.vec_deque uses rayon.iter.chain✕
- Connections
- 2 pairs of types, where a type in rayon.collections.vec_deque uses a type in rayon.iter.chain.
- The types involved
rayon.collections.vec_deque.Iter→rayon.iter.chain.Chainrayon.collections.vec_deque.IterMut→rayon.iter.chain.Chain
- Direction
- rayon.collections.vec_deque uses rayon.iter.chain, so a change to rayon.iter.chain can break rayon.collections.vec_deque, while a change to rayon.collections.vec_deque can't break rayon.iter.chain.
- Position
- Below the diagonal: rayon.collections.vec_deque uses a module listed above it, which is the healthy direction.
32→27 rayon.collections.vec_deque uses rayon.iter✕
- Connections
- 2 pairs of types, where a type in rayon.collections.vec_deque uses a type in rayon.iter.
- The types involved
rayon.collections.vec_deque.Drain→rayon.iter.IndexedParallelIteratorrayon.collections.vec_deque.Drain→rayon.iter.ParallelIterator
- Direction
- rayon.collections.vec_deque uses rayon.iter, so a change to rayon.iter can break rayon.collections.vec_deque, while a change to rayon.collections.vec_deque can't break rayon.iter.
- Position
- Below the diagonal: rayon.collections.vec_deque uses a module listed above it, which is the healthy direction.
32→29 rayon.collections.vec_deque uses rayon.array✕
- Connections
- 1 pair of types, where a type in rayon.collections.vec_deque uses a type in rayon.array.
- The types involved
rayon.collections.vec_deque.IntoIter→rayon.array.IntoIter
- Direction
- rayon.collections.vec_deque uses rayon.array, so a change to rayon.array can break rayon.collections.vec_deque, while a change to rayon.collections.vec_deque can't break rayon.array.
- Position
- Below the diagonal: rayon.collections.vec_deque uses a module listed above it, which is the healthy direction.
33→3 rayon.iter.repeat uses rayon.iter.plumbing✕
- Connections
- 2 pairs of types, where a type in rayon.iter.repeat uses a type in rayon.iter.plumbing.
- The types involved
rayon.iter.repeat.RepeatNProducer→rayon.iter.plumbing.Producerrayon.iter.repeat.RepeatProducer→rayon.iter.plumbing.UnindexedProducer
- Direction
- rayon.iter.repeat uses rayon.iter.plumbing, so a change to rayon.iter.plumbing can break rayon.iter.repeat, while a change to rayon.iter.repeat can't break rayon.iter.plumbing.
- Position
- Below the diagonal: rayon.iter.repeat uses a module listed above it, which is the healthy direction.
33→20 rayon.iter.repeat uses rayon.iter.zip✕
- Connections
- 1 pair of types, where a type in rayon.iter.repeat uses a type in rayon.iter.zip.
- The types involved
rayon.iter.repeat.Repeat→rayon.iter.zip.Zip
- Direction
- rayon.iter.repeat uses rayon.iter.zip, so a change to rayon.iter.zip can break rayon.iter.repeat, while a change to rayon.iter.repeat can't break rayon.iter.zip.
- Position
- Below the diagonal: rayon.iter.repeat uses a module listed above it, which is the healthy direction.
33→27 rayon.iter.repeat uses rayon.iter✕
- Connections
- 3 pairs of types, where a type in rayon.iter.repeat uses a type in rayon.iter.
- The types involved
rayon.iter.repeat.Repeat→rayon.iter.ParallelIteratorrayon.iter.repeat.RepeatN→rayon.iter.IndexedParallelIteratorrayon.iter.repeat.RepeatN→rayon.iter.ParallelIterator
- Direction
- rayon.iter.repeat uses rayon.iter, so a change to rayon.iter can break rayon.iter.repeat, while a change to rayon.iter.repeat can't break rayon.iter.
- Position
- Below the diagonal: rayon.iter.repeat uses a module listed above it, which is the healthy direction.
33→29 rayon.iter.repeat uses rayon.array✕
- Connections
- 1 pair of types, where a type in rayon.iter.repeat uses a type in rayon.array.
- The types involved
rayon.iter.repeat.RepeatNProducer→rayon.array.IntoIter
- Direction
- rayon.iter.repeat uses rayon.array, so a change to rayon.array can break rayon.iter.repeat, while a change to rayon.iter.repeat can't break rayon.array.
- Position
- Below the diagonal: rayon.iter.repeat uses a module listed above it, which is the healthy direction.
34→2 rayon.range uses rayon.collections.binary_heap✕
- Connections
- 2 pairs of types, where a type in rayon.range uses a type in rayon.collections.binary_heap.
- The types involved
rayon.range.IndexedRangeInteger→rayon.collections.binary_heap.Iterrayon.range.RangeInteger→rayon.collections.binary_heap.Iter
- Direction
- rayon.range uses rayon.collections.binary_heap, so a change to rayon.collections.binary_heap can break rayon.range, while a change to rayon.range can't break rayon.collections.binary_heap.
- Position
- Below the diagonal: rayon.range uses a module listed above it, which is the healthy direction.
34→3 rayon.range uses rayon.iter.plumbing✕
- Connections
- 2 pairs of types, where a type in rayon.range uses a type in rayon.iter.plumbing.
- The types involved
rayon.range.IterProducer→rayon.iter.plumbing.Producerrayon.range.IterProducer→rayon.iter.plumbing.UnindexedProducer
- Direction
- rayon.range uses rayon.iter.plumbing, so a change to rayon.iter.plumbing can break rayon.range, while a change to rayon.range can't break rayon.iter.plumbing.
- Position
- Below the diagonal: rayon.range uses a module listed above it, which is the healthy direction.
34→27 rayon.range uses rayon.iter✕
- Connections
- 2 pairs of types, where a type in rayon.range uses a type in rayon.iter.
- The types involved
rayon.range.Iter→rayon.iter.IndexedParallelIteratorrayon.range.Iter→rayon.iter.ParallelIterator
- Direction
- rayon.range uses rayon.iter, so a change to rayon.iter can break rayon.range, while a change to rayon.range can't break rayon.iter.
- Position
- Below the diagonal: rayon.range uses a module listed above it, which is the healthy direction.
34→29 rayon.range uses rayon.array✕
- Connections
- 1 pair of types, where a type in rayon.range uses a type in rayon.array.
- The types involved
rayon.range.IterProducer→rayon.array.IntoIter
- Direction
- rayon.range uses rayon.array, so a change to rayon.array can break rayon.range, while a change to rayon.range can't break rayon.array.
- Position
- Below the diagonal: rayon.range uses a module listed above it, which is the healthy direction.
35→3 rayon.slice.chunks uses rayon.iter.plumbing✕
- Connections
- 4 pairs of types, where a type in rayon.slice.chunks uses a type in rayon.iter.plumbing.
- The types involved
rayon.slice.chunks.ChunksExactMutProducer→rayon.iter.plumbing.Producerrayon.slice.chunks.ChunksExactProducer→rayon.iter.plumbing.Producerrayon.slice.chunks.ChunksMutProducer→rayon.iter.plumbing.Producerrayon.slice.chunks.ChunksProducer→rayon.iter.plumbing.Producer
- Direction
- rayon.slice.chunks uses rayon.iter.plumbing, so a change to rayon.iter.plumbing can break rayon.slice.chunks, while a change to rayon.slice.chunks can't break rayon.iter.plumbing.
- Position
- Below the diagonal: rayon.slice.chunks uses a module listed above it, which is the healthy direction.
35→27 rayon.slice.chunks uses rayon.iter✕
- Connections
- 8 pairs of types, where a type in rayon.slice.chunks uses a type in rayon.iter.
- The types involved
rayon.slice.chunks.Chunks→rayon.iter.IndexedParallelIteratorrayon.slice.chunks.Chunks→rayon.iter.ParallelIteratorrayon.slice.chunks.ChunksExact→rayon.iter.IndexedParallelIteratorrayon.slice.chunks.ChunksExact→rayon.iter.ParallelIteratorrayon.slice.chunks.ChunksExactMut→rayon.iter.IndexedParallelIteratorrayon.slice.chunks.ChunksExactMut→rayon.iter.ParallelIteratorrayon.slice.chunks.ChunksMut→rayon.iter.IndexedParallelIteratorrayon.slice.chunks.ChunksMut→rayon.iter.ParallelIterator
- Direction
- rayon.slice.chunks uses rayon.iter, so a change to rayon.iter can break rayon.slice.chunks, while a change to rayon.slice.chunks can't break rayon.iter.
- Position
- Below the diagonal: rayon.slice.chunks uses a module listed above it, which is the healthy direction.
35→29 rayon.slice.chunks uses rayon.array✕
- Connections
- 4 pairs of types, where a type in rayon.slice.chunks uses a type in rayon.array.
- The types involved
rayon.slice.chunks.ChunksExactMutProducer→rayon.array.IntoIterrayon.slice.chunks.ChunksExactProducer→rayon.array.IntoIterrayon.slice.chunks.ChunksMutProducer→rayon.array.IntoIterrayon.slice.chunks.ChunksProducer→rayon.array.IntoIter
- Direction
- rayon.slice.chunks uses rayon.array, so a change to rayon.array can break rayon.slice.chunks, while a change to rayon.slice.chunks can't break rayon.array.
- Position
- Below the diagonal: rayon.slice.chunks uses a module listed above it, which is the healthy direction.
36→3 rayon.slice.rchunks uses rayon.iter.plumbing✕
- Connections
- 4 pairs of types, where a type in rayon.slice.rchunks uses a type in rayon.iter.plumbing.
- The types involved
rayon.slice.rchunks.RChunksExactMutProducer→rayon.iter.plumbing.Producerrayon.slice.rchunks.RChunksExactProducer→rayon.iter.plumbing.Producerrayon.slice.rchunks.RChunksMutProducer→rayon.iter.plumbing.Producerrayon.slice.rchunks.RChunksProducer→rayon.iter.plumbing.Producer
- Direction
- rayon.slice.rchunks uses rayon.iter.plumbing, so a change to rayon.iter.plumbing can break rayon.slice.rchunks, while a change to rayon.slice.rchunks can't break rayon.iter.plumbing.
- Position
- Below the diagonal: rayon.slice.rchunks uses a module listed above it, which is the healthy direction.
36→27 rayon.slice.rchunks uses rayon.iter✕
- Connections
- 8 pairs of types, where a type in rayon.slice.rchunks uses a type in rayon.iter.
- The types involved
rayon.slice.rchunks.RChunks→rayon.iter.IndexedParallelIteratorrayon.slice.rchunks.RChunks→rayon.iter.ParallelIteratorrayon.slice.rchunks.RChunksExact→rayon.iter.IndexedParallelIteratorrayon.slice.rchunks.RChunksExact→rayon.iter.ParallelIteratorrayon.slice.rchunks.RChunksExactMut→rayon.iter.IndexedParallelIteratorrayon.slice.rchunks.RChunksExactMut→rayon.iter.ParallelIteratorrayon.slice.rchunks.RChunksMut→rayon.iter.IndexedParallelIteratorrayon.slice.rchunks.RChunksMut→rayon.iter.ParallelIterator
- Direction
- rayon.slice.rchunks uses rayon.iter, so a change to rayon.iter can break rayon.slice.rchunks, while a change to rayon.slice.rchunks can't break rayon.iter.
- Position
- Below the diagonal: rayon.slice.rchunks uses a module listed above it, which is the healthy direction.
36→29 rayon.slice.rchunks uses rayon.array✕
- Connections
- 4 pairs of types, where a type in rayon.slice.rchunks uses a type in rayon.array.
- The types involved
rayon.slice.rchunks.RChunksExactMutProducer→rayon.array.IntoIterrayon.slice.rchunks.RChunksExactProducer→rayon.array.IntoIterrayon.slice.rchunks.RChunksMutProducer→rayon.array.IntoIterrayon.slice.rchunks.RChunksProducer→rayon.array.IntoIter
- Direction
- rayon.slice.rchunks uses rayon.array, so a change to rayon.array can break rayon.slice.rchunks, while a change to rayon.slice.rchunks can't break rayon.array.
- Position
- Below the diagonal: rayon.slice.rchunks uses a module listed above it, which is the healthy direction.
37→3 rayon.slice.windows uses rayon.iter.plumbing✕
- Connections
- 1 pair of types, where a type in rayon.slice.windows uses a type in rayon.iter.plumbing.
- The types involved
rayon.slice.windows.WindowsProducer→rayon.iter.plumbing.Producer
- Direction
- rayon.slice.windows uses rayon.iter.plumbing, so a change to rayon.iter.plumbing can break rayon.slice.windows, while a change to rayon.slice.windows can't break rayon.iter.plumbing.
- Position
- Below the diagonal: rayon.slice.windows uses a module listed above it, which is the healthy direction.
37→27 rayon.slice.windows uses rayon.iter✕
- Connections
- 4 pairs of types, where a type in rayon.slice.windows uses a type in rayon.iter.
- The types involved
rayon.slice.windows.ArrayWindows→rayon.iter.IndexedParallelIteratorrayon.slice.windows.ArrayWindows→rayon.iter.ParallelIteratorrayon.slice.windows.Windows→rayon.iter.IndexedParallelIteratorrayon.slice.windows.Windows→rayon.iter.ParallelIterator
- Direction
- rayon.slice.windows uses rayon.iter, so a change to rayon.iter can break rayon.slice.windows, while a change to rayon.slice.windows can't break rayon.iter.
- Position
- Below the diagonal: rayon.slice.windows uses a module listed above it, which is the healthy direction.
37→29 rayon.slice.windows uses rayon.array✕
- Connections
- 1 pair of types, where a type in rayon.slice.windows uses a type in rayon.array.
- The types involved
rayon.slice.windows.WindowsProducer→rayon.array.IntoIter
- Direction
- rayon.slice.windows uses rayon.array, so a change to rayon.array can break rayon.slice.windows, while a change to rayon.slice.windows can't break rayon.array.
- Position
- Below the diagonal: rayon.slice.windows uses a module listed above it, which is the healthy direction.
38→3 rayon.vec uses rayon.iter.plumbing✕
- Connections
- 1 pair of types, where a type in rayon.vec uses a type in rayon.iter.plumbing.
- The types involved
rayon.vec.DrainProducer→rayon.iter.plumbing.Producer
- Direction
- rayon.vec uses rayon.iter.plumbing, so a change to rayon.iter.plumbing can break rayon.vec, while a change to rayon.vec can't break rayon.iter.plumbing.
- Position
- Below the diagonal: rayon.vec uses a module listed above it, which is the healthy direction.
38→27 rayon.vec uses rayon.iter✕
- Connections
- 4 pairs of types, where a type in rayon.vec uses a type in rayon.iter.
- The types involved
rayon.vec.Drain→rayon.iter.IndexedParallelIteratorrayon.vec.Drain→rayon.iter.ParallelIteratorrayon.vec.IntoIter→rayon.iter.IndexedParallelIteratorrayon.vec.IntoIter→rayon.iter.ParallelIterator
- Direction
- rayon.vec uses rayon.iter, so a change to rayon.iter can break rayon.vec, while a change to rayon.vec can't break rayon.iter.
- Position
- Below the diagonal: rayon.vec uses a module listed above it, which is the healthy direction.
38→29 rayon.vec uses rayon.array✕
- Connections
- 1 pair of types, where a type in rayon.vec uses a type in rayon.array.
- The types involved
rayon.vec.DrainProducer→rayon.array.IntoIter
- Direction
- rayon.vec uses rayon.array, so a change to rayon.array can break rayon.vec, while a change to rayon.vec can't break rayon.array.
- Position
- Below the diagonal: rayon.vec uses a module listed above it, which is the healthy direction.
39→3 rayon.slice uses rayon.iter.plumbing✕
- Connections
- 2 pairs of types, where a type in rayon.slice uses a type in rayon.iter.plumbing.
- The types involved
rayon.slice.IterMutProducer→rayon.iter.plumbing.Producerrayon.slice.IterProducer→rayon.iter.plumbing.Producer
- Direction
- rayon.slice uses rayon.iter.plumbing, so a change to rayon.iter.plumbing can break rayon.slice, while a change to rayon.slice can't break rayon.iter.plumbing.
- Position
- Below the diagonal: rayon.slice uses a module listed above it, which is the healthy direction.
39→8 rayon.slice uses rayon.iter.chunks✕
- Connections
- 1 pair of types, where a type in rayon.slice uses a type in rayon.iter.chunks.
- The types involved
rayon.slice.ParallelSlice→rayon.iter.chunks.Chunks
- Direction
- rayon.slice uses rayon.iter.chunks, so a change to rayon.iter.chunks can break rayon.slice, while a change to rayon.slice can't break rayon.iter.chunks.
- Position
- Below the diagonal: rayon.slice uses a module listed above it, which is the healthy direction.
39→27 rayon.slice uses rayon.iter✕
- Connections
- 8 pairs of types, where a type in rayon.slice uses a type in rayon.iter.
- The types involved
rayon.slice.Iter→rayon.iter.IndexedParallelIteratorrayon.slice.Iter→rayon.iter.ParallelIteratorrayon.slice.IterMut→rayon.iter.IndexedParallelIteratorrayon.slice.IterMut→rayon.iter.ParallelIteratorrayon.slice.Split→rayon.iter.ParallelIteratorrayon.slice.SplitInclusive→rayon.iter.ParallelIteratorrayon.slice.SplitInclusiveMut→rayon.iter.ParallelIteratorrayon.slice.SplitMut→rayon.iter.ParallelIterator
- Direction
- rayon.slice uses rayon.iter, so a change to rayon.iter can break rayon.slice, while a change to rayon.slice can't break rayon.iter.
- Position
- Below the diagonal: rayon.slice uses a module listed above it, which is the healthy direction.
39→29 rayon.slice uses rayon.array✕
- Connections
- 2 pairs of types, where a type in rayon.slice uses a type in rayon.array.
- The types involved
rayon.slice.IterMutProducer→rayon.array.IntoIterrayon.slice.IterProducer→rayon.array.IntoIter
- Direction
- rayon.slice uses rayon.array, so a change to rayon.array can break rayon.slice, while a change to rayon.slice can't break rayon.array.
- Position
- Below the diagonal: rayon.slice uses a module listed above it, which is the healthy direction.
39→31 rayon.slice uses rayon.iter.splitter✕
- Connections
- 1 pair of types, where a type in rayon.slice uses a type in rayon.iter.splitter.
- The types involved
rayon.slice.ParallelSlice→rayon.iter.splitter.Split
- Direction
- rayon.slice uses rayon.iter.splitter, so a change to rayon.iter.splitter can break rayon.slice, while a change to rayon.slice can't break rayon.iter.splitter.
- Position
- Below the diagonal: rayon.slice uses a module listed above it, which is the healthy direction.
39→35 rayon.slice uses rayon.slice.chunks✕
- Connections
- 3 pairs of types, where a type in rayon.slice uses a type in rayon.slice.chunks.
- The types involved
rayon.slice.ParallelSlice→rayon.slice.chunks.ChunksExactrayon.slice.ParallelSliceMut→rayon.slice.chunks.ChunksExactMutrayon.slice.ParallelSliceMut→rayon.slice.chunks.ChunksMut
- Direction
- rayon.slice uses rayon.slice.chunks, so a change to rayon.slice.chunks can break rayon.slice, while a change to rayon.slice can't break rayon.slice.chunks.
- Position
- Below the diagonal: rayon.slice uses a module listed above it, which is the healthy direction.
39→36 rayon.slice uses rayon.slice.rchunks✕
- Connections
- 4 pairs of types, where a type in rayon.slice uses a type in rayon.slice.rchunks.
- The types involved
rayon.slice.ParallelSlice→rayon.slice.rchunks.RChunksrayon.slice.ParallelSlice→rayon.slice.rchunks.RChunksExactrayon.slice.ParallelSliceMut→rayon.slice.rchunks.RChunksExactMutrayon.slice.ParallelSliceMut→rayon.slice.rchunks.RChunksMut
- Direction
- rayon.slice uses rayon.slice.rchunks, so a change to rayon.slice.rchunks can break rayon.slice, while a change to rayon.slice can't break rayon.slice.rchunks.
- Position
- Below the diagonal: rayon.slice uses a module listed above it, which is the healthy direction.
39→37 rayon.slice uses rayon.slice.windows✕
- Connections
- 2 pairs of types, where a type in rayon.slice uses a type in rayon.slice.windows.
- The types involved
rayon.slice.ParallelSlice→rayon.slice.windows.ArrayWindowsrayon.slice.ParallelSlice→rayon.slice.windows.Windows
- Direction
- rayon.slice uses rayon.slice.windows, so a change to rayon.slice.windows can break rayon.slice, while a change to rayon.slice can't break rayon.slice.windows.
- Position
- Below the diagonal: rayon.slice uses a module listed above it, which is the healthy direction.
40→3 rayon.str uses rayon.iter.plumbing✕
- Connections
- 7 pairs of types, where a type in rayon.str uses a type in rayon.iter.plumbing.
- The types involved
rayon.str.BytesProducer→rayon.iter.plumbing.UnindexedProducerrayon.str.CharIndicesProducer→rayon.iter.plumbing.UnindexedProducerrayon.str.CharsProducer→rayon.iter.plumbing.UnindexedProducerrayon.str.EncodeUtf16Producer→rayon.iter.plumbing.UnindexedProducerrayon.str.MatchIndicesProducer→rayon.iter.plumbing.UnindexedProducerrayon.str.MatchesProducer→rayon.iter.plumbing.UnindexedProducerrayon.str.SplitTerminatorProducer→rayon.iter.plumbing.UnindexedProducer
- Direction
- rayon.str uses rayon.iter.plumbing, so a change to rayon.iter.plumbing can break rayon.str, while a change to rayon.str can't break rayon.iter.plumbing.
- Position
- Below the diagonal: rayon.str uses a module listed above it, which is the healthy direction.
40→27 rayon.str uses rayon.iter✕
- Connections
- 12 pairs of types, where a type in rayon.str uses a type in rayon.iter.
- The types involved
rayon.str.Bytes→rayon.iter.ParallelIteratorrayon.str.CharIndices→rayon.iter.ParallelIteratorrayon.str.Chars→rayon.iter.ParallelIteratorrayon.str.EncodeUtf16→rayon.iter.ParallelIteratorrayon.str.Lines→rayon.iter.ParallelIteratorrayon.str.MatchIndices→rayon.iter.ParallelIteratorrayon.str.Matches→rayon.iter.ParallelIteratorrayon.str.Split→rayon.iter.ParallelIteratorrayon.str.SplitAsciiWhitespace→rayon.iter.ParallelIteratorrayon.str.SplitInclusive→rayon.iter.ParallelIteratorrayon.str.SplitTerminator→rayon.iter.ParallelIteratorrayon.str.SplitWhitespace→rayon.iter.ParallelIterator
- Direction
- rayon.str uses rayon.iter, so a change to rayon.iter can break rayon.str, while a change to rayon.str can't break rayon.iter.
- Position
- Below the diagonal: rayon.str uses a module listed above it, which is the healthy direction.
40→31 rayon.str uses rayon.iter.splitter✕
- Connections
- 2 pairs of types, where a type in rayon.str uses a type in rayon.iter.splitter.
- The types involved
rayon.str.ParallelString→rayon.iter.splitter.Splitrayon.str.SplitTerminatorProducer→rayon.iter.splitter.SplitProducer
- Direction
- rayon.str uses rayon.iter.splitter, so a change to rayon.iter.splitter can break rayon.str, while a change to rayon.str can't break rayon.iter.splitter.
- Position
- Below the diagonal: rayon.str uses a module listed above it, which is the healthy direction.
40→39 rayon.str uses rayon.slice✕
- Connections
- 1 pair of types, where a type in rayon.str uses a type in rayon.slice.
- The types involved
rayon.str.ParallelString→rayon.slice.SplitInclusive
- Direction
- rayon.str uses rayon.slice, so a change to rayon.slice can break rayon.str, while a change to rayon.str can't break rayon.slice.
- Position
- Below the diagonal: rayon.str uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 24 | High / Critical |
Roadmap
Begin by documenting significant design decisions in a dedicated folder to establish a clear architectural record. Enhance observability by implementing verbose logging in error paths to ensure users can provide actionable diagnostic trails. Strengthen security by integrating static analysis into the CI pipeline to prevent regressions, and clarify the testing process in the README. Finally, address the single off-boarding risk to improve team resilience.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +6.5 pts | Medium | Architecture documentation |
| Resolve the 1 Off-boarding risk finding(s) in Bus Factor. | +3.1 pts | Low | Bus Factor |
| Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce. | +5.8 pts | Medium | Observability |
| Add a SAST step to CI running what this repository's stack ships: cargo-audit / cargo-deny (or clippy) — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing. | +3.7 pts | Medium | Security & performance tooling |
| 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. | +3.1 pts | Medium | Documentation (README) |
| Resolve the 11 Orphaned file finding(s) in Knowledge Freshness — start with mod.rs (4), nbody.rs, test.rs. | +1.1 pts | Medium | Knowledge Freshness |
| Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. | +0.4 pts | Low | Static Analysis (SAST) |
| Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. | +0.4 pts | Low | Static Analysis (SAST) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.4 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| src/slice/sort.rs | 6.0 | Mixed | Explicit Debt: FixmeComment |
| rayon-demo/src/nbody/nbody.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/iter/multizip.rs | 7.2 | Mixed | Code Duplication: Members sharing a duplicated core (7 members, 50+ identical tokens) |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| src/iter/skip_any.rs | 7.4 | Mixed | Code Duplication: Duplicated block (5 lines × 2) |
| src/iter/fold.rs | 7.4 | Mixed | Code Duplication: Duplicated block (11 lines × 7) |
| src/iter/len.rs | 7.8 | Mixed | Code Duplication: Members sharing a duplicated core (7 members, 50+ identical tokens) |
| src/iter/rev.rs | 7.8 | Mixed | Code Duplication: Duplicated block (12–14 lines × 2) |
| src/iter/mod.rs | 7.8 | Mixed | Code Duplication: Duplicated block (5 lines × 2) |
| src/iter/skip_any_while.rs | 7.8 | Mixed | Code Duplication: Duplicated block (10 lines × 2) |
| src/iter/cloned.rs | 7.8 | Mixed | Code Duplication: Duplicated block (7 lines × 2) |
| rayon-demo/src/mergesort/mod.rs | 7.8 | Mixed | Code Duplication: Duplicated block (9 lines × 2) |
| src/compile_fail/must_use.rs | 8.0 | Near-clean | Change Coupling: Boundary-crossing change coupling: must_use.rs ↔ mod.rs |
| tests/octillion.rs | 8.2 | Near-clean | Explicit Debt: FixmeComment |
| src/str.rs | 8.2 | Near-clean | Explicit Debt: TodoComment |
| src/slice/windows.rs | 8.2 | Near-clean | Explicit Debt: TodoComment |
| src/iter/test.rs | 8.2 | Near-clean | Explicit Debt: FixmeComment |
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. 41 of 41 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.8 — 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 — 41 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, 89 of 97 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.
- D11 Test Reliability — 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. Test source is present (.rs) and this repository declares a Cargo test suite (repository root, 42 test files), but it was not re-run: no test result was produced. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- 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.
- 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.
- 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.
- 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
1 function(s) exceeded the cyclomatic complexity threshold of 15; the worst was rayon::slice::sort::partition_in_blocks at 20.
What to do
- Bring the 1 body over 15 down to 15 or less in Cyclomatic Complexity — start with rayon::slice::sort::partition_in_blocks (cyclomatic 20). — Refactoring it lifts Cyclomatic Complexity from 9.6 to about 10.0/10.
- 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
5 function(s) exceeded the cognitive complexity threshold of 15; the worst was rayon::slice::sort::partition_in_blocks at 38.
What to do
- Bring the 5 bodies over 15 down to 15 or less in Cognitive Complexity — start with rayon::slice::sort::partition_in_blocks (cognitive 38), rayon::slice::sort::recurse (cognitive 28), rayon::slice::sort::merge_sort (cognitive 22). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 5 together lifts Cognitive Complexity from 8.6 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
1 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 1 FileTooLong finding(s) in God Classes — start with sort.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
31 duplicated block group(s) detected. A further 3 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted. 9 of the 34 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
What to do
- Resolve the 4 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with skip_any.rs (2), mod.rs, cloned.rs. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 4 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with mod.rs (3), skip_any.rs. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 3 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with flat_map.rs, skip_any_while.rs, nbody.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
4 production modules (Cargo), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 1 module(s) off the main sequence, with abstractness counted on 2 of the 4 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
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 139 classes have LCOM4 above 3.
D9 · Test Distribution
451 test methods: 325 unit, 126 integration, 0 BDD, 0 e2e. The Rust suite contributes 451 `#[test]` function(s) across 42 file(s) declaring at least one; its unit/integration split is Cargo's own — 23 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.
D12 · Dependency Hygiene
0 outdated, 0 yanked direct Cargo dependencies. Only DIRECT edges are graded: a transitive crate cannot be moved past what its parent's requirement admits, so reporting one would be advice its owner cannot take. A newer release is reported only where this repository's OWN requirement already admits it, so the remedy is `cargo update` and never a manifest edit — which means a release outside the declared range is deliberately NOT charged, because a written-down constraint is a decision rather than a defect. Note that a bare requirement is a CARET, and for a 0.x crate its ceiling is the minor. Whether any crate is UNMAINTAINED is not graded — crates.io publishes no maintenance status, and release age does not stand in for one. Known CVEs in this dependency graph are D30's question, read from Cargo.lock there.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 219 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository commits no Cargo.lock, so its graph was resolved here: its manifests' `[dependencies]` and `[build-dependencies]` closed over the crates.io index, each crate at the newest release its requirement admits (what a fresh `cargo generate-lockfile` picks, not a graph the repository has pinned). Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository. This repository publishes itself under MIT 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
35 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is src/slice/sort.rs. Counted over 108 of the 163 production source files in this repository: 53 are under the ~2,400-byte size floor this dimension measures over, and the remaining 2 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
8 deducted task-comment markers across 34818 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 4 FixmeComment finding(s) in Explicit Debt — start with sort.rs (2), octillion.rs, test.rs. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 4 TodoComment finding(s) in Explicit Debt — start with str.rs, windows.rs, nbody.rs. — One of this dimension's main actionable groups (4 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. 6 document(s) read across 1 unit(s).
D26 · Project Cohesion
1 of 4 build units (Cargo) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
24 finding(s): 0 critical, 24 high, 0 medium, 0 low. 22 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 1 file(s) — `rayon-core/src/lib.rs` (line 468, line 478) — 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.
What to do
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 22 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (22 issue-level, 0 of them charged here).
D34 · Knowledge Freshness
11 of 110 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is rayon-demo/src/nbody/nbody.rs. Counted over 110 of the 163 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
Strongest change-coupling: must_use.rs↔mod.rs 70%; mod.rs↔mod.rs 50%
What to do
- Resolve the 1 Boundary-crossing change coupling finding(s) in Change Coupling — start with must_use.rs. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Change coupling finding(s) in Change Coupling — start with mod.rs. — One of this dimension's main actionable groups (1 warning-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)
- 54 code files changed in the last 6 months but the README was not touched — it may no longer reflect the system.
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Add a README to the 3 of 4 project(s) that lack one — worth up to 1.5 pts.
- Review the README against recent changes; refresh the parts that drifted.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
- No logging or diagnostics emission found. This repository ships a binary its users launch rather than a service you operate, so there is no operator to page — but when a run fails on a user's machine, neither they nor you have anything to read.
What to do
- Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add cargo-audit / cargo-deny (or clippy) (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 6474 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
What to do
- Add a SAST step to CI running what this repository's stack ships: cargo-audit / cargo-deny (or clippy) — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- 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 | 97% | Exemplary | Strongest area. |
| Architecture | 93% | Exemplary | Solid. |
| Maturity | 56% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 58% | Adequate — gated by P2, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 90% | Exemplary | Solid. |
| Performance | 85% | Strong | Solid. |
Unscored — 1 check(s) recorded observations but carry no score
- D36 Supply-chain Provenance & Signing — 3 observation(s) recorded · The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
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 — 75 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one.
- AX2 Stateful singletons — Not applicable: Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no data at rest for these controls to protect.
- C2 Access Controls — No access-control surface detected in the analyzed source — this repository starts no server another machine can reach (no actix-web HttpServer, axum::serve, Rocket launch, warp::serve, poem or salvo Server, tonic Server::builder, hyper or tiny_http server outside examples and tests, none bound beyond loopback). Access control is therefore N/A here — a crate is authorized by the application that serves it, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~1918 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.
- D11 Test Reliability — Test reliability not included — the .rs suite was found but not re-run
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — Naming consistency is measured on C# only; Rust not measured.
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed Rust surface was not measured.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ projects each declaring an entity of their own. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C# and Visual Basic comments only — this repository's production source is .rs, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.rs), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Cargo manifest — not scanned yet).
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Cargo manifest — not scanned yet).
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (21 value object(s))
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- M4 Documentation accuracy — Not applicable: the 6 current-state document(s) make no claim of a kind M4 checks.
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the Rust source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- 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: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
- S1 Web-Security Posture — No web surface: 115 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.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X12 Unreachable branch — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X13 Undrained process stream — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X16 Unfloored truncation loop — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X17 Uncapped recursion over a caller-supplied document — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X18 Disposal-pattern correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X19 Unrestored process-global state — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X2 Cancellation propagation — no C# was loaded; this repository's Rust was read, and no request in it can be cancelled by a caller — a Rust request takes no token: a future is cancelled by dropping it, from outside the call (select!, a timeout, an aborted task), and reqwest, hyper and tonic take none
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X22 Contradicted release guard — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X23 Unguarded diagnostic materialisation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X24 Document value interpolated into markup unescaped — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X25 Inert configuration knob — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. Rust's compiler refuses the unsynchronised version: a collection shared between a callback's thread and the waiting body must be `Sync`, which a `Vec`, `VecDeque` or `HashMap` is only behind a `Mutex`/`RwLock`, so the race this check looks for cannot be written in safe Rust. Not a gap in the analyzer and not a finding about your code.
- X3 Exception handling — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Rust was read, and it logs through none: the `log` crate's macros take one finished message (as log4net does in C#; its `kv` values are an opt-in its backends mostly drop), `println!`/`eprintln!` are not loggers, or it makes no log call outside its tests and examples at all. Calls through `tracing` (`tracing::info!`, or `info!` imported from it) would be judged.
- X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 25 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Boundary-crossing change coupling: must_use.rs ↔ mod.rs src/compile_fail/must_use.rs:1
Serious — 56 finding(s)
- rayon::slice::sort::partition_in_blocks (cognitive 38) src/slice/sort.rs:317
- rayon::slice::sort::recurse (cognitive 28) src/slice/sort.rs:829
- rayon::slice::sort::merge_sort (cognitive 22) src/slice/sort.rs:1100
- rayon::slice::sort::par_mergesort (cognitive 21) src/slice/sort.rs:1514
- rayon::slice::sort::merge (cognitive 16) src/slice/sort.rs:956
- FixmeComment tests/octillion.rs:61
- FixmeComment src/slice/sort.rs:352
- FixmeComment src/slice/sort.rs:358
- FixmeComment src/iter/test.rs:909
- TodoComment src/str.rs:35
- TodoComment src/slice/windows.rs:142
- TodoComment rayon-demo/src/nbody/nbody.rs:240
- TodoComment rayon-demo/src/matmul/mod.rs:24
- Duplicated block (7 lines × 2) rayon-core/src/scope/mod.rs:570
- Duplicated block (7 lines × 2) src/iter/cloned.rs:114
- Duplicated block (7 lines × 2) src/iter/skip_any.rs:31
- Duplicated block (7 lines × 2) src/iter/skip_any.rs:125
- Duplicated block (5 lines × 2) src/iter/mod.rs:1478
- Duplicated block (5 lines × 2) src/iter/mod.rs:1514
- Duplicated block (5 lines × 2) src/iter/skip_any.rs:103
- Duplicated block (5 lines × 2) rayon-demo/src/mergesort/mod.rs:243
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (10 lines × 2) src/iter/flat_map.rs:124
- Duplicated block (10 lines × 2) src/iter/skip_any_while.rs:118
- Duplicated block (10 lines × 2) rayon-demo/src/nbody/nbody.rs:94
- Duplicated block (8 lines × 2) src/iter/fold.rs:216
- Duplicated block (8 lines × 2) src/iter/intersperse.rs:190
- Duplicated block (8 lines × 2) src/iter/skip_any_while.rs:42
- Members sharing a duplicated core (7 members, 50+ identical tokens) src/iter/len.rs:54
- Members sharing a duplicated core (7 members, 50+ identical tokens) src/iter/multizip.rs:221
- Duplicated block (6 lines × 7) src/iter/multizip.rs:258
- Duplicated block (6 lines × 7) src/iter/multizip.rs:258
- rayon::slice::sort::partition_in_blocks (cyclomatic 20) src/slice/sort.rs:317
- FileTooLong: slice/sort.rs src/slice/sort.rs
- Change coupling: mod.rs ↔ mod.rs rayon-core/src/broadcast/mod.rs:1
- Duplicated block (12–14 lines × 2) src/iter/rev.rs:58
- Duplicated block (7–12 lines × 6) src/iter/multizip.rs:266
- Duplicated block (10 lines × 3) src/iter/rev.rs:60
- Duplicated block (9 lines × 7) src/iter/len.rs:65
- Duplicated block (8 lines × 4) src/iter/cloned.rs:152
- Duplicated block (8 lines × 7) src/iter/filter.rs:68
- Duplicated block (11 lines × 7) src/iter/fold.rs:72
- Duplicated block (15 lines × 2) src/iter/fold.rs:242
- Duplicated block (13 lines × 3) src/iter/inspect.rs:131
- Near-duplicate member pair (74 shared lines) rayon-demo/src/nbody/nbody.rs:193
- Duplicated block (33–35 lines × 2) rayon-demo/src/nbody/nbody.rs:297
- Duplicated block (27 lines × 2) rayon-demo/src/nbody/nbody.rs:194
- Duplicated block (14 lines × 2) rayon-demo/src/nbody/nbody.rs:225
- Duplicated block (11 lines × 2) rayon-demo/src/nbody/mod.rs:96
- Duplicated block (9 lines × 2) rayon-demo/src/mergesort/mod.rs:66
- Duplicated block (7 lines × 3) rayon-demo/src/nbody/nbody.rs:93
- Off the main sequence: rayon-core
- README may be stale
- No structured logging
Minor — 16 finding(s)
- Orphaned file rayon-demo/src/nbody/nbody.rs:1
- Orphaned file src/iter/collect/test.rs:1
- Orphaned file rayon-demo/src/matmul/mod.rs:1
- Orphaned file rayon-core/src/sleep/mod.rs:1
- Orphaned file src/iter/interleave.rs:1
- Orphaned file rayon-demo/src/tsp/step.rs:1
- Orphaned file rayon-demo/src/nbody/mod.rs:1
- Orphaned file rayon-demo/src/tsp/solver.rs:1
- Orphaned file src/iter/step_by.rs:1
- Orphaned file rayon-demo/src/tsp/mod.rs:1
- Orphaned file rayon-demo/src/tree.rs:1
- Off-boarding risk: anonymized user #1
- Projects may be oversized for their cohesion
- Orphaned files with no living knowledge
- No ADRs
- No SAST
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-a5a99e1393ad483c918543c0b531714f/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-a5a99e1393ad483c918543c0b531714f/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 . | 24 | 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 | — |