Executive summary
mfontanini/presenterm falls short of our standard for a preview release because we found no logging, tracing or health checks in the code. It scores 59 out of 100 and is rated Adequate, and 19 of its 21 critical findings are security problems in the build pipeline.
Production Readiness, at 51, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 5 points. Adding a diagnostic log would lift Production Readiness itself, also worth about 5. Raising Production Readiness to 62 would lift the score to about 63.
Seventeen pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Two secrets can leak from the build pipeline, and two sets of files in separate parts keep changing together, which points to hidden dependencies. Pinning each tool to an exact version, limiting each secret to its own step and making the hidden dependencies explicit would close these risks.
The product code is 22,847 lines, about €24,000 to rebuild.
If Production Readiness rose from 51 to 62, the lowest score rated Strong, the score would rise from 59 to about 63.
New since the last survey: 43 findings
- Cyclomatic Complexity · Presenter::present (cyclomatic 17) src/presenter.rs
- Cognitive Complexity · KittyPrinter::load_raw_resource (cognitive 18) src/terminal/image/protocols/kitty.rs
- Code Duplication · Edited copy of a member (21 corresponding lines) src/terminal/printer.rs
- Code Duplication · Edited copy of a member (27 corresponding lines) src/export/exporter.rs
- Code Duplication · Edited copy of a member (15 corresponding lines) src/presenter.rs
- Code Duplication · Edited copy of a member (23 corresponding lines) src/export/exporter.rs
- Code Duplication · Edited copy of a member (14 corresponding lines) src/markdown/parse.rs
- Code Duplication · Edited copy of a member (11 corresponding lines) src/theme/clean.rs
- Code Duplication · Edited copy of a member (11 corresponding lines) src/presentation/builder/snippet.rs
- Code Duplication · Edited copy of a member (8 corresponding lines) src/theme/clean.rs
- Code Duplication · Edited copy of a member (10 corresponding lines) src/presenter.rs
- Code Duplication · Edited copy of a member (6 corresponding lines) src/markdown/text.rs
- Code Duplication · Edited copy of a member (5 corresponding lines) src/markdown/text.rs
- Code Duplication · Edited copy of a member (5 corresponding lines) src/theme/clean.rs
- Code Duplication · Edited copy of a member (10 corresponding lines) src/render/properties.rs
- Code Duplication · Duplicated block (7 lines × 2) src/presenter.rs
- Code Coverage · Low coverage: src/commands/listener.rs src/commands/listener.rs
- Code Coverage · Low coverage: src/demo.rs src/demo.rs
- Code Coverage · Low coverage: src/export/exporter.rs src/export/exporter.rs
- Code Coverage · Low coverage: src/export/output.rs src/export/output.rs
- Code Coverage · Low coverage: src/main.rs src/main.rs
- Code Coverage · Low coverage: src/presentation/poller.rs src/presentation/poller.rs
- Code Coverage · Low coverage: src/presenter.rs src/presenter.rs
- Code Coverage · Low coverage: src/render/ascii_scaler.rs src/render/ascii_scaler.rs
- Code Coverage · Low coverage: src/render/mod.rs src/render/mod.rs
- Code Coverage · Low coverage: src/render/validate.rs src/render/validate.rs
- Code Coverage · Low coverage: src/terminal/capabilities.rs src/terminal/capabilities.rs
- Code Coverage · Low coverage: src/terminal/emulator.rs src/terminal/emulator.rs
- Code Coverage · Low coverage: src/terminal/image/mod.rs src/terminal/image/mod.rs
- Code Coverage · Low coverage: src/terminal/image/printer.rs src/terminal/image/printer.rs
- Code Coverage · Low coverage: src/terminal/image/protocols/ascii.rs src/terminal/image/protocols/ascii.rs
- Code Coverage · Low coverage: src/terminal/image/protocols/iterm.rs src/terminal/image/protocols/iterm.rs
- Code Coverage · Low coverage: src/terminal/image/protocols/kitty.rs src/terminal/image/protocols/kitty.rs
- Code Coverage · Low coverage: src/terminal/image/protocols/raw.rs src/terminal/image/protocols/raw.rs
- Code Coverage · Low coverage: src/terminal/image/protocols/sixel.rs src/terminal/image/protocols/sixel.rs
- Code Coverage · Low coverage: src/terminal/printer.rs src/terminal/printer.rs
- Code Coverage · Low coverage: src/third_party.rs src/third_party.rs
- Code Coverage · Low coverage: src/tools.rs src/tools.rs
- Code Coverage · Low coverage: src/ui/execution/acquire_terminal.rs src/ui/execution/acquire_terminal.rs
- Code Coverage · Low coverage: src/ui/execution/image.rs src/ui/execution/image.rs
- Code Coverage · Low coverage: src/ui/execution/pty.rs src/ui/execution/pty.rs
- Churn × Complexity Hotspots · Hotspot: src/presenter.rs src/presenter.rs
- Change Coupling · Boundary-crossing change coupling: engine.rs ↔ virt.rs src/render/engine.rs
Fixed since the last survey: 8 findings
- Code Duplication · Duplicated block (9–10 lines × 2) src/theme/clean.rs
- Code Duplication · Duplicated block (7 lines × 2) src/presenter.rs
- Churn × Complexity Hotspots · Hotspot: src/presentation/builder/comment.rs src/presentation/builder/comment.rs
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium advisory (unsound): RUSTSEC-2026-0097 REDACTED
- Dependency Vulnerabilities · Medium advisory (unsound): RUSTSEC-2026-0190 REDACTED
- Dependency Vulnerabilities · Medium vulnerability: RUSTSEC-2026-0194 REDACTED
- Dependency Vulnerabilities · Medium vulnerability: RUSTSEC-2026-0204 REDACTED
Rebuild cost: about €24,000 · Estimate
| Cost to rebuild | €8,100 to €40,000, for 134 to 426 hours of work, about 0.2 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 59. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Medium: 22,847 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 render.properties | 2 config | 3 presentation.builder.sources | 4 theme.raw | 5 commands.listener | 6 terminal.image.protocols.ascii | 7 terminal.image | 8 terminal.printer | 9 terminal.image.printer | 10 resource | 11 terminal.image.protocols.kitty | 12 theme.clean | 13 markdown.text_style | 14 markdown.elements | 15 terminal.virt | 16 code.highlighting | 17 markdown.parse | 18 markdown.text | 19 transitions | 20 ui.modals | 21 render.operation | 22 presentation | 23 presentation.builder.images | 24 third_party | 25 ui.execution.disabled | 26 ui.footer | 27 code.snippet | 28 export.output | 29 code.execute | 30 ui.execution.acquire_terminal | 31 ui.execution.image | 32 ui.execution.pty | 33 ui.execution.output | 34 presentation.builder | 35 export.exporter | 36 render.engine | 37 render | 38 render.ascii_scaler | 39 presenter | 40 presenterm |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 render.properties | ||||||||||||||||||||||||||||||||||||||||
| 2 config | 1 | |||||||||||||||||||||||||||||||||||||||
| 3 presentation.builder.sources | 1 | |||||||||||||||||||||||||||||||||||||||
| 4 theme.raw | 40 | 1 | ||||||||||||||||||||||||||||||||||||||
| 5 commands.listener | 1 | |||||||||||||||||||||||||||||||||||||||
| 6 terminal.image.protocols.ascii | 1 | 1 | 4 | 1 | ||||||||||||||||||||||||||||||||||||
| 7 terminal.image | 1 | 2 | 2 | |||||||||||||||||||||||||||||||||||||
| 8 terminal.printer | 1 | 2 | 3 | |||||||||||||||||||||||||||||||||||||
| 9 terminal.image.printer | 2 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 10 resource | 2 | |||||||||||||||||||||||||||||||||||||||
| 11 terminal.image.protocols.kitty | 1 | 4 | ||||||||||||||||||||||||||||||||||||||
| 12 theme.clean | 5 | 1 | 4 | 19 | ||||||||||||||||||||||||||||||||||||
| 13 markdown.text_style | 2 | |||||||||||||||||||||||||||||||||||||||
| 14 markdown.elements | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 15 terminal.virt | 1 | 2 | 2 | 1 | 5 | |||||||||||||||||||||||||||||||||||
| 16 code.highlighting | 2 | 2 | 2 | 2 | ||||||||||||||||||||||||||||||||||||
| 17 markdown.parse | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 18 markdown.text | 1 | 3 | ||||||||||||||||||||||||||||||||||||||
| 19 transitions | 2 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 20 ui.modals | 2 | 1 | 4 | 2 | 3 | 5 | 1 | 7 | 2 | |||||||||||||||||||||||||||||||
| 21 render.operation | 1 | 2 | 1 | 2 | 2 | 1 | ||||||||||||||||||||||||||||||||||
| 22 presentation | 1 | 1 | 4 | |||||||||||||||||||||||||||||||||||||
| 23 presentation.builder.images | 2 | 1 | 1 | 2 | 1 | 4 | ||||||||||||||||||||||||||||||||||
| 24 third_party | 1 | 3 | 4 | 2 | 2 | 6 | ||||||||||||||||||||||||||||||||||
| 25 ui.execution.disabled | 1 | 1 | 1 | 1 | 4 | |||||||||||||||||||||||||||||||||||
| 26 ui.footer | 1 | 1 | 1 | 8 | 2 | 1 | 2 | |||||||||||||||||||||||||||||||||
| 27 code.snippet | 1 | 3 | 2 | 1 | 1 | 4 | 2 | 1 | ||||||||||||||||||||||||||||||||
| 28 export.output | 1 | 1 | 1 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||
| 29 code.execute | 2 | 5 | ||||||||||||||||||||||||||||||||||||||
| 30 ui.execution.acquire_terminal | 1 | 1 | 5 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 31 ui.execution.image | 1 | 2 | 1 | 6 | 2 | 1 | 2 | |||||||||||||||||||||||||||||||||
| 32 ui.execution.pty | 4 | 1 | 1 | 1 | 1 | 11 | 3 | 5 | 1 | |||||||||||||||||||||||||||||||
| 33 ui.execution.output | 3 | 3 | 5 | 1 | 1 | 12 | 2 | 4 | 1 | 1 | ||||||||||||||||||||||||||||||
| 34 presentation.builder | 2 | 1 | 1 | 1 | 2 | 6 | 2 | 7 | 2 | 1 | 1 | 1 | 5 | 2 | 1 | 1 | 1 | 5 | 2 | 1 | 2 | |||||||||||||||||||
| 35 export.exporter | 2 | 3 | 1 | 1 | 1 | 1 | 2 | 1 | 1 | 1 | 1 | 2 | ||||||||||||||||||||||||||||
| 36 render.engine | 3 | 2 | 1 | 1 | 1 | 1 | 1 | 5 | 1 | 1 | ||||||||||||||||||||||||||||||
| 37 render | 2 | 1 | 1 | 1 | 2 | 1 | 3 | |||||||||||||||||||||||||||||||||
| 38 render.ascii_scaler | 1 | 1 | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 39 presenter | 1 | 3 | 2 | 1 | 1 | 1 | 1 | 1 | 1 | 3 | 2 | 1 | 2 | 2 | 2 | |||||||||||||||||||||||||
| 40 presenterm | 5 | 1 | 1 | 1 | 1 | 2 | 3 | 2 |
2→27 config uses code.snippet part of a loop✕
- Connections
- 1 pair of types, where a type in config uses a type in code.snippet.
- The types involved
presenterm.config.OptionsConfig→presenterm.code.snippet.SnippetLanguage
- Direction
- config uses code.snippet, so a change to code.snippet can break config, while a change to config can't break code.snippet.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
3→14 presentation.builder.sources uses markdown.elements part of a loop✕
- Connections
- 1 pair of types, where a type in presentation.builder.sources uses a type in markdown.elements.
- The types involved
presenterm.presentation.builder.sources.MarkdownSources→presenterm.markdown.elements.SourcePosition
- Direction
- presentation.builder.sources uses markdown.elements, so a change to markdown.elements can break presentation.builder.sources, while a change to presentation.builder.sources can't break markdown.elements.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
4→12 theme.raw uses theme.clean part of a loop✕
- Connections
- 40 pairs of types, where a type in theme.raw uses a type in theme.clean. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
presenterm.theme.raw.AlertStyle→presenterm.theme.clean.AlertTypeStylespresenterm.theme.raw.AlertStyle→presenterm.theme.clean.Alignmentpresenterm.theme.raw.AlertTypeStyles→presenterm.theme.clean.AlertTypeStylepresenterm.theme.raw.AuthorStyle→presenterm.theme.clean.Alignmentpresenterm.theme.raw.BasicStyle→presenterm.theme.clean.Alignmentpresenterm.theme.raw.BlockQuoteStyle→presenterm.theme.clean.Alignmentpresenterm.theme.raw.CodeBlockStyle→presenterm.theme.clean.Alignmentpresenterm.theme.raw.CodeBlockStyle→presenterm.theme.clean.PaddingRectpresenterm.theme.raw.DefaultStyle→presenterm.theme.clean.Alignmentpresenterm.theme.raw.DefaultStyle→presenterm.theme.clean.BackgroundImagepresenterm.theme.raw.ExecutionOutputBlockStyle→presenterm.theme.clean.ExecutionStatusBlockStylepresenterm.theme.raw.ExecutionOutputBlockStyle→presenterm.theme.clean.PaddingRectpresenterm.theme.raw.HeadingStyle→presenterm.theme.clean.Alignmentpresenterm.theme.raw.HeadingStyles→presenterm.theme.clean.HeadingStylepresenterm.theme.raw.IntroSlideStyle→presenterm.theme.clean.AuthorStylepresenterm.theme.raw.IntroSlideStyle→presenterm.theme.clean.IntroSlideTitleStylepresenterm.theme.raw.IntroSlideTitleStyle→presenterm.theme.clean.Alignmentpresenterm.theme.raw.PresentationTheme→presenterm.theme.clean.AlertStylepresenterm.theme.raw.PresentationTheme→presenterm.theme.clean.Alignmentpresenterm.theme.raw.PresentationTheme→presenterm.theme.clean.BlockQuoteStylepresenterm.theme.raw.PresentationTheme→presenterm.theme.clean.CodeBlockStylepresenterm.theme.raw.PresentationTheme→presenterm.theme.clean.ColorPalettepresenterm.theme.raw.PresentationTheme→presenterm.theme.clean.ColumnLayoutStylepresenterm.theme.raw.PresentationTheme→presenterm.theme.clean.D2Stylepresenterm.theme.raw.PresentationTheme→presenterm.theme.clean.DefaultStyle
- Direction
- theme.raw uses theme.clean, so a change to theme.clean can break theme.raw, while a change to theme.raw can't break theme.clean.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
4→13 theme.raw uses markdown.text_style part of a loop✕
- Connections
- 1 pair of types, where a type in theme.raw uses a type in markdown.text_style.
- The types involved
presenterm.theme.raw.RawColor→presenterm.markdown.text_style.Color
- Direction
- theme.raw uses markdown.text_style, so a change to markdown.text_style can break theme.raw, while a change to theme.raw can't break markdown.text_style.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
5→2 commands.listener uses config✕
- Connections
- 1 pair of types, where a type in commands.listener uses a type in config.
- The types involved
presenterm.commands.listener.CommandListener→presenterm.config.KeyBindingsConfig
- Direction
- commands.listener uses config, so a change to config can break commands.listener, while a change to commands.listener can't break config.
- Position
- Below the diagonal: commands.listener uses a module listed above it, which is the healthy direction.
6→3 terminal.image.protocols.ascii uses presentation.builder.sources✕
- Connections
- 1 pair of types, where a type in terminal.image.protocols.ascii uses a type in presentation.builder.sources.
- The types involved
presenterm.terminal.image.protocols.ascii.AsciiImage→presenterm.presentation.builder.sources.Inner
- Direction
- terminal.image.protocols.ascii uses presentation.builder.sources, so a change to presentation.builder.sources can break terminal.image.protocols.ascii, while a change to terminal.image.protocols.ascii can't break presentation.builder.sources.
- Position
- Below the diagonal: terminal.image.protocols.ascii uses a module listed above it, which is the healthy direction.
6→7 terminal.image.protocols.ascii uses terminal.image part of a loop✕
- Connections
- 1 pair of types, where a type in terminal.image.protocols.ascii uses a type in terminal.image.
- The types involved
presenterm.terminal.image.protocols.ascii.AsciiPrinter→presenterm.terminal.image.Image
- Direction
- terminal.image.protocols.ascii uses terminal.image, so a change to terminal.image can break terminal.image.protocols.ascii, while a change to terminal.image.protocols.ascii can't break terminal.image.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→9 terminal.image.protocols.ascii uses terminal.image.printer part of a loop✕
- Connections
- 4 pairs of types, where a type in terminal.image.protocols.ascii uses a type in terminal.image.printer.
- The types involved
presenterm.terminal.image.protocols.ascii.AsciiImage→presenterm.terminal.image.printer.ImagePropertiespresenterm.terminal.image.protocols.ascii.AsciiPrinter→presenterm.terminal.image.printer.ImageSpecpresenterm.terminal.image.protocols.ascii.AsciiPrinter→presenterm.terminal.image.printer.PrintImagepresenterm.terminal.image.protocols.ascii.AsciiPrinter→presenterm.terminal.image.printer.PrintOptions
- Direction
- terminal.image.protocols.ascii uses terminal.image.printer, so a change to terminal.image.printer can break terminal.image.protocols.ascii, while a change to terminal.image.protocols.ascii can't break terminal.image.printer.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→13 terminal.image.protocols.ascii uses markdown.text_style part of a loop✕
- Connections
- 1 pair of types, where a type in terminal.image.protocols.ascii uses a type in markdown.text_style.
- The types involved
presenterm.terminal.image.protocols.ascii.AsciiPrinter→presenterm.markdown.text_style.Color
- Direction
- terminal.image.protocols.ascii uses markdown.text_style, so a change to markdown.text_style can break terminal.image.protocols.ascii, while a change to terminal.image.protocols.ascii can't break markdown.text_style.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→3 terminal.image uses presentation.builder.sources✕
- Connections
- 1 pair of types, where a type in terminal.image uses a type in presentation.builder.sources.
- The types involved
presenterm.terminal.image.Image→presenterm.presentation.builder.sources.Inner
- Direction
- terminal.image uses presentation.builder.sources, so a change to presentation.builder.sources can break terminal.image, while a change to terminal.image can't break presentation.builder.sources.
- Position
- Below the diagonal: terminal.image uses a module listed above it, which is the healthy direction.
7→6 terminal.image uses terminal.image.protocols.ascii✕
- Connections
- 2 pairs of types, where a type in terminal.image uses a type in terminal.image.protocols.ascii.
- The types involved
presenterm.terminal.image.Image→presenterm.terminal.image.protocols.ascii.AsciiImagepresenterm.terminal.image.Inner→presenterm.terminal.image.protocols.ascii.AsciiImage
- Direction
- terminal.image uses terminal.image.protocols.ascii, so a change to terminal.image.protocols.ascii can break terminal.image, while a change to terminal.image can't break terminal.image.protocols.ascii.
- Position
- Below the diagonal: terminal.image uses a module listed above it, which is the healthy direction.
7→9 terminal.image uses terminal.image.printer part of a loop✕
- Connections
- 2 pairs of types, where a type in terminal.image uses a type in terminal.image.printer.
- The types involved
presenterm.terminal.image.Image→presenterm.terminal.image.printer.TerminalImagepresenterm.terminal.image.Inner→presenterm.terminal.image.printer.TerminalImage
- Direction
- terminal.image uses terminal.image.printer, so a change to terminal.image.printer can break terminal.image, while a change to terminal.image can't break terminal.image.printer.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→7 terminal.printer uses terminal.image✕
- Connections
- 1 pair of types, where a type in terminal.printer uses a type in terminal.image.
- The types involved
presenterm.terminal.printer.Terminal→presenterm.terminal.image.Image
- Direction
- terminal.printer uses terminal.image, so a change to terminal.image can break terminal.printer, while a change to terminal.printer can't break terminal.image.
- Position
- Below the diagonal: terminal.printer uses a module listed above it, which is the healthy direction.
8→9 terminal.printer uses terminal.image.printer part of a loop✕
- Connections
- 2 pairs of types, where a type in terminal.printer uses a type in terminal.image.printer.
- The types involved
presenterm.terminal.printer.Terminal→presenterm.terminal.image.printer.ImagePrinterpresenterm.terminal.printer.Terminal→presenterm.terminal.image.printer.PrintOptions
- Direction
- terminal.printer uses terminal.image.printer, so a change to terminal.image.printer can break terminal.printer, while a change to terminal.printer can't break terminal.image.printer.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→13 terminal.printer uses markdown.text_style part of a loop✕
- Connections
- 3 pairs of types, where a type in terminal.printer uses a type in markdown.text_style.
- The types involved
presenterm.terminal.printer.Terminal→presenterm.markdown.text_style.Colorpresenterm.terminal.printer.Terminal→presenterm.markdown.text_style.Colorspresenterm.terminal.printer.Terminal→presenterm.markdown.text_style.TextStyle
- Direction
- terminal.printer uses markdown.text_style, so a change to markdown.text_style can break terminal.printer, while a change to terminal.printer can't break markdown.text_style.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→7 terminal.image.printer uses terminal.image✕
- Connections
- 2 pairs of types, where a type in terminal.image.printer uses a type in terminal.image.
- The types involved
presenterm.terminal.image.printer.ImagePrinter→presenterm.terminal.image.Imagepresenterm.terminal.image.printer.PrintImage→presenterm.terminal.image.Image
- Direction
- terminal.image.printer uses terminal.image, so a change to terminal.image can break terminal.image.printer, while a change to terminal.image.printer can't break terminal.image.
- Position
- Below the diagonal: terminal.image.printer uses a module listed above it, which is the healthy direction.
9→8 terminal.image.printer uses terminal.printer✕
- Connections
- 1 pair of types, where a type in terminal.image.printer uses a type in terminal.printer.
- The types involved
presenterm.terminal.image.printer.PrintImageError→presenterm.terminal.printer.TerminalError
- Direction
- terminal.image.printer uses terminal.printer, so a change to terminal.printer can break terminal.image.printer, while a change to terminal.image.printer can't break terminal.printer.
- Position
- Below the diagonal: terminal.image.printer uses a module listed above it, which is the healthy direction.
9→13 terminal.image.printer uses markdown.text_style part of a loop✕
- Connections
- 2 pairs of types, where a type in terminal.image.printer uses a type in markdown.text_style.
- The types involved
presenterm.terminal.image.printer.PrintImageError→presenterm.markdown.text_style.PaletteColorErrorpresenterm.terminal.image.printer.PrintOptions→presenterm.markdown.text_style.Color
- Direction
- terminal.image.printer uses markdown.text_style, so a change to markdown.text_style can break terminal.image.printer, while a change to terminal.image.printer can't break markdown.text_style.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→9 resource uses terminal.image.printer✕
- Connections
- 2 pairs of types, where a type in resource uses a type in terminal.image.printer.
- The types involved
presenterm.resource.Resources→presenterm.terminal.image.printer.ImageRegistrypresenterm.resource.ResourcesInner→presenterm.terminal.image.printer.ImageRegistry
- Direction
- resource uses terminal.image.printer, so a change to terminal.image.printer can break resource, while a change to resource can't break terminal.image.printer.
- Position
- Below the diagonal: resource uses a module listed above it, which is the healthy direction.
11→7 terminal.image.protocols.kitty uses terminal.image✕
- Connections
- 1 pair of types, where a type in terminal.image.protocols.kitty uses a type in terminal.image.
- The types involved
presenterm.terminal.image.protocols.kitty.KittyPrinter→presenterm.terminal.image.Image
- Direction
- terminal.image.protocols.kitty uses terminal.image, so a change to terminal.image can break terminal.image.protocols.kitty, while a change to terminal.image.protocols.kitty can't break terminal.image.
- Position
- Below the diagonal: terminal.image.protocols.kitty uses a module listed above it, which is the healthy direction.
11→9 terminal.image.protocols.kitty uses terminal.image.printer✕
- Connections
- 4 pairs of types, where a type in terminal.image.protocols.kitty uses a type in terminal.image.printer.
- The types involved
presenterm.terminal.image.protocols.kitty.KittyImage→presenterm.terminal.image.printer.ImagePropertiespresenterm.terminal.image.protocols.kitty.KittyPrinter→presenterm.terminal.image.printer.ImageSpecpresenterm.terminal.image.protocols.kitty.KittyPrinter→presenterm.terminal.image.printer.PrintImagepresenterm.terminal.image.protocols.kitty.KittyPrinter→presenterm.terminal.image.printer.PrintOptions
- Direction
- terminal.image.protocols.kitty uses terminal.image.printer, so a change to terminal.image.printer can break terminal.image.protocols.kitty, while a change to terminal.image.protocols.kitty can't break terminal.image.printer.
- Position
- Below the diagonal: terminal.image.protocols.kitty uses a module listed above it, which is the healthy direction.
12→4 theme.clean uses theme.raw✕
- Connections
- 5 pairs of types, where a type in theme.clean uses a type in theme.raw.
- The types involved
presenterm.theme.clean.AuthorStyle→presenterm.theme.raw.AuthorPositioningpresenterm.theme.clean.BackgroundImage→presenterm.theme.raw.BackgroundImageFitpresenterm.theme.clean.ColumnLayoutStyle→presenterm.theme.raw.Marginpresenterm.theme.clean.DefaultStyle→presenterm.theme.raw.Marginpresenterm.theme.clean.IntroSlideLabelStyle→presenterm.theme.raw.BasicStyle
- Direction
- theme.clean uses theme.raw, so a change to theme.raw can break theme.clean, while a change to theme.clean can't break theme.raw.
- Position
- Below the diagonal: theme.clean uses a module listed above it, which is the healthy direction.
12→7 theme.clean uses terminal.image✕
- Connections
- 1 pair of types, where a type in theme.clean uses a type in terminal.image.
- The types involved
presenterm.theme.clean.BackgroundImage→presenterm.terminal.image.Image
- Direction
- theme.clean uses terminal.image, so a change to terminal.image can break theme.clean, while a change to theme.clean can't break terminal.image.
- Position
- Below the diagonal: theme.clean uses a module listed above it, which is the healthy direction.
12→10 theme.clean uses resource✕
- Connections
- 4 pairs of types, where a type in theme.clean uses a type in resource.
- The types involved
presenterm.theme.clean.DefaultStyle→presenterm.resource.Resourcespresenterm.theme.clean.FooterContent→presenterm.resource.Resourcespresenterm.theme.clean.FooterStyle→presenterm.resource.Resourcespresenterm.theme.clean.PresentationTheme→presenterm.resource.Resources
- Direction
- theme.clean uses resource, so a change to resource can break theme.clean, while a change to theme.clean can't break resource.
- Position
- Below the diagonal: theme.clean uses a module listed above it, which is the healthy direction.
12→13 theme.clean uses markdown.text_style part of a loop✕
- Connections
- 19 pairs of types, where a type in theme.clean uses a type in markdown.text_style.
- The types involved
presenterm.theme.clean.AlertStyle→presenterm.markdown.text_style.TextStylepresenterm.theme.clean.AlertTypeDefaults→presenterm.markdown.text_style.Colorpresenterm.theme.clean.AlertTypeStyle→presenterm.markdown.text_style.TextStylepresenterm.theme.clean.AlertTypeStyles→presenterm.markdown.text_style.TextStylepresenterm.theme.clean.AuthorStyle→presenterm.markdown.text_style.TextStylepresenterm.theme.clean.BlockQuoteStyle→presenterm.markdown.text_style.TextStylepresenterm.theme.clean.DefaultStyle→presenterm.markdown.text_style.TextStylepresenterm.theme.clean.ExecutionOutputBlockStyle→presenterm.markdown.text_style.TextStylepresenterm.theme.clean.ExecutionStatusBlockStyle→presenterm.markdown.text_style.TextStylepresenterm.theme.clean.HeadingStyle→presenterm.markdown.text_style.TextStylepresenterm.theme.clean.IntroSlideLabelStyle→presenterm.markdown.text_style.TextStylepresenterm.theme.clean.IntroSlideTitleStyle→presenterm.markdown.text_style.TextStylepresenterm.theme.clean.LayoutGridStyle→presenterm.markdown.text_style.TextStylepresenterm.theme.clean.ModalStyle→presenterm.markdown.text_style.TextStylepresenterm.theme.clean.ModifierStyle→presenterm.markdown.text_style.TextStylepresenterm.theme.clean.PtyCursorStyle→presenterm.markdown.text_style.TextStylepresenterm.theme.clean.PtyOutputBlockStyle→presenterm.markdown.text_style.TextStylepresenterm.theme.clean.SlideTitleStyle→presenterm.markdown.text_style.TextStylepresenterm.theme.clean.TypstStyle→presenterm.markdown.text_style.TextStyle
- Direction
- theme.clean uses markdown.text_style, so a change to markdown.text_style can break theme.clean, while a change to theme.clean can't break markdown.text_style.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→12 markdown.text_style uses theme.clean✕
- Connections
- 2 pairs of types, where a type in markdown.text_style uses a type in theme.clean.
- The types involved
presenterm.markdown.text_style.Colors→presenterm.theme.clean.ColorPalettepresenterm.markdown.text_style.TextStyle→presenterm.theme.clean.ColorPalette
- Direction
- markdown.text_style uses theme.clean, so a change to theme.clean can break markdown.text_style, while a change to markdown.text_style can't break theme.clean.
- Position
- Below the diagonal: markdown.text_style uses a module listed above it, which is the healthy direction.
14→12 markdown.elements uses theme.clean✕
- Connections
- 1 pair of types, where a type in markdown.elements uses a type in theme.clean.
- The types involved
presenterm.markdown.elements.Line→presenterm.theme.clean.ColorPalette
- Direction
- markdown.elements uses theme.clean, so a change to theme.clean can break markdown.elements, while a change to markdown.elements can't break theme.clean.
- Position
- Below the diagonal: markdown.elements uses a module listed above it, which is the healthy direction.
14→13 markdown.elements uses markdown.text_style✕
- Connections
- 2 pairs of types, where a type in markdown.elements uses a type in markdown.text_style.
- The types involved
presenterm.markdown.elements.Line→presenterm.markdown.text_style.TextStylepresenterm.markdown.elements.Text→presenterm.markdown.text_style.TextStyle
- Direction
- markdown.elements uses markdown.text_style, so a change to markdown.text_style can break markdown.elements, while a change to markdown.elements can't break markdown.text_style.
- Position
- Below the diagonal: markdown.elements uses a module listed above it, which is the healthy direction.
15→1 terminal.virt uses render.properties✕
- Connections
- 1 pair of types, where a type in terminal.virt uses a type in render.properties.
- The types involved
presenterm.terminal.virt.VirtualTerminal→presenterm.render.properties.WindowSize
- Direction
- terminal.virt uses render.properties, so a change to render.properties can break terminal.virt, while a change to terminal.virt can't break render.properties.
- Position
- Below the diagonal: terminal.virt uses a module listed above it, which is the healthy direction.
15→7 terminal.virt uses terminal.image✕
- Connections
- 2 pairs of types, where a type in terminal.virt uses a type in terminal.image.
- The types involved
presenterm.terminal.virt.PrintedImage→presenterm.terminal.image.Imagepresenterm.terminal.virt.VirtualTerminal→presenterm.terminal.image.Image
- Direction
- terminal.virt uses terminal.image, so a change to terminal.image can break terminal.virt, while a change to terminal.virt can't break terminal.image.
- Position
- Below the diagonal: terminal.virt uses a module listed above it, which is the healthy direction.
15→8 terminal.virt uses terminal.printer✕
- Connections
- 2 pairs of types, where a type in terminal.virt uses a type in terminal.printer.
- The types involved
presenterm.terminal.virt.VirtualTerminal→presenterm.terminal.printer.TerminalCommandpresenterm.terminal.virt.VirtualTerminal→presenterm.terminal.printer.TerminalIo
- Direction
- terminal.virt uses terminal.printer, so a change to terminal.printer can break terminal.virt, while a change to terminal.virt can't break terminal.printer.
- Position
- Below the diagonal: terminal.virt uses a module listed above it, which is the healthy direction.
15→9 terminal.virt uses terminal.image.printer✕
- Connections
- 1 pair of types, where a type in terminal.virt uses a type in terminal.image.printer.
- The types involved
presenterm.terminal.virt.VirtualTerminal→presenterm.terminal.image.printer.PrintOptions
- Direction
- terminal.virt uses terminal.image.printer, so a change to terminal.image.printer can break terminal.virt, while a change to terminal.virt can't break terminal.image.printer.
- Position
- Below the diagonal: terminal.virt uses a module listed above it, which is the healthy direction.
15→13 terminal.virt uses markdown.text_style✕
- Connections
- 5 pairs of types, where a type in terminal.virt uses a type in markdown.text_style.
- The types involved
presenterm.terminal.virt.StyledChar→presenterm.markdown.text_style.TextStylepresenterm.terminal.virt.TerminalGrid→presenterm.markdown.text_style.Colorpresenterm.terminal.virt.VirtualTerminal→presenterm.markdown.text_style.Colorpresenterm.terminal.virt.VirtualTerminal→presenterm.markdown.text_style.Colorspresenterm.terminal.virt.VirtualTerminal→presenterm.markdown.text_style.TextStyle
- Direction
- terminal.virt uses markdown.text_style, so a change to markdown.text_style can break terminal.virt, while a change to terminal.virt can't break markdown.text_style.
- Position
- Below the diagonal: terminal.virt uses a module listed above it, which is the healthy direction.
16→12 code.highlighting uses theme.clean✕
- Connections
- 2 pairs of types, where a type in code.highlighting uses a type in theme.clean.
- The types involved
presenterm.code.highlighting.LanguageHighlighter→presenterm.theme.clean.CodeBlockStylepresenterm.code.highlighting.StyledTokens→presenterm.theme.clean.CodeBlockStyle
- Direction
- code.highlighting uses theme.clean, so a change to theme.clean can break code.highlighting, while a change to code.highlighting can't break theme.clean.
- Position
- Below the diagonal: code.highlighting uses a module listed above it, which is the healthy direction.
16→13 code.highlighting uses markdown.text_style✕
- Connections
- 2 pairs of types, where a type in code.highlighting uses a type in markdown.text_style.
- The types involved
presenterm.code.highlighting.StyledTokens→presenterm.markdown.text_style.TextStylepresenterm.code.highlighting.highlighting$module→presenterm.markdown.text_style.Color
- Direction
- code.highlighting uses markdown.text_style, so a change to markdown.text_style can break code.highlighting, while a change to code.highlighting can't break markdown.text_style.
- Position
- Below the diagonal: code.highlighting uses a module listed above it, which is the healthy direction.
16→14 code.highlighting uses markdown.elements✕
- Connections
- 2 pairs of types, where a type in code.highlighting uses a type in markdown.elements.
- The types involved
presenterm.code.highlighting.LanguageHighlighter→presenterm.markdown.elements.Linepresenterm.code.highlighting.StyledTokens→presenterm.markdown.elements.Text
- Direction
- code.highlighting uses markdown.elements, so a change to markdown.elements can break code.highlighting, while a change to code.highlighting can't break markdown.elements.
- Position
- Below the diagonal: code.highlighting uses a module listed above it, which is the healthy direction.
16→27 code.highlighting uses code.snippet part of a loop✕
- Connections
- 2 pairs of types, where a type in code.highlighting uses a type in code.snippet.
- The types involved
presenterm.code.highlighting.LanguageHighlighter→presenterm.code.snippet.SnippetLanguagepresenterm.code.highlighting.SnippetHighlighter→presenterm.code.snippet.SnippetLanguage
- Direction
- code.highlighting uses code.snippet, so a change to code.snippet can break code.highlighting, while a change to code.highlighting can't break code.snippet.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→13 markdown.parse uses markdown.text_style✕
- Connections
- 1 pair of types, where a type in markdown.parse uses a type in markdown.text_style.
- The types involved
presenterm.markdown.parse.InlinesParser→presenterm.markdown.text_style.TextStyle
- Direction
- markdown.parse uses markdown.text_style, so a change to markdown.text_style can break markdown.parse, while a change to markdown.parse can't break markdown.text_style.
- Position
- Below the diagonal: markdown.parse uses a module listed above it, which is the healthy direction.
17→14 markdown.parse uses markdown.elements✕
- Connections
- 2 pairs of types, where a type in markdown.parse uses a type in markdown.elements.
- The types involved
presenterm.markdown.parse.InlinesParser→presenterm.markdown.elements.Textpresenterm.markdown.parse.ParseError→presenterm.markdown.elements.SourcePosition
- Direction
- markdown.parse uses markdown.elements, so a change to markdown.elements can break markdown.parse, while a change to markdown.parse can't break markdown.elements.
- Position
- Below the diagonal: markdown.parse uses a module listed above it, which is the healthy direction.
18→13 markdown.text uses markdown.text_style✕
- Connections
- 1 pair of types, where a type in markdown.text uses a type in markdown.text_style.
- The types involved
presenterm.markdown.text.WeightedTextRef→presenterm.markdown.text_style.TextStyle
- Direction
- markdown.text uses markdown.text_style, so a change to markdown.text_style can break markdown.text, while a change to markdown.text can't break markdown.text_style.
- Position
- Below the diagonal: markdown.text uses a module listed above it, which is the healthy direction.
18→14 markdown.text uses markdown.elements✕
- Connections
- 3 pairs of types, where a type in markdown.text uses a type in markdown.elements.
- The types involved
presenterm.markdown.text.WeightedLine→presenterm.markdown.elements.Linepresenterm.markdown.text.WeightedLine→presenterm.markdown.elements.Textpresenterm.markdown.text.WeightedText→presenterm.markdown.elements.Text
- Direction
- markdown.text uses markdown.elements, so a change to markdown.elements can break markdown.text, while a change to markdown.text can't break markdown.elements.
- Position
- Below the diagonal: markdown.text uses a module listed above it, which is the healthy direction.
19→8 transitions uses terminal.printer✕
- Connections
- 2 pairs of types, where a type in transitions uses a type in terminal.printer.
- The types involved
presenterm.transitions.AnimationFrame→presenterm.terminal.printer.TerminalCommandpresenterm.transitions.LinesFrame→presenterm.terminal.printer.TerminalCommand
- Direction
- transitions uses terminal.printer, so a change to terminal.printer can break transitions, while a change to transitions can't break terminal.printer.
- Position
- Below the diagonal: transitions uses a module listed above it, which is the healthy direction.
19→11 transitions uses terminal.image.protocols.kitty✕
- Connections
- 1 pair of types, where a type in transitions uses a type in terminal.image.protocols.kitty.
- The types involved
presenterm.transitions.LinesFrame→presenterm.terminal.image.protocols.kitty.AnimationFrame
- Direction
- transitions uses terminal.image.protocols.kitty, so a change to terminal.image.protocols.kitty can break transitions, while a change to transitions can't break terminal.image.protocols.kitty.
- Position
- Below the diagonal: transitions uses a module listed above it, which is the healthy direction.
19→13 transitions uses markdown.text_style✕
- Connections
- 1 pair of types, where a type in transitions uses a type in markdown.text_style.
- The types involved
presenterm.transitions.LinesFrame→presenterm.markdown.text_style.Color
- Direction
- transitions uses markdown.text_style, so a change to markdown.text_style can break transitions, while a change to transitions can't break markdown.text_style.
- Position
- Below the diagonal: transitions uses a module listed above it, which is the healthy direction.
19→14 transitions uses markdown.elements✕
- Connections
- 1 pair of types, where a type in transitions uses a type in markdown.elements.
- The types involved
presenterm.transitions.LinesFrame→presenterm.markdown.elements.Line
- Direction
- transitions uses markdown.elements, so a change to markdown.elements can break transitions, while a change to transitions can't break markdown.elements.
- Position
- Below the diagonal: transitions uses a module listed above it, which is the healthy direction.
19→15 transitions uses terminal.virt✕
- Connections
- 1 pair of types, where a type in transitions uses a type in terminal.virt.
- The types involved
presenterm.transitions.LinesFrame→presenterm.terminal.virt.TerminalGrid
- Direction
- transitions uses terminal.virt, so a change to terminal.virt can break transitions, while a change to transitions can't break terminal.virt.
- Position
- Below the diagonal: transitions uses a module listed above it, which is the healthy direction.
20→1 ui.modals uses render.properties✕
- Connections
- 2 pairs of types, where a type in ui.modals uses a type in render.properties.
- The types involved
presenterm.ui.modals.CenterModalContent→presenterm.render.properties.WindowSizepresenterm.ui.modals.IndexDrawer→presenterm.render.properties.WindowSize
- Direction
- ui.modals uses render.properties, so a change to render.properties can break ui.modals, while a change to ui.modals can't break render.properties.
- Position
- Below the diagonal: ui.modals uses a module listed above it, which is the healthy direction.
20→2 ui.modals uses config✕
- Connections
- 1 pair of types, where a type in ui.modals uses a type in config.
- The types involved
presenterm.ui.modals.KeyBindingsModalBuilder→presenterm.config.KeyBindingsConfig
- Direction
- ui.modals uses config, so a change to config can break ui.modals, while a change to ui.modals can't break config.
- Position
- Below the diagonal: ui.modals uses a module listed above it, which is the healthy direction.
20→7 ui.modals uses terminal.image✕
- Connections
- 4 pairs of types, where a type in ui.modals uses a type in terminal.image.
- The types involved
presenterm.ui.modals.CenterModalContent→presenterm.terminal.image.Imagepresenterm.ui.modals.IndexBuilder→presenterm.terminal.image.Imagepresenterm.ui.modals.IndexDrawer→presenterm.terminal.image.Imagepresenterm.ui.modals.KeyBindingsModalBuilder→presenterm.terminal.image.Image
- Direction
- ui.modals uses terminal.image, so a change to terminal.image can break ui.modals, while a change to ui.modals can't break terminal.image.
- Position
- Below the diagonal: ui.modals uses a module listed above it, which is the healthy direction.
20→12 ui.modals uses theme.clean✕
- Connections
- 2 pairs of types, where a type in ui.modals uses a type in theme.clean.
- The types involved
presenterm.ui.modals.IndexBuilder→presenterm.theme.clean.PresentationThemepresenterm.ui.modals.KeyBindingsModalBuilder→presenterm.theme.clean.PresentationTheme
- Direction
- ui.modals uses theme.clean, so a change to theme.clean can break ui.modals, while a change to ui.modals can't break theme.clean.
- Position
- Below the diagonal: ui.modals uses a module listed above it, which is the healthy direction.
20→13 ui.modals uses markdown.text_style✕
- Connections
- 3 pairs of types, where a type in ui.modals uses a type in markdown.text_style.
- The types involved
presenterm.ui.modals.ContentRow→presenterm.markdown.text_style.TextStylepresenterm.ui.modals.IndexDrawer→presenterm.markdown.text_style.TextStylepresenterm.ui.modals.ModalBuilder→presenterm.markdown.text_style.TextStyle
- Direction
- ui.modals uses markdown.text_style, so a change to markdown.text_style can break ui.modals, while a change to ui.modals can't break markdown.text_style.
- Position
- Below the diagonal: ui.modals uses a module listed above it, which is the healthy direction.
20→14 ui.modals uses markdown.elements✕
- Connections
- 5 pairs of types, where a type in ui.modals uses a type in markdown.elements.
- The types involved
presenterm.ui.modals.ContentRow→presenterm.markdown.elements.Textpresenterm.ui.modals.IndexBuilder→presenterm.markdown.elements.Linepresenterm.ui.modals.KeyBindingsModalBuilder→presenterm.markdown.elements.Linepresenterm.ui.modals.ModalBuilder→presenterm.markdown.elements.Linepresenterm.ui.modals.ModalBuilder→presenterm.markdown.elements.Text
- Direction
- ui.modals uses markdown.elements, so a change to markdown.elements can break ui.modals, while a change to ui.modals can't break markdown.elements.
- Position
- Below the diagonal: ui.modals uses a module listed above it, which is the healthy direction.
20→18 ui.modals uses markdown.text✕
- Connections
- 1 pair of types, where a type in ui.modals uses a type in markdown.text.
- The types involved
presenterm.ui.modals.ContentRow→presenterm.markdown.text.WeightedLine
- Direction
- ui.modals uses markdown.text, so a change to markdown.text can break ui.modals, while a change to ui.modals can't break markdown.text.
- Position
- Below the diagonal: ui.modals uses a module listed above it, which is the healthy direction.
20→21 ui.modals uses render.operation part of a loop✕
- Connections
- 7 pairs of types, where a type in ui.modals uses a type in render.operation.
- The types involved
presenterm.ui.modals.CenterModalContent→presenterm.render.operation.AsRenderOperationspresenterm.ui.modals.CenterModalContent→presenterm.render.operation.RenderOperationpresenterm.ui.modals.IndexBuilder→presenterm.render.operation.RenderOperationpresenterm.ui.modals.IndexDrawer→presenterm.render.operation.AsRenderOperationspresenterm.ui.modals.IndexDrawer→presenterm.render.operation.RenderOperationpresenterm.ui.modals.KeyBindingsModalBuilder→presenterm.render.operation.RenderOperationpresenterm.ui.modals.ModalContent→presenterm.render.operation.RenderOperation
- Direction
- ui.modals uses render.operation, so a change to render.operation can break ui.modals, while a change to ui.modals can't break render.operation.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→22 ui.modals uses presentation part of a loop✕
- Connections
- 2 pairs of types, where a type in ui.modals uses a type in presentation.
- The types involved
presenterm.ui.modals.IndexBuilder→presenterm.presentation.PresentationStatepresenterm.ui.modals.IndexDrawer→presenterm.presentation.PresentationState
- Direction
- ui.modals uses presentation, so a change to presentation can break ui.modals, while a change to ui.modals can't break presentation.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
21→1 render.operation uses render.properties✕
- Connections
- 1 pair of types, where a type in render.operation uses a type in render.properties.
- The types involved
presenterm.render.operation.AsRenderOperations→presenterm.render.properties.WindowSize
- Direction
- render.operation uses render.properties, so a change to render.properties can break render.operation, while a change to render.operation can't break render.properties.
- Position
- Below the diagonal: render.operation uses a module listed above it, which is the healthy direction.
21→4 render.operation uses theme.raw✕
- Connections
- 2 pairs of types, where a type in render.operation uses a type in theme.raw.
- The types involved
presenterm.render.operation.ImageSize→presenterm.theme.raw.BackgroundImageFitpresenterm.render.operation.MarginProperties→presenterm.theme.raw.Margin
- Direction
- render.operation uses theme.raw, so a change to theme.raw can break render.operation, while a change to render.operation can't break theme.raw.
- Position
- Below the diagonal: render.operation uses a module listed above it, which is the healthy direction.
21→12 render.operation uses theme.clean✕
- Connections
- 1 pair of types, where a type in render.operation uses a type in theme.clean.
- The types involved
presenterm.render.operation.BlockLine→presenterm.theme.clean.Alignment
- Direction
- render.operation uses theme.clean, so a change to theme.clean can break render.operation, while a change to render.operation can't break theme.clean.
- Position
- Below the diagonal: render.operation uses a module listed above it, which is the healthy direction.
21→13 render.operation uses markdown.text_style✕
- Connections
- 2 pairs of types, where a type in render.operation uses a type in markdown.text_style.
- The types involved
presenterm.render.operation.BlockLine→presenterm.markdown.text_style.Colorpresenterm.render.operation.ImageRenderProperties→presenterm.markdown.text_style.Color
- Direction
- render.operation uses markdown.text_style, so a change to markdown.text_style can break render.operation, while a change to render.operation can't break markdown.text_style.
- Position
- Below the diagonal: render.operation uses a module listed above it, which is the healthy direction.
21→18 render.operation uses markdown.text✕
- Connections
- 2 pairs of types, where a type in render.operation uses a type in markdown.text.
- The types involved
presenterm.render.operation.BlockLine→presenterm.markdown.text.WeightedLinepresenterm.render.operation.BlockLine→presenterm.markdown.text.WeightedText
- Direction
- render.operation uses markdown.text, so a change to markdown.text can break render.operation, while a change to render.operation can't break markdown.text.
- Position
- Below the diagonal: render.operation uses a module listed above it, which is the healthy direction.
21→20 render.operation uses ui.modals✕
- Connections
- 1 pair of types, where a type in render.operation uses a type in ui.modals.
- The types involved
presenterm.render.operation.RenderOperation→presenterm.ui.modals.CenterModalContent
- Direction
- render.operation uses ui.modals, so a change to ui.modals can break render.operation, while a change to render.operation can't break ui.modals.
- Position
- Below the diagonal: render.operation uses a module listed above it, which is the healthy direction.
22→2 presentation uses config✕
- Connections
- 1 pair of types, where a type in presentation uses a type in config.
- The types involved
presenterm.presentation.PresentationMetadata→presenterm.config.OptionsConfig
- Direction
- presentation uses config, so a change to config can break presentation, while a change to presentation can't break config.
- Position
- Below the diagonal: presentation uses a module listed above it, which is the healthy direction.
22→12 presentation uses theme.clean✕
- Connections
- 1 pair of types, where a type in presentation uses a type in theme.clean.
- The types involved
presenterm.presentation.PresentationThemeMetadata→presenterm.theme.clean.PresentationTheme
- Direction
- presentation uses theme.clean, so a change to theme.clean can break presentation, while a change to presentation can't break theme.clean.
- Position
- Below the diagonal: presentation uses a module listed above it, which is the healthy direction.
22→21 presentation uses render.operation✕
- Connections
- 4 pairs of types, where a type in presentation uses a type in render.operation.
- The types involved
presenterm.presentation.Modals→presenterm.render.operation.RenderOperationpresenterm.presentation.Slide→presenterm.render.operation.RenderOperationpresenterm.presentation.SlideBuilder→presenterm.render.operation.RenderOperationpresenterm.presentation.SlideChunk→presenterm.render.operation.RenderOperation
- Direction
- presentation uses render.operation, so a change to render.operation can break presentation, while a change to presentation can't break render.operation.
- Position
- Below the diagonal: presentation uses a module listed above it, which is the healthy direction.
23→1 presentation.builder.images uses render.properties✕
- Connections
- 2 pairs of types, where a type in presentation.builder.images uses a type in render.properties.
- The types involved
presenterm.presentation.builder.images.BackgroundImageSlot→presenterm.render.properties.WindowSizepresenterm.presentation.builder.images.CoverImageRenderer→presenterm.render.properties.WindowSize
- Direction
- presentation.builder.images uses render.properties, so a change to render.properties can break presentation.builder.images, while a change to presentation.builder.images can't break render.properties.
- Position
- Below the diagonal: presentation.builder.images uses a module listed above it, which is the healthy direction.
23→4 presentation.builder.images uses theme.raw✕
- Connections
- 1 pair of types, where a type in presentation.builder.images uses a type in theme.raw.
- The types involved
presenterm.presentation.builder.images.BackgroundImageSlot→presenterm.theme.raw.BackgroundImageFit
- Direction
- presentation.builder.images uses theme.raw, so a change to theme.raw can break presentation.builder.images, while a change to presentation.builder.images can't break theme.raw.
- Position
- Below the diagonal: presentation.builder.images uses a module listed above it, which is the healthy direction.
23→7 presentation.builder.images uses terminal.image✕
- Connections
- 1 pair of types, where a type in presentation.builder.images uses a type in terminal.image.
- The types involved
presenterm.presentation.builder.images.BackgroundImageSlot→presenterm.terminal.image.Image
- Direction
- presentation.builder.images uses terminal.image, so a change to terminal.image can break presentation.builder.images, while a change to presentation.builder.images can't break terminal.image.
- Position
- Below the diagonal: presentation.builder.images uses a module listed above it, which is the healthy direction.
23→9 presentation.builder.images uses terminal.image.printer✕
- Connections
- 2 pairs of types, where a type in presentation.builder.images uses a type in terminal.image.printer.
- The types involved
presenterm.presentation.builder.images.BackgroundImageSlot→presenterm.terminal.image.printer.ImageRegistrypresenterm.presentation.builder.images.CoverImageRenderer→presenterm.terminal.image.printer.ImageRegistry
- Direction
- presentation.builder.images uses terminal.image.printer, so a change to terminal.image.printer can break presentation.builder.images, while a change to presentation.builder.images can't break terminal.image.printer.
- Position
- Below the diagonal: presentation.builder.images uses a module listed above it, which is the healthy direction.
23→14 presentation.builder.images uses markdown.elements✕
- Connections
- 1 pair of types, where a type in presentation.builder.images uses a type in markdown.elements.
- The types involved
presenterm.presentation.builder.images.ImageAttributes→presenterm.markdown.elements.Percent
- Direction
- presentation.builder.images uses markdown.elements, so a change to markdown.elements can break presentation.builder.images, while a change to presentation.builder.images can't break markdown.elements.
- Position
- Below the diagonal: presentation.builder.images uses a module listed above it, which is the healthy direction.
23→21 presentation.builder.images uses render.operation✕
- Connections
- 4 pairs of types, where a type in presentation.builder.images uses a type in render.operation.
- The types involved
presenterm.presentation.builder.images.BackgroundImageSlot→presenterm.render.operation.AsRenderOperationspresenterm.presentation.builder.images.BackgroundImageSlot→presenterm.render.operation.RenderOperationpresenterm.presentation.builder.images.CoverImageRenderer→presenterm.render.operation.AsRenderOperationspresenterm.presentation.builder.images.CoverImageRenderer→presenterm.render.operation.RenderOperation
- Direction
- presentation.builder.images uses render.operation, so a change to render.operation can break presentation.builder.images, while a change to presentation.builder.images can't break render.operation.
- Position
- Below the diagonal: presentation.builder.images uses a module listed above it, which is the healthy direction.
24→1 third_party uses render.properties✕
- Connections
- 1 pair of types, where a type in third_party uses a type in render.properties.
- The types involved
presenterm.third_party.RenderThirdParty→presenterm.render.properties.WindowSize
- Direction
- third_party uses render.properties, so a change to render.properties can break third_party, while a change to third_party can't break render.properties.
- Position
- Below the diagonal: third_party uses a module listed above it, which is the healthy direction.
24→9 third_party uses terminal.image.printer✕
- Connections
- 3 pairs of types, where a type in third_party uses a type in terminal.image.printer.
- The types involved
presenterm.third_party.RenderPool→presenterm.terminal.image.printer.ImageRegistrypresenterm.third_party.RenderPoolState→presenterm.terminal.image.printer.ImageRegistrypresenterm.third_party.ThirdPartyRender→presenterm.terminal.image.printer.ImageRegistry
- Direction
- third_party uses terminal.image.printer, so a change to terminal.image.printer can break third_party, while a change to third_party can't break terminal.image.printer.
- Position
- Below the diagonal: third_party uses a module listed above it, which is the healthy direction.
24→12 third_party uses theme.clean✕
- Connections
- 4 pairs of types, where a type in third_party uses a type in theme.clean.
- The types involved
presenterm.third_party.ThirdPartyRender→presenterm.theme.clean.PresentationThemepresenterm.third_party.Worker→presenterm.theme.clean.D2Stylepresenterm.third_party.Worker→presenterm.theme.clean.MermaidStylepresenterm.third_party.Worker→presenterm.theme.clean.TypstStyle
- Direction
- third_party uses theme.clean, so a change to theme.clean can break third_party, while a change to third_party can't break theme.clean.
- Position
- Below the diagonal: third_party uses a module listed above it, which is the healthy direction.
24→13 third_party uses markdown.text_style✕
- Connections
- 2 pairs of types, where a type in third_party uses a type in markdown.text_style.
- The types involved
presenterm.third_party.RenderThirdParty→presenterm.markdown.text_style.TextStylepresenterm.third_party.Worker→presenterm.markdown.text_style.Color
- Direction
- third_party uses markdown.text_style, so a change to markdown.text_style can break third_party, while a change to third_party can't break markdown.text_style.
- Position
- Below the diagonal: third_party uses a module listed above it, which is the healthy direction.
24→14 third_party uses markdown.elements✕
- Connections
- 2 pairs of types, where a type in third_party uses a type in markdown.elements.
- The types involved
presenterm.third_party.RenderThirdParty→presenterm.markdown.elements.Percentpresenterm.third_party.ThirdPartyRender→presenterm.markdown.elements.Percent
- Direction
- third_party uses markdown.elements, so a change to markdown.elements can break third_party, while a change to third_party can't break markdown.elements.
- Position
- Below the diagonal: third_party uses a module listed above it, which is the healthy direction.
24→21 third_party uses render.operation✕
- Connections
- 6 pairs of types, where a type in third_party uses a type in render.operation.
- The types involved
presenterm.third_party.OperationPollable→presenterm.render.operation.Pollablepresenterm.third_party.OperationPollable→presenterm.render.operation.PollableStatepresenterm.third_party.RenderThirdParty→presenterm.render.operation.AsRenderOperationspresenterm.third_party.RenderThirdParty→presenterm.render.operation.RenderAsyncpresenterm.third_party.RenderThirdParty→presenterm.render.operation.RenderAsyncStartPolicypresenterm.third_party.RenderThirdParty→presenterm.render.operation.RenderOperation
- Direction
- third_party uses render.operation, so a change to render.operation can break third_party, while a change to third_party can't break render.operation.
- Position
- Below the diagonal: third_party uses a module listed above it, which is the healthy direction.
25→1 ui.execution.disabled uses render.properties✕
- Connections
- 1 pair of types, where a type in ui.execution.disabled uses a type in render.properties.
- The types involved
presenterm.ui.execution.disabled.SnippetExecutionDisabledOperation→presenterm.render.properties.WindowSize
- Direction
- ui.execution.disabled uses render.properties, so a change to render.properties can break ui.execution.disabled, while a change to ui.execution.disabled can't break render.properties.
- Position
- Below the diagonal: ui.execution.disabled uses a module listed above it, which is the healthy direction.
25→12 ui.execution.disabled uses theme.clean✕
- Connections
- 1 pair of types, where a type in ui.execution.disabled uses a type in theme.clean.
- The types involved
presenterm.ui.execution.disabled.SnippetExecutionDisabledOperation→presenterm.theme.clean.Alignment
- Direction
- ui.execution.disabled uses theme.clean, so a change to theme.clean can break ui.execution.disabled, while a change to ui.execution.disabled can't break theme.clean.
- Position
- Below the diagonal: ui.execution.disabled uses a module listed above it, which is the healthy direction.
25→13 ui.execution.disabled uses markdown.text_style✕
- Connections
- 1 pair of types, where a type in ui.execution.disabled uses a type in markdown.text_style.
- The types involved
presenterm.ui.execution.disabled.SnippetExecutionDisabledOperation→presenterm.markdown.text_style.TextStyle
- Direction
- ui.execution.disabled uses markdown.text_style, so a change to markdown.text_style can break ui.execution.disabled, while a change to ui.execution.disabled can't break markdown.text_style.
- Position
- Below the diagonal: ui.execution.disabled uses a module listed above it, which is the healthy direction.
25→14 ui.execution.disabled uses markdown.elements✕
- Connections
- 1 pair of types, where a type in ui.execution.disabled uses a type in markdown.elements.
- The types involved
presenterm.ui.execution.disabled.SnippetExecutionDisabledOperation→presenterm.markdown.elements.Text
- Direction
- ui.execution.disabled uses markdown.elements, so a change to markdown.elements can break ui.execution.disabled, while a change to ui.execution.disabled can't break markdown.elements.
- Position
- Below the diagonal: ui.execution.disabled uses a module listed above it, which is the healthy direction.
25→21 ui.execution.disabled uses render.operation✕
- Connections
- 4 pairs of types, where a type in ui.execution.disabled uses a type in render.operation.
- The types involved
presenterm.ui.execution.disabled.SnippetExecutionDisabledOperation→presenterm.render.operation.AsRenderOperationspresenterm.ui.execution.disabled.SnippetExecutionDisabledOperation→presenterm.render.operation.RenderAsyncpresenterm.ui.execution.disabled.SnippetExecutionDisabledOperation→presenterm.render.operation.RenderAsyncStartPolicypresenterm.ui.execution.disabled.SnippetExecutionDisabledOperation→presenterm.render.operation.RenderOperation
- Direction
- ui.execution.disabled uses render.operation, so a change to render.operation can break ui.execution.disabled, while a change to ui.execution.disabled can't break render.operation.
- Position
- Below the diagonal: ui.execution.disabled uses a module listed above it, which is the healthy direction.
26→1 ui.footer uses render.properties✕
- Connections
- 1 pair of types, where a type in ui.footer uses a type in render.properties.
- The types involved
presenterm.ui.footer.FooterGenerator→presenterm.render.properties.WindowSize
- Direction
- ui.footer uses render.properties, so a change to render.properties can break ui.footer, while a change to ui.footer can't break render.properties.
- Position
- Below the diagonal: ui.footer uses a module listed above it, which is the healthy direction.
26→4 ui.footer uses theme.raw✕
- Connections
- 1 pair of types, where a type in ui.footer uses a type in theme.raw.
- The types involved
presenterm.ui.footer.FooterLine→presenterm.theme.raw.FooterTemplate
- Direction
- ui.footer uses theme.raw, so a change to theme.raw can break ui.footer, while a change to ui.footer can't break theme.raw.
- Position
- Below the diagonal: ui.footer uses a module listed above it, which is the healthy direction.
26→7 ui.footer uses terminal.image✕
- Connections
- 1 pair of types, where a type in ui.footer uses a type in terminal.image.
- The types involved
presenterm.ui.footer.FooterGenerator→presenterm.terminal.image.Image
- Direction
- ui.footer uses terminal.image, so a change to terminal.image can break ui.footer, while a change to ui.footer can't break terminal.image.
- Position
- Below the diagonal: ui.footer uses a module listed above it, which is the healthy direction.
26→12 ui.footer uses theme.clean✕
- Connections
- 8 pairs of types, where a type in ui.footer uses a type in theme.clean.
- The types involved
presenterm.ui.footer.FooterGenerator→presenterm.theme.clean.Alignmentpresenterm.ui.footer.FooterGenerator→presenterm.theme.clean.ColorPalettepresenterm.ui.footer.FooterGenerator→presenterm.theme.clean.FooterStylepresenterm.ui.footer.FooterLine→presenterm.theme.clean.ColorPalettepresenterm.ui.footer.RenderedFooterContent→presenterm.theme.clean.ColorPalettepresenterm.ui.footer.RenderedFooterContent→presenterm.theme.clean.FooterContentpresenterm.ui.footer.RenderedFooterStyle→presenterm.theme.clean.ColorPalettepresenterm.ui.footer.RenderedFooterStyle→presenterm.theme.clean.FooterStyle
- Direction
- ui.footer uses theme.clean, so a change to theme.clean can break ui.footer, while a change to ui.footer can't break theme.clean.
- Position
- Below the diagonal: ui.footer uses a module listed above it, which is the healthy direction.
26→13 ui.footer uses markdown.text_style✕
- Connections
- 2 pairs of types, where a type in ui.footer uses a type in markdown.text_style.
- The types involved
presenterm.ui.footer.FooterLine→presenterm.markdown.text_style.TextStylepresenterm.ui.footer.RenderedFooterContent→presenterm.markdown.text_style.TextStyle
- Direction
- ui.footer uses markdown.text_style, so a change to markdown.text_style can break ui.footer, while a change to ui.footer can't break markdown.text_style.
- Position
- Below the diagonal: ui.footer uses a module listed above it, which is the healthy direction.
26→14 ui.footer uses markdown.elements✕
- Connections
- 1 pair of types, where a type in ui.footer uses a type in markdown.elements.
- The types involved
presenterm.ui.footer.FooterLine→presenterm.markdown.elements.Line
- Direction
- ui.footer uses markdown.elements, so a change to markdown.elements can break ui.footer, while a change to ui.footer can't break markdown.elements.
- Position
- Below the diagonal: ui.footer uses a module listed above it, which is the healthy direction.
26→21 ui.footer uses render.operation✕
- Connections
- 2 pairs of types, where a type in ui.footer uses a type in render.operation.
- The types involved
presenterm.ui.footer.FooterGenerator→presenterm.render.operation.AsRenderOperationspresenterm.ui.footer.FooterGenerator→presenterm.render.operation.RenderOperation
- Direction
- ui.footer uses render.operation, so a change to render.operation can break ui.footer, while a change to ui.footer can't break render.operation.
- Position
- Below the diagonal: ui.footer uses a module listed above it, which is the healthy direction.
27→1 code.snippet uses render.properties✕
- Connections
- 1 pair of types, where a type in code.snippet uses a type in render.properties.
- The types involved
presenterm.code.snippet.HighlightedLine→presenterm.render.properties.WindowSize
- Direction
- code.snippet uses render.properties, so a change to render.properties can break code.snippet, while a change to code.snippet can't break render.properties.
- Position
- Below the diagonal: code.snippet uses a module listed above it, which is the healthy direction.
27→12 code.snippet uses theme.clean✕
- Connections
- 3 pairs of types, where a type in code.snippet uses a type in theme.clean.
- The types involved
presenterm.code.snippet.HighlightContext→presenterm.theme.clean.Alignmentpresenterm.code.snippet.SnippetLine→presenterm.theme.clean.CodeBlockStylepresenterm.code.snippet.SnippetSplitter→presenterm.theme.clean.CodeBlockStyle
- Direction
- code.snippet uses theme.clean, so a change to theme.clean can break code.snippet, while a change to code.snippet can't break theme.clean.
- Position
- Below the diagonal: code.snippet uses a module listed above it, which is the healthy direction.
27→13 code.snippet uses markdown.text_style✕
- Connections
- 2 pairs of types, where a type in code.snippet uses a type in markdown.text_style.
- The types involved
presenterm.code.snippet.HighlightedLine→presenterm.markdown.text_style.Colorpresenterm.code.snippet.SnippetLine→presenterm.markdown.text_style.TextStyle
- Direction
- code.snippet uses markdown.text_style, so a change to markdown.text_style can break code.snippet, while a change to code.snippet can't break markdown.text_style.
- Position
- Below the diagonal: code.snippet uses a module listed above it, which is the healthy direction.
27→14 code.snippet uses markdown.elements✕
- Connections
- 1 pair of types, where a type in code.snippet uses a type in markdown.elements.
- The types involved
presenterm.code.snippet.SnippetAttributes→presenterm.markdown.elements.Percent
- Direction
- code.snippet uses markdown.elements, so a change to markdown.elements can break code.snippet, while a change to code.snippet can't break markdown.elements.
- Position
- Below the diagonal: code.snippet uses a module listed above it, which is the healthy direction.
27→16 code.snippet uses code.highlighting✕
- Connections
- 1 pair of types, where a type in code.snippet uses a type in code.highlighting.
- The types involved
presenterm.code.snippet.SnippetLine→presenterm.code.highlighting.LanguageHighlighter
- Direction
- code.snippet uses code.highlighting, so a change to code.highlighting can break code.snippet, while a change to code.snippet can't break code.highlighting.
- Position
- Below the diagonal: code.snippet uses a module listed above it, which is the healthy direction.
27→18 code.snippet uses markdown.text✕
- Connections
- 4 pairs of types, where a type in code.snippet uses a type in markdown.text.
- The types involved
presenterm.code.snippet.HighlightedLine→presenterm.markdown.text.WeightedLinepresenterm.code.snippet.HighlightedLine→presenterm.markdown.text.WeightedTextpresenterm.code.snippet.SnippetLine→presenterm.markdown.text.WeightedLinepresenterm.code.snippet.SnippetLine→presenterm.markdown.text.WeightedText
- Direction
- code.snippet uses markdown.text, so a change to markdown.text can break code.snippet, while a change to code.snippet can't break markdown.text.
- Position
- Below the diagonal: code.snippet uses a module listed above it, which is the healthy direction.
27→21 code.snippet uses render.operation✕
- Connections
- 2 pairs of types, where a type in code.snippet uses a type in render.operation.
- The types involved
presenterm.code.snippet.HighlightedLine→presenterm.render.operation.AsRenderOperationspresenterm.code.snippet.HighlightedLine→presenterm.render.operation.RenderOperation
- Direction
- code.snippet uses render.operation, so a change to render.operation can break code.snippet, while a change to code.snippet can't break render.operation.
- Position
- Below the diagonal: code.snippet uses a module listed above it, which is the healthy direction.
27→22 code.snippet uses presentation✕
- Connections
- 1 pair of types, where a type in code.snippet uses a type in presentation.
- The types involved
presenterm.code.snippet.HighlightMutator→presenterm.presentation.ChunkMutator
- Direction
- code.snippet uses presentation, so a change to presentation can break code.snippet, while a change to code.snippet can't break presentation.
- Position
- Below the diagonal: code.snippet uses a module listed above it, which is the healthy direction.
28→1 export.output uses render.properties✕
- Connections
- 1 pair of types, where a type in export.output uses a type in render.properties.
- The types involved
presenterm.export.output.ExportRenderer→presenterm.render.properties.WindowSize
- Direction
- export.output uses render.properties, so a change to render.properties can break export.output, while a change to export.output can't break render.properties.
- Position
- Below the diagonal: export.output uses a module listed above it, which is the healthy direction.
28→2 export.output uses config✕
- Connections
- 1 pair of types, where a type in export.output uses a type in config.
- The types involved
presenterm.export.output.ExportRenderer→presenterm.config.ExportFontsConfig
- Direction
- export.output uses config, so a change to config can break export.output, while a change to export.output can't break config.
- Position
- Below the diagonal: export.output uses a module listed above it, which is the healthy direction.
28→13 export.output uses markdown.text_style✕
- Connections
- 1 pair of types, where a type in export.output uses a type in markdown.text_style.
- The types involved
presenterm.export.output.HtmlSlide→presenterm.markdown.text_style.TextStyle
- Direction
- export.output uses markdown.text_style, so a change to markdown.text_style can break export.output, while a change to export.output can't break markdown.text_style.
- Position
- Below the diagonal: export.output uses a module listed above it, which is the healthy direction.
28→15 export.output uses terminal.virt✕
- Connections
- 1 pair of types, where a type in export.output uses a type in terminal.virt.
- The types involved
presenterm.export.output.HtmlSlide→presenterm.terminal.virt.TerminalGrid
- Direction
- export.output uses terminal.virt, so a change to terminal.virt can break export.output, while a change to export.output can't break terminal.virt.
- Position
- Below the diagonal: export.output uses a module listed above it, which is the healthy direction.
28→22 export.output uses presentation✕
- Connections
- 1 pair of types, where a type in export.output uses a type in presentation.
- The types involved
presenterm.export.output.ExportRenderer→presenterm.presentation.Slide
- Direction
- export.output uses presentation, so a change to presentation can break export.output, while a change to export.output can't break presentation.
- Position
- Below the diagonal: export.output uses a module listed above it, which is the healthy direction.
28→35 export.output uses export.exporter part of a loop✕
- Connections
- 2 pairs of types, where a type in export.output uses a type in export.exporter.
- The types involved
presenterm.export.output.ContentManager→presenterm.export.exporter.OutputDirectorypresenterm.export.output.ExportRenderer→presenterm.export.exporter.OutputDirectory
- Direction
- export.output uses export.exporter, so a change to export.exporter can break export.output, while a change to export.output can't break export.exporter.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
29→2 code.execute uses config✕
- Connections
- 2 pairs of types, where a type in code.execute uses a type in config.
- The types involved
presenterm.code.execute.LanguageSnippetExecutor→presenterm.config.SnippetExecutorConfigpresenterm.code.execute.SnippetExecutor→presenterm.config.SnippetExecutorConfig
- Direction
- code.execute uses config, so a change to config can break code.execute, while a change to code.execute can't break config.
- Position
- Below the diagonal: code.execute uses a module listed above it, which is the healthy direction.
29→27 code.execute uses code.snippet✕
- Connections
- 5 pairs of types, where a type in code.execute uses a type in code.snippet.
- The types involved
presenterm.code.execute.InvalidSnippetConfig→presenterm.code.snippet.SnippetLanguagepresenterm.code.execute.LanguageSnippetExecutor→presenterm.code.snippet.Snippetpresenterm.code.execute.SnippetExecutor→presenterm.code.snippet.SnippetExecutorSpecpresenterm.code.execute.SnippetExecutor→presenterm.code.snippet.SnippetLanguagepresenterm.code.execute.UnsupportedExecution→presenterm.code.snippet.SnippetLanguage
- Direction
- code.execute uses code.snippet, so a change to code.snippet can break code.execute, while a change to code.execute can't break code.snippet.
- Position
- Below the diagonal: code.execute uses a module listed above it, which is the healthy direction.
30→1 ui.execution.acquire_terminal uses render.properties✕
- Connections
- 1 pair of types, where a type in ui.execution.acquire_terminal uses a type in render.properties.
- The types involved
presenterm.ui.execution.acquire_terminal.RunAcquireTerminalSnippet→presenterm.render.properties.WindowSize
- Direction
- ui.execution.acquire_terminal uses render.properties, so a change to render.properties can break ui.execution.acquire_terminal, while a change to ui.execution.acquire_terminal can't break render.properties.
- Position
- Below the diagonal: ui.execution.acquire_terminal uses a module listed above it, which is the healthy direction.
30→12 ui.execution.acquire_terminal uses theme.clean✕
- Connections
- 1 pair of types, where a type in ui.execution.acquire_terminal uses a type in theme.clean.
- The types involved
presenterm.ui.execution.acquire_terminal.RunAcquireTerminalSnippet→presenterm.theme.clean.ExecutionStatusBlockStyle
- Direction
- ui.execution.acquire_terminal uses theme.clean, so a change to theme.clean can break ui.execution.acquire_terminal, while a change to ui.execution.acquire_terminal can't break theme.clean.
- Position
- Below the diagonal: ui.execution.acquire_terminal uses a module listed above it, which is the healthy direction.
30→21 ui.execution.acquire_terminal uses render.operation✕
- Connections
- 5 pairs of types, where a type in ui.execution.acquire_terminal uses a type in render.operation.
- The types involved
presenterm.ui.execution.acquire_terminal.OperationPollable→presenterm.render.operation.Pollablepresenterm.ui.execution.acquire_terminal.OperationPollable→presenterm.render.operation.PollableStatepresenterm.ui.execution.acquire_terminal.RunAcquireTerminalSnippet→presenterm.render.operation.AsRenderOperationspresenterm.ui.execution.acquire_terminal.RunAcquireTerminalSnippet→presenterm.render.operation.RenderAsyncpresenterm.ui.execution.acquire_terminal.RunAcquireTerminalSnippet→presenterm.render.operation.RenderOperation
- Direction
- ui.execution.acquire_terminal uses render.operation, so a change to render.operation can break ui.execution.acquire_terminal, while a change to ui.execution.acquire_terminal can't break render.operation.
- Position
- Below the diagonal: ui.execution.acquire_terminal uses a module listed above it, which is the healthy direction.
30→27 ui.execution.acquire_terminal uses code.snippet✕
- Connections
- 1 pair of types, where a type in ui.execution.acquire_terminal uses a type in code.snippet.
- The types involved
presenterm.ui.execution.acquire_terminal.RunAcquireTerminalSnippet→presenterm.code.snippet.Snippet
- Direction
- ui.execution.acquire_terminal uses code.snippet, so a change to code.snippet can break ui.execution.acquire_terminal, while a change to ui.execution.acquire_terminal can't break code.snippet.
- Position
- Below the diagonal: ui.execution.acquire_terminal uses a module listed above it, which is the healthy direction.
30→29 ui.execution.acquire_terminal uses code.execute✕
- Connections
- 1 pair of types, where a type in ui.execution.acquire_terminal uses a type in code.execute.
- The types involved
presenterm.ui.execution.acquire_terminal.RunAcquireTerminalSnippet→presenterm.code.execute.LanguageSnippetExecutor
- Direction
- ui.execution.acquire_terminal uses code.execute, so a change to code.execute can break ui.execution.acquire_terminal, while a change to ui.execution.acquire_terminal can't break code.execute.
- Position
- Below the diagonal: ui.execution.acquire_terminal uses a module listed above it, which is the healthy direction.
31→1 ui.execution.image uses render.properties✕
- Connections
- 1 pair of types, where a type in ui.execution.image uses a type in render.properties.
- The types involved
presenterm.ui.execution.image.RunImageSnippet→presenterm.render.properties.WindowSize
- Direction
- ui.execution.image uses render.properties, so a change to render.properties can break ui.execution.image, while a change to ui.execution.image can't break render.properties.
- Position
- Below the diagonal: ui.execution.image uses a module listed above it, which is the healthy direction.
31→9 ui.execution.image uses terminal.image.printer✕
- Connections
- 2 pairs of types, where a type in ui.execution.image uses a type in terminal.image.printer.
- The types involved
presenterm.ui.execution.image.OperationPollable→presenterm.terminal.image.printer.ImageRegistrypresenterm.ui.execution.image.RunImageSnippet→presenterm.terminal.image.printer.ImageRegistry
- Direction
- ui.execution.image uses terminal.image.printer, so a change to terminal.image.printer can break ui.execution.image, while a change to ui.execution.image can't break terminal.image.printer.
- Position
- Below the diagonal: ui.execution.image uses a module listed above it, which is the healthy direction.
31→12 ui.execution.image uses theme.clean✕
- Connections
- 1 pair of types, where a type in ui.execution.image uses a type in theme.clean.
- The types involved
presenterm.ui.execution.image.RunImageSnippet→presenterm.theme.clean.ExecutionStatusBlockStyle
- Direction
- ui.execution.image uses theme.clean, so a change to theme.clean can break ui.execution.image, while a change to ui.execution.image can't break theme.clean.
- Position
- Below the diagonal: ui.execution.image uses a module listed above it, which is the healthy direction.
31→21 ui.execution.image uses render.operation✕
- Connections
- 6 pairs of types, where a type in ui.execution.image uses a type in render.operation.
- The types involved
presenterm.ui.execution.image.OperationPollable→presenterm.render.operation.Pollablepresenterm.ui.execution.image.OperationPollable→presenterm.render.operation.PollableStatepresenterm.ui.execution.image.RunImageSnippet→presenterm.render.operation.AsRenderOperationspresenterm.ui.execution.image.RunImageSnippet→presenterm.render.operation.RenderAsyncpresenterm.ui.execution.image.RunImageSnippet→presenterm.render.operation.RenderAsyncStartPolicypresenterm.ui.execution.image.RunImageSnippet→presenterm.render.operation.RenderOperation
- Direction
- ui.execution.image uses render.operation, so a change to render.operation can break ui.execution.image, while a change to ui.execution.image can't break render.operation.
- Position
- Below the diagonal: ui.execution.image uses a module listed above it, which is the healthy direction.
31→27 ui.execution.image uses code.snippet✕
- Connections
- 2 pairs of types, where a type in ui.execution.image uses a type in code.snippet.
- The types involved
presenterm.ui.execution.image.OperationPollable→presenterm.code.snippet.Snippetpresenterm.ui.execution.image.RunImageSnippet→presenterm.code.snippet.Snippet
- Direction
- ui.execution.image uses code.snippet, so a change to code.snippet can break ui.execution.image, while a change to ui.execution.image can't break code.snippet.
- Position
- Below the diagonal: ui.execution.image uses a module listed above it, which is the healthy direction.
31→29 ui.execution.image uses code.execute✕
- Connections
- 1 pair of types, where a type in ui.execution.image uses a type in code.execute.
- The types involved
presenterm.ui.execution.image.RunImageSnippet→presenterm.code.execute.LanguageSnippetExecutor
- Direction
- ui.execution.image uses code.execute, so a change to code.execute can break ui.execution.image, while a change to ui.execution.image can't break code.execute.
- Position
- Below the diagonal: ui.execution.image uses a module listed above it, which is the healthy direction.
31→30 ui.execution.image uses ui.execution.acquire_terminal✕
- Connections
- 2 pairs of types, where a type in ui.execution.image uses a type in ui.execution.acquire_terminal.
- The types involved
presenterm.ui.execution.image.OperationPollable→presenterm.ui.execution.acquire_terminal.Statepresenterm.ui.execution.image.RunImageSnippet→presenterm.ui.execution.acquire_terminal.State
- Direction
- ui.execution.image uses ui.execution.acquire_terminal, so a change to ui.execution.acquire_terminal can break ui.execution.image, while a change to ui.execution.image can't break ui.execution.acquire_terminal.
- Position
- Below the diagonal: ui.execution.image uses a module listed above it, which is the healthy direction.
32→1 ui.execution.pty uses render.properties✕
- Connections
- 4 pairs of types, where a type in ui.execution.pty uses a type in render.properties.
- The types involved
presenterm.ui.execution.pty.Inner→presenterm.render.properties.WindowSizepresenterm.ui.execution.pty.OperationPollable→presenterm.render.properties.WindowSizepresenterm.ui.execution.pty.PtySnippetOutputOperation→presenterm.render.properties.WindowSizepresenterm.ui.execution.pty.RunPtySnippetTrigger→presenterm.render.properties.WindowSize
- Direction
- ui.execution.pty uses render.properties, so a change to render.properties can break ui.execution.pty, while a change to ui.execution.pty can't break render.properties.
- Position
- Below the diagonal: ui.execution.pty uses a module listed above it, which is the healthy direction.
32→3 ui.execution.pty uses presentation.builder.sources✕
- Connections
- 1 pair of types, where a type in ui.execution.pty uses a type in presentation.builder.sources.
- The types involved
presenterm.ui.execution.pty.PtySnippetHandle→presenterm.presentation.builder.sources.Inner
- Direction
- ui.execution.pty uses presentation.builder.sources, so a change to presentation.builder.sources can break ui.execution.pty, while a change to ui.execution.pty can't break presentation.builder.sources.
- Position
- Below the diagonal: ui.execution.pty uses a module listed above it, which is the healthy direction.
32→12 ui.execution.pty uses theme.clean✕
- Connections
- 1 pair of types, where a type in ui.execution.pty uses a type in theme.clean.
- The types involved
presenterm.ui.execution.pty.PtySnippetOutputOperation→presenterm.theme.clean.PtyOutputBlockStyle
- Direction
- ui.execution.pty uses theme.clean, so a change to theme.clean can break ui.execution.pty, while a change to ui.execution.pty can't break theme.clean.
- Position
- Below the diagonal: ui.execution.pty uses a module listed above it, which is the healthy direction.
32→13 ui.execution.pty uses markdown.text_style✕
- Connections
- 1 pair of types, where a type in ui.execution.pty uses a type in markdown.text_style.
- The types involved
presenterm.ui.execution.pty.pty$module→presenterm.markdown.text_style.Color
- Direction
- ui.execution.pty uses markdown.text_style, so a change to markdown.text_style can break ui.execution.pty, while a change to ui.execution.pty can't break markdown.text_style.
- Position
- Below the diagonal: ui.execution.pty uses a module listed above it, which is the healthy direction.
32→14 ui.execution.pty uses markdown.elements✕
- Connections
- 1 pair of types, where a type in ui.execution.pty uses a type in markdown.elements.
- The types involved
presenterm.ui.execution.pty.PtySnippetOutputOperation→presenterm.markdown.elements.Line
- Direction
- ui.execution.pty uses markdown.elements, so a change to markdown.elements can break ui.execution.pty, while a change to ui.execution.pty can't break markdown.elements.
- Position
- Below the diagonal: ui.execution.pty uses a module listed above it, which is the healthy direction.
32→21 ui.execution.pty uses render.operation✕
- Connections
- 11 pairs of types, where a type in ui.execution.pty uses a type in render.operation.
- The types involved
presenterm.ui.execution.pty.Inner→presenterm.render.operation.RenderAsyncStartPolicypresenterm.ui.execution.pty.OperationPollable→presenterm.render.operation.Pollablepresenterm.ui.execution.pty.OperationPollable→presenterm.render.operation.PollableStatepresenterm.ui.execution.pty.PtySnippetHandle→presenterm.render.operation.RenderAsyncStartPolicypresenterm.ui.execution.pty.PtySnippetOutputOperation→presenterm.render.operation.AsRenderOperationspresenterm.ui.execution.pty.PtySnippetOutputOperation→presenterm.render.operation.RenderAsyncpresenterm.ui.execution.pty.PtySnippetOutputOperation→presenterm.render.operation.RenderOperationpresenterm.ui.execution.pty.RunPtySnippetTrigger→presenterm.render.operation.AsRenderOperationspresenterm.ui.execution.pty.RunPtySnippetTrigger→presenterm.render.operation.RenderAsyncpresenterm.ui.execution.pty.RunPtySnippetTrigger→presenterm.render.operation.RenderAsyncStartPolicypresenterm.ui.execution.pty.RunPtySnippetTrigger→presenterm.render.operation.RenderOperation
- Direction
- ui.execution.pty uses render.operation, so a change to render.operation can break ui.execution.pty, while a change to ui.execution.pty can't break render.operation.
- Position
- Below the diagonal: ui.execution.pty uses a module listed above it, which is the healthy direction.
32→27 ui.execution.pty uses code.snippet✕
- Connections
- 3 pairs of types, where a type in ui.execution.pty uses a type in code.snippet.
- The types involved
presenterm.ui.execution.pty.Inner→presenterm.code.snippet.Snippetpresenterm.ui.execution.pty.PtySnippetHandle→presenterm.code.snippet.PtyArgspresenterm.ui.execution.pty.PtySnippetHandle→presenterm.code.snippet.Snippet
- Direction
- ui.execution.pty uses code.snippet, so a change to code.snippet can break ui.execution.pty, while a change to ui.execution.pty can't break code.snippet.
- Position
- Below the diagonal: ui.execution.pty uses a module listed above it, which is the healthy direction.
32→29 ui.execution.pty uses code.execute✕
- Connections
- 5 pairs of types, where a type in ui.execution.pty uses a type in code.execute.
- The types involved
presenterm.ui.execution.pty.Inner→presenterm.code.execute.LanguageSnippetExecutorpresenterm.ui.execution.pty.OperationPollable→presenterm.code.execute.PtySnippetContextpresenterm.ui.execution.pty.PtyMaster→presenterm.code.execute.PtySnippetContextpresenterm.ui.execution.pty.PtySnippetHandle→presenterm.code.execute.LanguageSnippetExecutorpresenterm.ui.execution.pty.PtySnippetHandle→presenterm.code.execute.ProcessStatus
- Direction
- ui.execution.pty uses code.execute, so a change to code.execute can break ui.execution.pty, while a change to ui.execution.pty can't break code.execute.
- Position
- Below the diagonal: ui.execution.pty uses a module listed above it, which is the healthy direction.
32→30 ui.execution.pty uses ui.execution.acquire_terminal✕
- Connections
- 1 pair of types, where a type in ui.execution.pty uses a type in ui.execution.acquire_terminal.
- The types involved
presenterm.ui.execution.pty.Inner→presenterm.ui.execution.acquire_terminal.State
- Direction
- ui.execution.pty uses ui.execution.acquire_terminal, so a change to ui.execution.acquire_terminal can break ui.execution.pty, while a change to ui.execution.pty can't break ui.execution.acquire_terminal.
- Position
- Below the diagonal: ui.execution.pty uses a module listed above it, which is the healthy direction.
33→1 ui.execution.output uses render.properties✕
- Connections
- 3 pairs of types, where a type in ui.execution.output uses a type in render.properties.
- The types involved
presenterm.ui.execution.output.ExecIndicator→presenterm.render.properties.WindowSizepresenterm.ui.execution.output.RunSnippetTrigger→presenterm.render.properties.WindowSizepresenterm.ui.execution.output.SnippetOutputOperation→presenterm.render.properties.WindowSize
- Direction
- ui.execution.output uses render.properties, so a change to render.properties can break ui.execution.output, while a change to ui.execution.output can't break render.properties.
- Position
- Below the diagonal: ui.execution.output uses a module listed above it, which is the healthy direction.
33→3 ui.execution.output uses presentation.builder.sources✕
- Connections
- 3 pairs of types, where a type in ui.execution.output uses a type in presentation.builder.sources.
- The types involved
presenterm.ui.execution.output.OperationPollable→presenterm.presentation.builder.sources.Innerpresenterm.ui.execution.output.RunSnippetTrigger→presenterm.presentation.builder.sources.Innerpresenterm.ui.execution.output.SnippetHandle→presenterm.presentation.builder.sources.Inner
- Direction
- ui.execution.output uses presentation.builder.sources, so a change to presentation.builder.sources can break ui.execution.output, while a change to ui.execution.output can't break presentation.builder.sources.
- Position
- Below the diagonal: ui.execution.output uses a module listed above it, which is the healthy direction.
33→12 ui.execution.output uses theme.clean✕
- Connections
- 5 pairs of types, where a type in ui.execution.output uses a type in theme.clean.
- The types involved
presenterm.ui.execution.output.ExecIndicator→presenterm.theme.clean.ExecutionStatusBlockStylepresenterm.ui.execution.output.ExecIndicatorStyle→presenterm.theme.clean.Alignmentpresenterm.ui.execution.output.ExecIndicatorStyle→presenterm.theme.clean.ExecutionStatusBlockStylepresenterm.ui.execution.output.SnippetOutputOperation→presenterm.theme.clean.Alignmentpresenterm.ui.execution.output.SnippetOutputOperation→presenterm.theme.clean.ExecutionOutputBlockStyle
- Direction
- ui.execution.output uses theme.clean, so a change to theme.clean can break ui.execution.output, while a change to ui.execution.output can't break theme.clean.
- Position
- Below the diagonal: ui.execution.output uses a module listed above it, which is the healthy direction.
33→13 ui.execution.output uses markdown.text_style✕
- Connections
- 1 pair of types, where a type in ui.execution.output uses a type in markdown.text_style.
- The types involved
presenterm.ui.execution.output.SnippetOutputOperation→presenterm.markdown.text_style.Colors
- Direction
- ui.execution.output uses markdown.text_style, so a change to markdown.text_style can break ui.execution.output, while a change to ui.execution.output can't break markdown.text_style.
- Position
- Below the diagonal: ui.execution.output uses a module listed above it, which is the healthy direction.
33→14 ui.execution.output uses markdown.elements✕
- Connections
- 1 pair of types, where a type in ui.execution.output uses a type in markdown.elements.
- The types involved
presenterm.ui.execution.output.Inner→presenterm.markdown.elements.Line
- Direction
- ui.execution.output uses markdown.elements, so a change to markdown.elements can break ui.execution.output, while a change to ui.execution.output can't break markdown.elements.
- Position
- Below the diagonal: ui.execution.output uses a module listed above it, which is the healthy direction.
33→21 ui.execution.output uses render.operation✕
- Connections
- 12 pairs of types, where a type in ui.execution.output uses a type in render.operation.
- The types involved
presenterm.ui.execution.output.ExecIndicator→presenterm.render.operation.AsRenderOperationspresenterm.ui.execution.output.ExecIndicator→presenterm.render.operation.RenderOperationpresenterm.ui.execution.output.Inner→presenterm.render.operation.RenderAsyncStartPolicypresenterm.ui.execution.output.OperationPollable→presenterm.render.operation.Pollablepresenterm.ui.execution.output.OperationPollable→presenterm.render.operation.PollableStatepresenterm.ui.execution.output.RunSnippetTrigger→presenterm.render.operation.AsRenderOperationspresenterm.ui.execution.output.RunSnippetTrigger→presenterm.render.operation.RenderAsyncpresenterm.ui.execution.output.RunSnippetTrigger→presenterm.render.operation.RenderAsyncStartPolicypresenterm.ui.execution.output.RunSnippetTrigger→presenterm.render.operation.RenderOperationpresenterm.ui.execution.output.SnippetHandle→presenterm.render.operation.RenderAsyncStartPolicypresenterm.ui.execution.output.SnippetOutputOperation→presenterm.render.operation.AsRenderOperationspresenterm.ui.execution.output.SnippetOutputOperation→presenterm.render.operation.RenderOperation
- Direction
- ui.execution.output uses render.operation, so a change to render.operation can break ui.execution.output, while a change to ui.execution.output can't break render.operation.
- Position
- Below the diagonal: ui.execution.output uses a module listed above it, which is the healthy direction.
33→27 ui.execution.output uses code.snippet✕
- Connections
- 2 pairs of types, where a type in ui.execution.output uses a type in code.snippet.
- The types involved
presenterm.ui.execution.output.Inner→presenterm.code.snippet.Snippetpresenterm.ui.execution.output.SnippetHandle→presenterm.code.snippet.Snippet
- Direction
- ui.execution.output uses code.snippet, so a change to code.snippet can break ui.execution.output, while a change to ui.execution.output can't break code.snippet.
- Position
- Below the diagonal: ui.execution.output uses a module listed above it, which is the healthy direction.
33→29 ui.execution.output uses code.execute✕
- Connections
- 4 pairs of types, where a type in ui.execution.output uses a type in code.execute.
- The types involved
presenterm.ui.execution.output.Inner→presenterm.code.execute.LanguageSnippetExecutorpresenterm.ui.execution.output.Inner→presenterm.code.execute.ProcessStatuspresenterm.ui.execution.output.SnippetHandle→presenterm.code.execute.LanguageSnippetExecutorpresenterm.ui.execution.output.WrappedSnippetHandle→presenterm.code.execute.ProcessStatus
- Direction
- ui.execution.output uses code.execute, so a change to code.execute can break ui.execution.output, while a change to ui.execution.output can't break code.execute.
- Position
- Below the diagonal: ui.execution.output uses a module listed above it, which is the healthy direction.
33→30 ui.execution.output uses ui.execution.acquire_terminal✕
- Connections
- 1 pair of types, where a type in ui.execution.output uses a type in ui.execution.acquire_terminal.
- The types involved
presenterm.ui.execution.output.Inner→presenterm.ui.execution.acquire_terminal.State
- Direction
- ui.execution.output uses ui.execution.acquire_terminal, so a change to ui.execution.acquire_terminal can break ui.execution.output, while a change to ui.execution.output can't break ui.execution.acquire_terminal.
- Position
- Below the diagonal: ui.execution.output uses a module listed above it, which is the healthy direction.
33→32 ui.execution.output uses ui.execution.pty✕
- Connections
- 1 pair of types, where a type in ui.execution.output uses a type in ui.execution.pty.
- The types involved
presenterm.ui.execution.output.WrappedSnippetHandle→presenterm.ui.execution.pty.PtySnippetHandle
- Direction
- ui.execution.output uses ui.execution.pty, so a change to ui.execution.pty can break ui.execution.output, while a change to ui.execution.output can't break ui.execution.pty.
- Position
- Below the diagonal: ui.execution.output uses a module listed above it, which is the healthy direction.
34→2 presentation.builder uses config✕
- Connections
- 2 pairs of types, where a type in presentation.builder uses a type in config.
- The types involved
presenterm.presentation.builder.PresentationBuilder→presenterm.config.KeyBindingsConfigpresenterm.presentation.builder.PresentationBuilderOptions→presenterm.config.OptionsConfig
- Direction
- presentation.builder uses config, so a change to config can break presentation.builder, while a change to presentation.builder can't break config.
- Position
- Below the diagonal: presentation.builder uses a module listed above it, which is the healthy direction.
34→3 presentation.builder uses presentation.builder.sources✕
- Connections
- 1 pair of types, where a type in presentation.builder uses a type in presentation.builder.sources.
- The types involved
presenterm.presentation.builder.PresentationBuilder→presenterm.presentation.builder.sources.MarkdownSources
- Direction
- presentation.builder uses presentation.builder.sources, so a change to presentation.builder.sources can break presentation.builder, while a change to presentation.builder can't break presentation.builder.sources.
- Position
- Below the diagonal: presentation.builder uses a module listed above it, which is the healthy direction.
34→7 presentation.builder uses terminal.image✕
- Connections
- 1 pair of types, where a type in presentation.builder uses a type in terminal.image.
- The types involved
presenterm.presentation.builder.PresentationBuilder→presenterm.terminal.image.Image
- Direction
- presentation.builder uses terminal.image, so a change to terminal.image can break presentation.builder, while a change to presentation.builder can't break terminal.image.
- Position
- Below the diagonal: presentation.builder uses a module listed above it, which is the healthy direction.
34→9 presentation.builder uses terminal.image.printer✕
- Connections
- 1 pair of types, where a type in presentation.builder uses a type in terminal.image.printer.
- The types involved
presenterm.presentation.builder.PresentationBuilder→presenterm.terminal.image.printer.ImageRegistry
- Direction
- presentation.builder uses terminal.image.printer, so a change to terminal.image.printer can break presentation.builder, while a change to presentation.builder can't break terminal.image.printer.
- Position
- Below the diagonal: presentation.builder uses a module listed above it, which is the healthy direction.
34→10 presentation.builder uses resource✕
- Connections
- 2 pairs of types, where a type in presentation.builder uses a type in resource.
- The types involved
presenterm.presentation.builder.PresentationBuilder→presenterm.resource.ResourceBasePathpresenterm.presentation.builder.PresentationBuilder→presenterm.resource.Resources
- Direction
- presentation.builder uses resource, so a change to resource can break presentation.builder, while a change to presentation.builder can't break resource.
- Position
- Below the diagonal: presentation.builder uses a module listed above it, which is the healthy direction.
34→12 presentation.builder uses theme.clean✕
- Connections
- 6 pairs of types, where a type in presentation.builder uses a type in theme.clean.
- The types involved
presenterm.presentation.builder.PresentationBuilder→presenterm.theme.clean.Alignmentpresenterm.presentation.builder.PresentationBuilder→presenterm.theme.clean.CodeBlockStylepresenterm.presentation.builder.PresentationBuilder→presenterm.theme.clean.ElementTypepresenterm.presentation.builder.PresentationBuilder→presenterm.theme.clean.PresentationThemepresenterm.presentation.builder.PresentationBuilderOptions→presenterm.theme.clean.ThemeOptionspresenterm.presentation.builder.SlideState→presenterm.theme.clean.Alignment
- Direction
- presentation.builder uses theme.clean, so a change to theme.clean can break presentation.builder, while a change to presentation.builder can't break theme.clean.
- Position
- Below the diagonal: presentation.builder uses a module listed above it, which is the healthy direction.
34→13 presentation.builder uses markdown.text_style✕
- Connections
- 2 pairs of types, where a type in presentation.builder uses a type in markdown.text_style.
- The types involved
presenterm.presentation.builder.PresentationBuilder→presenterm.markdown.text_style.Colorspresenterm.presentation.builder.PresentationBuilder→presenterm.markdown.text_style.TextStyle
- Direction
- presentation.builder uses markdown.text_style, so a change to markdown.text_style can break presentation.builder, while a change to presentation.builder can't break markdown.text_style.
- Position
- Below the diagonal: presentation.builder uses a module listed above it, which is the healthy direction.
34→14 presentation.builder uses markdown.elements✕
- Connections
- 7 pairs of types, where a type in presentation.builder uses a type in markdown.elements.
- The types involved
presenterm.presentation.builder.PresentationBuilder→presenterm.markdown.elements.Linepresenterm.presentation.builder.PresentationBuilder→presenterm.markdown.elements.ListItempresenterm.presentation.builder.PresentationBuilder→presenterm.markdown.elements.MarkdownElementpresenterm.presentation.builder.PresentationBuilder→presenterm.markdown.elements.SourcePositionpresenterm.presentation.builder.PresentationBuilder→presenterm.markdown.elements.Tablepresenterm.presentation.builder.PresentationBuilder→presenterm.markdown.elements.Textpresenterm.presentation.builder.SlideState→presenterm.markdown.elements.Line
- Direction
- presentation.builder uses markdown.elements, so a change to markdown.elements can break presentation.builder, while a change to presentation.builder can't break markdown.elements.
- Position
- Below the diagonal: presentation.builder uses a module listed above it, which is the healthy direction.
34→16 presentation.builder uses code.highlighting✕
- Connections
- 2 pairs of types, where a type in presentation.builder uses a type in code.highlighting.
- The types involved
presenterm.presentation.builder.PresentationBuilder→presenterm.code.highlighting.SnippetHighlighterpresenterm.presentation.builder.Themes→presenterm.code.highlighting.HighlightThemeSet
- Direction
- presentation.builder uses code.highlighting, so a change to code.highlighting can break presentation.builder, while a change to presentation.builder can't break code.highlighting.
- Position
- Below the diagonal: presentation.builder uses a module listed above it, which is the healthy direction.
34→17 presentation.builder uses markdown.parse✕
- Connections
- 1 pair of types, where a type in presentation.builder uses a type in markdown.parse.
- The types involved
presenterm.presentation.builder.PresentationBuilder→presenterm.markdown.parse.MarkdownParser
- Direction
- presentation.builder uses markdown.parse, so a change to markdown.parse can break presentation.builder, while a change to presentation.builder can't break markdown.parse.
- Position
- Below the diagonal: presentation.builder uses a module listed above it, which is the healthy direction.
34→20 presentation.builder uses ui.modals✕
- Connections
- 1 pair of types, where a type in presentation.builder uses a type in ui.modals.
- The types involved
presenterm.presentation.builder.PresentationBuilder→presenterm.ui.modals.IndexBuilder
- Direction
- presentation.builder uses ui.modals, so a change to ui.modals can break presentation.builder, while a change to presentation.builder can't break ui.modals.
- Position
- Below the diagonal: presentation.builder uses a module listed above it, which is the healthy direction.
34→21 presentation.builder uses render.operation✕
- Connections
- 1 pair of types, where a type in presentation.builder uses a type in render.operation.
- The types involved
presenterm.presentation.builder.PresentationBuilder→presenterm.render.operation.RenderOperation
- Direction
- presentation.builder uses render.operation, so a change to render.operation can break presentation.builder, while a change to presentation.builder can't break render.operation.
- Position
- Below the diagonal: presentation.builder uses a module listed above it, which is the healthy direction.
34→22 presentation.builder uses presentation✕
- Connections
- 5 pairs of types, where a type in presentation.builder uses a type in presentation.
- The types involved
presenterm.presentation.builder.PresentationBuilder→presenterm.presentation.PresentationMetadatapresenterm.presentation.builder.PresentationBuilder→presenterm.presentation.PresentationStatepresenterm.presentation.builder.PresentationBuilder→presenterm.presentation.PresentationThemeMetadatapresenterm.presentation.builder.PresentationBuilder→presenterm.presentation.SlideBuilderpresenterm.presentation.builder.PresentationBuilder→presenterm.presentation.SlideChunk
- Direction
- presentation.builder uses presentation, so a change to presentation can break presentation.builder, while a change to presentation.builder can't break presentation.
- Position
- Below the diagonal: presentation.builder uses a module listed above it, which is the healthy direction.
34→23 presentation.builder uses presentation.builder.images✕
- Connections
- 2 pairs of types, where a type in presentation.builder uses a type in presentation.builder.images.
- The types involved
presenterm.presentation.builder.PresentationBuilder→presenterm.presentation.builder.images.ImageAttributespresenterm.presentation.builder.SlideState→presenterm.presentation.builder.images.BackgroundImageSlot
- Direction
- presentation.builder uses presentation.builder.images, so a change to presentation.builder.images can break presentation.builder, while a change to presentation.builder can't break presentation.builder.images.
- Position
- Below the diagonal: presentation.builder uses a module listed above it, which is the healthy direction.
34→24 presentation.builder uses third_party✕
- Connections
- 1 pair of types, where a type in presentation.builder uses a type in third_party.
- The types involved
presenterm.presentation.builder.PresentationBuilder→presenterm.third_party.ThirdPartyRender
- Direction
- presentation.builder uses third_party, so a change to third_party can break presentation.builder, while a change to presentation.builder can't break third_party.
- Position
- Below the diagonal: presentation.builder uses a module listed above it, which is the healthy direction.
34→25 presentation.builder uses ui.execution.disabled✕
- Connections
- 1 pair of types, where a type in presentation.builder uses a type in ui.execution.disabled.
- The types involved
presenterm.presentation.builder.PresentationBuilder→presenterm.ui.execution.disabled.ExecutionType
- Direction
- presentation.builder uses ui.execution.disabled, so a change to ui.execution.disabled can break presentation.builder, while a change to presentation.builder can't break ui.execution.disabled.
- Position
- Below the diagonal: presentation.builder uses a module listed above it, which is the healthy direction.
34→26 presentation.builder uses ui.footer✕
- Connections
- 1 pair of types, where a type in presentation.builder uses a type in ui.footer.
- The types involved
presenterm.presentation.builder.PresentationBuilder→presenterm.ui.footer.FooterVariables
- Direction
- presentation.builder uses ui.footer, so a change to ui.footer can break presentation.builder, while a change to presentation.builder can't break ui.footer.
- Position
- Below the diagonal: presentation.builder uses a module listed above it, which is the healthy direction.
34→27 presentation.builder uses code.snippet✕
- Connections
- 5 pairs of types, where a type in presentation.builder uses a type in code.snippet.
- The types involved
presenterm.presentation.builder.PresentationBuilder→presenterm.code.snippet.PtyArgspresenterm.presentation.builder.PresentationBuilder→presenterm.code.snippet.Snippetpresenterm.presentation.builder.PresentationBuilder→presenterm.code.snippet.SnippetExecArgspresenterm.presentation.builder.PresentationBuilder→presenterm.code.snippet.SnippetLinepresenterm.presentation.builder.PresentationBuilderOptions→presenterm.code.snippet.SnippetLanguage
- Direction
- presentation.builder uses code.snippet, so a change to code.snippet can break presentation.builder, while a change to presentation.builder can't break code.snippet.
- Position
- Below the diagonal: presentation.builder uses a module listed above it, which is the healthy direction.
34→29 presentation.builder uses code.execute✕
- Connections
- 2 pairs of types, where a type in presentation.builder uses a type in code.execute.
- The types involved
presenterm.presentation.builder.PresentationBuilder→presenterm.code.execute.LanguageSnippetExecutorpresenterm.presentation.builder.PresentationBuilder→presenterm.code.execute.SnippetExecutor
- Direction
- presentation.builder uses code.execute, so a change to code.execute can break presentation.builder, while a change to presentation.builder can't break code.execute.
- Position
- Below the diagonal: presentation.builder uses a module listed above it, which is the healthy direction.
34→32 presentation.builder uses ui.execution.pty✕
- Connections
- 1 pair of types, where a type in presentation.builder uses a type in ui.execution.pty.
- The types involved
presenterm.presentation.builder.PresentationBuilder→presenterm.ui.execution.pty.PtySnippetHandle
- Direction
- presentation.builder uses ui.execution.pty, so a change to ui.execution.pty can break presentation.builder, while a change to presentation.builder can't break ui.execution.pty.
- Position
- Below the diagonal: presentation.builder uses a module listed above it, which is the healthy direction.
34→33 presentation.builder uses ui.execution.output✕
- Connections
- 2 pairs of types, where a type in presentation.builder uses a type in ui.execution.output.
- The types involved
presenterm.presentation.builder.PresentationBuilder→presenterm.ui.execution.output.SnippetHandlepresenterm.presentation.builder.PresentationBuilder→presenterm.ui.execution.output.WrappedSnippetHandle
- Direction
- presentation.builder uses ui.execution.output, so a change to ui.execution.output can break presentation.builder, while a change to presentation.builder can't break ui.execution.output.
- Position
- Below the diagonal: presentation.builder uses a module listed above it, which is the healthy direction.
35→1 export.exporter uses render.properties✕
- Connections
- 2 pairs of types, where a type in export.exporter uses a type in render.properties.
- The types involved
presenterm.export.exporter.Exporter→presenterm.render.properties.WindowSizepresenterm.export.exporter.RenderMany→presenterm.render.properties.WindowSize
- Direction
- export.exporter uses render.properties, so a change to render.properties can break export.exporter, while a change to export.exporter can't break render.properties.
- Position
- Below the diagonal: export.exporter uses a module listed above it, which is the healthy direction.
35→2 export.exporter uses config✕
- Connections
- 3 pairs of types, where a type in export.exporter uses a type in config.
- The types involved
presenterm.export.exporter.Exporter→presenterm.config.PauseExportPolicypresenterm.export.exporter.Exporter→presenterm.config.PdfExportConfigpresenterm.export.exporter.Exporter→presenterm.config.SnippetsExportPolicy
- Direction
- export.exporter uses config, so a change to config can break export.exporter, while a change to export.exporter can't break config.
- Position
- Below the diagonal: export.exporter uses a module listed above it, which is the healthy direction.
35→9 export.exporter uses terminal.image.printer✕
- Connections
- 1 pair of types, where a type in export.exporter uses a type in terminal.image.printer.
- The types involved
presenterm.export.exporter.Exporter→presenterm.terminal.image.printer.ImagePrinter
- Direction
- export.exporter uses terminal.image.printer, so a change to terminal.image.printer can break export.exporter, while a change to export.exporter can't break terminal.image.printer.
- Position
- Below the diagonal: export.exporter uses a module listed above it, which is the healthy direction.
35→10 export.exporter uses resource✕
- Connections
- 1 pair of types, where a type in export.exporter uses a type in resource.
- The types involved
presenterm.export.exporter.Exporter→presenterm.resource.Resources
- Direction
- export.exporter uses resource, so a change to resource can break export.exporter, while a change to export.exporter can't break resource.
- Position
- Below the diagonal: export.exporter uses a module listed above it, which is the healthy direction.
35→12 export.exporter uses theme.clean✕
- Connections
- 1 pair of types, where a type in export.exporter uses a type in theme.clean.
- The types involved
presenterm.export.exporter.Exporter→presenterm.theme.clean.PresentationTheme
- Direction
- export.exporter uses theme.clean, so a change to theme.clean can break export.exporter, while a change to export.exporter can't break theme.clean.
- Position
- Below the diagonal: export.exporter uses a module listed above it, which is the healthy direction.
35→17 export.exporter uses markdown.parse✕
- Connections
- 1 pair of types, where a type in export.exporter uses a type in markdown.parse.
- The types involved
presenterm.export.exporter.Exporter→presenterm.markdown.parse.MarkdownParser
- Direction
- export.exporter uses markdown.parse, so a change to markdown.parse can break export.exporter, while a change to export.exporter can't break markdown.parse.
- Position
- Below the diagonal: export.exporter uses a module listed above it, which is the healthy direction.
35→21 export.exporter uses render.operation✕
- Connections
- 2 pairs of types, where a type in export.exporter uses a type in render.operation.
- The types involved
presenterm.export.exporter.RenderMany→presenterm.render.operation.AsRenderOperationspresenterm.export.exporter.RenderMany→presenterm.render.operation.RenderOperation
- Direction
- export.exporter uses render.operation, so a change to render.operation can break export.exporter, while a change to export.exporter can't break render.operation.
- Position
- Below the diagonal: export.exporter uses a module listed above it, which is the healthy direction.
35→22 export.exporter uses presentation✕
- Connections
- 1 pair of types, where a type in export.exporter uses a type in presentation.
- The types involved
presenterm.export.exporter.Exporter→presenterm.presentation.Presentation
- Direction
- export.exporter uses presentation, so a change to presentation can break export.exporter, while a change to export.exporter can't break presentation.
- Position
- Below the diagonal: export.exporter uses a module listed above it, which is the healthy direction.
35→24 export.exporter uses third_party✕
- Connections
- 1 pair of types, where a type in export.exporter uses a type in third_party.
- The types involved
presenterm.export.exporter.Exporter→presenterm.third_party.ThirdPartyRender
- Direction
- export.exporter uses third_party, so a change to third_party can break export.exporter, while a change to export.exporter can't break third_party.
- Position
- Below the diagonal: export.exporter uses a module listed above it, which is the healthy direction.
35→28 export.exporter uses export.output✕
- Connections
- 1 pair of types, where a type in export.exporter uses a type in export.output.
- The types involved
presenterm.export.exporter.Exporter→presenterm.export.output.OutputFormat
- Direction
- export.exporter uses export.output, so a change to export.output can break export.exporter, while a change to export.exporter can't break export.output.
- Position
- Below the diagonal: export.exporter uses a module listed above it, which is the healthy direction.
35→29 export.exporter uses code.execute✕
- Connections
- 1 pair of types, where a type in export.exporter uses a type in code.execute.
- The types involved
presenterm.export.exporter.Exporter→presenterm.code.execute.SnippetExecutor
- Direction
- export.exporter uses code.execute, so a change to code.execute can break export.exporter, while a change to export.exporter can't break code.execute.
- Position
- Below the diagonal: export.exporter uses a module listed above it, which is the healthy direction.
35→34 export.exporter uses presentation.builder✕
- Connections
- 2 pairs of types, where a type in export.exporter uses a type in presentation.builder.
- The types involved
presenterm.export.exporter.Exporter→presenterm.presentation.builder.PresentationBuilderOptionspresenterm.export.exporter.Exporter→presenterm.presentation.builder.Themes
- Direction
- export.exporter uses presentation.builder, so a change to presentation.builder can break export.exporter, while a change to export.exporter can't break presentation.builder.
- Position
- Below the diagonal: export.exporter uses a module listed above it, which is the healthy direction.
36→1 render.engine uses render.properties✕
- Connections
- 3 pairs of types, where a type in render.engine uses a type in render.properties.
- The types involved
presenterm.render.engine.RenderEngine→presenterm.render.properties.CursorPositionpresenterm.render.engine.RenderEngine→presenterm.render.properties.WindowSizepresenterm.render.engine.WindowRect→presenterm.render.properties.WindowSize
- Direction
- render.engine uses render.properties, so a change to render.properties can break render.engine, while a change to render.engine can't break render.properties.
- Position
- Below the diagonal: render.engine uses a module listed above it, which is the healthy direction.
36→2 render.engine uses config✕
- Connections
- 2 pairs of types, where a type in render.engine uses a type in config.
- The types involved
presenterm.render.engine.MaxSize→presenterm.config.MaxColumnsAlignmentpresenterm.render.engine.MaxSize→presenterm.config.MaxRowsAlignment
- Direction
- render.engine uses config, so a change to config can break render.engine, while a change to render.engine can't break config.
- Position
- Below the diagonal: render.engine uses a module listed above it, which is the healthy direction.
36→4 render.engine uses theme.raw✕
- Connections
- 1 pair of types, where a type in render.engine uses a type in theme.raw.
- The types involved
presenterm.render.engine.RenderEngine→presenterm.theme.raw.Margin
- Direction
- render.engine uses theme.raw, so a change to theme.raw can break render.engine, while a change to render.engine can't break theme.raw.
- Position
- Below the diagonal: render.engine uses a module listed above it, which is the healthy direction.
36→7 render.engine uses terminal.image✕
- Connections
- 1 pair of types, where a type in render.engine uses a type in terminal.image.
- The types involved
presenterm.render.engine.RenderEngine→presenterm.terminal.image.Image
- Direction
- render.engine uses terminal.image, so a change to terminal.image can break render.engine, while a change to render.engine can't break terminal.image.
- Position
- Below the diagonal: render.engine uses a module listed above it, which is the healthy direction.
36→12 render.engine uses theme.clean✕
- Connections
- 1 pair of types, where a type in render.engine uses a type in theme.clean.
- The types involved
presenterm.render.engine.RenderEngine→presenterm.theme.clean.Alignment
- Direction
- render.engine uses theme.clean, so a change to theme.clean can break render.engine, while a change to render.engine can't break theme.clean.
- Position
- Below the diagonal: render.engine uses a module listed above it, which is the healthy direction.
36→13 render.engine uses markdown.text_style✕
- Connections
- 1 pair of types, where a type in render.engine uses a type in markdown.text_style.
- The types involved
presenterm.render.engine.RenderEngine→presenterm.markdown.text_style.Colors
- Direction
- render.engine uses markdown.text_style, so a change to markdown.text_style can break render.engine, while a change to render.engine can't break markdown.text_style.
- Position
- Below the diagonal: render.engine uses a module listed above it, which is the healthy direction.
36→18 render.engine uses markdown.text✕
- Connections
- 1 pair of types, where a type in render.engine uses a type in markdown.text.
- The types involved
presenterm.render.engine.RenderEngine→presenterm.markdown.text.WeightedLine
- Direction
- render.engine uses markdown.text, so a change to markdown.text can break render.engine, while a change to render.engine can't break markdown.text.
- Position
- Below the diagonal: render.engine uses a module listed above it, which is the healthy direction.
36→21 render.engine uses render.operation✕
- Connections
- 5 pairs of types, where a type in render.engine uses a type in render.operation.
- The types involved
presenterm.render.engine.RenderEngine→presenterm.render.operation.BlockLinepresenterm.render.engine.RenderEngine→presenterm.render.operation.ImageRenderPropertiespresenterm.render.engine.RenderEngine→presenterm.render.operation.LayoutGridpresenterm.render.engine.RenderEngine→presenterm.render.operation.MarginPropertiespresenterm.render.engine.RenderEngine→presenterm.render.operation.RenderOperation
- Direction
- render.engine uses render.operation, so a change to render.operation can break render.engine, while a change to render.engine can't break render.operation.
- Position
- Below the diagonal: render.engine uses a module listed above it, which is the healthy direction.
36→24 render.engine uses third_party✕
- Connections
- 1 pair of types, where a type in render.engine uses a type in third_party.
- The types involved
presenterm.render.engine.RenderEngine→presenterm.third_party.RenderResult
- Direction
- render.engine uses third_party, so a change to third_party can break render.engine, while a change to render.engine can't break third_party.
- Position
- Below the diagonal: render.engine uses a module listed above it, which is the healthy direction.
36→34 render.engine uses presentation.builder✕
- Connections
- 1 pair of types, where a type in render.engine uses a type in presentation.builder.
- The types involved
presenterm.render.engine.RenderEngine→presenterm.presentation.builder.LayoutState
- Direction
- render.engine uses presentation.builder, so a change to presentation.builder can break render.engine, while a change to render.engine can't break presentation.builder.
- Position
- Below the diagonal: render.engine uses a module listed above it, which is the healthy direction.
37→1 render uses render.properties✕
- Connections
- 2 pairs of types, where a type in render uses a type in render.properties.
- The types involved
presenterm.render.RenderErrorOperation→presenterm.render.properties.WindowSizepresenterm.render.TerminalDrawer→presenterm.render.properties.WindowSize
- Direction
- render uses render.properties, so a change to render.properties can break render, while a change to render can't break render.properties.
- Position
- Below the diagonal: render uses a module listed above it, which is the healthy direction.
37→8 render uses terminal.printer✕
- Connections
- 1 pair of types, where a type in render uses a type in terminal.printer.
- The types involved
presenterm.render.TerminalDrawer→presenterm.terminal.printer.Terminal
- Direction
- render uses terminal.printer, so a change to terminal.printer can break render, while a change to render can't break terminal.printer.
- Position
- Below the diagonal: render uses a module listed above it, which is the healthy direction.
37→9 render uses terminal.image.printer✕
- Connections
- 1 pair of types, where a type in render uses a type in terminal.image.printer.
- The types involved
presenterm.render.TerminalDrawer→presenterm.terminal.image.printer.ImagePrinter
- Direction
- render uses terminal.image.printer, so a change to terminal.image.printer can break render, while a change to render can't break terminal.image.printer.
- Position
- Below the diagonal: render uses a module listed above it, which is the healthy direction.
37→18 render uses markdown.text✕
- Connections
- 1 pair of types, where a type in render uses a type in markdown.text.
- The types involved
presenterm.render.RenderErrorOperation→presenterm.markdown.text.WeightedLine
- Direction
- render uses markdown.text, so a change to markdown.text can break render, while a change to render can't break markdown.text.
- Position
- Below the diagonal: render uses a module listed above it, which is the healthy direction.
37→21 render uses render.operation✕
- Connections
- 2 pairs of types, where a type in render uses a type in render.operation.
- The types involved
presenterm.render.RenderErrorOperation→presenterm.render.operation.AsRenderOperationspresenterm.render.RenderErrorOperation→presenterm.render.operation.RenderOperation
- Direction
- render uses render.operation, so a change to render.operation can break render, while a change to render can't break render.operation.
- Position
- Below the diagonal: render uses a module listed above it, which is the healthy direction.
37→24 render uses third_party✕
- Connections
- 1 pair of types, where a type in render uses a type in third_party.
- The types involved
presenterm.render.TerminalDrawer→presenterm.third_party.RenderResult
- Direction
- render uses third_party, so a change to third_party can break render, while a change to render can't break third_party.
- Position
- Below the diagonal: render uses a module listed above it, which is the healthy direction.
37→36 render uses render.engine✕
- Connections
- 3 pairs of types, where a type in render uses a type in render.engine.
- The types involved
presenterm.render.TerminalDrawer→presenterm.render.engine.RenderEnginepresenterm.render.TerminalDrawer→presenterm.render.engine.RenderEngineOptionspresenterm.render.TerminalDrawerOptions→presenterm.render.engine.MaxSize
- Direction
- render uses render.engine, so a change to render.engine can break render, while a change to render can't break render.engine.
- Position
- Below the diagonal: render uses a module listed above it, which is the healthy direction.
38→1 render.ascii_scaler uses render.properties✕
- Connections
- 1 pair of types, where a type in render.ascii_scaler uses a type in render.properties.
- The types involved
presenterm.render.ascii_scaler.AsciiScaler→presenterm.render.properties.WindowSize
- Direction
- render.ascii_scaler uses render.properties, so a change to render.properties can break render.ascii_scaler, while a change to render.ascii_scaler can't break render.properties.
- Position
- Below the diagonal: render.ascii_scaler uses a module listed above it, which is the healthy direction.
38→7 render.ascii_scaler uses terminal.image✕
- Connections
- 1 pair of types, where a type in render.ascii_scaler uses a type in terminal.image.
- The types involved
presenterm.render.ascii_scaler.ScalableImage→presenterm.terminal.image.Image
- Direction
- render.ascii_scaler uses terminal.image, so a change to terminal.image can break render.ascii_scaler, while a change to render.ascii_scaler can't break terminal.image.
- Position
- Below the diagonal: render.ascii_scaler uses a module listed above it, which is the healthy direction.
38→8 render.ascii_scaler uses terminal.printer✕
- Connections
- 2 pairs of types, where a type in render.ascii_scaler uses a type in terminal.printer.
- The types involved
presenterm.render.ascii_scaler.ImageCollector→presenterm.terminal.printer.TerminalCommandpresenterm.render.ascii_scaler.ImageCollector→presenterm.terminal.printer.TerminalIo
- Direction
- render.ascii_scaler uses terminal.printer, so a change to terminal.printer can break render.ascii_scaler, while a change to render.ascii_scaler can't break terminal.printer.
- Position
- Below the diagonal: render.ascii_scaler uses a module listed above it, which is the healthy direction.
38→22 render.ascii_scaler uses presentation✕
- Connections
- 1 pair of types, where a type in render.ascii_scaler uses a type in presentation.
- The types involved
presenterm.render.ascii_scaler.AsciiScaler→presenterm.presentation.Presentation
- Direction
- render.ascii_scaler uses presentation, so a change to presentation can break render.ascii_scaler, while a change to render.ascii_scaler can't break presentation.
- Position
- Below the diagonal: render.ascii_scaler uses a module listed above it, which is the healthy direction.
38→36 render.ascii_scaler uses render.engine✕
- Connections
- 1 pair of types, where a type in render.ascii_scaler uses a type in render.engine.
- The types involved
presenterm.render.ascii_scaler.AsciiScaler→presenterm.render.engine.RenderEngineOptions
- Direction
- render.ascii_scaler uses render.engine, so a change to render.engine can break render.ascii_scaler, while a change to render.ascii_scaler can't break render.engine.
- Position
- Below the diagonal: render.ascii_scaler uses a module listed above it, which is the healthy direction.
39→1 presenter uses render.properties✕
- Connections
- 1 pair of types, where a type in presenter uses a type in render.properties.
- The types involved
presenterm.presenter.Presenter→presenterm.render.properties.WindowSize
- Direction
- presenter uses render.properties, so a change to render.properties can break presenter, while a change to presenter can't break render.properties.
- Position
- Below the diagonal: presenter uses a module listed above it, which is the healthy direction.
39→2 presenter uses config✕
- Connections
- 3 pairs of types, where a type in presenter uses a type in config.
- The types involved
presenterm.presenter.Presenter→presenterm.config.SlideTransitionConfigpresenterm.presenter.PresenterOptions→presenterm.config.KeyBindingsConfigpresenterm.presenter.PresenterOptions→presenterm.config.SlideTransitionConfig
- Direction
- presenter uses config, so a change to config can break presenter, while a change to presenter can't break config.
- Position
- Below the diagonal: presenter uses a module listed above it, which is the healthy direction.
39→5 presenter uses commands.listener✕
- Connections
- 2 pairs of types, where a type in presenter uses a type in commands.listener.
- The types involved
presenterm.presenter.Presenter→presenterm.commands.listener.Commandpresenterm.presenter.Presenter→presenterm.commands.listener.CommandListener
- Direction
- presenter uses commands.listener, so a change to commands.listener can break presenter, while a change to presenter can't break commands.listener.
- Position
- Below the diagonal: presenter uses a module listed above it, which is the healthy direction.
39→9 presenter uses terminal.image.printer✕
- Connections
- 1 pair of types, where a type in presenter uses a type in terminal.image.printer.
- The types involved
presenterm.presenter.Presenter→presenterm.terminal.image.printer.ImagePrinter
- Direction
- presenter uses terminal.image.printer, so a change to terminal.image.printer can break presenter, while a change to presenter can't break terminal.image.printer.
- Position
- Below the diagonal: presenter uses a module listed above it, which is the healthy direction.
39→10 presenter uses resource✕
- Connections
- 1 pair of types, where a type in presenter uses a type in resource.
- The types involved
presenterm.presenter.Presenter→presenterm.resource.Resources
- Direction
- presenter uses resource, so a change to resource can break presenter, while a change to presenter can't break resource.
- Position
- Below the diagonal: presenter uses a module listed above it, which is the healthy direction.
39→12 presenter uses theme.clean✕
- Connections
- 1 pair of types, where a type in presenter uses a type in theme.clean.
- The types involved
presenterm.presenter.Presenter→presenterm.theme.clean.PresentationTheme
- Direction
- presenter uses theme.clean, so a change to theme.clean can break presenter, while a change to presenter can't break theme.clean.
- Position
- Below the diagonal: presenter uses a module listed above it, which is the healthy direction.
39→15 presenter uses terminal.virt✕
- Connections
- 1 pair of types, where a type in presenter uses a type in terminal.virt.
- The types involved
presenterm.presenter.Presenter→presenterm.terminal.virt.TerminalGrid
- Direction
- presenter uses terminal.virt, so a change to terminal.virt can break presenter, while a change to presenter can't break terminal.virt.
- Position
- Below the diagonal: presenter uses a module listed above it, which is the healthy direction.
39→17 presenter uses markdown.parse✕
- Connections
- 1 pair of types, where a type in presenter uses a type in markdown.parse.
- The types involved
presenterm.presenter.Presenter→presenterm.markdown.parse.MarkdownParser
- Direction
- presenter uses markdown.parse, so a change to markdown.parse can break presenter, while a change to presenter can't break markdown.parse.
- Position
- Below the diagonal: presenter uses a module listed above it, which is the healthy direction.
39→19 presenter uses transitions✕
- Connections
- 1 pair of types, where a type in presenter uses a type in transitions.
- The types involved
presenterm.presenter.Presenter→presenterm.transitions.TransitionDirection
- Direction
- presenter uses transitions, so a change to transitions can break presenter, while a change to presenter can't break transitions.
- Position
- Below the diagonal: presenter uses a module listed above it, which is the healthy direction.
39→22 presenter uses presentation✕
- Connections
- 3 pairs of types, where a type in presenter uses a type in presentation.
- The types involved
presenterm.presenter.Presenter→presenterm.presentation.Presentationpresenterm.presenter.Presenter→presenterm.presentation.Slidepresenterm.presenter.PresenterState→presenterm.presentation.Presentation
- Direction
- presenter uses presentation, so a change to presentation can break presenter, while a change to presenter can't break presentation.
- Position
- Below the diagonal: presenter uses a module listed above it, which is the healthy direction.
39→24 presenter uses third_party✕
- Connections
- 2 pairs of types, where a type in presenter uses a type in third_party.
- The types involved
presenterm.presenter.Presenter→presenterm.third_party.RenderResultpresenterm.presenter.Presenter→presenterm.third_party.ThirdPartyRender
- Direction
- presenter uses third_party, so a change to third_party can break presenter, while a change to presenter can't break third_party.
- Position
- Below the diagonal: presenter uses a module listed above it, which is the healthy direction.
39→29 presenter uses code.execute✕
- Connections
- 1 pair of types, where a type in presenter uses a type in code.execute.
- The types involved
presenterm.presenter.Presenter→presenterm.code.execute.SnippetExecutor
- Direction
- presenter uses code.execute, so a change to code.execute can break presenter, while a change to presenter can't break code.execute.
- Position
- Below the diagonal: presenter uses a module listed above it, which is the healthy direction.
39→34 presenter uses presentation.builder✕
- Connections
- 2 pairs of types, where a type in presenter uses a type in presentation.builder.
- The types involved
presenterm.presenter.Presenter→presenterm.presentation.builder.Themespresenterm.presenter.PresenterOptions→presenterm.presentation.builder.PresentationBuilderOptions
- Direction
- presenter uses presentation.builder, so a change to presentation.builder can break presenter, while a change to presenter can't break presentation.builder.
- Position
- Below the diagonal: presenter uses a module listed above it, which is the healthy direction.
39→36 presenter uses render.engine✕
- Connections
- 2 pairs of types, where a type in presenter uses a type in render.engine.
- The types involved
presenterm.presenter.Presenter→presenterm.render.engine.RenderEngineOptionspresenterm.presenter.PresenterOptions→presenterm.render.engine.MaxSize
- Direction
- presenter uses render.engine, so a change to render.engine can break presenter, while a change to presenter can't break render.engine.
- Position
- Below the diagonal: presenter uses a module listed above it, which is the healthy direction.
39→37 presenter uses render✕
- Connections
- 2 pairs of types, where a type in presenter uses a type in render.
- The types involved
presenterm.presenter.Presenter→presenterm.render.TerminalDrawerpresenterm.presenter.PresenterState→presenterm.render.ErrorSource
- Direction
- presenter uses render, so a change to render can break presenter, while a change to presenter can't break render.
- Position
- Below the diagonal: presenter uses a module listed above it, which is the healthy direction.
40→2 presenterm uses config✕
- Connections
- 5 pairs of types, where a type in presenterm uses a type in config.
- The types involved
presenterm.Cli→presenterm.config.ImageProtocolpresenterm.CoreComponents→presenterm.config.Configpresenterm.Customizations→presenterm.config.Configpresenterm.SpeakerNotesComponents→presenterm.config.Configpresenterm.presenterm$module→presenterm.config.ValidateOverflows
- Direction
- presenterm uses config, so a change to config can break presenterm, while a change to presenterm can't break config.
- Position
- Below the diagonal: presenterm uses a module listed above it, which is the healthy direction.
40→9 presenterm uses terminal.image.printer✕
- Connections
- 1 pair of types, where a type in presenterm uses a type in terminal.image.printer.
- The types involved
presenterm.CoreComponents→presenterm.terminal.image.printer.ImagePrinter
- Direction
- presenterm uses terminal.image.printer, so a change to terminal.image.printer can break presenterm, while a change to presenterm can't break terminal.image.printer.
- Position
- Below the diagonal: presenterm uses a module listed above it, which is the healthy direction.
40→10 presenterm uses resource✕
- Connections
- 1 pair of types, where a type in presenterm uses a type in resource.
- The types involved
presenterm.CoreComponents→presenterm.resource.Resources
- Direction
- presenterm uses resource, so a change to resource can break presenterm, while a change to presenterm can't break resource.
- Position
- Below the diagonal: presenterm uses a module listed above it, which is the healthy direction.
40→12 presenterm uses theme.clean✕
- Connections
- 1 pair of types, where a type in presenterm uses a type in theme.clean.
- The types involved
presenterm.CoreComponents→presenterm.theme.clean.PresentationTheme
- Direction
- presenterm uses theme.clean, so a change to theme.clean can break presenterm, while a change to presenterm can't break theme.clean.
- Position
- Below the diagonal: presenterm uses a module listed above it, which is the healthy direction.
40→24 presenterm uses third_party✕
- Connections
- 1 pair of types, where a type in presenterm uses a type in third_party.
- The types involved
presenterm.CoreComponents→presenterm.third_party.ThirdPartyRender
- Direction
- presenterm uses third_party, so a change to third_party can break presenterm, while a change to presenterm can't break third_party.
- Position
- Below the diagonal: presenterm uses a module listed above it, which is the healthy direction.
40→29 presenterm uses code.execute✕
- Connections
- 2 pairs of types, where a type in presenterm uses a type in code.execute.
- The types involved
presenterm.CoreComponents→presenterm.code.execute.SnippetExecutorpresenterm.Customizations→presenterm.code.execute.SnippetExecutor
- Direction
- presenterm uses code.execute, so a change to code.execute can break presenterm, while a change to presenterm can't break code.execute.
- Position
- Below the diagonal: presenterm uses a module listed above it, which is the healthy direction.
40→34 presenterm uses presentation.builder✕
- Connections
- 3 pairs of types, where a type in presenterm uses a type in presentation.builder.
- The types involved
presenterm.CoreComponents→presenterm.presentation.builder.PresentationBuilderOptionspresenterm.CoreComponents→presenterm.presentation.builder.Themespresenterm.Customizations→presenterm.presentation.builder.Themes
- Direction
- presenterm uses presentation.builder, so a change to presentation.builder can break presenterm, while a change to presenterm can't break presentation.builder.
- Position
- Below the diagonal: presenterm uses a module listed above it, which is the healthy direction.
40→39 presenterm uses presenter✕
- Connections
- 2 pairs of types, where a type in presenterm uses a type in presenter.
- The types involved
presenterm.CoreComponents→presenterm.presenter.PresentModepresenterm.presenterm$module→presenterm.presenter.PresentMode
- Direction
- presenterm uses presenter, so a change to presenter can break presenterm, while a change to presenterm can't break presenter.
- Position
- Below the diagonal: presenterm 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 | 21 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 12 | Medium |
Roadmap
Top priorities: Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce; Resolve the 1 No ADRs found finding(s) in ADR Quality — start with main.rs; Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with main.rs. | +4.7 pts | Low | ADR Quality |
| Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce. | +5.0 pts | Medium | Observability |
| Resolve the 25 Low coverage finding(s) in Code Coverage — start with mod.rs (2), printer.rs (2), listener.rs. | +1.9 pts | Medium | Code Coverage |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +3.1 pts | Medium | Architecture documentation |
| 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.7 pts | Medium | Deployment & Rollback |
| Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. | +1.0 pts | Low | Static Analysis (SAST) |
| Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. | +1.0 pts | Low | Static Analysis (SAST) |
| Add a build/run (quick start) section to the root README — the first thing a newcomer needs. | +1.6 pts | Medium | Documentation (README) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 1.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.5 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Mixed | Static Analysis (SAST): High: REDACTED |
| src/main.rs | 5.4 | Mixed | Cyclomatic Complexity: presenterm::run (cyclomatic 17) |
| src/presenter.rs | 5.5 | Mixed | Cyclomatic Complexity: Presenter::apply_command (cyclomatic 30) |
| src/export/exporter.rs | 5.7 | Mixed | Cognitive Complexity: Exporter::wait_async_renders_parallel (cognitive 18) |
| src/code/snippet.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/ui/execution/pty.rs | 6.3 | Mixed | Cyclomatic Complexity: PtySnippetOutputOperation::as_render_operations (cyclomatic 17) |
| src/presentation/builder/mod.rs | 6.3 | Mixed | Cognitive Complexity: PresentationBuilder::build_from_parsed (cognitive 16) |
| src/terminal/printer.rs | 6.3 | Mixed | Code Duplication: Edited copy of a member (21 corresponding lines) |
| src/presentation/poller.rs | 6.7 | Mixed | Explicit Debt: TodoComment |
| REDACTED | 6.9 | Mixed | Dependency Vulnerabilities: Medium advisory (unmaintained): REDACTED |
| src/export/output.rs | 7.0 | Near-clean | Cognitive Complexity: HtmlSlide::new (cognitive 18) |
| src/terminal/image/protocols/kitty.rs | 7.0 | Near-clean | Cognitive Complexity: KittyPrinter::load_raw_resource (cognitive 18) |
| src/terminal/capabilities.rs | 7.0 | Near-clean | Cognitive Complexity: TerminalCapabilities::parse_response (cognitive 16) |
| src/theme/clean.rs | 7.2 | Near-clean | God Classes: FileTooLong: theme/clean.rs |
| src/markdown/parse.rs | 7.4 | Near-clean | Cyclomatic Complexity: InlinesParser::process_node (cyclomatic 29) |
| src/presentation/builder/snippet.rs | 7.4 | Near-clean | Cyclomatic Complexity: PresentationBuilder::push_code (cyclomatic 25) |
| src/theme/raw.rs | 7.4 | Near-clean | Cyclomatic Complexity: FooterTemplate::from_str (cyclomatic 20) |
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 34 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 1.0, the weighted average across measured dimensions.
What we checked — 34 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, 116 of 127 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 | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (74 contributor(s) across 1543 commit(s) sampled, automation and bot accounts excluded). One of them holds 86% of the history; the other 73 hold 0.2% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- 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 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (Cargo.toml), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict. For npm the surface is what a published package.json's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
- 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. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- D26 Project Cohesion — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `(repository root)` (22929 LoC, 88 module-visible types across 11 directories) is over its size bounds, and whether one unit is a coherent whole or a grab-bag is read from its type references: the parts of it that reach the rest only through its shared core. Those are read over the C#/VB code model, which this unit's source did not supply. Its size alone is no verdict on its cohesion, so none is published.
- D27 Navigability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- D44 Platform End-of-Life — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a Dockerfile) is simply not read here yet.
- AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- 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 this repository's Rust is most of its product and 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 this repository's Rust is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check'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.
- X5 Nullable reference types — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax and MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, and Kotlin source only, and no C# was loaded, no TypeScript was found, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- 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
12 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was PresentationBuilder::process_comment_command_presentation_mode at 30. A further 14 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being SnippetHighlighter::language_extension at 75 — they are counted neither in the figure above nor in this dimension's score. 7 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold functions was excluded, so the exclusion is disclosed nowhere in the file itself: src/code/highlighting.rs (SnippetHighlighter::language_extension at 75), src/render/engine.rs (RenderEngine::render_one at 19), src/markdown/text_style.rs (Color::from_8bit at 18), src/export/html.rs (presenterm::export::html::color_to_html at 17), src/terminal/image/protocols/kitty.rs (ControlOption::fmt at 17), and 2 more not listed here. 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 12 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with PresentationBuilder::process_comment_command_presentation_mode (cyclomatic 30), Presenter::apply_command (cyclomatic 30), InlinesParser::process_node (cyclomatic 29). — 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 12 together lifts Cyclomatic Complexity from 8.3 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
18 method(s) exceeded the cognitive complexity threshold of 15; the worst was PresentationBuilder::push_code at 37.
What to do
- Bring the 18 bodies over 15 down to 15 or less in Cognitive Complexity — start with PresentationBuilder::push_code (cognitive 37), PtySnippetOutputOperation::as_render_operations (cognitive 37), FooterTemplate::from_str (cognitive 31). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 18 together lifts Cognitive Complexity from 7.6 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
7 god class(es) detected.
What to do
- Resolve the 4 FileTooLong finding(s) in God Classes — start with clean.rs, snippet.rs, raw.rs. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 1 TooManyMethods finding(s) in God Classes — start with mod.rs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 FunctionTooLong finding(s) in God Classes — start with main.rs. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
3 duplicated block group(s) detected. 1.4 % of the production lines (323 of 22,847) are in a reported copy. A further 13 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
What to do
- Resolve the 2 Edited copy of a member (11 corresponding lines) finding(s) in Code Duplication — start with clean.rs, snippet.rs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Edited copy of a member (10 corresponding lines) finding(s) in Code Duplication — start with presenter.rs, properties.rs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Edited copy of a member (5 corresponding lines) finding(s) in Code Duplication — start with text.rs, clean.rs. — One of this dimension's main actionable groups (2 warning-level).
D6 · Cohesion (LCOM4)
0 of 92 classes have LCOM4 above 3.
D8 · Code Coverage
Line coverage 56.4% — 25 file(s) below 50%. Measured from the Rust suite (repository root: `cargo test --workspace` instrumented over 74 production file(s), 1 test binaries and 0 doc-test binaries).
What to do
- Resolve the 25 Low coverage finding(s) in Code Coverage — start with mod.rs (2), printer.rs (2), listener.rs. — One of this dimension's main actionable groups (25 warning-level).
D11 · Test Reliability
0 flaky across 1 measured tier(s). Rust (repository root, 43 test files): measured (0 flaky).
D12 · Dependency Hygiene
1 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
0 of 207 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 BSD-2-Clause, which is its own choice and is not judged here.
D15 · Churn × Complexity Hotspots
Top hotspots: src/main.rs (4×17=68); src/presenter.rs (3×17=51)
What to do
- Resolve the 2 Hotspot finding(s) in Churn × Complexity Hotspots — start with main.rs, presenter.rs. — One of this dimension's main actionable groups (2 warning-level).
D17 · Explicit Debt
3 deducted task-comment markers across 22847 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 3 TodoComment finding(s) in Explicit Debt — start with build.rs, poller.rs, snippet.rs. — One of this dimension's main actionable groups (3 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 23 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with main.rs. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
21 finding(s): 0 critical, 19 high, 2 medium, 0 low. 17 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. Separately, one or more rules could not re-parse an embedded snippet in 2 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 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 17 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 (17 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
2 finding(s): 0 critical, 0 high, 2 medium, 0 low.
What to do
- Resolve the 2 Medium advisory (unmaintained) finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 69 of the 84 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
Strongest change-coupling: mod.rs↔diff.rs 88%; diff.rs↔engine.rs 71%; engine.rs↔virt.rs 50%
What to do
- Resolve the 2 Boundary-crossing change coupling finding(s) in Change Coupling — start with diff.rs, engine.rs. — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 1 Change coupling finding(s) in Change Coupling — start with mod.rs. — One of this dimension's main actionable groups (1 warning-level).
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX9 · CQS / query purity
M1 · Documentation (README)
What to do
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
P1 · CI/CD gates
P2 · Observability
- No logging or diagnostics emission found. This repository ships a binary its users launch rather than a service you operate, so there is no operator to page — but when a run fails on a user's machine, neither they nor you have anything to read.
What to do
- Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.
P3 · Security & performance tooling
What to do
- Enable Dependabot/Renovate or a dependency-review gate.
- 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
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 92% | Exemplary | Solid. |
| Architecture | 98% | Exemplary | Strongest area. |
| Maturity | 63% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 51% | Adequate — gated by P2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 55% | Adequate — gated by D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
Unscored — 1 check(s) recorded observations but carry no score
- X7 Silent fallback defaults — 3 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 79 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one.
- AX2 Stateful singletons — Not applicable: Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written. 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 — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no data at rest for these controls to protect.
- C2 Access Controls — No access-control surface detected in the analyzed source — this repository starts no server another machine can reach (no actix-web HttpServer, axum::serve, Rocket launch, warp::serve, poem or salvo Server, tonic Server::builder, hyper or tiny_http server outside examples and tests, none bound beyond loopback). Access control is therefore N/A here — a crate is authorized by the application that serves it, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~37 lines of test source are present (.rs) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — D21 withholds its sibling role token rows: 1 candidate(s) found and not reported.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .rs source were not judged.
- D25 ADR Conformance — no ADRs to check
- D26 Project Cohesion — D26 could not read how the parts of this repository's one build unit reference each other, so its cohesion was not measured. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.rs), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
- D5 Coupling — Not applicable — this Cargo build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (36 value object(s))
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- M4 Documentation accuracy — Not applicable: the 23 current-state document(s) make no claim of a kind M4 checks. 1 claim(s) of kinds M4 does not check were not checked (environment variable 1); M4 checks only links and versions and artefact counts.
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript, Rust source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage data present for 74 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `#[bench]`, criterion's `bench_function`/`bench_with_input`, `#[divan::bench]` or `#[library_benchmark]` in any `.rs` file, or criterion, divan, iai or a `[[bench]]` target in a Cargo.toml, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
- S1 Web-Security Posture — No web surface: 83 Rust file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation and obsolete TLS versions, and none was found. This repository serves no HTTP of its own — no HTTP-server crate (actix-web, axum, Rocket, warp, poem, tide, salvo, tonic, a hyper server, …) among its Cargo manifests' run-time dependencies, and no server started in its production source — so HTTPS enforcement, HSTS, cookie flags and input validation are N/A here, as they are for a C# library or worker. If this codebase starts serving HTTP, the dimension reactivates automatically.
- X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X12 Unreachable branch — X12 reached only 0% of this repository's production lines — rust (22,847 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X16 Unfloored truncation loop — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — no C# was loaded; this repository's 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 applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — Not applicable: 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. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
- X27 Collection changed while being enumerated — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X3 Exception handling — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Rust was read, and it logs through none: the `log` crate's macros take one finished message (as log4net does in C#; its `kv` values are an opt-in its backends mostly drop), `println!`/`eprintln!` are not loggers, or it makes no log call outside its tests and examples at all. Calls through `tracing` (`tracing::info!`, or `info!` imported from it) would be judged.
- X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 21 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Boundary-crossing change coupling: diff.rs ↔ engine.rs src/presentation/diff.rs:1
- Boundary-crossing change coupling: engine.rs ↔ virt.rs src/render/engine.rs:1
- REDACTED
- REDACTED
Serious — 94 finding(s)
- Low coverage: src/commands/listener.rs src/commands/listener.rs:1
- Low coverage: src/demo.rs src/demo.rs:1
- Low coverage: src/export/exporter.rs src/export/exporter.rs:1
- Low coverage: src/export/output.rs src/export/output.rs:1
- Low coverage: src/main.rs src/main.rs:1
- Low coverage: src/presentation/poller.rs src/presentation/poller.rs:1
- Low coverage: src/presenter.rs src/presenter.rs:1
- Low coverage: src/render/ascii_scaler.rs src/render/ascii_scaler.rs:1
- Low coverage: src/render/mod.rs src/render/mod.rs:1
- Low coverage: src/render/validate.rs src/render/validate.rs:1
- Low coverage: src/terminal/capabilities.rs src/terminal/capabilities.rs:1
- Low coverage: src/terminal/emulator.rs src/terminal/emulator.rs:1
- Low coverage: src/terminal/image/mod.rs src/terminal/image/mod.rs:1
- Low coverage: src/terminal/image/printer.rs src/terminal/image/printer.rs:1
- Low coverage: src/terminal/image/protocols/ascii.rs src/terminal/image/protocols/ascii.rs:1
- Low coverage: src/terminal/image/protocols/iterm.rs src/terminal/image/protocols/iterm.rs:1
- Low coverage: src/terminal/image/protocols/kitty.rs src/terminal/image/protocols/kitty.rs:1
- Low coverage: src/terminal/image/protocols/raw.rs src/terminal/image/protocols/raw.rs:1
- Low coverage: src/terminal/image/protocols/sixel.rs src/terminal/image/protocols/sixel.rs:1
- Low coverage: src/terminal/printer.rs src/terminal/printer.rs:1
- Low coverage: src/third_party.rs src/third_party.rs:1
- Low coverage: src/tools.rs src/tools.rs:1
- Low coverage: src/ui/execution/acquire_terminal.rs src/ui/execution/acquire_terminal.rs:1
- Low coverage: src/ui/execution/image.rs src/ui/execution/image.rs:1
- Low coverage: src/ui/execution/pty.rs src/ui/execution/pty.rs:1
- PresentationBuilder::push_code (cognitive 37) src/presentation/builder/snippet.rs:31
- PresentationBuilder::push_intro_slide (cognitive 18) src/presentation/builder/frontmatter.rs:109
- PresentationBuilder::process_comment_command_presentation_mode (cognitive 16) src/presentation/builder/comment.rs:36
- PresentationBuilder::build_from_parsed (cognitive 16) src/presentation/builder/mod.rs:236
- FileTooLong: theme/clean.rs src/theme/clean.rs
- FileTooLong: code/snippet.rs src/code/snippet.rs
- FileTooLong: theme/raw.rs src/theme/raw.rs
- FileTooLong: src/presenter.rs src/presenter.rs
- TodoComment build.rs:27
- TodoComment src/presentation/poller.rs:69
- TodoComment src/code/snippet.rs:131
- PresentationBuilder::process_comment_command_presentation_mode (cyclomatic 30) src/presentation/builder/comment.rs:36
- PresentationBuilder::push_code (cyclomatic 25) src/presentation/builder/snippet.rs:31
- Presenter::apply_command (cyclomatic 30) src/presenter.rs:279
- Presenter::present (cyclomatic 17) src/presenter.rs:113
- SnippetParser::parse_attribute (cyclomatic 26) src/code/snippet.rs:303
- SnippetParser::parse_attributes (cyclomatic 19) src/code/snippet.rs:226
- Hotspot: src/main.rs src/main.rs:398
- Hotspot: src/presenter.rs src/presenter.rs:113
- Presenter::present (cognitive 29) src/presenter.rs:113
- Presenter::apply_command (cognitive 24) src/presenter.rs:279
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Edited copy of a member (11 corresponding lines) src/theme/clean.rs:222
- Edited copy of a member (11 corresponding lines) src/presentation/builder/snippet.rs:371
- Edited copy of a member (10 corresponding lines) src/presenter.rs:491
- Edited copy of a member (10 corresponding lines) src/render/properties.rs:41
- Edited copy of a member (5 corresponding lines) src/markdown/text.rs:233
- Edited copy of a member (5 corresponding lines) src/theme/clean.rs:440
- InlinesParser::process_node (cyclomatic 29) src/markdown/parse.rs:411
- FooterTemplate::from_str (cyclomatic 20) src/theme/raw.rs:605
- KeyMatcher::parse_key_code (cyclomatic 19) src/commands/keyboard.rs:326
- AnsiColorParser::parse (cyclomatic 18) src/terminal/ansi.rs:74
- PtySnippetOutputOperation::as_render_operations (cyclomatic 17) src/ui/execution/pty.rs:97
- presenterm::run (cyclomatic 17) src/main.rs:398
- PtySnippetOutputOperation::as_render_operations (cognitive 37) src/ui/execution/pty.rs:97
- FooterTemplate::from_str (cognitive 31) src/theme/raw.rs:605
- TextDrawer::draw (cognitive 25) src/render/text.rs:82
- KeyMatcher::parse_key_code (cognitive 23) src/commands/keyboard.rs:326
- InlinesParser::process_node (cognitive 22) src/markdown/parse.rs:411
- LinesFrame::build_commands (cognitive 22) src/transitions/mod.rs:67
- presenterm::run (cognitive 22) src/main.rs:398
- Exporter::wait_async_renders_parallel (cognitive 18) src/export/exporter.rs:219
- HtmlSlide::new (cognitive 18) src/export/output.rs:39
- KittyPrinter::load_raw_resource (cognitive 18) src/terminal/image/protocols/kitty.rs:393
- AnsiColorParser::parse (cognitive 17) src/terminal/ansi.rs:74
- TerminalCapabilities::parse_response (cognitive 16) src/terminal/capabilities.rs:131
- TooManyMethods: PresentationBuilder src/presentation/builder/mod.rs:164
- FunctionTooLong: presenterm::run src/main.rs:398
- ClassTooLong: Presenter src/presenter.rs:63
- Change coupling: mod.rs ↔ diff.rs src/presentation/builder/mod.rs:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Edited copy of a member (21 corresponding lines) src/terminal/printer.rs:237
- Edited copy of a member (27 corresponding lines) src/export/exporter.rs:219
- Edited copy of a member (15 corresponding lines) src/presenter.rs:522
- Edited copy of a member (23 corresponding lines) src/export/exporter.rs:161
- Edited copy of a member (14 corresponding lines) src/markdown/parse.rs:235
- Edited copy of a member (8 corresponding lines) src/theme/clean.rs:295
- Edited copy of a member (6 corresponding lines) src/markdown/text.rs:218
- Duplicated block (8 lines × 2) src/export/exporter.rs:248
- Duplicated block (7 lines × 2) src/presenter.rs:523
- Duplicated block (11 lines × 2) src/terminal/printer.rs:242
- No structured logging
Minor — 11 finding(s)
- Silent fallback default on Err src/presentation/builder/images.rs:134
- Silent fallback default on Err src/terminal/image/protocols/kitty.rs:91
- Silent fallback default on Err src/main.rs:532
- No ADRs found src/main.rs:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No release approval gate
Minor — 1 finding(s)
- Outdated: flate2
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-803b42b953fc4ee1b745df530e97918a/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-803b42b953fc4ee1b745df530e97918a/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 . | 21 | 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 . | 2 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |