Executive summary
pest-parser/pest falls short of our standard for production, in part because we found no logging, tracing or health checks in the code. It scores 56 out of 100 and is rated Adequate, and all 24 of its critical findings are security problems in the build pipeline.
Production Readiness, at 41, is the weakest lens and counts most in the score. The best first step for the work it takes is recording design decisions, worth about 6 points. Adding a diagnostic log would lift Production Readiness itself, worth about 8 points. Raising Production Readiness to 70 would lift the score to about 67.
Twenty-two pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. One pipeline step runs a download nobody checks, and one secret can leak from the build pipeline. Pinning each tool to an exact version, checking the download against a checksum and limiting the secret to its own step would close these risks.
The product code is 19,747 lines, about €25,000 to rebuild.
If Production Readiness rose from 41 to 70, the lowest score rated Strong, the score would rise from 56 to about 67.
Rebuild cost: about €25,000 · Estimate
| Cost to rebuild | €8,300 to €42,000, for 139 to 440 hours of work, about 0.2 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 56. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 19,747 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 pest | 2 pest.iterators.line_index | 3 pest.iterators.queueable_token | 4 pest.parser | 5 pest.pratt_parser | 6 pest.stack | 7 pest.token | 8 pest.unicode | 9 pest_bootstrap | 10 pest_derive | 11 pest_generator.parse_derive | 12 pest_meta.ast | 13 pest.iterators.tokens | 14 pest.prec_climber | 15 pest.span | 16 pest_meta.grammar | 17 pest_meta.optimizer | 18 pest_meta.optimizer.concatenator | 19 pest_meta.optimizer.factorizer | 20 pest_meta.optimizer.lister | 21 pest_meta.optimizer.rotator | 22 pest_meta.optimizer.skipper | 23 pest_meta.optimizer.unroller | 24 pest.iterators.flat_pairs | 25 pest.position | 26 pest_debugger | 27 pest_meta.optimizer.restorer | 28 pest.iterators.pairs | 29 pest.parser_state | 30 pest_debugger.main | 31 pest.error | 32 pest.iterators.pair | 33 pest.iterators.pairs_builder | 34 pest_generator.docs | 35 pest_meta.parser | 36 pest_vm | 37 pest.error.miette_adapter | 38 pest_generator.generator | 39 pest_meta.validator | 40 pest_meta.validator.stack_loops |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 pest | ||||||||||||||||||||||||||||||||||||||||
| 2 pest.iterators.line_index | ||||||||||||||||||||||||||||||||||||||||
| 3 pest.iterators.queueable_token | ||||||||||||||||||||||||||||||||||||||||
| 4 pest.parser | ||||||||||||||||||||||||||||||||||||||||
| 5 pest.pratt_parser | ||||||||||||||||||||||||||||||||||||||||
| 6 pest.stack | ||||||||||||||||||||||||||||||||||||||||
| 7 pest.token | ||||||||||||||||||||||||||||||||||||||||
| 8 pest.unicode | ||||||||||||||||||||||||||||||||||||||||
| 9 pest_bootstrap | ||||||||||||||||||||||||||||||||||||||||
| 10 pest_derive | ||||||||||||||||||||||||||||||||||||||||
| 11 pest_generator.parse_derive | ||||||||||||||||||||||||||||||||||||||||
| 12 pest_meta.ast | ||||||||||||||||||||||||||||||||||||||||
| 13 pest.iterators.tokens | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 14 pest.prec_climber | 1 | |||||||||||||||||||||||||||||||||||||||
| 15 pest.span | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 pest_meta.grammar | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 17 pest_meta.optimizer | 2 | |||||||||||||||||||||||||||||||||||||||
| 18 pest_meta.optimizer.concatenator | 1 | |||||||||||||||||||||||||||||||||||||||
| 19 pest_meta.optimizer.factorizer | 1 | |||||||||||||||||||||||||||||||||||||||
| 20 pest_meta.optimizer.lister | 1 | |||||||||||||||||||||||||||||||||||||||
| 21 pest_meta.optimizer.rotator | 1 | |||||||||||||||||||||||||||||||||||||||
| 22 pest_meta.optimizer.skipper | 1 | |||||||||||||||||||||||||||||||||||||||
| 23 pest_meta.optimizer.unroller | 1 | |||||||||||||||||||||||||||||||||||||||
| 24 pest.iterators.flat_pairs | 2 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 25 pest.position | 1 | |||||||||||||||||||||||||||||||||||||||
| 26 pest_debugger | 1 | |||||||||||||||||||||||||||||||||||||||
| 27 pest_meta.optimizer.restorer | 2 | |||||||||||||||||||||||||||||||||||||||
| 28 pest.iterators.pairs | 2 | 2 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 29 pest.parser_state | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 30 pest_debugger.main | 1 | |||||||||||||||||||||||||||||||||||||||
| 31 pest.error | 2 | 2 | 2 | |||||||||||||||||||||||||||||||||||||
| 32 pest.iterators.pair | 2 | 2 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 33 pest.iterators.pairs_builder | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 34 pest_generator.docs | 1 | |||||||||||||||||||||||||||||||||||||||
| 35 pest_meta.parser | 1 | 3 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 36 pest_vm | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 37 pest.error.miette_adapter | 1 | |||||||||||||||||||||||||||||||||||||||
| 38 pest_generator.generator | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 39 pest_meta.validator | 1 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 40 pest_meta.validator.stack_loops | 2 | 2 |
13→3 pest.iterators.tokens uses pest.iterators.queueable_token✕
- Connections
- 2 pairs of types, where a type in pest.iterators.tokens uses a type in pest.iterators.queueable_token.
- The types involved
pest.iterators.tokens.Tokens→pest.iterators.queueable_token.QueueableTokenpest.iterators.tokens.tokens$module→pest.iterators.queueable_token.QueueableToken
- Direction
- pest.iterators.tokens uses pest.iterators.queueable_token, so a change to pest.iterators.queueable_token can break pest.iterators.tokens, while a change to pest.iterators.tokens can't break pest.iterators.queueable_token.
- Position
- Below the diagonal: pest.iterators.tokens uses a module listed above it, which is the healthy direction.
13→7 pest.iterators.tokens uses pest.token✕
- Connections
- 1 pair of types, where a type in pest.iterators.tokens uses a type in pest.token.
- The types involved
pest.iterators.tokens.Tokens→pest.token.Token
- Direction
- pest.iterators.tokens uses pest.token, so a change to pest.token can break pest.iterators.tokens, while a change to pest.iterators.tokens can't break pest.token.
- Position
- Below the diagonal: pest.iterators.tokens uses a module listed above it, which is the healthy direction.
14→5 pest.prec_climber uses pest.pratt_parser✕
- Connections
- 1 pair of types, where a type in pest.prec_climber uses a type in pest.pratt_parser.
- The types involved
pest.prec_climber.Operator→pest.pratt_parser.Assoc
- Direction
- pest.prec_climber uses pest.pratt_parser, so a change to pest.pratt_parser can break pest.prec_climber, while a change to pest.prec_climber can't break pest.pratt_parser.
- Position
- Below the diagonal: pest.prec_climber uses a module listed above it, which is the healthy direction.
15→25 pest.span uses pest.position part of a loop✕
- Connections
- 1 pair of types, where a type in pest.span uses a type in pest.position.
- The types involved
pest.span.Span→pest.position.Position
- Direction
- pest.span uses pest.position, so a change to pest.position can break pest.span, while a change to pest.span can't break pest.position.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→4 pest_meta.grammar uses pest.parser✕
- Connections
- 1 pair of types, where a type in pest_meta.grammar uses a type in pest.parser.
- The types involved
pest_meta.grammar.PestParser→pest.parser.Parser
- Direction
- pest_meta.grammar uses pest.parser, so a change to pest.parser can break pest_meta.grammar, while a change to pest_meta.grammar can't break pest.parser.
- Position
- Below the diagonal: pest_meta.grammar uses a module listed above it, which is the healthy direction.
16→12 pest_meta.grammar uses pest_meta.ast✕
- Connections
- 1 pair of types, where a type in pest_meta.grammar uses a type in pest_meta.ast.
- The types involved
pest_meta.grammar.PestParser→pest_meta.ast.Rule
- Direction
- pest_meta.grammar uses pest_meta.ast, so a change to pest_meta.ast can break pest_meta.grammar, while a change to pest_meta.grammar can't break pest_meta.ast.
- Position
- Below the diagonal: pest_meta.grammar uses a module listed above it, which is the healthy direction.
17→12 pest_meta.optimizer uses pest_meta.ast✕
- Connections
- 2 pairs of types, where a type in pest_meta.optimizer uses a type in pest_meta.ast.
- The types involved
pest_meta.optimizer.OptimizedRule→pest_meta.ast.RuleTypepest_meta.optimizer.optimizer$module→pest_meta.ast.Rule
- Direction
- pest_meta.optimizer uses pest_meta.ast, so a change to pest_meta.ast can break pest_meta.optimizer, while a change to pest_meta.optimizer can't break pest_meta.ast.
- Position
- Below the diagonal: pest_meta.optimizer uses a module listed above it, which is the healthy direction.
18→12 pest_meta.optimizer.concatenator uses pest_meta.ast✕
- Connections
- 1 pair of types, where a type in pest_meta.optimizer.concatenator uses a type in pest_meta.ast.
- The types involved
pest_meta.optimizer.concatenator.concatenator$module→pest_meta.ast.Rule
- Direction
- pest_meta.optimizer.concatenator uses pest_meta.ast, so a change to pest_meta.ast can break pest_meta.optimizer.concatenator, while a change to pest_meta.optimizer.concatenator can't break pest_meta.ast.
- Position
- Below the diagonal: pest_meta.optimizer.concatenator uses a module listed above it, which is the healthy direction.
19→12 pest_meta.optimizer.factorizer uses pest_meta.ast✕
- Connections
- 1 pair of types, where a type in pest_meta.optimizer.factorizer uses a type in pest_meta.ast.
- The types involved
pest_meta.optimizer.factorizer.factorizer$module→pest_meta.ast.Rule
- Direction
- pest_meta.optimizer.factorizer uses pest_meta.ast, so a change to pest_meta.ast can break pest_meta.optimizer.factorizer, while a change to pest_meta.optimizer.factorizer can't break pest_meta.ast.
- Position
- Below the diagonal: pest_meta.optimizer.factorizer uses a module listed above it, which is the healthy direction.
20→12 pest_meta.optimizer.lister uses pest_meta.ast✕
- Connections
- 1 pair of types, where a type in pest_meta.optimizer.lister uses a type in pest_meta.ast.
- The types involved
pest_meta.optimizer.lister.lister$module→pest_meta.ast.Rule
- Direction
- pest_meta.optimizer.lister uses pest_meta.ast, so a change to pest_meta.ast can break pest_meta.optimizer.lister, while a change to pest_meta.optimizer.lister can't break pest_meta.ast.
- Position
- Below the diagonal: pest_meta.optimizer.lister uses a module listed above it, which is the healthy direction.
21→12 pest_meta.optimizer.rotator uses pest_meta.ast✕
- Connections
- 1 pair of types, where a type in pest_meta.optimizer.rotator uses a type in pest_meta.ast.
- The types involved
pest_meta.optimizer.rotator.rotator$module→pest_meta.ast.Rule
- Direction
- pest_meta.optimizer.rotator uses pest_meta.ast, so a change to pest_meta.ast can break pest_meta.optimizer.rotator, while a change to pest_meta.optimizer.rotator can't break pest_meta.ast.
- Position
- Below the diagonal: pest_meta.optimizer.rotator uses a module listed above it, which is the healthy direction.
22→12 pest_meta.optimizer.skipper uses pest_meta.ast✕
- Connections
- 1 pair of types, where a type in pest_meta.optimizer.skipper uses a type in pest_meta.ast.
- The types involved
pest_meta.optimizer.skipper.skipper$module→pest_meta.ast.Rule
- Direction
- pest_meta.optimizer.skipper uses pest_meta.ast, so a change to pest_meta.ast can break pest_meta.optimizer.skipper, while a change to pest_meta.optimizer.skipper can't break pest_meta.ast.
- Position
- Below the diagonal: pest_meta.optimizer.skipper uses a module listed above it, which is the healthy direction.
23→12 pest_meta.optimizer.unroller uses pest_meta.ast✕
- Connections
- 1 pair of types, where a type in pest_meta.optimizer.unroller uses a type in pest_meta.ast.
- The types involved
pest_meta.optimizer.unroller.unroller$module→pest_meta.ast.Rule
- Direction
- pest_meta.optimizer.unroller uses pest_meta.ast, so a change to pest_meta.ast can break pest_meta.optimizer.unroller, while a change to pest_meta.optimizer.unroller can't break pest_meta.ast.
- Position
- Below the diagonal: pest_meta.optimizer.unroller uses a module listed above it, which is the healthy direction.
24→2 pest.iterators.flat_pairs uses pest.iterators.line_index✕
- Connections
- 2 pairs of types, where a type in pest.iterators.flat_pairs uses a type in pest.iterators.line_index.
- The types involved
pest.iterators.flat_pairs.FlatPairs→pest.iterators.line_index.LineIndexpest.iterators.flat_pairs.flat_pairs$module→pest.iterators.line_index.LineIndex
- Direction
- pest.iterators.flat_pairs uses pest.iterators.line_index, so a change to pest.iterators.line_index can break pest.iterators.flat_pairs, while a change to pest.iterators.flat_pairs can't break pest.iterators.line_index.
- Position
- Below the diagonal: pest.iterators.flat_pairs uses a module listed above it, which is the healthy direction.
24→3 pest.iterators.flat_pairs uses pest.iterators.queueable_token✕
- Connections
- 2 pairs of types, where a type in pest.iterators.flat_pairs uses a type in pest.iterators.queueable_token.
- The types involved
pest.iterators.flat_pairs.FlatPairs→pest.iterators.queueable_token.QueueableTokenpest.iterators.flat_pairs.flat_pairs$module→pest.iterators.queueable_token.QueueableToken
- Direction
- pest.iterators.flat_pairs uses pest.iterators.queueable_token, so a change to pest.iterators.queueable_token can break pest.iterators.flat_pairs, while a change to pest.iterators.flat_pairs can't break pest.iterators.queueable_token.
- Position
- Below the diagonal: pest.iterators.flat_pairs uses a module listed above it, which is the healthy direction.
24→13 pest.iterators.flat_pairs uses pest.iterators.tokens✕
- Connections
- 1 pair of types, where a type in pest.iterators.flat_pairs uses a type in pest.iterators.tokens.
- The types involved
pest.iterators.flat_pairs.FlatPairs→pest.iterators.tokens.Tokens
- Direction
- pest.iterators.flat_pairs uses pest.iterators.tokens, so a change to pest.iterators.tokens can break pest.iterators.flat_pairs, while a change to pest.iterators.flat_pairs can't break pest.iterators.tokens.
- Position
- Below the diagonal: pest.iterators.flat_pairs uses a module listed above it, which is the healthy direction.
25→15 pest.position uses pest.span✕
- Connections
- 1 pair of types, where a type in pest.position uses a type in pest.span.
- The types involved
pest.position.Position→pest.span.Span
- Direction
- pest.position uses pest.span, so a change to pest.span can break pest.position, while a change to pest.position can't break pest.span.
- Position
- Below the diagonal: pest.position uses a module listed above it, which is the healthy direction.
26→17 pest_debugger uses pest_meta.optimizer✕
- Connections
- 1 pair of types, where a type in pest_debugger uses a type in pest_meta.optimizer.
- The types involved
pest_debugger.DebuggerContext→pest_meta.optimizer.OptimizedRule
- Direction
- pest_debugger uses pest_meta.optimizer, so a change to pest_meta.optimizer can break pest_debugger, while a change to pest_debugger can't break pest_meta.optimizer.
- Position
- Below the diagonal: pest_debugger uses a module listed above it, which is the healthy direction.
27→17 pest_meta.optimizer.restorer uses pest_meta.optimizer✕
- Connections
- 2 pairs of types, where a type in pest_meta.optimizer.restorer uses a type in pest_meta.optimizer.
- The types involved
pest_meta.optimizer.restorer.restorer$module→pest_meta.optimizer.OptimizedExprpest_meta.optimizer.restorer.restorer$module→pest_meta.optimizer.OptimizedRule
- Direction
- pest_meta.optimizer.restorer uses pest_meta.optimizer, so a change to pest_meta.optimizer can break pest_meta.optimizer.restorer, while a change to pest_meta.optimizer.restorer can't break pest_meta.optimizer.
- Position
- Below the diagonal: pest_meta.optimizer.restorer uses a module listed above it, which is the healthy direction.
28→2 pest.iterators.pairs uses pest.iterators.line_index✕
- Connections
- 2 pairs of types, where a type in pest.iterators.pairs uses a type in pest.iterators.line_index.
- The types involved
pest.iterators.pairs.Pairs→pest.iterators.line_index.LineIndexpest.iterators.pairs.pairs$module→pest.iterators.line_index.LineIndex
- Direction
- pest.iterators.pairs uses pest.iterators.line_index, so a change to pest.iterators.line_index can break pest.iterators.pairs, while a change to pest.iterators.pairs can't break pest.iterators.line_index.
- Position
- Below the diagonal: pest.iterators.pairs uses a module listed above it, which is the healthy direction.
28→3 pest.iterators.pairs uses pest.iterators.queueable_token✕
- Connections
- 2 pairs of types, where a type in pest.iterators.pairs uses a type in pest.iterators.queueable_token.
- The types involved
pest.iterators.pairs.Pairs→pest.iterators.queueable_token.QueueableTokenpest.iterators.pairs.pairs$module→pest.iterators.queueable_token.QueueableToken
- Direction
- pest.iterators.pairs uses pest.iterators.queueable_token, so a change to pest.iterators.queueable_token can break pest.iterators.pairs, while a change to pest.iterators.pairs can't break pest.iterators.queueable_token.
- Position
- Below the diagonal: pest.iterators.pairs uses a module listed above it, which is the healthy direction.
28→13 pest.iterators.pairs uses pest.iterators.tokens✕
- Connections
- 1 pair of types, where a type in pest.iterators.pairs uses a type in pest.iterators.tokens.
- The types involved
pest.iterators.pairs.Pairs→pest.iterators.tokens.Tokens
- Direction
- pest.iterators.pairs uses pest.iterators.tokens, so a change to pest.iterators.tokens can break pest.iterators.pairs, while a change to pest.iterators.pairs can't break pest.iterators.tokens.
- Position
- Below the diagonal: pest.iterators.pairs uses a module listed above it, which is the healthy direction.
28→24 pest.iterators.pairs uses pest.iterators.flat_pairs✕
- Connections
- 1 pair of types, where a type in pest.iterators.pairs uses a type in pest.iterators.flat_pairs.
- The types involved
pest.iterators.pairs.Pairs→pest.iterators.flat_pairs.FlatPairs
- Direction
- pest.iterators.pairs uses pest.iterators.flat_pairs, so a change to pest.iterators.flat_pairs can break pest.iterators.pairs, while a change to pest.iterators.pairs can't break pest.iterators.flat_pairs.
- Position
- Below the diagonal: pest.iterators.pairs uses a module listed above it, which is the healthy direction.
28→32 pest.iterators.pairs uses pest.iterators.pair part of a loop✕
- Connections
- 1 pair of types, where a type in pest.iterators.pairs uses a type in pest.iterators.pair.
- The types involved
pest.iterators.pairs.Pairs→pest.iterators.pair.Pair
- Direction
- pest.iterators.pairs uses pest.iterators.pair, so a change to pest.iterators.pair can break pest.iterators.pairs, while a change to pest.iterators.pairs can't break pest.iterators.pair.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
29→3 pest.parser_state uses pest.iterators.queueable_token✕
- Connections
- 1 pair of types, where a type in pest.parser_state uses a type in pest.iterators.queueable_token.
- The types involved
pest.parser_state.ParserState→pest.iterators.queueable_token.QueueableToken
- Direction
- pest.parser_state uses pest.iterators.queueable_token, so a change to pest.iterators.queueable_token can break pest.parser_state, while a change to pest.parser_state can't break pest.iterators.queueable_token.
- Position
- Below the diagonal: pest.parser_state uses a module listed above it, which is the healthy direction.
29→6 pest.parser_state uses pest.stack✕
- Connections
- 1 pair of types, where a type in pest.parser_state uses a type in pest.stack.
- The types involved
pest.parser_state.ParserState→pest.stack.Stack
- Direction
- pest.parser_state uses pest.stack, so a change to pest.stack can break pest.parser_state, while a change to pest.parser_state can't break pest.stack.
- Position
- Below the diagonal: pest.parser_state uses a module listed above it, which is the healthy direction.
29→25 pest.parser_state uses pest.position✕
- Connections
- 1 pair of types, where a type in pest.parser_state uses a type in pest.position.
- The types involved
pest.parser_state.ParserState→pest.position.Position
- Direction
- pest.parser_state uses pest.position, so a change to pest.position can break pest.parser_state, while a change to pest.parser_state can't break pest.position.
- Position
- Below the diagonal: pest.parser_state uses a module listed above it, which is the healthy direction.
30→26 pest_debugger.main uses pest_debugger✕
- Connections
- 1 pair of types, where a type in pest_debugger.main uses a type in pest_debugger.
- The types involved
pest_debugger.main.Cli→pest_debugger.DebuggerContext
- Direction
- pest_debugger.main uses pest_debugger, so a change to pest_debugger can break pest_debugger.main, while a change to pest_debugger.main can't break pest_debugger.
- Position
- Below the diagonal: pest_debugger.main uses a module listed above it, which is the healthy direction.
31→15 pest.error uses pest.span✕
- Connections
- 2 pairs of types, where a type in pest.error uses a type in pest.span.
- The types involved
pest.error.Error→pest.span.Spanpest.error.LineColLocation→pest.span.Span
- Direction
- pest.error uses pest.span, so a change to pest.span can break pest.error, while a change to pest.error can't break pest.span.
- Position
- Below the diagonal: pest.error uses a module listed above it, which is the healthy direction.
31→25 pest.error uses pest.position✕
- Connections
- 2 pairs of types, where a type in pest.error uses a type in pest.position.
- The types involved
pest.error.Error→pest.position.Positionpest.error.LineColLocation→pest.position.Position
- Direction
- pest.error uses pest.position, so a change to pest.position can break pest.error, while a change to pest.error can't break pest.position.
- Position
- Below the diagonal: pest.error uses a module listed above it, which is the healthy direction.
31→29 pest.error uses pest.parser_state✕
- Connections
- 2 pairs of types, where a type in pest.error uses a type in pest.parser_state.
- The types involved
pest.error.Error→pest.parser_state.ParseAttemptspest.error.ErrorInner→pest.parser_state.ParseAttempts
- Direction
- pest.error uses pest.parser_state, so a change to pest.parser_state can break pest.error, while a change to pest.error can't break pest.parser_state.
- Position
- Below the diagonal: pest.error uses a module listed above it, which is the healthy direction.
32→2 pest.iterators.pair uses pest.iterators.line_index✕
- Connections
- 2 pairs of types, where a type in pest.iterators.pair uses a type in pest.iterators.line_index.
- The types involved
pest.iterators.pair.Pair→pest.iterators.line_index.LineIndexpest.iterators.pair.pair$module→pest.iterators.line_index.LineIndex
- Direction
- pest.iterators.pair uses pest.iterators.line_index, so a change to pest.iterators.line_index can break pest.iterators.pair, while a change to pest.iterators.pair can't break pest.iterators.line_index.
- Position
- Below the diagonal: pest.iterators.pair uses a module listed above it, which is the healthy direction.
32→3 pest.iterators.pair uses pest.iterators.queueable_token✕
- Connections
- 2 pairs of types, where a type in pest.iterators.pair uses a type in pest.iterators.queueable_token.
- The types involved
pest.iterators.pair.Pair→pest.iterators.queueable_token.QueueableTokenpest.iterators.pair.pair$module→pest.iterators.queueable_token.QueueableToken
- Direction
- pest.iterators.pair uses pest.iterators.queueable_token, so a change to pest.iterators.queueable_token can break pest.iterators.pair, while a change to pest.iterators.pair can't break pest.iterators.queueable_token.
- Position
- Below the diagonal: pest.iterators.pair uses a module listed above it, which is the healthy direction.
32→13 pest.iterators.pair uses pest.iterators.tokens✕
- Connections
- 1 pair of types, where a type in pest.iterators.pair uses a type in pest.iterators.tokens.
- The types involved
pest.iterators.pair.Pair→pest.iterators.tokens.Tokens
- Direction
- pest.iterators.pair uses pest.iterators.tokens, so a change to pest.iterators.tokens can break pest.iterators.pair, while a change to pest.iterators.pair can't break pest.iterators.tokens.
- Position
- Below the diagonal: pest.iterators.pair uses a module listed above it, which is the healthy direction.
32→15 pest.iterators.pair uses pest.span✕
- Connections
- 1 pair of types, where a type in pest.iterators.pair uses a type in pest.span.
- The types involved
pest.iterators.pair.Pair→pest.span.Span
- Direction
- pest.iterators.pair uses pest.span, so a change to pest.span can break pest.iterators.pair, while a change to pest.iterators.pair can't break pest.span.
- Position
- Below the diagonal: pest.iterators.pair uses a module listed above it, which is the healthy direction.
32→28 pest.iterators.pair uses pest.iterators.pairs✕
- Connections
- 1 pair of types, where a type in pest.iterators.pair uses a type in pest.iterators.pairs.
- The types involved
pest.iterators.pair.Pair→pest.iterators.pairs.Pairs
- Direction
- pest.iterators.pair uses pest.iterators.pairs, so a change to pest.iterators.pairs can break pest.iterators.pair, while a change to pest.iterators.pair can't break pest.iterators.pairs.
- Position
- Below the diagonal: pest.iterators.pair uses a module listed above it, which is the healthy direction.
33→3 pest.iterators.pairs_builder uses pest.iterators.queueable_token✕
- Connections
- 1 pair of types, where a type in pest.iterators.pairs_builder uses a type in pest.iterators.queueable_token.
- The types involved
pest.iterators.pairs_builder.pairs_builder$module→pest.iterators.queueable_token.QueueableToken
- Direction
- pest.iterators.pairs_builder uses pest.iterators.queueable_token, so a change to pest.iterators.queueable_token can break pest.iterators.pairs_builder, while a change to pest.iterators.pairs_builder can't break pest.iterators.queueable_token.
- Position
- Below the diagonal: pest.iterators.pairs_builder uses a module listed above it, which is the healthy direction.
33→28 pest.iterators.pairs_builder uses pest.iterators.pairs✕
- Connections
- 1 pair of types, where a type in pest.iterators.pairs_builder uses a type in pest.iterators.pairs.
- The types involved
pest.iterators.pairs_builder.PairsBuilder→pest.iterators.pairs.Pairs
- Direction
- pest.iterators.pairs_builder uses pest.iterators.pairs, so a change to pest.iterators.pairs can break pest.iterators.pairs_builder, while a change to pest.iterators.pairs_builder can't break pest.iterators.pairs.
- Position
- Below the diagonal: pest.iterators.pairs_builder uses a module listed above it, which is the healthy direction.
34→28 pest_generator.docs uses pest.iterators.pairs✕
- Connections
- 1 pair of types, where a type in pest_generator.docs uses a type in pest.iterators.pairs.
- The types involved
pest_generator.docs.docs$module→pest.iterators.pairs.Pairs
- Direction
- pest_generator.docs uses pest.iterators.pairs, so a change to pest.iterators.pairs can break pest_generator.docs, while a change to pest_generator.docs can't break pest.iterators.pairs.
- Position
- Below the diagonal: pest_generator.docs uses a module listed above it, which is the healthy direction.
35→5 pest_meta.parser uses pest.pratt_parser✕
- Connections
- 1 pair of types, where a type in pest_meta.parser uses a type in pest.pratt_parser.
- The types involved
pest_meta.parser.parser$module→pest.pratt_parser.PrattParser
- Direction
- pest_meta.parser uses pest.pratt_parser, so a change to pest.pratt_parser can break pest_meta.parser, while a change to pest_meta.parser can't break pest.pratt_parser.
- Position
- Below the diagonal: pest_meta.parser uses a module listed above it, which is the healthy direction.
35→12 pest_meta.parser uses pest_meta.ast✕
- Connections
- 3 pairs of types, where a type in pest_meta.parser uses a type in pest_meta.ast.
- The types involved
pest_meta.parser.ParserRule→pest_meta.ast.RuleTypepest_meta.parser.parser$module→pest_meta.ast.Exprpest_meta.parser.parser$module→pest_meta.ast.Rule
- Direction
- pest_meta.parser uses pest_meta.ast, so a change to pest_meta.ast can break pest_meta.parser, while a change to pest_meta.parser can't break pest_meta.ast.
- Position
- Below the diagonal: pest_meta.parser uses a module listed above it, which is the healthy direction.
35→15 pest_meta.parser uses pest.span✕
- Connections
- 2 pairs of types, where a type in pest_meta.parser uses a type in pest.span.
- The types involved
pest_meta.parser.ParserNode→pest.span.Spanpest_meta.parser.ParserRule→pest.span.Span
- Direction
- pest_meta.parser uses pest.span, so a change to pest.span can break pest_meta.parser, while a change to pest_meta.parser can't break pest.span.
- Position
- Below the diagonal: pest_meta.parser uses a module listed above it, which is the healthy direction.
35→28 pest_meta.parser uses pest.iterators.pairs✕
- Connections
- 1 pair of types, where a type in pest_meta.parser uses a type in pest.iterators.pairs.
- The types involved
pest_meta.parser.parser$module→pest.iterators.pairs.Pairs
- Direction
- pest_meta.parser uses pest.iterators.pairs, so a change to pest.iterators.pairs can break pest_meta.parser, while a change to pest_meta.parser can't break pest.iterators.pairs.
- Position
- Below the diagonal: pest_meta.parser uses a module listed above it, which is the healthy direction.
36→17 pest_vm uses pest_meta.optimizer✕
- Connections
- 2 pairs of types, where a type in pest_vm uses a type in pest_meta.optimizer.
- The types involved
pest_vm.Vm→pest_meta.optimizer.OptimizedExprpest_vm.Vm→pest_meta.optimizer.OptimizedRule
- Direction
- pest_vm uses pest_meta.optimizer, so a change to pest_meta.optimizer can break pest_vm, while a change to pest_vm can't break pest_meta.optimizer.
- Position
- Below the diagonal: pest_vm uses a module listed above it, which is the healthy direction.
36→29 pest_vm uses pest.parser_state✕
- Connections
- 1 pair of types, where a type in pest_vm uses a type in pest.parser_state.
- The types involved
pest_vm.Vm→pest.parser_state.ParserState
- Direction
- pest_vm uses pest.parser_state, so a change to pest.parser_state can break pest_vm, while a change to pest_vm can't break pest.parser_state.
- Position
- Below the diagonal: pest_vm uses a module listed above it, which is the healthy direction.
37→31 pest.error.miette_adapter uses pest.error✕
- Connections
- 1 pair of types, where a type in pest.error.miette_adapter uses a type in pest.error.
- The types involved
pest.error.miette_adapter.MietteAdapter→pest.error.Error
- Direction
- pest.error.miette_adapter uses pest.error, so a change to pest.error can break pest.error.miette_adapter, while a change to pest.error.miette_adapter can't break pest.error.
- Position
- Below the diagonal: pest.error.miette_adapter uses a module listed above it, which is the healthy direction.
38→11 pest_generator.generator uses pest_generator.parse_derive✕
- Connections
- 1 pair of types, where a type in pest_generator.generator uses a type in pest_generator.parse_derive.
- The types involved
pest_generator.generator.generator$module→pest_generator.parse_derive.ParsedDerive
- Direction
- pest_generator.generator uses pest_generator.parse_derive, so a change to pest_generator.parse_derive can break pest_generator.generator, while a change to pest_generator.generator can't break pest_generator.parse_derive.
- Position
- Below the diagonal: pest_generator.generator uses a module listed above it, which is the healthy direction.
38→17 pest_generator.generator uses pest_meta.optimizer✕
- Connections
- 2 pairs of types, where a type in pest_generator.generator uses a type in pest_meta.optimizer.
- The types involved
pest_generator.generator.generator$module→pest_meta.optimizer.OptimizedExprpest_generator.generator.generator$module→pest_meta.optimizer.OptimizedRule
- Direction
- pest_generator.generator uses pest_meta.optimizer, so a change to pest_meta.optimizer can break pest_generator.generator, while a change to pest_generator.generator can't break pest_meta.optimizer.
- Position
- Below the diagonal: pest_generator.generator uses a module listed above it, which is the healthy direction.
38→34 pest_generator.generator uses pest_generator.docs✕
- Connections
- 1 pair of types, where a type in pest_generator.generator uses a type in pest_generator.docs.
- The types involved
pest_generator.generator.generator$module→pest_generator.docs.DocComment
- Direction
- pest_generator.generator uses pest_generator.docs, so a change to pest_generator.docs can break pest_generator.generator, while a change to pest_generator.generator can't break pest_generator.docs.
- Position
- Below the diagonal: pest_generator.generator uses a module listed above it, which is the healthy direction.
39→15 pest_meta.validator uses pest.span✕
- Connections
- 1 pair of types, where a type in pest_meta.validator uses a type in pest.span.
- The types involved
pest_meta.validator.validator$module→pest.span.Span
- Direction
- pest_meta.validator uses pest.span, so a change to pest.span can break pest_meta.validator, while a change to pest_meta.validator can't break pest.span.
- Position
- Below the diagonal: pest_meta.validator uses a module listed above it, which is the healthy direction.
39→28 pest_meta.validator uses pest.iterators.pairs✕
- Connections
- 1 pair of types, where a type in pest_meta.validator uses a type in pest.iterators.pairs.
- The types involved
pest_meta.validator.validator$module→pest.iterators.pairs.Pairs
- Direction
- pest_meta.validator uses pest.iterators.pairs, so a change to pest.iterators.pairs can break pest_meta.validator, while a change to pest_meta.validator can't break pest.iterators.pairs.
- Position
- Below the diagonal: pest_meta.validator uses a module listed above it, which is the healthy direction.
39→31 pest_meta.validator uses pest.error✕
- Connections
- 1 pair of types, where a type in pest_meta.validator uses a type in pest.error.
- The types involved
pest_meta.validator.validator$module→pest.error.Error
- Direction
- pest_meta.validator uses pest.error, so a change to pest.error can break pest_meta.validator, while a change to pest_meta.validator can't break pest.error.
- Position
- Below the diagonal: pest_meta.validator uses a module listed above it, which is the healthy direction.
39→35 pest_meta.validator uses pest_meta.parser✕
- Connections
- 2 pairs of types, where a type in pest_meta.validator uses a type in pest_meta.parser.
- The types involved
pest_meta.validator.validator$module→pest_meta.parser.ParserExprpest_meta.validator.validator$module→pest_meta.parser.ParserRule
- Direction
- pest_meta.validator uses pest_meta.parser, so a change to pest_meta.parser can break pest_meta.validator, while a change to pest_meta.validator can't break pest_meta.parser.
- Position
- Below the diagonal: pest_meta.validator uses a module listed above it, which is the healthy direction.
40→31 pest_meta.validator.stack_loops uses pest.error✕
- Connections
- 2 pairs of types, where a type in pest_meta.validator.stack_loops uses a type in pest.error.
- The types involved
pest_meta.validator.stack_loops.StackAnalysis→pest.error.Errorpest_meta.validator.stack_loops.stack_loops$module→pest.error.Error
- Direction
- pest_meta.validator.stack_loops uses pest.error, so a change to pest.error can break pest_meta.validator.stack_loops, while a change to pest_meta.validator.stack_loops can't break pest.error.
- Position
- Below the diagonal: pest_meta.validator.stack_loops uses a module listed above it, which is the healthy direction.
40→35 pest_meta.validator.stack_loops uses pest_meta.parser✕
- Connections
- 2 pairs of types, where a type in pest_meta.validator.stack_loops uses a type in pest_meta.parser.
- The types involved
pest_meta.validator.stack_loops.StackAnalysis→pest_meta.parser.ParserNodepest_meta.validator.stack_loops.stack_loops$module→pest_meta.parser.ParserExpr
- Direction
- pest_meta.validator.stack_loops uses pest_meta.parser, so a change to pest_meta.parser can break pest_meta.validator.stack_loops, while a change to pest_meta.validator.stack_loops can't break pest_meta.parser.
- Position
- Below the diagonal: pest_meta.validator.stack_loops uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 25 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 6 | Medium |
Roadmap
First, implement a diagnostic log accessible via a debug flag to capture error details that are currently lost, and immediately clean up orphaned source files to ensure codebase freshness. Next, establish a structured repository for architecture decision records to document significant design choices and their consequences. Finally, automate the release process in CI to ensure deployments are repeatable and reversible.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +6.3 pts | Low | ADR Quality |
| Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce. | +7.6 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. | +5.6 pts | Medium | Architecture documentation |
| Automate the release in CI — a deploy stage for a service (Helm/Kubernetes manifests or an equivalent rollout), or a tag-triggered publish job for an artifact — so releases are repeatable and reversible. | +5.1 pts | Medium | Deployment & Rollback |
| Resolve the 11 Orphaned file finding(s) in Knowledge Freshness — start with pair.rs, prec_climber.rs, mod.rs. | +2.4 pts | Medium | Knowledge Freshness |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +2.3 pts | Medium | Release Hygiene |
| Resolve the 5 REDACTED finding(s) charged to Static Analysis (SAST) — the other 17 are reported here at file:line but scored by D36 (supply-chain provenance), which charges them once. | +1.0 pts | Low | Static Analysis (SAST) |
| Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite. | +1.6 pts | Medium | Documentation (README) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.6 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| pest/src/position.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| generator/src/lib.rs | 6.7 | Mixed | Explicit Debt: TodoComment |
| meta/src/ast.rs | 7.0 | Mixed | Cyclomatic Complexity: Expr::fmt (cyclomatic 25) |
| generator/src/generator.rs | 7.1 | Mixed | God Classes: FunctionTooLong: pest_generator::generator::generate_expr |
| debugger/src/main.rs | 7.1 | Mixed | Cyclomatic Complexity: Cli::execute_command (cyclomatic 19) |
| pest/src/parser_state.rs | 7.1 | Mixed | Cyclomatic Complexity: ParserState::rule (cyclomatic 16) |
| meta/src/parser.rs | 7.2 | Mixed | Cyclomatic Complexity: pest_meta::parser::consume_expr::unaries (cyclomatic 34) |
| meta/src/validator.rs | 7.2 | Mixed | Cyclomatic Complexity: pest_meta::validator::is_non_progressing (cyclomatic 20) |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| meta/src/validator/stack_loops.rs | 7.4 | Mixed | Cyclomatic Complexity: StackAnalysis::step (cyclomatic 30) |
| vm/src/lib.rs | 7.8 | Mixed | Cyclomatic Complexity: Vm::parse_rule (cyclomatic 34) |
| meta/src/optimizer/mod.rs | 7.8 | Mixed | Cyclomatic Complexity: OptimizedExpr::fmt (cyclomatic 22) |
| pest/src/error.rs | 7.8 | Mixed | Cognitive Complexity: Error::parse_attempts_error (cognitive 35) |
| pest/src/iterators/pair.rs | 7.8 | Mixed | Code Duplication: Duplicated block (8 lines × 2) |
| meta/src/optimizer/factorizer.rs | 8.2 | Near-clean | Explicit Debt: FixmeComment |
| bootstrap/src/main.rs | 8.2 | Near-clean | Explicit Debt: TodoComment |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 48 of 48 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
What we checked — 48 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, 96 of 118 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Watchdog duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
| LLM (sampled · advisory) | Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement | — | ◐ LLM · sampled · advisory |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT READ here — but this repository measures it: a coverage step in CI (`cargo llvm-cov`) shows that coverage is collected and tracked in your own CI. The built-in collector has no runner for this ecosystem (.rs), so the analyzer could not read the number — a gap in the analyzer's language coverage, not an unmeasured repo. Not scored. To have the real number read, produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
- D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D24 Comment Value — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D27 Navigability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- D44 Platform End-of-Life — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a Dockerfile) is simply not read here yet.
- AX6 Interface segregation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- GD1 Unfinished & placeholder code — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- X12 Unreachable branch — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X13 Undrained process stream — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X16 Unfloored truncation loop — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X17 Uncapped recursion over a caller-supplied document — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X18 Disposal-pattern correctness — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X19 Unrestored process-global state — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X22 Contradicted release guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Java, TypeScript/JavaScript, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X23 Unguarded diagnostic materialisation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X24 Document value interpolated into markup unescaped — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X25 Inert configuration knob — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart and Ruby source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart or Ruby was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X3 Exception handling — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go and JavaScript/TypeScript source only, and no C# was loaded and no PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go, JavaScript or TypeScript was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X5 Nullable reference types — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax and MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, and Kotlin source only, and no C# was loaded, no TypeScript was found, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D11 Test Reliability: Flakiness is inferred from history/markers — Watchdog runs the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
11 function(s) exceeded the cyclomatic complexity threshold of 15; the worst was pest_meta::parser::consume_expr::unaries at 34. A further 7 function(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being PestParser::parse at 67 — they are counted neither in the figure above nor in this dimension's score. 2 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold functions was excluded, so the exclusion is disclosed nowhere in the file itself: meta/src/grammar.rs (PestParser::parse at 67), generator/src/generator.rs (pest_generator::generator::generate_expr at 21). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 11 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with pest_meta::parser::consume_expr::unaries (cyclomatic 34), Vm::parse_rule (cyclomatic 34), StackAnalysis::step (cyclomatic 30). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 11 together lifts Cyclomatic Complexity from 8.3 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
15 function(s) exceeded the cognitive complexity threshold of 15; the worst was pest_meta::parser::consume_expr::unaries at 42.
What to do
- Bring the 15 bodies over 15 down to 15 or less in Cognitive Complexity — start with pest_meta::parser::consume_expr::unaries (cognitive 42), Error::parse_attempts_error (cognitive 35), pest_meta::optimizer::skipper::skip (cognitive 31). — 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 15 together lifts Cognitive Complexity from 7.7 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
7 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 2 FileTooLong finding(s) in God Classes — start with parser_state.rs, generator.rs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 FunctionTooLong finding(s) in God Classes — start with generator.rs (2). — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 TooManyFunctions finding(s) in God Classes — start with mod.rs. — One of this dimension's main actionable groups (1 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
17 duplicated block group(s) detected. One further row reports members as variants of one another; it aggregates block groups already counted above and is not itself counted.
What to do
- Resolve the 3 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with ast.rs (2), generator.rs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with ast.rs (2). — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Near-duplicate member pair (36 shared lines) finding(s) in Code Duplication — start with ast.rs. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
8 production modules (Cargo), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 2 module(s) off the main sequence, with abstractness counted on 6 of the 8 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What to do
- Resolve the 2 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (2 warning-level).
- Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
0 of 25 classes have LCOM4 above 3.
D9 · Test Distribution
604 test methods: 342 unit, 262 integration, 0 BDD, 0 e2e. The Rust suite contributes 604 `#[test]` function(s) across 44 file(s) declaring at least one; its unit/integration split is Cargo's own — 20 of those file(s) are integration-test targets under a crate's tests/ directory, and the rest are #[test] functions compiled into the crate they test.
D11 · Test Reliability
0 flaky across 1 measured tier(s). Rust (repository root, 44 test files): measured (0 flaky).
D12 · Dependency Hygiene
3 outdated, 0 yanked direct Cargo dependencies. Only DIRECT edges are graded: a transitive crate cannot be moved past what its parent's requirement admits, so reporting one would be advice its owner cannot take. A newer release is reported only where this repository's OWN requirement already admits it, so the remedy is `cargo update` and never a manifest edit — which means a release outside the declared range is deliberately NOT charged, because a written-down constraint is a decision rather than a defect. Note that a bare requirement is a CARET, and for a 0.x crate its ceiling is the minor. Whether any crate is UNMAINTAINED is not graded — crates.io publishes no maintenance status, and release age does not stand in for one. Known CVEs in this dependency graph are D30's question, read from Cargo.lock there.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 98 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository's Cargo.lock closed over its manifests' `[dependencies]` and `[build-dependencies]`. Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository.
D15 · Churn × Complexity Hotspots
Top hotspots: vm/src/lib.rs (2×34=68); meta/src/ast.rs (2×25=50); meta/src/optimizer/mod.rs (2×22=44)
What to do
- Resolve the 3 Hotspot finding(s) in Churn × Complexity Hotspots — start with lib.rs, ast.rs, mod.rs. — One of this dimension's main actionable groups (3 warning-level).
D16 · Bus Factor
3 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is pest/src/lib.rs. Counted over 36 of the 51 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D17 · Explicit Debt
5 deducted task-comment markers across 19747 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 4 TodoComment finding(s) in Explicit Debt — start with position.rs (2), lib.rs, main.rs. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 1 FixmeComment finding(s) in Explicit Debt — start with factorizer.rs. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 4 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
0 of 8 build units (Cargo) flagged as possibly oversized/incoherent.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
25 finding(s): 0 critical, 24 high, 1 medium, 0 low. 17 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens.
What to do
- Resolve the 5 REDACTED finding(s) charged to Static Analysis (SAST) — the other 17 are reported here at file:line but scored by D36 (supply-chain provenance), which charges them once. — One of this dimension's main actionable groups (22 issue-level, 5 of them charged here).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D30 · Dependency Vulnerabilities
No known-vulnerable dependencies in any ecosystem this repository declares.
D34 · Knowledge Freshness
11 of 36 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is pest/src/iterators/pair.rs. Counted over 36 of the 51 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 11 Orphaned file finding(s) in Knowledge Freshness — start with pair.rs, prec_climber.rs, mod.rs. — One of this dimension's main actionable groups (11 recommendation-level).
- Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — 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.
Frontend & cross-cutting dimensions
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX4 · Dependency direction
AX9 · CQS / query purity
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Add a README to the 8 of 10 project(s) that lack one — worth up to 1.6 pts.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
- 55/76 types (72%) declared in the published library are public. For a library, every public type is a stability contract — keep implementation types off the surface and expose only the intended API.
What to do
- Keep implementation types off the public surface (Rust: `pub(crate)`, or keep the module private) so internals can change without breaking consumers.
P2 · Observability
- No logging or diagnostics emission found. This repository ships a binary its users launch rather than a service you operate, so there is no operator to page — but when a run fails on a user's machine, neither they nor you have anything to read.
What to do
- Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.
P3 · Security & performance tooling
What to do
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- No release automation was found in CI — neither a deploy stage (Helm/Kubernetes/compose manifests, an orchestrated rollout) nor a publish job that ships the built artifact. Releases appear to be run by hand, which is slower, less repeatable and harder to reverse.
What to do
- Automate the release in CI — a deploy stage for a service (Helm/Kubernetes manifests or an equivalent rollout), or a tag-triggered publish job for an artifact — so releases are repeatable and reversible.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
PF1 · Benchmark discipline
X1 · Async correctness
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X21 · Side-effecting pattern guard
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X30 · Support guard that admits what it rejects
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 94% | Exemplary | Solid. |
| Architecture | 98% | Exemplary | Strongest area. |
| Maturity | 58% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 41% | Weak — gated by P2, P4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 71% | Adequate — gated by D29, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 85% | Strong | Solid. |
Unscored — 2 check(s) recorded observations but carry no score
- P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
- X10 Duplicated predicate — 1 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 — 68 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one.
- AX2 Stateful singletons — Not applicable: Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no data at rest for these controls to protect.
- C2 Access Controls — No access-control surface detected in the analyzed source — this repository starts no server another machine can reach (no actix-web HttpServer, axum::serve, Rocket launch, warp::serve, poem or salvo Server, tonic Server::builder, hyper or tiny_http server outside examples and tests, none bound beyond loopback). Access control is therefore N/A here — a crate is authorized by the application that serves it, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~4860 lines of test source are present (.rs) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — Naming consistency is measured on C# only; Rust not measured.
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed Rust surface was not measured.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ projects each declaring an entity of their own. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C# and Visual Basic comments only — this repository's production source is .rs, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.rs), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (7 value object(s))
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the Rust source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF2 Allocation hygiene — Not applicable: Rust spells out every heap allocation and makes borrowed slices (&[T], &str) its ordinary parameter types, so the allocation-aware style this card rewards elsewhere is the language's baseline rather than a rung to climb.
- PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
- S1 Web-Security Posture — No web surface: 46 Rust file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation and obsolete TLS versions, and none was found. This repository serves no HTTP of its own — no HTTP-server crate (actix-web, axum, Rocket, warp, poem, tide, salvo, tonic, a hyper server, …) among its Cargo manifests' run-time dependencies, and no server started in its production source — so HTTPS enforcement, HSTS, cookie flags and input validation are N/A here, as they are for a C# library or worker. If this codebase starts serving HTTP, the dimension reactivates automatically.
- X12 Unreachable branch — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X13 Undrained process stream — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X16 Unfloored truncation loop — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X17 Uncapped recursion over a caller-supplied document — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X18 Disposal-pattern correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X19 Unrestored process-global state — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X2 Cancellation propagation — no C# was loaded; this repository's Rust was read, and no request in it can be cancelled by a caller — a Rust request takes no token: a future is cancelled by dropping it, from outside the call (select!, a timeout, an aborted task), and reqwest, hyper and tonic take none
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X22 Contradicted release guard — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X23 Unguarded diagnostic materialisation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X24 Document value interpolated into markup unescaped — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X25 Inert configuration knob — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. Rust's compiler refuses the unsynchronised version: a collection shared between a callback's thread and the waiting body must be `Sync`, which a `Vec`, `VecDeque` or `HashMap` is only behind a `Mutex`/`RwLock`, so the race this check looks for cannot be written in safe Rust. Not a gap in the analyzer and not a finding about your code.
- X3 Exception handling — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Rust was read, and it logs through none: the `log` crate's macros take one finished message (as log4net does in C#; its `kv` values are an opt-in its backends mostly drop), `println!`/`eprintln!` are not loggers, or it makes no log call outside its tests and examples at all. Calls through `tracing` (`tracing::info!`, or `info!` imported from it) would be judged.
- X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 24 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 67 finding(s)
- pest_meta::parser::consume_expr::unaries (cyclomatic 34) meta/src/parser.rs:343
- pest_meta::validator::is_non_progressing (cyclomatic 20) meta/src/validator.rs:334
- pest_meta::validator::is_non_failing (cyclomatic 20) meta/src/validator.rs:430
- pest_meta::parser::unescape (cyclomatic 19) meta/src/parser.rs:709
- pest_meta::validator::left_recursion::check_expr (cyclomatic 17) meta/src/validator.rs:638
- TodoComment pest/src/position.rs:104
- TodoComment pest/src/position.rs:354
- TodoComment generator/src/lib.rs:77
- TodoComment bootstrap/src/main.rs:15
- Hotspot: vm/src/lib.rs vm/src/lib.rs:76
- Hotspot: meta/src/ast.rs meta/src/ast.rs:303
- Hotspot: meta/src/optimizer/mod.rs meta/src/optimizer/mod.rs:289
- pest_meta::parser::consume_expr::unaries (cognitive 42) meta/src/parser.rs:343
- pest_meta::optimizer::skipper::skip (cognitive 31) meta/src/optimizer/skipper.rs:14
- pest_meta::parser::unescape (cognitive 27) meta/src/parser.rs:709
- Duplicated block (11 lines × 2) generator/src/generator.rs:581
- Duplicated block (11 lines × 2) meta/src/ast.rs:331
- Duplicated block (11 lines × 2) meta/src/ast.rs:347
- StackAnalysis::ident (cognitive 24) meta/src/validator/stack_loops.rs:529
- StackAnalysis::step (cognitive 17) meta/src/validator/stack_loops.rs:423
- pest_generator::derive_parser (cognitive 16) generator/src/lib.rs:58
- pest_generator::docs::consume (cognitive 16) generator/src/docs.rs:40
- FileTooLong: src/parser_state.rs pest/src/parser_state.rs
- FileTooLong: src/generator.rs generator/src/generator.rs
- FunctionTooLong: pest_generator::generator::generate_expr generator/src/generator.rs:429
- FunctionTooLong: pest_generator::generator::generate_expr_atomic generator/src/generator.rs:638
- Duplicated block (9 lines × 2) meta/src/ast.rs:368
- Duplicated block (9 lines × 2) meta/src/ast.rs:401
- Off the main sequence: pest
- Off the main sequence: pest_meta
- Vm::parse_rule (cyclomatic 34) vm/src/lib.rs:76
- StackAnalysis::step (cyclomatic 30) meta/src/validator/stack_loops.rs:423
- Expr::fmt (cyclomatic 25) meta/src/ast.rs:303
- OptimizedExpr::fmt (cyclomatic 22) meta/src/optimizer/mod.rs:289
- Cli::execute_command (cyclomatic 19) debugger/src/main.rs:133
- ParserState::rule (cyclomatic 16) pest/src/parser_state.rs:743
- FixmeComment meta/src/optimizer/factorizer.rs:29
- Error::parse_attempts_error (cognitive 35) pest/src/error.rs:427
- PrecClimber::climb_rec (cognitive 27) pest/src/prec_climber.rs:313
- ParserState::rule (cognitive 25) pest/src/parser_state.rs:743
- CliArgs::default (cognitive 24) debugger/src/main.rs:236
- Cli::execute_command (cognitive 19) debugger/src/main.rs:133
- pest_debugger::main (cognitive 19) debugger/src/main.rs:345
- Position::skip_until (cognitive 17) pest/src/position.rs:300
- Vm::parse_rule (cognitive 16) vm/src/lib.rs:76
- REDACTED
- TooManyFunctions: pest::unicode pest/src/unicode/mod.rs:56
- TooManyMethods: ParserState pest/src/parser_state.rs:530
- ClassTooLong: ParserState pest/src/parser_state.rs:530
- REDACTED
- REDACTED
- Near-duplicate member pair (36 shared lines) meta/src/ast.rs:303
- Duplicated block (56–58 lines × 2) meta/src/ast.rs:122
- Duplicated block (31–33 lines × 2) meta/src/optimizer/mod.rs:183
- Duplicated block (30 lines × 2) generator/src/generator.rs:430
- Duplicated block (12–14 lines × 2) debugger/src/main.rs:59
- Duplicated block (11–13 lines × 2) generator/src/generator.rs:530
- Duplicated block (12 lines × 2) meta/src/validator.rs:392
- Duplicated block (11–12 lines × 2) pest/src/error.rs:638
- Duplicated block (10 lines × 2) meta/src/ast.rs:449
- Duplicated block (8 lines × 4) meta/src/ast.rs:331
- Duplicated block (5 lines × 2) meta/src/ast.rs:314
- Duplicated block (8 lines × 2) pest/src/iterators/pair.rs:295
- Duplicated block (7 lines × 2) pest/src/iterators/pair.rs:304
- Coverage collected but not gated
- No structured logging
- No deployment automation
Minor — 24 finding(s)
- Orphaned file pest/src/iterators/pair.rs:1
- Orphaned file pest/src/prec_climber.rs:1
- Orphaned file pest/src/unicode/mod.rs:1
- Orphaned file pest/src/iterators/flat_pairs.rs:1
- Orphaned file generator/src/lib.rs:1
- Orphaned file generator/src/parse_derive.rs:1
- Orphaned file meta/src/optimizer/restorer.rs:1
- Orphaned file pest/src/iterators/tokens.rs:1
- Orphaned file meta/src/optimizer/skipper.rs:1
- Orphaned file pest/src/iterators/line_index.rs:1
- Orphaned file meta/src/optimizer/unroller.rs:1
- Off-boarding risk: anonymized user #1
- Further sole-owners (lower concentration)
- No ADRs found
- Orphaned files with no living knowledge
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- Large public API surface
- No changelog
- Duplicated predicate generator/src/generator.rs:316
Minor — 3 finding(s)
- Outdated: pest_generator
- Outdated: serde_json
- Outdated: syn
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-8b055cfda68a422aa47667d8e9ffcd0b/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-8b055cfda68a422aa47667d8e9ffcd0b/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 25 | 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 . | 0 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | 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 |