Executive summary
skim-rs/skim meets our standard for production, though the project keeps no record of its design decisions. It scores 72 out of 100 and is rated Strong, and 52 of its 105 critical findings are security problems.
Maturity, at 68, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 4 points. Fixing the part of the code only one person knows comes next, also worth about 4. Raising Maturity to 70 would lift the score to about 73.
Thirty-eight pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Eight secrets can leak from the build pipeline, and two pipeline steps run downloads nobody checks. Pinning each tool to an exact version, limiting each secret to its own step and checking each download against a checksum would close these risks. Setting a waiting period for automatic updates would fix the automatic dependency update that takes a new release at once, and the two unsafe settings in infrastructure or container files need changing to safe values.
The product code is 22,687 lines, about €56,000 to rebuild.
If Maturity rose from 68 to 70, the lowest score rated Strong, the score would rise from 72 to about 73.
New since the last survey: 58 findings
- Cognitive Complexity · Preview::spawn_callback (cognitive 22) src/tui/preview.rs
- God Classes · ClassTooLong: Skim src/skim.rs
- Code Duplication · Near-duplicate member family (4 members, 21 shared lines) src/theme.rs
- Code Duplication · Near-duplicate member family (3 members, 6 shared lines) src/theme.rs
- Code Duplication · Duplicated block (12 lines × 4) src/theme.rs
- Code Duplication · Duplicated block (6 lines × 3) src/theme.rs
- Code Duplication · Duplicated block (6 lines × 2) src/fuzzy_matcher/fzy.rs
- Test Reliability · Flaky test: skim::ansi.test_ansi_hide_nth_searchable
- Test Reliability · Flaky test: skim::binds.bind_act_prefix
- Test Reliability · Flaky test: skim::binds.bind_change
- Test Reliability · Flaky test: skim::binds.bind_result
- Test Reliability · Flaky test: skim::binds.bind_set_query_basic
- Test Reliability · Flaky test: skim::binds.bind_set_query_expand
- Test Reliability · Flaky test: skim::case.case_ignore_different
- Test Reliability · Flaky test: skim::case.case_non_ascii
- Test Reliability · Flaky test: skim::case.case_respect_exact
- Test Reliability · Flaky test: skim::case.case_smart_exact
- Test Reliability · Flaky test: skim::case.case_smart_lower
- Test Reliability · Flaky test: skim::case.case_smart_no_match
- Test Reliability · Flaky test: skim::keys.keys_ctrl_arrows
- Test Reliability · Flaky test: skim::keys.keys_ctrl_c
- Test Reliability · Flaky test: skim::layout.layout_default
- Test Reliability · Flaky test: skim::layout.layout_reverse_border
- Test Reliability · Flaky test: skim::matcher.matcher_skim_v2
- Test Reliability · Flaky test: skim::multiline.multiline_custom_sep_comma
- Test Reliability · Flaky test: skim::multiline.multiline_layout_reverse_border
- Test Reliability · Flaky test: skim::multiline.multiline_tabstop_1
- Test Reliability · Flaky test: skim::multiline.multiline_tabstop_default
- Test Reliability · Flaky test: skim::multiline.multiline_with_header
- Test Reliability · Flaky test: skim::normalize.insta_no_normalize_accented_item
- Test Reliability · Flaky test: skim::normalize.insta_normalize_accented_item_unaccented_query
- Test Reliability · Flaky test: skim::normalize.insta_normalize_multiple_diacritics
- Test Reliability · Flaky test: skim::normalize.insta_normalize_suffix
- Test Reliability · Flaky test: skim::options.opt_border_rounded
- Test Reliability · Flaky test: skim::options.opt_no_info
- Test Reliability · Flaky test: skim::options.opt_nth_oob
- Test Reliability · Flaky test: skim::options.opt_null_delimiter_with_nth
- Test Reliability · Flaky test: skim::options.opt_separator_hidden
- Test Reliability · Flaky test: skim::options.opt_skip_to_pattern
- Test Reliability · Flaky test: skim::preview.preview_image_navigation
- Test Reliability · Flaky test: skim::preview.preview_image_window_down
- Test Reliability · Flaky test: skim::preview.preview_plus
- Test Reliability · Flaky test: skim::preview.preview_pty::preview_pty_offset_fixed
- Test Reliability · Flaky test: skim::preview.preview_pty::preview_pty_offset_fixed_and_expr
- Test Reliability · Flaky test: skim::preview.preview_pty::preview_pty_window_down
- Test Reliability · Flaky test: skim::preview.preview_window_up
- Test Reliability · Flaky test: skim::split_match.split_match_empty_after
- Test Reliability · Flaky test: skim::tiebreak.tiebreak_neg_score
- Test Reliability · Flaky test: skim::tiebreak.tiebreak_pathname
- Dependency Hygiene · Yanked release: tokio
- Churn × Complexity Hotspots · Hotspot: src/fuzzy_matcher/fzy.rs src/fuzzy_matcher/fzy.rs
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
Fixed since the last survey: 40 findings
- Code Duplication · Near-duplicate member family (4 members, 20 shared lines) src/theme.rs
- Code Duplication · Near-duplicate member family (3 members, 6 shared lines) src/theme.rs
- Code Duplication · Duplicated block (11 lines × 4) src/theme.rs
- Code Duplication · Duplicated block (7 lines × 2) src/fuzzy_matcher/fzy.rs
- Code Duplication · Duplicated block (6 lines × 3) src/theme.rs
- Test Reliability · Flaky test: skim::binds.bind_zero
- Test Reliability · Flaky test: skim::multiline.multiline_custom_sep_colon
- Test Reliability · Flaky test: skim::multiline.multiline_header_lines
- Test Reliability · Flaky test: skim::multiline.multiline_layout_reverse
- Test Reliability · Flaky test: skim::options.opt_border_quadrant_outside
- Test Reliability · Flaky test: skim::options.opt_cycle_header_lines
- Test Reliability · Flaky test: skim::options.opt_header_lines_inline_info
- Test Reliability · Flaky test: skim::options.opt_header_reverse_inline_info
- Test Reliability · Flaky test: skim::options.opt_hide_nth_hscroll
- Test Reliability · Flaky test: skim::options.opt_info_control
- Test Reliability · Flaky test: skim::options.opt_info_inline_custom
- Test Reliability · Flaky test: skim::options.opt_info_inline_right
- Test Reliability · Flaky test: skim::options.opt_multiple_flags_combined_nth
- Test Reliability · Flaky test: skim::options.opt_multiple_flags_combined_with_nth
- Test Reliability · Flaky test: skim::options.opt_multiple_flags_layout_and_reverse
- Test Reliability · Flaky test: skim::options.opt_multiple_flags_reverse_and_layout
- Test Reliability · Flaky test: skim::options.opt_nth_range_dec
- Test Reliability · Flaky test: skim::options.opt_read0
- Test Reliability · Flaky test: skim::options.opt_replstr
- Test Reliability · Flaky test: skim::options.opt_tabstop_3
- Test Reliability · Flaky test: skim::preview.preview_no_pty_linux
- Test Reliability · Flaky test: skim::preview.preview_offset_fixed
- Test Reliability · Flaky test: skim::preview.preview_preserve_quotes
- Test Reliability · Flaky test: skim::preview.preview_pty::preview_pty_offset_expr
- Test Reliability · Flaky test: skim::preview.preview_pty::preview_pty_window_up
- Test Reliability · Flaky test: skim::preview.preview_window_down
- Test Reliability · Flaky test: skim::preview.preview_window_left_neg
- Test Reliability · Flaky test: skim::split_match.split_match_both_parts
- Test Reliability · Flaky test: skim::split_match.split_match_multiple_delimiters_in_item
- Churn × Complexity Hotspots · Hotspot: src/binds.rs src/binds.rs
- Churn × Complexity Hotspots · Hotspot: src/tui/layout.rs src/tui/layout.rs
- Churn × Complexity Hotspots · Repeated repair: src/tui/backend.rs src/tui/backend.rs
- Supply-chain Provenance & Signing REDACTED
- Supply-chain Provenance & Signing REDACTED
- Supply-chain Provenance & Signing REDACTED
Rebuild cost: about €56,000 · Estimate
| Cost to rebuild | €19,000 to €94,000, for 311 to 987 hours of work, about 0.4 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 | ×1.1 at a score of 72. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Medium: 22,687 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 fuzzy_matcher | 2 fuzzy_matcher.arinae.banding | 3 thread_pool | 4 tui | 5 tui.event | 6 fuzzy_matcher.clangd | 7 theme | 8 tui.backend | 9 skim | 10 binds | 11 fuzzy_matcher.arinae | 12 fuzzy_matcher.arinae.algo | 13 fuzzy_matcher.frizbee | 14 fuzzy_matcher.skim | 15 tui.widget | 16 item | 17 skim_item | 18 tui.preview | 19 engine.all | 20 engine.exact | 21 engine.fuzzy | 22 engine.normalized | 23 engine.regexp | 24 engine.split | 25 engine.factory | 26 options | 27 output | 28 reader | 29 tui.header | 30 tui.input | 31 tui.item_list | 32 tui.layout | 33 bin.main | 34 helper.item_reader | 35 matcher | 36 popup | 37 tui.item_renderer | 38 popup.zellij | 39 tui.app | 40 skim |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 fuzzy_matcher | ||||||||||||||||||||||||||||||||||||||||
| 2 fuzzy_matcher.arinae.banding | ||||||||||||||||||||||||||||||||||||||||
| 3 thread_pool | ||||||||||||||||||||||||||||||||||||||||
| 4 tui | ||||||||||||||||||||||||||||||||||||||||
| 5 tui.event | ||||||||||||||||||||||||||||||||||||||||
| 6 fuzzy_matcher.clangd | 1 | |||||||||||||||||||||||||||||||||||||||
| 7 theme | 1 | |||||||||||||||||||||||||||||||||||||||
| 8 tui.backend | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 9 skim | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 10 binds | 1 | |||||||||||||||||||||||||||||||||||||||
| 11 fuzzy_matcher.arinae | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 12 fuzzy_matcher.arinae.algo | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 13 fuzzy_matcher.frizbee | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 14 fuzzy_matcher.skim | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 15 tui.widget | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 16 item | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 17 skim_item | 4 | |||||||||||||||||||||||||||||||||||||||
| 18 tui.preview | 3 | 1 | 1 | 1 | 2 | 2 | ||||||||||||||||||||||||||||||||||
| 19 engine.all | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 20 engine.exact | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 21 engine.fuzzy | 1 | 3 | 2 | |||||||||||||||||||||||||||||||||||||
| 22 engine.normalized | 1 | 3 | 1 | |||||||||||||||||||||||||||||||||||||
| 23 engine.regexp | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 24 engine.split | 1 | 3 | 1 | |||||||||||||||||||||||||||||||||||||
| 25 engine.factory | 3 | 4 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 26 options | 1 | 1 | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 27 output | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 28 reader | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 29 tui.header | 1 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 30 tui.input | 1 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 31 tui.item_list | 1 | 1 | 2 | 3 | 1 | |||||||||||||||||||||||||||||||||||
| 32 tui.layout | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 33 bin.main | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 34 helper.item_reader | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 35 matcher | 1 | 1 | 3 | 1 | 4 | |||||||||||||||||||||||||||||||||||
| 36 popup | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 37 tui.item_renderer | 1 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 38 popup.zellij | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 39 tui.app | 1 | 1 | 1 | 1 | 1 | 2 | 1 | 1 | 1 | 1 | 1 | 2 | 2 | |||||||||||||||||||||||||||
| 40 skim | 1 | 1 | 1 | 1 | 1 | 2 | 1 |
6→1 fuzzy_matcher.clangd uses fuzzy_matcher✕
- Connections
- 1 pair of types, where a type in fuzzy_matcher.clangd uses a type in fuzzy_matcher.
- The types involved
skim.fuzzy_matcher.clangd.ClangdMatcher→skim.fuzzy_matcher.FuzzyMatcher
- Direction
- fuzzy_matcher.clangd uses fuzzy_matcher, so a change to fuzzy_matcher can break fuzzy_matcher.clangd, while a change to fuzzy_matcher.clangd can't break fuzzy_matcher.
- Position
- Below the diagonal: fuzzy_matcher.clangd uses a module listed above it, which is the healthy direction.
7→26 theme uses options part of a loop✕
- Connections
- 1 pair of types, where a type in theme uses a type in options.
- The types involved
skim.theme.ColorTheme→skim.options.SkimOptions
- Direction
- theme uses options, so a change to options can break theme, while a change to theme can't break options.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→4 tui.backend uses tui✕
- Connections
- 1 pair of types, where a type in tui.backend uses a type in tui.
- The types involved
skim.tui.backend.Tui→skim.tui.Size
- Direction
- tui.backend uses tui, so a change to tui can break tui.backend, while a change to tui.backend can't break tui.
- Position
- Below the diagonal: tui.backend uses a module listed above it, which is the healthy direction.
8→5 tui.backend uses tui.event✕
- Connections
- 1 pair of types, where a type in tui.backend uses a type in tui.event.
- The types involved
skim.tui.backend.Tui→skim.tui.event.Event
- Direction
- tui.backend uses tui.event, so a change to tui.event can break tui.backend, while a change to tui.backend can't break tui.event.
- Position
- Below the diagonal: tui.backend uses a module listed above it, which is the healthy direction.
9→4 skim uses tui✕
- Connections
- 1 pair of types, where a type in skim uses a type in tui.
- The types involved
skim.PreviewPosition→skim.tui.Size
- Direction
- skim uses tui, so a change to tui can break skim, while a change to skim can't break tui.
- Position
- Below the diagonal: skim uses a module listed above it, which is the healthy direction.
9→6 skim uses fuzzy_matcher.clangd✕
- Connections
- 2 pairs of types, where a type in skim uses a type in fuzzy_matcher.clangd.
- The types involved
skim.CaseMatching→skim.fuzzy_matcher.clangd.CaseMatchingskim.MatchEngineFactory→skim.fuzzy_matcher.clangd.CaseMatching
- Direction
- skim uses fuzzy_matcher.clangd, so a change to fuzzy_matcher.clangd can break skim, while a change to skim can't break fuzzy_matcher.clangd.
- Position
- Below the diagonal: skim uses a module listed above it, which is the healthy direction.
10→6 binds uses fuzzy_matcher.clangd✕
- Connections
- 1 pair of types, where a type in binds uses a type in fuzzy_matcher.clangd.
- The types involved
skim.binds.KeyMap→skim.fuzzy_matcher.clangd.Action
- Direction
- binds uses fuzzy_matcher.clangd, so a change to fuzzy_matcher.clangd can break binds, while a change to binds can't break fuzzy_matcher.clangd.
- Position
- Below the diagonal: binds uses a module listed above it, which is the healthy direction.
11→1 fuzzy_matcher.arinae uses fuzzy_matcher✕
- Connections
- 1 pair of types, where a type in fuzzy_matcher.arinae uses a type in fuzzy_matcher.
- The types involved
skim.fuzzy_matcher.arinae.ArinaeMatcher→skim.fuzzy_matcher.FuzzyMatcher
- Direction
- fuzzy_matcher.arinae uses fuzzy_matcher, so a change to fuzzy_matcher can break fuzzy_matcher.arinae, while a change to fuzzy_matcher.arinae can't break fuzzy_matcher.
- Position
- Below the diagonal: fuzzy_matcher.arinae uses a module listed above it, which is the healthy direction.
11→2 fuzzy_matcher.arinae uses fuzzy_matcher.arinae.banding✕
- Connections
- 1 pair of types, where a type in fuzzy_matcher.arinae uses a type in fuzzy_matcher.arinae.banding.
- The types involved
skim.fuzzy_matcher.arinae.ArinaeMatcher→skim.fuzzy_matcher.arinae.banding.BandingInfo
- Direction
- fuzzy_matcher.arinae uses fuzzy_matcher.arinae.banding, so a change to fuzzy_matcher.arinae.banding can break fuzzy_matcher.arinae, while a change to fuzzy_matcher.arinae can't break fuzzy_matcher.arinae.banding.
- Position
- Below the diagonal: fuzzy_matcher.arinae uses a module listed above it, which is the healthy direction.
11→6 fuzzy_matcher.arinae uses fuzzy_matcher.clangd✕
- Connections
- 2 pairs of types, where a type in fuzzy_matcher.arinae uses a type in fuzzy_matcher.clangd.
- The types involved
skim.fuzzy_matcher.arinae.ArinaeMatcher→skim.fuzzy_matcher.clangd.CaseMatchingskim.fuzzy_matcher.arinae.arinae$module→skim.fuzzy_matcher.clangd.Score
- Direction
- fuzzy_matcher.arinae uses fuzzy_matcher.clangd, so a change to fuzzy_matcher.clangd can break fuzzy_matcher.arinae, while a change to fuzzy_matcher.arinae can't break fuzzy_matcher.clangd.
- Position
- Below the diagonal: fuzzy_matcher.arinae uses a module listed above it, which is the healthy direction.
12→2 fuzzy_matcher.arinae.algo uses fuzzy_matcher.arinae.banding✕
- Connections
- 1 pair of types, where a type in fuzzy_matcher.arinae.algo uses a type in fuzzy_matcher.arinae.banding.
- The types involved
skim.fuzzy_matcher.arinae.algo.algo$module→skim.fuzzy_matcher.arinae.banding.BandingInfo
- Direction
- fuzzy_matcher.arinae.algo uses fuzzy_matcher.arinae.banding, so a change to fuzzy_matcher.arinae.banding can break fuzzy_matcher.arinae.algo, while a change to fuzzy_matcher.arinae.algo can't break fuzzy_matcher.arinae.banding.
- Position
- Below the diagonal: fuzzy_matcher.arinae.algo uses a module listed above it, which is the healthy direction.
12→6 fuzzy_matcher.arinae.algo uses fuzzy_matcher.clangd✕
- Connections
- 1 pair of types, where a type in fuzzy_matcher.arinae.algo uses a type in fuzzy_matcher.clangd.
- The types involved
skim.fuzzy_matcher.arinae.algo.algo$module→skim.fuzzy_matcher.clangd.Score
- Direction
- fuzzy_matcher.arinae.algo uses fuzzy_matcher.clangd, so a change to fuzzy_matcher.clangd can break fuzzy_matcher.arinae.algo, while a change to fuzzy_matcher.arinae.algo can't break fuzzy_matcher.clangd.
- Position
- Below the diagonal: fuzzy_matcher.arinae.algo uses a module listed above it, which is the healthy direction.
13→1 fuzzy_matcher.frizbee uses fuzzy_matcher✕
- Connections
- 1 pair of types, where a type in fuzzy_matcher.frizbee uses a type in fuzzy_matcher.
- The types involved
skim.fuzzy_matcher.frizbee.FrizbeeMatcher→skim.fuzzy_matcher.FuzzyMatcher
- Direction
- fuzzy_matcher.frizbee uses fuzzy_matcher, so a change to fuzzy_matcher can break fuzzy_matcher.frizbee, while a change to fuzzy_matcher.frizbee can't break fuzzy_matcher.
- Position
- Below the diagonal: fuzzy_matcher.frizbee uses a module listed above it, which is the healthy direction.
13→6 fuzzy_matcher.frizbee uses fuzzy_matcher.clangd✕
- Connections
- 1 pair of types, where a type in fuzzy_matcher.frizbee uses a type in fuzzy_matcher.clangd.
- The types involved
skim.fuzzy_matcher.frizbee.FrizbeeMatcher→skim.fuzzy_matcher.clangd.CaseMatching
- Direction
- fuzzy_matcher.frizbee uses fuzzy_matcher.clangd, so a change to fuzzy_matcher.clangd can break fuzzy_matcher.frizbee, while a change to fuzzy_matcher.frizbee can't break fuzzy_matcher.clangd.
- Position
- Below the diagonal: fuzzy_matcher.frizbee uses a module listed above it, which is the healthy direction.
14→1 fuzzy_matcher.skim uses fuzzy_matcher✕
- Connections
- 1 pair of types, where a type in fuzzy_matcher.skim uses a type in fuzzy_matcher.
- The types involved
skim.fuzzy_matcher.skim.SkimMatcherV2→skim.fuzzy_matcher.FuzzyMatcher
- Direction
- fuzzy_matcher.skim uses fuzzy_matcher, so a change to fuzzy_matcher can break fuzzy_matcher.skim, while a change to fuzzy_matcher.skim can't break fuzzy_matcher.
- Position
- Below the diagonal: fuzzy_matcher.skim uses a module listed above it, which is the healthy direction.
14→6 fuzzy_matcher.skim uses fuzzy_matcher.clangd✕
- Connections
- 1 pair of types, where a type in fuzzy_matcher.skim uses a type in fuzzy_matcher.clangd.
- The types involved
skim.fuzzy_matcher.skim.SkimMatcherV2→skim.fuzzy_matcher.clangd.CaseMatching
- Direction
- fuzzy_matcher.skim uses fuzzy_matcher.clangd, so a change to fuzzy_matcher.clangd can break fuzzy_matcher.skim, while a change to fuzzy_matcher.skim can't break fuzzy_matcher.clangd.
- Position
- Below the diagonal: fuzzy_matcher.skim uses a module listed above it, which is the healthy direction.
15→7 tui.widget uses theme✕
- Connections
- 1 pair of types, where a type in tui.widget uses a type in theme.
- The types involved
skim.tui.widget.SkimWidget→skim.theme.ColorTheme
- Direction
- tui.widget uses theme, so a change to theme can break tui.widget, while a change to tui.widget can't break theme.
- Position
- Below the diagonal: tui.widget uses a module listed above it, which is the healthy direction.
15→26 tui.widget uses options part of a loop✕
- Connections
- 1 pair of types, where a type in tui.widget uses a type in options.
- The types involved
skim.tui.widget.SkimWidget→skim.options.SkimOptions
- Direction
- tui.widget uses options, so a change to options can break tui.widget, while a change to tui.widget can't break options.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→9 item uses skim✕
- Connections
- 3 pairs of types, where a type in item uses a type in skim.
- The types involved
skim.item.MatchedItem→skim.MatchRangeskim.item.MatchedItem→skim.Rankskim.item.RankBuilder→skim.Rank
- Direction
- item uses skim, so a change to skim can break item, while a change to item can't break skim.
- Position
- Below the diagonal: item uses a module listed above it, which is the healthy direction.
16→26 item uses options part of a loop✕
- Connections
- 1 pair of types, where a type in item uses a type in options.
- The types involved
skim.item.ItemPool→skim.options.SkimOptions
- Direction
- item uses options, so a change to options can break item, while a change to item can't break options.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→9 skim_item uses skim✕
- Connections
- 4 pairs of types, where a type in skim_item uses a type in skim.
- The types involved
skim.skim_item.SkimItem→skim.AsAnyskim.skim_item.SkimItem→skim.DisplayContextskim.skim_item.SkimItem→skim.ItemPreviewskim.skim_item.SkimItem→skim.PreviewContext
- Direction
- skim_item uses skim, so a change to skim can break skim_item, while a change to skim_item can't break skim.
- Position
- Below the diagonal: skim_item uses a module listed above it, which is the healthy direction.
18→4 tui.preview uses tui✕
- Connections
- 3 pairs of types, where a type in tui.preview uses a type in tui.
- The types involved
skim.tui.preview.Preview→skim.tui.BorderTypeskim.tui.preview.Preview→skim.tui.Directionskim.tui.preview.Preview→skim.tui.Size
- Direction
- tui.preview uses tui, so a change to tui can break tui.preview, while a change to tui.preview can't break tui.
- Position
- Below the diagonal: tui.preview uses a module listed above it, which is the healthy direction.
18→7 tui.preview uses theme✕
- Connections
- 1 pair of types, where a type in tui.preview uses a type in theme.
- The types involved
skim.tui.preview.Preview→skim.theme.ColorTheme
- Direction
- tui.preview uses theme, so a change to theme can break tui.preview, while a change to tui.preview can't break theme.
- Position
- Below the diagonal: tui.preview uses a module listed above it, which is the healthy direction.
18→8 tui.preview uses tui.backend✕
- Connections
- 1 pair of types, where a type in tui.preview uses a type in tui.backend.
- The types involved
skim.tui.preview.Preview→skim.tui.backend.Tui
- Direction
- tui.preview uses tui.backend, so a change to tui.backend can break tui.preview, while a change to tui.preview can't break tui.backend.
- Position
- Below the diagonal: tui.preview uses a module listed above it, which is the healthy direction.
18→9 tui.preview uses skim✕
- Connections
- 1 pair of types, where a type in tui.preview uses a type in skim.
- The types involved
skim.tui.preview.Preview→skim.PreviewPosition
- Direction
- tui.preview uses skim, so a change to skim can break tui.preview, while a change to tui.preview can't break skim.
- Position
- Below the diagonal: tui.preview uses a module listed above it, which is the healthy direction.
18→15 tui.preview uses tui.widget✕
- Connections
- 2 pairs of types, where a type in tui.preview uses a type in tui.widget.
- The types involved
skim.tui.preview.Preview→skim.tui.widget.SkimRenderskim.tui.preview.Preview→skim.tui.widget.SkimWidget
- Direction
- tui.preview uses tui.widget, so a change to tui.widget can break tui.preview, while a change to tui.preview can't break tui.widget.
- Position
- Below the diagonal: tui.preview uses a module listed above it, which is the healthy direction.
18→26 tui.preview uses options part of a loop✕
- Connections
- 2 pairs of types, where a type in tui.preview uses a type in options.
- The types involved
skim.tui.preview.Preview→skim.options.ImageProtocolskim.tui.preview.Preview→skim.options.SkimOptions
- Direction
- tui.preview uses options, so a change to options can break tui.preview, while a change to tui.preview can't break options.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→9 engine.all uses skim✕
- Connections
- 2 pairs of types, where a type in engine.all uses a type in skim.
- The types involved
skim.engine.all.MatchAllEngine→skim.MatchEngineskim.engine.all.MatchAllEngine→skim.MatchResult
- Direction
- engine.all uses skim, so a change to skim can break engine.all, while a change to engine.all can't break skim.
- Position
- Below the diagonal: engine.all uses a module listed above it, which is the healthy direction.
19→16 engine.all uses item✕
- Connections
- 1 pair of types, where a type in engine.all uses a type in item.
- The types involved
skim.engine.all.MatchAllEngine→skim.item.RankBuilder
- Direction
- engine.all uses item, so a change to item can break engine.all, while a change to engine.all can't break item.
- Position
- Below the diagonal: engine.all uses a module listed above it, which is the healthy direction.
20→6 engine.exact uses fuzzy_matcher.clangd✕
- Connections
- 1 pair of types, where a type in engine.exact uses a type in fuzzy_matcher.clangd.
- The types involved
skim.engine.exact.ExactMatchingParam→skim.fuzzy_matcher.clangd.CaseMatching
- Direction
- engine.exact uses fuzzy_matcher.clangd, so a change to fuzzy_matcher.clangd can break engine.exact, while a change to engine.exact can't break fuzzy_matcher.clangd.
- Position
- Below the diagonal: engine.exact uses a module listed above it, which is the healthy direction.
20→9 engine.exact uses skim✕
- Connections
- 2 pairs of types, where a type in engine.exact uses a type in skim.
- The types involved
skim.engine.exact.ExactEngine→skim.MatchEngineskim.engine.exact.ExactEngine→skim.MatchResult
- Direction
- engine.exact uses skim, so a change to skim can break engine.exact, while a change to engine.exact can't break skim.
- Position
- Below the diagonal: engine.exact uses a module listed above it, which is the healthy direction.
20→16 engine.exact uses item✕
- Connections
- 1 pair of types, where a type in engine.exact uses a type in item.
- The types involved
skim.engine.exact.ExactEngine→skim.item.RankBuilder
- Direction
- engine.exact uses item, so a change to item can break engine.exact, while a change to engine.exact can't break item.
- Position
- Below the diagonal: engine.exact uses a module listed above it, which is the healthy direction.
21→6 engine.fuzzy uses fuzzy_matcher.clangd✕
- Connections
- 1 pair of types, where a type in engine.fuzzy uses a type in fuzzy_matcher.clangd.
- The types involved
skim.engine.fuzzy.FuzzyEngineBuilder→skim.fuzzy_matcher.clangd.CaseMatching
- Direction
- engine.fuzzy uses fuzzy_matcher.clangd, so a change to fuzzy_matcher.clangd can break engine.fuzzy, while a change to engine.fuzzy can't break fuzzy_matcher.clangd.
- Position
- Below the diagonal: engine.fuzzy uses a module listed above it, which is the healthy direction.
21→9 engine.fuzzy uses skim✕
- Connections
- 3 pairs of types, where a type in engine.fuzzy uses a type in skim.
- The types involved
skim.engine.fuzzy.FuzzyEngine→skim.MatchEngineskim.engine.fuzzy.FuzzyEngine→skim.MatchResultskim.engine.fuzzy.FuzzyEngineBuilder→skim.Typos
- Direction
- engine.fuzzy uses skim, so a change to skim can break engine.fuzzy, while a change to engine.fuzzy can't break skim.
- Position
- Below the diagonal: engine.fuzzy uses a module listed above it, which is the healthy direction.
21→16 engine.fuzzy uses item✕
- Connections
- 2 pairs of types, where a type in engine.fuzzy uses a type in item.
- The types involved
skim.engine.fuzzy.FuzzyEngine→skim.item.RankBuilderskim.engine.fuzzy.FuzzyEngineBuilder→skim.item.RankBuilder
- Direction
- engine.fuzzy uses item, so a change to item can break engine.fuzzy, while a change to engine.fuzzy can't break item.
- Position
- Below the diagonal: engine.fuzzy uses a module listed above it, which is the healthy direction.
22→6 engine.normalized uses fuzzy_matcher.clangd✕
- Connections
- 1 pair of types, where a type in engine.normalized uses a type in fuzzy_matcher.clangd.
- The types involved
skim.engine.normalized.NormalizedEngineFactory→skim.fuzzy_matcher.clangd.CaseMatching
- Direction
- engine.normalized uses fuzzy_matcher.clangd, so a change to fuzzy_matcher.clangd can break engine.normalized, while a change to engine.normalized can't break fuzzy_matcher.clangd.
- Position
- Below the diagonal: engine.normalized uses a module listed above it, which is the healthy direction.
22→9 engine.normalized uses skim✕
- Connections
- 3 pairs of types, where a type in engine.normalized uses a type in skim.
- The types involved
skim.engine.normalized.NormalizedEngine→skim.MatchEngineskim.engine.normalized.NormalizedEngine→skim.MatchResultskim.engine.normalized.NormalizedEngineFactory→skim.MatchEngineFactory
- Direction
- engine.normalized uses skim, so a change to skim can break engine.normalized, while a change to engine.normalized can't break skim.
- Position
- Below the diagonal: engine.normalized uses a module listed above it, which is the healthy direction.
22→17 engine.normalized uses skim_item✕
- Connections
- 1 pair of types, where a type in engine.normalized uses a type in skim_item.
- The types involved
skim.engine.normalized.NormalizedItem→skim.skim_item.SkimItem
- Direction
- engine.normalized uses skim_item, so a change to skim_item can break engine.normalized, while a change to engine.normalized can't break skim_item.
- Position
- Below the diagonal: engine.normalized uses a module listed above it, which is the healthy direction.
23→6 engine.regexp uses fuzzy_matcher.clangd✕
- Connections
- 1 pair of types, where a type in engine.regexp uses a type in fuzzy_matcher.clangd.
- The types involved
skim.engine.regexp.RegexEngine→skim.fuzzy_matcher.clangd.CaseMatching
- Direction
- engine.regexp uses fuzzy_matcher.clangd, so a change to fuzzy_matcher.clangd can break engine.regexp, while a change to engine.regexp can't break fuzzy_matcher.clangd.
- Position
- Below the diagonal: engine.regexp uses a module listed above it, which is the healthy direction.
23→9 engine.regexp uses skim✕
- Connections
- 2 pairs of types, where a type in engine.regexp uses a type in skim.
- The types involved
skim.engine.regexp.RegexEngine→skim.MatchEngineskim.engine.regexp.RegexEngine→skim.MatchResult
- Direction
- engine.regexp uses skim, so a change to skim can break engine.regexp, while a change to engine.regexp can't break skim.
- Position
- Below the diagonal: engine.regexp uses a module listed above it, which is the healthy direction.
23→16 engine.regexp uses item✕
- Connections
- 1 pair of types, where a type in engine.regexp uses a type in item.
- The types involved
skim.engine.regexp.RegexEngine→skim.item.RankBuilder
- Direction
- engine.regexp uses item, so a change to item can break engine.regexp, while a change to engine.regexp can't break item.
- Position
- Below the diagonal: engine.regexp uses a module listed above it, which is the healthy direction.
24→6 engine.split uses fuzzy_matcher.clangd✕
- Connections
- 1 pair of types, where a type in engine.split uses a type in fuzzy_matcher.clangd.
- The types involved
skim.engine.split.SplitMatchEngineFactory→skim.fuzzy_matcher.clangd.CaseMatching
- Direction
- engine.split uses fuzzy_matcher.clangd, so a change to fuzzy_matcher.clangd can break engine.split, while a change to engine.split can't break fuzzy_matcher.clangd.
- Position
- Below the diagonal: engine.split uses a module listed above it, which is the healthy direction.
24→9 engine.split uses skim✕
- Connections
- 3 pairs of types, where a type in engine.split uses a type in skim.
- The types involved
skim.engine.split.SplitMatchEngine→skim.MatchEngineskim.engine.split.SplitMatchEngine→skim.MatchResultskim.engine.split.SplitMatchEngineFactory→skim.MatchEngineFactory
- Direction
- engine.split uses skim, so a change to skim can break engine.split, while a change to engine.split can't break skim.
- Position
- Below the diagonal: engine.split uses a module listed above it, which is the healthy direction.
24→17 engine.split uses skim_item✕
- Connections
- 1 pair of types, where a type in engine.split uses a type in skim_item.
- The types involved
skim.engine.split.StringItem→skim.skim_item.SkimItem
- Direction
- engine.split uses skim_item, so a change to skim_item can break engine.split, while a change to engine.split can't break skim_item.
- Position
- Below the diagonal: engine.split uses a module listed above it, which is the healthy direction.
25→6 engine.factory uses fuzzy_matcher.clangd✕
- Connections
- 3 pairs of types, where a type in engine.factory uses a type in fuzzy_matcher.clangd.
- The types involved
skim.engine.factory.AndOrEngineFactory→skim.fuzzy_matcher.clangd.CaseMatchingskim.engine.factory.ExactOrFuzzyEngineFactory→skim.fuzzy_matcher.clangd.CaseMatchingskim.engine.factory.RegexEngineFactory→skim.fuzzy_matcher.clangd.CaseMatching
- Direction
- engine.factory uses fuzzy_matcher.clangd, so a change to fuzzy_matcher.clangd can break engine.factory, while a change to engine.factory can't break fuzzy_matcher.clangd.
- Position
- Below the diagonal: engine.factory uses a module listed above it, which is the healthy direction.
25→9 engine.factory uses skim✕
- Connections
- 4 pairs of types, where a type in engine.factory uses a type in skim.
- The types involved
skim.engine.factory.AndOrEngineFactory→skim.MatchEngineFactoryskim.engine.factory.ExactOrFuzzyEngineFactory→skim.MatchEngineFactoryskim.engine.factory.ExactOrFuzzyEngineFactory→skim.Typosskim.engine.factory.RegexEngineFactory→skim.MatchEngineFactory
- Direction
- engine.factory uses skim, so a change to skim can break engine.factory, while a change to engine.factory can't break skim.
- Position
- Below the diagonal: engine.factory uses a module listed above it, which is the healthy direction.
25→16 engine.factory uses item✕
- Connections
- 2 pairs of types, where a type in engine.factory uses a type in item.
- The types involved
skim.engine.factory.ExactOrFuzzyEngineFactory→skim.item.RankBuilderskim.engine.factory.RegexEngineFactory→skim.item.RankBuilder
- Direction
- engine.factory uses item, so a change to item can break engine.factory, while a change to engine.factory can't break item.
- Position
- Below the diagonal: engine.factory uses a module listed above it, which is the healthy direction.
25→21 engine.factory uses engine.fuzzy✕
- Connections
- 1 pair of types, where a type in engine.factory uses a type in engine.fuzzy.
- The types involved
skim.engine.factory.ExactOrFuzzyEngineFactory→skim.engine.fuzzy.FuzzyAlgorithm
- Direction
- engine.factory uses engine.fuzzy, so a change to engine.fuzzy can break engine.factory, while a change to engine.factory can't break engine.fuzzy.
- Position
- Below the diagonal: engine.factory uses a module listed above it, which is the healthy direction.
26→4 options uses tui✕
- Connections
- 1 pair of types, where a type in options uses a type in tui.
- The types involved
skim.options.SkimOptions→skim.tui.BorderType
- Direction
- options uses tui, so a change to tui can break options, while a change to options can't break tui.
- Position
- Below the diagonal: options uses a module listed above it, which is the healthy direction.
26→6 options uses fuzzy_matcher.clangd✕
- Connections
- 1 pair of types, where a type in options uses a type in fuzzy_matcher.clangd.
- The types involved
skim.options.SkimOptions→skim.fuzzy_matcher.clangd.CaseMatching
- Direction
- options uses fuzzy_matcher.clangd, so a change to fuzzy_matcher.clangd can break options, while a change to options can't break fuzzy_matcher.clangd.
- Position
- Below the diagonal: options uses a module listed above it, which is the healthy direction.
26→9 options uses skim✕
- Connections
- 1 pair of types, where a type in options uses a type in skim.
- The types involved
skim.options.SkimOptions→skim.Typos
- Direction
- options uses skim, so a change to skim can break options, while a change to options can't break skim.
- Position
- Below the diagonal: options uses a module listed above it, which is the healthy direction.
26→10 options uses binds✕
- Connections
- 1 pair of types, where a type in options uses a type in binds.
- The types involved
skim.options.SkimOptions→skim.binds.KeyMap
- Direction
- options uses binds, so a change to binds can break options, while a change to options can't break binds.
- Position
- Below the diagonal: options uses a module listed above it, which is the healthy direction.
26→16 options uses item✕
- Connections
- 1 pair of types, where a type in options uses a type in item.
- The types involved
skim.options.SkimOptions→skim.item.RankCriteria
- Direction
- options uses item, so a change to item can break options, while a change to options can't break item.
- Position
- Below the diagonal: options uses a module listed above it, which is the healthy direction.
26→18 options uses tui.preview✕
- Connections
- 1 pair of types, where a type in options uses a type in tui.preview.
- The types involved
skim.options.SkimOptions→skim.tui.preview.PreviewCallback
- Direction
- options uses tui.preview, so a change to tui.preview can break options, while a change to options can't break tui.preview.
- Position
- Below the diagonal: options uses a module listed above it, which is the healthy direction.
26→21 options uses engine.fuzzy✕
- Connections
- 1 pair of types, where a type in options uses a type in engine.fuzzy.
- The types involved
skim.options.SkimOptions→skim.engine.fuzzy.FuzzyAlgorithm
- Direction
- options uses engine.fuzzy, so a change to engine.fuzzy can break options, while a change to options can't break engine.fuzzy.
- Position
- Below the diagonal: options uses a module listed above it, which is the healthy direction.
27→5 output uses tui.event✕
- Connections
- 1 pair of types, where a type in output uses a type in tui.event.
- The types involved
skim.output.SkimOutput→skim.tui.event.Event
- Direction
- output uses tui.event, so a change to tui.event can break output, while a change to output can't break tui.event.
- Position
- Below the diagonal: output uses a module listed above it, which is the healthy direction.
27→16 output uses item✕
- Connections
- 1 pair of types, where a type in output uses a type in item.
- The types involved
skim.output.SkimOutput→skim.item.MatchedItem
- Direction
- output uses item, so a change to item can break output, while a change to output can't break item.
- Position
- Below the diagonal: output uses a module listed above it, which is the healthy direction.
27→26 output uses options✕
- Connections
- 1 pair of types, where a type in output uses a type in options.
- The types involved
skim.output.BinOptions→skim.options.SkimOptions
- Direction
- output uses options, so a change to options can break output, while a change to output can't break options.
- Position
- Below the diagonal: output uses a module listed above it, which is the healthy direction.
28→3 reader uses thread_pool✕
- Connections
- 2 pairs of types, where a type in reader uses a type in thread_pool.
- The types involved
skim.reader.CommandCollector→skim.thread_pool.ThreadPoolskim.reader.Reader→skim.thread_pool.ThreadPool
- Direction
- reader uses thread_pool, so a change to thread_pool can break reader, while a change to reader can't break thread_pool.
- Position
- Below the diagonal: reader uses a module listed above it, which is the healthy direction.
28→16 reader uses item✕
- Connections
- 1 pair of types, where a type in reader uses a type in item.
- The types involved
skim.reader.Reader→skim.item.ItemPool
- Direction
- reader uses item, so a change to item can break reader, while a change to reader can't break item.
- Position
- Below the diagonal: reader uses a module listed above it, which is the healthy direction.
28→26 reader uses options✕
- Connections
- 1 pair of types, where a type in reader uses a type in options.
- The types involved
skim.reader.Reader→skim.options.SkimOptions
- Direction
- reader uses options, so a change to options can break reader, while a change to reader can't break options.
- Position
- Below the diagonal: reader uses a module listed above it, which is the healthy direction.
29→4 tui.header uses tui✕
- Connections
- 1 pair of types, where a type in tui.header uses a type in tui.
- The types involved
skim.tui.header.Header→skim.tui.BorderType
- Direction
- tui.header uses tui, so a change to tui can break tui.header, while a change to tui.header can't break tui.
- Position
- Below the diagonal: tui.header uses a module listed above it, which is the healthy direction.
29→7 tui.header uses theme✕
- Connections
- 1 pair of types, where a type in tui.header uses a type in theme.
- The types involved
skim.tui.header.Header→skim.theme.ColorTheme
- Direction
- tui.header uses theme, so a change to theme can break tui.header, while a change to tui.header can't break theme.
- Position
- Below the diagonal: tui.header uses a module listed above it, which is the healthy direction.
29→15 tui.header uses tui.widget✕
- Connections
- 2 pairs of types, where a type in tui.header uses a type in tui.widget.
- The types involved
skim.tui.header.Header→skim.tui.widget.SkimRenderskim.tui.header.Header→skim.tui.widget.SkimWidget
- Direction
- tui.header uses tui.widget, so a change to tui.widget can break tui.header, while a change to tui.header can't break tui.widget.
- Position
- Below the diagonal: tui.header uses a module listed above it, which is the healthy direction.
29→26 tui.header uses options✕
- Connections
- 1 pair of types, where a type in tui.header uses a type in options.
- The types involved
skim.tui.header.Header→skim.options.SkimOptions
- Direction
- tui.header uses options, so a change to options can break tui.header, while a change to tui.header can't break options.
- Position
- Below the diagonal: tui.header uses a module listed above it, which is the healthy direction.
30→4 tui.input uses tui✕
- Connections
- 1 pair of types, where a type in tui.input uses a type in tui.
- The types involved
skim.tui.input.Input→skim.tui.BorderType
- Direction
- tui.input uses tui, so a change to tui can break tui.input, while a change to tui.input can't break tui.
- Position
- Below the diagonal: tui.input uses a module listed above it, which is the healthy direction.
30→7 tui.input uses theme✕
- Connections
- 1 pair of types, where a type in tui.input uses a type in theme.
- The types involved
skim.tui.input.Input→skim.theme.ColorTheme
- Direction
- tui.input uses theme, so a change to theme can break tui.input, while a change to tui.input can't break theme.
- Position
- Below the diagonal: tui.input uses a module listed above it, which is the healthy direction.
30→15 tui.input uses tui.widget✕
- Connections
- 2 pairs of types, where a type in tui.input uses a type in tui.widget.
- The types involved
skim.tui.input.Input→skim.tui.widget.SkimRenderskim.tui.input.Input→skim.tui.widget.SkimWidget
- Direction
- tui.input uses tui.widget, so a change to tui.widget can break tui.input, while a change to tui.input can't break tui.widget.
- Position
- Below the diagonal: tui.input uses a module listed above it, which is the healthy direction.
30→26 tui.input uses options✕
- Connections
- 1 pair of types, where a type in tui.input uses a type in options.
- The types involved
skim.tui.input.Input→skim.options.SkimOptions
- Direction
- tui.input uses options, so a change to options can break tui.input, while a change to tui.input can't break options.
- Position
- Below the diagonal: tui.input uses a module listed above it, which is the healthy direction.
31→4 tui.item_list uses tui✕
- Connections
- 1 pair of types, where a type in tui.item_list uses a type in tui.
- The types involved
skim.tui.item_list.ItemList→skim.tui.BorderType
- Direction
- tui.item_list uses tui, so a change to tui can break tui.item_list, while a change to tui.item_list can't break tui.
- Position
- Below the diagonal: tui.item_list uses a module listed above it, which is the healthy direction.
31→7 tui.item_list uses theme✕
- Connections
- 1 pair of types, where a type in tui.item_list uses a type in theme.
- The types involved
skim.tui.item_list.ItemList→skim.theme.ColorTheme
- Direction
- tui.item_list uses theme, so a change to theme can break tui.item_list, while a change to tui.item_list can't break theme.
- Position
- Below the diagonal: tui.item_list uses a module listed above it, which is the healthy direction.
31→15 tui.item_list uses tui.widget✕
- Connections
- 2 pairs of types, where a type in tui.item_list uses a type in tui.widget.
- The types involved
skim.tui.item_list.ItemList→skim.tui.widget.SkimRenderskim.tui.item_list.ItemList→skim.tui.widget.SkimWidget
- Direction
- tui.item_list uses tui.widget, so a change to tui.widget can break tui.item_list, while a change to tui.item_list can't break tui.widget.
- Position
- Below the diagonal: tui.item_list uses a module listed above it, which is the healthy direction.
31→16 tui.item_list uses item✕
- Connections
- 3 pairs of types, where a type in tui.item_list uses a type in item.
- The types involved
skim.tui.item_list.ItemList→skim.item.MatchedItemskim.tui.item_list.ProcessedItems→skim.item.MatchedItemskim.tui.item_list.item_list$module→skim.item.MatchedItem
- Direction
- tui.item_list uses item, so a change to item can break tui.item_list, while a change to tui.item_list can't break item.
- Position
- Below the diagonal: tui.item_list uses a module listed above it, which is the healthy direction.
31→26 tui.item_list uses options✕
- Connections
- 1 pair of types, where a type in tui.item_list uses a type in options.
- The types involved
skim.tui.item_list.ItemList→skim.options.SkimOptions
- Direction
- tui.item_list uses options, so a change to options can break tui.item_list, while a change to tui.item_list can't break options.
- Position
- Below the diagonal: tui.item_list uses a module listed above it, which is the healthy direction.
32→4 tui.layout uses tui✕
- Connections
- 1 pair of types, where a type in tui.layout uses a type in tui.
- The types involved
skim.tui.layout.layout$module→skim.tui.Size
- Direction
- tui.layout uses tui, so a change to tui can break tui.layout, while a change to tui.layout can't break tui.
- Position
- Below the diagonal: tui.layout uses a module listed above it, which is the healthy direction.
32→26 tui.layout uses options✕
- Connections
- 2 pairs of types, where a type in tui.layout uses a type in options.
- The types involved
skim.tui.layout.AppLayout→skim.options.SkimOptionsskim.tui.layout.LayoutTemplate→skim.options.SkimOptions
- Direction
- tui.layout uses options, so a change to options can break tui.layout, while a change to tui.layout can't break options.
- Position
- Below the diagonal: tui.layout uses a module listed above it, which is the healthy direction.
33→26 bin.main uses options✕
- Connections
- 1 pair of types, where a type in bin.main uses a type in options.
- The types involved
skim.bin.main.main$module→skim.options.SkimOptions
- Direction
- bin.main uses options, so a change to options can break bin.main, while a change to bin.main can't break options.
- Position
- Below the diagonal: bin.main uses a module listed above it, which is the healthy direction.
33→27 bin.main uses output✕
- Connections
- 1 pair of types, where a type in bin.main uses a type in output.
- The types involved
skim.bin.main.main$module→skim.output.SkimOutput
- Direction
- bin.main uses output, so a change to output can break bin.main, while a change to bin.main can't break output.
- Position
- Below the diagonal: bin.main uses a module listed above it, which is the healthy direction.
34→3 helper.item_reader uses thread_pool✕
- Connections
- 2 pairs of types, where a type in helper.item_reader uses a type in thread_pool.
- The types involved
skim.helper.item_reader.SkimItemReader→skim.thread_pool.ThreadPoolskim.helper.item_reader.item_reader$module→skim.thread_pool.ThreadPool
- Direction
- helper.item_reader uses thread_pool, so a change to thread_pool can break helper.item_reader, while a change to helper.item_reader can't break thread_pool.
- Position
- Below the diagonal: helper.item_reader uses a module listed above it, which is the healthy direction.
34→26 helper.item_reader uses options✕
- Connections
- 1 pair of types, where a type in helper.item_reader uses a type in options.
- The types involved
skim.helper.item_reader.SkimItemReaderOption→skim.options.SkimOptions
- Direction
- helper.item_reader uses options, so a change to options can break helper.item_reader, while a change to helper.item_reader can't break options.
- Position
- Below the diagonal: helper.item_reader uses a module listed above it, which is the healthy direction.
34→28 helper.item_reader uses reader✕
- Connections
- 1 pair of types, where a type in helper.item_reader uses a type in reader.
- The types involved
skim.helper.item_reader.SkimItemReader→skim.reader.CommandCollector
- Direction
- helper.item_reader uses reader, so a change to reader can break helper.item_reader, while a change to helper.item_reader can't break reader.
- Position
- Below the diagonal: helper.item_reader uses a module listed above it, which is the healthy direction.
35→3 matcher uses thread_pool✕
- Connections
- 1 pair of types, where a type in matcher uses a type in thread_pool.
- The types involved
skim.matcher.Matcher→skim.thread_pool.ThreadPool
- Direction
- matcher uses thread_pool, so a change to thread_pool can break matcher, while a change to matcher can't break thread_pool.
- Position
- Below the diagonal: matcher uses a module listed above it, which is the healthy direction.
35→6 matcher uses fuzzy_matcher.clangd✕
- Connections
- 1 pair of types, where a type in matcher uses a type in fuzzy_matcher.clangd.
- The types involved
skim.matcher.Matcher→skim.fuzzy_matcher.clangd.CaseMatching
- Direction
- matcher uses fuzzy_matcher.clangd, so a change to fuzzy_matcher.clangd can break matcher, while a change to matcher can't break fuzzy_matcher.clangd.
- Position
- Below the diagonal: matcher uses a module listed above it, which is the healthy direction.
35→16 matcher uses item✕
- Connections
- 3 pairs of types, where a type in matcher uses a type in item.
- The types involved
skim.matcher.Matcher→skim.item.ItemPoolskim.matcher.Matcher→skim.item.RankBuilderskim.matcher.matcher$module→skim.item.MatchedItem
- Direction
- matcher uses item, so a change to item can break matcher, while a change to matcher can't break item.
- Position
- Below the diagonal: matcher uses a module listed above it, which is the healthy direction.
35→26 matcher uses options✕
- Connections
- 1 pair of types, where a type in matcher uses a type in options.
- The types involved
skim.matcher.Matcher→skim.options.SkimOptions
- Direction
- matcher uses options, so a change to options can break matcher, while a change to matcher can't break options.
- Position
- Below the diagonal: matcher uses a module listed above it, which is the healthy direction.
35→31 matcher uses tui.item_list✕
- Connections
- 4 pairs of types, where a type in matcher uses a type in tui.item_list.
- The types involved
skim.matcher.Matcher→skim.tui.item_list.MergeStrategyskim.matcher.Matcher→skim.tui.item_list.ProcessedItemsskim.matcher.matcher$module→skim.tui.item_list.MergeStrategyskim.matcher.matcher$module→skim.tui.item_list.ProcessedItems
- Direction
- matcher uses tui.item_list, so a change to tui.item_list can break matcher, while a change to matcher can't break tui.item_list.
- Position
- Below the diagonal: matcher uses a module listed above it, which is the healthy direction.
36→17 popup uses skim_item✕
- Connections
- 1 pair of types, where a type in popup uses a type in skim_item.
- The types involved
skim.popup.SkimPopupOutput→skim.skim_item.SkimItem
- Direction
- popup uses skim_item, so a change to skim_item can break popup, while a change to popup can't break skim_item.
- Position
- Below the diagonal: popup uses a module listed above it, which is the healthy direction.
36→26 popup uses options✕
- Connections
- 2 pairs of types, where a type in popup uses a type in options.
- The types involved
skim.popup.SkimPopup→skim.options.SkimOptionsskim.popup.popup$module→skim.options.SkimOptions
- Direction
- popup uses options, so a change to options can break popup, while a change to popup can't break options.
- Position
- Below the diagonal: popup uses a module listed above it, which is the healthy direction.
36→27 popup uses output✕
- Connections
- 1 pair of types, where a type in popup uses a type in output.
- The types involved
skim.popup.popup$module→skim.output.SkimOutput
- Direction
- popup uses output, so a change to output can break popup, while a change to popup can't break output.
- Position
- Below the diagonal: popup uses a module listed above it, which is the healthy direction.
37→7 tui.item_renderer uses theme✕
- Connections
- 1 pair of types, where a type in tui.item_renderer uses a type in theme.
- The types involved
skim.tui.item_renderer.ItemRenderer→skim.theme.ColorTheme
- Direction
- tui.item_renderer uses theme, so a change to theme can break tui.item_renderer, while a change to tui.item_renderer can't break theme.
- Position
- Below the diagonal: tui.item_renderer uses a module listed above it, which is the healthy direction.
37→9 tui.item_renderer uses skim✕
- Connections
- 2 pairs of types, where a type in tui.item_renderer uses a type in skim.
- The types involved
skim.tui.item_renderer.ItemRenderer→skim.MatchRangeskim.tui.item_renderer.ItemRenderer→skim.Matches
- Direction
- tui.item_renderer uses skim, so a change to skim can break tui.item_renderer, while a change to tui.item_renderer can't break skim.
- Position
- Below the diagonal: tui.item_renderer uses a module listed above it, which is the healthy direction.
37→16 tui.item_renderer uses item✕
- Connections
- 1 pair of types, where a type in tui.item_renderer uses a type in item.
- The types involved
skim.tui.item_renderer.ItemRenderer→skim.item.MatchedItem
- Direction
- tui.item_renderer uses item, so a change to item can break tui.item_renderer, while a change to tui.item_renderer can't break item.
- Position
- Below the diagonal: tui.item_renderer uses a module listed above it, which is the healthy direction.
37→31 tui.item_renderer uses tui.item_list✕
- Connections
- 1 pair of types, where a type in tui.item_renderer uses a type in tui.item_list.
- The types involved
skim.tui.item_renderer.ItemRenderer→skim.tui.item_list.ItemList
- Direction
- tui.item_renderer uses tui.item_list, so a change to tui.item_list can break tui.item_renderer, while a change to tui.item_renderer can't break tui.item_list.
- Position
- Below the diagonal: tui.item_renderer uses a module listed above it, which is the healthy direction.
38→4 popup.zellij uses tui✕
- Connections
- 1 pair of types, where a type in popup.zellij uses a type in tui.
- The types involved
skim.popup.zellij.zellij$module→skim.tui.Size
- Direction
- popup.zellij uses tui, so a change to tui can break popup.zellij, while a change to popup.zellij can't break tui.
- Position
- Below the diagonal: popup.zellij uses a module listed above it, which is the healthy direction.
38→26 popup.zellij uses options✕
- Connections
- 1 pair of types, where a type in popup.zellij uses a type in options.
- The types involved
skim.popup.zellij.ZellijPopup→skim.options.SkimOptions
- Direction
- popup.zellij uses options, so a change to options can break popup.zellij, while a change to popup.zellij can't break options.
- Position
- Below the diagonal: popup.zellij uses a module listed above it, which is the healthy direction.
38→36 popup.zellij uses popup✕
- Connections
- 1 pair of types, where a type in popup.zellij uses a type in popup.
- The types involved
skim.popup.zellij.ZellijPopup→skim.popup.SkimPopup
- Direction
- popup.zellij uses popup, so a change to popup can break popup.zellij, while a change to popup.zellij can't break popup.
- Position
- Below the diagonal: popup.zellij uses a module listed above it, which is the healthy direction.
39→3 tui.app uses thread_pool✕
- Connections
- 1 pair of types, where a type in tui.app uses a type in thread_pool.
- The types involved
skim.tui.app.App→skim.thread_pool.ThreadPool
- Direction
- tui.app uses thread_pool, so a change to thread_pool can break tui.app, while a change to tui.app can't break thread_pool.
- Position
- Below the diagonal: tui.app uses a module listed above it, which is the healthy direction.
39→5 tui.app uses tui.event✕
- Connections
- 1 pair of types, where a type in tui.app uses a type in tui.event.
- The types involved
skim.tui.app.App→skim.tui.event.Event
- Direction
- tui.app uses tui.event, so a change to tui.event can break tui.app, while a change to tui.app can't break tui.event.
- Position
- Below the diagonal: tui.app uses a module listed above it, which is the healthy direction.
39→6 tui.app uses fuzzy_matcher.clangd✕
- Connections
- 1 pair of types, where a type in tui.app uses a type in fuzzy_matcher.clangd.
- The types involved
skim.tui.app.App→skim.fuzzy_matcher.clangd.Action
- Direction
- tui.app uses fuzzy_matcher.clangd, so a change to fuzzy_matcher.clangd can break tui.app, while a change to tui.app can't break fuzzy_matcher.clangd.
- Position
- Below the diagonal: tui.app uses a module listed above it, which is the healthy direction.
39→7 tui.app uses theme✕
- Connections
- 1 pair of types, where a type in tui.app uses a type in theme.
- The types involved
skim.tui.app.App→skim.theme.ColorTheme
- Direction
- tui.app uses theme, so a change to theme can break tui.app, while a change to tui.app can't break theme.
- Position
- Below the diagonal: tui.app uses a module listed above it, which is the healthy direction.
39→8 tui.app uses tui.backend✕
- Connections
- 1 pair of types, where a type in tui.app uses a type in tui.backend.
- The types involved
skim.tui.app.App→skim.tui.backend.Tui
- Direction
- tui.app uses tui.backend, so a change to tui.backend can break tui.app, while a change to tui.app can't break tui.backend.
- Position
- Below the diagonal: tui.app uses a module listed above it, which is the healthy direction.
39→16 tui.app uses item✕
- Connections
- 2 pairs of types, where a type in tui.app uses a type in item.
- The types involved
skim.tui.app.App→skim.item.ItemPoolskim.tui.app.App→skim.item.MatchedItem
- Direction
- tui.app uses item, so a change to item can break tui.app, while a change to tui.app can't break item.
- Position
- Below the diagonal: tui.app uses a module listed above it, which is the healthy direction.
39→18 tui.app uses tui.preview✕
- Connections
- 1 pair of types, where a type in tui.app uses a type in tui.preview.
- The types involved
skim.tui.app.App→skim.tui.preview.Preview
- Direction
- tui.app uses tui.preview, so a change to tui.preview can break tui.app, while a change to tui.app can't break tui.preview.
- Position
- Below the diagonal: tui.app uses a module listed above it, which is the healthy direction.
39→26 tui.app uses options✕
- Connections
- 1 pair of types, where a type in tui.app uses a type in options.
- The types involved
skim.tui.app.App→skim.options.SkimOptions
- Direction
- tui.app uses options, so a change to options can break tui.app, while a change to tui.app can't break options.
- Position
- Below the diagonal: tui.app uses a module listed above it, which is the healthy direction.
39→29 tui.app uses tui.header✕
- Connections
- 1 pair of types, where a type in tui.app uses a type in tui.header.
- The types involved
skim.tui.app.App→skim.tui.header.Header
- Direction
- tui.app uses tui.header, so a change to tui.header can break tui.app, while a change to tui.app can't break tui.header.
- Position
- Below the diagonal: tui.app uses a module listed above it, which is the healthy direction.
39→30 tui.app uses tui.input✕
- Connections
- 1 pair of types, where a type in tui.app uses a type in tui.input.
- The types involved
skim.tui.app.App→skim.tui.input.Input
- Direction
- tui.app uses tui.input, so a change to tui.input can break tui.app, while a change to tui.app can't break tui.input.
- Position
- Below the diagonal: tui.app uses a module listed above it, which is the healthy direction.
39→31 tui.app uses tui.item_list✕
- Connections
- 1 pair of types, where a type in tui.app uses a type in tui.item_list.
- The types involved
skim.tui.app.App→skim.tui.item_list.ItemList
- Direction
- tui.app uses tui.item_list, so a change to tui.item_list can break tui.app, while a change to tui.app can't break tui.item_list.
- Position
- Below the diagonal: tui.app uses a module listed above it, which is the healthy direction.
39→32 tui.app uses tui.layout✕
- Connections
- 2 pairs of types, where a type in tui.app uses a type in tui.layout.
- The types involved
skim.tui.app.App→skim.tui.layout.AppLayoutskim.tui.app.App→skim.tui.layout.LayoutTemplate
- Direction
- tui.app uses tui.layout, so a change to tui.layout can break tui.app, while a change to tui.app can't break tui.layout.
- Position
- Below the diagonal: tui.app uses a module listed above it, which is the healthy direction.
39→35 tui.app uses matcher✕
- Connections
- 2 pairs of types, where a type in tui.app uses a type in matcher.
- The types involved
skim.tui.app.App→skim.matcher.Matcherskim.tui.app.App→skim.matcher.MatcherControl
- Direction
- tui.app uses matcher, so a change to matcher can break tui.app, while a change to tui.app can't break matcher.
- Position
- Below the diagonal: tui.app uses a module listed above it, which is the healthy direction.
40→4 skim uses tui✕
- Connections
- 1 pair of types, where a type in skim uses a type in tui.
- The types involved
skim.skim.Skim→skim.tui.Size
- Direction
- skim uses tui, so a change to tui can break skim, while a change to skim can't break tui.
- Position
- Below the diagonal: skim uses a module listed above it, which is the healthy direction.
40→5 skim uses tui.event✕
- Connections
- 1 pair of types, where a type in skim uses a type in tui.event.
- The types involved
skim.skim.Skim→skim.tui.event.Event
- Direction
- skim uses tui.event, so a change to tui.event can break skim, while a change to skim can't break tui.event.
- Position
- Below the diagonal: skim uses a module listed above it, which is the healthy direction.
40→8 skim uses tui.backend✕
- Connections
- 1 pair of types, where a type in skim uses a type in tui.backend.
- The types involved
skim.skim.Skim→skim.tui.backend.Tui
- Direction
- skim uses tui.backend, so a change to tui.backend can break skim, while a change to skim can't break tui.backend.
- Position
- Below the diagonal: skim uses a module listed above it, which is the healthy direction.
40→26 skim uses options✕
- Connections
- 1 pair of types, where a type in skim uses a type in options.
- The types involved
skim.skim.Skim→skim.options.SkimOptions
- Direction
- skim uses options, so a change to options can break skim, while a change to skim can't break options.
- Position
- Below the diagonal: skim uses a module listed above it, which is the healthy direction.
40→27 skim uses output✕
- Connections
- 1 pair of types, where a type in skim uses a type in output.
- The types involved
skim.skim.Skim→skim.output.SkimOutput
- Direction
- skim uses output, so a change to output can break skim, while a change to skim can't break output.
- Position
- Below the diagonal: skim uses a module listed above it, which is the healthy direction.
40→28 skim uses reader✕
- Connections
- 2 pairs of types, where a type in skim uses a type in reader.
- The types involved
skim.skim.Skim→skim.reader.Readerskim.skim.Skim→skim.reader.ReaderControl
- Direction
- skim uses reader, so a change to reader can break skim, while a change to skim can't break reader.
- Position
- Below the diagonal: skim uses a module listed above it, which is the healthy direction.
40→39 skim uses tui.app✕
- Connections
- 1 pair of types, where a type in skim uses a type in tui.app.
- The types involved
skim.skim.Skim→skim.tui.app.App
- Direction
- skim uses tui.app, so a change to tui.app can break skim, while a change to skim can't break tui.app.
- Position
- Below the diagonal: skim uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 50 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 12 | Medium |
| A02:2025 — Security Misconfiguration | 4 | High / Critical |
Roadmap
Begin by addressing the absence of Architecture Decision Records to properly document significant design choices and mitigate bus factor risks associated with off-boarding. Next, stabilize the development process by resolving the numerous flaky tests that undermine confidence in the codebase. Finally, implement a draft release or approval gate to ensure that bad builds are stopped before they reach users, enabling safe and rapid deployments.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +4.2 pts | Low | ADR Quality |
| Resolve the 1 Off-boarding risk finding(s) in Bus Factor. | +3.6 pts | Low | Bus Factor |
| 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. | +4.0 pts | Medium | Architecture documentation |
| Resolve the 53 Flaky test finding(s) in Test Reliability. | +3.3 pts | Medium | Test Reliability |
| Resolve the 1 Yanked release finding(s) in Dependency Hygiene. | +1.4 pts | Low | Dependency Hygiene |
| Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it. | +1.7 pts | Medium | Deployment & Rollback |
| Resolve the 5 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (5). | +0.7 pts | Low | Static Analysis (SAST) |
| Resolve the 7 Hotspot finding(s) in Churn × Complexity Hotspots — start with app.rs, options.rs, skim.rs. | +1.0 pts | High | Churn × Complexity Hotspots |
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 | 2.7 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 6.9 | Mixed | Dependency Vulnerabilities: Medium CVE: REDACTED |
| src/tui/app.rs | 7.0 | Mixed | Cyclomatic Complexity: App::dispatch_action (cyclomatic 102) |
| src/fuzzy_matcher/fzy.rs | 7.0 | Mixed | Cyclomatic Complexity: skim::fuzzy_matcher::fzy::fzy_score_typos_full (cyclomatic 40) |
| src/fuzzy_matcher/arinae/algo.rs | 7.0 | Mixed | Cyclomatic Complexity: skim::fuzzy_matcher::arinae::algo::range_dp (cyclomatic 35) |
| src/theme.rs | 7.0 | Mixed | Cyclomatic Complexity: ColorTheme::set_color (cyclomatic 37) |
| src/tui/preview.rs | 7.0 | Mixed | Cyclomatic Complexity: Preview::spawn (cyclomatic 34) |
| src/helper/item.rs | 7.0 | Mixed | Cyclomatic Complexity: DefaultSkimItem::display (cyclomatic 29) |
| src/options.rs | 7.1 | Mixed | Cyclomatic Complexity: SkimOptions::build (cyclomatic 20) |
| src/tui/item_list.rs | 7.2 | Mixed | Cyclomatic Complexity: ItemList::render (cyclomatic 25) |
| src/tui/util.rs | 7.2 | Mixed | Cyclomatic Complexity: skim::tui::util::detect_image_picker (cyclomatic 22) |
| src/skim.rs | 7.2 | Mixed | Cyclomatic Complexity: Skim::should_enter (cyclomatic 16) |
| src/fuzzy_matcher/clangd.rs | 7.2 | Mixed | Cognitive Complexity: skim::fuzzy_matcher::clangd::build_graph (cognitive 35) |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 49 of 49 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
What we checked — 49 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, 200 of 266 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Watchdog duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
| LLM (sampled · advisory) | Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement | — | ◐ LLM · sampled · advisory |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.rs) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage read, produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
- D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D24 Comment Value — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D27 Navigability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- AX6 Interface segregation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AXR1 Runtime accessibility — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via Dockerfile (REDACTED). docker build failed (exit 1) — ------ REDACTED:1 -------------------- 1 | >>> FROM rust:1-slim 2 | 3 | RUN apt-get update && apt-get install -y tmux bsdmainutils && apt-get clean -------------------- ERROR: failed to solve: rust:1-slim: failed to resolve source metadata for docker.io/library/rust:1-slim: failed to do request: Head "https://registry-1.docker.io/v2/library/rust/manifests/1-slim": Forbidden; runtime evidence skipped.
- GD1 Unfinished & placeholder code — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- M4 Documentation accuracy — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9). 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X13 Undrained process stream — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X16 Unfloored truncation loop — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X17 Uncapped recursion over a caller-supplied document — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X18 Disposal-pattern correctness — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X19 Unrestored process-global state — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X22 Contradicted release guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Java, TypeScript/JavaScript, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X23 Unguarded diagnostic materialisation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X24 Document value interpolated into markup unescaped — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X25 Inert configuration knob — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart and Ruby source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart or Ruby was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X3 Exception handling — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go and JavaScript/TypeScript source only, and no C# was loaded and no PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go, JavaScript or TypeScript was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X5 Nullable reference types — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax and MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, and Kotlin source only, and no C# was loaded, no TypeScript was found, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D11 Test Reliability: Flakiness is inferred from history/markers — Watchdog runs the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
22 function(s) exceeded the cyclomatic complexity threshold of 15; the worst was App::dispatch_action at 102. A further 1 function(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being skim::manpage::key_name at 25 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold functions was excluded, so the exclusion is disclosed nowhere in the file itself: src/manpage.rs (skim::manpage::key_name at 25). 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 60 down to 60 or less in Cyclomatic Complexity — start with App::dispatch_action (cyclomatic 102). — Refactoring it lifts Cyclomatic Complexity from 5.7 to about 6.4/10.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
43 function(s) exceeded the cognitive complexity threshold of 15; the worst was skim::fuzzy_matcher::fzy::fzy_score_typos_full at 128.
What to do
- Bring the 16 bodies over 30 down to 30 or less in Cognitive Complexity — start with skim::fuzzy_matcher::fzy::fzy_score_typos_full (cognitive 128), skim::util::printf (cognitive 87), skim::fuzzy_matcher::fzy::fzy_score_typos_rolling (cognitive 85). — 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 16 together lifts Cognitive Complexity from 2.4 to about 6.2/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
22 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 5 MethodTooLong finding(s) in God Classes — start with app.rs, preview.rs, options.rs. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 5 ClassTooLong finding(s) in God Classes — start with app.rs, options.rs, preview.rs. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 5 FunctionTooLong finding(s) in God Classes — start with algo.rs (2), mod.rs, fzy.rs. — One of this dimension's main actionable groups (5 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
33 duplicated block group(s) detected. A further 5 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.
What to do
- Resolve the 4 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with clangd.rs (2), app.rs (2). — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 4 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with exact.rs, split.rs, algo.rs. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 2 Near-duplicate member pair (52 shared lines) finding(s) in Code Duplication — start with fzy.rs (2). — One of this dimension's main actionable groups (2 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
0 of 54 classes have LCOM4 above 3.
D9 · Test Distribution
1014 test methods: 921 unit, 93 integration, 0 BDD, 0 e2e. The Rust suite contributes 1014 `#[test]` function(s) across 65 file(s) declaring at least one; its unit/integration split is Cargo's own — 10 of those file(s) are integration-test targets under a crate's tests/ directory, and the rest are #[test] functions compiled into the crate they test.
D11 · Test Reliability
53 flaky across 1 measured tier(s). Rust (repository root, 65 test files): measured (53 flaky).
What to do
- Resolve the 53 Flaky test finding(s) in Test Reliability. — One of this dimension's main actionable groups (53 issue-level).
D12 · Dependency Hygiene
2 outdated, 1 yanked direct Cargo dependencies. 40 of 42 direct crates were graded against crates.io (0 not published there, 2 not resolved by a committed REDACTED). 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.
What to do
- Resolve the 1 Yanked release finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 348 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository's REDACTED closed over its manifests' `[dependencies]` and `[build-dependencies]`. Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository. This repository publishes itself under MIT, which is its own choice and is not judged here.
D15 · Churn × Complexity Hotspots
Top hotspots: src/tui/app.rs (8×102=816); src/options.rs (9×20=180); src/skim.rs (9×16=144)
What to do
- Resolve the 7 Hotspot finding(s) in Churn × Complexity Hotspots — start with app.rs, options.rs, skim.rs. — One of this dimension's main actionable groups (7 warning-level).
D16 · Bus Factor
30 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is src/tui/app.rs. Counted over 59 of the 72 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 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
D17 · Explicit Debt
1 deducted task-comment markers across 22687 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 1 TodoComment finding(s) in Explicit Debt — start with listen.rs. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 3 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
1 of 1 build units (Cargo) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
50 finding(s): 0 critical, 50 high, 0 medium, 0 low. 38 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. semgrep hit a parse error in 1 file(s) — `bin/sk-tmux` (line 125) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 3 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 5 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (5). — One of this dimension's main actionable groups (5 issue-level).
- Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 issue-level).
- No action in Static Analysis (SAST) — all 38 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 (38 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
2 finding(s): 0 critical, 0 high, 2 medium, 0 low.
What to do
- Resolve the 1 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Medium vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D31 · IaC & Container Security
4 finding(s): 0 critical, 2 high, 2 medium, 0 low.
What to do
- Resolve the 2 High IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 2 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 59 of the 72 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 2 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX4 · Dependency direction
AX9 · CQS / query purity
M1 · Documentation (README)
What to do
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
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
P3 · Security & performance tooling
What to do
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
What to do
- Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
P6 · Release Hygiene
PF1 · Benchmark discipline
PF3 · Async & latency hygiene
X1 · Async correctness
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X21 · Side-effecting pattern guard
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X30 · Support guard that admits what it rejects
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 84% | Adequate — gated by D2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 88% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 68% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 70% | Adequate — gated by D11 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 75% | Adequate — gated by D29, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 94% | Exemplary | Strongest area. |
Unscored — 3 check(s) recorded observations but carry no score
- P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
- X7 Silent fallback defaults — 3 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X9 Subsumed condition operand — 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 — 67 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one.
- AX2 Stateful singletons — Not applicable: Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — docker build failed (exit 1) — ------ REDACTED:1 -------------------- 1 | >>> FROM rust:1-slim 2 | 3 | RUN apt-get update && apt-get install -y tmux bsdmainutils && apt-get clean -------------------- ERROR: failed to solve: rust:1-slim: failed to resolve source metadata for docker.io/library/rust:1-slim: failed to do request: Head "https://registry-1.docker.io/v2/library/rust/manifests/1-slim": Forbidden; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no data at rest for these controls to protect.
- C2 Access Controls — No access-control surface detected in the analyzed source — this repository starts no server another machine can reach (no actix-web HttpServer, axum::serve, Rocket launch, warp::serve, poem or salvo Server, tonic Server::builder, hyper or tiny_http server outside examples and tests, none bound beyond loopback). Access control is therefore N/A here — a crate is authorized by the application that serves it, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~18139 lines of test source are present (.rs) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — Naming consistency is measured on C# only; Rust not measured.
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed Rust surface was not measured.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ projects each declaring an entity of their own. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C# and Visual Basic comments only — this repository's production source is .rs, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.rs), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- 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.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D5 Coupling — Not applicable — this Cargo build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (8 value object(s))
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the Rust source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF2 Allocation hygiene — Not applicable: Rust spells out every heap allocation and makes borrowed slices (&[T], &str) its ordinary parameter types, so the allocation-aware style this card rewards elsewhere is the language's baseline rather than a rung to climb.
- S1 Web-Security Posture — No web surface: 67 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.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X12 Unreachable branch — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X13 Undrained process stream — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X16 Unfloored truncation loop — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X17 Uncapped recursion over a caller-supplied document — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X18 Disposal-pattern correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X19 Unrestored process-global state — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X2 Cancellation propagation — no C# was loaded; this repository's Rust was read, and no request in it can be cancelled by a caller — a Rust request takes no token: a future is cancelled by dropping it, from outside the call (select!, a timeout, an aborted task), and reqwest, hyper and tonic take none
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X22 Contradicted release guard — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X23 Unguarded diagnostic materialisation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X24 Document value interpolated into markup unescaped — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X25 Inert configuration knob — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. Rust's compiler refuses the unsynchronised version: a collection shared between a callback's thread and the waiting body must be `Sync`, which a `Vec`, `VecDeque` or `HashMap` is only behind a `Mutex`/`RwLock`, so the race this check looks for cannot be written in safe Rust. Not a gap in the analyzer and not a finding about your code.
- X3 Exception handling — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Rust was read, and it logs through none: the `log` crate's macros take one finished message (as log4net does in C#; its `kv` values are an opt-in its backends mostly drop), `println!`/`eprintln!` are not loggers, or it makes no log call outside its tests and examples at all. Calls through `tracing` (`tracing::info!`, or `info!` imported from it) would be judged.
- X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 105 finding(s)
- Flaky test: skim::ansi.test_ansi_hide_nth_searchable
- Flaky test: skim::binds.bind_act_prefix
- Flaky test: skim::binds.bind_change
- Flaky test: skim::binds.bind_result
- Flaky test: skim::binds.bind_set_query_basic
- Flaky test: skim::binds.bind_set_query_expand
- Flaky test: skim::case.case_ignore_different
- Flaky test: skim::case.case_non_ascii
- Flaky test: skim::case.case_respect_exact
- Flaky test: skim::case.case_smart_exact
- Flaky test: skim::case.case_smart_lower
- Flaky test: skim::case.case_smart_no_match
- Flaky test: skim::issues.issue_547_null_match
- Flaky test: skim::keys.keys_ctrl_arrows
- Flaky test: skim::keys.keys_ctrl_c
- Flaky test: skim::layout.layout_default
- Flaky test: skim::layout.layout_reverse_border
- Flaky test: skim::matcher.matcher_skim_v2
- Flaky test: skim::multiline.multiline_custom_sep_comma
- Flaky test: skim::multiline.multiline_layout_reverse_border
- Flaky test: skim::multiline.multiline_read0
- Flaky test: skim::multiline.multiline_tabstop_1
- Flaky test: skim::multiline.multiline_tabstop_default
- Flaky test: skim::multiline.multiline_tabstop_midline
- Flaky test: skim::multiline.multiline_tac
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 147 finding(s)
- skim::fuzzy_matcher::fzy::fzy_score_typos_full (cognitive 128) src/fuzzy_matcher/fzy.rs:495
- skim::util::printf (cognitive 87) src/util.rs:136
- skim::fuzzy_matcher::fzy::fzy_score_typos_rolling (cognitive 85) src/fuzzy_matcher/fzy.rs:367
- skim::fuzzy_matcher::fzy::fzy_score (cognitive 78) src/fuzzy_matcher/fzy.rs:132
- skim::fuzzy_matcher::arinae::algo::full_dp (cognitive 75) src/fuzzy_matcher/arinae/algo.rs:115
- skim::fuzzy_matcher::arinae::algo::range_dp (cognitive 75) src/fuzzy_matcher/arinae/algo.rs:374
- skim::popup::run_with (cognitive 54) src/popup/mod.rs:97
- skim::helper::item::strip_ansi (cognitive 40) src/helper/item.rs:554
- skim::fuzzy_matcher::clangd::build_graph (cognitive 35) src/fuzzy_matcher/clangd.rs:231
- skim::tui::util::detect_image_picker (cognitive 32) src/tui/util.rs:259
- skim::tui::util::wrap_text (cognitive 21) src/tui/util.rs:53
- skim::binds::parse_key (cognitive 20) src/binds.rs:226
- skim::thread_pool::parallel_work_queue (cognitive 18) src/thread_pool.rs:310
- skim::util::unescape_delimiter (cognitive 18) src/util.rs:30
- skim::bin::main::main (cognitive 16) src/bin/main.rs:70
- skim::fuzzy_matcher::fzy::can_match_with_typos (cognitive 16) src/fuzzy_matcher/fzy.rs:293
- skim::fuzzy_matcher::fzy::fzy_score_typos_full (cyclomatic 40) src/fuzzy_matcher/fzy.rs:495
- skim::fuzzy_matcher::arinae::algo::range_dp (cyclomatic 35) src/fuzzy_matcher/arinae/algo.rs:374
- skim::fuzzy_matcher::arinae::algo::full_dp (cyclomatic 33) src/fuzzy_matcher/arinae/algo.rs:115
- skim::popup::run_with (cyclomatic 33) src/popup/mod.rs:97
- skim::fuzzy_matcher::fzy::fzy_score (cyclomatic 28) src/fuzzy_matcher/fzy.rs:132
- skim::binds::parse_key (cyclomatic 27) src/binds.rs:226
- skim::util::printf (cyclomatic 25) src/util.rs:136
- skim::fuzzy_matcher::fzy::fzy_score_typos_rolling (cyclomatic 24) src/fuzzy_matcher/fzy.rs:367
- skim::tui::util::detect_image_picker (cyclomatic 22) src/tui/util.rs:259
- Hotspot: src/tui/app.rs src/tui/app.rs:894
- Hotspot: src/options.rs src/options.rs:1368
- Hotspot: src/skim.rs src/skim.rs:482
- Hotspot: src/tui/preview.rs src/tui/preview.rs:594
- Hotspot: src/tui/util.rs src/tui/util.rs:259
- Hotspot: src/tui/item_list.rs src/tui/item_list.rs:481
- Hotspot: src/fuzzy_matcher/fzy.rs src/fuzzy_matcher/fzy.rs:132
- App::dispatch_action (cognitive 71) src/tui/app.rs:894
- App::handle_event (cognitive 38) src/tui/app.rs:647
- App::run_preview (cognitive 27) src/tui/app.rs:518
- App::handle_mouse (cognitive 25) src/tui/app.rs:1557
- App::restart_matcher (cognitive 19) src/tui/app.rs:1393
- MethodTooLong: App.dispatch_action src/tui/app.rs:894
- MethodTooLong: Preview.spawn src/tui/preview.rs:594
- MethodTooLong: SkimOptions.default src/options.rs:1188
- MethodTooLong: ItemList.render src/tui/item_list.rs:481
- MethodTooLong: DefaultSkimItem.display src/helper/item.rs:326
- ClassTooLong: App src/tui/app.rs:50
- ClassTooLong: SkimOptions src/options.rs:135
- ClassTooLong: Preview src/tui/preview.rs:278
- ClassTooLong: ItemRenderer src/tui/item_renderer.rs:27
- ClassTooLong: Skim src/skim.rs:49
- FunctionTooLong: skim::popup::run_with src/popup/mod.rs:97
- FunctionTooLong: skim::fuzzy_matcher::arinae::algo::range_dp src/fuzzy_matcher/arinae/algo.rs:374
- FunctionTooLong: skim::fuzzy_matcher::arinae::algo::full_dp src/fuzzy_matcher/arinae/algo.rs:115
- FunctionTooLong: skim::fuzzy_matcher::fzy::fzy_score_typos_full src/fuzzy_matcher/fzy.rs:495
- FunctionTooLong: skim::manpage::generate src/manpage.rs:272
- App::dispatch_action (cyclomatic 102) src/tui/app.rs:894
- App::handle_event (cyclomatic 37) src/tui/app.rs:647
- App::run_preview (cyclomatic 21) src/tui/app.rs:518
- App::handle_mouse (cyclomatic 18) src/tui/app.rs:1557
- FileTooLong: tui/app.rs src/tui/app.rs
- FileTooLong: src/options.rs src/options.rs
- FileTooLong: tui/preview.rs src/tui/preview.rs
- FileTooLong: fuzzy_matcher/fzy.rs src/fuzzy_matcher/fzy.rs
- Duplicated block (7 lines × 2) src/fuzzy_matcher/clangd.rs:162
- Duplicated block (7 lines × 2) src/fuzzy_matcher/clangd.rs:97
- Duplicated block (7 lines × 2) src/tui/app.rs:582
- Duplicated block (7 lines × 2) src/tui/app.rs:599
- Duplicated block (6 lines × 2) src/engine/exact.rs:112
- Duplicated block (6 lines × 2) src/engine/split.rs:58
- Duplicated block (6 lines × 2) src/fuzzy_matcher/arinae/algo.rs:233
- Duplicated block (6 lines × 2) src/fuzzy_matcher/fzy.rs:583
- Preview::spawn (cognitive 69) src/tui/preview.rs:594
- Preview::spawn_callback (cognitive 22) src/tui/preview.rs:530
- Preview::filter_and_respond_to_queries (cognitive 20) src/tui/preview.rs:381
- TooManyFields: SkimOptions src/options.rs:135
- TooManyFields: App src/tui/app.rs:50
- TooManyFields: ItemList src/tui/item_list.rs:55
- DefaultSkimItem::display (cyclomatic 29) src/helper/item.rs:326
- DefaultSkimItem::new (cyclomatic 18) src/helper/item.rs:64
- DefaultSkimItem::display (cognitive 83) src/helper/item.rs:326
- DefaultSkimItem::new (cognitive 33) src/helper/item.rs:64
- Skim::tick (cognitive 28) src/skim.rs:690
- Skim::should_enter (cognitive 26) src/skim.rs:482
- SkimMatcherV2::fuzzy (cognitive 27) src/fuzzy_matcher/skim.rs:590
- SkimMatcherV2::build_score_matrix (cognitive 18) src/fuzzy_matcher/skim.rs:434
- ItemRenderer::apply_hscroll (cognitive 27) src/tui/item_renderer.rs:519
- ItemRenderer::calc_hscroll_for_width (cognitive 26) src/tui/item_renderer.rs:430
- LayoutTemplate::from_options (cognitive 22) src/tui/layout.rs:78
- LayoutTemplate::apply (cognitive 22) src/tui/layout.rs:155
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Near-duplicate member pair (52 shared lines) src/fuzzy_matcher/fzy.rs:376
- Near-duplicate member pair (52 shared lines) src/fuzzy_matcher/fzy.rs:798
- Duplicated block (21–26 lines × 2) src/fuzzy_matcher/arinae/algo.rs:179
- Duplicated block (21–26 lines × 2) src/fuzzy_matcher/arinae/mod.rs:172
- Duplicated block (16 lines × 2) src/fuzzy_matcher/clangd.rs:111
- Duplicated block (16 lines × 2) src/fuzzy_matcher/fzy.rs:408
- ColorTheme::set_color (cyclomatic 37) src/theme.rs:296
- Preview::spawn (cyclomatic 34) src/tui/preview.rs:594
- ItemList::render (cyclomatic 25) src/tui/item_list.rs:481
- SkimOptions::build (cyclomatic 20) src/options.rs:1368
- LayoutTemplate::from_options (cyclomatic 20) src/tui/layout.rs:78
- SkimMatcherV2::fuzzy (cyclomatic 17) src/fuzzy_matcher/skim.rs:590
- Skim::should_enter (cyclomatic 16) src/skim.rs:482
- Yanked release: tokio
- TodoComment tests/listen.rs:1
- ItemList::render (cognitive 46) src/tui/item_list.rs:481
- Input::render (cognitive 27) src/tui/input.rs:516
- ColorTheme::set_color (cognitive 26) src/theme.rs:296
- ArinaeMatcher::run_range (cognitive 23) src/fuzzy_matcher/arinae/mod.rs:208
- Header::render (cognitive 22) src/tui/header.rs:151
- SkimOptions::build (cognitive 21) src/options.rs:1368
- SkimItemReader::spawn_io_reader (cognitive 18) src/helper/item_reader.rs:384
- PreviewLayout::from (cognitive 18) src/tui/options.rs:47
- FieldRange::to_index_pair (cognitive 17) src/field.rs:73
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Near-duplicate member family (4 members, 21 shared lines) src/theme.rs:180
- Near-duplicate member family (3 members, 6 shared lines) src/theme.rs:122
- Near-duplicate member pair (123 shared lines) src/fuzzy_matcher/arinae/algo.rs:124
- Duplicated block (34–46 lines × 2) src/fuzzy_matcher/arinae/algo.rs:125
- Duplicated block (39 lines × 2) src/helper/item.rs:421
- Duplicated block (31 lines × 2) src/fuzzy_matcher/fzy.rs:825
- Duplicated block (19–28 lines × 2) src/fuzzy_matcher/arinae/algo.rs:205
- Duplicated block (24–26 lines × 2) src/fuzzy_matcher/arinae/algo.rs:241
- Duplicated block (24 lines × 2) src/fuzzy_matcher/arinae/mod.rs:228
- Duplicated block (19–22 lines × 2) src/fuzzy_matcher/fzy.rs:444
- Duplicated block (18 lines × 2) src/tui/app.rs:1055
- Duplicated block (17 lines × 2) src/fuzzy_matcher/fzy.rs:426
- Duplicated block (13–14 lines × 2) src/reader.rs:123
- Duplicated block (12 lines × 4) src/theme.rs:196
- Duplicated block (11–12 lines × 2) src/fuzzy_matcher/fzy.rs:866
- Duplicated block (10–11 lines × 2) src/fuzzy_matcher/arinae/algo.rs:320
- Duplicated block (11 lines × 2) src/tui/app.rs:252
- Duplicated block (3–10 lines × 3) src/fuzzy_matcher/fzy.rs:802
- Duplicated block (9–10 lines × 2) src/tui/util.rs:299
- Duplicated block (9 lines × 4) src/theme.rs:187
- Duplicated block (9 lines × 2) src/fuzzy_matcher/arinae/algo.rs:276
- Duplicated block (8 lines × 2) src/fuzzy_matcher/arinae/mod.rs:148
- Duplicated block (6 lines × 3) src/theme.rs:134
- Duplicated block (5 lines × 2) src/tui/app.rs:383
- Coverage collected but not gated
Minor — 12 finding(s)
- Silent fallback default on Err src/tui/app.rs:400
- Silent fallback default on Err src/popup/zellij.rs:22
- Silent fallback default on Err src/popup/zellij.rs:35
- Subsumed condition operand src/shell_tests.rs:14
- Subsumed condition operand src/shell_tests.rs:24
- Off-boarding risk: anonymized user #1
- No ADRs found
- Projects may be oversized for their cohesion
- REDACTED
- REDACTED
- No ADRs
- No release approval gate
Minor — 2 finding(s)
- Outdated: interprocess
- Outdated: mimalloc
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-900fc35528ef4620a1ef5554e3bd5c6f/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-900fc35528ef4620a1ef5554e3bd5c6f/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 50 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 2 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 4 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |