Executive summary
rsonquery/rsonpath meets our standard for a preview release. It scores 76.1 out of 100 and is rated Strong, and all eight of its critical findings are security problems.
Every lens scores high enough to be rated Strong, so no single lens holds the score back. The best first step for the work it takes is recording design decisions, worth about 1.8 points. Adding structured logging comes next, worth about 2.1 points.
Four secrets can leak from the build pipeline. Two settings leave the servers or containers unsafe, and one automatic update takes new releases before a bad one can be spotted. Limiting each secret to its own step, correcting the unsafe settings and setting a waiting period for automatic updates would close these risks. Pinning each tool to an exact version would fix the pipeline tool referenced by a changeable name.
The product code is 25,838 lines, about €44,000 to rebuild.
Every lens already scores high enough to be rated Strong, so no single lens holds the score back.
Rebuild cost: about €44,000 · Estimate
| Cost to rebuild | €15,000 to €74,000, for 246 to 780 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 | ×1.2 at a score of 76. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Medium: 25,838 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 rsonpath_lib | 2 rsonpath_lib.classification.memmem.shared.vector_128 | 3 rsonpath_lib.depth | 4 rsonpath_lib.string_pattern | 5 rsonpath_syntax | 6 rsonpath_syntax.error | 7 rsonpath.error | 8 rsonpath_lib.automaton | 9 rsonpath_lib.classification.structural | 10 rsonpath_lib.input | 11 rsonpath_lib.automaton.minimizer | 12 rsonpath_lib.classification.structural.nosimd | 13 rsonpath_lib.classification.memmem | 14 rsonpath_lib.classification.quotes | 15 rsonpath_lib.classification | 16 rsonpath_lib.classification.quotes.avx2_32 | 17 rsonpath_lib.classification.quotes.neon_64 | 18 rsonpath_lib.classification.quotes.sse2_32 | 19 rsonpath_lib.classification.structural.shared.mask_32 | 20 rsonpath_lib.classification.depth | 21 rsonpath_lib.classification.quotes.avx2_64 | 22 rsonpath_lib.classification.quotes.sse2_64 | 23 rsonpath_lib.classification.structural.avx2_32 | 24 rsonpath_lib.classification.structural.avx2_64 | 25 rsonpath_lib.classification.structural.avx512_64 | 26 rsonpath_lib.classification.structural.neon_64 | 27 rsonpath_lib.classification.structural.ssse3_32 | 28 rsonpath_lib.classification.structural.ssse3_64 | 29 rsonpath_lib.engine.head_skipping | 30 rsonpath_lib.classification.depth.avx2_32 | 31 rsonpath_lib.classification.depth.nosimd | 32 rsonpath_lib.classification.depth.shared.mask_64 | 33 rsonpath_lib.classification.depth.sse2_32 | 34 rsonpath_lib.classification.simd | 35 rsonpath_lib.classification.depth.avx2_64 | 36 rsonpath_lib.classification.depth.avx512_64 | 37 rsonpath_lib.classification.depth.neon_64 | 38 rsonpath_lib.classification.depth.sse2_64 | 39 rsonpath_lib.engine.main | 40 rsonpath_lib.result |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 rsonpath_lib | ||||||||||||||||||||||||||||||||||||||||
| 2 rsonpath_lib.classification.memmem.shared.vector_128 | ||||||||||||||||||||||||||||||||||||||||
| 3 rsonpath_lib.depth | ||||||||||||||||||||||||||||||||||||||||
| 4 rsonpath_lib.string_pattern | ||||||||||||||||||||||||||||||||||||||||
| 5 rsonpath_syntax | ||||||||||||||||||||||||||||||||||||||||
| 6 rsonpath_syntax.error | ||||||||||||||||||||||||||||||||||||||||
| 7 rsonpath.error | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 8 rsonpath_lib.automaton | 2 | |||||||||||||||||||||||||||||||||||||||
| 9 rsonpath_lib.classification.structural | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 10 rsonpath_lib.input | 2 | |||||||||||||||||||||||||||||||||||||||
| 11 rsonpath_lib.automaton.minimizer | 1 | |||||||||||||||||||||||||||||||||||||||
| 12 rsonpath_lib.classification.structural.nosimd | 1 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 13 rsonpath_lib.classification.memmem | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 14 rsonpath_lib.classification.quotes | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 15 rsonpath_lib.classification | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 rsonpath_lib.classification.quotes.avx2_32 | 1 | 1 | 4 | |||||||||||||||||||||||||||||||||||||
| 17 rsonpath_lib.classification.quotes.neon_64 | 1 | 1 | 4 | |||||||||||||||||||||||||||||||||||||
| 18 rsonpath_lib.classification.quotes.sse2_32 | 1 | 1 | 4 | |||||||||||||||||||||||||||||||||||||
| 19 rsonpath_lib.classification.structural.shared.mask_32 | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 20 rsonpath_lib.classification.depth | 1 | 2 | 2 | 2 | ||||||||||||||||||||||||||||||||||||
| 21 rsonpath_lib.classification.quotes.avx2_64 | 1 | 1 | 4 | 1 | ||||||||||||||||||||||||||||||||||||
| 22 rsonpath_lib.classification.quotes.sse2_64 | 1 | 1 | 4 | 1 | ||||||||||||||||||||||||||||||||||||
| 23 rsonpath_lib.classification.structural.avx2_32 | 1 | 2 | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||
| 24 rsonpath_lib.classification.structural.avx2_64 | 1 | 2 | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||
| 25 rsonpath_lib.classification.structural.avx512_64 | 1 | 2 | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||
| 26 rsonpath_lib.classification.structural.neon_64 | 1 | 2 | 1 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||
| 27 rsonpath_lib.classification.structural.ssse3_32 | 1 | 1 | 2 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||
| 28 rsonpath_lib.classification.structural.ssse3_64 | 1 | 1 | 2 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||
| 29 rsonpath_lib.engine.head_skipping | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 30 rsonpath_lib.classification.depth.avx2_32 | 1 | 1 | 1 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||
| 31 rsonpath_lib.classification.depth.nosimd | 1 | 2 | 1 | 1 | 1 | 3 | ||||||||||||||||||||||||||||||||||
| 32 rsonpath_lib.classification.depth.shared.mask_64 | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 33 rsonpath_lib.classification.depth.sse2_32 | 1 | 1 | 1 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||
| 34 rsonpath_lib.classification.simd | 2 | 2 | 2 | 2 | 2 | |||||||||||||||||||||||||||||||||||
| 35 rsonpath_lib.classification.depth.avx2_64 | 1 | 1 | 1 | 1 | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||
| 36 rsonpath_lib.classification.depth.avx512_64 | 1 | 1 | 1 | 1 | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||
| 37 rsonpath_lib.classification.depth.neon_64 | 1 | 1 | 1 | 1 | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||
| 38 rsonpath_lib.classification.depth.sse2_64 | 1 | 1 | 1 | 1 | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||
| 39 rsonpath_lib.engine.main | 1 | 1 | 1 | 3 | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 40 rsonpath_lib.result | 1 | 1 |
7→5 rsonpath.error uses rsonpath_syntax✕
- Connections
- 1 pair of types, where a type in rsonpath.error uses a type in rsonpath_syntax.
- The types involved
rsonpath.error.error$module→rsonpath_syntax.JsonPathQuery
- Direction
- rsonpath.error uses rsonpath_syntax, so a change to rsonpath_syntax can break rsonpath.error, while a change to rsonpath.error can't break rsonpath_syntax.
- Position
- Below the diagonal: rsonpath.error uses a module listed above it, which is the healthy direction.
7→6 rsonpath.error uses rsonpath_syntax.error✕
- Connections
- 1 pair of types, where a type in rsonpath.error uses a type in rsonpath_syntax.error.
- The types involved
rsonpath.error.error$module→rsonpath_syntax.error.ParseError
- Direction
- rsonpath.error uses rsonpath_syntax.error, so a change to rsonpath_syntax.error can break rsonpath.error, while a change to rsonpath.error can't break rsonpath_syntax.error.
- Position
- Below the diagonal: rsonpath.error uses a module listed above it, which is the healthy direction.
8→5 rsonpath_lib.automaton uses rsonpath_syntax✕
- Connections
- 2 pairs of types, where a type in rsonpath_lib.automaton uses a type in rsonpath_syntax.
- The types involved
rsonpath_lib.automaton.Automaton→rsonpath_syntax.Indexrsonpath_lib.automaton.Automaton→rsonpath_syntax.JsonPathQuery
- Direction
- rsonpath_lib.automaton uses rsonpath_syntax, so a change to rsonpath_syntax can break rsonpath_lib.automaton, while a change to rsonpath_lib.automaton can't break rsonpath_syntax.
- Position
- Below the diagonal: rsonpath_lib.automaton uses a module listed above it, which is the healthy direction.
9→1 rsonpath_lib.classification.structural uses rsonpath_lib✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.classification.structural uses a type in rsonpath_lib.
- The types involved
rsonpath_lib.classification.structural.StructuralIterator→rsonpath_lib.FallibleIterator
- Direction
- rsonpath_lib.classification.structural uses rsonpath_lib, so a change to rsonpath_lib can break rsonpath_lib.classification.structural, while a change to rsonpath_lib.classification.structural can't break rsonpath_lib.
- Position
- Below the diagonal: rsonpath_lib.classification.structural uses a module listed above it, which is the healthy direction.
9→15 rsonpath_lib.classification.structural uses rsonpath_lib.classification part of a loop✕
- Connections
- 2 pairs of types, where a type in rsonpath_lib.classification.structural uses a type in rsonpath_lib.classification.
- The types involved
rsonpath_lib.classification.structural.StructuralImpl→rsonpath_lib.classification.ResumeClassifierStatersonpath_lib.classification.structural.StructuralIterator→rsonpath_lib.classification.ResumeClassifierState
- Direction
- rsonpath_lib.classification.structural uses rsonpath_lib.classification, so a change to rsonpath_lib.classification can break rsonpath_lib.classification.structural, while a change to rsonpath_lib.classification.structural can't break rsonpath_lib.classification.
- 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→4 rsonpath_lib.input uses rsonpath_lib.string_pattern✕
- Connections
- 2 pairs of types, where a type in rsonpath_lib.input uses a type in rsonpath_lib.string_pattern.
- The types involved
rsonpath_lib.input.Input→rsonpath_lib.string_pattern.StringPatternrsonpath_lib.input.SliceSeekable→rsonpath_lib.string_pattern.StringPattern
- Direction
- rsonpath_lib.input uses rsonpath_lib.string_pattern, so a change to rsonpath_lib.string_pattern can break rsonpath_lib.input, while a change to rsonpath_lib.input can't break rsonpath_lib.string_pattern.
- Position
- Below the diagonal: rsonpath_lib.input uses a module listed above it, which is the healthy direction.
11→8 rsonpath_lib.automaton.minimizer uses rsonpath_lib.automaton✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.automaton.minimizer uses a type in rsonpath_lib.automaton.
- The types involved
rsonpath_lib.automaton.minimizer.Minimizer→rsonpath_lib.automaton.StateTable
- Direction
- rsonpath_lib.automaton.minimizer uses rsonpath_lib.automaton, so a change to rsonpath_lib.automaton can break rsonpath_lib.automaton.minimizer, while a change to rsonpath_lib.automaton.minimizer can't break rsonpath_lib.automaton.
- Position
- Below the diagonal: rsonpath_lib.automaton.minimizer uses a module listed above it, which is the healthy direction.
12→1 rsonpath_lib.classification.structural.nosimd uses rsonpath_lib✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.classification.structural.nosimd uses a type in rsonpath_lib.
- The types involved
rsonpath_lib.classification.structural.nosimd.SequentialClassifier→rsonpath_lib.FallibleIterator
- Direction
- rsonpath_lib.classification.structural.nosimd uses rsonpath_lib, so a change to rsonpath_lib can break rsonpath_lib.classification.structural.nosimd, while a change to rsonpath_lib.classification.structural.nosimd can't break rsonpath_lib.
- Position
- Below the diagonal: rsonpath_lib.classification.structural.nosimd uses a module listed above it, which is the healthy direction.
12→9 rsonpath_lib.classification.structural.nosimd uses rsonpath_lib.classification.structural✕
- Connections
- 2 pairs of types, where a type in rsonpath_lib.classification.structural.nosimd uses a type in rsonpath_lib.classification.structural.
- The types involved
rsonpath_lib.classification.structural.nosimd.Constructor→rsonpath_lib.classification.structural.StructuralImplrsonpath_lib.classification.structural.nosimd.SequentialClassifier→rsonpath_lib.classification.structural.StructuralIterator
- Direction
- rsonpath_lib.classification.structural.nosimd uses rsonpath_lib.classification.structural, so a change to rsonpath_lib.classification.structural can break rsonpath_lib.classification.structural.nosimd, while a change to rsonpath_lib.classification.structural.nosimd can't break rsonpath_lib.classification.structural.
- Position
- Below the diagonal: rsonpath_lib.classification.structural.nosimd uses a module listed above it, which is the healthy direction.
12→14 rsonpath_lib.classification.structural.nosimd uses rsonpath_lib.classification.quotes part of a loop✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.classification.structural.nosimd uses a type in rsonpath_lib.classification.quotes.
- The types involved
rsonpath_lib.classification.structural.nosimd.Block→rsonpath_lib.classification.quotes.QuoteClassifiedBlock
- Direction
- rsonpath_lib.classification.structural.nosimd uses rsonpath_lib.classification.quotes, so a change to rsonpath_lib.classification.quotes can break rsonpath_lib.classification.structural.nosimd, while a change to rsonpath_lib.classification.structural.nosimd can't break rsonpath_lib.classification.quotes.
- 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→15 rsonpath_lib.classification.structural.nosimd uses rsonpath_lib.classification part of a loop✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.classification.structural.nosimd uses a type in rsonpath_lib.classification.
- The types involved
rsonpath_lib.classification.structural.nosimd.SequentialClassifier→rsonpath_lib.classification.ResumeClassifierState
- Direction
- rsonpath_lib.classification.structural.nosimd uses rsonpath_lib.classification, so a change to rsonpath_lib.classification can break rsonpath_lib.classification.structural.nosimd, while a change to rsonpath_lib.classification.structural.nosimd can't break rsonpath_lib.classification.
- 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→4 rsonpath_lib.classification.memmem uses rsonpath_lib.string_pattern✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.classification.memmem uses a type in rsonpath_lib.string_pattern.
- The types involved
rsonpath_lib.classification.memmem.Memmem→rsonpath_lib.string_pattern.StringPattern
- Direction
- rsonpath_lib.classification.memmem uses rsonpath_lib.string_pattern, so a change to rsonpath_lib.string_pattern can break rsonpath_lib.classification.memmem, while a change to rsonpath_lib.classification.memmem can't break rsonpath_lib.string_pattern.
- Position
- Below the diagonal: rsonpath_lib.classification.memmem uses a module listed above it, which is the healthy direction.
13→12 rsonpath_lib.classification.memmem uses rsonpath_lib.classification.structural.nosimd✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.classification.memmem uses a type in rsonpath_lib.classification.structural.nosimd.
- The types involved
rsonpath_lib.classification.memmem.Memmem→rsonpath_lib.classification.structural.nosimd.Block
- Direction
- rsonpath_lib.classification.memmem uses rsonpath_lib.classification.structural.nosimd, so a change to rsonpath_lib.classification.structural.nosimd can break rsonpath_lib.classification.memmem, while a change to rsonpath_lib.classification.memmem can't break rsonpath_lib.classification.structural.nosimd.
- Position
- Below the diagonal: rsonpath_lib.classification.memmem uses a module listed above it, which is the healthy direction.
14→1 rsonpath_lib.classification.quotes uses rsonpath_lib✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.classification.quotes uses a type in rsonpath_lib.
- The types involved
rsonpath_lib.classification.quotes.QuoteClassifiedIterator→rsonpath_lib.FallibleIterator
- Direction
- rsonpath_lib.classification.quotes uses rsonpath_lib, so a change to rsonpath_lib can break rsonpath_lib.classification.quotes, while a change to rsonpath_lib.classification.quotes can't break rsonpath_lib.
- Position
- Below the diagonal: rsonpath_lib.classification.quotes uses a module listed above it, which is the healthy direction.
14→12 rsonpath_lib.classification.quotes uses rsonpath_lib.classification.structural.nosimd✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.classification.quotes uses a type in rsonpath_lib.classification.structural.nosimd.
- The types involved
rsonpath_lib.classification.quotes.QuotesImpl→rsonpath_lib.classification.structural.nosimd.Block
- Direction
- rsonpath_lib.classification.quotes uses rsonpath_lib.classification.structural.nosimd, so a change to rsonpath_lib.classification.structural.nosimd can break rsonpath_lib.classification.quotes, while a change to rsonpath_lib.classification.quotes can't break rsonpath_lib.classification.structural.nosimd.
- Position
- Below the diagonal: rsonpath_lib.classification.quotes uses a module listed above it, which is the healthy direction.
15→14 rsonpath_lib.classification uses rsonpath_lib.classification.quotes✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.classification uses a type in rsonpath_lib.classification.quotes.
- The types involved
rsonpath_lib.classification.ResumeClassifierBlockState→rsonpath_lib.classification.quotes.QuoteClassifiedBlock
- Direction
- rsonpath_lib.classification uses rsonpath_lib.classification.quotes, so a change to rsonpath_lib.classification.quotes can break rsonpath_lib.classification, while a change to rsonpath_lib.classification can't break rsonpath_lib.classification.quotes.
- Position
- Below the diagonal: rsonpath_lib.classification uses a module listed above it, which is the healthy direction.
16→1 rsonpath_lib.classification.quotes.avx2_32 uses rsonpath_lib✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.classification.quotes.avx2_32 uses a type in rsonpath_lib.
- The types involved
rsonpath_lib.classification.quotes.avx2_32.Avx2QuoteClassifier32→rsonpath_lib.FallibleIterator
- Direction
- rsonpath_lib.classification.quotes.avx2_32 uses rsonpath_lib, so a change to rsonpath_lib can break rsonpath_lib.classification.quotes.avx2_32, while a change to rsonpath_lib.classification.quotes.avx2_32 can't break rsonpath_lib.
- Position
- Below the diagonal: rsonpath_lib.classification.quotes.avx2_32 uses a module listed above it, which is the healthy direction.
16→12 rsonpath_lib.classification.quotes.avx2_32 uses rsonpath_lib.classification.structural.nosimd✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.classification.quotes.avx2_32 uses a type in rsonpath_lib.classification.structural.nosimd.
- The types involved
rsonpath_lib.classification.quotes.avx2_32.Constructor→rsonpath_lib.classification.structural.nosimd.Block
- Direction
- rsonpath_lib.classification.quotes.avx2_32 uses rsonpath_lib.classification.structural.nosimd, so a change to rsonpath_lib.classification.structural.nosimd can break rsonpath_lib.classification.quotes.avx2_32, while a change to rsonpath_lib.classification.quotes.avx2_32 can't break rsonpath_lib.classification.structural.nosimd.
- Position
- Below the diagonal: rsonpath_lib.classification.quotes.avx2_32 uses a module listed above it, which is the healthy direction.
16→14 rsonpath_lib.classification.quotes.avx2_32 uses rsonpath_lib.classification.quotes✕
- Connections
- 4 pairs of types, where a type in rsonpath_lib.classification.quotes.avx2_32 uses a type in rsonpath_lib.classification.quotes.
- The types involved
rsonpath_lib.classification.quotes.avx2_32.Avx2QuoteClassifier32→rsonpath_lib.classification.quotes.InnerIterrsonpath_lib.classification.quotes.avx2_32.Avx2QuoteClassifier32→rsonpath_lib.classification.quotes.QuoteClassifiedIteratorrsonpath_lib.classification.quotes.avx2_32.Constructor→rsonpath_lib.classification.quotes.QuotesImplrsonpath_lib.classification.quotes.avx2_32.Constructor→rsonpath_lib.classification.quotes.ResumedQuoteClassifier
- Direction
- rsonpath_lib.classification.quotes.avx2_32 uses rsonpath_lib.classification.quotes, so a change to rsonpath_lib.classification.quotes can break rsonpath_lib.classification.quotes.avx2_32, while a change to rsonpath_lib.classification.quotes.avx2_32 can't break rsonpath_lib.classification.quotes.
- Position
- Below the diagonal: rsonpath_lib.classification.quotes.avx2_32 uses a module listed above it, which is the healthy direction.
17→1 rsonpath_lib.classification.quotes.neon_64 uses rsonpath_lib✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.classification.quotes.neon_64 uses a type in rsonpath_lib.
- The types involved
rsonpath_lib.classification.quotes.neon_64.NeonQuoteClassifier→rsonpath_lib.FallibleIterator
- Direction
- rsonpath_lib.classification.quotes.neon_64 uses rsonpath_lib, so a change to rsonpath_lib can break rsonpath_lib.classification.quotes.neon_64, while a change to rsonpath_lib.classification.quotes.neon_64 can't break rsonpath_lib.
- Position
- Below the diagonal: rsonpath_lib.classification.quotes.neon_64 uses a module listed above it, which is the healthy direction.
17→12 rsonpath_lib.classification.quotes.neon_64 uses rsonpath_lib.classification.structural.nosimd✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.classification.quotes.neon_64 uses a type in rsonpath_lib.classification.structural.nosimd.
- The types involved
rsonpath_lib.classification.quotes.neon_64.Constructor→rsonpath_lib.classification.structural.nosimd.Block
- Direction
- rsonpath_lib.classification.quotes.neon_64 uses rsonpath_lib.classification.structural.nosimd, so a change to rsonpath_lib.classification.structural.nosimd can break rsonpath_lib.classification.quotes.neon_64, while a change to rsonpath_lib.classification.quotes.neon_64 can't break rsonpath_lib.classification.structural.nosimd.
- Position
- Below the diagonal: rsonpath_lib.classification.quotes.neon_64 uses a module listed above it, which is the healthy direction.
17→14 rsonpath_lib.classification.quotes.neon_64 uses rsonpath_lib.classification.quotes✕
- Connections
- 4 pairs of types, where a type in rsonpath_lib.classification.quotes.neon_64 uses a type in rsonpath_lib.classification.quotes.
- The types involved
rsonpath_lib.classification.quotes.neon_64.Constructor→rsonpath_lib.classification.quotes.QuotesImplrsonpath_lib.classification.quotes.neon_64.Constructor→rsonpath_lib.classification.quotes.ResumedQuoteClassifierrsonpath_lib.classification.quotes.neon_64.NeonQuoteClassifier→rsonpath_lib.classification.quotes.InnerIterrsonpath_lib.classification.quotes.neon_64.NeonQuoteClassifier→rsonpath_lib.classification.quotes.QuoteClassifiedIterator
- Direction
- rsonpath_lib.classification.quotes.neon_64 uses rsonpath_lib.classification.quotes, so a change to rsonpath_lib.classification.quotes can break rsonpath_lib.classification.quotes.neon_64, while a change to rsonpath_lib.classification.quotes.neon_64 can't break rsonpath_lib.classification.quotes.
- Position
- Below the diagonal: rsonpath_lib.classification.quotes.neon_64 uses a module listed above it, which is the healthy direction.
18→1 rsonpath_lib.classification.quotes.sse2_32 uses rsonpath_lib✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.classification.quotes.sse2_32 uses a type in rsonpath_lib.
- The types involved
rsonpath_lib.classification.quotes.sse2_32.Sse2QuoteClassifier32→rsonpath_lib.FallibleIterator
- Direction
- rsonpath_lib.classification.quotes.sse2_32 uses rsonpath_lib, so a change to rsonpath_lib can break rsonpath_lib.classification.quotes.sse2_32, while a change to rsonpath_lib.classification.quotes.sse2_32 can't break rsonpath_lib.
- Position
- Below the diagonal: rsonpath_lib.classification.quotes.sse2_32 uses a module listed above it, which is the healthy direction.
18→12 rsonpath_lib.classification.quotes.sse2_32 uses rsonpath_lib.classification.structural.nosimd✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.classification.quotes.sse2_32 uses a type in rsonpath_lib.classification.structural.nosimd.
- The types involved
rsonpath_lib.classification.quotes.sse2_32.Constructor→rsonpath_lib.classification.structural.nosimd.Block
- Direction
- rsonpath_lib.classification.quotes.sse2_32 uses rsonpath_lib.classification.structural.nosimd, so a change to rsonpath_lib.classification.structural.nosimd can break rsonpath_lib.classification.quotes.sse2_32, while a change to rsonpath_lib.classification.quotes.sse2_32 can't break rsonpath_lib.classification.structural.nosimd.
- Position
- Below the diagonal: rsonpath_lib.classification.quotes.sse2_32 uses a module listed above it, which is the healthy direction.
18→14 rsonpath_lib.classification.quotes.sse2_32 uses rsonpath_lib.classification.quotes✕
- Connections
- 4 pairs of types, where a type in rsonpath_lib.classification.quotes.sse2_32 uses a type in rsonpath_lib.classification.quotes.
- The types involved
rsonpath_lib.classification.quotes.sse2_32.Constructor→rsonpath_lib.classification.quotes.QuotesImplrsonpath_lib.classification.quotes.sse2_32.Constructor→rsonpath_lib.classification.quotes.ResumedQuoteClassifierrsonpath_lib.classification.quotes.sse2_32.Sse2QuoteClassifier32→rsonpath_lib.classification.quotes.InnerIterrsonpath_lib.classification.quotes.sse2_32.Sse2QuoteClassifier32→rsonpath_lib.classification.quotes.QuoteClassifiedIterator
- Direction
- rsonpath_lib.classification.quotes.sse2_32 uses rsonpath_lib.classification.quotes, so a change to rsonpath_lib.classification.quotes can break rsonpath_lib.classification.quotes.sse2_32, while a change to rsonpath_lib.classification.quotes.sse2_32 can't break rsonpath_lib.classification.quotes.
- Position
- Below the diagonal: rsonpath_lib.classification.quotes.sse2_32 uses a module listed above it, which is the healthy direction.
19→9 rsonpath_lib.classification.structural.shared.mask_32 uses rsonpath_lib.classification.structural✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.classification.structural.shared.mask_32 uses a type in rsonpath_lib.classification.structural.
- The types involved
rsonpath_lib.classification.structural.shared.mask_32.StructuralsBlock→rsonpath_lib.classification.structural.Structural
- Direction
- rsonpath_lib.classification.structural.shared.mask_32 uses rsonpath_lib.classification.structural, so a change to rsonpath_lib.classification.structural can break rsonpath_lib.classification.structural.shared.mask_32, while a change to rsonpath_lib.classification.structural.shared.mask_32 can't break rsonpath_lib.classification.structural.
- Position
- Below the diagonal: rsonpath_lib.classification.structural.shared.mask_32 uses a module listed above it, which is the healthy direction.
19→14 rsonpath_lib.classification.structural.shared.mask_32 uses rsonpath_lib.classification.quotes✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.classification.structural.shared.mask_32 uses a type in rsonpath_lib.classification.quotes.
- The types involved
rsonpath_lib.classification.structural.shared.mask_32.StructuralsBlock→rsonpath_lib.classification.quotes.QuoteClassifiedBlock
- Direction
- rsonpath_lib.classification.structural.shared.mask_32 uses rsonpath_lib.classification.quotes, so a change to rsonpath_lib.classification.quotes can break rsonpath_lib.classification.structural.shared.mask_32, while a change to rsonpath_lib.classification.structural.shared.mask_32 can't break rsonpath_lib.classification.quotes.
- Position
- Below the diagonal: rsonpath_lib.classification.structural.shared.mask_32 uses a module listed above it, which is the healthy direction.
20→1 rsonpath_lib.classification.depth uses rsonpath_lib✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.classification.depth uses a type in rsonpath_lib.
- The types involved
rsonpath_lib.classification.depth.DepthIterator→rsonpath_lib.FallibleIterator
- Direction
- rsonpath_lib.classification.depth uses rsonpath_lib, so a change to rsonpath_lib can break rsonpath_lib.classification.depth, while a change to rsonpath_lib.classification.depth can't break rsonpath_lib.
- Position
- Below the diagonal: rsonpath_lib.classification.depth uses a module listed above it, which is the healthy direction.
20→9 rsonpath_lib.classification.depth uses rsonpath_lib.classification.structural✕
- Connections
- 2 pairs of types, where a type in rsonpath_lib.classification.depth uses a type in rsonpath_lib.classification.structural.
- The types involved
rsonpath_lib.classification.depth.DepthImpl→rsonpath_lib.classification.structural.BracketTypersonpath_lib.classification.depth.DepthIterator→rsonpath_lib.classification.structural.BracketType
- Direction
- rsonpath_lib.classification.depth uses rsonpath_lib.classification.structural, so a change to rsonpath_lib.classification.structural can break rsonpath_lib.classification.depth, while a change to rsonpath_lib.classification.depth can't break rsonpath_lib.classification.structural.
- Position
- Below the diagonal: rsonpath_lib.classification.depth uses a module listed above it, which is the healthy direction.
20→12 rsonpath_lib.classification.depth uses rsonpath_lib.classification.structural.nosimd✕
- Connections
- 2 pairs of types, where a type in rsonpath_lib.classification.depth uses a type in rsonpath_lib.classification.structural.nosimd.
- The types involved
rsonpath_lib.classification.depth.DepthIterator→rsonpath_lib.classification.structural.nosimd.Blockrsonpath_lib.classification.depth.DepthIteratorResumeOutcome→rsonpath_lib.classification.structural.nosimd.Block
- Direction
- rsonpath_lib.classification.depth uses rsonpath_lib.classification.structural.nosimd, so a change to rsonpath_lib.classification.structural.nosimd can break rsonpath_lib.classification.depth, while a change to rsonpath_lib.classification.depth can't break rsonpath_lib.classification.structural.nosimd.
- Position
- Below the diagonal: rsonpath_lib.classification.depth uses a module listed above it, which is the healthy direction.
20→15 rsonpath_lib.classification.depth uses rsonpath_lib.classification✕
- Connections
- 2 pairs of types, where a type in rsonpath_lib.classification.depth uses a type in rsonpath_lib.classification.
- The types involved
rsonpath_lib.classification.depth.DepthImpl→rsonpath_lib.classification.ResumeClassifierStatersonpath_lib.classification.depth.DepthIterator→rsonpath_lib.classification.ResumeClassifierState
- Direction
- rsonpath_lib.classification.depth uses rsonpath_lib.classification, so a change to rsonpath_lib.classification can break rsonpath_lib.classification.depth, while a change to rsonpath_lib.classification.depth can't break rsonpath_lib.classification.
- Position
- Below the diagonal: rsonpath_lib.classification.depth uses a module listed above it, which is the healthy direction.
21→1 rsonpath_lib.classification.quotes.avx2_64 uses rsonpath_lib✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.classification.quotes.avx2_64 uses a type in rsonpath_lib.
- The types involved
rsonpath_lib.classification.quotes.avx2_64.Avx2QuoteClassifier64→rsonpath_lib.FallibleIterator
- Direction
- rsonpath_lib.classification.quotes.avx2_64 uses rsonpath_lib, so a change to rsonpath_lib can break rsonpath_lib.classification.quotes.avx2_64, while a change to rsonpath_lib.classification.quotes.avx2_64 can't break rsonpath_lib.
- Position
- Below the diagonal: rsonpath_lib.classification.quotes.avx2_64 uses a module listed above it, which is the healthy direction.
21→12 rsonpath_lib.classification.quotes.avx2_64 uses rsonpath_lib.classification.structural.nosimd✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.classification.quotes.avx2_64 uses a type in rsonpath_lib.classification.structural.nosimd.
- The types involved
rsonpath_lib.classification.quotes.avx2_64.Constructor→rsonpath_lib.classification.structural.nosimd.Block
- Direction
- rsonpath_lib.classification.quotes.avx2_64 uses rsonpath_lib.classification.structural.nosimd, so a change to rsonpath_lib.classification.structural.nosimd can break rsonpath_lib.classification.quotes.avx2_64, while a change to rsonpath_lib.classification.quotes.avx2_64 can't break rsonpath_lib.classification.structural.nosimd.
- Position
- Below the diagonal: rsonpath_lib.classification.quotes.avx2_64 uses a module listed above it, which is the healthy direction.
21→14 rsonpath_lib.classification.quotes.avx2_64 uses rsonpath_lib.classification.quotes✕
- Connections
- 4 pairs of types, where a type in rsonpath_lib.classification.quotes.avx2_64 uses a type in rsonpath_lib.classification.quotes.
- The types involved
rsonpath_lib.classification.quotes.avx2_64.Avx2QuoteClassifier64→rsonpath_lib.classification.quotes.InnerIterrsonpath_lib.classification.quotes.avx2_64.Avx2QuoteClassifier64→rsonpath_lib.classification.quotes.QuoteClassifiedIteratorrsonpath_lib.classification.quotes.avx2_64.Constructor→rsonpath_lib.classification.quotes.QuotesImplrsonpath_lib.classification.quotes.avx2_64.Constructor→rsonpath_lib.classification.quotes.ResumedQuoteClassifier
- Direction
- rsonpath_lib.classification.quotes.avx2_64 uses rsonpath_lib.classification.quotes, so a change to rsonpath_lib.classification.quotes can break rsonpath_lib.classification.quotes.avx2_64, while a change to rsonpath_lib.classification.quotes.avx2_64 can't break rsonpath_lib.classification.quotes.
- Position
- Below the diagonal: rsonpath_lib.classification.quotes.avx2_64 uses a module listed above it, which is the healthy direction.
21→16 rsonpath_lib.classification.quotes.avx2_64 uses rsonpath_lib.classification.quotes.avx2_32✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.classification.quotes.avx2_64 uses a type in rsonpath_lib.classification.quotes.avx2_32.
- The types involved
rsonpath_lib.classification.quotes.avx2_64.Avx2QuoteClassifier64→rsonpath_lib.classification.quotes.avx2_32.BlockAvx2Classifier
- Direction
- rsonpath_lib.classification.quotes.avx2_64 uses rsonpath_lib.classification.quotes.avx2_32, so a change to rsonpath_lib.classification.quotes.avx2_32 can break rsonpath_lib.classification.quotes.avx2_64, while a change to rsonpath_lib.classification.quotes.avx2_64 can't break rsonpath_lib.classification.quotes.avx2_32.
- Position
- Below the diagonal: rsonpath_lib.classification.quotes.avx2_64 uses a module listed above it, which is the healthy direction.
22→1 rsonpath_lib.classification.quotes.sse2_64 uses rsonpath_lib✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.classification.quotes.sse2_64 uses a type in rsonpath_lib.
- The types involved
rsonpath_lib.classification.quotes.sse2_64.Sse2QuoteClassifier64→rsonpath_lib.FallibleIterator
- Direction
- rsonpath_lib.classification.quotes.sse2_64 uses rsonpath_lib, so a change to rsonpath_lib can break rsonpath_lib.classification.quotes.sse2_64, while a change to rsonpath_lib.classification.quotes.sse2_64 can't break rsonpath_lib.
- Position
- Below the diagonal: rsonpath_lib.classification.quotes.sse2_64 uses a module listed above it, which is the healthy direction.
22→12 rsonpath_lib.classification.quotes.sse2_64 uses rsonpath_lib.classification.structural.nosimd✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.classification.quotes.sse2_64 uses a type in rsonpath_lib.classification.structural.nosimd.
- The types involved
rsonpath_lib.classification.quotes.sse2_64.Constructor→rsonpath_lib.classification.structural.nosimd.Block
- Direction
- rsonpath_lib.classification.quotes.sse2_64 uses rsonpath_lib.classification.structural.nosimd, so a change to rsonpath_lib.classification.structural.nosimd can break rsonpath_lib.classification.quotes.sse2_64, while a change to rsonpath_lib.classification.quotes.sse2_64 can't break rsonpath_lib.classification.structural.nosimd.
- Position
- Below the diagonal: rsonpath_lib.classification.quotes.sse2_64 uses a module listed above it, which is the healthy direction.
22→14 rsonpath_lib.classification.quotes.sse2_64 uses rsonpath_lib.classification.quotes✕
- Connections
- 4 pairs of types, where a type in rsonpath_lib.classification.quotes.sse2_64 uses a type in rsonpath_lib.classification.quotes.
- The types involved
rsonpath_lib.classification.quotes.sse2_64.Constructor→rsonpath_lib.classification.quotes.QuotesImplrsonpath_lib.classification.quotes.sse2_64.Constructor→rsonpath_lib.classification.quotes.ResumedQuoteClassifierrsonpath_lib.classification.quotes.sse2_64.Sse2QuoteClassifier64→rsonpath_lib.classification.quotes.InnerIterrsonpath_lib.classification.quotes.sse2_64.Sse2QuoteClassifier64→rsonpath_lib.classification.quotes.QuoteClassifiedIterator
- Direction
- rsonpath_lib.classification.quotes.sse2_64 uses rsonpath_lib.classification.quotes, so a change to rsonpath_lib.classification.quotes can break rsonpath_lib.classification.quotes.sse2_64, while a change to rsonpath_lib.classification.quotes.sse2_64 can't break rsonpath_lib.classification.quotes.
- Position
- Below the diagonal: rsonpath_lib.classification.quotes.sse2_64 uses a module listed above it, which is the healthy direction.
22→18 rsonpath_lib.classification.quotes.sse2_64 uses rsonpath_lib.classification.quotes.sse2_32✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.classification.quotes.sse2_64 uses a type in rsonpath_lib.classification.quotes.sse2_32.
- The types involved
rsonpath_lib.classification.quotes.sse2_64.Sse2QuoteClassifier64→rsonpath_lib.classification.quotes.sse2_32.BlockSse2Classifier
- Direction
- rsonpath_lib.classification.quotes.sse2_64 uses rsonpath_lib.classification.quotes.sse2_32, so a change to rsonpath_lib.classification.quotes.sse2_32 can break rsonpath_lib.classification.quotes.sse2_64, while a change to rsonpath_lib.classification.quotes.sse2_64 can't break rsonpath_lib.classification.quotes.sse2_32.
- Position
- Below the diagonal: rsonpath_lib.classification.quotes.sse2_64 uses a module listed above it, which is the healthy direction.
23→1 rsonpath_lib.classification.structural.avx2_32 uses rsonpath_lib✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.classification.structural.avx2_32 uses a type in rsonpath_lib.
- The types involved
rsonpath_lib.classification.structural.avx2_32.Avx2Classifier32→rsonpath_lib.FallibleIterator
- Direction
- rsonpath_lib.classification.structural.avx2_32 uses rsonpath_lib, so a change to rsonpath_lib can break rsonpath_lib.classification.structural.avx2_32, while a change to rsonpath_lib.classification.structural.avx2_32 can't break rsonpath_lib.
- Position
- Below the diagonal: rsonpath_lib.classification.structural.avx2_32 uses a module listed above it, which is the healthy direction.
23→9 rsonpath_lib.classification.structural.avx2_32 uses rsonpath_lib.classification.structural✕
- Connections
- 2 pairs of types, where a type in rsonpath_lib.classification.structural.avx2_32 uses a type in rsonpath_lib.classification.structural.
- The types involved
rsonpath_lib.classification.structural.avx2_32.Avx2Classifier32→rsonpath_lib.classification.structural.StructuralIteratorrsonpath_lib.classification.structural.avx2_32.Constructor→rsonpath_lib.classification.structural.StructuralImpl
- Direction
- rsonpath_lib.classification.structural.avx2_32 uses rsonpath_lib.classification.structural, so a change to rsonpath_lib.classification.structural can break rsonpath_lib.classification.structural.avx2_32, while a change to rsonpath_lib.classification.structural.avx2_32 can't break rsonpath_lib.classification.structural.
- Position
- Below the diagonal: rsonpath_lib.classification.structural.avx2_32 uses a module listed above it, which is the healthy direction.
23→14 rsonpath_lib.classification.structural.avx2_32 uses rsonpath_lib.classification.quotes✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.classification.structural.avx2_32 uses a type in rsonpath_lib.classification.quotes.
- The types involved
rsonpath_lib.classification.structural.avx2_32.BlockAvx2Classifier32→rsonpath_lib.classification.quotes.QuoteClassifiedBlock
- Direction
- rsonpath_lib.classification.structural.avx2_32 uses rsonpath_lib.classification.quotes, so a change to rsonpath_lib.classification.quotes can break rsonpath_lib.classification.structural.avx2_32, while a change to rsonpath_lib.classification.structural.avx2_32 can't break rsonpath_lib.classification.quotes.
- Position
- Below the diagonal: rsonpath_lib.classification.structural.avx2_32 uses a module listed above it, which is the healthy direction.
23→15 rsonpath_lib.classification.structural.avx2_32 uses rsonpath_lib.classification✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.classification.structural.avx2_32 uses a type in rsonpath_lib.classification.
- The types involved
rsonpath_lib.classification.structural.avx2_32.Avx2Classifier32→rsonpath_lib.classification.ResumeClassifierState
- Direction
- rsonpath_lib.classification.structural.avx2_32 uses rsonpath_lib.classification, so a change to rsonpath_lib.classification can break rsonpath_lib.classification.structural.avx2_32, while a change to rsonpath_lib.classification.structural.avx2_32 can't break rsonpath_lib.classification.
- Position
- Below the diagonal: rsonpath_lib.classification.structural.avx2_32 uses a module listed above it, which is the healthy direction.
23→19 rsonpath_lib.classification.structural.avx2_32 uses rsonpath_lib.classification.structural.shared.mask_32✕
- Connections
- 2 pairs of types, where a type in rsonpath_lib.classification.structural.avx2_32 uses a type in rsonpath_lib.classification.structural.shared.mask_32.
- The types involved
rsonpath_lib.classification.structural.avx2_32.Avx2Classifier32→rsonpath_lib.classification.structural.shared.mask_32.StructuralsBlockrsonpath_lib.classification.structural.avx2_32.BlockAvx2Classifier32→rsonpath_lib.classification.structural.shared.mask_32.StructuralsBlock
- Direction
- rsonpath_lib.classification.structural.avx2_32 uses rsonpath_lib.classification.structural.shared.mask_32, so a change to rsonpath_lib.classification.structural.shared.mask_32 can break rsonpath_lib.classification.structural.avx2_32, while a change to rsonpath_lib.classification.structural.avx2_32 can't break rsonpath_lib.classification.structural.shared.mask_32.
- Position
- Below the diagonal: rsonpath_lib.classification.structural.avx2_32 uses a module listed above it, which is the healthy direction.
24→1 rsonpath_lib.classification.structural.avx2_64 uses rsonpath_lib✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.classification.structural.avx2_64 uses a type in rsonpath_lib.
- The types involved
rsonpath_lib.classification.structural.avx2_64.Avx2Classifier64→rsonpath_lib.FallibleIterator
- Direction
- rsonpath_lib.classification.structural.avx2_64 uses rsonpath_lib, so a change to rsonpath_lib can break rsonpath_lib.classification.structural.avx2_64, while a change to rsonpath_lib.classification.structural.avx2_64 can't break rsonpath_lib.
- Position
- Below the diagonal: rsonpath_lib.classification.structural.avx2_64 uses a module listed above it, which is the healthy direction.
24→9 rsonpath_lib.classification.structural.avx2_64 uses rsonpath_lib.classification.structural✕
- Connections
- 2 pairs of types, where a type in rsonpath_lib.classification.structural.avx2_64 uses a type in rsonpath_lib.classification.structural.
- The types involved
rsonpath_lib.classification.structural.avx2_64.Avx2Classifier64→rsonpath_lib.classification.structural.StructuralIteratorrsonpath_lib.classification.structural.avx2_64.Constructor→rsonpath_lib.classification.structural.StructuralImpl
- Direction
- rsonpath_lib.classification.structural.avx2_64 uses rsonpath_lib.classification.structural, so a change to rsonpath_lib.classification.structural can break rsonpath_lib.classification.structural.avx2_64, while a change to rsonpath_lib.classification.structural.avx2_64 can't break rsonpath_lib.classification.structural.
- Position
- Below the diagonal: rsonpath_lib.classification.structural.avx2_64 uses a module listed above it, which is the healthy direction.
24→14 rsonpath_lib.classification.structural.avx2_64 uses rsonpath_lib.classification.quotes✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.classification.structural.avx2_64 uses a type in rsonpath_lib.classification.quotes.
- The types involved
rsonpath_lib.classification.structural.avx2_64.BlockAvx2Classifier64→rsonpath_lib.classification.quotes.QuoteClassifiedBlock
- Direction
- rsonpath_lib.classification.structural.avx2_64 uses rsonpath_lib.classification.quotes, so a change to rsonpath_lib.classification.quotes can break rsonpath_lib.classification.structural.avx2_64, while a change to rsonpath_lib.classification.structural.avx2_64 can't break rsonpath_lib.classification.quotes.
- Position
- Below the diagonal: rsonpath_lib.classification.structural.avx2_64 uses a module listed above it, which is the healthy direction.
24→15 rsonpath_lib.classification.structural.avx2_64 uses rsonpath_lib.classification✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.classification.structural.avx2_64 uses a type in rsonpath_lib.classification.
- The types involved
rsonpath_lib.classification.structural.avx2_64.Avx2Classifier64→rsonpath_lib.classification.ResumeClassifierState
- Direction
- rsonpath_lib.classification.structural.avx2_64 uses rsonpath_lib.classification, so a change to rsonpath_lib.classification can break rsonpath_lib.classification.structural.avx2_64, while a change to rsonpath_lib.classification.structural.avx2_64 can't break rsonpath_lib.classification.
- Position
- Below the diagonal: rsonpath_lib.classification.structural.avx2_64 uses a module listed above it, which is the healthy direction.
24→19 rsonpath_lib.classification.structural.avx2_64 uses rsonpath_lib.classification.structural.shared.mask_32✕
- Connections
- 2 pairs of types, where a type in rsonpath_lib.classification.structural.avx2_64 uses a type in rsonpath_lib.classification.structural.shared.mask_32.
- The types involved
rsonpath_lib.classification.structural.avx2_64.Avx2Classifier64→rsonpath_lib.classification.structural.shared.mask_32.StructuralsBlockrsonpath_lib.classification.structural.avx2_64.BlockAvx2Classifier64→rsonpath_lib.classification.structural.shared.mask_32.StructuralsBlock
- Direction
- rsonpath_lib.classification.structural.avx2_64 uses rsonpath_lib.classification.structural.shared.mask_32, so a change to rsonpath_lib.classification.structural.shared.mask_32 can break rsonpath_lib.classification.structural.avx2_64, while a change to rsonpath_lib.classification.structural.avx2_64 can't break rsonpath_lib.classification.structural.shared.mask_32.
- Position
- Below the diagonal: rsonpath_lib.classification.structural.avx2_64 uses a module listed above it, which is the healthy direction.
25→1 rsonpath_lib.classification.structural.avx512_64 uses rsonpath_lib✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.classification.structural.avx512_64 uses a type in rsonpath_lib.
- The types involved
rsonpath_lib.classification.structural.avx512_64.Avx512Classifier64→rsonpath_lib.FallibleIterator
- Direction
- rsonpath_lib.classification.structural.avx512_64 uses rsonpath_lib, so a change to rsonpath_lib can break rsonpath_lib.classification.structural.avx512_64, while a change to rsonpath_lib.classification.structural.avx512_64 can't break rsonpath_lib.
- Position
- Below the diagonal: rsonpath_lib.classification.structural.avx512_64 uses a module listed above it, which is the healthy direction.
25→9 rsonpath_lib.classification.structural.avx512_64 uses rsonpath_lib.classification.structural✕
- Connections
- 2 pairs of types, where a type in rsonpath_lib.classification.structural.avx512_64 uses a type in rsonpath_lib.classification.structural.
- The types involved
rsonpath_lib.classification.structural.avx512_64.Avx512Classifier64→rsonpath_lib.classification.structural.StructuralIteratorrsonpath_lib.classification.structural.avx512_64.Constructor→rsonpath_lib.classification.structural.StructuralImpl
- Direction
- rsonpath_lib.classification.structural.avx512_64 uses rsonpath_lib.classification.structural, so a change to rsonpath_lib.classification.structural can break rsonpath_lib.classification.structural.avx512_64, while a change to rsonpath_lib.classification.structural.avx512_64 can't break rsonpath_lib.classification.structural.
- Position
- Below the diagonal: rsonpath_lib.classification.structural.avx512_64 uses a module listed above it, which is the healthy direction.
25→14 rsonpath_lib.classification.structural.avx512_64 uses rsonpath_lib.classification.quotes✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.classification.structural.avx512_64 uses a type in rsonpath_lib.classification.quotes.
- The types involved
rsonpath_lib.classification.structural.avx512_64.BlockAvx512Classifier64→rsonpath_lib.classification.quotes.QuoteClassifiedBlock
- Direction
- rsonpath_lib.classification.structural.avx512_64 uses rsonpath_lib.classification.quotes, so a change to rsonpath_lib.classification.quotes can break rsonpath_lib.classification.structural.avx512_64, while a change to rsonpath_lib.classification.structural.avx512_64 can't break rsonpath_lib.classification.quotes.
- Position
- Below the diagonal: rsonpath_lib.classification.structural.avx512_64 uses a module listed above it, which is the healthy direction.
25→15 rsonpath_lib.classification.structural.avx512_64 uses rsonpath_lib.classification✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.classification.structural.avx512_64 uses a type in rsonpath_lib.classification.
- The types involved
rsonpath_lib.classification.structural.avx512_64.Avx512Classifier64→rsonpath_lib.classification.ResumeClassifierState
- Direction
- rsonpath_lib.classification.structural.avx512_64 uses rsonpath_lib.classification, so a change to rsonpath_lib.classification can break rsonpath_lib.classification.structural.avx512_64, while a change to rsonpath_lib.classification.structural.avx512_64 can't break rsonpath_lib.classification.
- Position
- Below the diagonal: rsonpath_lib.classification.structural.avx512_64 uses a module listed above it, which is the healthy direction.
25→19 rsonpath_lib.classification.structural.avx512_64 uses rsonpath_lib.classification.structural.shared.mask_32✕
- Connections
- 2 pairs of types, where a type in rsonpath_lib.classification.structural.avx512_64 uses a type in rsonpath_lib.classification.structural.shared.mask_32.
- The types involved
rsonpath_lib.classification.structural.avx512_64.Avx512Classifier64→rsonpath_lib.classification.structural.shared.mask_32.StructuralsBlockrsonpath_lib.classification.structural.avx512_64.BlockAvx512Classifier64→rsonpath_lib.classification.structural.shared.mask_32.StructuralsBlock
- Direction
- rsonpath_lib.classification.structural.avx512_64 uses rsonpath_lib.classification.structural.shared.mask_32, so a change to rsonpath_lib.classification.structural.shared.mask_32 can break rsonpath_lib.classification.structural.avx512_64, while a change to rsonpath_lib.classification.structural.avx512_64 can't break rsonpath_lib.classification.structural.shared.mask_32.
- Position
- Below the diagonal: rsonpath_lib.classification.structural.avx512_64 uses a module listed above it, which is the healthy direction.
26→1 rsonpath_lib.classification.structural.neon_64 uses rsonpath_lib✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.classification.structural.neon_64 uses a type in rsonpath_lib.
- The types involved
rsonpath_lib.classification.structural.neon_64.NeonClassifier→rsonpath_lib.FallibleIterator
- Direction
- rsonpath_lib.classification.structural.neon_64 uses rsonpath_lib, so a change to rsonpath_lib can break rsonpath_lib.classification.structural.neon_64, while a change to rsonpath_lib.classification.structural.neon_64 can't break rsonpath_lib.
- Position
- Below the diagonal: rsonpath_lib.classification.structural.neon_64 uses a module listed above it, which is the healthy direction.
26→9 rsonpath_lib.classification.structural.neon_64 uses rsonpath_lib.classification.structural✕
- Connections
- 2 pairs of types, where a type in rsonpath_lib.classification.structural.neon_64 uses a type in rsonpath_lib.classification.structural.
- The types involved
rsonpath_lib.classification.structural.neon_64.Constructor→rsonpath_lib.classification.structural.StructuralImplrsonpath_lib.classification.structural.neon_64.NeonClassifier→rsonpath_lib.classification.structural.StructuralIterator
- Direction
- rsonpath_lib.classification.structural.neon_64 uses rsonpath_lib.classification.structural, so a change to rsonpath_lib.classification.structural can break rsonpath_lib.classification.structural.neon_64, while a change to rsonpath_lib.classification.structural.neon_64 can't break rsonpath_lib.classification.structural.
- Position
- Below the diagonal: rsonpath_lib.classification.structural.neon_64 uses a module listed above it, which is the healthy direction.
26→14 rsonpath_lib.classification.structural.neon_64 uses rsonpath_lib.classification.quotes✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.classification.structural.neon_64 uses a type in rsonpath_lib.classification.quotes.
- The types involved
rsonpath_lib.classification.structural.neon_64.BlockNeonClassifier→rsonpath_lib.classification.quotes.QuoteClassifiedBlock
- Direction
- rsonpath_lib.classification.structural.neon_64 uses rsonpath_lib.classification.quotes, so a change to rsonpath_lib.classification.quotes can break rsonpath_lib.classification.structural.neon_64, while a change to rsonpath_lib.classification.structural.neon_64 can't break rsonpath_lib.classification.quotes.
- Position
- Below the diagonal: rsonpath_lib.classification.structural.neon_64 uses a module listed above it, which is the healthy direction.
26→15 rsonpath_lib.classification.structural.neon_64 uses rsonpath_lib.classification✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.classification.structural.neon_64 uses a type in rsonpath_lib.classification.
- The types involved
rsonpath_lib.classification.structural.neon_64.NeonClassifier→rsonpath_lib.classification.ResumeClassifierState
- Direction
- rsonpath_lib.classification.structural.neon_64 uses rsonpath_lib.classification, so a change to rsonpath_lib.classification can break rsonpath_lib.classification.structural.neon_64, while a change to rsonpath_lib.classification.structural.neon_64 can't break rsonpath_lib.classification.
- Position
- Below the diagonal: rsonpath_lib.classification.structural.neon_64 uses a module listed above it, which is the healthy direction.
26→17 rsonpath_lib.classification.structural.neon_64 uses rsonpath_lib.classification.quotes.neon_64✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.classification.structural.neon_64 uses a type in rsonpath_lib.classification.quotes.neon_64.
- The types involved
rsonpath_lib.classification.structural.neon_64.NeonClassifier→rsonpath_lib.classification.quotes.neon_64.BlockNeonClassifier
- Direction
- rsonpath_lib.classification.structural.neon_64 uses rsonpath_lib.classification.quotes.neon_64, so a change to rsonpath_lib.classification.quotes.neon_64 can break rsonpath_lib.classification.structural.neon_64, while a change to rsonpath_lib.classification.structural.neon_64 can't break rsonpath_lib.classification.quotes.neon_64.
- Position
- Below the diagonal: rsonpath_lib.classification.structural.neon_64 uses a module listed above it, which is the healthy direction.
26→19 rsonpath_lib.classification.structural.neon_64 uses rsonpath_lib.classification.structural.shared.mask_32✕
- Connections
- 2 pairs of types, where a type in rsonpath_lib.classification.structural.neon_64 uses a type in rsonpath_lib.classification.structural.shared.mask_32.
- The types involved
rsonpath_lib.classification.structural.neon_64.BlockNeonClassifier→rsonpath_lib.classification.structural.shared.mask_32.StructuralsBlockrsonpath_lib.classification.structural.neon_64.NeonClassifier→rsonpath_lib.classification.structural.shared.mask_32.StructuralsBlock
- Direction
- rsonpath_lib.classification.structural.neon_64 uses rsonpath_lib.classification.structural.shared.mask_32, so a change to rsonpath_lib.classification.structural.shared.mask_32 can break rsonpath_lib.classification.structural.neon_64, while a change to rsonpath_lib.classification.structural.neon_64 can't break rsonpath_lib.classification.structural.shared.mask_32.
- Position
- Below the diagonal: rsonpath_lib.classification.structural.neon_64 uses a module listed above it, which is the healthy direction.
27→1 rsonpath_lib.classification.structural.ssse3_32 uses rsonpath_lib✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.classification.structural.ssse3_32 uses a type in rsonpath_lib.
- The types involved
rsonpath_lib.classification.structural.ssse3_32.Ssse3Classifier32→rsonpath_lib.FallibleIterator
- Direction
- rsonpath_lib.classification.structural.ssse3_32 uses rsonpath_lib, so a change to rsonpath_lib can break rsonpath_lib.classification.structural.ssse3_32, while a change to rsonpath_lib.classification.structural.ssse3_32 can't break rsonpath_lib.
- Position
- Below the diagonal: rsonpath_lib.classification.structural.ssse3_32 uses a module listed above it, which is the healthy direction.
27→2 rsonpath_lib.classification.structural.ssse3_32 uses rsonpath_lib.classification.memmem.shared.vector_128✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.classification.structural.ssse3_32 uses a type in rsonpath_lib.classification.memmem.shared.vector_128.
- The types involved
rsonpath_lib.classification.structural.ssse3_32.BlockSse2Classifier32→rsonpath_lib.classification.memmem.shared.vector_128.BlockClassifier128
- Direction
- rsonpath_lib.classification.structural.ssse3_32 uses rsonpath_lib.classification.memmem.shared.vector_128, so a change to rsonpath_lib.classification.memmem.shared.vector_128 can break rsonpath_lib.classification.structural.ssse3_32, while a change to rsonpath_lib.classification.structural.ssse3_32 can't break rsonpath_lib.classification.memmem.shared.vector_128.
- Position
- Below the diagonal: rsonpath_lib.classification.structural.ssse3_32 uses a module listed above it, which is the healthy direction.
27→9 rsonpath_lib.classification.structural.ssse3_32 uses rsonpath_lib.classification.structural✕
- Connections
- 2 pairs of types, where a type in rsonpath_lib.classification.structural.ssse3_32 uses a type in rsonpath_lib.classification.structural.
- The types involved
rsonpath_lib.classification.structural.ssse3_32.Constructor→rsonpath_lib.classification.structural.StructuralImplrsonpath_lib.classification.structural.ssse3_32.Ssse3Classifier32→rsonpath_lib.classification.structural.StructuralIterator
- Direction
- rsonpath_lib.classification.structural.ssse3_32 uses rsonpath_lib.classification.structural, so a change to rsonpath_lib.classification.structural can break rsonpath_lib.classification.structural.ssse3_32, while a change to rsonpath_lib.classification.structural.ssse3_32 can't break rsonpath_lib.classification.structural.
- Position
- Below the diagonal: rsonpath_lib.classification.structural.ssse3_32 uses a module listed above it, which is the healthy direction.
27→14 rsonpath_lib.classification.structural.ssse3_32 uses rsonpath_lib.classification.quotes✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.classification.structural.ssse3_32 uses a type in rsonpath_lib.classification.quotes.
- The types involved
rsonpath_lib.classification.structural.ssse3_32.BlockSse2Classifier32→rsonpath_lib.classification.quotes.QuoteClassifiedBlock
- Direction
- rsonpath_lib.classification.structural.ssse3_32 uses rsonpath_lib.classification.quotes, so a change to rsonpath_lib.classification.quotes can break rsonpath_lib.classification.structural.ssse3_32, while a change to rsonpath_lib.classification.structural.ssse3_32 can't break rsonpath_lib.classification.quotes.
- Position
- Below the diagonal: rsonpath_lib.classification.structural.ssse3_32 uses a module listed above it, which is the healthy direction.
27→15 rsonpath_lib.classification.structural.ssse3_32 uses rsonpath_lib.classification✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.classification.structural.ssse3_32 uses a type in rsonpath_lib.classification.
- The types involved
rsonpath_lib.classification.structural.ssse3_32.Ssse3Classifier32→rsonpath_lib.classification.ResumeClassifierState
- Direction
- rsonpath_lib.classification.structural.ssse3_32 uses rsonpath_lib.classification, so a change to rsonpath_lib.classification can break rsonpath_lib.classification.structural.ssse3_32, while a change to rsonpath_lib.classification.structural.ssse3_32 can't break rsonpath_lib.classification.
- Position
- Below the diagonal: rsonpath_lib.classification.structural.ssse3_32 uses a module listed above it, which is the healthy direction.
27→19 rsonpath_lib.classification.structural.ssse3_32 uses rsonpath_lib.classification.structural.shared.mask_32✕
- Connections
- 2 pairs of types, where a type in rsonpath_lib.classification.structural.ssse3_32 uses a type in rsonpath_lib.classification.structural.shared.mask_32.
- The types involved
rsonpath_lib.classification.structural.ssse3_32.BlockSse2Classifier32→rsonpath_lib.classification.structural.shared.mask_32.StructuralsBlockrsonpath_lib.classification.structural.ssse3_32.Ssse3Classifier32→rsonpath_lib.classification.structural.shared.mask_32.StructuralsBlock
- Direction
- rsonpath_lib.classification.structural.ssse3_32 uses rsonpath_lib.classification.structural.shared.mask_32, so a change to rsonpath_lib.classification.structural.shared.mask_32 can break rsonpath_lib.classification.structural.ssse3_32, while a change to rsonpath_lib.classification.structural.ssse3_32 can't break rsonpath_lib.classification.structural.shared.mask_32.
- Position
- Below the diagonal: rsonpath_lib.classification.structural.ssse3_32 uses a module listed above it, which is the healthy direction.
28→1 rsonpath_lib.classification.structural.ssse3_64 uses rsonpath_lib✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.classification.structural.ssse3_64 uses a type in rsonpath_lib.
- The types involved
rsonpath_lib.classification.structural.ssse3_64.Ssse3Classifier64→rsonpath_lib.FallibleIterator
- Direction
- rsonpath_lib.classification.structural.ssse3_64 uses rsonpath_lib, so a change to rsonpath_lib can break rsonpath_lib.classification.structural.ssse3_64, while a change to rsonpath_lib.classification.structural.ssse3_64 can't break rsonpath_lib.
- Position
- Below the diagonal: rsonpath_lib.classification.structural.ssse3_64 uses a module listed above it, which is the healthy direction.
28→2 rsonpath_lib.classification.structural.ssse3_64 uses rsonpath_lib.classification.memmem.shared.vector_128✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.classification.structural.ssse3_64 uses a type in rsonpath_lib.classification.memmem.shared.vector_128.
- The types involved
rsonpath_lib.classification.structural.ssse3_64.BlockSse2Classifier64→rsonpath_lib.classification.memmem.shared.vector_128.BlockClassifier128
- Direction
- rsonpath_lib.classification.structural.ssse3_64 uses rsonpath_lib.classification.memmem.shared.vector_128, so a change to rsonpath_lib.classification.memmem.shared.vector_128 can break rsonpath_lib.classification.structural.ssse3_64, while a change to rsonpath_lib.classification.structural.ssse3_64 can't break rsonpath_lib.classification.memmem.shared.vector_128.
- Position
- Below the diagonal: rsonpath_lib.classification.structural.ssse3_64 uses a module listed above it, which is the healthy direction.
28→9 rsonpath_lib.classification.structural.ssse3_64 uses rsonpath_lib.classification.structural✕
- Connections
- 2 pairs of types, where a type in rsonpath_lib.classification.structural.ssse3_64 uses a type in rsonpath_lib.classification.structural.
- The types involved
rsonpath_lib.classification.structural.ssse3_64.Constructor→rsonpath_lib.classification.structural.StructuralImplrsonpath_lib.classification.structural.ssse3_64.Ssse3Classifier64→rsonpath_lib.classification.structural.StructuralIterator
- Direction
- rsonpath_lib.classification.structural.ssse3_64 uses rsonpath_lib.classification.structural, so a change to rsonpath_lib.classification.structural can break rsonpath_lib.classification.structural.ssse3_64, while a change to rsonpath_lib.classification.structural.ssse3_64 can't break rsonpath_lib.classification.structural.
- Position
- Below the diagonal: rsonpath_lib.classification.structural.ssse3_64 uses a module listed above it, which is the healthy direction.
28→14 rsonpath_lib.classification.structural.ssse3_64 uses rsonpath_lib.classification.quotes✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.classification.structural.ssse3_64 uses a type in rsonpath_lib.classification.quotes.
- The types involved
rsonpath_lib.classification.structural.ssse3_64.BlockSse2Classifier64→rsonpath_lib.classification.quotes.QuoteClassifiedBlock
- Direction
- rsonpath_lib.classification.structural.ssse3_64 uses rsonpath_lib.classification.quotes, so a change to rsonpath_lib.classification.quotes can break rsonpath_lib.classification.structural.ssse3_64, while a change to rsonpath_lib.classification.structural.ssse3_64 can't break rsonpath_lib.classification.quotes.
- Position
- Below the diagonal: rsonpath_lib.classification.structural.ssse3_64 uses a module listed above it, which is the healthy direction.
28→15 rsonpath_lib.classification.structural.ssse3_64 uses rsonpath_lib.classification✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.classification.structural.ssse3_64 uses a type in rsonpath_lib.classification.
- The types involved
rsonpath_lib.classification.structural.ssse3_64.Ssse3Classifier64→rsonpath_lib.classification.ResumeClassifierState
- Direction
- rsonpath_lib.classification.structural.ssse3_64 uses rsonpath_lib.classification, so a change to rsonpath_lib.classification can break rsonpath_lib.classification.structural.ssse3_64, while a change to rsonpath_lib.classification.structural.ssse3_64 can't break rsonpath_lib.classification.
- Position
- Below the diagonal: rsonpath_lib.classification.structural.ssse3_64 uses a module listed above it, which is the healthy direction.
28→19 rsonpath_lib.classification.structural.ssse3_64 uses rsonpath_lib.classification.structural.shared.mask_32✕
- Connections
- 2 pairs of types, where a type in rsonpath_lib.classification.structural.ssse3_64 uses a type in rsonpath_lib.classification.structural.shared.mask_32.
- The types involved
rsonpath_lib.classification.structural.ssse3_64.BlockSse2Classifier64→rsonpath_lib.classification.structural.shared.mask_32.StructuralsBlockrsonpath_lib.classification.structural.ssse3_64.Ssse3Classifier64→rsonpath_lib.classification.structural.shared.mask_32.StructuralsBlock
- Direction
- rsonpath_lib.classification.structural.ssse3_64 uses rsonpath_lib.classification.structural.shared.mask_32, so a change to rsonpath_lib.classification.structural.shared.mask_32 can break rsonpath_lib.classification.structural.ssse3_64, while a change to rsonpath_lib.classification.structural.ssse3_64 can't break rsonpath_lib.classification.structural.shared.mask_32.
- Position
- Below the diagonal: rsonpath_lib.classification.structural.ssse3_64 uses a module listed above it, which is the healthy direction.
29→4 rsonpath_lib.engine.head_skipping uses rsonpath_lib.string_pattern✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.engine.head_skipping uses a type in rsonpath_lib.string_pattern.
- The types involved
rsonpath_lib.engine.head_skipping.HeadSkip→rsonpath_lib.string_pattern.StringPattern
- Direction
- rsonpath_lib.engine.head_skipping uses rsonpath_lib.string_pattern, so a change to rsonpath_lib.string_pattern can break rsonpath_lib.engine.head_skipping, while a change to rsonpath_lib.engine.head_skipping can't break rsonpath_lib.string_pattern.
- Position
- Below the diagonal: rsonpath_lib.engine.head_skipping uses a module listed above it, which is the healthy direction.
29→8 rsonpath_lib.engine.head_skipping uses rsonpath_lib.automaton✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.engine.head_skipping uses a type in rsonpath_lib.automaton.
- The types involved
rsonpath_lib.engine.head_skipping.HeadSkip→rsonpath_lib.automaton.Automaton
- Direction
- rsonpath_lib.engine.head_skipping uses rsonpath_lib.automaton, so a change to rsonpath_lib.automaton can break rsonpath_lib.engine.head_skipping, while a change to rsonpath_lib.engine.head_skipping can't break rsonpath_lib.automaton.
- Position
- Below the diagonal: rsonpath_lib.engine.head_skipping uses a module listed above it, which is the healthy direction.
29→9 rsonpath_lib.engine.head_skipping uses rsonpath_lib.classification.structural✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.engine.head_skipping uses a type in rsonpath_lib.classification.structural.
- The types involved
rsonpath_lib.engine.head_skipping.CanHeadSkip→rsonpath_lib.classification.structural.Structural
- Direction
- rsonpath_lib.engine.head_skipping uses rsonpath_lib.classification.structural, so a change to rsonpath_lib.classification.structural can break rsonpath_lib.engine.head_skipping, while a change to rsonpath_lib.engine.head_skipping can't break rsonpath_lib.classification.structural.
- Position
- Below the diagonal: rsonpath_lib.engine.head_skipping uses a module listed above it, which is the healthy direction.
29→15 rsonpath_lib.engine.head_skipping uses rsonpath_lib.classification✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.engine.head_skipping uses a type in rsonpath_lib.classification.
- The types involved
rsonpath_lib.engine.head_skipping.ResumeState→rsonpath_lib.classification.ResumeClassifierState
- Direction
- rsonpath_lib.engine.head_skipping uses rsonpath_lib.classification, so a change to rsonpath_lib.classification can break rsonpath_lib.engine.head_skipping, while a change to rsonpath_lib.engine.head_skipping can't break rsonpath_lib.classification.
- Position
- Below the diagonal: rsonpath_lib.engine.head_skipping uses a module listed above it, which is the healthy direction.
30→1 rsonpath_lib.classification.depth.avx2_32 uses rsonpath_lib✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.classification.depth.avx2_32 uses a type in rsonpath_lib.
- The types involved
rsonpath_lib.classification.depth.avx2_32.Avx2VectorIterator32→rsonpath_lib.FallibleIterator
- Direction
- rsonpath_lib.classification.depth.avx2_32 uses rsonpath_lib, so a change to rsonpath_lib can break rsonpath_lib.classification.depth.avx2_32, while a change to rsonpath_lib.classification.depth.avx2_32 can't break rsonpath_lib.
- Position
- Below the diagonal: rsonpath_lib.classification.depth.avx2_32 uses a module listed above it, which is the healthy direction.
30→9 rsonpath_lib.classification.depth.avx2_32 uses rsonpath_lib.classification.structural✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.classification.depth.avx2_32 uses a type in rsonpath_lib.classification.structural.
- The types involved
rsonpath_lib.classification.depth.avx2_32.Avx2VectorIterator32→rsonpath_lib.classification.structural.BracketType
- Direction
- rsonpath_lib.classification.depth.avx2_32 uses rsonpath_lib.classification.structural, so a change to rsonpath_lib.classification.structural can break rsonpath_lib.classification.depth.avx2_32, while a change to rsonpath_lib.classification.depth.avx2_32 can't break rsonpath_lib.classification.structural.
- Position
- Below the diagonal: rsonpath_lib.classification.depth.avx2_32 uses a module listed above it, which is the healthy direction.
30→12 rsonpath_lib.classification.depth.avx2_32 uses rsonpath_lib.classification.structural.nosimd✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.classification.depth.avx2_32 uses a type in rsonpath_lib.classification.structural.nosimd.
- The types involved
rsonpath_lib.classification.depth.avx2_32.Avx2VectorIterator32→rsonpath_lib.classification.structural.nosimd.Block
- Direction
- rsonpath_lib.classification.depth.avx2_32 uses rsonpath_lib.classification.structural.nosimd, so a change to rsonpath_lib.classification.structural.nosimd can break rsonpath_lib.classification.depth.avx2_32, while a change to rsonpath_lib.classification.depth.avx2_32 can't break rsonpath_lib.classification.structural.nosimd.
- Position
- Below the diagonal: rsonpath_lib.classification.depth.avx2_32 uses a module listed above it, which is the healthy direction.
30→14 rsonpath_lib.classification.depth.avx2_32 uses rsonpath_lib.classification.quotes✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.classification.depth.avx2_32 uses a type in rsonpath_lib.classification.quotes.
- The types involved
rsonpath_lib.classification.depth.avx2_32.avx2_32$module→rsonpath_lib.classification.quotes.QuoteClassifiedBlock
- Direction
- rsonpath_lib.classification.depth.avx2_32 uses rsonpath_lib.classification.quotes, so a change to rsonpath_lib.classification.quotes can break rsonpath_lib.classification.depth.avx2_32, while a change to rsonpath_lib.classification.depth.avx2_32 can't break rsonpath_lib.classification.quotes.
- Position
- Below the diagonal: rsonpath_lib.classification.depth.avx2_32 uses a module listed above it, which is the healthy direction.
30→15 rsonpath_lib.classification.depth.avx2_32 uses rsonpath_lib.classification✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.classification.depth.avx2_32 uses a type in rsonpath_lib.classification.
- The types involved
rsonpath_lib.classification.depth.avx2_32.Avx2VectorIterator32→rsonpath_lib.classification.ResumeClassifierState
- Direction
- rsonpath_lib.classification.depth.avx2_32 uses rsonpath_lib.classification, so a change to rsonpath_lib.classification can break rsonpath_lib.classification.depth.avx2_32, while a change to rsonpath_lib.classification.depth.avx2_32 can't break rsonpath_lib.classification.
- Position
- Below the diagonal: rsonpath_lib.classification.depth.avx2_32 uses a module listed above it, which is the healthy direction.
30→20 rsonpath_lib.classification.depth.avx2_32 uses rsonpath_lib.classification.depth✕
- Connections
- 2 pairs of types, where a type in rsonpath_lib.classification.depth.avx2_32 uses a type in rsonpath_lib.classification.depth.
- The types involved
rsonpath_lib.classification.depth.avx2_32.Avx2VectorIterator32→rsonpath_lib.classification.depth.DepthIteratorrsonpath_lib.classification.depth.avx2_32.Constructor→rsonpath_lib.classification.depth.DepthImpl
- Direction
- rsonpath_lib.classification.depth.avx2_32 uses rsonpath_lib.classification.depth, so a change to rsonpath_lib.classification.depth can break rsonpath_lib.classification.depth.avx2_32, while a change to rsonpath_lib.classification.depth.avx2_32 can't break rsonpath_lib.classification.depth.
- Position
- Below the diagonal: rsonpath_lib.classification.depth.avx2_32 uses a module listed above it, which is the healthy direction.
31→1 rsonpath_lib.classification.depth.nosimd uses rsonpath_lib✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.classification.depth.nosimd uses a type in rsonpath_lib.
- The types involved
rsonpath_lib.classification.depth.nosimd.VectorIterator→rsonpath_lib.FallibleIterator
- Direction
- rsonpath_lib.classification.depth.nosimd uses rsonpath_lib, so a change to rsonpath_lib can break rsonpath_lib.classification.depth.nosimd, while a change to rsonpath_lib.classification.depth.nosimd can't break rsonpath_lib.
- Position
- Below the diagonal: rsonpath_lib.classification.depth.nosimd uses a module listed above it, which is the healthy direction.
31→9 rsonpath_lib.classification.depth.nosimd uses rsonpath_lib.classification.structural✕
- Connections
- 2 pairs of types, where a type in rsonpath_lib.classification.depth.nosimd uses a type in rsonpath_lib.classification.structural.
- The types involved
rsonpath_lib.classification.depth.nosimd.Vector→rsonpath_lib.classification.structural.BracketTypersonpath_lib.classification.depth.nosimd.VectorIterator→rsonpath_lib.classification.structural.BracketType
- Direction
- rsonpath_lib.classification.depth.nosimd uses rsonpath_lib.classification.structural, so a change to rsonpath_lib.classification.structural can break rsonpath_lib.classification.depth.nosimd, while a change to rsonpath_lib.classification.depth.nosimd can't break rsonpath_lib.classification.structural.
- Position
- Below the diagonal: rsonpath_lib.classification.depth.nosimd uses a module listed above it, which is the healthy direction.
31→12 rsonpath_lib.classification.depth.nosimd uses rsonpath_lib.classification.structural.nosimd✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.classification.depth.nosimd uses a type in rsonpath_lib.classification.structural.nosimd.
- The types involved
rsonpath_lib.classification.depth.nosimd.VectorIterator→rsonpath_lib.classification.structural.nosimd.Block
- Direction
- rsonpath_lib.classification.depth.nosimd uses rsonpath_lib.classification.structural.nosimd, so a change to rsonpath_lib.classification.structural.nosimd can break rsonpath_lib.classification.depth.nosimd, while a change to rsonpath_lib.classification.depth.nosimd can't break rsonpath_lib.classification.structural.nosimd.
- Position
- Below the diagonal: rsonpath_lib.classification.depth.nosimd uses a module listed above it, which is the healthy direction.
31→14 rsonpath_lib.classification.depth.nosimd uses rsonpath_lib.classification.quotes✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.classification.depth.nosimd uses a type in rsonpath_lib.classification.quotes.
- The types involved
rsonpath_lib.classification.depth.nosimd.Vector→rsonpath_lib.classification.quotes.QuoteClassifiedBlock
- Direction
- rsonpath_lib.classification.depth.nosimd uses rsonpath_lib.classification.quotes, so a change to rsonpath_lib.classification.quotes can break rsonpath_lib.classification.depth.nosimd, while a change to rsonpath_lib.classification.depth.nosimd can't break rsonpath_lib.classification.quotes.
- Position
- Below the diagonal: rsonpath_lib.classification.depth.nosimd uses a module listed above it, which is the healthy direction.
31→15 rsonpath_lib.classification.depth.nosimd uses rsonpath_lib.classification✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.classification.depth.nosimd uses a type in rsonpath_lib.classification.
- The types involved
rsonpath_lib.classification.depth.nosimd.VectorIterator→rsonpath_lib.classification.ResumeClassifierState
- Direction
- rsonpath_lib.classification.depth.nosimd uses rsonpath_lib.classification, so a change to rsonpath_lib.classification can break rsonpath_lib.classification.depth.nosimd, while a change to rsonpath_lib.classification.depth.nosimd can't break rsonpath_lib.classification.
- Position
- Below the diagonal: rsonpath_lib.classification.depth.nosimd uses a module listed above it, which is the healthy direction.
31→20 rsonpath_lib.classification.depth.nosimd uses rsonpath_lib.classification.depth✕
- Connections
- 3 pairs of types, where a type in rsonpath_lib.classification.depth.nosimd uses a type in rsonpath_lib.classification.depth.
- The types involved
rsonpath_lib.classification.depth.nosimd.Constructor→rsonpath_lib.classification.depth.DepthImplrsonpath_lib.classification.depth.nosimd.Vector→rsonpath_lib.classification.depth.DepthBlockrsonpath_lib.classification.depth.nosimd.VectorIterator→rsonpath_lib.classification.depth.DepthIterator
- Direction
- rsonpath_lib.classification.depth.nosimd uses rsonpath_lib.classification.depth, so a change to rsonpath_lib.classification.depth can break rsonpath_lib.classification.depth.nosimd, while a change to rsonpath_lib.classification.depth.nosimd can't break rsonpath_lib.classification.depth.
- Position
- Below the diagonal: rsonpath_lib.classification.depth.nosimd uses a module listed above it, which is the healthy direction.
32→14 rsonpath_lib.classification.depth.shared.mask_64 uses rsonpath_lib.classification.quotes✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.classification.depth.shared.mask_64 uses a type in rsonpath_lib.classification.quotes.
- The types involved
rsonpath_lib.classification.depth.shared.mask_64.DepthVector64→rsonpath_lib.classification.quotes.QuoteClassifiedBlock
- Direction
- rsonpath_lib.classification.depth.shared.mask_64 uses rsonpath_lib.classification.quotes, so a change to rsonpath_lib.classification.quotes can break rsonpath_lib.classification.depth.shared.mask_64, while a change to rsonpath_lib.classification.depth.shared.mask_64 can't break rsonpath_lib.classification.quotes.
- Position
- Below the diagonal: rsonpath_lib.classification.depth.shared.mask_64 uses a module listed above it, which is the healthy direction.
32→20 rsonpath_lib.classification.depth.shared.mask_64 uses rsonpath_lib.classification.depth✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.classification.depth.shared.mask_64 uses a type in rsonpath_lib.classification.depth.
- The types involved
rsonpath_lib.classification.depth.shared.mask_64.DepthVector64→rsonpath_lib.classification.depth.DepthBlock
- Direction
- rsonpath_lib.classification.depth.shared.mask_64 uses rsonpath_lib.classification.depth, so a change to rsonpath_lib.classification.depth can break rsonpath_lib.classification.depth.shared.mask_64, while a change to rsonpath_lib.classification.depth.shared.mask_64 can't break rsonpath_lib.classification.depth.
- Position
- Below the diagonal: rsonpath_lib.classification.depth.shared.mask_64 uses a module listed above it, which is the healthy direction.
33→1 rsonpath_lib.classification.depth.sse2_32 uses rsonpath_lib✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.classification.depth.sse2_32 uses a type in rsonpath_lib.
- The types involved
rsonpath_lib.classification.depth.sse2_32.Sse2VectorIterator32→rsonpath_lib.FallibleIterator
- Direction
- rsonpath_lib.classification.depth.sse2_32 uses rsonpath_lib, so a change to rsonpath_lib can break rsonpath_lib.classification.depth.sse2_32, while a change to rsonpath_lib.classification.depth.sse2_32 can't break rsonpath_lib.
- Position
- Below the diagonal: rsonpath_lib.classification.depth.sse2_32 uses a module listed above it, which is the healthy direction.
33→9 rsonpath_lib.classification.depth.sse2_32 uses rsonpath_lib.classification.structural✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.classification.depth.sse2_32 uses a type in rsonpath_lib.classification.structural.
- The types involved
rsonpath_lib.classification.depth.sse2_32.Sse2VectorIterator32→rsonpath_lib.classification.structural.BracketType
- Direction
- rsonpath_lib.classification.depth.sse2_32 uses rsonpath_lib.classification.structural, so a change to rsonpath_lib.classification.structural can break rsonpath_lib.classification.depth.sse2_32, while a change to rsonpath_lib.classification.depth.sse2_32 can't break rsonpath_lib.classification.structural.
- Position
- Below the diagonal: rsonpath_lib.classification.depth.sse2_32 uses a module listed above it, which is the healthy direction.
33→12 rsonpath_lib.classification.depth.sse2_32 uses rsonpath_lib.classification.structural.nosimd✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.classification.depth.sse2_32 uses a type in rsonpath_lib.classification.structural.nosimd.
- The types involved
rsonpath_lib.classification.depth.sse2_32.Sse2VectorIterator32→rsonpath_lib.classification.structural.nosimd.Block
- Direction
- rsonpath_lib.classification.depth.sse2_32 uses rsonpath_lib.classification.structural.nosimd, so a change to rsonpath_lib.classification.structural.nosimd can break rsonpath_lib.classification.depth.sse2_32, while a change to rsonpath_lib.classification.depth.sse2_32 can't break rsonpath_lib.classification.structural.nosimd.
- Position
- Below the diagonal: rsonpath_lib.classification.depth.sse2_32 uses a module listed above it, which is the healthy direction.
33→14 rsonpath_lib.classification.depth.sse2_32 uses rsonpath_lib.classification.quotes✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.classification.depth.sse2_32 uses a type in rsonpath_lib.classification.quotes.
- The types involved
rsonpath_lib.classification.depth.sse2_32.sse2_32$module→rsonpath_lib.classification.quotes.QuoteClassifiedBlock
- Direction
- rsonpath_lib.classification.depth.sse2_32 uses rsonpath_lib.classification.quotes, so a change to rsonpath_lib.classification.quotes can break rsonpath_lib.classification.depth.sse2_32, while a change to rsonpath_lib.classification.depth.sse2_32 can't break rsonpath_lib.classification.quotes.
- Position
- Below the diagonal: rsonpath_lib.classification.depth.sse2_32 uses a module listed above it, which is the healthy direction.
33→15 rsonpath_lib.classification.depth.sse2_32 uses rsonpath_lib.classification✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.classification.depth.sse2_32 uses a type in rsonpath_lib.classification.
- The types involved
rsonpath_lib.classification.depth.sse2_32.Sse2VectorIterator32→rsonpath_lib.classification.ResumeClassifierState
- Direction
- rsonpath_lib.classification.depth.sse2_32 uses rsonpath_lib.classification, so a change to rsonpath_lib.classification can break rsonpath_lib.classification.depth.sse2_32, while a change to rsonpath_lib.classification.depth.sse2_32 can't break rsonpath_lib.classification.
- Position
- Below the diagonal: rsonpath_lib.classification.depth.sse2_32 uses a module listed above it, which is the healthy direction.
33→20 rsonpath_lib.classification.depth.sse2_32 uses rsonpath_lib.classification.depth✕
- Connections
- 2 pairs of types, where a type in rsonpath_lib.classification.depth.sse2_32 uses a type in rsonpath_lib.classification.depth.
- The types involved
rsonpath_lib.classification.depth.sse2_32.Constructor→rsonpath_lib.classification.depth.DepthImplrsonpath_lib.classification.depth.sse2_32.Sse2VectorIterator32→rsonpath_lib.classification.depth.DepthIterator
- Direction
- rsonpath_lib.classification.depth.sse2_32 uses rsonpath_lib.classification.depth, so a change to rsonpath_lib.classification.depth can break rsonpath_lib.classification.depth.sse2_32, while a change to rsonpath_lib.classification.depth.sse2_32 can't break rsonpath_lib.classification.depth.
- Position
- Below the diagonal: rsonpath_lib.classification.depth.sse2_32 uses a module listed above it, which is the healthy direction.
34→9 rsonpath_lib.classification.simd uses rsonpath_lib.classification.structural✕
- Connections
- 2 pairs of types, where a type in rsonpath_lib.classification.simd uses a type in rsonpath_lib.classification.structural.
- The types involved
rsonpath_lib.classification.simd.ResolvedSimd→rsonpath_lib.classification.structural.BracketTypersonpath_lib.classification.simd.Simd→rsonpath_lib.classification.structural.BracketType
- Direction
- rsonpath_lib.classification.simd uses rsonpath_lib.classification.structural, so a change to rsonpath_lib.classification.structural can break rsonpath_lib.classification.simd, while a change to rsonpath_lib.classification.simd can't break rsonpath_lib.classification.structural.
- Position
- Below the diagonal: rsonpath_lib.classification.simd uses a module listed above it, which is the healthy direction.
34→12 rsonpath_lib.classification.simd uses rsonpath_lib.classification.structural.nosimd✕
- Connections
- 2 pairs of types, where a type in rsonpath_lib.classification.simd uses a type in rsonpath_lib.classification.structural.nosimd.
- The types involved
rsonpath_lib.classification.simd.ResolvedSimd→rsonpath_lib.classification.structural.nosimd.Blockrsonpath_lib.classification.simd.Simd→rsonpath_lib.classification.structural.nosimd.Block
- Direction
- rsonpath_lib.classification.simd uses rsonpath_lib.classification.structural.nosimd, so a change to rsonpath_lib.classification.structural.nosimd can break rsonpath_lib.classification.simd, while a change to rsonpath_lib.classification.simd can't break rsonpath_lib.classification.structural.nosimd.
- Position
- Below the diagonal: rsonpath_lib.classification.simd uses a module listed above it, which is the healthy direction.
34→14 rsonpath_lib.classification.simd uses rsonpath_lib.classification.quotes✕
- Connections
- 2 pairs of types, where a type in rsonpath_lib.classification.simd uses a type in rsonpath_lib.classification.quotes.
- The types involved
rsonpath_lib.classification.simd.ResolvedSimd→rsonpath_lib.classification.quotes.ResumedQuoteClassifierrsonpath_lib.classification.simd.Simd→rsonpath_lib.classification.quotes.ResumedQuoteClassifier
- Direction
- rsonpath_lib.classification.simd uses rsonpath_lib.classification.quotes, so a change to rsonpath_lib.classification.quotes can break rsonpath_lib.classification.simd, while a change to rsonpath_lib.classification.simd can't break rsonpath_lib.classification.quotes.
- Position
- Below the diagonal: rsonpath_lib.classification.simd uses a module listed above it, which is the healthy direction.
34→15 rsonpath_lib.classification.simd uses rsonpath_lib.classification✕
- Connections
- 2 pairs of types, where a type in rsonpath_lib.classification.simd uses a type in rsonpath_lib.classification.
- The types involved
rsonpath_lib.classification.simd.ResolvedSimd→rsonpath_lib.classification.ResumeClassifierStatersonpath_lib.classification.simd.Simd→rsonpath_lib.classification.ResumeClassifierState
- Direction
- rsonpath_lib.classification.simd uses rsonpath_lib.classification, so a change to rsonpath_lib.classification can break rsonpath_lib.classification.simd, while a change to rsonpath_lib.classification.simd can't break rsonpath_lib.classification.
- Position
- Below the diagonal: rsonpath_lib.classification.simd uses a module listed above it, which is the healthy direction.
34→20 rsonpath_lib.classification.simd uses rsonpath_lib.classification.depth✕
- Connections
- 2 pairs of types, where a type in rsonpath_lib.classification.simd uses a type in rsonpath_lib.classification.depth.
- The types involved
rsonpath_lib.classification.simd.ResolvedSimd→rsonpath_lib.classification.depth.DepthIteratorResumeOutcomersonpath_lib.classification.simd.Simd→rsonpath_lib.classification.depth.DepthIteratorResumeOutcome
- Direction
- rsonpath_lib.classification.simd uses rsonpath_lib.classification.depth, so a change to rsonpath_lib.classification.depth can break rsonpath_lib.classification.simd, while a change to rsonpath_lib.classification.simd can't break rsonpath_lib.classification.depth.
- Position
- Below the diagonal: rsonpath_lib.classification.simd uses a module listed above it, which is the healthy direction.
35→1 rsonpath_lib.classification.depth.avx2_64 uses rsonpath_lib✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.classification.depth.avx2_64 uses a type in rsonpath_lib.
- The types involved
rsonpath_lib.classification.depth.avx2_64.Avx2VectorIterator64→rsonpath_lib.FallibleIterator
- Direction
- rsonpath_lib.classification.depth.avx2_64 uses rsonpath_lib, so a change to rsonpath_lib can break rsonpath_lib.classification.depth.avx2_64, while a change to rsonpath_lib.classification.depth.avx2_64 can't break rsonpath_lib.
- Position
- Below the diagonal: rsonpath_lib.classification.depth.avx2_64 uses a module listed above it, which is the healthy direction.
35→9 rsonpath_lib.classification.depth.avx2_64 uses rsonpath_lib.classification.structural✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.classification.depth.avx2_64 uses a type in rsonpath_lib.classification.structural.
- The types involved
rsonpath_lib.classification.depth.avx2_64.Avx2VectorIterator64→rsonpath_lib.classification.structural.BracketType
- Direction
- rsonpath_lib.classification.depth.avx2_64 uses rsonpath_lib.classification.structural, so a change to rsonpath_lib.classification.structural can break rsonpath_lib.classification.depth.avx2_64, while a change to rsonpath_lib.classification.depth.avx2_64 can't break rsonpath_lib.classification.structural.
- Position
- Below the diagonal: rsonpath_lib.classification.depth.avx2_64 uses a module listed above it, which is the healthy direction.
35→12 rsonpath_lib.classification.depth.avx2_64 uses rsonpath_lib.classification.structural.nosimd✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.classification.depth.avx2_64 uses a type in rsonpath_lib.classification.structural.nosimd.
- The types involved
rsonpath_lib.classification.depth.avx2_64.Avx2VectorIterator64→rsonpath_lib.classification.structural.nosimd.Block
- Direction
- rsonpath_lib.classification.depth.avx2_64 uses rsonpath_lib.classification.structural.nosimd, so a change to rsonpath_lib.classification.structural.nosimd can break rsonpath_lib.classification.depth.avx2_64, while a change to rsonpath_lib.classification.depth.avx2_64 can't break rsonpath_lib.classification.structural.nosimd.
- Position
- Below the diagonal: rsonpath_lib.classification.depth.avx2_64 uses a module listed above it, which is the healthy direction.
35→14 rsonpath_lib.classification.depth.avx2_64 uses rsonpath_lib.classification.quotes✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.classification.depth.avx2_64 uses a type in rsonpath_lib.classification.quotes.
- The types involved
rsonpath_lib.classification.depth.avx2_64.avx2_64$module→rsonpath_lib.classification.quotes.QuoteClassifiedBlock
- Direction
- rsonpath_lib.classification.depth.avx2_64 uses rsonpath_lib.classification.quotes, so a change to rsonpath_lib.classification.quotes can break rsonpath_lib.classification.depth.avx2_64, while a change to rsonpath_lib.classification.depth.avx2_64 can't break rsonpath_lib.classification.quotes.
- Position
- Below the diagonal: rsonpath_lib.classification.depth.avx2_64 uses a module listed above it, which is the healthy direction.
35→15 rsonpath_lib.classification.depth.avx2_64 uses rsonpath_lib.classification✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.classification.depth.avx2_64 uses a type in rsonpath_lib.classification.
- The types involved
rsonpath_lib.classification.depth.avx2_64.Avx2VectorIterator64→rsonpath_lib.classification.ResumeClassifierState
- Direction
- rsonpath_lib.classification.depth.avx2_64 uses rsonpath_lib.classification, so a change to rsonpath_lib.classification can break rsonpath_lib.classification.depth.avx2_64, while a change to rsonpath_lib.classification.depth.avx2_64 can't break rsonpath_lib.classification.
- Position
- Below the diagonal: rsonpath_lib.classification.depth.avx2_64 uses a module listed above it, which is the healthy direction.
35→20 rsonpath_lib.classification.depth.avx2_64 uses rsonpath_lib.classification.depth✕
- Connections
- 2 pairs of types, where a type in rsonpath_lib.classification.depth.avx2_64 uses a type in rsonpath_lib.classification.depth.
- The types involved
rsonpath_lib.classification.depth.avx2_64.Avx2VectorIterator64→rsonpath_lib.classification.depth.DepthIteratorrsonpath_lib.classification.depth.avx2_64.Constructor→rsonpath_lib.classification.depth.DepthImpl
- Direction
- rsonpath_lib.classification.depth.avx2_64 uses rsonpath_lib.classification.depth, so a change to rsonpath_lib.classification.depth can break rsonpath_lib.classification.depth.avx2_64, while a change to rsonpath_lib.classification.depth.avx2_64 can't break rsonpath_lib.classification.depth.
- Position
- Below the diagonal: rsonpath_lib.classification.depth.avx2_64 uses a module listed above it, which is the healthy direction.
35→32 rsonpath_lib.classification.depth.avx2_64 uses rsonpath_lib.classification.depth.shared.mask_64✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.classification.depth.avx2_64 uses a type in rsonpath_lib.classification.depth.shared.mask_64.
- The types involved
rsonpath_lib.classification.depth.avx2_64.avx2_64$module→rsonpath_lib.classification.depth.shared.mask_64.DepthVector64
- Direction
- rsonpath_lib.classification.depth.avx2_64 uses rsonpath_lib.classification.depth.shared.mask_64, so a change to rsonpath_lib.classification.depth.shared.mask_64 can break rsonpath_lib.classification.depth.avx2_64, while a change to rsonpath_lib.classification.depth.avx2_64 can't break rsonpath_lib.classification.depth.shared.mask_64.
- Position
- Below the diagonal: rsonpath_lib.classification.depth.avx2_64 uses a module listed above it, which is the healthy direction.
36→1 rsonpath_lib.classification.depth.avx512_64 uses rsonpath_lib✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.classification.depth.avx512_64 uses a type in rsonpath_lib.
- The types involved
rsonpath_lib.classification.depth.avx512_64.Avx512VectorIterator64→rsonpath_lib.FallibleIterator
- Direction
- rsonpath_lib.classification.depth.avx512_64 uses rsonpath_lib, so a change to rsonpath_lib can break rsonpath_lib.classification.depth.avx512_64, while a change to rsonpath_lib.classification.depth.avx512_64 can't break rsonpath_lib.
- Position
- Below the diagonal: rsonpath_lib.classification.depth.avx512_64 uses a module listed above it, which is the healthy direction.
36→9 rsonpath_lib.classification.depth.avx512_64 uses rsonpath_lib.classification.structural✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.classification.depth.avx512_64 uses a type in rsonpath_lib.classification.structural.
- The types involved
rsonpath_lib.classification.depth.avx512_64.Avx512VectorIterator64→rsonpath_lib.classification.structural.BracketType
- Direction
- rsonpath_lib.classification.depth.avx512_64 uses rsonpath_lib.classification.structural, so a change to rsonpath_lib.classification.structural can break rsonpath_lib.classification.depth.avx512_64, while a change to rsonpath_lib.classification.depth.avx512_64 can't break rsonpath_lib.classification.structural.
- Position
- Below the diagonal: rsonpath_lib.classification.depth.avx512_64 uses a module listed above it, which is the healthy direction.
36→12 rsonpath_lib.classification.depth.avx512_64 uses rsonpath_lib.classification.structural.nosimd✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.classification.depth.avx512_64 uses a type in rsonpath_lib.classification.structural.nosimd.
- The types involved
rsonpath_lib.classification.depth.avx512_64.Avx512VectorIterator64→rsonpath_lib.classification.structural.nosimd.Block
- Direction
- rsonpath_lib.classification.depth.avx512_64 uses rsonpath_lib.classification.structural.nosimd, so a change to rsonpath_lib.classification.structural.nosimd can break rsonpath_lib.classification.depth.avx512_64, while a change to rsonpath_lib.classification.depth.avx512_64 can't break rsonpath_lib.classification.structural.nosimd.
- Position
- Below the diagonal: rsonpath_lib.classification.depth.avx512_64 uses a module listed above it, which is the healthy direction.
36→14 rsonpath_lib.classification.depth.avx512_64 uses rsonpath_lib.classification.quotes✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.classification.depth.avx512_64 uses a type in rsonpath_lib.classification.quotes.
- The types involved
rsonpath_lib.classification.depth.avx512_64.avx512_64$module→rsonpath_lib.classification.quotes.QuoteClassifiedBlock
- Direction
- rsonpath_lib.classification.depth.avx512_64 uses rsonpath_lib.classification.quotes, so a change to rsonpath_lib.classification.quotes can break rsonpath_lib.classification.depth.avx512_64, while a change to rsonpath_lib.classification.depth.avx512_64 can't break rsonpath_lib.classification.quotes.
- Position
- Below the diagonal: rsonpath_lib.classification.depth.avx512_64 uses a module listed above it, which is the healthy direction.
36→15 rsonpath_lib.classification.depth.avx512_64 uses rsonpath_lib.classification✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.classification.depth.avx512_64 uses a type in rsonpath_lib.classification.
- The types involved
rsonpath_lib.classification.depth.avx512_64.Avx512VectorIterator64→rsonpath_lib.classification.ResumeClassifierState
- Direction
- rsonpath_lib.classification.depth.avx512_64 uses rsonpath_lib.classification, so a change to rsonpath_lib.classification can break rsonpath_lib.classification.depth.avx512_64, while a change to rsonpath_lib.classification.depth.avx512_64 can't break rsonpath_lib.classification.
- Position
- Below the diagonal: rsonpath_lib.classification.depth.avx512_64 uses a module listed above it, which is the healthy direction.
36→20 rsonpath_lib.classification.depth.avx512_64 uses rsonpath_lib.classification.depth✕
- Connections
- 2 pairs of types, where a type in rsonpath_lib.classification.depth.avx512_64 uses a type in rsonpath_lib.classification.depth.
- The types involved
rsonpath_lib.classification.depth.avx512_64.Avx512VectorIterator64→rsonpath_lib.classification.depth.DepthIteratorrsonpath_lib.classification.depth.avx512_64.Constructor→rsonpath_lib.classification.depth.DepthImpl
- Direction
- rsonpath_lib.classification.depth.avx512_64 uses rsonpath_lib.classification.depth, so a change to rsonpath_lib.classification.depth can break rsonpath_lib.classification.depth.avx512_64, while a change to rsonpath_lib.classification.depth.avx512_64 can't break rsonpath_lib.classification.depth.
- Position
- Below the diagonal: rsonpath_lib.classification.depth.avx512_64 uses a module listed above it, which is the healthy direction.
36→32 rsonpath_lib.classification.depth.avx512_64 uses rsonpath_lib.classification.depth.shared.mask_64✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.classification.depth.avx512_64 uses a type in rsonpath_lib.classification.depth.shared.mask_64.
- The types involved
rsonpath_lib.classification.depth.avx512_64.avx512_64$module→rsonpath_lib.classification.depth.shared.mask_64.DepthVector64
- Direction
- rsonpath_lib.classification.depth.avx512_64 uses rsonpath_lib.classification.depth.shared.mask_64, so a change to rsonpath_lib.classification.depth.shared.mask_64 can break rsonpath_lib.classification.depth.avx512_64, while a change to rsonpath_lib.classification.depth.avx512_64 can't break rsonpath_lib.classification.depth.shared.mask_64.
- Position
- Below the diagonal: rsonpath_lib.classification.depth.avx512_64 uses a module listed above it, which is the healthy direction.
37→1 rsonpath_lib.classification.depth.neon_64 uses rsonpath_lib✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.classification.depth.neon_64 uses a type in rsonpath_lib.
- The types involved
rsonpath_lib.classification.depth.neon_64.NeonVectorIterator→rsonpath_lib.FallibleIterator
- Direction
- rsonpath_lib.classification.depth.neon_64 uses rsonpath_lib, so a change to rsonpath_lib can break rsonpath_lib.classification.depth.neon_64, while a change to rsonpath_lib.classification.depth.neon_64 can't break rsonpath_lib.
- Position
- Below the diagonal: rsonpath_lib.classification.depth.neon_64 uses a module listed above it, which is the healthy direction.
37→9 rsonpath_lib.classification.depth.neon_64 uses rsonpath_lib.classification.structural✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.classification.depth.neon_64 uses a type in rsonpath_lib.classification.structural.
- The types involved
rsonpath_lib.classification.depth.neon_64.NeonVectorIterator→rsonpath_lib.classification.structural.BracketType
- Direction
- rsonpath_lib.classification.depth.neon_64 uses rsonpath_lib.classification.structural, so a change to rsonpath_lib.classification.structural can break rsonpath_lib.classification.depth.neon_64, while a change to rsonpath_lib.classification.depth.neon_64 can't break rsonpath_lib.classification.structural.
- Position
- Below the diagonal: rsonpath_lib.classification.depth.neon_64 uses a module listed above it, which is the healthy direction.
37→12 rsonpath_lib.classification.depth.neon_64 uses rsonpath_lib.classification.structural.nosimd✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.classification.depth.neon_64 uses a type in rsonpath_lib.classification.structural.nosimd.
- The types involved
rsonpath_lib.classification.depth.neon_64.NeonVectorIterator→rsonpath_lib.classification.structural.nosimd.Block
- Direction
- rsonpath_lib.classification.depth.neon_64 uses rsonpath_lib.classification.structural.nosimd, so a change to rsonpath_lib.classification.structural.nosimd can break rsonpath_lib.classification.depth.neon_64, while a change to rsonpath_lib.classification.depth.neon_64 can't break rsonpath_lib.classification.structural.nosimd.
- Position
- Below the diagonal: rsonpath_lib.classification.depth.neon_64 uses a module listed above it, which is the healthy direction.
37→14 rsonpath_lib.classification.depth.neon_64 uses rsonpath_lib.classification.quotes✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.classification.depth.neon_64 uses a type in rsonpath_lib.classification.quotes.
- The types involved
rsonpath_lib.classification.depth.neon_64.neon_64$module→rsonpath_lib.classification.quotes.QuoteClassifiedBlock
- Direction
- rsonpath_lib.classification.depth.neon_64 uses rsonpath_lib.classification.quotes, so a change to rsonpath_lib.classification.quotes can break rsonpath_lib.classification.depth.neon_64, while a change to rsonpath_lib.classification.depth.neon_64 can't break rsonpath_lib.classification.quotes.
- Position
- Below the diagonal: rsonpath_lib.classification.depth.neon_64 uses a module listed above it, which is the healthy direction.
37→15 rsonpath_lib.classification.depth.neon_64 uses rsonpath_lib.classification✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.classification.depth.neon_64 uses a type in rsonpath_lib.classification.
- The types involved
rsonpath_lib.classification.depth.neon_64.NeonVectorIterator→rsonpath_lib.classification.ResumeClassifierState
- Direction
- rsonpath_lib.classification.depth.neon_64 uses rsonpath_lib.classification, so a change to rsonpath_lib.classification can break rsonpath_lib.classification.depth.neon_64, while a change to rsonpath_lib.classification.depth.neon_64 can't break rsonpath_lib.classification.
- Position
- Below the diagonal: rsonpath_lib.classification.depth.neon_64 uses a module listed above it, which is the healthy direction.
37→20 rsonpath_lib.classification.depth.neon_64 uses rsonpath_lib.classification.depth✕
- Connections
- 2 pairs of types, where a type in rsonpath_lib.classification.depth.neon_64 uses a type in rsonpath_lib.classification.depth.
- The types involved
rsonpath_lib.classification.depth.neon_64.Constructor→rsonpath_lib.classification.depth.DepthImplrsonpath_lib.classification.depth.neon_64.NeonVectorIterator→rsonpath_lib.classification.depth.DepthIterator
- Direction
- rsonpath_lib.classification.depth.neon_64 uses rsonpath_lib.classification.depth, so a change to rsonpath_lib.classification.depth can break rsonpath_lib.classification.depth.neon_64, while a change to rsonpath_lib.classification.depth.neon_64 can't break rsonpath_lib.classification.depth.
- Position
- Below the diagonal: rsonpath_lib.classification.depth.neon_64 uses a module listed above it, which is the healthy direction.
37→32 rsonpath_lib.classification.depth.neon_64 uses rsonpath_lib.classification.depth.shared.mask_64✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.classification.depth.neon_64 uses a type in rsonpath_lib.classification.depth.shared.mask_64.
- The types involved
rsonpath_lib.classification.depth.neon_64.neon_64$module→rsonpath_lib.classification.depth.shared.mask_64.DepthVector64
- Direction
- rsonpath_lib.classification.depth.neon_64 uses rsonpath_lib.classification.depth.shared.mask_64, so a change to rsonpath_lib.classification.depth.shared.mask_64 can break rsonpath_lib.classification.depth.neon_64, while a change to rsonpath_lib.classification.depth.neon_64 can't break rsonpath_lib.classification.depth.shared.mask_64.
- Position
- Below the diagonal: rsonpath_lib.classification.depth.neon_64 uses a module listed above it, which is the healthy direction.
38→1 rsonpath_lib.classification.depth.sse2_64 uses rsonpath_lib✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.classification.depth.sse2_64 uses a type in rsonpath_lib.
- The types involved
rsonpath_lib.classification.depth.sse2_64.Sse2VectorIterator64→rsonpath_lib.FallibleIterator
- Direction
- rsonpath_lib.classification.depth.sse2_64 uses rsonpath_lib, so a change to rsonpath_lib can break rsonpath_lib.classification.depth.sse2_64, while a change to rsonpath_lib.classification.depth.sse2_64 can't break rsonpath_lib.
- Position
- Below the diagonal: rsonpath_lib.classification.depth.sse2_64 uses a module listed above it, which is the healthy direction.
38→9 rsonpath_lib.classification.depth.sse2_64 uses rsonpath_lib.classification.structural✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.classification.depth.sse2_64 uses a type in rsonpath_lib.classification.structural.
- The types involved
rsonpath_lib.classification.depth.sse2_64.Sse2VectorIterator64→rsonpath_lib.classification.structural.BracketType
- Direction
- rsonpath_lib.classification.depth.sse2_64 uses rsonpath_lib.classification.structural, so a change to rsonpath_lib.classification.structural can break rsonpath_lib.classification.depth.sse2_64, while a change to rsonpath_lib.classification.depth.sse2_64 can't break rsonpath_lib.classification.structural.
- Position
- Below the diagonal: rsonpath_lib.classification.depth.sse2_64 uses a module listed above it, which is the healthy direction.
38→12 rsonpath_lib.classification.depth.sse2_64 uses rsonpath_lib.classification.structural.nosimd✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.classification.depth.sse2_64 uses a type in rsonpath_lib.classification.structural.nosimd.
- The types involved
rsonpath_lib.classification.depth.sse2_64.Sse2VectorIterator64→rsonpath_lib.classification.structural.nosimd.Block
- Direction
- rsonpath_lib.classification.depth.sse2_64 uses rsonpath_lib.classification.structural.nosimd, so a change to rsonpath_lib.classification.structural.nosimd can break rsonpath_lib.classification.depth.sse2_64, while a change to rsonpath_lib.classification.depth.sse2_64 can't break rsonpath_lib.classification.structural.nosimd.
- Position
- Below the diagonal: rsonpath_lib.classification.depth.sse2_64 uses a module listed above it, which is the healthy direction.
38→14 rsonpath_lib.classification.depth.sse2_64 uses rsonpath_lib.classification.quotes✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.classification.depth.sse2_64 uses a type in rsonpath_lib.classification.quotes.
- The types involved
rsonpath_lib.classification.depth.sse2_64.sse2_64$module→rsonpath_lib.classification.quotes.QuoteClassifiedBlock
- Direction
- rsonpath_lib.classification.depth.sse2_64 uses rsonpath_lib.classification.quotes, so a change to rsonpath_lib.classification.quotes can break rsonpath_lib.classification.depth.sse2_64, while a change to rsonpath_lib.classification.depth.sse2_64 can't break rsonpath_lib.classification.quotes.
- Position
- Below the diagonal: rsonpath_lib.classification.depth.sse2_64 uses a module listed above it, which is the healthy direction.
38→15 rsonpath_lib.classification.depth.sse2_64 uses rsonpath_lib.classification✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.classification.depth.sse2_64 uses a type in rsonpath_lib.classification.
- The types involved
rsonpath_lib.classification.depth.sse2_64.Sse2VectorIterator64→rsonpath_lib.classification.ResumeClassifierState
- Direction
- rsonpath_lib.classification.depth.sse2_64 uses rsonpath_lib.classification, so a change to rsonpath_lib.classification can break rsonpath_lib.classification.depth.sse2_64, while a change to rsonpath_lib.classification.depth.sse2_64 can't break rsonpath_lib.classification.
- Position
- Below the diagonal: rsonpath_lib.classification.depth.sse2_64 uses a module listed above it, which is the healthy direction.
38→20 rsonpath_lib.classification.depth.sse2_64 uses rsonpath_lib.classification.depth✕
- Connections
- 2 pairs of types, where a type in rsonpath_lib.classification.depth.sse2_64 uses a type in rsonpath_lib.classification.depth.
- The types involved
rsonpath_lib.classification.depth.sse2_64.Constructor→rsonpath_lib.classification.depth.DepthImplrsonpath_lib.classification.depth.sse2_64.Sse2VectorIterator64→rsonpath_lib.classification.depth.DepthIterator
- Direction
- rsonpath_lib.classification.depth.sse2_64 uses rsonpath_lib.classification.depth, so a change to rsonpath_lib.classification.depth can break rsonpath_lib.classification.depth.sse2_64, while a change to rsonpath_lib.classification.depth.sse2_64 can't break rsonpath_lib.classification.depth.
- Position
- Below the diagonal: rsonpath_lib.classification.depth.sse2_64 uses a module listed above it, which is the healthy direction.
38→32 rsonpath_lib.classification.depth.sse2_64 uses rsonpath_lib.classification.depth.shared.mask_64✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.classification.depth.sse2_64 uses a type in rsonpath_lib.classification.depth.shared.mask_64.
- The types involved
rsonpath_lib.classification.depth.sse2_64.sse2_64$module→rsonpath_lib.classification.depth.shared.mask_64.DepthVector64
- Direction
- rsonpath_lib.classification.depth.sse2_64 uses rsonpath_lib.classification.depth.shared.mask_64, so a change to rsonpath_lib.classification.depth.shared.mask_64 can break rsonpath_lib.classification.depth.sse2_64, while a change to rsonpath_lib.classification.depth.sse2_64 can't break rsonpath_lib.classification.depth.shared.mask_64.
- Position
- Below the diagonal: rsonpath_lib.classification.depth.sse2_64 uses a module listed above it, which is the healthy direction.
39→3 rsonpath_lib.engine.main uses rsonpath_lib.depth✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.engine.main uses a type in rsonpath_lib.depth.
- The types involved
rsonpath_lib.engine.main.Executor→rsonpath_lib.depth.Depth
- Direction
- rsonpath_lib.engine.main uses rsonpath_lib.depth, so a change to rsonpath_lib.depth can break rsonpath_lib.engine.main, while a change to rsonpath_lib.engine.main can't break rsonpath_lib.depth.
- Position
- Below the diagonal: rsonpath_lib.engine.main uses a module listed above it, which is the healthy direction.
39→4 rsonpath_lib.engine.main uses rsonpath_lib.string_pattern✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.engine.main uses a type in rsonpath_lib.string_pattern.
- The types involved
rsonpath_lib.engine.main.Executor→rsonpath_lib.string_pattern.StringPattern
- Direction
- rsonpath_lib.engine.main uses rsonpath_lib.string_pattern, so a change to rsonpath_lib.string_pattern can break rsonpath_lib.engine.main, while a change to rsonpath_lib.engine.main can't break rsonpath_lib.string_pattern.
- Position
- Below the diagonal: rsonpath_lib.engine.main uses a module listed above it, which is the healthy direction.
39→5 rsonpath_lib.engine.main uses rsonpath_syntax✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.engine.main uses a type in rsonpath_syntax.
- The types involved
rsonpath_lib.engine.main.MainEngine→rsonpath_syntax.JsonPathQuery
- Direction
- rsonpath_lib.engine.main uses rsonpath_syntax, so a change to rsonpath_syntax can break rsonpath_lib.engine.main, while a change to rsonpath_lib.engine.main can't break rsonpath_syntax.
- Position
- Below the diagonal: rsonpath_lib.engine.main uses a module listed above it, which is the healthy direction.
39→8 rsonpath_lib.engine.main uses rsonpath_lib.automaton✕
- Connections
- 3 pairs of types, where a type in rsonpath_lib.engine.main uses a type in rsonpath_lib.automaton.
- The types involved
rsonpath_lib.engine.main.Executor→rsonpath_lib.automaton.Automatonrsonpath_lib.engine.main.MainEngine→rsonpath_lib.automaton.Automatonrsonpath_lib.engine.main.main$module→rsonpath_lib.automaton.Automaton
- Direction
- rsonpath_lib.engine.main uses rsonpath_lib.automaton, so a change to rsonpath_lib.automaton can break rsonpath_lib.engine.main, while a change to rsonpath_lib.engine.main can't break rsonpath_lib.automaton.
- Position
- Below the diagonal: rsonpath_lib.engine.main uses a module listed above it, which is the healthy direction.
39→9 rsonpath_lib.engine.main uses rsonpath_lib.classification.structural✕
- Connections
- 2 pairs of types, where a type in rsonpath_lib.engine.main uses a type in rsonpath_lib.classification.structural.
- The types involved
rsonpath_lib.engine.main.Executor→rsonpath_lib.classification.structural.BracketTypersonpath_lib.engine.main.Executor→rsonpath_lib.classification.structural.Structural
- Direction
- rsonpath_lib.engine.main uses rsonpath_lib.classification.structural, so a change to rsonpath_lib.classification.structural can break rsonpath_lib.engine.main, while a change to rsonpath_lib.engine.main can't break rsonpath_lib.classification.structural.
- Position
- Below the diagonal: rsonpath_lib.engine.main uses a module listed above it, which is the healthy direction.
39→29 rsonpath_lib.engine.main uses rsonpath_lib.engine.head_skipping✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.engine.main uses a type in rsonpath_lib.engine.head_skipping.
- The types involved
rsonpath_lib.engine.main.Executor→rsonpath_lib.engine.head_skipping.CanHeadSkip
- Direction
- rsonpath_lib.engine.main uses rsonpath_lib.engine.head_skipping, so a change to rsonpath_lib.engine.head_skipping can break rsonpath_lib.engine.main, while a change to rsonpath_lib.engine.main can't break rsonpath_lib.engine.head_skipping.
- Position
- Below the diagonal: rsonpath_lib.engine.main uses a module listed above it, which is the healthy direction.
39→34 rsonpath_lib.engine.main uses rsonpath_lib.classification.simd✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.engine.main uses a type in rsonpath_lib.classification.simd.
- The types involved
rsonpath_lib.engine.main.MainEngine→rsonpath_lib.classification.simd.SimdConfiguration
- Direction
- rsonpath_lib.engine.main uses rsonpath_lib.classification.simd, so a change to rsonpath_lib.classification.simd can break rsonpath_lib.engine.main, while a change to rsonpath_lib.engine.main can't break rsonpath_lib.classification.simd.
- Position
- Below the diagonal: rsonpath_lib.engine.main uses a module listed above it, which is the healthy direction.
40→3 rsonpath_lib.result uses rsonpath_lib.depth✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.result uses a type in rsonpath_lib.depth.
- The types involved
rsonpath_lib.result.Recorder→rsonpath_lib.depth.Depth
- Direction
- rsonpath_lib.result uses rsonpath_lib.depth, so a change to rsonpath_lib.depth can break rsonpath_lib.result, while a change to rsonpath_lib.result can't break rsonpath_lib.depth.
- Position
- Below the diagonal: rsonpath_lib.result uses a module listed above it, which is the healthy direction.
40→39 rsonpath_lib.result uses rsonpath_lib.engine.main✕
- Connections
- 1 pair of types, where a type in rsonpath_lib.result uses a type in rsonpath_lib.engine.main.
- The types involved
rsonpath_lib.result.MatchedNodeType→rsonpath_lib.engine.main.NodeType
- Direction
- rsonpath_lib.result uses rsonpath_lib.engine.main, so a change to rsonpath_lib.engine.main can break rsonpath_lib.result, while a change to rsonpath_lib.result can't break rsonpath_lib.engine.main.
- Position
- Below the diagonal: rsonpath_lib.result uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 14 | Medium |
| A05:2025 — Injection | 12 | High / Critical |
| A02:2025 — Security Misconfiguration | 2 | High / Critical |
Roadmap
Top priorities: Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production; Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Cargo.toml; 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.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Cargo.toml. | +1.8 pts | Low | ADR Quality |
| Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production. | +2.1 pts | Medium | Observability |
| 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. | +1.6 pts | Medium | Architecture documentation |
| Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4). | +0.8 pts | Low | Static Analysis (SAST) |
| Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. | +0.6 pts | Low | Static Analysis (SAST) |
| Resolve the 2 High IaC finding(s) in IaC & Container Security — start with REDACTED (2). | +0.6 pts | Low | IaC & Container Security |
| Resolve the 7 Orphaned file finding(s) in Knowledge Freshness — start with neon_64.rs (2), avx512_64.rs (2), vector_512.rs. | +0.5 pts | Low | Knowledge Freshness |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +0.3 pts | Low | Supply-chain Provenance & Signing |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 4.6 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 5.8 | Mixed | Dependency Vulnerabilities: Medium advisory (unsound): REDACTED |
| REDACTED | 5.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| crates/rsonpath-lib/src/engine/main.rs | 6.0 | Mixed | Explicit Debt: FixmeComment |
| crates/rsonpath-syntax/src/parser.rs | 7.0 | Near-clean | Cyclomatic Complexity: rsonpath_syntax::parser::string (cyclomatic 26) |
| crates/rsonpath-lib/src/classification/memmem/avx2_32.rs | 7.0 | Near-clean | Code Duplication: Members sharing a duplicated core (4 members, 50+ identical tokens) |
| crates/rsonpath-lib/src/input/borrowed.rs | 7.0 | Near-clean | Code Duplication: Edited copy of a member (32 corresponding lines) |
| crates/rsonpath-lib/src/input/padding.rs | 7.0 | Near-clean | Code Duplication: Edited copy of a member (16 corresponding lines) |
| crates/rsonpath-syntax/src/error/display.rs | 7.0 | Near-clean | Cyclomatic Complexity: SyntaxError::generate_notes (cyclomatic 61) |
| crates/rsonpath-syntax-proptest/src/lib.rs | 7.1 | Near-clean | Cyclomatic Complexity: rsonpath_syntax_proptest::filters::any_json_float::arbitrary_exp_repr (cyclomatic 20) |
| crates/rsonpath-lib/src/classification/memmem/sse2_32.rs | 7.1 | Near-clean | Code Duplication: Edited copy of a member (24 corresponding lines) |
| crates/rsonpath-lib/src/classification/structural/avx2_32.rs | 7.1 | Near-clean | Code Duplication: Edited copies of one member (6 members, 1+ corresponding lines) |
| crates/rsonpath-lib/src/classification/memmem/neon_64.rs | 7.2 | Near-clean | Code Duplication: Edited copy of a member (43 corresponding lines) |
| crates/rsonpath-lib/src/result/nodes.rs | 7.2 | Near-clean | Code Duplication: Edited copy of a member (29 corresponding lines) |
| crates/rsonpath-lib/src/classification/depth/avx2_32.rs | 7.2 | Near-clean | Code Duplication: Edited copies of one member (6 members, 1+ corresponding lines) |
| crates/rsonpath-lib/src/classification/memmem/avx2_64.rs | 7.2 | Near-clean | Code Duplication: Duplicated block (19–21 lines × 4) |
| REDACTED | 7.2 | Near-clean | Static Analysis (SAST): High: REDACTED |
| crates/rsonpath-syntax/src/lib.rs | 7.4 | Near-clean | Cognitive Complexity: LogicalExpr::fmt (cognitive 16) |
| crates/rsonpath-lib/src/classification/quotes/shared/mask_32.rs | 7.4 | Near-clean | Code Duplication: Edited copies of one member (3 members, 38+ corresponding lines) |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 49 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 49 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, 204 of 231 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the Rust half could not be measured — the Cargo suite in repository root did not build, so it was never run. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.rs) and this repository declares a Cargo test suite (repository root, 34 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.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (9 contributor(s) across 928 commit(s) sampled, automation and bot accounts excluded). One of them holds 97% of the history; the other 8 hold 0.4% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated per language (docs/plans/deterministic-engine.md, P5; C# and each NeutralApiArms arm pass): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D27 Navigability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- AXB2 Runtime readiness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. An image the REDACTED builds FROM could not be fetched: our sandbox reaches registries only through its pull-through mirror, and the mirror did not serve it. This is a limit of our sandbox, not of your repository. (rule: registry). The renderer reported: docker build failed (exit 1) — v1@sha256:c19039c2c093ddac3472fa28880fe5d66118e9104694943408608aa029dc1d8a: failed to resolve source metadata for gcr.io/oss-fuzz-base/base-builder-rust:v1@sha256:c19039c2c093ddac3472fa28880fe5d66118e9104694943408608aa029dc1d8a: failed to do request: Head "https://gcr.io/v2/oss-fuzz-base/base-builder-rust/manifests/sha256:c19039c2c093ddac3472fa28880fe5d66118e9104694943408608aa029dc1d8a": Forbidden; likely cause (our sandbox): an image the REDACTED builds FROM could not be fetched: our sandbox reaches registries only through its pull-through mirror, and the mirror did not serve it. This is a limit of our sandbox, not of your repository; runtime evidence skipped.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via REDACTED (REDACTED). docker build failed (exit 1) — v1@sha256:c19039c2c093ddac3472fa28880fe5d66118e9104694943408608aa029dc1d8a: failed to resolve source metadata for gcr.io/oss-fuzz-base/base-builder-rust:v1@sha256:c19039c2c093ddac3472fa28880fe5d66118e9104694943408608aa029dc1d8a: failed to do request: Head "https://gcr.io/v2/oss-fuzz-base/base-builder-rust/manifests/sha256:c19039c2c093ddac3472fa28880fe5d66118e9104694943408608aa029dc1d8a": Forbidden; likely cause (our sandbox): an image the REDACTED builds FROM could not be fetched: our sandbox reaches registries only through its pull-through mirror, and the mirror did not serve it. This is a limit of our sandbox, not of your repository; runtime evidence skipped.
- 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.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
6 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was SyntaxError::generate_notes at 61. A further 2 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being SyntaxErrorKind::toplevel_message at 31 — they are counted neither in the figure above nor in this dimension's score.
What to do
- Bring the 1 body over 30 down to 30 or less in Cyclomatic Complexity — start with SyntaxError::generate_notes (cyclomatic 61). — Refactoring it lifts Cyclomatic Complexity from 8.1 to about 8.8/10.
D2 · Cognitive Complexity
14 method(s) exceeded the cognitive complexity threshold of 15; the worst was SyntaxError::generate_notes at 56.
What to do
- Bring the 14 bodies over 15 down to 15 or less in Cognitive Complexity — start with SyntaxError::generate_notes (cognitive 56), Executor::handle_opening (cognitive 48), rsonpath_syntax_proptest::filters::any_json_float::arbitrary_exp_repr (cognitive 47). — 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 14 together lifts Cognitive Complexity from 7.5 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
8 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 3 MethodTooLong finding(s) in God Classes — start with display.rs, head_skipping.rs, formatter.rs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 3 FileTooLong finding(s) in God Classes — start with simd.rs, parser.rs, lib.rs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 FunctionTooLong finding(s) in God Classes — start with parser.rs, lib.rs. — One of this dimension's main actionable groups (2 warning-level).
D4 · Code Duplication
44 duplicated block group(s) detected. 8.0 % of the production lines (2,070 of 25,838) are in a reported copy. A further 60 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 2 of the 104 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 6 Edited copies of one member (7 members, 1+ corresponding lines) finding(s) in Code Duplication — start with avx2_32.rs (6). — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 4 Edited copy of a member (16 corresponding lines) finding(s) in Code Duplication — start with padding.rs, mask_32.rs, buffered.rs. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 4 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with borrowed.rs, avx2_32.rs, nodes.rs. — One of this dimension's main actionable groups (4 warning-level).
D5 · Coupling
5 production modules (Cargo), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 1 module(s) off the main sequence.
What to do
- Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
D6 · Cohesion (LCOM4)
0 of 96 classes have LCOM4 above 3.
D12 · Dependency Hygiene
16 outdated, 0 yanked direct Cargo dependencies. 27 of 41 direct crates were graded against crates.io (0 not published there, 14 not resolved by a committed REDACTED). Only DIRECT edges are graded: a transitive crate cannot be moved past what its parent's requirement admits, so reporting one would be advice its owner cannot take. A newer release is reported only where this repository's OWN requirement already admits it, so the remedy is `cargo update` and never a manifest edit — which means a release outside the declared range is deliberately NOT charged, because a written-down constraint is a decision rather than a defect. Note that a bare requirement is a CARET, and for a 0.x crate its ceiling is the minor. Whether any crate is UNMAINTAINED is not graded — crates.io publishes no maintenance status, and release age does not stand in for one. Known CVEs in this dependency graph are D30's question, read from REDACTED there.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 180 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository's REDACTED closed over its manifests' `[dependencies]` and `[build-dependencies]`. Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository. This repository publishes itself under MIT, which is its own choice and is not judged here.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
2 deducted task-comment markers across 25838 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 1 HackComment finding(s) in Explicit Debt — start with error.rs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 FixmeComment finding(s) in Explicit Debt — start with main.rs. — One of this dimension's main actionable groups (1 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 8 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Cargo.toml. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
1 of 5 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 — start with Cargo.toml. — 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)
12 finding(s): 0 critical, 6 high, 6 medium, 0 low. 1 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 2 file(s) — `crates/rsonpath-syntax-proptest/src/lib.rs` (line 418), `crates/rsonpath-syntax/src/parser.rs` (line 77, line 238, line 241, …) — 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. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4). — One of this dimension's main actionable groups (4 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 1 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 (1 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
7 finding(s): 0 critical, 0 high, 7 medium, 0 low.
What to do
- Resolve the 5 Medium advisory (unsound) finding(s) in Dependency Vulnerabilities — start with REDACTED (5). — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 2 Medium vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
D31 · IaC & Container Security
2 finding(s): 0 critical, 2 high, 0 medium, 0 low.
What to do
- Resolve the 2 High IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
D34 · Knowledge Freshness
7 of 85 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is crates/rsonpath-lib/src/classification/memmem/neon_64.rs. Counted over 85 of the 148 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D37 · Vulnerability-disclosure Policy
A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX8 · Test isolation
AX9 · CQS / query purity
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
M1 · Documentation (README)
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
- 2 public types in `rsonpath_benchmarks.framework.implementation` are marked as implementation by their own namespace, folder or name: `Implementation` (crates/rsonpath-benchmarks/src/framework/implementation.rs:3, `implementation`), `PreparedQuery` (crates/rsonpath-benchmarks/src/framework/implementation.rs:20, `implementation`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — crates/rsonpath-benchmarks/src/framework/implementation.rs:3
- 3 public types in `rsonpath_benchmarks.implementations.jsonpath_rust` are marked as implementation by their own namespace, folder or name: `JsonpathRust` (crates/rsonpath-benchmarks/src/implementations/jsonpath_rust.rs:14, `implementations`), `JsonpathRustResult` (crates/rsonpath-benchmarks/src/implementations/jsonpath_rust.rs:16, `implementations`), `JsonpathRustError` (crates/rsonpath-benchmarks/src/implementations/jsonpath_rust.rs:65, `implementations`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — crates/rsonpath-benchmarks/src/implementations/jsonpath_rust.rs:14
- 6 public types in `rsonpath_benchmarks.implementations.rsonpath` are marked as implementation by their own namespace, folder or name: `Rsonpath` (crates/rsonpath-benchmarks/src/implementations/rsonpath.rs:11, `implementations`), `RsonpathCount` (crates/rsonpath-benchmarks/src/implementations/rsonpath.rs:12, `implementations`), `RsonpathMmap` (crates/rsonpath-benchmarks/src/implementations/rsonpath.rs:13, `implementations`), `RsonpathMmapCount` (crates/rsonpath-benchmarks/src/implementations/rsonpath.rs:14, `implementations`), `RsonpathError` (crates/rsonpath-benchmarks/src/implementations/rsonpath.rs:169, `implementations`), `MatchDisplay` (crates/rsonpath-benchmarks/src/implementations/rsonpath.rs:182, `implementations`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — crates/rsonpath-benchmarks/src/implementations/rsonpath.rs:11
- 3 public types in `rsonpath_benchmarks.implementations.serde_json_path` are marked as implementation by their own namespace, folder or name: `SerdeJsonPath` (crates/rsonpath-benchmarks/src/implementations/serde_json_path.rs:11, `implementations`), `SerdeJsonPathResult` (crates/rsonpath-benchmarks/src/implementations/serde_json_path.rs:13, `implementations`), `SerdeJsonPathError` (crates/rsonpath-benchmarks/src/implementations/serde_json_path.rs:60, `implementations`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — crates/rsonpath-benchmarks/src/implementations/serde_json_path.rs:11
What to do
- Hide `rsonpath_benchmarks.framework.implementation` (`Implementation`, `PreparedQuery`) (Rust: `pub(crate)`, or keep the module private): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `rsonpath_benchmarks.implementations.jsonpath_rust` (`JsonpathRust`, `JsonpathRustResult`, `JsonpathRustError`) (Rust: `pub(crate)`, or keep the module private): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `rsonpath_benchmarks.implementations.rsonpath` (`Rsonpath`, `RsonpathCount`, `RsonpathMmap`, `RsonpathMmapCount`, `RsonpathError`, `MatchDisplay`) (Rust: `pub(crate)`, or keep the module private): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `rsonpath_benchmarks.implementations.serde_json_path` (`SerdeJsonPath`, `SerdeJsonPathResult`, `SerdeJsonPathError`) (Rust: `pub(crate)`, or keep the module private): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
P2 · Observability
- Only 2/4 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `.`, `crates/rsonpath-benchmarks`.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
P3 · Security & performance tooling
- `REDACTED` schedules updates, but no `package-ecosystem` entry covers `gitsubmodule`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entry to the `updates:` list. — REDACTED:7
What to do
- Dependabot is configured but does not watch `gitsubmodule` — add that `package-ecosystem` entry to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
P6 · Release Hygiene
PF1 · Benchmark discipline
X12 · Unreachable branch
X13 · Undrained process stream
X16 · Unfloored truncation loop
X21 · Side-effecting pattern guard
X23 · Unguarded diagnostic materialisation
X25 · Inert configuration knob
X28 · Index access outside its own emptiness guard
X5 · Nullable reference types
- `self.cases.iter_mut().find(|x|x.test_case.name==name)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `add_special_case_tag` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/rsonpath-test/src/lib.rs:259
- `JsonInt::try_from(i)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `any_json_int` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/rsonpath-syntax-proptest/src/lib.rs:315
- `JsonInt::try_from(i)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `rsonpath_valid_json_int` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/rsonpath-syntax-proptest/src/lib.rs:319
- `JsonFloat::try_from(f)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `any_json_float` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). (×2) — crates/rsonpath-syntax-proptest/src/lib.rs:628, crates/rsonpath-syntax-proptest/src/lib.rs:630
- `s.find('.').unwrap_or(s.len()).try_into()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `arbitrary_exp_repr` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/rsonpath-syntax-proptest/src/lib.rs:639
- `value.abs().try_into()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `from` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). (×2) — crates/rsonpath-syntax/src/lib.rs:418, crates/rsonpath-syntax/src/lib.rs:439
- `s.inner.drain(..).next()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `into_singular` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/rsonpath-syntax/src/lib.rs:887
- `self.0.partial_cmp(&other.0)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `cmp` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/rsonpath-syntax/src/num.rs:149
- `chars.next()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `from_str` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/rsonpath-syntax/src/num.rs:1009
- `ctx.options.recursion_limit` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `parse_json_path_query` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/rsonpath-syntax/src/parser.rs:109
- `int.abs().try_into()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `parse_directional_int` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/rsonpath-syntax/src/parser.rs:750
- `char::from_u32(n)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `read_escape_sequence` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/rsonpath-syntax/src/parser.rs:868
- `char::from_u32(raw_c)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `read_escape_sequence` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/rsonpath-syntax/src/parser.rs:883
- `write!(result,"\\u{:0>4x}",c as u8)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `escape` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/rsonpath-syntax/src/str.rs:164
- `diffs.pop()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `apply` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/rsonpath-syntax/src/error/display.rs:680
- `std::str::from_utf8(label.unquoted())` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `fmt` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/rsonpath-lib/src/automaton.rs:517
- `self.stack.pop()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `record_end` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/rsonpath-lib/src/result/approx_span.rs:93
- `self.node.take()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `record_value_terminator` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/rsonpath-lib/src/result/nodes.rs:243
- `self.stack.pop()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `record_value_terminator` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/rsonpath-lib/src/result/nodes.rs:373
- `node` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `output_to` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/rsonpath-lib/src/result/output_queue.rs:59
- `tail_skip.classifier.take()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `skip` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/rsonpath-lib/src/engine/tail_skipping.rs:52
- `self.classifier` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `stop` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/rsonpath-lib/src/engine/tail_skipping.rs:114
- `self.classifier.as_ref()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `deref` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/rsonpath-lib/src/engine/tail_skipping.rs:130
- `self.classifier.as_mut()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `deref_mut` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/rsonpath-lib/src/engine/tail_skipping.rs:144
- `SimdConfiguration::try_parse(&simd)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `configure` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/rsonpath-lib/src/classification/simd.rs:555
- `u64::try_from(gcd)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `solve_linear_congruence` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/rsonpath-lib/src/automaton/array_transition_set.rs:330
- `std::str::from_utf8(label.unquoted())` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `stringify_label` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/rsonpath-lib/src/automaton/nfa.rs:215
- `ProgressStyle::with_template("{msg} {spinner} {wide_bar:.green/white} {bytes:>12}/{total_bytes:>12} ({bytes_per_sec:>12}) {eta:>10}",)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `get_progress_bar` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/rsonpath-benchmarks/src/dataset.rs:255
- `u64::try_from(bench.json_document.size_in_bytes)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `run` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/rsonpath-benchmarks/src/framework.rs:53
- `self.implementation.load_file(file_path)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `run` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/rsonpath-benchmarks/src/framework.rs:299
- `self.implementation.compile_query(query_string)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `run` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/rsonpath-benchmarks/src/framework.rs:306
- `self.implementation.run(q,f)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `run` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/rsonpath-benchmarks/src/framework.rs:312
- `rsonpath_syntax::parse(query)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `compile_query` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). (×4) — crates/rsonpath-benchmarks/src/implementations/rsonpath.rs:41, crates/rsonpath-benchmarks/src/implementations/rsonpath.rs:79, crates/rsonpath-benchmarks/src/implementations/rsonpath.rs:117, …
What to do
- Each row is a forced `Option`/`Result` no guard on its path proves present. Handle the absent case where it arises rather than forcing it: `?` to hand it to the caller, `if let` / `match` / `let … else` to branch on it, `unwrap_or` / `unwrap_or_default` / `unwrap_or_else` where a default is right. Where the value genuinely cannot be absent, say so in a way a reader can check from the line: test it first (`if x.is_none() { return … }`), look the key up with `contains_key` or the index against `len()`, or construct the value so it cannot be absent.
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 90.3 | Exemplary | Solid. |
| Architecture | 95.4 | Exemplary | Strongest area. |
| Maturity | 77.6 | Strong | Solid. |
| Readiness | 72.6 | Strong | Largest drag on the score — prioritise here. |
| Security | 74.9 | Adequate — gated by D29, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 85.0 | Exemplary | Solid. |
Unscored — 1 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 4 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 66 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: this repository's Python imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one.
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — no interface, protocol or abstract type declares an operation an implementer must write
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — docker build failed (exit 1) — v1@sha256:c19039c2c093ddac3472fa28880fe5d66118e9104694943408608aa029dc1d8a: failed to resolve source metadata for gcr.io/oss-fuzz-base/base-builder-rust:v1@sha256:c19039c2c093ddac3472fa28880fe5d66118e9104694943408608aa029dc1d8a: failed to do request: Head "https://gcr.io/v2/oss-fuzz-base/base-builder-rust/manifests/sha256:c19039c2c093ddac3472fa28880fe5d66118e9104694943408608aa029dc1d8a": Forbidden; likely cause (our sandbox): an image the REDACTED builds FROM could not be fetched: our sandbox reaches registries only through its pull-through mirror, and the mirror did not serve it. This is a limit of our sandbox, not of your repository; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no data at rest for these controls to protect.
- 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 — ~2868 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
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (3600 declarations, no unit with a dominant convention).
- D22 Internal API Consistency — API consistency is measured on C#, TypeScript, Go only; the exposed Rust surface was not measured.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .py, .rs, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.rs), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- 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.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not measured — Rust suite
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (48 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
- M4 Documentation accuracy — Not applicable: the 8 current-state document(s) make no claim of a kind M4 checks. 1 claim(s) of kinds M4 does not check were not checked (environment variable 1); M4 checks only links and versions and artefact counts.
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the Python, Rust source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- 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: 117 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.
- X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — no C# was loaded; this repository's Python and Rust were read, and no request in it can be cancelled by a caller — a Python request takes no token: asyncio cancels the task and trio or anyio the scope that made it, from outside the call, and requests, httpx, aiohttp and gRPC take a timeout, not a cancellation; a Rust request takes no token: a future is cancelled by dropping it, from outside the call (select!, a timeout, an aborted task), and reqwest, hyper and tonic take none
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X27 Collection changed while being enumerated — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X3 Exception handling — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- 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.
- 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 — 8 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 181 finding(s)
- Symbol treated as nullable, then dereferenced unguarded crates/rsonpath-test/src/lib.rs:259
- Symbol treated as nullable, then dereferenced unguarded crates/rsonpath-syntax-proptest/src/lib.rs:315
- Symbol treated as nullable, then dereferenced unguarded crates/rsonpath-syntax-proptest/src/lib.rs:319
- Symbol treated as nullable, then dereferenced unguarded crates/rsonpath-syntax-proptest/src/lib.rs:628
- Symbol treated as nullable, then dereferenced unguarded crates/rsonpath-syntax-proptest/src/lib.rs:630
- Symbol treated as nullable, then dereferenced unguarded crates/rsonpath-syntax-proptest/src/lib.rs:639
- Symbol treated as nullable, then dereferenced unguarded crates/rsonpath-syntax/src/lib.rs:418
- Symbol treated as nullable, then dereferenced unguarded crates/rsonpath-syntax/src/lib.rs:439
- Symbol treated as nullable, then dereferenced unguarded crates/rsonpath-syntax/src/lib.rs:887
- Symbol treated as nullable, then dereferenced unguarded crates/rsonpath-syntax/src/num.rs:149
- Symbol treated as nullable, then dereferenced unguarded crates/rsonpath-syntax/src/num.rs:1009
- Symbol treated as nullable, then dereferenced unguarded crates/rsonpath-syntax/src/parser.rs:109
- Symbol treated as nullable, then dereferenced unguarded crates/rsonpath-syntax/src/parser.rs:750
- Symbol treated as nullable, then dereferenced unguarded crates/rsonpath-syntax/src/parser.rs:868
- Symbol treated as nullable, then dereferenced unguarded crates/rsonpath-syntax/src/parser.rs:883
- Symbol treated as nullable, then dereferenced unguarded crates/rsonpath-syntax/src/str.rs:164
- Symbol treated as nullable, then dereferenced unguarded crates/rsonpath-syntax/src/error/display.rs:680
- Symbol treated as nullable, then dereferenced unguarded crates/rsonpath-lib/src/automaton.rs:517
- Symbol treated as nullable, then dereferenced unguarded crates/rsonpath-lib/src/result/approx_span.rs:93
- Symbol treated as nullable, then dereferenced unguarded crates/rsonpath-lib/src/result/nodes.rs:243
- Symbol treated as nullable, then dereferenced unguarded crates/rsonpath-lib/src/result/nodes.rs:373
- Symbol treated as nullable, then dereferenced unguarded crates/rsonpath-lib/src/result/output_queue.rs:59
- Symbol treated as nullable, then dereferenced unguarded crates/rsonpath-lib/src/engine/tail_skipping.rs:52
- Symbol treated as nullable, then dereferenced unguarded crates/rsonpath-lib/src/engine/tail_skipping.rs:114
- Symbol treated as nullable, then dereferenced unguarded crates/rsonpath-lib/src/engine/tail_skipping.rs:130
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Edited copies of one member (7 members, 1+ corresponding lines) crates/rsonpath-lib/src/classification/structural/avx2_32.rs:12
- Edited copies of one member (7 members, 1+ corresponding lines) crates/rsonpath-lib/src/classification/structural/avx2_32.rs:12
- Edited copies of one member (7 members, 1+ corresponding lines) crates/rsonpath-lib/src/classification/depth/avx2_32.rs:14
- Edited copies of one member (7 members, 1+ corresponding lines) crates/rsonpath-lib/src/classification/structural/avx2_32.rs:12
- Edited copies of one member (7 members, 1+ corresponding lines) crates/rsonpath-lib/src/classification/quotes/avx2_32.rs:8
- Edited copies of one member (7 members, 1+ corresponding lines) crates/rsonpath-lib/src/classification/depth/avx2_32.rs:14
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Edited copy of a member (16 corresponding lines) crates/rsonpath-lib/src/input/padding.rs:270
- Edited copy of a member (16 corresponding lines) crates/rsonpath-lib/src/classification/memmem/shared/mask_32.rs:17
- Edited copy of a member (16 corresponding lines) crates/rsonpath-lib/src/input/buffered.rs:179
- Edited copy of a member (16 corresponding lines) fuzz/src/query.rs:387
- Duplicated block (10 lines × 2) crates/rsonpath-lib/src/input/borrowed.rs:257
- Duplicated block (10 lines × 2) crates/rsonpath-lib/src/classification/quotes/avx2_32.rs:22
- Duplicated block (10 lines × 2) crates/rsonpath-lib/src/result/nodes.rs:228
- Duplicated block (10 lines × 2) fuzz/src/query.rs:242
- Duplicated block (7 lines × 2) crates/rsonpath-lib/src/classification/memmem/avx2_32.rs:116
- Duplicated block (7 lines × 2) crates/rsonpath-lib/src/classification/memmem/sse2_32.rs:124
- Duplicated block (7 lines × 2) crates/rsonpath-benchmarks/src/implementations/jsonpath_rust.rs:35
- Duplicated block (7 lines × 2) crates/rsonpath-syntax-proptest/src/lib.rs:228
- MethodTooLong: SyntaxError.generate_notes crates/rsonpath-syntax/src/error/display.rs:206
- MethodTooLong: HeadSkip.run_head_skipping crates/rsonpath-lib/src/engine/head_skipping.rs:123
- MethodTooLong: ErrorFormatter.build_error_lines crates/rsonpath-syntax/src/error/formatter.rs:104
- FileTooLong: classification/simd.rs crates/rsonpath-lib/src/classification/simd.rs
- FileTooLong: src/parser.rs crates/rsonpath-syntax/src/parser.rs
- FileTooLong: src/lib.rs crates/rsonpath-syntax/src/lib.rs
- Edited copy of a member (13 corresponding lines) crates/rsonpath-syntax/src/parser.rs:185
- Edited copy of a member (13 corresponding lines) crates/rsonpath-lib/src/classification/structural/avx2_64.rs:31
- Edited copy of a member (13 corresponding lines) crates/rsonpath-lib/src/result/nodes.rs:225
- Edited copies of one member (6 members, 1+ corresponding lines) crates/rsonpath-lib/src/classification/structural/avx2_32.rs:12
- Edited copies of one member (6 members, 1+ corresponding lines) crates/rsonpath-lib/src/classification/depth/avx2_32.rs:14
- Edited copies of one member (6 members, 1+ corresponding lines) crates/rsonpath-lib/src/classification/quotes/avx2_32.rs:8
- Edited copy of a member (12 corresponding lines) crates/rsonpath-lib/src/classification/quotes/avx2_64.rs:22
- Edited copy of a member (12 corresponding lines) crates/rsonpath-lib/src/input/padding.rs:359
- Edited copy of a member (12 corresponding lines) crates/rsonpath-lib/src/classification/structural/avx2_32.rs:30
- Edited copy of a member (11 corresponding lines) crates/rsonpath-lib/src/classification/depth/shared/vector_128.rs:36
- Edited copy of a member (11 corresponding lines) crates/rsonpath-lib/src/classification/depth/shared/vector_256.rs:36
- Edited copy of a member (11 corresponding lines) crates/rsonpath-lib/src/input/owned.rs:47
- Duplicated block (13 lines × 2) crates/rsonpath-lib/src/classification/depth/avx2_32.rs:44
- Duplicated block (13 lines × 2) crates/rsonpath-lib/src/classification/depth/shared/mask_32.rs:50
- Duplicated block (13 lines × 2) crates/rsonpath-lib/src/classification/quotes/shared/mask_64.rs:81
- Duplicated block (9 lines × 2) crates/rsonpath-lib/src/classification/memmem/avx2_32.rs:160
- Duplicated block (9 lines × 2) crates/rsonpath-lib/src/classification/memmem/sse2_32.rs:168
- Duplicated block (9 lines × 2) crates/rsonpath-lib/src/input/padding.rs:273
- rsonpath_syntax::parser::string (cyclomatic 26) crates/rsonpath-syntax/src/parser.rs:773
- rsonpath_syntax::parser::logical_expr::parse_single (cyclomatic 16) crates/rsonpath-syntax/src/parser.rs:474
- SyntaxError::generate_notes (cognitive 56) crates/rsonpath-syntax/src/error/display.rs:206
- SyntaxError::generate_notes::fix_unquoted_bracketed_selector (cognitive 23) crates/rsonpath-syntax/src/error/display.rs:466
- Executor::handle_opening (cognitive 48) crates/rsonpath-lib/src/engine/main.rs:472
- Executor::handle_comma (cognitive 19) crates/rsonpath-lib/src/engine/main.rs:421
- rsonpath_syntax::parser::logical_expr::parse_single (cognitive 31) crates/rsonpath-syntax/src/parser.rs:474
- rsonpath_syntax::parser::string (cognitive 27) crates/rsonpath-syntax/src/parser.rs:773
- NondeterministicAutomaton::new (cognitive 21) crates/rsonpath-lib/src/automaton/nfa.rs:70
- NondeterministicAutomaton::fmt (cognitive 16) crates/rsonpath-lib/src/automaton/nfa.rs:162
- FunctionTooLong: rsonpath_syntax::parser::string crates/rsonpath-syntax/src/parser.rs:773
- FunctionTooLong: rsonpath_test::read_and_tag crates/rsonpath-test/src/lib.rs:91
- REDACTED
- REDACTED
- Members sharing a duplicated core (4 members, 50+ identical tokens) crates/rsonpath-lib/src/classification/depth/avx2_64.rs:39
- Members sharing a duplicated core (4 members, 50+ identical tokens) crates/rsonpath-lib/src/classification/memmem/avx2_32.rs:85
- Edited copy of a member (17 corresponding lines) crates/rsonpath-lib/src/input/padding.rs:341
- Edited copy of a member (17 corresponding lines) crates/rsonpath-syntax/src/lib.rs:1221
- Edited copy of a member (8 corresponding lines) crates/rsonpath-syntax-proptest/src/lib.rs:294
- Edited copy of a member (8 corresponding lines) crates/rsonpath-lib/src/input/padding.rs:192
- Duplicated block (18 lines × 2) crates/rsonpath-lib/src/classification/memmem/sse2_32.rs:99
- Duplicated block (18 lines × 2) crates/rsonpath-lib/src/classification/structural/neon_64.rs:33
- Duplicated block (11 lines × 2) crates/rsonpath-lib/src/classification/memmem/shared/mask_32.rs:22
- Duplicated block (11 lines × 2) crates/rsonpath-benchmarks/src/dataset.rs:167
- SyntaxError::generate_notes (cyclomatic 61) crates/rsonpath-syntax/src/error/display.rs:206
- Executor::handle_opening (cyclomatic 23) crates/rsonpath-lib/src/engine/main.rs:472
- rsonpath_syntax_proptest::filters::any_json_float::arbitrary_exp_repr (cyclomatic 20) crates/rsonpath-syntax-proptest/src/lib.rs:637
- DisplayableSyntaxError::fmt (cyclomatic 18) crates/rsonpath-syntax/src/error/display.rs:732
- HackComment crates/rsonpath-lib/src/input/error.rs:26
- FixmeComment crates/rsonpath-lib/src/engine/main.rs:237
- rsonpath_syntax_proptest::filters::any_json_float::arbitrary_exp_repr (cognitive 47) crates/rsonpath-syntax-proptest/src/lib.rs:637
- DisplayableSyntaxError::fmt (cognitive 46) crates/rsonpath-syntax/src/error/display.rs:732
- Suggestion::apply (cognitive 46) crates/rsonpath-syntax/src/error/display.rs:664
- JsonFloat::from_str (cognitive 24) crates/rsonpath-syntax/src/num.rs:987
- Automaton::fmt (cognitive 20) crates/rsonpath-lib/src/automaton.rs:454
- LogicalExpr::fmt (cognitive 16) crates/rsonpath-syntax/src/lib.rs:1169
- REDACTED
- REDACTED
- Edited copy of a member (21 corresponding lines) crates/rsonpath-syntax-proptest/src/lib.rs:322
- Edited copy of a member (34 corresponding lines) crates/rsonpath-benchmarks/src/framework.rs:191
- Edited copy of a member (43 corresponding lines) crates/rsonpath-lib/src/classification/memmem/neon_64.rs:53
- Edited copies of one member (3 members, 38+ corresponding lines) crates/rsonpath-lib/src/classification/quotes/shared/mask_32.rs:55
- Edited copies of one member (3 members, 36+ corresponding lines) crates/rsonpath-lib/src/classification/memmem/neon_64.rs:105
- Edited copy of a member (32 corresponding lines) crates/rsonpath-lib/src/input/borrowed.rs:250
- Edited copy of a member (27 corresponding lines) crates/rsonpath-benchmarks/src/dataset.rs:164
- Edited copy of a member (24 corresponding lines) crates/rsonpath-lib/src/classification/memmem/sse2_32.rs:93
- Edited copies of one member (3 members, 25+ corresponding lines) crates/rsonpath-lib/src/classification/memmem/avx2_32.rs:50
- Edited copy of a member (31 corresponding lines) crates/rsonpath-lib/src/classification/depth/shared/mask_32.rs:31
- Edited copy of a member (29 corresponding lines) crates/rsonpath-lib/src/result/nodes.rs:239
- Edited copy of a member (22 corresponding lines) crates/rsonpath-lib/src/input/borrowed.rs:151
- Edited copy of a member (25 corresponding lines) crates/rsonpath-lib/src/classification/quotes/neon_64.rs:22
- Edited copies of one member (3 members, 16+ corresponding lines) crates/rsonpath-lib/src/input/borrowed.rs:133
- Edited copy of a member (14 corresponding lines) crates/rsonpath-benchmarks/src/dataset.rs:133
- Edited copies of one member (4 members, 16+ corresponding lines) crates/rsonpath-lib/src/engine/main.rs:127
- Edited copy of a member (15 corresponding lines) crates/rsonpath-lib/src/input/borrowed.rs:222
- Edited copies of one member (4 members, 12+ corresponding lines) crates/rsonpath-lib/src/input/padding.rs:328
- Edited copy of a member (7 corresponding lines) crates/rsonpath-lib/src/automaton.rs:190
- Edited copies of one member (4 members, 6+ corresponding lines) crates/rsonpath-lib/src/input/padding.rs:209
- Edited copies of one member (3 members, 10+ corresponding lines) crates/rsonpath-lib/src/classification/memmem/avx512_64.rs:157
- Edited copies of one member (3 members, 6+ corresponding lines) crates/rsonpath-syntax/src/num.rs:686
- Edited copy of a member (10 corresponding lines) crates/rsonpath-syntax/src/num/error.rs:95
- Edited copy of a member (9 corresponding lines) crates/rsonpath-lib/src/input/padding.rs:287
- Edited copies of one member (3 members, 17+ corresponding lines) crates/rsonpath-lib/src/input/padding.rs:569
- Duplicated block (22 lines × 4) crates/rsonpath-lib/src/classification/memmem/neon_64.rs:116
- Duplicated block (22 lines × 2) crates/rsonpath-lib/src/classification/memmem/avx2_32.rs:54
- Duplicated block (21 lines × 6) crates/rsonpath-lib/src/classification/memmem/neon_64.rs:55
- Duplicated block (19–21 lines × 4) crates/rsonpath-lib/src/classification/memmem/avx2_64.rs:65
- Duplicated block (21 lines × 2) crates/rsonpath-lib/src/classification/memmem/avx2_32.rs:87
- Duplicated block (20–21 lines × 2) crates/rsonpath-lib/src/classification/memmem/avx512_64.rs:86
- Duplicated block (20 lines × 3) crates/rsonpath-lib/src/classification/quotes/shared/mask_32.rs:56
- Duplicated block (20 lines × 2) crates/rsonpath-syntax-proptest/src/lib.rs:327
- Duplicated block (19 lines × 2) crates/rsonpath-lib/src/classification/structural/shared/mask_32.rs:39
- Duplicated block (17 lines × 2) crates/rsonpath-lib/src/classification/depth/neon_64.rs:43
- Duplicated block (16 lines × 4) crates/rsonpath-lib/src/classification/memmem/avx2_32.rs:93
- Duplicated block (14–15 lines × 2) crates/rsonpath-lib/src/classification/memmem/avx2_64.rs:99
- Duplicated block (15 lines × 2) crates/rsonpath-lib/src/classification/quotes/neon_64.rs:32
- Duplicated block (13–15 lines × 2) crates/rsonpath-lib/src/input/borrowed.rs:161
- Duplicated block (10–14 lines × 6) crates/rsonpath-lib/src/classification/memmem/avx2_64.rs:105
- Duplicated block (14 lines × 2) crates/rsonpath-lib/src/input/borrowed.rs:268
- Duplicated block (13 lines × 6) crates/rsonpath-lib/src/classification/memmem/avx2_32.rs:58
- Duplicated block (13 lines × 4) crates/rsonpath-lib/src/classification/depth/avx2_64.rs:48
- Duplicated block (9–11 lines × 2) crates/rsonpath-lib/src/input/borrowed.rs:191
- Duplicated block (9 lines × 3) crates/rsonpath-lib/src/classification/memmem/sse2_32.rs:55
- Duplicated block (8–9 lines × 2) crates/rsonpath-syntax/src/parser.rs:202
- Duplicated block (8 lines × 2) crates/rsonpath-lib/src/engine/main.rs:398
- Duplicated block (7 lines × 3) crates/rsonpath-lib/src/classification/memmem/avx2_64.rs:57
- Duplicated block (8 lines × 4) crates/rsonpath-lib/src/classification/depth/shared/vector_128.rs:13
- Duplicated block (5 lines × 3) crates/rsonpath-lib/src/classification/quotes/shared/mask_32.rs:31
- Duplicated block (12 lines × 2) crates/rsonpath-lib/src/result/nodes.rs:245
- Off the main sequence: rsonpath-syntax
Minor — 26 finding(s)
- Orphaned file crates/rsonpath-lib/src/classification/memmem/neon_64.rs:1
- Orphaned file crates/rsonpath-lib/src/classification/memmem/avx512_64.rs:1
- Orphaned file crates/rsonpath-lib/src/classification/structural/shared/vector_512.rs:1
- Orphaned file crates/rsonpath-lib/src/classification/structural/shared/vector_neon.rs:1
- Orphaned file crates/rsonpath-lib/src/classification/quotes/shared/mask_neon.rs:1
- Orphaned file crates/rsonpath-lib/src/classification/quotes/neon_64.rs:1
- Orphaned file crates/rsonpath-lib/src/classification/quotes/avx512_64.rs:1
- Implementation type on the public API crates/rsonpath-benchmarks/src/framework/implementation.rs:3
- Implementation type on the public API crates/rsonpath-benchmarks/src/implementations/jsonpath_rust.rs:14
- Implementation type on the public API crates/rsonpath-benchmarks/src/implementations/rsonpath.rs:11
- Implementation type on the public API crates/rsonpath-benchmarks/src/implementations/serde_json_path.rs:11
- Duplicated predicate crates/rsonpath-lib/src/classification/structural/nosimd.rs:172
- Duplicated predicate crates/rsonpath-lib/src/input/borrowed.rs:233
- Duplicated predicate crates/rsonpath-lib/src/classification/memmem/shared/mask_32.rs:22
- Duplicated predicate crates/rsonpath-lib/src/classification/structural/nosimd.rs:186
- No ADRs found crates/rsonpath-benchmarks/Cargo.toml:17
- Projects may be oversized for their cohesion crates/rsonpath-lib/Cargo.toml:1
- Orphaned files with no living knowledge
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- Logging is not universal
- Dependabot does not watch gitsubmodule REDACTED:7
Minor — 16 finding(s)
- Outdated: cfg-if
- Outdated: clap
- Outdated: eyre
- Outdated: glob
- Outdated: log
- Outdated: md5
- Outdated: memmap2
- Outdated: owo-colors
- Outdated: proc-macro2
- Outdated: proptest
- Outdated: quote
- Outdated: serde
- Outdated: serde_json
- Outdated: smallvec
- Outdated: thiserror
- Outdated: unicode-width
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=0 --max-count=200" --report-format json --report-path /tmp/watchdog-gitleaks-6858565e588f4f5fa5e31b02a576dbd7/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=200 --max-count=729" --report-format json --report-path /tmp/watchdog-gitleaks-6858565e588f4f5fa5e31b02a576dbd7/history-1.json --exit-code 0 --source . | 16 | artifacts/raw/gitleaks-history-1.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-6858565e588f4f5fa5e31b02a576dbd7/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 12 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 7 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 2 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |