Executive summary
dandavison/delta falls short of our standard for a preview release because we found no logging, tracing or health checks in the code. It scores 63 out of 100 and is rated Adequate, and 41 of its 42 critical findings are security problems.
Production Readiness, at 52, is the weakest lens and counts most in the score. The best first step for the work it takes is fixing the package under a licence on your banned list, worth about 5 points. Adding a diagnostic log would lift Production Readiness itself, worth about 7 points. Raising Production Readiness to 62 would lift the score to about 67.
Twenty-eight pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Six secrets can leak from the build pipeline, and four settings leave the servers or containers unsafe. Pinning each tool to an exact version, limiting each secret to its own step and correcting the unsafe settings would close these risks. Passing outside input through environment variables would fix the two pipeline steps that put outside input straight into a shell command, and setting a waiting period for automatic updates would deal with the automatic dependency update that takes a new release at once. The package under a licence on your banned list needs replacing, or clearing with your legal team.
The product code is 26,756 lines, about €39,000 to rebuild.
If Production Readiness rose from 52 to 62, the lowest score rated Strong, the score would rise from 63 to about 67.
New since the last survey: 25 findings
- Cyclomatic Complexity · git_delta::options::set::set_options (cyclomatic 19) src/options/set.rs
- Cognitive Complexity · git_delta::options::set::gather_features_recursively (cognitive 25) src/options/set.rs
- God Classes · FileTooLong: options/set.rs src/options/set.rs
- Code Duplication · Edited copy of a member (30 corresponding lines) src/parse_style.rs
- Code Duplication · Edited copy of a member (23 corresponding lines) src/handlers/diff_header.rs
- Code Duplication · Edited copy of a member (10 corresponding lines) src/handlers/merge_conflict.rs
- Code Coverage · Low coverage: src/colors.rs src/colors.rs
- Code Coverage · Low coverage: src/features/navigate.rs src/features/navigate.rs
- Code Coverage · Low coverage: src/handlers/diff_stat.rs src/handlers/diff_stat.rs
- Code Coverage · Low coverage: src/handlers/git_show_file.rs src/handlers/git_show_file.rs
- Code Coverage · Low coverage: src/main.rs src/main.rs
- Code Coverage · Low coverage: src/subcommands/generate_completion.rs src/subcommands/generate_completion.rs
- Code Coverage · Low coverage: src/subcommands/parse_ansi.rs src/subcommands/parse_ansi.rs
- Code Coverage · Low coverage: src/subcommands/show_colors.rs src/subcommands/show_colors.rs
- Code Coverage · Low coverage: src/subcommands/show_syntax_themes.rs src/subcommands/show_syntax_themes.rs
- Code Coverage · Low coverage: src/subcommands/show_themes.rs src/subcommands/show_themes.rs
- Code Coverage · Low coverage: src/utils/bat/assets.rs src/utils/bat/assets.rs
- Code Coverage · Low coverage: src/utils/bat/output.rs src/utils/bat/output.rs
- Code Coverage · Low coverage: src/utils/bat/terminal.rs src/utils/bat/terminal.rs
- Code Coverage · Low coverage: src/utils/round_char_boundary.rs src/utils/round_char_boundary.rs
- Churn × Complexity Hotspots · Hotspot: src/options/set.rs src/options/set.rs
- Churn × Complexity Hotspots · Hotspot: src/config.rs src/config.rs
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
Fixed since the last survey: 5 findings
- Cyclomatic Complexity · git_delta::options::set::gather_features (cyclomatic 19) src/options/set.rs
- Cognitive Complexity · git_delta::options::set::gather_builtin_features_recursively (cognitive 20) src/options/set.rs
- Code Duplication · Duplicated block (20 lines × 2) src/parse_styles.rs
- Explicit Debt · TodoComment src/options/set.rs
- Knowledge Freshness · Orphaned knowledge src/utils/process.rs
Rebuild cost: about €39,000 · Estimate
| Cost to rebuild | €13,000 to €65,000, for 217 to 688 hours of work, about 0.3 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.9 at a score of 63. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Medium: 26,756 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: which parts of the code depend on which
| uses → | 1 align | 2 env | 3 format | 4 git_config.remote | 5 minusplus | 6 utils.tabs | 7 color | 8 edits | 9 features.diff_line_metadata | 10 handlers.blame | 11 options.get | 12 options.option_value | 13 utils.bat.output | 14 utils.syntect | 15 cli | 16 features.navigate | 17 features.side_by_side.ansifill | 18 options.theme | 19 subcommands.show_syntax_themes | 20 features.line_numbers | 21 paint | 22 handlers.diff_header | 23 handlers.grep | 24 handlers.hunk_header | 25 handlers.merge_conflict | 26 delta | 27 wrapping | 28 config | 29 features.hyperlinks | 30 features.side_by_side | 31 git_config | 32 handlers.hunk | 33 options.set | 34 parse_style | 35 style | 36 ansi | 37 ansi.iterator | 38 handlers.draw | 39 parse_styles | 40 subcommands.show_config |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 align | ||||||||||||||||||||||||||||||||||||||||
| 2 env | ||||||||||||||||||||||||||||||||||||||||
| 3 format | ||||||||||||||||||||||||||||||||||||||||
| 4 git_config.remote | ||||||||||||||||||||||||||||||||||||||||
| 5 minusplus | ||||||||||||||||||||||||||||||||||||||||
| 6 utils.tabs | ||||||||||||||||||||||||||||||||||||||||
| 7 color | 1 | |||||||||||||||||||||||||||||||||||||||
| 8 edits | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 9 features.diff_line_metadata | 1 | |||||||||||||||||||||||||||||||||||||||
| 10 handlers.blame | 1 | |||||||||||||||||||||||||||||||||||||||
| 11 options.get | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 12 options.option_value | 1 | |||||||||||||||||||||||||||||||||||||||
| 13 utils.bat.output | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 14 utils.syntect | 2 | |||||||||||||||||||||||||||||||||||||||
| 15 cli | 1 | 1 | 1 | 1 | 1 | 3 | ||||||||||||||||||||||||||||||||||
| 16 features.navigate | 1 | |||||||||||||||||||||||||||||||||||||||
| 17 features.side_by_side.ansifill | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 18 options.theme | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 19 subcommands.show_syntax_themes | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 20 features.line_numbers | 1 | 3 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 21 paint | 1 | 2 | 2 | 2 | 2 | 2 | ||||||||||||||||||||||||||||||||||
| 22 handlers.diff_header | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 23 handlers.grep | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 24 handlers.hunk_header | 2 | 4 | 2 | |||||||||||||||||||||||||||||||||||||
| 25 handlers.merge_conflict | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 26 delta | 1 | 1 | 1 | 2 | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||
| 27 wrapping | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 28 config | 1 | 1 | 1 | 1 | 1 | 4 | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||
| 29 features.hyperlinks | 1 | |||||||||||||||||||||||||||||||||||||||
| 30 features.side_by_side | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 31 git_config | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 32 handlers.hunk | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 33 options.set | 1 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 34 parse_style | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 35 style | 2 | 3 | 1 | |||||||||||||||||||||||||||||||||||||
| 36 ansi | 1 | |||||||||||||||||||||||||||||||||||||||
| 37 ansi.iterator | 1 | |||||||||||||||||||||||||||||||||||||||
| 38 handlers.draw | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 39 parse_styles | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 40 subcommands.show_config | 1 | 1 | 1 |
7→31 color uses git_config part of a loop✕
- Connections
- 1 pair of types, where a type in color uses a type in git_config.
- The types involved
git_delta.color.color$module→git_delta.git_config.GitConfig
- Direction
- color uses git_config, so a change to git_config can break color, while a change to color can't break git_config.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→1 edits uses align✕
- Connections
- 1 pair of types, where a type in edits uses a type in align.
- The types involved
git_delta.edits.edits$module→git_delta.align.Alignment
- Direction
- edits uses align, so a change to align can break edits, while a change to edits can't break align.
- Position
- Below the diagonal: edits uses a module listed above it, which is the healthy direction.
8→5 edits uses minusplus✕
- Connections
- 1 pair of types, where a type in edits uses a type in minusplus.
- The types involved
git_delta.edits.edits$module→git_delta.minusplus.MinusPlus
- Direction
- edits uses minusplus, so a change to minusplus can break edits, while a change to edits can't break minusplus.
- Position
- Below the diagonal: edits uses a module listed above it, which is the healthy direction.
9→26 features.diff_line_metadata uses delta part of a loop✕
- Connections
- 1 pair of types, where a type in features.diff_line_metadata uses a type in delta.
- The types involved
git_delta.features.diff_line_metadata.DiffLineMetadata→git_delta.delta.State
- Direction
- features.diff_line_metadata uses delta, so a change to delta can break features.diff_line_metadata, while a change to features.diff_line_metadata can't break delta.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→28 handlers.blame uses config part of a loop✕
- Connections
- 1 pair of types, where a type in handlers.blame uses a type in config.
- The types involved
git_delta.handlers.blame.blame$module→git_delta.config.Config
- Direction
- handlers.blame uses config, so a change to config can break handlers.blame, while a change to handlers.blame can't break config.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→15 options.get uses cli part of a loop✕
- Connections
- 2 pairs of types, where a type in options.get uses a type in cli.
- The types involved
git_delta.options.get.GetOptionValue→git_delta.cli.Optgit_delta.options.get.get$module→git_delta.cli.Opt
- Direction
- options.get uses cli, so a change to cli can break options.get, while a change to options.get can't break cli.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→31 options.get uses git_config part of a loop✕
- Connections
- 2 pairs of types, where a type in options.get uses a type in git_config.
- The types involved
git_delta.options.get.GetOptionValue→git_delta.git_config.GitConfiggit_delta.options.get.get$module→git_delta.git_config.GitConfig
- Direction
- options.get uses git_config, so a change to git_config can break options.get, while a change to options.get can't break git_config.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→15 options.option_value uses cli part of a loop✕
- Connections
- 1 pair of types, where a type in options.option_value uses a type in cli.
- The types involved
git_delta.options.option_value.OptionValue→git_delta.cli.SideBySide
- Direction
- options.option_value uses cli, so a change to cli can break options.option_value, while a change to options.option_value can't break cli.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→2 utils.bat.output uses env✕
- Connections
- 1 pair of types, where a type in utils.bat.output uses a type in env.
- The types involved
git_delta.utils.bat.output.OutputType→git_delta.env.DeltaEnv
- Direction
- utils.bat.output uses env, so a change to env can break utils.bat.output, while a change to utils.bat.output can't break env.
- Position
- Below the diagonal: utils.bat.output uses a module listed above it, which is the healthy direction.
13→28 utils.bat.output uses config part of a loop✕
- Connections
- 1 pair of types, where a type in utils.bat.output uses a type in config.
- The types involved
git_delta.utils.bat.output.PagerCfg→git_delta.config.Config
- Direction
- utils.bat.output uses config, so a change to config can break utils.bat.output, while a change to utils.bat.output can't break config.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→35 utils.syntect uses style part of a loop✕
- Connections
- 2 pairs of types, where a type in utils.syntect uses a type in style.
- The types involved
git_delta.utils.syntect.FromAnsiTermStyle→git_delta.style.Stylegit_delta.utils.syntect.FromDeltaStyle→git_delta.style.Style
- Direction
- utils.syntect uses style, so a change to style can break utils.syntect, while a change to utils.syntect can't break style.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→2 cli uses env✕
- Connections
- 1 pair of types, where a type in cli uses a type in env.
- The types involved
git_delta.cli.Opt→git_delta.env.DeltaEnv
- Direction
- cli uses env, so a change to env can break cli, while a change to cli can't break env.
- Position
- Below the diagonal: cli uses a module listed above it, which is the healthy direction.
15→7 cli uses color✕
- Connections
- 1 pair of types, where a type in cli uses a type in color.
- The types involved
git_delta.cli.ComputedValues→git_delta.color.ColorMode
- Direction
- cli uses color, so a change to color can break cli, while a change to cli can't break color.
- Position
- Below the diagonal: cli uses a module listed above it, which is the healthy direction.
15→11 cli uses options.get✕
- Connections
- 1 pair of types, where a type in cli uses a type in options.get.
- The types involved
git_delta.cli.SideBySide→git_delta.options.get.GetOptionValue
- Direction
- cli uses options.get, so a change to options.get can break cli, while a change to cli can't break options.get.
- Position
- Below the diagonal: cli uses a module listed above it, which is the healthy direction.
15→12 cli uses options.option_value✕
- Connections
- 1 pair of types, where a type in cli uses a type in options.option_value.
- The types involved
git_delta.cli.SideBySide→git_delta.options.option_value.OptionValue
- Direction
- cli uses options.option_value, so a change to options.option_value can break cli, while a change to cli can't break options.option_value.
- Position
- Below the diagonal: cli uses a module listed above it, which is the healthy direction.
15→13 cli uses utils.bat.output✕
- Connections
- 1 pair of types, where a type in cli uses a type in utils.bat.output.
- The types involved
git_delta.cli.ComputedValues→git_delta.utils.bat.output.PagingMode
- Direction
- cli uses utils.bat.output, so a change to utils.bat.output can break cli, while a change to cli can't break utils.bat.output.
- Position
- Below the diagonal: cli uses a module listed above it, which is the healthy direction.
15→31 cli uses git_config part of a loop✕
- Connections
- 3 pairs of types, where a type in cli uses a type in git_config.
- The types involved
git_delta.cli.Opt→git_delta.git_config.GitConfiggit_delta.cli.SideBySide→git_delta.git_config.GitConfiggit_delta.cli.SideBySide→git_delta.git_config.GitConfigGet
- Direction
- cli uses git_config, so a change to git_config can break cli, while a change to cli can't break git_config.
- 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→13 features.navigate uses utils.bat.output✕
- Connections
- 1 pair of types, where a type in features.navigate uses a type in utils.bat.output.
- The types involved
git_delta.features.navigate.navigate$module→git_delta.utils.bat.output.PagerCfg
- Direction
- features.navigate uses utils.bat.output, so a change to utils.bat.output can break features.navigate, while a change to features.navigate can't break utils.bat.output.
- Position
- Below the diagonal: features.navigate uses a module listed above it, which is the healthy direction.
17→15 features.side_by_side.ansifill uses cli✕
- Connections
- 1 pair of types, where a type in features.side_by_side.ansifill uses a type in cli.
- The types involved
git_delta.features.side_by_side.ansifill.UseFullPanelWidth→git_delta.cli.Width
- Direction
- features.side_by_side.ansifill uses cli, so a change to cli can break features.side_by_side.ansifill, while a change to features.side_by_side.ansifill can't break cli.
- Position
- Below the diagonal: features.side_by_side.ansifill uses a module listed above it, which is the healthy direction.
17→21 features.side_by_side.ansifill uses paint part of a loop✕
- Connections
- 1 pair of types, where a type in features.side_by_side.ansifill uses a type in paint.
- The types involved
git_delta.features.side_by_side.ansifill.UseFullPanelWidth→git_delta.paint.BgFillMethod
- Direction
- features.side_by_side.ansifill uses paint, so a change to paint can break features.side_by_side.ansifill, while a change to features.side_by_side.ansifill can't break paint.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→28 features.side_by_side.ansifill uses config part of a loop✕
- Connections
- 1 pair of types, where a type in features.side_by_side.ansifill uses a type in config.
- The types involved
git_delta.features.side_by_side.ansifill.UseFullPanelWidth→git_delta.config.Config
- Direction
- features.side_by_side.ansifill uses config, so a change to config can break features.side_by_side.ansifill, while a change to features.side_by_side.ansifill can't break config.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→7 options.theme uses color✕
- Connections
- 1 pair of types, where a type in options.theme uses a type in color.
- The types involved
git_delta.options.theme.theme$module→git_delta.color.ColorMode
- Direction
- options.theme uses color, so a change to color can break options.theme, while a change to options.theme can't break color.
- Position
- Below the diagonal: options.theme uses a module listed above it, which is the healthy direction.
18→15 options.theme uses cli✕
- Connections
- 1 pair of types, where a type in options.theme uses a type in cli.
- The types involved
git_delta.options.theme.theme$module→git_delta.cli.Opt
- Direction
- options.theme uses cli, so a change to cli can break options.theme, while a change to options.theme can't break cli.
- Position
- Below the diagonal: options.theme uses a module listed above it, which is the healthy direction.
19→7 subcommands.show_syntax_themes uses color✕
- Connections
- 1 pair of types, where a type in subcommands.show_syntax_themes uses a type in color.
- The types involved
git_delta.subcommands.show_syntax_themes.show_syntax_themes$module→git_delta.color.ColorMode
- Direction
- subcommands.show_syntax_themes uses color, so a change to color can break subcommands.show_syntax_themes, while a change to subcommands.show_syntax_themes can't break color.
- Position
- Below the diagonal: subcommands.show_syntax_themes uses a module listed above it, which is the healthy direction.
19→15 subcommands.show_syntax_themes uses cli✕
- Connections
- 1 pair of types, where a type in subcommands.show_syntax_themes uses a type in cli.
- The types involved
git_delta.subcommands.show_syntax_themes.show_syntax_themes$module→git_delta.cli.Opt
- Direction
- subcommands.show_syntax_themes uses cli, so a change to cli can break subcommands.show_syntax_themes, while a change to subcommands.show_syntax_themes can't break cli.
- Position
- Below the diagonal: subcommands.show_syntax_themes uses a module listed above it, which is the healthy direction.
20→3 features.line_numbers uses format✕
- Connections
- 1 pair of types, where a type in features.line_numbers uses a type in format.
- The types involved
git_delta.features.line_numbers.line_numbers$module→git_delta.format.Align
- Direction
- features.line_numbers uses format, so a change to format can break features.line_numbers, while a change to features.line_numbers can't break format.
- Position
- Below the diagonal: features.line_numbers uses a module listed above it, which is the healthy direction.
20→5 features.line_numbers uses minusplus✕
- Connections
- 3 pairs of types, where a type in features.line_numbers uses a type in minusplus.
- The types involved
git_delta.features.line_numbers.LineNumbersData→git_delta.minusplus.MinusPlusgit_delta.features.line_numbers.line_numbers$module→git_delta.minusplus.MinusPlusgit_delta.features.line_numbers.line_numbers$module→git_delta.minusplus.MinusPlusIndex
- Direction
- features.line_numbers uses minusplus, so a change to minusplus can break features.line_numbers, while a change to features.line_numbers can't break minusplus.
- Position
- Below the diagonal: features.line_numbers uses a module listed above it, which is the healthy direction.
20→17 features.line_numbers uses features.side_by_side.ansifill✕
- Connections
- 1 pair of types, where a type in features.line_numbers uses a type in features.side_by_side.ansifill.
- The types involved
git_delta.features.line_numbers.LineNumbersData→git_delta.features.side_by_side.ansifill.UseFullPanelWidth
- Direction
- features.line_numbers uses features.side_by_side.ansifill, so a change to features.side_by_side.ansifill can break features.line_numbers, while a change to features.line_numbers can't break features.side_by_side.ansifill.
- Position
- Below the diagonal: features.line_numbers uses a module listed above it, which is the healthy direction.
20→26 features.line_numbers uses delta part of a loop✕
- Connections
- 1 pair of types, where a type in features.line_numbers uses a type in delta.
- The types involved
git_delta.features.line_numbers.line_numbers$module→git_delta.delta.State
- Direction
- features.line_numbers uses delta, so a change to delta can break features.line_numbers, while a change to features.line_numbers can't break delta.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→28 features.line_numbers uses config part of a loop✕
- Connections
- 1 pair of types, where a type in features.line_numbers uses a type in config.
- The types involved
git_delta.features.line_numbers.line_numbers$module→git_delta.config.Config
- Direction
- features.line_numbers uses config, so a change to config can break features.line_numbers, while a change to features.line_numbers can't break config.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
21→5 paint uses minusplus✕
- Connections
- 1 pair of types, where a type in paint uses a type in minusplus.
- The types involved
git_delta.paint.paint$module→git_delta.minusplus.MinusPlus
- Direction
- paint uses minusplus, so a change to minusplus can break paint, while a change to paint can't break minusplus.
- Position
- Below the diagonal: paint uses a module listed above it, which is the healthy direction.
21→9 paint uses features.diff_line_metadata✕
- Connections
- 2 pairs of types, where a type in paint uses a type in features.diff_line_metadata.
- The types involved
git_delta.paint.Painter→git_delta.features.diff_line_metadata.DiffLineMetadatagit_delta.paint.paint$module→git_delta.features.diff_line_metadata.DiffLineMetadata
- Direction
- paint uses features.diff_line_metadata, so a change to features.diff_line_metadata can break paint, while a change to paint can't break features.diff_line_metadata.
- Position
- Below the diagonal: paint uses a module listed above it, which is the healthy direction.
21→20 paint uses features.line_numbers✕
- Connections
- 2 pairs of types, where a type in paint uses a type in features.line_numbers.
- The types involved
git_delta.paint.Painter→git_delta.features.line_numbers.LineNumbersDatagit_delta.paint.paint$module→git_delta.features.line_numbers.LineNumbersData
- Direction
- paint uses features.line_numbers, so a change to features.line_numbers can break paint, while a change to paint can't break features.line_numbers.
- Position
- Below the diagonal: paint uses a module listed above it, which is the healthy direction.
21→26 paint uses delta part of a loop✕
- Connections
- 2 pairs of types, where a type in paint uses a type in delta.
- The types involved
git_delta.paint.Painter→git_delta.delta.Stategit_delta.paint.paint$module→git_delta.delta.State
- Direction
- paint uses delta, so a change to delta can break paint, while a change to paint can't break delta.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
21→28 paint uses config part of a loop✕
- Connections
- 2 pairs of types, where a type in paint uses a type in config.
- The types involved
git_delta.paint.Painter→git_delta.config.Configgit_delta.paint.paint$module→git_delta.config.Config
- Direction
- paint uses config, so a change to config can break paint, while a change to paint can't break config.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
21→35 paint uses style part of a loop✕
- Connections
- 2 pairs of types, where a type in paint uses a type in style.
- The types involved
git_delta.paint.Painter→git_delta.style.Stylegit_delta.paint.paint$module→git_delta.style.Style
- Direction
- paint uses style, so a change to style can break paint, while a change to paint can't break style.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
22→21 handlers.diff_header uses paint✕
- Connections
- 1 pair of types, where a type in handlers.diff_header uses a type in paint.
- The types involved
git_delta.handlers.diff_header.diff_header$module→git_delta.paint.Painter
- Direction
- handlers.diff_header uses paint, so a change to paint can break handlers.diff_header, while a change to handlers.diff_header can't break paint.
- Position
- Below the diagonal: handlers.diff_header uses a module listed above it, which is the healthy direction.
22→28 handlers.diff_header uses config part of a loop✕
- Connections
- 1 pair of types, where a type in handlers.diff_header uses a type in config.
- The types involved
git_delta.handlers.diff_header.diff_header$module→git_delta.config.Config
- Direction
- handlers.diff_header uses config, so a change to config can break handlers.diff_header, while a change to handlers.diff_header can't break config.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→6 handlers.grep uses utils.tabs✕
- Connections
- 1 pair of types, where a type in handlers.grep uses a type in utils.tabs.
- The types involved
git_delta.handlers.grep.GrepLine→git_delta.utils.tabs.TabCfg
- Direction
- handlers.grep uses utils.tabs, so a change to utils.tabs can break handlers.grep, while a change to handlers.grep can't break utils.tabs.
- Position
- Below the diagonal: handlers.grep uses a module listed above it, which is the healthy direction.
23→21 handlers.grep uses paint✕
- Connections
- 1 pair of types, where a type in handlers.grep uses a type in paint.
- The types involved
git_delta.handlers.grep.grep$module→git_delta.paint.StyleSectionSpecifier
- Direction
- handlers.grep uses paint, so a change to paint can break handlers.grep, while a change to handlers.grep can't break paint.
- Position
- Below the diagonal: handlers.grep uses a module listed above it, which is the healthy direction.
23→28 handlers.grep uses config part of a loop✕
- Connections
- 1 pair of types, where a type in handlers.grep uses a type in config.
- The types involved
git_delta.handlers.grep.GrepLine→git_delta.config.GrepType
- Direction
- handlers.grep uses config, so a change to config can break handlers.grep, while a change to handlers.grep can't break config.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→35 handlers.grep uses style part of a loop✕
- Connections
- 1 pair of types, where a type in handlers.grep uses a type in style.
- The types involved
git_delta.handlers.grep.grep$module→git_delta.style.Style
- Direction
- handlers.grep uses style, so a change to style can break handlers.grep, while a change to handlers.grep can't break style.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
24→21 handlers.hunk_header uses paint✕
- Connections
- 2 pairs of types, where a type in handlers.hunk_header uses a type in paint.
- The types involved
git_delta.handlers.hunk_header.hunk_header$module→git_delta.paint.Paintergit_delta.handlers.hunk_header.hunk_header$module→git_delta.paint.StyleSectionSpecifier
- Direction
- handlers.hunk_header uses paint, so a change to paint can break handlers.hunk_header, while a change to handlers.hunk_header can't break paint.
- Position
- Below the diagonal: handlers.hunk_header uses a module listed above it, which is the healthy direction.
24→28 handlers.hunk_header uses config part of a loop✕
- Connections
- 4 pairs of types, where a type in handlers.hunk_header uses a type in config.
- The types involved
git_delta.handlers.hunk_header.hunk_header$module→git_delta.config.Configgit_delta.handlers.hunk_header.hunk_header$module→git_delta.config.HunkHeaderIncludeCodeFragmentgit_delta.handlers.hunk_header.hunk_header$module→git_delta.config.HunkHeaderIncludeFilePathgit_delta.handlers.hunk_header.hunk_header$module→git_delta.config.HunkHeaderIncludeLineNumber
- Direction
- handlers.hunk_header uses config, so a change to config can break handlers.hunk_header, while a change to handlers.hunk_header can't break config.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
24→35 handlers.hunk_header uses style part of a loop✕
- Connections
- 2 pairs of types, where a type in handlers.hunk_header uses a type in style.
- The types involved
git_delta.handlers.hunk_header.hunk_header$module→git_delta.style.DecorationStylegit_delta.handlers.hunk_header.hunk_header$module→git_delta.style.Style
- Direction
- handlers.hunk_header uses style, so a change to style can break handlers.hunk_header, while a change to handlers.hunk_header can't break style.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
25→21 handlers.merge_conflict uses paint✕
- Connections
- 1 pair of types, where a type in handlers.merge_conflict uses a type in paint.
- The types involved
git_delta.handlers.merge_conflict.merge_conflict$module→git_delta.paint.Painter
- Direction
- handlers.merge_conflict uses paint, so a change to paint can break handlers.merge_conflict, while a change to handlers.merge_conflict can't break paint.
- Position
- Below the diagonal: handlers.merge_conflict uses a module listed above it, which is the healthy direction.
25→28 handlers.merge_conflict uses config part of a loop✕
- Connections
- 1 pair of types, where a type in handlers.merge_conflict uses a type in config.
- The types involved
git_delta.handlers.merge_conflict.merge_conflict$module→git_delta.config.Config
- Direction
- handlers.merge_conflict uses config, so a change to config can break handlers.merge_conflict, while a change to handlers.merge_conflict can't break config.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
25→35 handlers.merge_conflict uses style part of a loop✕
- Connections
- 1 pair of types, where a type in handlers.merge_conflict uses a type in style.
- The types involved
git_delta.handlers.merge_conflict.merge_conflict$module→git_delta.style.Style
- Direction
- handlers.merge_conflict uses style, so a change to style can break handlers.merge_conflict, while a change to handlers.merge_conflict can't break style.
- 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.
26→21 delta uses paint✕
- Connections
- 1 pair of types, where a type in delta uses a type in paint.
- The types involved
git_delta.delta.StateMachine→git_delta.paint.Painter
- Direction
- delta uses paint, so a change to paint can break delta, while a change to delta can't break paint.
- Position
- Below the diagonal: delta uses a module listed above it, which is the healthy direction.
26→22 delta uses handlers.diff_header✕
- Connections
- 1 pair of types, where a type in delta uses a type in handlers.diff_header.
- The types involved
git_delta.delta.StateMachine→git_delta.handlers.diff_header.FileEvent
- Direction
- delta uses handlers.diff_header, so a change to handlers.diff_header can break delta, while a change to delta can't break handlers.diff_header.
- Position
- Below the diagonal: delta uses a module listed above it, which is the healthy direction.
26→23 delta uses handlers.grep✕
- Connections
- 1 pair of types, where a type in delta uses a type in handlers.grep.
- The types involved
git_delta.delta.StateMachine→git_delta.handlers.grep.GrepLine
- Direction
- delta uses handlers.grep, so a change to handlers.grep can break delta, while a change to delta can't break handlers.grep.
- Position
- Below the diagonal: delta uses a module listed above it, which is the healthy direction.
26→24 delta uses handlers.hunk_header✕
- Connections
- 2 pairs of types, where a type in delta uses a type in handlers.hunk_header.
- The types involved
git_delta.delta.StateMachine→git_delta.handlers.hunk_header.AmbiguousDiffMinusCountergit_delta.delta.StateMachine→git_delta.handlers.hunk_header.ParsedHunkHeader
- Direction
- delta uses handlers.hunk_header, so a change to handlers.hunk_header can break delta, while a change to delta can't break handlers.hunk_header.
- Position
- Below the diagonal: delta uses a module listed above it, which is the healthy direction.
26→25 delta uses handlers.merge_conflict✕
- Connections
- 1 pair of types, where a type in delta uses a type in handlers.merge_conflict.
- The types involved
git_delta.delta.StateMachine→git_delta.handlers.merge_conflict.MergeConflictCommit
- Direction
- delta uses handlers.merge_conflict, so a change to handlers.merge_conflict can break delta, while a change to delta can't break handlers.merge_conflict.
- Position
- Below the diagonal: delta uses a module listed above it, which is the healthy direction.
26→28 delta uses config part of a loop✕
- Connections
- 2 pairs of types, where a type in delta uses a type in config.
- The types involved
git_delta.delta.StateMachine→git_delta.config.Configgit_delta.delta.delta$module→git_delta.config.Config
- Direction
- delta uses config, so a change to config can break delta, while a change to delta can't break config.
- 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.
26→35 delta uses style part of a loop✕
- Connections
- 1 pair of types, where a type in delta uses a type in style.
- The types involved
git_delta.delta.StateMachine→git_delta.style.Style
- Direction
- delta uses style, so a change to style can break delta, while a change to delta can't break style.
- 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.
27→5 wrapping uses minusplus✕
- Connections
- 1 pair of types, where a type in wrapping uses a type in minusplus.
- The types involved
git_delta.wrapping.wrapping$module→git_delta.minusplus.MinusPlus
- Direction
- wrapping uses minusplus, so a change to minusplus can break wrapping, while a change to wrapping can't break minusplus.
- Position
- Below the diagonal: wrapping uses a module listed above it, which is the healthy direction.
27→15 wrapping uses cli✕
- Connections
- 1 pair of types, where a type in wrapping uses a type in cli.
- The types involved
git_delta.wrapping.WrapConfig→git_delta.cli.Opt
- Direction
- wrapping uses cli, so a change to cli can break wrapping, while a change to wrapping can't break cli.
- Position
- Below the diagonal: wrapping uses a module listed above it, which is the healthy direction.
27→20 wrapping uses features.line_numbers✕
- Connections
- 1 pair of types, where a type in wrapping uses a type in features.line_numbers.
- The types involved
git_delta.wrapping.wrapping$module→git_delta.features.line_numbers.LineNumbersData
- Direction
- wrapping uses features.line_numbers, so a change to features.line_numbers can break wrapping, while a change to wrapping can't break features.line_numbers.
- Position
- Below the diagonal: wrapping uses a module listed above it, which is the healthy direction.
27→26 wrapping uses delta✕
- Connections
- 1 pair of types, where a type in wrapping uses a type in delta.
- The types involved
git_delta.wrapping.wrapping$module→git_delta.delta.State
- Direction
- wrapping uses delta, so a change to delta can break wrapping, while a change to wrapping can't break delta.
- Position
- Below the diagonal: wrapping uses a module listed above it, which is the healthy direction.
27→28 wrapping uses config part of a loop✕
- Connections
- 1 pair of types, where a type in wrapping uses a type in config.
- The types involved
git_delta.wrapping.wrapping$module→git_delta.config.Config
- Direction
- wrapping uses config, so a change to config can break wrapping, while a change to wrapping can't break config.
- 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.
27→35 wrapping uses style part of a loop✕
- Connections
- 1 pair of types, where a type in wrapping uses a type in style.
- The types involved
git_delta.wrapping.WrapConfig→git_delta.style.Style
- Direction
- wrapping uses style, so a change to style can break wrapping, while a change to wrapping can't break style.
- 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.
28→5 config uses minusplus✕
- Connections
- 1 pair of types, where a type in config uses a type in minusplus.
- The types involved
git_delta.config.Config→git_delta.minusplus.MinusPlus
- Direction
- config uses minusplus, so a change to minusplus can break config, while a change to config can't break minusplus.
- Position
- Below the diagonal: config uses a module listed above it, which is the healthy direction.
28→6 config uses utils.tabs✕
- Connections
- 1 pair of types, where a type in config uses a type in utils.tabs.
- The types involved
git_delta.config.Config→git_delta.utils.tabs.TabCfg
- Direction
- config uses utils.tabs, so a change to utils.tabs can break config, while a change to config can't break utils.tabs.
- Position
- Below the diagonal: config uses a module listed above it, which is the healthy direction.
28→7 config uses color✕
- Connections
- 1 pair of types, where a type in config uses a type in color.
- The types involved
git_delta.config.config$module→git_delta.color.ColorMode
- Direction
- config uses color, so a change to color can break config, while a change to config can't break color.
- Position
- Below the diagonal: config uses a module listed above it, which is the healthy direction.
28→10 config uses handlers.blame✕
- Connections
- 1 pair of types, where a type in config uses a type in handlers.blame.
- The types involved
git_delta.config.Config→git_delta.handlers.blame.BlameLineNumbers
- Direction
- config uses handlers.blame, so a change to handlers.blame can break config, while a change to config can't break handlers.blame.
- Position
- Below the diagonal: config uses a module listed above it, which is the healthy direction.
28→13 config uses utils.bat.output✕
- Connections
- 1 pair of types, where a type in config uses a type in utils.bat.output.
- The types involved
git_delta.config.Config→git_delta.utils.bat.output.PagingMode
- Direction
- config uses utils.bat.output, so a change to utils.bat.output can break config, while a change to config can't break utils.bat.output.
- Position
- Below the diagonal: config uses a module listed above it, which is the healthy direction.
28→15 config uses cli✕
- Connections
- 4 pairs of types, where a type in config uses a type in cli.
- The types involved
git_delta.config.Config→git_delta.cli.InspectRawLinesgit_delta.config.Config→git_delta.cli.Optgit_delta.config.Config→git_delta.cli.SideBySideScopegit_delta.config.Config→git_delta.cli.Width
- Direction
- config uses cli, so a change to cli can break config, while a change to config can't break cli.
- Position
- Below the diagonal: config uses a module listed above it, which is the healthy direction.
28→21 config uses paint✕
- Connections
- 1 pair of types, where a type in config uses a type in paint.
- The types involved
git_delta.config.Config→git_delta.paint.BgFillMethod
- Direction
- config uses paint, so a change to paint can break config, while a change to config can't break paint.
- Position
- Below the diagonal: config uses a module listed above it, which is the healthy direction.
28→26 config uses delta✕
- Connections
- 1 pair of types, where a type in config uses a type in delta.
- The types involved
git_delta.config.Config→git_delta.delta.State
- Direction
- config uses delta, so a change to delta can break config, while a change to config can't break delta.
- Position
- Below the diagonal: config uses a module listed above it, which is the healthy direction.
28→27 config uses wrapping✕
- Connections
- 1 pair of types, where a type in config uses a type in wrapping.
- The types involved
git_delta.config.Config→git_delta.wrapping.WrapConfig
- Direction
- config uses wrapping, so a change to wrapping can break config, while a change to config can't break wrapping.
- Position
- Below the diagonal: config uses a module listed above it, which is the healthy direction.
28→31 config uses git_config part of a loop✕
- Connections
- 1 pair of types, where a type in config uses a type in git_config.
- The types involved
git_delta.config.Config→git_delta.git_config.GitConfig
- Direction
- config uses git_config, so a change to git_config can break config, while a change to config can't break git_config.
- 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.
28→35 config uses style part of a loop✕
- Connections
- 1 pair of types, where a type in config uses a type in style.
- The types involved
git_delta.config.Config→git_delta.style.Style
- Direction
- config uses style, so a change to style can break config, while a change to config can't break style.
- 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→28 features.hyperlinks uses config✕
- Connections
- 1 pair of types, where a type in features.hyperlinks uses a type in config.
- The types involved
git_delta.features.hyperlinks.hyperlinks$module→git_delta.config.Config
- Direction
- features.hyperlinks uses config, so a change to config can break features.hyperlinks, while a change to features.hyperlinks can't break config.
- Position
- Below the diagonal: features.hyperlinks uses a module listed above it, which is the healthy direction.
30→9 features.side_by_side uses features.diff_line_metadata✕
- Connections
- 1 pair of types, where a type in features.side_by_side uses a type in features.diff_line_metadata.
- The types involved
git_delta.features.side_by_side.side_by_side$module→git_delta.features.diff_line_metadata.DiffLineMetadata
- Direction
- features.side_by_side uses features.diff_line_metadata, so a change to features.diff_line_metadata can break features.side_by_side, while a change to features.side_by_side can't break features.diff_line_metadata.
- Position
- Below the diagonal: features.side_by_side uses a module listed above it, which is the healthy direction.
30→20 features.side_by_side uses features.line_numbers✕
- Connections
- 1 pair of types, where a type in features.side_by_side uses a type in features.line_numbers.
- The types involved
git_delta.features.side_by_side.side_by_side$module→git_delta.features.line_numbers.LineNumbersData
- Direction
- features.side_by_side uses features.line_numbers, so a change to features.line_numbers can break features.side_by_side, while a change to features.side_by_side can't break features.line_numbers.
- Position
- Below the diagonal: features.side_by_side uses a module listed above it, which is the healthy direction.
30→21 features.side_by_side uses paint✕
- Connections
- 1 pair of types, where a type in features.side_by_side uses a type in paint.
- The types involved
git_delta.features.side_by_side.side_by_side$module→git_delta.paint.BgShouldFill
- Direction
- features.side_by_side uses paint, so a change to paint can break features.side_by_side, while a change to features.side_by_side can't break paint.
- Position
- Below the diagonal: features.side_by_side uses a module listed above it, which is the healthy direction.
30→26 features.side_by_side uses delta✕
- Connections
- 1 pair of types, where a type in features.side_by_side uses a type in delta.
- The types involved
git_delta.features.side_by_side.side_by_side$module→git_delta.delta.State
- Direction
- features.side_by_side uses delta, so a change to delta can break features.side_by_side, while a change to features.side_by_side can't break delta.
- Position
- Below the diagonal: features.side_by_side uses a module listed above it, which is the healthy direction.
30→28 features.side_by_side uses config✕
- Connections
- 1 pair of types, where a type in features.side_by_side uses a type in config.
- The types involved
git_delta.features.side_by_side.side_by_side$module→git_delta.config.Config
- Direction
- features.side_by_side uses config, so a change to config can break features.side_by_side, while a change to features.side_by_side can't break config.
- Position
- Below the diagonal: features.side_by_side uses a module listed above it, which is the healthy direction.
31→2 git_config uses env✕
- Connections
- 2 pairs of types, where a type in git_config uses a type in env.
- The types involved
git_delta.git_config.GitConfig→git_delta.env.DeltaEnvgit_delta.git_config.git_config$module→git_delta.env.DeltaEnv
- Direction
- git_config uses env, so a change to env can break git_config, while a change to git_config can't break env.
- Position
- Below the diagonal: git_config uses a module listed above it, which is the healthy direction.
31→4 git_config uses git_config.remote✕
- Connections
- 1 pair of types, where a type in git_config uses a type in git_config.remote.
- The types involved
git_delta.git_config.GitConfig→git_delta.git_config.remote.GitRemoteRepo
- Direction
- git_config uses git_config.remote, so a change to git_config.remote can break git_config, while a change to git_config can't break git_config.remote.
- Position
- Below the diagonal: git_config uses a module listed above it, which is the healthy direction.
31→28 git_config uses config✕
- Connections
- 1 pair of types, where a type in git_config uses a type in config.
- The types involved
git_delta.git_config.GitConfig→git_delta.config.Config
- Direction
- git_config uses config, so a change to config can break git_config, while a change to git_config can't break config.
- Position
- Below the diagonal: git_config uses a module listed above it, which is the healthy direction.
32→26 handlers.hunk uses delta✕
- Connections
- 1 pair of types, where a type in handlers.hunk uses a type in delta.
- The types involved
git_delta.handlers.hunk.hunk$module→git_delta.delta.State
- Direction
- handlers.hunk uses delta, so a change to delta can break handlers.hunk, while a change to handlers.hunk can't break delta.
- Position
- Below the diagonal: handlers.hunk uses a module listed above it, which is the healthy direction.
32→28 handlers.hunk uses config✕
- Connections
- 1 pair of types, where a type in handlers.hunk uses a type in config.
- The types involved
git_delta.handlers.hunk.hunk$module→git_delta.config.Config
- Direction
- handlers.hunk uses config, so a change to config can break handlers.hunk, while a change to handlers.hunk can't break config.
- Position
- Below the diagonal: handlers.hunk uses a module listed above it, which is the healthy direction.
33→2 options.set uses env✕
- Connections
- 1 pair of types, where a type in options.set uses a type in env.
- The types involved
git_delta.options.set.set$module→git_delta.env.DeltaEnv
- Direction
- options.set uses env, so a change to env can break options.set, while a change to options.set can't break env.
- Position
- Below the diagonal: options.set uses a module listed above it, which is the healthy direction.
33→13 options.set uses utils.bat.output✕
- Connections
- 1 pair of types, where a type in options.set uses a type in utils.bat.output.
- The types involved
git_delta.options.set.set$module→git_delta.utils.bat.output.PagingMode
- Direction
- options.set uses utils.bat.output, so a change to utils.bat.output can break options.set, while a change to options.set can't break utils.bat.output.
- Position
- Below the diagonal: options.set uses a module listed above it, which is the healthy direction.
33→15 options.set uses cli✕
- Connections
- 2 pairs of types, where a type in options.set uses a type in cli.
- The types involved
git_delta.options.set.set$module→git_delta.cli.Optgit_delta.options.set.set$module→git_delta.cli.SideBySide
- Direction
- options.set uses cli, so a change to cli can break options.set, while a change to options.set can't break cli.
- Position
- Below the diagonal: options.set uses a module listed above it, which is the healthy direction.
33→31 options.set uses git_config✕
- Connections
- 1 pair of types, where a type in options.set uses a type in git_config.
- The types involved
git_delta.options.set.set$module→git_delta.git_config.GitConfig
- Direction
- options.set uses git_config, so a change to git_config can break options.set, while a change to options.set can't break git_config.
- Position
- Below the diagonal: options.set uses a module listed above it, which is the healthy direction.
34→31 parse_style uses git_config✕
- Connections
- 1 pair of types, where a type in parse_style uses a type in git_config.
- The types involved
git_delta.parse_style.parse_style$module→git_delta.git_config.GitConfig
- Direction
- parse_style uses git_config, so a change to git_config can break parse_style, while a change to parse_style can't break git_config.
- Position
- Below the diagonal: parse_style uses a module listed above it, which is the healthy direction.
34→35 parse_style uses style part of a loop✕
- Connections
- 1 pair of types, where a type in parse_style uses a type in style.
- The types involved
git_delta.parse_style.parse_style$module→git_delta.style.Style
- Direction
- parse_style uses style, so a change to style can break parse_style, while a change to parse_style can't break style.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
35→14 style uses utils.syntect✕
- Connections
- 2 pairs of types, where a type in style uses a type in utils.syntect.
- The types involved
git_delta.style.Style→git_delta.utils.syntect.FromAnsiTermStylegit_delta.style.Style→git_delta.utils.syntect.FromDeltaStyle
- Direction
- style uses utils.syntect, so a change to utils.syntect can break style, while a change to style can't break utils.syntect.
- Position
- Below the diagonal: style uses a module listed above it, which is the healthy direction.
35→31 style uses git_config✕
- Connections
- 3 pairs of types, where a type in style uses a type in git_config.
- The types involved
git_delta.style.DecorationStyle→git_delta.git_config.GitConfiggit_delta.style.Style→git_delta.git_config.GitConfiggit_delta.style.style$module→git_delta.git_config.GitConfig
- Direction
- style uses git_config, so a change to git_config can break style, while a change to style can't break git_config.
- Position
- Below the diagonal: style uses a module listed above it, which is the healthy direction.
35→34 style uses parse_style✕
- Connections
- 1 pair of types, where a type in style uses a type in parse_style.
- The types involved
git_delta.style.DecorationStyle→git_delta.parse_style.DecorationAttributes
- Direction
- style uses parse_style, so a change to parse_style can break style, while a change to style can't break parse_style.
- Position
- Below the diagonal: style uses a module listed above it, which is the healthy direction.
36→35 ansi uses style✕
- Connections
- 1 pair of types, where a type in ansi uses a type in style.
- The types involved
git_delta.ansi.ansi$module→git_delta.style.Style
- Direction
- ansi uses style, so a change to style can break ansi, while a change to ansi can't break style.
- Position
- Below the diagonal: ansi uses a module listed above it, which is the healthy direction.
37→35 ansi.iterator uses style✕
- Connections
- 1 pair of types, where a type in ansi.iterator uses a type in style.
- The types involved
git_delta.ansi.iterator.iterator$module→git_delta.style.Style
- Direction
- ansi.iterator uses style, so a change to style can break ansi.iterator, while a change to ansi.iterator can't break style.
- Position
- Below the diagonal: ansi.iterator uses a module listed above it, which is the healthy direction.
38→15 handlers.draw uses cli✕
- Connections
- 1 pair of types, where a type in handlers.draw uses a type in cli.
- The types involved
git_delta.handlers.draw.draw$module→git_delta.cli.Width
- Direction
- handlers.draw uses cli, so a change to cli can break handlers.draw, while a change to handlers.draw can't break cli.
- Position
- Below the diagonal: handlers.draw uses a module listed above it, which is the healthy direction.
38→35 handlers.draw uses style✕
- Connections
- 2 pairs of types, where a type in handlers.draw uses a type in style.
- The types involved
git_delta.handlers.draw.draw$module→git_delta.style.DecorationStylegit_delta.handlers.draw.draw$module→git_delta.style.Style
- Direction
- handlers.draw uses style, so a change to style can break handlers.draw, while a change to handlers.draw can't break style.
- Position
- Below the diagonal: handlers.draw uses a module listed above it, which is the healthy direction.
39→15 parse_styles uses cli✕
- Connections
- 1 pair of types, where a type in parse_styles uses a type in cli.
- The types involved
git_delta.parse_styles.parse_styles$module→git_delta.cli.Opt
- Direction
- parse_styles uses cli, so a change to cli can break parse_styles, while a change to parse_styles can't break cli.
- Position
- Below the diagonal: parse_styles uses a module listed above it, which is the healthy direction.
39→31 parse_styles uses git_config✕
- Connections
- 1 pair of types, where a type in parse_styles uses a type in git_config.
- The types involved
git_delta.parse_styles.parse_styles$module→git_delta.git_config.GitConfig
- Direction
- parse_styles uses git_config, so a change to git_config can break parse_styles, while a change to parse_styles can't break git_config.
- Position
- Below the diagonal: parse_styles uses a module listed above it, which is the healthy direction.
39→35 parse_styles uses style✕
- Connections
- 1 pair of types, where a type in parse_styles uses a type in style.
- The types involved
git_delta.parse_styles.parse_styles$module→git_delta.style.Style
- Direction
- parse_styles uses style, so a change to style can break parse_styles, while a change to parse_styles can't break style.
- Position
- Below the diagonal: parse_styles uses a module listed above it, which is the healthy direction.
40→15 subcommands.show_config uses cli✕
- Connections
- 1 pair of types, where a type in subcommands.show_config uses a type in cli.
- The types involved
git_delta.subcommands.show_config.show_config$module→git_delta.cli.Opt
- Direction
- subcommands.show_config uses cli, so a change to cli can break subcommands.show_config, while a change to subcommands.show_config can't break cli.
- Position
- Below the diagonal: subcommands.show_config uses a module listed above it, which is the healthy direction.
40→28 subcommands.show_config uses config✕
- Connections
- 1 pair of types, where a type in subcommands.show_config uses a type in config.
- The types involved
git_delta.subcommands.show_config.show_config$module→git_delta.config.Config
- Direction
- subcommands.show_config uses config, so a change to config can break subcommands.show_config, while a change to subcommands.show_config can't break config.
- Position
- Below the diagonal: subcommands.show_config uses a module listed above it, which is the healthy direction.
40→35 subcommands.show_config uses style✕
- Connections
- 1 pair of types, where a type in subcommands.show_config uses a type in style.
- The types involved
git_delta.subcommands.show_config.show_config$module→git_delta.style.DecorationStyle
- Direction
- subcommands.show_config uses style, so a change to style can break subcommands.show_config, while a change to subcommands.show_config can't break style.
- Position
- Below the diagonal: subcommands.show_config 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 — Event Sourcing
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 39 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 29 | Medium |
| A02:2025 — Security Misconfiguration | 6 | High / Critical |
Roadmap
Top priorities: 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; Resolve the 1 Banned license finding(s) in License Compliance; Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Cargo.toml.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 Banned license finding(s) in License Compliance. | +4.6 pts | Low | License Compliance |
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Cargo.toml. | +4.0 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. | +6.8 pts | Medium | Observability |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +3.3 pts | Medium | Release Hygiene |
| 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. | +3.2 pts | Medium | Architecture documentation |
| Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED, REDACTED. | +0.9 pts | Low | Static Analysis (SAST) |
| Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose. | +1.4 pts | Medium | Web-Security Posture |
| Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). | +0.7 pts | Low | Static Analysis (SAST) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 1.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 1.6 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 2.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.4 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Dependency Vulnerabilities: Medium advisory (unmaintained): REDACTED |
| src/main.rs | 5.9 | Mixed | Cyclomatic Complexity: git_delta::run_app (cyclomatic 35) |
| src/wrapping.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/parse_style.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/options/set.rs | 6.0 | Mixed | Explicit Debt: HackComment |
| src/handlers/hunk.rs | 6.0 | Mixed | Explicit Debt: FixmeComment |
| src/utils/process.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/paint.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/edits.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/features/side_by_side.rs | 6.0 | Mixed | Explicit Debt: HackComment |
| src/delta.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/handlers/diff_header.rs | 6.0 | Mixed | Explicit Debt: FixmeComment |
| src/handlers/merge_conflict.rs | 6.0 | Mixed | 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
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 38 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 38 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, 188 of 215 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (157 contributor(s) across 2209 commit(s) sampled, automation and bot accounts excluded). One of them holds 80% of the history; the other 156 hold 0.1% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D26 Project Cohesion — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `(repository root)` (26752 LoC, 138 module-visible types across 9 directories) is over its size bounds, and whether one unit is a coherent whole or a grab-bag is read from its type references: the parts of it that reach the rest only through its shared core. Those are read over the C#/VB code model, which this unit's source did not supply. Its size alone is no verdict on its cohesion, so none is published.
- D27 Navigability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- D34 Knowledge Freshness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. File-level freshness contradicts repo activity: 30 commits in the last 90 days, yet 35 of 59 significant files carry no living knowledge. Those two readings cannot both be true, so the per-file recency signal is treated as unreliable here and freshness is not scored for this run.
- D44 Platform End-of-Life — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via Dockerfile (REDACTED). docker build failed (exit 1) — REDACTED:10 -------------------- 8 | RUN git clone https://github.com/dandavison/delta.git 9 | WORKDIR delta 10 | >>> RUN /root/.cargo/bin/cargo build --release 11 | 12 | ENV PATH="${PWD}/target/release:${PATH}" -------------------- ERROR: failed to solve: process "/bin/sh -c /root/.cargo/bin/cargo build --release" did not complete successfully: exit code: 127; runtime evidence skipped.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- 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.
- D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run 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.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- 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: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- 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
8 function(s) exceeded the cyclomatic complexity threshold of 15; the worst was git_delta::ansi::iterator::ansi_term_style_from_sgr_parameters at 53. A further 1 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 DecorationStyle::apply_special_decoration_attributes at 16 — they are counted neither in the figure above nor in this dimension's score.
What to do
- Bring the 2 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with git_delta::ansi::iterator::ansi_term_style_from_sgr_parameters (cyclomatic 53), git_delta::run_app (cyclomatic 35). — 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 2 together lifts Cyclomatic Complexity from 8.0 to about 8.6/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
D2 · Cognitive Complexity
24 function(s) exceeded the cognitive complexity threshold of 15; the worst was git_delta::wrapping::wrap_line at 52.
What to do
- Bring the 24 bodies over 15 down to 15 or less in Cognitive Complexity — start with git_delta::wrapping::wrap_line (cognitive 52), git_delta::run_app (cognitive 50), git_delta::utils::helpwrap::wrap (cognitive 50). — 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 24 together lifts Cognitive Complexity from 5.4 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
12 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 4 FunctionTooLong finding(s) in God Classes — start with set.rs, show_config.rs, main.rs. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 3 FileTooLong finding(s) in God Classes — start with cli.rs, set.rs, paint.rs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 TooManyFields finding(s) in God Classes — start with cli.rs, config.rs. — One of this dimension's main actionable groups (2 warning-level).
D4 · Code Duplication
4 duplicated block group(s) detected. 0.8 % of the production lines (214 of 26,756) are in a reported copy. A further 3 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
What to do
- Resolve the 1 Edited copy of a member (30 corresponding lines) finding(s) in Code Duplication — start with parse_style.rs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Edited copy of a member (23 corresponding lines) finding(s) in Code Duplication — start with diff_header.rs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Edited copy of a member (10 corresponding lines) finding(s) in Code Duplication — start with merge_conflict.rs. — One of this dimension's main actionable groups (1 warning-level).
D6 · Cohesion (LCOM4)
0 of 21 classes have LCOM4 above 3.
D8 · Code Coverage
Line coverage 84.2% — 14 file(s) below 50%. Measured from the Rust suite (repository root: `cargo test --workspace` instrumented over 73 production file(s), 1 test binaries and 0 doc-test binaries).
What to do
- Resolve the 14 Low coverage finding(s) in Code Coverage — start with colors.rs, navigate.rs, diff_stat.rs. — One of this dimension's main actionable groups (14 warning-level).
D11 · Test Reliability
0 flaky across 1 measured tier(s). Rust (repository root, 52 test files): measured (0 flaky).
D12 · Dependency Hygiene
15 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 REDACTED there.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
1 of 252 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository's REDACTED closed over its manifests' `[dependencies]` and `[build-dependencies]`. Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository. This repository publishes itself under MIT, which is its own choice and is not judged here.
What to do
- Resolve the 1 Banned license finding(s) in License Compliance. — One of this dimension's main actionable groups (1 issue-level).
D15 · Churn × Complexity Hotspots
Top hotspots: src/options/set.rs (9×19=171); src/config.rs (3×19=57)
What to do
- Resolve the 2 Hotspot finding(s) in Churn × Complexity Hotspots — start with set.rs, config.rs. — One of this dimension's main actionable groups (2 warning-level).
D17 · Explicit Debt
51 deducted task-comment markers across 26756 LoC (0.2/KLoC) → score 9.6. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 38 TodoComment finding(s) in Explicit Debt — start with merge_conflict.rs (8), paint.rs (4), wrapping.rs (3). — One of this dimension's main actionable groups (38 warning-level).
- Resolve the 9 HackComment finding(s) in Explicit Debt — start with set.rs (3), grep.rs (3), paint.rs. — One of this dimension's main actionable groups (9 warning-level).
- Resolve the 4 FixmeComment finding(s) in Explicit Debt — start with paint.rs (2), hunk.rs, diff_header.rs. — One of this dimension's main actionable groups (4 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 3 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Cargo.toml. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
39 finding(s): 0 critical, 37 high, 2 medium, 0 low. 28 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. Separately, one or more rules could not re-parse an embedded snippet in 3 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (4 issue-level).
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- No action in Static Analysis (SAST) — all 28 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (28 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
16 finding(s): 0 critical, 0 high, 16 medium, 0 low.
What to do
- Resolve the 6 Medium advisory (unsound) finding(s) in Dependency Vulnerabilities — start with REDACTED (6). — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 5 Medium advisory (unmaintained) finding(s) in Dependency Vulnerabilities — start with REDACTED (5). — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 3 Medium vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 warning-level).
D31 · IaC & Container Security
6 finding(s): 0 critical, 4 high, 2 medium, 0 low.
What to do
- Resolve the 4 High IaC finding(s) in IaC & Container Security — start with REDACTED (4). — One of this dimension's main actionable groups (4 issue-level).
- Resolve the 2 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-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 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX5 · Architecture & structure
AX9 · CQS / query purity
ES2 · Immutable events
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
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
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
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.
S1 · Web-Security Posture
- `https://cdn.jsdelivr.net/npm/vega@5.4.0/build/vega.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. 3 such include(s) across the repository's markup. — etc/performance/index.html:6
What to do
- Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose.
X21 · Side-effecting pattern guard
X30 · Support guard that admits what it rejects
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 87% | Strong | Solid. |
| Architecture | 99% | Exemplary | Solid. |
| Maturity | 65% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 52% | Adequate — gated by P2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 63% | Adequate — gated by D29, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Event Sourcing | 100% | Exemplary | Strongest area. |
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.
- X7 Silent fallback defaults — 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 — 76 check(s) not relevant to this codebase
- AC1 Text alternatives — Frontend below the scale floor (11 DOM element(s) < 25) — too little surface to assess accessibility.
- AC2 Forms & labels — Frontend below the scale floor (11 DOM element(s) < 25) — too little surface to assess accessibility.
- AC3 Page structure — Frontend below the scale floor (11 DOM element(s) < 25) — too little surface to assess accessibility.
- AC4 Keyboard semantics — Frontend below the scale floor (11 DOM element(s) < 25) — too little surface to assess accessibility.
- AC5 ARIA correctness — Frontend below the scale floor (11 DOM element(s) < 25) — too little surface to assess accessibility.
- AC6 Visual & motion safety — Frontend below the scale floor (11 DOM element(s) < 25) — too little surface to assess accessibility.
- AX1 Captive dependencies — Not applicable: this repository's Python imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one.
- AX2 Stateful singletons — 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.
- AX4 Dependency direction — not applicable to a vertical-slice architecture (the inward-dependency rule is for layered/clean styles)
- 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 — vertical-slice architecture detected, but individual slices could not be resolved from namespaces or project layout
- AX8 Test isolation — no test/production split to check
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — docker build failed (exit 1) — REDACTED:10 -------------------- 8 | RUN git clone https://github.com/dandavison/delta.git 9 | WORKDIR delta 10 | >>> RUN /root/.cargo/bin/cargo build --release 11 | 12 | ENV PATH="${PWD}/target/release:${PATH}" -------------------- ERROR: failed to solve: process "/bin/sh -c /root/.cargo/bin/cargo build --release" did not complete successfully: exit code: 127; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no data at rest for these controls to protect.
- C2 Access Controls — No access-control surface detected in the analyzed source — this repository starts no server another machine can reach (no actix-web HttpServer, axum::serve, Rocket launch, warp::serve, poem or salvo Server, tonic Server::builder, hyper or tiny_http server outside examples and tests, none bound beyond loopback). Access control is therefore N/A here — a crate is authorized by the application that serves it, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~4925 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.
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (1871 declarations, no unit with a dominant convention).
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .py, .rs, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D26 Project Cohesion — D26 could not read how the parts of this repository's one build unit reference each other, so its cohesion was not measured. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.rs), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D34 Knowledge Freshness — knowledge concentrated in recent work — freshness signal contradicted by repo activity
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- 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
- D5 Coupling — Not applicable — this Cargo build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
- 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
- DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 1 value object(s); 1 domain event(s); its domain events are published by services or handlers — no domain entity raises one
- 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 Fold determinism — not applicable — the code was read and holds no event-replay fold, so there is nothing for this check to judge
- 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 — coverage data present for 73 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `#[bench]`, criterion's `bench_function`/`bench_with_input`, `#[divan::bench]` or `#[library_benchmark]` in any `.rs` file, or criterion, divan, iai or a `[[bench]]` target in a Cargo.toml, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
- X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X12 Unreachable branch — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X13 Undrained process stream — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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.
- X27 Collection changed while being enumerated — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X3 Exception handling — not 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.
- 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 — 42 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
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Banned license: ansi_colours
- REDACTED
- REDACTED
- REDACTED
Serious — 149 finding(s)
- TodoComment src/align.rs:38
- TodoComment src/delta.rs:261
- TodoComment src/delta.rs:308
- TodoComment src/edits.rs:725
- TodoComment src/edits.rs:920
- TodoComment src/paint.rs:192
- TodoComment src/paint.rs:578
- TodoComment src/paint.rs:590
- TodoComment src/paint.rs:1041
- TodoComment src/parse_style.rs:59
- TodoComment src/style.rs:220
- TodoComment src/wrapping.rs:442
- TodoComment src/wrapping.rs:619
- TodoComment src/wrapping.rs:1171
- TodoComment src/utils/process.rs:202
- TodoComment src/utils/round_char_boundary.rs:2
- TodoComment src/utils/bat/terminal.rs:30
- TodoComment src/tests/test_example_diffs.rs:716
- TodoComment src/tests/test_example_diffs.rs:1818
- TodoComment src/options/set.rs:138
- TodoComment src/options/set.rs:1153
- TodoComment src/options/theme.rs:131
- TodoComment src/handlers/blame.rs:32
- TodoComment src/handlers/blame.rs:118
- TodoComment src/handlers/draw.rs:41
- git_delta::wrapping::wrap_line (cognitive 52) src/wrapping.rs:136
- git_delta::run_app (cognitive 50) src/main.rs:80
- git_delta::utils::helpwrap::wrap (cognitive 50) src/utils/helpwrap.rs:23
- git_delta::wrapping::wrap_minusplus_block (cognitive 36) src/wrapping.rs:381
- git_delta::parse_style::parse_ansi_term_style (cognitive 35) src/parse_style.rs:146
- git_delta::ansi::truncate_str_impl (cognitive 34) src/ansi/mod.rs:31
- git_delta::ansi::wrap_str (cognitive 33) src/ansi/mod.rs:118
- git_delta::options::set::set_options (cognitive 25) src/options/set.rs:69
- git_delta::options::set::gather_features_recursively (cognitive 25) src/options/set.rs:672
- git_delta::utils::bat::output::_make_process_from_less_path (cognitive 25) src/utils/bat/output.rs:174
- git_delta::ansi::iterator::ansi_term_style_from_sgr_parameters (cognitive 23) src/ansi/iterator.rs:173
- git_delta::options::set::gather_features (cognitive 22) src/options/set.rs:550
- git_delta::utils::process::calling_process_cmdline (cognitive 22) src/utils/process.rs:423
- git_delta::utils::bat::assets::list_languages (cognitive 21) src/utils/bat/assets.rs:17
- git_delta::edits::annotate (cognitive 20) src/edits.rs:174
- git_delta::paint::paint_file_path_with_line_number (cognitive 18) src/paint.rs:872
- git_delta::subcommands::external::extract (cognitive 18) src/subcommands/external.rs:75
- git_delta::subcommands::show_themes::show_themes (cognitive 18) src/subcommands/show_themes.rs:12
- git_delta::edits::infer_edits (cognitive 17) src/edits.rs:24
- git_delta::features::side_by_side::paint_minus_and_plus_lines_side_by_side (cognitive 17) src/features/side_by_side.rs:111
- git_delta::utils::process::describe_calling_process (cognitive 17) src/utils/process.rs:143
- Low coverage: src/colors.rs src/colors.rs:1
- Low coverage: src/features/navigate.rs src/features/navigate.rs:1
- Low coverage: src/handlers/diff_stat.rs src/handlers/diff_stat.rs:1
- Low coverage: src/handlers/git_show_file.rs src/handlers/git_show_file.rs:1
- Low coverage: src/main.rs src/main.rs:1
- Low coverage: src/subcommands/generate_completion.rs src/subcommands/generate_completion.rs:1
- Low coverage: src/subcommands/parse_ansi.rs src/subcommands/parse_ansi.rs:1
- Low coverage: src/subcommands/show_colors.rs src/subcommands/show_colors.rs:1
- Low coverage: src/subcommands/show_syntax_themes.rs src/subcommands/show_syntax_themes.rs:1
- Low coverage: src/subcommands/show_themes.rs src/subcommands/show_themes.rs:1
- Low coverage: src/utils/bat/assets.rs src/utils/bat/assets.rs:1
- Low coverage: src/utils/bat/output.rs src/utils/bat/output.rs:1
- Low coverage: src/utils/bat/terminal.rs src/utils/bat/terminal.rs:1
- Low coverage: src/utils/round_char_boundary.rs src/utils/round_char_boundary.rs:1
- HackComment src/paint.rs:399
- HackComment src/options/set.rs:122
- HackComment src/options/set.rs:207
- HackComment src/options/set.rs:234
- HackComment src/handlers/grep.rs:35
- HackComment src/handlers/grep.rs:204
- HackComment src/handlers/grep.rs:347
- HackComment src/handlers/hunk.rs:13
- HackComment src/features/side_by_side.rs:234
- git_delta::ansi::iterator::ansi_term_style_from_sgr_parameters (cyclomatic 53) src/ansi/iterator.rs:173
- git_delta::run_app (cyclomatic 35) src/main.rs:80
- git_delta::wrapping::wrap_line (cyclomatic 28) src/wrapping.rs:136
- git_delta::parse_style::parse_ansi_term_style (cyclomatic 26) src/parse_style.rs:146
- git_delta::options::set::set_options (cyclomatic 19) src/options/set.rs:69
- git_delta::handlers::hunk::new_line_state (cyclomatic 18) src/handlers/hunk.rs:156
- git_delta::wrapping::wrap_minusplus_block (cyclomatic 17) src/wrapping.rs:381
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- FixmeComment src/paint.rs:807
- FixmeComment src/paint.rs:809
- FixmeComment src/handlers/hunk.rs:319
- FixmeComment src/handlers/diff_header.rs:245
- FunctionTooLong: git_delta::options::set::set_options src/options/set.rs:69
- FunctionTooLong: git_delta::subcommands::show_config::write_config src/subcommands/show_config.rs:79
- FunctionTooLong: git_delta::run_app src/main.rs:80
- FunctionTooLong: git_delta::wrapping::wrap_minusplus_block src/wrapping.rs:381
- FileTooLong: src/cli.rs src/cli.rs
- FileTooLong: options/set.rs src/options/set.rs
- FileTooLong: src/paint.rs src/paint.rs
- REDACTED
- REDACTED
- REDACTED
- Hotspot: src/options/set.rs src/options/set.rs:69
- Hotspot: src/config.rs src/config.rs:192
- TooManyFields: Opt src/cli.rs:39
- TooManyFields: Config src/config.rs:39
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Config::from (cyclomatic 19) src/config.rs:192
- Opt::handle_help_and_version (cognitive 21) src/cli.rs:1344
- Config::from (cognitive 21) src/config.rs:192
- Painter::update_diff_style_sections (cognitive 21) src/paint.rs:550
- REDACTED
- REDACTED
- MethodTooLong: Config.from src/config.rs:192
- TooManyMethods: StateMachine src/delta.rs:93
- ClassTooLong: Opt src/cli.rs:39
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Edited copy of a member (30 corresponding lines) src/parse_style.rs:79
- Edited copy of a member (23 corresponding lines) src/handlers/diff_header.rs:321
- Edited copy of a member (10 corresponding lines) src/handlers/merge_conflict.rs:79
- Duplicated block (37 lines × 2) src/handlers/grep.rs:187
- Duplicated block (10 lines × 2) src/handlers/diff_header.rs:332
- Duplicated block (7–8 lines × 2) src/subcommands/show_syntax_themes.rs:99
- Duplicated block (7 lines × 2) src/parse_style.rs:99
- Coverage collected but not gated
- No structured logging
- Third-party script without Subresource Integrity etc/performance/index.html:6
Minor — 9 finding(s)
- No ADRs found Cargo.toml:13
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No changelog
- Silent fallback default on Err src/config.rs:202
Minor — 15 finding(s)
- Outdated: ansi_colours
- Outdated: anyhow
- Outdated: bitflags
- Outdated: chrono
- Outdated: clap
- Outdated: clap_complete
- Outdated: ctrlc
- Outdated: lazy_static
- Outdated: palette
- Outdated: pathdiff
- Outdated: regex
- Outdated: serde
- Outdated: serde_json
- Outdated: shell-words
- Outdated: unicode-segmentation
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-b22b3ab8b59246029ca2b26e5f41ac9a/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/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-b22b3ab8b59246029ca2b26e5f41ac9a/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude etc/ci --exclude etc/performance . | 39 | 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 . | 16 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 6 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | 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 |