Executive summary
unhappychoice/gitlogue falls short of our standard for a preview release, in part because it has pipeline tools referenced by a changeable name. It scores 55 out of 100 and is rated Adequate, and all 38 of its critical findings are security problems.
Security and Compliance, at 44, is the weakest lens and counts most in the score. The best first step for the work it takes is recording design decisions, worth about 2 points. Adopting a type checker comes next, worth about 4 points. Raising Security and Compliance to 68 would lift the score to about 62.
Thirty-one pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Three secrets can leak from the build pipeline, and one automatic update takes new releases before a bad one can be spotted. Pinning each tool to an exact version, limiting each secret to its own step and setting a waiting period for automatic updates would close these risks. Updating the vulnerable packages would fix the package with a known security hole, and the pipeline step that installs packages without pinning their versions needs the packages it installs pinned to exact versions.
The product code is 11,545 lines, about €12,000 to rebuild.
If Security and Compliance rose from 44 to 68, the lowest score rated Strong, the score would rise from 55 to about 62.
New since the last survey: 13 findings
- Code Duplication · Members sharing a duplicated core (17 members, 50+ identical tokens) src/theme/themes/ayu_dark.rs
- Code Duplication · Edited copy of a member (31 corresponding lines) src/ui.rs
- Code Duplication · Edited copies of one member (4 members, 19+ corresponding lines) src/git.rs
- Code Duplication · Edited copy of a member (19 corresponding lines) src/main.rs
- Code Duplication · Edited copy of a member (13 corresponding lines) src/git.rs
- Code Duplication · Edited copy of a member (10 corresponding lines) src/git.rs
- Code Duplication · Edited copy of a member (15 corresponding lines) src/config.rs
- Code Duplication · Duplicated block (27 lines × 2) src/git.rs
- Code Duplication · Duplicated block (20–21 lines × 3) src/widgets/selectable_paragraph.rs
- Code Duplication · Duplicated block (13–14 lines × 2) src/git.rs
- Code Duplication · Duplicated block (10–11 lines × 3) src/animation.rs
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
Fixed since the last survey: 9 findings
- Code Duplication · Near-duplicate member family (17 members, 40 shared lines) src/theme/themes/ayu_dark.rs
- Code Duplication · Duplicated block (27 lines × 2) src/git.rs
- Code Duplication · Duplicated block (20–21 lines × 3) src/widgets/selectable_paragraph.rs
- Code Duplication · Duplicated block (20 lines × 17) src/theme/themes/ayu_dark.rs
- Code Duplication · Duplicated block (13–14 lines × 2) src/git.rs
- Code Duplication · Duplicated block (10–11 lines × 3) src/animation.rs
- Code Duplication · Duplicated block (7 lines × 17) src/theme/themes/ayu_dark.rs
- Code Duplication · Duplicated block (6 lines × 17) src/theme/themes/ayu_dark.rs
- Dependency Vulnerabilities · Medium vulnerability: [GHSA redacted] REDACTED
Rebuild cost: about €12,000 · Estimate
| Cost to rebuild | €4,000 to €20,000, for 66 to 209 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 55. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 11,545 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 (global) | 2 gitlogue.config | 3 gitlogue.git | 4 gitlogue.syntax.languages | 5 gitlogue.syntax.languages.astro | 6 gitlogue.syntax.languages.bash | 7 gitlogue.syntax.languages.c | 8 gitlogue.syntax.languages.clojure | 9 gitlogue.syntax.languages.cpp | 10 gitlogue.syntax.languages.csharp | 11 gitlogue.syntax.languages.css | 12 gitlogue.syntax.languages.dart | 13 gitlogue.syntax.languages.elixir | 14 gitlogue.theme | 15 gitlogue.panes.file_tree | 16 gitlogue.panes.status_bar | 17 gitlogue.syntax | 18 gitlogue.theme.themes.ayu_dark | 19 gitlogue.theme.themes.catppuccin | 20 gitlogue.theme.themes.dracula | 21 gitlogue.theme.themes.everforest | 22 gitlogue.theme.themes.fluorite | 23 gitlogue.theme.themes.github_dark | 24 gitlogue.theme.themes.gruvbox | 25 gitlogue.theme.themes.material | 26 gitlogue.theme.themes.monokai | 27 gitlogue.theme.themes.night_owl | 28 gitlogue.theme.themes.nord | 29 gitlogue.theme.themes.one_dark | 30 gitlogue.theme.themes.rose_pine | 31 gitlogue.theme.themes.solarized_dark | 32 gitlogue.theme.themes.solarized_light | 33 gitlogue.theme.themes.telemetry | 34 gitlogue.theme.themes.tokyo_night | 35 gitlogue.watch | 36 gitlogue.animation | 37 gitlogue.main | 38 gitlogue.panes.editor | 39 gitlogue.panes.terminal | 40 gitlogue.ui |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 (global) | ||||||||||||||||||||||||||||||||||||||||
| 2 gitlogue.config | ||||||||||||||||||||||||||||||||||||||||
| 3 gitlogue.git | ||||||||||||||||||||||||||||||||||||||||
| 4 gitlogue.syntax.languages | ||||||||||||||||||||||||||||||||||||||||
| 5 gitlogue.syntax.languages.astro | ||||||||||||||||||||||||||||||||||||||||
| 6 gitlogue.syntax.languages.bash | ||||||||||||||||||||||||||||||||||||||||
| 7 gitlogue.syntax.languages.c | ||||||||||||||||||||||||||||||||||||||||
| 8 gitlogue.syntax.languages.clojure | ||||||||||||||||||||||||||||||||||||||||
| 9 gitlogue.syntax.languages.cpp | ||||||||||||||||||||||||||||||||||||||||
| 10 gitlogue.syntax.languages.csharp | ||||||||||||||||||||||||||||||||||||||||
| 11 gitlogue.syntax.languages.css | ||||||||||||||||||||||||||||||||||||||||
| 12 gitlogue.syntax.languages.dart | ||||||||||||||||||||||||||||||||||||||||
| 13 gitlogue.syntax.languages.elixir | ||||||||||||||||||||||||||||||||||||||||
| 14 gitlogue.theme | ||||||||||||||||||||||||||||||||||||||||
| 15 gitlogue.panes.file_tree | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 16 gitlogue.panes.status_bar | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 17 gitlogue.syntax | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 18 gitlogue.theme.themes.ayu_dark | 1 | |||||||||||||||||||||||||||||||||||||||
| 19 gitlogue.theme.themes.catppuccin | 1 | |||||||||||||||||||||||||||||||||||||||
| 20 gitlogue.theme.themes.dracula | 1 | |||||||||||||||||||||||||||||||||||||||
| 21 gitlogue.theme.themes.everforest | 1 | |||||||||||||||||||||||||||||||||||||||
| 22 gitlogue.theme.themes.fluorite | 1 | |||||||||||||||||||||||||||||||||||||||
| 23 gitlogue.theme.themes.github_dark | 1 | |||||||||||||||||||||||||||||||||||||||
| 24 gitlogue.theme.themes.gruvbox | 1 | |||||||||||||||||||||||||||||||||||||||
| 25 gitlogue.theme.themes.material | 1 | |||||||||||||||||||||||||||||||||||||||
| 26 gitlogue.theme.themes.monokai | 1 | |||||||||||||||||||||||||||||||||||||||
| 27 gitlogue.theme.themes.night_owl | 1 | |||||||||||||||||||||||||||||||||||||||
| 28 gitlogue.theme.themes.nord | 1 | |||||||||||||||||||||||||||||||||||||||
| 29 gitlogue.theme.themes.one_dark | 1 | |||||||||||||||||||||||||||||||||||||||
| 30 gitlogue.theme.themes.rose_pine | 1 | |||||||||||||||||||||||||||||||||||||||
| 31 gitlogue.theme.themes.solarized_dark | 1 | |||||||||||||||||||||||||||||||||||||||
| 32 gitlogue.theme.themes.solarized_light | 1 | |||||||||||||||||||||||||||||||||||||||
| 33 gitlogue.theme.themes.telemetry | 1 | |||||||||||||||||||||||||||||||||||||||
| 34 gitlogue.theme.themes.tokyo_night | 1 | |||||||||||||||||||||||||||||||||||||||
| 35 gitlogue.watch | 1 | |||||||||||||||||||||||||||||||||||||||
| 36 gitlogue.animation | 3 | 2 | ||||||||||||||||||||||||||||||||||||||
| 37 gitlogue.main | 1 | 4 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 38 gitlogue.panes.editor | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 39 gitlogue.panes.terminal | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 40 gitlogue.ui | 3 | 1 | 1 | 1 | 1 | 2 | 1 | 1 | 1 |
15→3 gitlogue.panes.file_tree uses gitlogue.git✕
- Connections
- 1 pair of types, where a type in gitlogue.panes.file_tree uses a type in gitlogue.git.
- The types involved
gitlogue.panes.file_tree.FileTreePane→gitlogue.git.CommitMetadata
- Direction
- gitlogue.panes.file_tree uses gitlogue.git, so a change to gitlogue.git can break gitlogue.panes.file_tree, while a change to gitlogue.panes.file_tree can't break gitlogue.git.
- Position
- Below the diagonal: gitlogue.panes.file_tree uses a module listed above it, which is the healthy direction.
15→14 gitlogue.panes.file_tree uses gitlogue.theme✕
- Connections
- 1 pair of types, where a type in gitlogue.panes.file_tree uses a type in gitlogue.theme.
- The types involved
gitlogue.panes.file_tree.FileTreePane→gitlogue.theme.Theme
- Direction
- gitlogue.panes.file_tree uses gitlogue.theme, so a change to gitlogue.theme can break gitlogue.panes.file_tree, while a change to gitlogue.panes.file_tree can't break gitlogue.theme.
- Position
- Below the diagonal: gitlogue.panes.file_tree uses a module listed above it, which is the healthy direction.
16→3 gitlogue.panes.status_bar uses gitlogue.git✕
- Connections
- 1 pair of types, where a type in gitlogue.panes.status_bar uses a type in gitlogue.git.
- The types involved
gitlogue.panes.status_bar.StatusBarPane→gitlogue.git.CommitMetadata
- Direction
- gitlogue.panes.status_bar uses gitlogue.git, so a change to gitlogue.git can break gitlogue.panes.status_bar, while a change to gitlogue.panes.status_bar can't break gitlogue.git.
- Position
- Below the diagonal: gitlogue.panes.status_bar uses a module listed above it, which is the healthy direction.
16→14 gitlogue.panes.status_bar uses gitlogue.theme✕
- Connections
- 1 pair of types, where a type in gitlogue.panes.status_bar uses a type in gitlogue.theme.
- The types involved
gitlogue.panes.status_bar.StatusBarPane→gitlogue.theme.Theme
- Direction
- gitlogue.panes.status_bar uses gitlogue.theme, so a change to gitlogue.theme can break gitlogue.panes.status_bar, while a change to gitlogue.panes.status_bar can't break gitlogue.theme.
- Position
- Below the diagonal: gitlogue.panes.status_bar uses a module listed above it, which is the healthy direction.
17→4 gitlogue.syntax uses gitlogue.syntax.languages✕
- Connections
- 2 pairs of types, where a type in gitlogue.syntax uses a type in gitlogue.syntax.languages.
- The types involved
gitlogue.syntax.Highlighter→gitlogue.syntax.languages.LanguageSupportgitlogue.syntax.syntax$module→gitlogue.syntax.languages.LanguageSupport
- Direction
- gitlogue.syntax uses gitlogue.syntax.languages, so a change to gitlogue.syntax.languages can break gitlogue.syntax, while a change to gitlogue.syntax can't break gitlogue.syntax.languages.
- Position
- Below the diagonal: gitlogue.syntax uses a module listed above it, which is the healthy direction.
17→14 gitlogue.syntax uses gitlogue.theme✕
- Connections
- 1 pair of types, where a type in gitlogue.syntax uses a type in gitlogue.theme.
- The types involved
gitlogue.syntax.TokenType→gitlogue.theme.Theme
- Direction
- gitlogue.syntax uses gitlogue.theme, so a change to gitlogue.theme can break gitlogue.syntax, while a change to gitlogue.syntax can't break gitlogue.theme.
- Position
- Below the diagonal: gitlogue.syntax uses a module listed above it, which is the healthy direction.
18→14 gitlogue.theme.themes.ayu_dark uses gitlogue.theme✕
- Connections
- 1 pair of types, where a type in gitlogue.theme.themes.ayu_dark uses a type in gitlogue.theme.
- The types involved
gitlogue.theme.themes.ayu_dark.ayu_dark$module→gitlogue.theme.Theme
- Direction
- gitlogue.theme.themes.ayu_dark uses gitlogue.theme, so a change to gitlogue.theme can break gitlogue.theme.themes.ayu_dark, while a change to gitlogue.theme.themes.ayu_dark can't break gitlogue.theme.
- Position
- Below the diagonal: gitlogue.theme.themes.ayu_dark uses a module listed above it, which is the healthy direction.
19→14 gitlogue.theme.themes.catppuccin uses gitlogue.theme✕
- Connections
- 1 pair of types, where a type in gitlogue.theme.themes.catppuccin uses a type in gitlogue.theme.
- The types involved
gitlogue.theme.themes.catppuccin.catppuccin$module→gitlogue.theme.Theme
- Direction
- gitlogue.theme.themes.catppuccin uses gitlogue.theme, so a change to gitlogue.theme can break gitlogue.theme.themes.catppuccin, while a change to gitlogue.theme.themes.catppuccin can't break gitlogue.theme.
- Position
- Below the diagonal: gitlogue.theme.themes.catppuccin uses a module listed above it, which is the healthy direction.
20→14 gitlogue.theme.themes.dracula uses gitlogue.theme✕
- Connections
- 1 pair of types, where a type in gitlogue.theme.themes.dracula uses a type in gitlogue.theme.
- The types involved
gitlogue.theme.themes.dracula.dracula$module→gitlogue.theme.Theme
- Direction
- gitlogue.theme.themes.dracula uses gitlogue.theme, so a change to gitlogue.theme can break gitlogue.theme.themes.dracula, while a change to gitlogue.theme.themes.dracula can't break gitlogue.theme.
- Position
- Below the diagonal: gitlogue.theme.themes.dracula uses a module listed above it, which is the healthy direction.
21→14 gitlogue.theme.themes.everforest uses gitlogue.theme✕
- Connections
- 1 pair of types, where a type in gitlogue.theme.themes.everforest uses a type in gitlogue.theme.
- The types involved
gitlogue.theme.themes.everforest.everforest$module→gitlogue.theme.Theme
- Direction
- gitlogue.theme.themes.everforest uses gitlogue.theme, so a change to gitlogue.theme can break gitlogue.theme.themes.everforest, while a change to gitlogue.theme.themes.everforest can't break gitlogue.theme.
- Position
- Below the diagonal: gitlogue.theme.themes.everforest uses a module listed above it, which is the healthy direction.
22→14 gitlogue.theme.themes.fluorite uses gitlogue.theme✕
- Connections
- 1 pair of types, where a type in gitlogue.theme.themes.fluorite uses a type in gitlogue.theme.
- The types involved
gitlogue.theme.themes.fluorite.fluorite$module→gitlogue.theme.Theme
- Direction
- gitlogue.theme.themes.fluorite uses gitlogue.theme, so a change to gitlogue.theme can break gitlogue.theme.themes.fluorite, while a change to gitlogue.theme.themes.fluorite can't break gitlogue.theme.
- Position
- Below the diagonal: gitlogue.theme.themes.fluorite uses a module listed above it, which is the healthy direction.
23→14 gitlogue.theme.themes.github_dark uses gitlogue.theme✕
- Connections
- 1 pair of types, where a type in gitlogue.theme.themes.github_dark uses a type in gitlogue.theme.
- The types involved
gitlogue.theme.themes.github_dark.github_dark$module→gitlogue.theme.Theme
- Direction
- gitlogue.theme.themes.github_dark uses gitlogue.theme, so a change to gitlogue.theme can break gitlogue.theme.themes.github_dark, while a change to gitlogue.theme.themes.github_dark can't break gitlogue.theme.
- Position
- Below the diagonal: gitlogue.theme.themes.github_dark uses a module listed above it, which is the healthy direction.
24→14 gitlogue.theme.themes.gruvbox uses gitlogue.theme✕
- Connections
- 1 pair of types, where a type in gitlogue.theme.themes.gruvbox uses a type in gitlogue.theme.
- The types involved
gitlogue.theme.themes.gruvbox.gruvbox$module→gitlogue.theme.Theme
- Direction
- gitlogue.theme.themes.gruvbox uses gitlogue.theme, so a change to gitlogue.theme can break gitlogue.theme.themes.gruvbox, while a change to gitlogue.theme.themes.gruvbox can't break gitlogue.theme.
- Position
- Below the diagonal: gitlogue.theme.themes.gruvbox uses a module listed above it, which is the healthy direction.
25→14 gitlogue.theme.themes.material uses gitlogue.theme✕
- Connections
- 1 pair of types, where a type in gitlogue.theme.themes.material uses a type in gitlogue.theme.
- The types involved
gitlogue.theme.themes.material.material$module→gitlogue.theme.Theme
- Direction
- gitlogue.theme.themes.material uses gitlogue.theme, so a change to gitlogue.theme can break gitlogue.theme.themes.material, while a change to gitlogue.theme.themes.material can't break gitlogue.theme.
- Position
- Below the diagonal: gitlogue.theme.themes.material uses a module listed above it, which is the healthy direction.
26→14 gitlogue.theme.themes.monokai uses gitlogue.theme✕
- Connections
- 1 pair of types, where a type in gitlogue.theme.themes.monokai uses a type in gitlogue.theme.
- The types involved
gitlogue.theme.themes.monokai.monokai$module→gitlogue.theme.Theme
- Direction
- gitlogue.theme.themes.monokai uses gitlogue.theme, so a change to gitlogue.theme can break gitlogue.theme.themes.monokai, while a change to gitlogue.theme.themes.monokai can't break gitlogue.theme.
- Position
- Below the diagonal: gitlogue.theme.themes.monokai uses a module listed above it, which is the healthy direction.
27→14 gitlogue.theme.themes.night_owl uses gitlogue.theme✕
- Connections
- 1 pair of types, where a type in gitlogue.theme.themes.night_owl uses a type in gitlogue.theme.
- The types involved
gitlogue.theme.themes.night_owl.night_owl$module→gitlogue.theme.Theme
- Direction
- gitlogue.theme.themes.night_owl uses gitlogue.theme, so a change to gitlogue.theme can break gitlogue.theme.themes.night_owl, while a change to gitlogue.theme.themes.night_owl can't break gitlogue.theme.
- Position
- Below the diagonal: gitlogue.theme.themes.night_owl uses a module listed above it, which is the healthy direction.
28→14 gitlogue.theme.themes.nord uses gitlogue.theme✕
- Connections
- 1 pair of types, where a type in gitlogue.theme.themes.nord uses a type in gitlogue.theme.
- The types involved
gitlogue.theme.themes.nord.nord$module→gitlogue.theme.Theme
- Direction
- gitlogue.theme.themes.nord uses gitlogue.theme, so a change to gitlogue.theme can break gitlogue.theme.themes.nord, while a change to gitlogue.theme.themes.nord can't break gitlogue.theme.
- Position
- Below the diagonal: gitlogue.theme.themes.nord uses a module listed above it, which is the healthy direction.
29→14 gitlogue.theme.themes.one_dark uses gitlogue.theme✕
- Connections
- 1 pair of types, where a type in gitlogue.theme.themes.one_dark uses a type in gitlogue.theme.
- The types involved
gitlogue.theme.themes.one_dark.one_dark$module→gitlogue.theme.Theme
- Direction
- gitlogue.theme.themes.one_dark uses gitlogue.theme, so a change to gitlogue.theme can break gitlogue.theme.themes.one_dark, while a change to gitlogue.theme.themes.one_dark can't break gitlogue.theme.
- Position
- Below the diagonal: gitlogue.theme.themes.one_dark uses a module listed above it, which is the healthy direction.
30→14 gitlogue.theme.themes.rose_pine uses gitlogue.theme✕
- Connections
- 1 pair of types, where a type in gitlogue.theme.themes.rose_pine uses a type in gitlogue.theme.
- The types involved
gitlogue.theme.themes.rose_pine.rose_pine$module→gitlogue.theme.Theme
- Direction
- gitlogue.theme.themes.rose_pine uses gitlogue.theme, so a change to gitlogue.theme can break gitlogue.theme.themes.rose_pine, while a change to gitlogue.theme.themes.rose_pine can't break gitlogue.theme.
- Position
- Below the diagonal: gitlogue.theme.themes.rose_pine uses a module listed above it, which is the healthy direction.
31→14 gitlogue.theme.themes.solarized_dark uses gitlogue.theme✕
- Connections
- 1 pair of types, where a type in gitlogue.theme.themes.solarized_dark uses a type in gitlogue.theme.
- The types involved
gitlogue.theme.themes.solarized_dark.solarized_dark$module→gitlogue.theme.Theme
- Direction
- gitlogue.theme.themes.solarized_dark uses gitlogue.theme, so a change to gitlogue.theme can break gitlogue.theme.themes.solarized_dark, while a change to gitlogue.theme.themes.solarized_dark can't break gitlogue.theme.
- Position
- Below the diagonal: gitlogue.theme.themes.solarized_dark uses a module listed above it, which is the healthy direction.
32→14 gitlogue.theme.themes.solarized_light uses gitlogue.theme✕
- Connections
- 1 pair of types, where a type in gitlogue.theme.themes.solarized_light uses a type in gitlogue.theme.
- The types involved
gitlogue.theme.themes.solarized_light.solarized_light$module→gitlogue.theme.Theme
- Direction
- gitlogue.theme.themes.solarized_light uses gitlogue.theme, so a change to gitlogue.theme can break gitlogue.theme.themes.solarized_light, while a change to gitlogue.theme.themes.solarized_light can't break gitlogue.theme.
- Position
- Below the diagonal: gitlogue.theme.themes.solarized_light uses a module listed above it, which is the healthy direction.
33→14 gitlogue.theme.themes.telemetry uses gitlogue.theme✕
- Connections
- 1 pair of types, where a type in gitlogue.theme.themes.telemetry uses a type in gitlogue.theme.
- The types involved
gitlogue.theme.themes.telemetry.telemetry$module→gitlogue.theme.Theme
- Direction
- gitlogue.theme.themes.telemetry uses gitlogue.theme, so a change to gitlogue.theme can break gitlogue.theme.themes.telemetry, while a change to gitlogue.theme.themes.telemetry can't break gitlogue.theme.
- Position
- Below the diagonal: gitlogue.theme.themes.telemetry uses a module listed above it, which is the healthy direction.
34→14 gitlogue.theme.themes.tokyo_night uses gitlogue.theme✕
- Connections
- 1 pair of types, where a type in gitlogue.theme.themes.tokyo_night uses a type in gitlogue.theme.
- The types involved
gitlogue.theme.themes.tokyo_night.tokyo_night$module→gitlogue.theme.Theme
- Direction
- gitlogue.theme.themes.tokyo_night uses gitlogue.theme, so a change to gitlogue.theme can break gitlogue.theme.themes.tokyo_night, while a change to gitlogue.theme.themes.tokyo_night can't break gitlogue.theme.
- Position
- Below the diagonal: gitlogue.theme.themes.tokyo_night uses a module listed above it, which is the healthy direction.
35→3 gitlogue.watch uses gitlogue.git✕
- Connections
- 1 pair of types, where a type in gitlogue.watch uses a type in gitlogue.git.
- The types involved
gitlogue.watch.CommitWatcher→gitlogue.git.GitRepository
- Direction
- gitlogue.watch uses gitlogue.git, so a change to gitlogue.git can break gitlogue.watch, while a change to gitlogue.watch can't break gitlogue.git.
- Position
- Below the diagonal: gitlogue.watch uses a module listed above it, which is the healthy direction.
36→3 gitlogue.animation uses gitlogue.git✕
- Connections
- 3 pairs of types, where a type in gitlogue.animation uses a type in gitlogue.git.
- The types involved
gitlogue.animation.AnimationEngine→gitlogue.git.CommitMetadatagitlogue.animation.AnimationEngine→gitlogue.git.DiffHunkgitlogue.animation.AnimationEngine→gitlogue.git.FileChange
- Direction
- gitlogue.animation uses gitlogue.git, so a change to gitlogue.git can break gitlogue.animation, while a change to gitlogue.animation can't break gitlogue.git.
- Position
- Below the diagonal: gitlogue.animation uses a module listed above it, which is the healthy direction.
36→17 gitlogue.animation uses gitlogue.syntax✕
- Connections
- 2 pairs of types, where a type in gitlogue.animation uses a type in gitlogue.syntax.
- The types involved
gitlogue.animation.AnimationEngine→gitlogue.syntax.Highlightergitlogue.animation.EditorBuffer→gitlogue.syntax.HighlightSpan
- Direction
- gitlogue.animation uses gitlogue.syntax, so a change to gitlogue.syntax can break gitlogue.animation, while a change to gitlogue.animation can't break gitlogue.syntax.
- Position
- Below the diagonal: gitlogue.animation uses a module listed above it, which is the healthy direction.
37→2 gitlogue.main uses gitlogue.config✕
- Connections
- 1 pair of types, where a type in gitlogue.main uses a type in gitlogue.config.
- The types involved
gitlogue.main.main$module→gitlogue.config.Config
- Direction
- gitlogue.main uses gitlogue.config, so a change to gitlogue.config can break gitlogue.main, while a change to gitlogue.main can't break gitlogue.config.
- Position
- Below the diagonal: gitlogue.main uses a module listed above it, which is the healthy direction.
37→3 gitlogue.main uses gitlogue.git✕
- Connections
- 4 pairs of types, where a type in gitlogue.main uses a type in gitlogue.git.
- The types involved
gitlogue.main.CommitPlaybackPlan→gitlogue.git.CommitMetadatagitlogue.main.DiffPlaybackPlan→gitlogue.git.CommitMetadatagitlogue.main.DiffPlaybackPlan→gitlogue.git.DiffModegitlogue.main.main$module→gitlogue.git.GitRepository
- Direction
- gitlogue.main uses gitlogue.git, so a change to gitlogue.git can break gitlogue.main, while a change to gitlogue.main can't break gitlogue.git.
- Position
- Below the diagonal: gitlogue.main uses a module listed above it, which is the healthy direction.
37→14 gitlogue.main uses gitlogue.theme✕
- Connections
- 1 pair of types, where a type in gitlogue.main uses a type in gitlogue.theme.
- The types involved
gitlogue.main.RuntimeOptions→gitlogue.theme.Theme
- Direction
- gitlogue.main uses gitlogue.theme, so a change to gitlogue.theme can break gitlogue.main, while a change to gitlogue.main can't break gitlogue.theme.
- Position
- Below the diagonal: gitlogue.main uses a module listed above it, which is the healthy direction.
37→36 gitlogue.main uses gitlogue.animation✕
- Connections
- 2 pairs of types, where a type in gitlogue.main uses a type in gitlogue.animation.
- The types involved
gitlogue.main.RuntimeOptions→gitlogue.animation.SpeedRulegitlogue.main.main$module→gitlogue.animation.SpeedRule
- Direction
- gitlogue.main uses gitlogue.animation, so a change to gitlogue.animation can break gitlogue.main, while a change to gitlogue.main can't break gitlogue.animation.
- Position
- Below the diagonal: gitlogue.main uses a module listed above it, which is the healthy direction.
38→14 gitlogue.panes.editor uses gitlogue.theme✕
- Connections
- 2 pairs of types, where a type in gitlogue.panes.editor uses a type in gitlogue.theme.
- The types involved
gitlogue.panes.editor.EditorPane→gitlogue.theme.Themegitlogue.panes.editor.HighlightContext→gitlogue.theme.Theme
- Direction
- gitlogue.panes.editor uses gitlogue.theme, so a change to gitlogue.theme can break gitlogue.panes.editor, while a change to gitlogue.panes.editor can't break gitlogue.theme.
- Position
- Below the diagonal: gitlogue.panes.editor uses a module listed above it, which is the healthy direction.
38→36 gitlogue.panes.editor uses gitlogue.animation✕
- Connections
- 1 pair of types, where a type in gitlogue.panes.editor uses a type in gitlogue.animation.
- The types involved
gitlogue.panes.editor.EditorPane→gitlogue.animation.AnimationEngine
- Direction
- gitlogue.panes.editor uses gitlogue.animation, so a change to gitlogue.animation can break gitlogue.panes.editor, while a change to gitlogue.panes.editor can't break gitlogue.animation.
- Position
- Below the diagonal: gitlogue.panes.editor uses a module listed above it, which is the healthy direction.
39→14 gitlogue.panes.terminal uses gitlogue.theme✕
- Connections
- 1 pair of types, where a type in gitlogue.panes.terminal uses a type in gitlogue.theme.
- The types involved
gitlogue.panes.terminal.TerminalPane→gitlogue.theme.Theme
- Direction
- gitlogue.panes.terminal uses gitlogue.theme, so a change to gitlogue.theme can break gitlogue.panes.terminal, while a change to gitlogue.panes.terminal can't break gitlogue.theme.
- Position
- Below the diagonal: gitlogue.panes.terminal uses a module listed above it, which is the healthy direction.
39→36 gitlogue.panes.terminal uses gitlogue.animation✕
- Connections
- 1 pair of types, where a type in gitlogue.panes.terminal uses a type in gitlogue.animation.
- The types involved
gitlogue.panes.terminal.TerminalPane→gitlogue.animation.AnimationEngine
- Direction
- gitlogue.panes.terminal uses gitlogue.animation, so a change to gitlogue.animation can break gitlogue.panes.terminal, while a change to gitlogue.panes.terminal can't break gitlogue.animation.
- Position
- Below the diagonal: gitlogue.panes.terminal uses a module listed above it, which is the healthy direction.
40→3 gitlogue.ui uses gitlogue.git✕
- Connections
- 3 pairs of types, where a type in gitlogue.ui uses a type in gitlogue.git.
- The types involved
gitlogue.ui.UI→gitlogue.git.CommitMetadatagitlogue.ui.UI→gitlogue.git.DiffModegitlogue.ui.UI→gitlogue.git.GitRepository
- Direction
- gitlogue.ui uses gitlogue.git, so a change to gitlogue.git can break gitlogue.ui, while a change to gitlogue.ui can't break gitlogue.git.
- Position
- Below the diagonal: gitlogue.ui uses a module listed above it, which is the healthy direction.
40→14 gitlogue.ui uses gitlogue.theme✕
- Connections
- 1 pair of types, where a type in gitlogue.ui uses a type in gitlogue.theme.
- The types involved
gitlogue.ui.UI→gitlogue.theme.Theme
- Direction
- gitlogue.ui uses gitlogue.theme, so a change to gitlogue.theme can break gitlogue.ui, while a change to gitlogue.ui can't break gitlogue.theme.
- Position
- Below the diagonal: gitlogue.ui uses a module listed above it, which is the healthy direction.
40→15 gitlogue.ui uses gitlogue.panes.file_tree✕
- Connections
- 1 pair of types, where a type in gitlogue.ui uses a type in gitlogue.panes.file_tree.
- The types involved
gitlogue.ui.UI→gitlogue.panes.file_tree.FileTreePane
- Direction
- gitlogue.ui uses gitlogue.panes.file_tree, so a change to gitlogue.panes.file_tree can break gitlogue.ui, while a change to gitlogue.ui can't break gitlogue.panes.file_tree.
- Position
- Below the diagonal: gitlogue.ui uses a module listed above it, which is the healthy direction.
40→16 gitlogue.ui uses gitlogue.panes.status_bar✕
- Connections
- 1 pair of types, where a type in gitlogue.ui uses a type in gitlogue.panes.status_bar.
- The types involved
gitlogue.ui.UI→gitlogue.panes.status_bar.StatusBarPane
- Direction
- gitlogue.ui uses gitlogue.panes.status_bar, so a change to gitlogue.panes.status_bar can break gitlogue.ui, while a change to gitlogue.ui can't break gitlogue.panes.status_bar.
- Position
- Below the diagonal: gitlogue.ui uses a module listed above it, which is the healthy direction.
40→35 gitlogue.ui uses gitlogue.watch✕
- Connections
- 1 pair of types, where a type in gitlogue.ui uses a type in gitlogue.watch.
- The types involved
gitlogue.ui.UI→gitlogue.watch.CommitWatcher
- Direction
- gitlogue.ui uses gitlogue.watch, so a change to gitlogue.watch can break gitlogue.ui, while a change to gitlogue.ui can't break gitlogue.watch.
- Position
- Below the diagonal: gitlogue.ui uses a module listed above it, which is the healthy direction.
40→36 gitlogue.ui uses gitlogue.animation✕
- Connections
- 2 pairs of types, where a type in gitlogue.ui uses a type in gitlogue.animation.
- The types involved
gitlogue.ui.UI→gitlogue.animation.AnimationEnginegitlogue.ui.UI→gitlogue.animation.SpeedRule
- Direction
- gitlogue.ui uses gitlogue.animation, so a change to gitlogue.animation can break gitlogue.ui, while a change to gitlogue.ui can't break gitlogue.animation.
- Position
- Below the diagonal: gitlogue.ui uses a module listed above it, which is the healthy direction.
40→37 gitlogue.ui uses gitlogue.main✕
- Connections
- 1 pair of types, where a type in gitlogue.ui uses a type in gitlogue.main.
- The types involved
gitlogue.ui.UI→gitlogue.main.PlaybackOrder
- Direction
- gitlogue.ui uses gitlogue.main, so a change to gitlogue.main can break gitlogue.ui, while a change to gitlogue.ui can't break gitlogue.main.
- Position
- Below the diagonal: gitlogue.ui uses a module listed above it, which is the healthy direction.
40→38 gitlogue.ui uses gitlogue.panes.editor✕
- Connections
- 1 pair of types, where a type in gitlogue.ui uses a type in gitlogue.panes.editor.
- The types involved
gitlogue.ui.UI→gitlogue.panes.editor.EditorPane
- Direction
- gitlogue.ui uses gitlogue.panes.editor, so a change to gitlogue.panes.editor can break gitlogue.ui, while a change to gitlogue.ui can't break gitlogue.panes.editor.
- Position
- Below the diagonal: gitlogue.ui uses a module listed above it, which is the healthy direction.
40→39 gitlogue.ui uses gitlogue.panes.terminal✕
- Connections
- 1 pair of types, where a type in gitlogue.ui uses a type in gitlogue.panes.terminal.
- The types involved
gitlogue.ui.UI→gitlogue.panes.terminal.TerminalPane
- Direction
- gitlogue.ui uses gitlogue.panes.terminal, so a change to gitlogue.panes.terminal can break gitlogue.ui, while a change to gitlogue.ui can't break gitlogue.panes.terminal.
- Position
- Below the diagonal: gitlogue.ui uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Domain Modelling
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 39 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 15 | High / Critical |
Roadmap
Top priorities: Adopt a checker and raise it file by file: with Sorbet, `srb init` (or `bundle exec tapioca init`) commits `sorbet/config`, then move each file's sigil from `# typed: false` to `# typed: true` and on to `strict` as its methods get `sig`s — `spoom bump` does the moving; with Steep, write RBS signatures and `check` the product directories in the `Steepfile` under `D::Ruby.default` or `strict`, not `lenient`. Then pay down the assertions rather than adding to them: each `T.must` is a nil the checker could not rule out — narrow it (`return unless x`, `x&.`, `if (y = x)`), make the attribute non-nilable and set it in `initialize`, or change the method so the nil cannot arrive; Thread an AbortSignal through async functions that make requests, so the work stops when its caller gives up; 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.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Cargo.toml. | +2.1 pts | Low | ADR Quality |
| Adopt a checker and raise it file by file: with Sorbet, `srb init` (or `bundle exec tapioca init`) commits `sorbet/config`, then move each file's sigil from `# typed: false` to `# typed: true` and on to `strict` as its methods get `sig`s — `spoom bump` does the moving; with Steep, write RBS signatures and `check` the product directories in the `Steepfile` under `D::Ruby.default` or `strict`, not `lenient`. Then pay down the assertions rather than adding to them: each `T.must` is a nil the checker could not rule out — narrow it (`return unless x`, `x&.`, `if (y = x)`), make the attribute non-nilable and set it in `initialize`, or change the method so the nil cannot arrive. | +3.7 pts | Medium | Nullable reference types |
| Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. | +1.8 pts | Low | Static Analysis (SAST) |
| Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. | +1.8 pts | Low | Static Analysis (SAST) |
| Resolve the 1 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. | +1.8 pts | Low | Dependency Vulnerabilities |
| Thread an AbortSignal through async functions that make requests, so the work stops when its caller gives up. | +2.8 pts | Medium | Cancellation propagation |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +1.3 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +1.3 pts | Low | Supply-chain Provenance & Signing |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 1.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.1 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 5.9 | Mixed | Dependency Vulnerabilities: Medium advisory (unmaintained): REDACTED |
| src/git.rs | 7.0 | Near-clean | Cyclomatic Complexity: GitRepository::extract_changes (cyclomatic 26) |
| src/animation.rs | 7.0 | Near-clean | Cyclomatic Complexity: AnimationEngine::execute_step (cyclomatic 19) |
| src/ui.rs | 7.1 | Near-clean | Cognitive Complexity: UI::advance_to_next_commit (cognitive 18) |
| src/widgets/selectable_paragraph.rs | 7.1 | Near-clean | Cyclomatic Complexity: SelectableParagraph::render (cyclomatic 45) |
| REDACTED | 7.2 | Near-clean | Static Analysis (SAST): High: REDACTED |
| src/panes/file_tree.rs | 7.8 | Near-clean | Cyclomatic Complexity: FileTreePane::build_tree_lines (cyclomatic 18) |
| src/main.rs | 7.8 | Near-clean | God Classes: FileTooLong: src/main.rs |
| src/theme/themes/ayu_dark.rs | 7.8 | Near-clean | Code Duplication: Members sharing a duplicated core (17 members, 50+ identical tokens) |
| src/syntax/mod.rs | 8.5 | Near-clean | Cognitive Complexity: gitlogue::syntax::gather_injections (cognitive 16) |
| scripts/ogp/generate.js | 8.5 | Near-clean | God Classes: FunctionTooLong: generate.generateOGP |
| src/syntax/languages/mod.rs | 8.5 | Near-clean | God Classes: FunctionTooLong: gitlogue::syntax::languages::by_name |
| src/theme/mod.rs | 8.5 | Near-clean | God Classes: TooManyFields: Theme |
| src/config.rs | 8.5 | Near-clean | Code Duplication: Edited copy of a member (15 corresponding lines) |
| Cargo.toml | 9.5 | Near-clean | ADR Quality: No ADRs found |
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 43 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 — 43 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, 108 of 123 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 (20 contributor(s) across 617 commit(s) sampled, automation and bot accounts excluded). One of them holds 88% of the history; the other 19 hold 0.6% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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.
- 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.
- 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.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- 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.
- X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check'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.
- X3 Exception handling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check'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.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- 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.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- DM4 Rich vs anemic domain model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
4 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was SelectableParagraph::render at 45. A further 4 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 gitlogue::syntax::languages::resolve_language_kind at 35 — they are counted neither in the figure above nor in this dimension's score. 3 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/syntax/languages/mod.rs (gitlogue::syntax::languages::resolve_language_kind at 35), src/syntax/mod.rs (gitlogue::syntax::capture_name_to_token at 30), src/theme/mod.rs (Theme::load at 18). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 1 body over 30 down to 30 or less in Cyclomatic Complexity — start with SelectableParagraph::render (cyclomatic 45). — Refactoring it lifts Cyclomatic Complexity from 8.5 to about 9.0/10.
D2 · Cognitive Complexity
10 method(s) exceeded the cognitive complexity threshold of 15; the worst was SelectableParagraph::render at 134.
What to do
- Bring the 3 bodies over 30 down to 30 or less in Cognitive Complexity — start with SelectableParagraph::render (cognitive 134), GitRepository::extract_changes (cognitive 75), FileTreePane::build_tree_lines (cognitive 35). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 3 together lifts Cognitive Complexity from 5.8 to about 8.1/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
D3 · God Classes
17 god class(es) detected.
What to do
- Resolve the 4 FileTooLong finding(s) in God Classes — start with animation.rs, git.rs, ui.rs. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 3 ClassTooLong finding(s) in God Classes — start with animation.rs, ui.rs, git.rs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 3 MethodTooLong finding(s) in God Classes — start with animation.rs, selectable_paragraph.rs, git.rs. — One of this dimension's main actionable groups (3 warning-level).
D4 · Code Duplication
14 duplicated block group(s) detected. 11.3 % of the production lines (1,310 of 11,545) are in a reported copy. A further 7 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 Duplicated block (13 lines × 2) finding(s) in Code Duplication — start with git.rs, ui.rs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with animation.rs (2). — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Members sharing a duplicated core (17 members, 50+ identical tokens) finding(s) in Code Duplication — start with ayu_dark.rs. — One of this dimension's main actionable groups (1 warning-level).
D5 · Coupling
2 production modules (Cargo+npm), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 0 module(s) off the main sequence, with abstractness counted on 1 of the 2 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
D6 · Cohesion (LCOM4)
0 of 12 classes have LCOM4 above 3.
D8 · Code Coverage
Line coverage 96.1%. Measured from the Rust suite (repository root: `cargo test --workspace` instrumented over 65 production file(s), 3 test binaries and 0 doc-test binaries).
D11 · Test Reliability
0 flaky across 1 measured tier(s). Rust (repository root, 15 test files): measured (0 flaky).
D12 · Dependency Hygiene
4 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 300 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 ISC, which is its own choice and is not judged here.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window. Repeated repair below the complexity floor: src/ui.rs (4 of 7 changes were fixes)
What to do
- Resolve the 1 Repeated repair finding(s) in Churn × Complexity Hotspots — start with ui.rs. — One of this dimension's main actionable groups (1 warning-level).
D17 · Explicit Debt
0 deducted task-comment markers across 11545 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.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 9 document(s) read across 2 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Cargo.toml. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
0 of 2 build units (Cargo, npm) flagged as possibly oversized/incoherent.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
39 finding(s): 0 critical, 37 high, 2 medium, 0 low. 31 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 31 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 (31 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
8 finding(s): 0 critical, 1 high, 7 medium, 0 low.
What to do
- Resolve the 1 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 3 Medium advisory (unsound) finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
D34 · Knowledge Freshness
2 of 16 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/theme/themes/fluorite.rs. Counted over 16 of the 70 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 2 Orphaned file finding(s) in Knowledge Freshness — start with fluorite.rs, telemetry.rs. — One of this dimension's main actionable groups (2 recommendation-level).
- Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — 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. — 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
DM4 · Rich vs anemic domain model
M1 · Documentation (README)
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
- No logging or diagnostics emission found. This repository ships a binary its users launch rather than a service you operate, so there is no operator to page — but when a run fails on a user's machine, neither they nor you have anything to read.
What to do
- Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.
P3 · Security & performance tooling
- `REDACTED` schedules updates, but no `package-ecosystem` entry covers `github-actions`, `npm`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entries to the `updates:` list. — REDACTED:2
What to do
- Dependabot is configured but does not watch `github-actions`, `npm` — add those `package-ecosystem` entries to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
P6 · Release Hygiene
PF3 · Async & latency hygiene
X1 · Async correctness
X2 · Cancellation propagation
- Only 0/1 async functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
- `fetchFontFromGoogleFonts` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — scripts/ogp/generate.js:10
What to do
- Thread an AbortSignal through async functions that make requests, so the work stops when its caller gives up.
X21 · Side-effecting pattern guard
X5 · Nullable reference types
- This repository commits no Sorbet configuration (`sorbet/config`) and no `Steepfile`, so nothing type-checks its 1 Ruby product file(s): a nilable value reaches a method call silently and raises `NoMethodError: undefined method … for nil` the first time it is nil. A `# typed:` sigil does nothing without a `sorbet/config` beside the code; a Steep run configured only on a command line is not something this check can read.
What to do
- Adopt a checker and raise it file by file: with Sorbet, `srb init` (or `bundle exec tapioca init`) commits `sorbet/config`, then move each file's sigil from `# typed: false` to `# typed: true` and on to `strict` as its methods get `sig`s — `spoom bump` does the moving; with Steep, write RBS signatures and `check` the product directories in the `Steepfile` under `D::Ruby.default` or `strict`, not `lenient`. Then pay down the assertions rather than adding to them: each `T.must` is a nil the checker could not rule out — narrow it (`return unless x`, `x&.`, `if (y = x)`), make the attribute non-nilable and set it in `initialize`, or change the method so the nil cannot arrive.
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 53% | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 99% | Exemplary | Solid. |
| Maturity | 72% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 62% | Adequate — gated by P2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 44% | Weak — gated by D29, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 100% | Exemplary | Strongest area. |
| Performance | 100% | Exemplary | Solid. |
Unscored — 1 check(s) recorded observations but carry no score
- X7 Silent fallback defaults — 2 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 — 78 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: this repository's Ruby imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one.
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Ruby code is a Rails controller, a Sinatra, Grape or Roda app, a Hanami action or a Rack app (an instance `call(env)`), so no request handler shares state between request threads. Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written. 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 — no class or module declares an abstract method
- 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 — ~378 lines of test source are present (.rs, .rb) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (842 declarations, no unit with a dominant convention).
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed Rust surface was not measured.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .rb, .rs source were not judged.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.rs), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- 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
- 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 Aggregate boundaries — this Rust crate declares no domain aggregate (a struct with private state and its own command methods), so DM1's aggregate-boundary read has no population to be taken over
- DM2 Strongly-typed ids — no in-repo typed-id idiom — primitive-obsession recorded as advisory DM8, DM2 not gated
- DM3 Integration-event coupling — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
- DM5 Encapsulated state — this Rust crate declares no type implementing a hand-rolled Hash/PartialEq, so DM5's value-identity encapsulation read has no population to be taken over
- DM6 Domain ↔ infrastructure boundary — this Rust crate maps no type to a persistence framework (diesel/sea-orm/sqlx), so DM6's domain↔infrastructure fusion read has no population to be taken over
- DM7 Repository granularity — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P12 CI test-gate honesty — Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript, Ruby, 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 65 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.
- S1 Web-Security Posture — No web surface: 69 Rust file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation and obsolete TLS versions, and none was found. This repository serves no HTTP of its own — no HTTP-server crate (actix-web, axum, Rocket, warp, poem, tide, salvo, tonic, a hyper server, …) among its Cargo manifests' run-time dependencies, and no server started in its production source — so HTTPS enforcement, HSTS, cookie flags and input validation are N/A here, as they are for a C# library or worker. If this codebase starts serving HTTP, the dimension reactivates automatically.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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 4% of this repository's production lines — rust (11,514 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
- 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 — X24 reached only 4% of this repository's production lines — rust (11,514 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- 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 — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X27 Collection changed while being enumerated — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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 — X3 reached only 4% of this repository's production lines — rust (11,514 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- 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 Ruby was read, and it logs through none: the standard library's Logger, which Rails.logger is, takes one finished message and no template arguments or fields (as log4net does in C#), so an interpolated message there loses nothing the API could have kept. The console gem (`Console.info`), SemanticLogger, Ougai and dry-logger would be judged.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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 — 38 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 67 finding(s)
- FileTooLong: src/animation.rs src/animation.rs
- FileTooLong: src/git.rs src/git.rs
- FileTooLong: src/ui.rs src/ui.rs
- FileTooLong: src/main.rs src/main.rs
- GitRepository::extract_changes (cognitive 75) src/git.rs:634
- GitRepository::extract_hunks_from_diff (cognitive 30) src/git.rs:1016
- GitRepository::collect_commits_from_revwalk (cognitive 23) src/git.rs:517
- ClassTooLong: AnimationEngine src/animation.rs:269
- ClassTooLong: UI src/ui.rs:47
- ClassTooLong: GitRepository src/git.rs:186
- MethodTooLong: AnimationEngine.load_commit src/animation.rs:609
- MethodTooLong: SelectableParagraph.render src/widgets/selectable_paragraph.rs:167
- MethodTooLong: GitRepository.extract_changes src/git.rs:634
- TooManyMethods: UI src/ui.rs:47
- TooManyMethods: AnimationEngine src/animation.rs:269
- TooManyMethods: GitRepository src/git.rs:186
- REDACTED
- REDACTED
- REDACTED
- SelectableParagraph::render (cognitive 134) src/widgets/selectable_paragraph.rs:167
- SelectableParagraph::wrap_line (cognitive 21) src/widgets/selectable_paragraph.rs:96
- AnimationEngine::load_commit (cognitive 17) src/animation.rs:609
- AnimationEngine::generate_cursor_movement (cognitive 16) src/animation.rs:946
- REDACTED
- REDACTED
- FunctionTooLong: generate.generateOGP scripts/ogp/generate.js:26
- FunctionTooLong: gitlogue::syntax::languages::by_name src/syntax/languages/mod.rs:93
- TooManyFields: Theme src/theme/mod.rs:7
- TooManyFields: AnimationEngine src/animation.rs:269
- REDACTED
- REDACTED
- Duplicated block (13 lines × 2) src/git.rs:353
- Duplicated block (13 lines × 2) src/ui.rs:866
- Duplicated block (9 lines × 2) src/animation.rs:846
- Duplicated block (9 lines × 2) src/animation.rs:630
- SelectableParagraph::render (cyclomatic 45) src/widgets/selectable_paragraph.rs:167
- GitRepository::extract_changes (cyclomatic 26) src/git.rs:634
- AnimationEngine::execute_step (cyclomatic 19) src/animation.rs:1192
- FileTreePane::build_tree_lines (cyclomatic 18) src/panes/file_tree.rs:79
- Repeated repair: src/ui.rs src/ui.rs:475
- FileTreePane::build_tree_lines (cognitive 35) src/panes/file_tree.rs:79
- UI::advance_to_next_commit (cognitive 18) src/ui.rs:332
- gitlogue::syntax::gather_injections (cognitive 16) src/syntax/mod.rs:244
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Members sharing a duplicated core (17 members, 50+ identical tokens) src/theme/themes/ayu_dark.rs:5
- Edited copy of a member (31 corresponding lines) src/ui.rs:843
- Edited copies of one member (4 members, 19+ corresponding lines) src/git.rs:352
- Edited copy of a member (19 corresponding lines) src/main.rs:317
- Edited copy of a member (13 corresponding lines) src/git.rs:338
- Edited copy of a member (10 corresponding lines) src/git.rs:1004
- Edited copy of a member (15 corresponding lines) src/config.rs:232
- Duplicated block (58–59 lines × 2) src/git.rs:726
- Duplicated block (33–34 lines × 2) src/git.rs:787
- Duplicated block (27 lines × 2) src/git.rs:658
- Duplicated block (20–21 lines × 3) src/widgets/selectable_paragraph.rs:285
- Duplicated block (48 lines × 17) src/theme/themes/ayu_dark.rs:6
- Duplicated block (13–14 lines × 2) src/git.rs:688
- Duplicated block (12 lines × 2) src/animation.rs:92
- Duplicated block (10–11 lines × 3) src/animation.rs:688
- Duplicated block (11 lines × 2) src/git.rs:459
- Duplicated block (7–10 lines × 2) src/git.rs:368
- No structured logging
- Async function without AbortSignal: fetchFontFromGoogleFonts scripts/ogp/generate.js:10
Minor — 14 finding(s)
- Orphaned file src/theme/themes/fluorite.rs:1
- Orphaned file src/theme/themes/telemetry.rs:1
- Silent fallback default on Err src/git.rs:639
- Silent fallback default on Err src/syntax/mod.rs:329
- No ADRs found Cargo.toml:83
- Orphaned files with no living knowledge
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- Dependabot does not watch github-actions/npm REDACTED:2
- Not all async functions that make a request accept an AbortSignal
- Ruby's type checker does not check nil everywhere
Minor — 4 finding(s)
- Outdated: clap
- Outdated: toml
- Outdated: toml_edit
- Outdated: tree-sitter-scala
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-6f59defc64734fb29b23e28087ee7a60/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-6f59defc64734fb29b23e28087ee7a60/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 . | 39 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 8 | artifacts/raw/trivy-fs.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 | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |