Executive summary
sharkdp/bat falls short of our standard for a preview release because we found no recorded design decisions and no architecture document or diagram, and the documentation refers to four links that don't exist. It scores 54 out of 100 and is rated Adequate, and 25 of its 27 critical findings are security problems.
Maturity, at 40, is the weakest lens and counts most in the score. The best first step for the work it takes is having someone learn and document the nine files no active contributor knows, worth about 5 points. Recording design decisions would lift Maturity itself, worth about 10 points. Raising Maturity to 62 would lift the score to about 63.
Nineteen pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. One automatic update takes new releases before a bad one can be spotted, and one pipeline step installs packages that can change without warning. Pinning each tool to an exact version, setting a waiting period for automatic updates and pinning what the pipeline installs would close these risks. Correcting the flagged pipeline settings would fix the two weaknesses in the build pipeline's configuration, and limiting each secret to its own step would deal with the secret exposed to more of the pipeline than needed. The package under a licence on your banned list needs replacing, or clearing with your legal team.
The product code is 11,505 lines, about €17,000 to rebuild.
If Maturity rose from 40 to 62, the lowest score rated Strong, the score would rise from 54 to about 63.
New since the last survey: 4 findings
- Code Duplication · Edited copy of a member (46 corresponding lines) src/vscreen.rs
- Churn × Complexity Hotspots · Hotspot: src/printer.rs src/printer.rs
- Churn × Complexity Hotspots · Hotspot: src/bin/bat/main.rs src/bin/bat/main.rs
- Dependency Vulnerabilities · REDACTED
Fixed since the last survey: 1 finding
- Platform End-of-Life · End-of-life runtime: .NET net9.0 tests/syntax-tests/source/XML/console.csproj
Rebuild cost: about €17,000 · Estimate
| Cost to rebuild | €5,700 to €29,000, for 95 to 302 hours of work, about 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 54. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 11,505 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 assets.assets_metadata | 2 assets.build_assets.acknowledgements | 3 assets.lazy_theme_set | 4 assets.serialized_syntax_set | 5 assets.theme_preview | 6 bin.bat.assets | 7 bin.bat.clap_app | 8 bin.bat.config | 9 bin.bat.directories | 10 build | 11 build.application | 12 build.syntax_mapping | 13 build.util | 14 diff | 15 error | 16 input | 17 line_range | 18 nonprintable_notation | 19 pager | 20 paging | 21 style | 22 syntax_mapping.ignored_suffixes | 23 theme | 24 vscreen | 25 wrapping | 26 assets.build_assets | 27 bin.bat.input | 28 lessopen | 29 output | 30 preprocessor | 31 syntax_mapping | 32 syntax_mapping.builtin | 33 assets | 34 bin.bat.app | 35 config | 36 bin.bat.main | 37 controller | 38 pretty_printer | 39 printer | 40 decorations |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 assets.assets_metadata | ||||||||||||||||||||||||||||||||||||||||
| 2 assets.build_assets.acknowledgements | ||||||||||||||||||||||||||||||||||||||||
| 3 assets.lazy_theme_set | ||||||||||||||||||||||||||||||||||||||||
| 4 assets.serialized_syntax_set | ||||||||||||||||||||||||||||||||||||||||
| 5 assets.theme_preview | ||||||||||||||||||||||||||||||||||||||||
| 6 bin.bat.assets | ||||||||||||||||||||||||||||||||||||||||
| 7 bin.bat.clap_app | ||||||||||||||||||||||||||||||||||||||||
| 8 bin.bat.config | ||||||||||||||||||||||||||||||||||||||||
| 9 bin.bat.directories | ||||||||||||||||||||||||||||||||||||||||
| 10 build | ||||||||||||||||||||||||||||||||||||||||
| 11 build.application | ||||||||||||||||||||||||||||||||||||||||
| 12 build.syntax_mapping | ||||||||||||||||||||||||||||||||||||||||
| 13 build.util | ||||||||||||||||||||||||||||||||||||||||
| 14 diff | ||||||||||||||||||||||||||||||||||||||||
| 15 error | ||||||||||||||||||||||||||||||||||||||||
| 16 input | ||||||||||||||||||||||||||||||||||||||||
| 17 line_range | ||||||||||||||||||||||||||||||||||||||||
| 18 nonprintable_notation | ||||||||||||||||||||||||||||||||||||||||
| 19 pager | ||||||||||||||||||||||||||||||||||||||||
| 20 paging | ||||||||||||||||||||||||||||||||||||||||
| 21 style | ||||||||||||||||||||||||||||||||||||||||
| 22 syntax_mapping.ignored_suffixes | ||||||||||||||||||||||||||||||||||||||||
| 23 theme | ||||||||||||||||||||||||||||||||||||||||
| 24 vscreen | ||||||||||||||||||||||||||||||||||||||||
| 25 wrapping | ||||||||||||||||||||||||||||||||||||||||
| 26 assets.build_assets | 1 | |||||||||||||||||||||||||||||||||||||||
| 27 bin.bat.input | 1 | |||||||||||||||||||||||||||||||||||||||
| 28 lessopen | 1 | |||||||||||||||||||||||||||||||||||||||
| 29 output | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 30 preprocessor | 1 | |||||||||||||||||||||||||||||||||||||||
| 31 syntax_mapping | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 32 syntax_mapping.builtin | 1 | |||||||||||||||||||||||||||||||||||||||
| 33 assets | 2 | 1 | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 34 bin.bat.app | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 35 config | 1 | 2 | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 36 bin.bat.main | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 37 controller | 3 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 38 pretty_printer | 2 | 2 | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||
| 39 printer | 3 | 3 | 1 | 3 | 2 | 2 | ||||||||||||||||||||||||||||||||||
| 40 decorations | 7 |
26→3 assets.build_assets uses assets.lazy_theme_set✕
- Connections
- 1 pair of types, where a type in assets.build_assets uses a type in assets.lazy_theme_set.
- The types involved
bat.assets.build_assets.build_assets$module→bat.assets.lazy_theme_set.LazyThemeSet
- Direction
- assets.build_assets uses assets.lazy_theme_set, so a change to assets.lazy_theme_set can break assets.build_assets, while a change to assets.build_assets can't break assets.lazy_theme_set.
- Position
- Below the diagonal: assets.build_assets uses a module listed above it, which is the healthy direction.
27→16 bin.bat.input uses input✕
- Connections
- 1 pair of types, where a type in bin.bat.input uses a type in input.
- The types involved
bat.bin.bat.input.input$module→bat.input.Input
- Direction
- bin.bat.input uses input, so a change to input can break bin.bat.input, while a change to bin.bat.input can't break input.
- Position
- Below the diagonal: bin.bat.input uses a module listed above it, which is the healthy direction.
28→16 lessopen uses input✕
- Connections
- 1 pair of types, where a type in lessopen uses a type in input.
- The types involved
bat.lessopen.LessOpenPreprocessor→bat.input.Input
- Direction
- lessopen uses input, so a change to input can break lessopen, while a change to lessopen can't break input.
- Position
- Below the diagonal: lessopen uses a module listed above it, which is the healthy direction.
29→19 output uses pager✕
- Connections
- 1 pair of types, where a type in output uses a type in pager.
- The types involved
bat.output.BuiltinPager→bat.pager.Pager
- Direction
- output uses pager, so a change to pager can break output, while a change to output can't break pager.
- Position
- Below the diagonal: output uses a module listed above it, which is the healthy direction.
29→20 output uses paging✕
- Connections
- 1 pair of types, where a type in output uses a type in paging.
- The types involved
bat.output.OutputType→bat.paging.PagingMode
- Direction
- output uses paging, so a change to paging can break output, while a change to output can't break paging.
- Position
- Below the diagonal: output uses a module listed above it, which is the healthy direction.
29→25 output uses wrapping✕
- Connections
- 1 pair of types, where a type in output uses a type in wrapping.
- The types involved
bat.output.OutputType→bat.wrapping.WrappingMode
- Direction
- output uses wrapping, so a change to wrapping can break output, while a change to output can't break wrapping.
- Position
- Below the diagonal: output uses a module listed above it, which is the healthy direction.
30→18 preprocessor uses nonprintable_notation✕
- Connections
- 1 pair of types, where a type in preprocessor uses a type in nonprintable_notation.
- The types involved
bat.preprocessor.preprocessor$module→bat.nonprintable_notation.NonprintableNotation
- Direction
- preprocessor uses nonprintable_notation, so a change to nonprintable_notation can break preprocessor, while a change to preprocessor can't break nonprintable_notation.
- Position
- Below the diagonal: preprocessor uses a module listed above it, which is the healthy direction.
31→12 syntax_mapping uses build.syntax_mapping✕
- Connections
- 2 pairs of types, where a type in syntax_mapping uses a type in build.syntax_mapping.
- The types involved
bat.syntax_mapping.SyntaxMapping→bat.build.syntax_mapping.MappingTargetbat.syntax_mapping.syntax_mapping$module→bat.build.syntax_mapping.Case
- Direction
- syntax_mapping uses build.syntax_mapping, so a change to build.syntax_mapping can break syntax_mapping, while a change to syntax_mapping can't break build.syntax_mapping.
- Position
- Below the diagonal: syntax_mapping uses a module listed above it, which is the healthy direction.
31→22 syntax_mapping uses syntax_mapping.ignored_suffixes✕
- Connections
- 1 pair of types, where a type in syntax_mapping uses a type in syntax_mapping.ignored_suffixes.
- The types involved
bat.syntax_mapping.SyntaxMapping→bat.syntax_mapping.ignored_suffixes.IgnoredSuffixes
- Direction
- syntax_mapping uses syntax_mapping.ignored_suffixes, so a change to syntax_mapping.ignored_suffixes can break syntax_mapping, while a change to syntax_mapping can't break syntax_mapping.ignored_suffixes.
- Position
- Below the diagonal: syntax_mapping uses a module listed above it, which is the healthy direction.
32→12 syntax_mapping.builtin uses build.syntax_mapping✕
- Connections
- 1 pair of types, where a type in syntax_mapping.builtin uses a type in build.syntax_mapping.
- The types involved
bat.syntax_mapping.builtin.builtin$module→bat.build.syntax_mapping.Case
- Direction
- syntax_mapping.builtin uses build.syntax_mapping, so a change to build.syntax_mapping can break syntax_mapping.builtin, while a change to syntax_mapping.builtin can't break build.syntax_mapping.
- Position
- Below the diagonal: syntax_mapping.builtin uses a module listed above it, which is the healthy direction.
33→3 assets uses assets.lazy_theme_set✕
- Connections
- 2 pairs of types, where a type in assets uses a type in assets.lazy_theme_set.
- The types involved
bat.assets.HighlightingAssets→bat.assets.lazy_theme_set.LazyThemeSetbat.assets.assets$module→bat.assets.lazy_theme_set.LazyThemeSet
- Direction
- assets uses assets.lazy_theme_set, so a change to assets.lazy_theme_set can break assets, while a change to assets can't break assets.lazy_theme_set.
- Position
- Below the diagonal: assets uses a module listed above it, which is the healthy direction.
33→4 assets uses assets.serialized_syntax_set✕
- Connections
- 1 pair of types, where a type in assets uses a type in assets.serialized_syntax_set.
- The types involved
bat.assets.HighlightingAssets→bat.assets.serialized_syntax_set.SerializedSyntaxSet
- Direction
- assets uses assets.serialized_syntax_set, so a change to assets.serialized_syntax_set can break assets, while a change to assets can't break assets.serialized_syntax_set.
- Position
- Below the diagonal: assets uses a module listed above it, which is the healthy direction.
33→16 assets uses input✕
- Connections
- 2 pairs of types, where a type in assets uses a type in input.
- The types involved
bat.assets.HighlightingAssets→bat.input.InputReaderbat.assets.HighlightingAssets→bat.input.OpenedInput
- Direction
- assets uses input, so a change to input can break assets, while a change to assets can't break input.
- Position
- Below the diagonal: assets uses a module listed above it, which is the healthy direction.
33→22 assets uses syntax_mapping.ignored_suffixes✕
- Connections
- 1 pair of types, where a type in assets uses a type in syntax_mapping.ignored_suffixes.
- The types involved
bat.assets.HighlightingAssets→bat.syntax_mapping.ignored_suffixes.IgnoredSuffixes
- Direction
- assets uses syntax_mapping.ignored_suffixes, so a change to syntax_mapping.ignored_suffixes can break assets, while a change to assets can't break syntax_mapping.ignored_suffixes.
- Position
- Below the diagonal: assets uses a module listed above it, which is the healthy direction.
33→31 assets uses syntax_mapping✕
- Connections
- 1 pair of types, where a type in assets uses a type in syntax_mapping.
- The types involved
bat.assets.HighlightingAssets→bat.syntax_mapping.SyntaxMapping
- Direction
- assets uses syntax_mapping, so a change to syntax_mapping can break assets, while a change to assets can't break syntax_mapping.
- Position
- Below the diagonal: assets uses a module listed above it, which is the healthy direction.
34→21 bin.bat.app uses style✕
- Connections
- 1 pair of types, where a type in bin.bat.app uses a type in style.
- The types involved
bat.bin.bat.app.App→bat.style.StyleComponents
- Direction
- bin.bat.app uses style, so a change to style can break bin.bat.app, while a change to bin.bat.app can't break style.
- Position
- Below the diagonal: bin.bat.app uses a module listed above it, which is the healthy direction.
34→23 bin.bat.app uses theme✕
- Connections
- 1 pair of types, where a type in bin.bat.app uses a type in theme.
- The types involved
bat.bin.bat.app.App→bat.theme.ThemeOptions
- Direction
- bin.bat.app uses theme, so a change to theme can break bin.bat.app, while a change to bin.bat.app can't break theme.
- Position
- Below the diagonal: bin.bat.app uses a module listed above it, which is the healthy direction.
34→30 bin.bat.app uses preprocessor✕
- Connections
- 1 pair of types, where a type in bin.bat.app uses a type in preprocessor.
- The types involved
bat.bin.bat.app.app$module→bat.preprocessor.StripAnsiMode
- Direction
- bin.bat.app uses preprocessor, so a change to preprocessor can break bin.bat.app, while a change to bin.bat.app can't break preprocessor.
- Position
- Below the diagonal: bin.bat.app uses a module listed above it, which is the healthy direction.
35→17 config uses line_range✕
- Connections
- 1 pair of types, where a type in config uses a type in line_range.
- The types involved
bat.config.Config→bat.line_range.HighlightedLineRanges
- Direction
- config uses line_range, so a change to line_range can break config, while a change to config can't break line_range.
- Position
- Below the diagonal: config uses a module listed above it, which is the healthy direction.
35→18 config uses nonprintable_notation✕
- Connections
- 2 pairs of types, where a type in config uses a type in nonprintable_notation.
- The types involved
bat.config.Config→bat.nonprintable_notation.BinaryBehaviorbat.config.Config→bat.nonprintable_notation.NonprintableNotation
- Direction
- config uses nonprintable_notation, so a change to nonprintable_notation can break config, while a change to config can't break nonprintable_notation.
- Position
- Below the diagonal: config uses a module listed above it, which is the healthy direction.
35→20 config uses paging✕
- Connections
- 1 pair of types, where a type in config uses a type in paging.
- The types involved
bat.config.Config→bat.paging.PagingMode
- Direction
- config uses paging, so a change to paging can break config, while a change to config can't break paging.
- Position
- Below the diagonal: config uses a module listed above it, which is the healthy direction.
35→21 config uses style✕
- Connections
- 1 pair of types, where a type in config uses a type in style.
- The types involved
bat.config.Config→bat.style.StyleComponents
- Direction
- config uses style, so a change to style can break config, while a change to config can't break style.
- Position
- Below the diagonal: config uses a module listed above it, which is the healthy direction.
35→25 config uses wrapping✕
- Connections
- 1 pair of types, where a type in config uses a type in wrapping.
- The types involved
bat.config.Config→bat.wrapping.WrappingMode
- 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.
35→30 config uses preprocessor✕
- Connections
- 1 pair of types, where a type in config uses a type in preprocessor.
- The types involved
bat.config.Config→bat.preprocessor.StripAnsiMode
- Direction
- config uses preprocessor, so a change to preprocessor can break config, while a change to config can't break preprocessor.
- Position
- Below the diagonal: config uses a module listed above it, which is the healthy direction.
35→31 config uses syntax_mapping✕
- Connections
- 1 pair of types, where a type in config uses a type in syntax_mapping.
- The types involved
bat.config.Config→bat.syntax_mapping.SyntaxMapping
- Direction
- config uses syntax_mapping, so a change to syntax_mapping can break config, while a change to config can't break syntax_mapping.
- Position
- Below the diagonal: config uses a module listed above it, which is the healthy direction.
36→16 bin.bat.main uses input✕
- Connections
- 1 pair of types, where a type in bin.bat.main uses a type in input.
- The types involved
bat.bin.bat.main.main$module→bat.input.Input
- Direction
- bin.bat.main uses input, so a change to input can break bin.bat.main, while a change to bin.bat.main can't break input.
- Position
- Below the diagonal: bin.bat.main uses a module listed above it, which is the healthy direction.
36→23 bin.bat.main uses theme✕
- Connections
- 1 pair of types, where a type in bin.bat.main uses a type in theme.
- The types involved
bat.bin.bat.main.main$module→bat.theme.ThemeOptions
- Direction
- bin.bat.main uses theme, so a change to theme can break bin.bat.main, while a change to bin.bat.main can't break theme.
- Position
- Below the diagonal: bin.bat.main uses a module listed above it, which is the healthy direction.
36→34 bin.bat.main uses bin.bat.app✕
- Connections
- 1 pair of types, where a type in bin.bat.main uses a type in bin.bat.app.
- The types involved
bat.bin.bat.main.main$module→bat.bin.bat.app.App
- Direction
- bin.bat.main uses bin.bat.app, so a change to bin.bat.app can break bin.bat.main, while a change to bin.bat.main can't break bin.bat.app.
- Position
- Below the diagonal: bin.bat.main uses a module listed above it, which is the healthy direction.
36→35 bin.bat.main uses config✕
- Connections
- 1 pair of types, where a type in bin.bat.main uses a type in config.
- The types involved
bat.bin.bat.main.main$module→bat.config.Config
- Direction
- bin.bat.main uses config, so a change to config can break bin.bat.main, while a change to bin.bat.main can't break config.
- Position
- Below the diagonal: bin.bat.main uses a module listed above it, which is the healthy direction.
37→16 controller uses input✕
- Connections
- 3 pairs of types, where a type in controller uses a type in input.
- The types involved
bat.controller.Controller→bat.input.Inputbat.controller.Controller→bat.input.InputReaderbat.controller.Controller→bat.input.OpenedInput
- Direction
- controller uses input, so a change to input can break controller, while a change to controller can't break input.
- Position
- Below the diagonal: controller uses a module listed above it, which is the healthy direction.
37→17 controller uses line_range✕
- Connections
- 1 pair of types, where a type in controller uses a type in line_range.
- The types involved
bat.controller.Controller→bat.line_range.LineRanges
- Direction
- controller uses line_range, so a change to line_range can break controller, while a change to controller can't break line_range.
- Position
- Below the diagonal: controller uses a module listed above it, which is the healthy direction.
37→28 controller uses lessopen✕
- Connections
- 1 pair of types, where a type in controller uses a type in lessopen.
- The types involved
bat.controller.Controller→bat.lessopen.LessOpenPreprocessor
- Direction
- controller uses lessopen, so a change to lessopen can break controller, while a change to controller can't break lessopen.
- Position
- Below the diagonal: controller uses a module listed above it, which is the healthy direction.
37→29 controller uses output✕
- Connections
- 1 pair of types, where a type in controller uses a type in output.
- The types involved
bat.controller.Controller→bat.output.OutputHandle
- Direction
- controller uses output, so a change to output can break controller, while a change to controller can't break output.
- Position
- Below the diagonal: controller uses a module listed above it, which is the healthy direction.
37→33 controller uses assets✕
- Connections
- 1 pair of types, where a type in controller uses a type in assets.
- The types involved
bat.controller.Controller→bat.assets.HighlightingAssets
- Direction
- controller uses assets, so a change to assets can break controller, while a change to controller can't break assets.
- Position
- Below the diagonal: controller uses a module listed above it, which is the healthy direction.
37→35 controller uses config✕
- Connections
- 1 pair of types, where a type in controller uses a type in config.
- The types involved
bat.controller.Controller→bat.config.Config
- Direction
- controller uses config, so a change to config can break controller, while a change to controller can't break config.
- Position
- Below the diagonal: controller uses a module listed above it, which is the healthy direction.
38→16 pretty_printer uses input✕
- Connections
- 2 pairs of types, where a type in pretty_printer uses a type in input.
- The types involved
bat.pretty_printer.Input→bat.input.Inputbat.pretty_printer.PrettyPrinter→bat.input.Input
- Direction
- pretty_printer uses input, so a change to input can break pretty_printer, while a change to pretty_printer can't break input.
- Position
- Below the diagonal: pretty_printer uses a module listed above it, which is the healthy direction.
38→17 pretty_printer uses line_range✕
- Connections
- 2 pairs of types, where a type in pretty_printer uses a type in line_range.
- The types involved
bat.pretty_printer.PrettyPrinter→bat.line_range.LineRangebat.pretty_printer.PrettyPrinter→bat.line_range.LineRanges
- Direction
- pretty_printer uses line_range, so a change to line_range can break pretty_printer, while a change to pretty_printer can't break line_range.
- Position
- Below the diagonal: pretty_printer uses a module listed above it, which is the healthy direction.
38→20 pretty_printer uses paging✕
- Connections
- 1 pair of types, where a type in pretty_printer uses a type in paging.
- The types involved
bat.pretty_printer.PrettyPrinter→bat.paging.PagingMode
- Direction
- pretty_printer uses paging, so a change to paging can break pretty_printer, while a change to pretty_printer can't break paging.
- Position
- Below the diagonal: pretty_printer uses a module listed above it, which is the healthy direction.
38→25 pretty_printer uses wrapping✕
- Connections
- 1 pair of types, where a type in pretty_printer uses a type in wrapping.
- The types involved
bat.pretty_printer.PrettyPrinter→bat.wrapping.WrappingMode
- Direction
- pretty_printer uses wrapping, so a change to wrapping can break pretty_printer, while a change to pretty_printer can't break wrapping.
- Position
- Below the diagonal: pretty_printer uses a module listed above it, which is the healthy direction.
38→30 pretty_printer uses preprocessor✕
- Connections
- 1 pair of types, where a type in pretty_printer uses a type in preprocessor.
- The types involved
bat.pretty_printer.PrettyPrinter→bat.preprocessor.StripAnsiMode
- Direction
- pretty_printer uses preprocessor, so a change to preprocessor can break pretty_printer, while a change to pretty_printer can't break preprocessor.
- Position
- Below the diagonal: pretty_printer uses a module listed above it, which is the healthy direction.
38→31 pretty_printer uses syntax_mapping✕
- Connections
- 1 pair of types, where a type in pretty_printer uses a type in syntax_mapping.
- The types involved
bat.pretty_printer.PrettyPrinter→bat.syntax_mapping.SyntaxMapping
- Direction
- pretty_printer uses syntax_mapping, so a change to syntax_mapping can break pretty_printer, while a change to pretty_printer can't break syntax_mapping.
- Position
- Below the diagonal: pretty_printer uses a module listed above it, which is the healthy direction.
38→33 pretty_printer uses assets✕
- Connections
- 1 pair of types, where a type in pretty_printer uses a type in assets.
- The types involved
bat.pretty_printer.PrettyPrinter→bat.assets.HighlightingAssets
- Direction
- pretty_printer uses assets, so a change to assets can break pretty_printer, while a change to pretty_printer can't break assets.
- Position
- Below the diagonal: pretty_printer uses a module listed above it, which is the healthy direction.
38→35 pretty_printer uses config✕
- Connections
- 1 pair of types, where a type in pretty_printer uses a type in config.
- The types involved
bat.pretty_printer.PrettyPrinter→bat.config.Config
- Direction
- pretty_printer uses config, so a change to config can break pretty_printer, while a change to pretty_printer can't break config.
- Position
- Below the diagonal: pretty_printer uses a module listed above it, which is the healthy direction.
39→16 printer uses input✕
- Connections
- 3 pairs of types, where a type in printer uses a type in input.
- The types involved
bat.printer.InteractivePrinter→bat.input.OpenedInputbat.printer.Printer→bat.input.OpenedInputbat.printer.SimplePrinter→bat.input.OpenedInput
- Direction
- printer uses input, so a change to input can break printer, while a change to printer can't break input.
- Position
- Below the diagonal: printer uses a module listed above it, which is the healthy direction.
39→17 printer uses line_range✕
- Connections
- 3 pairs of types, where a type in printer uses a type in line_range.
- The types involved
bat.printer.InteractivePrinter→bat.line_range.MaxBufferedLineNumberbat.printer.Printer→bat.line_range.MaxBufferedLineNumberbat.printer.SimplePrinter→bat.line_range.MaxBufferedLineNumber
- Direction
- printer uses line_range, so a change to line_range can break printer, while a change to printer can't break line_range.
- Position
- Below the diagonal: printer uses a module listed above it, which is the healthy direction.
39→24 printer uses vscreen✕
- Connections
- 1 pair of types, where a type in printer uses a type in vscreen.
- The types involved
bat.printer.InteractivePrinter→bat.vscreen.AnsiStyle
- Direction
- printer uses vscreen, so a change to vscreen can break printer, while a change to printer can't break vscreen.
- Position
- Below the diagonal: printer uses a module listed above it, which is the healthy direction.
39→29 printer uses output✕
- Connections
- 3 pairs of types, where a type in printer uses a type in output.
- The types involved
bat.printer.InteractivePrinter→bat.output.OutputHandlebat.printer.Printer→bat.output.OutputHandlebat.printer.SimplePrinter→bat.output.OutputHandle
- Direction
- printer uses output, so a change to output can break printer, while a change to printer can't break output.
- Position
- Below the diagonal: printer uses a module listed above it, which is the healthy direction.
39→33 printer uses assets✕
- Connections
- 2 pairs of types, where a type in printer uses a type in assets.
- The types involved
bat.printer.HighlighterFromSet→bat.assets.SyntaxReferenceInSetbat.printer.InteractivePrinter→bat.assets.HighlightingAssets
- Direction
- printer uses assets, so a change to assets can break printer, while a change to printer can't break assets.
- Position
- Below the diagonal: printer uses a module listed above it, which is the healthy direction.
39→35 printer uses config✕
- Connections
- 2 pairs of types, where a type in printer uses a type in config.
- The types involved
bat.printer.InteractivePrinter→bat.config.Configbat.printer.SimplePrinter→bat.config.Config
- Direction
- printer uses config, so a change to config can break printer, while a change to printer can't break config.
- Position
- Below the diagonal: printer uses a module listed above it, which is the healthy direction.
40→39 decorations uses printer✕
- Connections
- 7 pairs of types, where a type in decorations uses a type in printer.
- The types involved
bat.decorations.Decoration→bat.printer.InteractivePrinterbat.decorations.GridBorderDecoration→bat.printer.Colorsbat.decorations.GridBorderDecoration→bat.printer.InteractivePrinterbat.decorations.LineChangesDecoration→bat.printer.Colorsbat.decorations.LineChangesDecoration→bat.printer.InteractivePrinterbat.decorations.LineNumberDecoration→bat.printer.Colorsbat.decorations.LineNumberDecoration→bat.printer.InteractivePrinter
- Direction
- decorations uses printer, so a change to printer can break decorations, while a change to decorations can't break printer.
- Position
- Below the diagonal: decorations 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
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 25 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 15 | Medium |
Roadmap
Top priorities: 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; Reconcile the README with reality: doc/README-ru.md links to `doc/alternatives.md`, but `doc/doc/alternatives.md` does not exist; doc/README-zh.md links to `doc/assets.md`, but `doc/doc/assets.md` does not exist; doc/README-zh.md links to `CONTRIBUTING.md`, but `doc/CONTRIBUTING.md` does not exist; doc/README-zh.md links to `doc/alternatives.md`, but `doc/doc/alternatives.md` does not exist; Resolve the 9 Orphaned file finding(s) in Knowledge Freshness — start with style.rs, output.rs, acknowledgements.rs.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 9 Orphaned file finding(s) in Knowledge Freshness — start with style.rs, output.rs, acknowledgements.rs. | +5.1 pts | Low | Knowledge Freshness |
| 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. | +9.7 pts | Medium | Architecture documentation |
| Reconcile the README with reality: doc/README-ru.md links to `doc/alternatives.md`, but `doc/doc/alternatives.md` does not exist; doc/README-zh.md links to `doc/assets.md`, but `doc/doc/assets.md` does not exist; doc/README-zh.md links to `CONTRIBUTING.md`, but `doc/CONTRIBUTING.md` does not exist; doc/README-zh.md links to `doc/alternatives.md`, but `doc/doc/alternatives.md` does not exist. | +7.9 pts | Medium | Documentation accuracy |
| Resolve the 1 Orphaned knowledge finding(s) in Knowledge Freshness — start with theme.rs. | +3.2 pts | Low | Knowledge Freshness |
| Resolve the 1 Banned license finding(s) in License Compliance. | +2.6 pts | Low | License Compliance |
| 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. | +4.6 pts | Medium | Observability |
| Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it. | +2.1 pts | Medium | Deployment & Rollback |
| Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. | +0.6 pts | Low | Bus Factor |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.2 | Mixed | Dependency Vulnerabilities: Medium advisory (unmaintained): REDACTED |
| REDACTED | 5.7 | Mixed | Static Analysis (SAST): High: REDACTED |
| src/printer.rs | 7.0 | Near-clean | Cyclomatic Complexity: InteractivePrinter::print_line (cyclomatic 46) |
| src/bin/bat/app.rs | 7.2 | Near-clean | Cyclomatic Complexity: App::config (cyclomatic 49) |
| src/controller.rs | 7.2 | Near-clean | Cyclomatic Complexity: Controller::print_file_ranges (cyclomatic 21) |
| REDACTED | 7.2 | Near-clean | Static Analysis (SAST): High: REDACTED |
| src/bin/bat/main.rs | 7.4 | Near-clean | Cyclomatic Complexity: bat::bin::bat::main::run (cyclomatic 16) |
| src/vscreen.rs | 7.4 | Near-clean | Code Duplication: Edited copy of a member (46 corresponding lines) |
| src/output.rs | 7.8 | Near-clean | Cyclomatic Complexity: OutputType::try_pager (cyclomatic 16) |
| src/bin/bat/clap_app.rs | 7.8 | Near-clean | God Classes: FunctionTooLong: bat::bin::bat::clap_app::build_app |
| src/assets.rs | 8.5 | Near-clean | Cognitive Complexity: HighlightingAssets::get_syntax (cognitive 22) |
| src/preprocessor.rs | 8.5 | Near-clean | Cognitive Complexity: bat::preprocessor::replace_nonprintable (cognitive 21) |
| src/line_range.rs | 8.5 | Near-clean | Cognitive Complexity: LineRange::parse_range (cognitive 19) |
| src/diff.rs | 8.5 | Near-clean | Cognitive Complexity: bat::diff::collect_changes_from_hunks (cognitive 17) |
| src/pretty_printer.rs | 8.5 | Near-clean | God Classes: TooManyMethods: PrettyPrinter |
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 39 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 — 39 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, 83 of 114 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
- 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.
- D21 Naming 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. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
- D21 Naming 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. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D27 Navigability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- D31 IaC & Container Security — 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. Tests/syntax-tests/highlighted/Dockerfile/Dockerfile carries no `FROM` instruction, so it declares no build stage and every Dockerfile rule this engine owns — the runtime-hardening, key-material, mutable-clone, no-op-shim, build-context, trust-anchor, install-guard, setuid and world-writable-path rules — is outside its own premise there and returned nothing. That silence is deliberate and correct: with no base image there is no image to reason about. It is reported here because it is NOT the same fact as a clean file, and coverage is stated as 4 of 5 Infrastructure-as-Code manifest(s) fully judged rather than as 100%. The vendor scanners (trivy, checkov) do read these files and their findings above stand; only this engine's own stage-keyed rules are absent. No owner action: a build file with no FROM is a legitimate include fragment.
- 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's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- AXB1 Runtime evidence locked — no reproducible boot — 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. Subject: a native UI project (tests/syntax-tests/source/XAML/ItemPage.xaml). The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. We then boot it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
- 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.
- M4 Documentation accuracy — 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. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- 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.
- 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.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- 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.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- M4 Documentation accuracy: 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 App::config at 49. 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 Attributes::update_with_sgr at 18 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold functions was excluded, so the exclusion is disclosed nowhere in the file itself: src/vscreen.rs (Attributes::update_with_sgr at 18). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 2 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with App::config (cyclomatic 49), InteractivePrinter::print_line (cyclomatic 46). — 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.1 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
14 function(s) exceeded the cognitive complexity threshold of 15; the worst was InteractivePrinter::print_line at 143.
What to do
- Bring the 2 bodies over 60 down to 60 or less in Cognitive Complexity — start with InteractivePrinter::print_line (cognitive 143), App::config (cognitive 66). — 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 Cognitive Complexity from 5.3 to about 6.7/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
D3 · God Classes
8 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 2 MethodTooLong finding(s) in God Classes — start with printer.rs, app.rs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 FileTooLong finding(s) in God Classes — start with clap_app.rs, printer.rs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 ClassTooLong finding(s) in God Classes — start with printer.rs, app.rs. — One of this dimension's main actionable groups (2 warning-level).
D4 · Code Duplication
2 duplicated block group(s) detected. 0.9 % of the production lines (100 of 11,505) are in a reported copy. One further row reports 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 (46 corresponding lines) finding(s) in Code Duplication — start with vscreen.rs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (13–14 lines × 2) finding(s) in Code Duplication — start with vscreen.rs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with vscreen.rs. — One of this dimension's main actionable groups (1 warning-level).
D6 · Cohesion (LCOM4)
0 of 25 classes have LCOM4 above 3.
D11 · Test Reliability
0 flaky across 1 measured tier(s). Rust (repository root, 25 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 298 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 OR Apache-2.0, 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/printer.rs (3×46=138); src/bin/bat/main.rs (3×16=48)
What to do
- Resolve the 2 Hotspot finding(s) in Churn × Complexity Hotspots — start with printer.rs, main.rs. — One of this dimension's main actionable groups (2 warning-level).
D16 · Bus Factor
2 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is src/diff.rs. Counted over 26 of the 32 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 11 document(s) read across 1 unit(s).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
25 finding(s): 0 critical, 25 high, 0 medium, 0 low. 19 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 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 19 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 (19 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
6 finding(s): 0 critical, 0 high, 5 medium, 0 low.
What to do
- Resolve the 3 Medium advisory (unmaintained) finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 Medium advisory (unsound) finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Medium advisory (unmaintained) finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D31 · IaC & Container Security
trivy and checkov found no infrastructure-as-code or container misconfigurations.
D34 · Knowledge Freshness
10 of 26 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/theme.rs. Counted over 26 of the 32 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 9 Orphaned file finding(s) in Knowledge Freshness — start with style.rs, output.rs, acknowledgements.rs. — One of this dimension's main actionable groups (9 recommendation-level).
- Resolve the 1 Orphaned knowledge finding(s) in Knowledge Freshness — start with theme.rs. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 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).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
D37 · Vulnerability-disclosure Policy
A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 3 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX9 · CQS / query purity
M1 · Documentation (README)
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
M4 · Documentation accuracy
- doc/README-ru.md links to `doc/alternatives.md`, but `doc/doc/alternatives.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — doc/README-ru.md:643
- doc/README-zh.md links to `doc/assets.md`, but `doc/doc/assets.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — doc/README-zh.md:451
- doc/README-zh.md links to `CONTRIBUTING.md`, but `doc/CONTRIBUTING.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — doc/README-zh.md:647
- doc/README-zh.md links to `doc/alternatives.md`, but `doc/doc/alternatives.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — doc/README-zh.md:669
What to do
- Reconcile the README with reality: doc/README-ru.md links to `doc/alternatives.md`, but `doc/doc/alternatives.md` does not exist; doc/README-zh.md links to `doc/assets.md`, but `doc/doc/assets.md` does not exist; doc/README-zh.md links to `CONTRIBUTING.md`, but `doc/CONTRIBUTING.md` does not exist; doc/README-zh.md links to `doc/alternatives.md`, but `doc/doc/alternatives.md` does not exist.
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
- No logging or diagnostics emission found. This repository ships a binary its users launch rather than a service you operate, so there is no operator to page — but when a run fails on a user's machine, neither they nor you have anything to read.
What to do
- Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.
P3 · Security & performance tooling
- `REDACTED` schedules updates, but no `package-ecosystem` entry covers `nuget`, `gomod`, `pip`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entries to the `updates:` list. — REDACTED:2
What to do
- Dependabot is configured but does not watch `nuget`, `gomod`, `pip` — add those `package-ecosystem` entries to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
What to do
- Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
P6 · Release Hygiene
X21 · Side-effecting pattern guard
X28 · Index access outside its own emptiness guard
X30 · Support guard that admits what it rejects
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 79% | Strong | Solid. |
| Architecture | 99% | Exemplary | Strongest area. |
| Maturity | 40% | Weak — gated by M2, M4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 56% | Adequate — gated by P2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 69% | Adequate — gated by D29, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
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 — 78 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one.
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Java code is a Spring, JSR-330 or CDI singleton bean. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. Dart isolates share no mutable memory, so no two requests write one object at the same instant. 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. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — AX6 reached only 0% of this repository's production lines — rust (11,505 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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 — ~5934 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.
- D17 Explicit Debt — the C# workspace loaded 0 projects, so explicit-debt density could not be measured
- D18 Solution Shape — D18 scores the shape of a .NET solution, but this repository's production source is mostly .rs — the .NET project files present are an immaterial minority — so the dimension does not apply.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — Naming consistency does not read html yet; not measured.
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed Rust surface was not measured.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ 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 .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 — This repository is one build unit, `(repository root)` (11505 LoC, 79 module-visible types across 7 directories), within the size bounds. Not scored: a single unit of this size gives project cohesion nothing to grade.
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.rs), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- 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
- D8 Code Coverage — Coverage NOT MEASURED: this repository did not build in our analyzer environment (a C#/MSBuild compiler error), so no coverage could be collected. It is excluded from the score rather than counted as a near-zero defect. We did not read WHERE the failing diagnostic is, so this does not claim the fault is in your test code — a repository written for an older SDK band can compile for you and not for us. Run `dotnet build` on this commit; if it succeeds, the gap is ours. Committing the Cobertura/OpenCover/lcov report your CI already produces also lets us measure real coverage without building anything.
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (5 value object(s))
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, which this analysis does not build from source alone for this language. Reported as guidance rather than measured
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- 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 not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- 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.
- S1 Web-Security Posture — No web surface: 44 Rust file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation and obsolete TLS versions, and none was found. This repository serves no HTTP of its own — no HTTP-server crate (actix-web, axum, Rocket, warp, poem, tide, salvo, tonic, a hyper server, …) among its Cargo manifests' run-time dependencies, and no server started in its production source — so HTTPS enforcement, HSTS, cookie flags and input validation are N/A here, as they are for a C# library or worker. If this codebase starts serving HTTP, the dimension reactivates automatically.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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
- 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.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 27 finding(s)
- 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
- REDACTED
- Orphaned knowledge src/theme.rs:1
Serious — 46 finding(s)
- bat::bin::bat::main::get_languages (cognitive 28) src/bin/bat/main.rs:100
- bat::preprocessor::replace_nonprintable (cognitive 21) src/preprocessor.rs:59
- bat::bin::bat::main::run (cognitive 17) src/bin/bat/main.rs:389
- bat::diff::collect_changes_from_hunks (cognitive 17) src/diff.rs:20
- InteractivePrinter::print_line (cyclomatic 46) src/printer.rs:656
- InteractivePrinter::new (cyclomatic 24) src/printer.rs:227
- InteractivePrinter::print_header (cyclomatic 21) src/printer.rs:489
- InteractivePrinter::print_line (cognitive 143) src/printer.rs:656
- InteractivePrinter::print_header (cognitive 21) src/printer.rs:489
- InteractivePrinter::new (cognitive 19) src/printer.rs:227
- REDACTED
- REDACTED
- REDACTED
- Controller::print_file_ranges (cyclomatic 21) src/controller.rs:254
- Controller::run_with_error_handler (cyclomatic 18) src/controller.rs:49
- Hotspot: src/printer.rs src/printer.rs:656
- Hotspot: src/bin/bat/main.rs src/bin/bat/main.rs:389
- Controller::print_file_ranges (cognitive 42) src/controller.rs:254
- Controller::run_with_error_handler (cognitive 30) src/controller.rs:49
- MethodTooLong: InteractivePrinter.print_line src/printer.rs:656
- MethodTooLong: App.config src/bin/bat/app.rs:271
- FileTooLong: bat/clap_app.rs src/bin/bat/clap_app.rs
- FileTooLong: src/printer.rs src/printer.rs
- ClassTooLong: InteractivePrinter src/printer.rs:209
- ClassTooLong: App src/bin/bat/app.rs:55
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- App::config (cyclomatic 49) src/bin/bat/app.rs:271
- OutputType::try_pager (cyclomatic 16) src/output.rs:93
- bat::bin::bat::main::run (cyclomatic 16) src/bin/bat/main.rs:389
- App::config (cognitive 66) src/bin/bat/app.rs:271
- LessOpenPreprocessor::open (cognitive 31) REDACTED:124
- OutputType::try_pager (cognitive 28) src/output.rs:93
- HighlightingAssets::get_syntax (cognitive 22) src/assets.rs:216
- LineRange::parse_range (cognitive 19) src/line_range.rs:40
- FunctionTooLong: bat::bin::bat::clap_app::build_app src/bin/bat/clap_app.rs:21
- TooManyMethods: PrettyPrinter src/pretty_printer.rs:38
- REDACTED
- REDACTED
- Edited copy of a member (46 corresponding lines) src/vscreen.rs:455
- Duplicated block (13–14 lines × 2) src/vscreen.rs:470
- Duplicated block (9 lines × 2) src/vscreen.rs:328
- Coverage not measured — test suite did not build
- No structured logging
Minor — 26 finding(s)
- Orphaned file src/style.rs:1
- Orphaned file src/output.rs:1
- Orphaned file src/assets/build_assets/acknowledgements.rs:1
- Orphaned file src/decorations.rs:1
- Orphaned file src/less.rs:1
- Orphaned file src/syntax_mapping/builtin.rs:1
- Orphaned file src/assets/lazy_theme_set.rs:1
- Orphaned file src/terminal.rs:1
- Orphaned file src/assets/assets_metadata.rs:1
- README/code drift doc/README-ru.md:643
- README/code drift doc/README-zh.md:451
- README/code drift doc/README-zh.md:647
- README/code drift doc/README-zh.md:669
- Off-boarding risk: anonymized user #1
- Further sole-owners (lower concentration)
- REDACTED
- Further orphaned files (smaller)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- Dependabot does not watch nuget/gomod/pip REDACTED:2
- No release approval gate
Minor — 15 finding(s)
- Outdated: anyhow
- Outdated: clap
- Outdated: console
- Outdated: encoding_rs
- Outdated: flate2
- Outdated: globset
- Outdated: indexmap
- Outdated: minus
- Outdated: plist
- Outdated: serde
- Outdated: serde_derive
- Outdated: serde_with
- Outdated: thiserror
- Outdated: toml
- Outdated: unicode-width
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-f8f0fe3dca4849a28aa277a8830f0aee/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-f8f0fe3dca4849a28aa277a8830f0aee/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 assets --exclude diagnostics --exclude tests/benchmarks --exclude tests/examples --exclude tests/snapshots --exclude tests/syntax-tests/highlighted --exclude tests/syntax-tests/source . | 25 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 6 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 0 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |