Executive summary
Byron/dua-cli falls short of our standard for production, in part because we found no recorded design decisions and no architecture document or diagram. It scores 66 out of 100 and is rated Adequate, and all 27 of its critical findings are security problems in the build pipeline and in its servers and containers.
Maturity, at 55, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 11 points. Describing the project's structure in the README is another step, worth about 3 points. Raising Maturity to 70 would lift the score to about 73.
Nineteen pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Three settings leave the servers or containers unsafe, and two pipeline steps run downloads nobody checks. Pinning each tool to an exact version, correcting the unsafe settings and checking each download against a checksum would close these risks. Limiting each secret to its own step would fix the two secrets exposed to more of the pipeline than needed, and the pipeline step that installs packages without pinning their versions needs the packages it installs pinned to exact versions.
The product code is 25,672 lines, about €37,000 to rebuild.
If Maturity rose from 55 to 70, the lowest score rated Strong, the score would rise from 66 to about 73.
New since the last survey: 5 findings
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Dependency Vulnerabilities · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
Fixed since the last survey: 2 findings
- Supply-chain Provenance & Signing REDACTED
- Supply-chain Provenance & Signing REDACTED
Rebuild cost: about €37,000 · Estimate
| Cost to rebuild | €12,000 to €61,000, for 202 to 642 hours of work, about 0.3 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.9 at a score of 66. 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: 25,672 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 — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 dua_cli.interactive.widgets.i18n | 2 dua_cli.interactive.widgets.tui_ext | 3 dua_cli.interactive.app.common | 4 dua_core.macos.attributes | 5 dua_cli.interactive.app.tree_view | 6 dua_core.macos | 7 dua_cli.crossdev | 8 dua_cli.inodefilter.apfs | 9 dua_core | 10 dua_cli.common | 11 dua_cli.interactive.app.input | 12 dua_core.windows | 13 dua_cli.clean | 14 dua_cli.config | 15 dua_cli.inodefilter | 16 dua_cli.interactive.app.bytevis | 17 dua_cli.interactive.app.notification | 18 dua_cli.interactive.app.handlers | 19 dua_cli.interactive.widgets.entries | 20 dua_cli.interactive.widgets.footer | 21 dua_cli.options | 22 dua_cli.interactive.app.navigation | 23 dua_cli.interactive.widgets.help | 24 dua_cli.interactive.widgets.mark | 25 dua_cli.main | 26 dua_cli.interactive.app.deletion | 27 dua_cli.interactive.app.deletion_progress | 28 dua_cli.traverse | 29 dua_cli.interactive | 30 dua_cli.interactive.app.clean_hub | 31 dua_cli.interactive.widgets.glob | 32 dua_cli.snapshot | 33 dua_cli.aggregate | 34 dua_cli.diff | 35 dua_cli.interactive.app.state | 36 dua_cli.stacks | 37 dua_cli.tree | 38 dua_cli.interactive.widgets.main | 39 dua_cli.interactive.app.eventloop | 40 dua_cli.interactive.app.terminal |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 dua_cli.interactive.widgets.i18n | ||||||||||||||||||||||||||||||||||||||||
| 2 dua_cli.interactive.widgets.tui_ext | ||||||||||||||||||||||||||||||||||||||||
| 3 dua_cli.interactive.app.common | 3 | |||||||||||||||||||||||||||||||||||||||
| 4 dua_core.macos.attributes | 1 | |||||||||||||||||||||||||||||||||||||||
| 5 dua_cli.interactive.app.tree_view | 3 | 5 | ||||||||||||||||||||||||||||||||||||||
| 6 dua_core.macos | 3 | 5 | ||||||||||||||||||||||||||||||||||||||
| 7 dua_cli.crossdev | 1 | |||||||||||||||||||||||||||||||||||||||
| 8 dua_cli.inodefilter.apfs | 1 | |||||||||||||||||||||||||||||||||||||||
| 9 dua_core | 1 | |||||||||||||||||||||||||||||||||||||||
| 10 dua_cli.common | 2 | |||||||||||||||||||||||||||||||||||||||
| 11 dua_cli.interactive.app.input | 2 | |||||||||||||||||||||||||||||||||||||||
| 12 dua_core.windows | 2 | 3 | ||||||||||||||||||||||||||||||||||||||
| 13 dua_cli.clean | 1 | |||||||||||||||||||||||||||||||||||||||
| 14 dua_cli.config | 1 | |||||||||||||||||||||||||||||||||||||||
| 15 dua_cli.inodefilter | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 16 dua_cli.interactive.app.bytevis | 1 | |||||||||||||||||||||||||||||||||||||||
| 17 dua_cli.interactive.app.notification | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 18 dua_cli.interactive.app.handlers | 1 | |||||||||||||||||||||||||||||||||||||||
| 19 dua_cli.interactive.widgets.entries | 2 | 1 | 3 | 2 | 2 | |||||||||||||||||||||||||||||||||||
| 20 dua_cli.interactive.widgets.footer | 2 | 3 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 21 dua_cli.options | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 22 dua_cli.interactive.app.navigation | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 23 dua_cli.interactive.widgets.help | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 24 dua_cli.interactive.widgets.mark | 1 | 1 | 1 | 1 | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 25 dua_cli.main | 1 | 2 | 3 | |||||||||||||||||||||||||||||||||||||
| 26 dua_cli.interactive.app.deletion | 2 | |||||||||||||||||||||||||||||||||||||||
| 27 dua_cli.interactive.app.deletion_progress | 1 | 2 | 1 | 1 | 2 | 2 | ||||||||||||||||||||||||||||||||||
| 28 dua_cli.traverse | 1 | 2 | 5 | 2 | 1 | |||||||||||||||||||||||||||||||||||
| 29 dua_cli.interactive | 2 | |||||||||||||||||||||||||||||||||||||||
| 30 dua_cli.interactive.app.clean_hub | 1 | 1 | 2 | 1 | 3 | |||||||||||||||||||||||||||||||||||
| 31 dua_cli.interactive.widgets.glob | 2 | 1 | 3 | 2 | ||||||||||||||||||||||||||||||||||||
| 32 dua_cli.snapshot | 4 | |||||||||||||||||||||||||||||||||||||||
| 33 dua_cli.aggregate | 1 | 1 | 3 | 2 | ||||||||||||||||||||||||||||||||||||
| 34 dua_cli.diff | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 35 dua_cli.interactive.app.state | 1 | 3 | 1 | 1 | 2 | 1 | 1 | 1 | 4 | 1 | 1 | 1 | 1 | 4 | 1 | 1 | 1 | |||||||||||||||||||||||
| 36 dua_cli.stacks | 1 | 4 | 1 | |||||||||||||||||||||||||||||||||||||
| 37 dua_cli.tree | 2 | 3 | 1 | |||||||||||||||||||||||||||||||||||||
| 38 dua_cli.interactive.widgets.main | 1 | 1 | 2 | 1 | 1 | 1 | 1 | 1 | 2 | |||||||||||||||||||||||||||||||
| 39 dua_cli.interactive.app.eventloop | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 40 dua_cli.interactive.app.terminal | 1 | 2 | 1 | 1 | 3 | 1 | 1 |
3→28 dua_cli.interactive.app.common uses dua_cli.traverse part of a loop✕
- Connections
- 3 pairs of types, where a type in dua_cli.interactive.app.common uses a type in dua_cli.traverse.
- The types involved
dua_cli.interactive.app.common.EntryDataBundle→dua_cli.traverse.TreeIndexdua_cli.interactive.app.common.common$module→dua_cli.traverse.Treedua_cli.interactive.app.common.common$module→dua_cli.traverse.TreeIndex
- Direction
- dua_cli.interactive.app.common uses dua_cli.traverse, so a change to dua_cli.traverse can break dua_cli.interactive.app.common, while a change to dua_cli.interactive.app.common can't break dua_cli.traverse.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
4→6 dua_core.macos.attributes uses dua_core.macos part of a loop✕
- Connections
- 1 pair of types, where a type in dua_core.macos.attributes uses a type in dua_core.macos.
- The types involved
dua_core.macos.attributes.ParsedRecord→dua_core.macos.FileType
- Direction
- dua_core.macos.attributes uses dua_core.macos, so a change to dua_core.macos can break dua_core.macos.attributes, while a change to dua_core.macos.attributes can't break dua_core.macos.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
5→3 dua_cli.interactive.app.tree_view uses dua_cli.interactive.app.common✕
- Connections
- 3 pairs of types, where a type in dua_cli.interactive.app.tree_view uses a type in dua_cli.interactive.app.common.
- The types involved
dua_cli.interactive.app.tree_view.TreeView→dua_cli.interactive.app.common.EntryCheckdua_cli.interactive.app.tree_view.TreeView→dua_cli.interactive.app.common.EntryDataBundledua_cli.interactive.app.tree_view.TreeView→dua_cli.interactive.app.common.SortMode
- Direction
- dua_cli.interactive.app.tree_view uses dua_cli.interactive.app.common, so a change to dua_cli.interactive.app.common can break dua_cli.interactive.app.tree_view, while a change to dua_cli.interactive.app.tree_view can't break dua_cli.interactive.app.common.
- Position
- Below the diagonal: dua_cli.interactive.app.tree_view uses a module listed above it, which is the healthy direction.
5→28 dua_cli.interactive.app.tree_view uses dua_cli.traverse part of a loop✕
- Connections
- 5 pairs of types, where a type in dua_cli.interactive.app.tree_view uses a type in dua_cli.traverse.
- The types involved
dua_cli.interactive.app.tree_view.TreeView→dua_cli.traverse.Traversaldua_cli.interactive.app.tree_view.TreeView→dua_cli.traverse.Treedua_cli.interactive.app.tree_view.TreeView→dua_cli.traverse.TreeIndexdua_cli.interactive.app.tree_view.tree_view$module→dua_cli.traverse.Treedua_cli.interactive.app.tree_view.tree_view$module→dua_cli.traverse.TreeIndex
- Direction
- dua_cli.interactive.app.tree_view uses dua_cli.traverse, so a change to dua_cli.traverse can break dua_cli.interactive.app.tree_view, while a change to dua_cli.interactive.app.tree_view can't break dua_cli.traverse.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→4 dua_core.macos uses dua_core.macos.attributes✕
- Connections
- 3 pairs of types, where a type in dua_core.macos uses a type in dua_core.macos.attributes.
- The types involved
dua_core.macos.Metadata→dua_core.macos.attributes.DataForkdua_core.macos.ReadDir→dua_core.macos.attributes.AlignedBufferdua_core.macos.macos$module→dua_core.macos.attributes.DataFork
- Direction
- dua_core.macos uses dua_core.macos.attributes, so a change to dua_core.macos.attributes can break dua_core.macos, while a change to dua_core.macos can't break dua_core.macos.attributes.
- Position
- Below the diagonal: dua_core.macos uses a module listed above it, which is the healthy direction.
6→9 dua_core.macos uses dua_core part of a loop✕
- Connections
- 5 pairs of types, where a type in dua_core.macos uses a type in dua_core.
- The types involved
dua_core.macos.Entry→dua_core.DirectoryIddua_core.macos.Entry→dua_core.Optionsdua_core.macos.ReadDir→dua_core.Entrydua_core.macos.ReadDir→dua_core.Optionsdua_core.macos.ReadDir→dua_core.ReadDir
- Direction
- dua_core.macos uses dua_core, so a change to dua_core can break dua_core.macos, while a change to dua_core.macos can't break dua_core.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→6 dua_cli.crossdev uses dua_core.macos✕
- Connections
- 1 pair of types, where a type in dua_cli.crossdev uses a type in dua_core.macos.
- The types involved
dua_cli.crossdev.crossdev$module→dua_core.macos.Metadata
- Direction
- dua_cli.crossdev uses dua_core.macos, so a change to dua_core.macos can break dua_cli.crossdev, while a change to dua_cli.crossdev can't break dua_core.macos.
- Position
- Below the diagonal: dua_cli.crossdev uses a module listed above it, which is the healthy direction.
8→6 dua_cli.inodefilter.apfs uses dua_core.macos✕
- Connections
- 1 pair of types, where a type in dua_cli.inodefilter.apfs uses a type in dua_core.macos.
- The types involved
dua_cli.inodefilter.apfs.ApfsFilter→dua_core.macos.Metadata
- Direction
- dua_cli.inodefilter.apfs uses dua_core.macos, so a change to dua_core.macos can break dua_cli.inodefilter.apfs, while a change to dua_cli.inodefilter.apfs can't break dua_core.macos.
- Position
- Below the diagonal: dua_cli.inodefilter.apfs uses a module listed above it, which is the healthy direction.
9→6 dua_core uses dua_core.macos✕
- Connections
- 1 pair of types, where a type in dua_core uses a type in dua_core.macos.
- The types involved
dua_core.Entry→dua_core.macos.FileType
- Direction
- dua_core uses dua_core.macos, so a change to dua_core.macos can break dua_core, while a change to dua_core can't break dua_core.macos.
- Position
- Below the diagonal: dua_core uses a module listed above it, which is the healthy direction.
10→9 dua_cli.common uses dua_core✕
- Connections
- 2 pairs of types, where a type in dua_cli.common uses a type in dua_core.
- The types involved
dua_cli.common.WalkOptions→dua_core.Orderdua_cli.common.WalkRoot→dua_core.Entry
- Direction
- dua_cli.common uses dua_core, so a change to dua_core can break dua_cli.common, while a change to dua_cli.common can't break dua_core.
- Position
- Below the diagonal: dua_cli.common uses a module listed above it, which is the healthy direction.
11→9 dua_cli.interactive.app.input uses dua_core✕
- Connections
- 2 pairs of types, where a type in dua_cli.interactive.app.input uses a type in dua_core.
- The types involved
dua_cli.interactive.app.input.TerminalFocus→dua_core.Eventdua_cli.interactive.app.input.input$module→dua_core.Event
- Direction
- dua_cli.interactive.app.input uses dua_core, so a change to dua_core can break dua_cli.interactive.app.input, while a change to dua_cli.interactive.app.input can't break dua_core.
- Position
- Below the diagonal: dua_cli.interactive.app.input uses a module listed above it, which is the healthy direction.
12→6 dua_core.windows uses dua_core.macos✕
- Connections
- 2 pairs of types, where a type in dua_core.windows uses a type in dua_core.macos.
- The types involved
dua_core.windows.Entry→dua_core.macos.FileTypedua_core.windows.FileType→dua_core.macos.FileType
- Direction
- dua_core.windows uses dua_core.macos, so a change to dua_core.macos can break dua_core.windows, while a change to dua_core.windows can't break dua_core.macos.
- Position
- Below the diagonal: dua_core.windows uses a module listed above it, which is the healthy direction.
12→9 dua_core.windows uses dua_core✕
- Connections
- 3 pairs of types, where a type in dua_core.windows uses a type in dua_core.
- The types involved
dua_core.windows.Entry→dua_core.DirectoryIddua_core.windows.Entry→dua_core.Optionsdua_core.windows.ReadDir→dua_core.Options
- Direction
- dua_core.windows uses dua_core, so a change to dua_core can break dua_core.windows, while a change to dua_core.windows can't break dua_core.
- Position
- Below the diagonal: dua_core.windows uses a module listed above it, which is the healthy direction.
13→10 dua_cli.clean uses dua_cli.common✕
- Connections
- 1 pair of types, where a type in dua_cli.clean uses a type in dua_cli.common.
- The types involved
dua_cli.clean.clean$module→dua_cli.common.WalkOptions
- Direction
- dua_cli.clean uses dua_cli.common, so a change to dua_cli.common can break dua_cli.clean, while a change to dua_cli.clean can't break dua_cli.common.
- Position
- Below the diagonal: dua_cli.clean uses a module listed above it, which is the healthy direction.
14→10 dua_cli.config uses dua_cli.common✕
- Connections
- 1 pair of types, where a type in dua_cli.config uses a type in dua_cli.common.
- The types involved
dua_cli.config.Config→dua_cli.common.ByteFormat
- Direction
- dua_cli.config uses dua_cli.common, so a change to dua_cli.common can break dua_cli.config, while a change to dua_cli.config can't break dua_cli.common.
- Position
- Below the diagonal: dua_cli.config uses a module listed above it, which is the healthy direction.
15→6 dua_cli.inodefilter uses dua_core.macos✕
- Connections
- 1 pair of types, where a type in dua_cli.inodefilter uses a type in dua_core.macos.
- The types involved
dua_cli.inodefilter.InodeFilter→dua_core.macos.Metadata
- Direction
- dua_cli.inodefilter uses dua_core.macos, so a change to dua_core.macos can break dua_cli.inodefilter, while a change to dua_cli.inodefilter can't break dua_core.macos.
- Position
- Below the diagonal: dua_cli.inodefilter uses a module listed above it, which is the healthy direction.
15→8 dua_cli.inodefilter uses dua_cli.inodefilter.apfs✕
- Connections
- 1 pair of types, where a type in dua_cli.inodefilter uses a type in dua_cli.inodefilter.apfs.
- The types involved
dua_cli.inodefilter.InodeFilter→dua_cli.inodefilter.apfs.ApfsFilter
- Direction
- dua_cli.inodefilter uses dua_cli.inodefilter.apfs, so a change to dua_cli.inodefilter.apfs can break dua_cli.inodefilter, while a change to dua_cli.inodefilter can't break dua_cli.inodefilter.apfs.
- Position
- Below the diagonal: dua_cli.inodefilter uses a module listed above it, which is the healthy direction.
15→9 dua_cli.inodefilter uses dua_core✕
- Connections
- 1 pair of types, where a type in dua_cli.inodefilter uses a type in dua_core.
- The types involved
dua_cli.inodefilter.InodeFilter→dua_core.Entry
- Direction
- dua_cli.inodefilter uses dua_core, so a change to dua_core can break dua_cli.inodefilter, while a change to dua_cli.inodefilter can't break dua_core.
- Position
- Below the diagonal: dua_cli.inodefilter uses a module listed above it, which is the healthy direction.
15→10 dua_cli.inodefilter uses dua_cli.common✕
- Connections
- 1 pair of types, where a type in dua_cli.inodefilter uses a type in dua_cli.common.
- The types involved
dua_cli.inodefilter.InodeFilter→dua_cli.common.WalkOptions
- Direction
- dua_cli.inodefilter uses dua_cli.common, so a change to dua_cli.common can break dua_cli.inodefilter, while a change to dua_cli.inodefilter can't break dua_cli.common.
- Position
- Below the diagonal: dua_cli.inodefilter uses a module listed above it, which is the healthy direction.
16→10 dua_cli.interactive.app.bytevis uses dua_cli.common✕
- Connections
- 1 pair of types, where a type in dua_cli.interactive.app.bytevis uses a type in dua_cli.common.
- The types involved
dua_cli.interactive.app.bytevis.DisplayOptions→dua_cli.common.ByteFormat
- Direction
- dua_cli.interactive.app.bytevis uses dua_cli.common, so a change to dua_cli.common can break dua_cli.interactive.app.bytevis, while a change to dua_cli.interactive.app.bytevis can't break dua_cli.common.
- Position
- Below the diagonal: dua_cli.interactive.app.bytevis uses a module listed above it, which is the healthy direction.
17→1 dua_cli.interactive.app.notification uses dua_cli.interactive.widgets.i18n✕
- Connections
- 1 pair of types, where a type in dua_cli.interactive.app.notification uses a type in dua_cli.interactive.widgets.i18n.
- The types involved
dua_cli.interactive.app.notification.notification$module→dua_cli.interactive.widgets.i18n.Language
- Direction
- dua_cli.interactive.app.notification uses dua_cli.interactive.widgets.i18n, so a change to dua_cli.interactive.widgets.i18n can break dua_cli.interactive.app.notification, while a change to dua_cli.interactive.app.notification can't break dua_cli.interactive.widgets.i18n.
- Position
- Below the diagonal: dua_cli.interactive.app.notification uses a module listed above it, which is the healthy direction.
17→10 dua_cli.interactive.app.notification uses dua_cli.common✕
- Connections
- 1 pair of types, where a type in dua_cli.interactive.app.notification uses a type in dua_cli.common.
- The types involved
dua_cli.interactive.app.notification.notification$module→dua_cli.common.ByteFormat
- Direction
- dua_cli.interactive.app.notification uses dua_cli.common, so a change to dua_cli.common can break dua_cli.interactive.app.notification, while a change to dua_cli.interactive.app.notification can't break dua_cli.common.
- Position
- Below the diagonal: dua_cli.interactive.app.notification uses a module listed above it, which is the healthy direction.
18→14 dua_cli.interactive.app.handlers uses dua_cli.config✕
- Connections
- 1 pair of types, where a type in dua_cli.interactive.app.handlers uses a type in dua_cli.config.
- The types involved
dua_cli.interactive.app.handlers.CursorDirection→dua_cli.config.KeysConfig
- Direction
- dua_cli.interactive.app.handlers uses dua_cli.config, so a change to dua_cli.config can break dua_cli.interactive.app.handlers, while a change to dua_cli.interactive.app.handlers can't break dua_cli.config.
- Position
- Below the diagonal: dua_cli.interactive.app.handlers uses a module listed above it, which is the healthy direction.
19→1 dua_cli.interactive.widgets.entries uses dua_cli.interactive.widgets.i18n✕
- Connections
- 2 pairs of types, where a type in dua_cli.interactive.widgets.entries uses a type in dua_cli.interactive.widgets.i18n.
- The types involved
dua_cli.interactive.widgets.entries.EntriesProps→dua_cli.interactive.widgets.i18n.Languagedua_cli.interactive.widgets.entries.entries$module→dua_cli.interactive.widgets.i18n.Language
- Direction
- dua_cli.interactive.widgets.entries uses dua_cli.interactive.widgets.i18n, so a change to dua_cli.interactive.widgets.i18n can break dua_cli.interactive.widgets.entries, while a change to dua_cli.interactive.widgets.entries can't break dua_cli.interactive.widgets.i18n.
- Position
- Below the diagonal: dua_cli.interactive.widgets.entries uses a module listed above it, which is the healthy direction.
19→2 dua_cli.interactive.widgets.entries uses dua_cli.interactive.widgets.tui_ext✕
- Connections
- 1 pair of types, where a type in dua_cli.interactive.widgets.entries uses a type in dua_cli.interactive.widgets.tui_ext.
- The types involved
dua_cli.interactive.widgets.entries.Entries→dua_cli.interactive.widgets.tui_ext.List
- Direction
- dua_cli.interactive.widgets.entries uses dua_cli.interactive.widgets.tui_ext, so a change to dua_cli.interactive.widgets.tui_ext can break dua_cli.interactive.widgets.entries, while a change to dua_cli.interactive.widgets.entries can't break dua_cli.interactive.widgets.tui_ext.
- Position
- Below the diagonal: dua_cli.interactive.widgets.entries uses a module listed above it, which is the healthy direction.
19→3 dua_cli.interactive.widgets.entries uses dua_cli.interactive.app.common✕
- Connections
- 3 pairs of types, where a type in dua_cli.interactive.widgets.entries uses a type in dua_cli.interactive.app.common.
- The types involved
dua_cli.interactive.widgets.entries.EntriesProps→dua_cli.interactive.app.common.SortModedua_cli.interactive.widgets.entries.EntryRow→dua_cli.interactive.app.common.EntryDataBundledua_cli.interactive.widgets.entries.entries$module→dua_cli.interactive.app.common.SortMode
- Direction
- dua_cli.interactive.widgets.entries uses dua_cli.interactive.app.common, so a change to dua_cli.interactive.app.common can break dua_cli.interactive.widgets.entries, while a change to dua_cli.interactive.widgets.entries can't break dua_cli.interactive.app.common.
- Position
- Below the diagonal: dua_cli.interactive.widgets.entries uses a module listed above it, which is the healthy direction.
19→14 dua_cli.interactive.widgets.entries uses dua_cli.config✕
- Connections
- 2 pairs of types, where a type in dua_cli.interactive.widgets.entries uses a type in dua_cli.config.
- The types involved
dua_cli.interactive.widgets.entries.EntriesProps→dua_cli.config.KeysConfigdua_cli.interactive.widgets.entries.entries$module→dua_cli.config.KeysConfig
- Direction
- dua_cli.interactive.widgets.entries uses dua_cli.config, so a change to dua_cli.config can break dua_cli.interactive.widgets.entries, while a change to dua_cli.interactive.widgets.entries can't break dua_cli.config.
- Position
- Below the diagonal: dua_cli.interactive.widgets.entries uses a module listed above it, which is the healthy direction.
19→16 dua_cli.interactive.widgets.entries uses dua_cli.interactive.app.bytevis✕
- Connections
- 2 pairs of types, where a type in dua_cli.interactive.widgets.entries uses a type in dua_cli.interactive.app.bytevis.
- The types involved
dua_cli.interactive.widgets.entries.EntriesProps→dua_cli.interactive.app.bytevis.DisplayOptionsdua_cli.interactive.widgets.entries.entries$module→dua_cli.interactive.app.bytevis.DisplayOptions
- Direction
- dua_cli.interactive.widgets.entries uses dua_cli.interactive.app.bytevis, so a change to dua_cli.interactive.app.bytevis can break dua_cli.interactive.widgets.entries, while a change to dua_cli.interactive.widgets.entries can't break dua_cli.interactive.app.bytevis.
- Position
- Below the diagonal: dua_cli.interactive.widgets.entries uses a module listed above it, which is the healthy direction.
20→1 dua_cli.interactive.widgets.footer uses dua_cli.interactive.widgets.i18n✕
- Connections
- 2 pairs of types, where a type in dua_cli.interactive.widgets.footer uses a type in dua_cli.interactive.widgets.i18n.
- The types involved
dua_cli.interactive.widgets.footer.FooterProps→dua_cli.interactive.widgets.i18n.Languagedua_cli.interactive.widgets.footer.footer$module→dua_cli.interactive.widgets.i18n.Language
- Direction
- dua_cli.interactive.widgets.footer uses dua_cli.interactive.widgets.i18n, so a change to dua_cli.interactive.widgets.i18n can break dua_cli.interactive.widgets.footer, while a change to dua_cli.interactive.widgets.footer can't break dua_cli.interactive.widgets.i18n.
- Position
- Below the diagonal: dua_cli.interactive.widgets.footer uses a module listed above it, which is the healthy direction.
20→3 dua_cli.interactive.widgets.footer uses dua_cli.interactive.app.common✕
- Connections
- 3 pairs of types, where a type in dua_cli.interactive.widgets.footer uses a type in dua_cli.interactive.app.common.
- The types involved
dua_cli.interactive.widgets.footer.FooterProps→dua_cli.interactive.app.common.SortModedua_cli.interactive.widgets.footer.footer$module→dua_cli.interactive.app.common.MTimeSortdua_cli.interactive.widgets.footer.footer$module→dua_cli.interactive.app.common.SortMode
- Direction
- dua_cli.interactive.widgets.footer uses dua_cli.interactive.app.common, so a change to dua_cli.interactive.app.common can break dua_cli.interactive.widgets.footer, while a change to dua_cli.interactive.widgets.footer can't break dua_cli.interactive.app.common.
- Position
- Below the diagonal: dua_cli.interactive.widgets.footer uses a module listed above it, which is the healthy direction.
20→10 dua_cli.interactive.widgets.footer uses dua_cli.common✕
- Connections
- 1 pair of types, where a type in dua_cli.interactive.widgets.footer uses a type in dua_cli.common.
- The types involved
dua_cli.interactive.widgets.footer.FooterProps→dua_cli.common.ByteFormat
- Direction
- dua_cli.interactive.widgets.footer uses dua_cli.common, so a change to dua_cli.common can break dua_cli.interactive.widgets.footer, while a change to dua_cli.interactive.widgets.footer can't break dua_cli.common.
- Position
- Below the diagonal: dua_cli.interactive.widgets.footer uses a module listed above it, which is the healthy direction.
20→14 dua_cli.interactive.widgets.footer uses dua_cli.config✕
- Connections
- 1 pair of types, where a type in dua_cli.interactive.widgets.footer uses a type in dua_cli.config.
- The types involved
dua_cli.interactive.widgets.footer.FooterProps→dua_cli.config.KeysConfig
- Direction
- dua_cli.interactive.widgets.footer uses dua_cli.config, so a change to dua_cli.config can break dua_cli.interactive.widgets.footer, while a change to dua_cli.interactive.widgets.footer can't break dua_cli.config.
- Position
- Below the diagonal: dua_cli.interactive.widgets.footer uses a module listed above it, which is the healthy direction.
21→10 dua_cli.options uses dua_cli.common✕
- Connections
- 2 pairs of types, where a type in dua_cli.options uses a type in dua_cli.common.
- The types involved
dua_cli.options.TraversalArgs→dua_cli.common.ByteFormatdua_cli.options.options$module→dua_cli.common.ByteFormat
- Direction
- dua_cli.options uses dua_cli.common, so a change to dua_cli.common can break dua_cli.options, while a change to dua_cli.options can't break dua_cli.common.
- Position
- Below the diagonal: dua_cli.options uses a module listed above it, which is the healthy direction.
21→14 dua_cli.options uses dua_cli.config✕
- Connections
- 1 pair of types, where a type in dua_cli.options uses a type in dua_cli.config.
- The types involved
dua_cli.options.TraversalArgs→dua_cli.config.Config
- Direction
- dua_cli.options uses dua_cli.config, so a change to dua_cli.config can break dua_cli.options, while a change to dua_cli.options can't break dua_cli.config.
- Position
- Below the diagonal: dua_cli.options uses a module listed above it, which is the healthy direction.
22→18 dua_cli.interactive.app.navigation uses dua_cli.interactive.app.handlers✕
- Connections
- 1 pair of types, where a type in dua_cli.interactive.app.navigation uses a type in dua_cli.interactive.app.handlers.
- The types involved
dua_cli.interactive.app.navigation.Navigation→dua_cli.interactive.app.handlers.CursorDirection
- Direction
- dua_cli.interactive.app.navigation uses dua_cli.interactive.app.handlers, so a change to dua_cli.interactive.app.handlers can break dua_cli.interactive.app.navigation, while a change to dua_cli.interactive.app.navigation can't break dua_cli.interactive.app.handlers.
- Position
- Below the diagonal: dua_cli.interactive.app.navigation uses a module listed above it, which is the healthy direction.
22→28 dua_cli.interactive.app.navigation uses dua_cli.traverse part of a loop✕
- Connections
- 1 pair of types, where a type in dua_cli.interactive.app.navigation uses a type in dua_cli.traverse.
- The types involved
dua_cli.interactive.app.navigation.Navigation→dua_cli.traverse.TreeIndex
- Direction
- dua_cli.interactive.app.navigation uses dua_cli.traverse, so a change to dua_cli.traverse can break dua_cli.interactive.app.navigation, while a change to dua_cli.interactive.app.navigation can't break dua_cli.traverse.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→1 dua_cli.interactive.widgets.help uses dua_cli.interactive.widgets.i18n✕
- Connections
- 1 pair of types, where a type in dua_cli.interactive.widgets.help uses a type in dua_cli.interactive.widgets.i18n.
- The types involved
dua_cli.interactive.widgets.help.HelpPaneProps→dua_cli.interactive.widgets.i18n.Language
- Direction
- dua_cli.interactive.widgets.help uses dua_cli.interactive.widgets.i18n, so a change to dua_cli.interactive.widgets.i18n can break dua_cli.interactive.widgets.help, while a change to dua_cli.interactive.widgets.help can't break dua_cli.interactive.widgets.i18n.
- Position
- Below the diagonal: dua_cli.interactive.widgets.help uses a module listed above it, which is the healthy direction.
23→14 dua_cli.interactive.widgets.help uses dua_cli.config✕
- Connections
- 2 pairs of types, where a type in dua_cli.interactive.widgets.help uses a type in dua_cli.config.
- The types involved
dua_cli.interactive.widgets.help.HelpPane→dua_cli.config.KeysConfigdua_cli.interactive.widgets.help.HelpPaneProps→dua_cli.config.KeysConfig
- Direction
- dua_cli.interactive.widgets.help uses dua_cli.config, so a change to dua_cli.config can break dua_cli.interactive.widgets.help, while a change to dua_cli.interactive.widgets.help can't break dua_cli.config.
- Position
- Below the diagonal: dua_cli.interactive.widgets.help uses a module listed above it, which is the healthy direction.
23→18 dua_cli.interactive.widgets.help uses dua_cli.interactive.app.handlers✕
- Connections
- 1 pair of types, where a type in dua_cli.interactive.widgets.help uses a type in dua_cli.interactive.app.handlers.
- The types involved
dua_cli.interactive.widgets.help.HelpPane→dua_cli.interactive.app.handlers.CursorDirection
- Direction
- dua_cli.interactive.widgets.help uses dua_cli.interactive.app.handlers, so a change to dua_cli.interactive.app.handlers can break dua_cli.interactive.widgets.help, while a change to dua_cli.interactive.widgets.help can't break dua_cli.interactive.app.handlers.
- Position
- Below the diagonal: dua_cli.interactive.widgets.help uses a module listed above it, which is the healthy direction.
24→1 dua_cli.interactive.widgets.mark uses dua_cli.interactive.widgets.i18n✕
- Connections
- 1 pair of types, where a type in dua_cli.interactive.widgets.mark uses a type in dua_cli.interactive.widgets.i18n.
- The types involved
dua_cli.interactive.widgets.mark.MarkPaneProps→dua_cli.interactive.widgets.i18n.Language
- Direction
- dua_cli.interactive.widgets.mark uses dua_cli.interactive.widgets.i18n, so a change to dua_cli.interactive.widgets.i18n can break dua_cli.interactive.widgets.mark, while a change to dua_cli.interactive.widgets.mark can't break dua_cli.interactive.widgets.i18n.
- Position
- Below the diagonal: dua_cli.interactive.widgets.mark uses a module listed above it, which is the healthy direction.
24→2 dua_cli.interactive.widgets.mark uses dua_cli.interactive.widgets.tui_ext✕
- Connections
- 1 pair of types, where a type in dua_cli.interactive.widgets.mark uses a type in dua_cli.interactive.widgets.tui_ext.
- The types involved
dua_cli.interactive.widgets.mark.MarkPane→dua_cli.interactive.widgets.tui_ext.List
- Direction
- dua_cli.interactive.widgets.mark uses dua_cli.interactive.widgets.tui_ext, so a change to dua_cli.interactive.widgets.tui_ext can break dua_cli.interactive.widgets.mark, while a change to dua_cli.interactive.widgets.mark can't break dua_cli.interactive.widgets.tui_ext.
- Position
- Below the diagonal: dua_cli.interactive.widgets.mark uses a module listed above it, which is the healthy direction.
24→5 dua_cli.interactive.widgets.mark uses dua_cli.interactive.app.tree_view✕
- Connections
- 1 pair of types, where a type in dua_cli.interactive.widgets.mark uses a type in dua_cli.interactive.app.tree_view.
- The types involved
dua_cli.interactive.widgets.mark.MarkPane→dua_cli.interactive.app.tree_view.TreeView
- Direction
- dua_cli.interactive.widgets.mark uses dua_cli.interactive.app.tree_view, so a change to dua_cli.interactive.app.tree_view can break dua_cli.interactive.widgets.mark, while a change to dua_cli.interactive.widgets.mark can't break dua_cli.interactive.app.tree_view.
- Position
- Below the diagonal: dua_cli.interactive.widgets.mark uses a module listed above it, which is the healthy direction.
24→10 dua_cli.interactive.widgets.mark uses dua_cli.common✕
- Connections
- 1 pair of types, where a type in dua_cli.interactive.widgets.mark uses a type in dua_cli.common.
- The types involved
dua_cli.interactive.widgets.mark.MarkPaneProps→dua_cli.common.ByteFormat
- Direction
- dua_cli.interactive.widgets.mark uses dua_cli.common, so a change to dua_cli.common can break dua_cli.interactive.widgets.mark, while a change to dua_cli.interactive.widgets.mark can't break dua_cli.common.
- Position
- Below the diagonal: dua_cli.interactive.widgets.mark uses a module listed above it, which is the healthy direction.
24→14 dua_cli.interactive.widgets.mark uses dua_cli.config✕
- Connections
- 2 pairs of types, where a type in dua_cli.interactive.widgets.mark uses a type in dua_cli.config.
- The types involved
dua_cli.interactive.widgets.mark.MarkPane→dua_cli.config.KeysConfigdua_cli.interactive.widgets.mark.MarkPaneProps→dua_cli.config.KeysConfig
- Direction
- dua_cli.interactive.widgets.mark uses dua_cli.config, so a change to dua_cli.config can break dua_cli.interactive.widgets.mark, while a change to dua_cli.interactive.widgets.mark can't break dua_cli.config.
- Position
- Below the diagonal: dua_cli.interactive.widgets.mark uses a module listed above it, which is the healthy direction.
24→18 dua_cli.interactive.widgets.mark uses dua_cli.interactive.app.handlers✕
- Connections
- 1 pair of types, where a type in dua_cli.interactive.widgets.mark uses a type in dua_cli.interactive.app.handlers.
- The types involved
dua_cli.interactive.widgets.mark.MarkPane→dua_cli.interactive.app.handlers.CursorDirection
- Direction
- dua_cli.interactive.widgets.mark uses dua_cli.interactive.app.handlers, so a change to dua_cli.interactive.app.handlers can break dua_cli.interactive.widgets.mark, while a change to dua_cli.interactive.widgets.mark can't break dua_cli.interactive.app.handlers.
- Position
- Below the diagonal: dua_cli.interactive.widgets.mark uses a module listed above it, which is the healthy direction.
24→28 dua_cli.interactive.widgets.mark uses dua_cli.traverse part of a loop✕
- Connections
- 1 pair of types, where a type in dua_cli.interactive.widgets.mark uses a type in dua_cli.traverse.
- The types involved
dua_cli.interactive.widgets.mark.MarkPane→dua_cli.traverse.TreeIndex
- Direction
- dua_cli.interactive.widgets.mark uses dua_cli.traverse, so a change to dua_cli.traverse can break dua_cli.interactive.widgets.mark, while a change to dua_cli.interactive.widgets.mark can't break dua_cli.traverse.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
25→9 dua_cli.main uses dua_core✕
- Connections
- 1 pair of types, where a type in dua_cli.main uses a type in dua_core.
- The types involved
dua_cli.main.main$module→dua_core.Options
- Direction
- dua_cli.main uses dua_core, so a change to dua_core can break dua_cli.main, while a change to dua_cli.main can't break dua_core.
- Position
- Below the diagonal: dua_cli.main uses a module listed above it, which is the healthy direction.
25→10 dua_cli.main uses dua_cli.common✕
- Connections
- 2 pairs of types, where a type in dua_cli.main uses a type in dua_cli.common.
- The types involved
dua_cli.main.main$module→dua_cli.common.ByteFormatdua_cli.main.main$module→dua_cli.common.WalkOptions
- Direction
- dua_cli.main uses dua_cli.common, so a change to dua_cli.common can break dua_cli.main, while a change to dua_cli.main can't break dua_cli.common.
- Position
- Below the diagonal: dua_cli.main uses a module listed above it, which is the healthy direction.
25→21 dua_cli.main uses dua_cli.options✕
- Connections
- 3 pairs of types, where a type in dua_cli.main uses a type in dua_cli.options.
- The types involved
dua_cli.main.main$module→dua_cli.options.ScanArgsdua_cli.main.main$module→dua_cli.options.StackArgsdua_cli.main.main$module→dua_cli.options.TraversalArgs
- Direction
- dua_cli.main uses dua_cli.options, so a change to dua_cli.options can break dua_cli.main, while a change to dua_cli.main can't break dua_cli.options.
- Position
- Below the diagonal: dua_cli.main uses a module listed above it, which is the healthy direction.
26→24 dua_cli.interactive.app.deletion uses dua_cli.interactive.widgets.mark✕
- Connections
- 2 pairs of types, where a type in dua_cli.interactive.app.deletion uses a type in dua_cli.interactive.widgets.mark.
- The types involved
dua_cli.interactive.app.deletion.DeletionTask→dua_cli.interactive.widgets.mark.MarkModedua_cli.interactive.app.deletion.deletion$module→dua_cli.interactive.widgets.mark.MarkMode
- Direction
- dua_cli.interactive.app.deletion uses dua_cli.interactive.widgets.mark, so a change to dua_cli.interactive.widgets.mark can break dua_cli.interactive.app.deletion, while a change to dua_cli.interactive.app.deletion can't break dua_cli.interactive.widgets.mark.
- Position
- Below the diagonal: dua_cli.interactive.app.deletion uses a module listed above it, which is the healthy direction.
27→1 dua_cli.interactive.app.deletion_progress uses dua_cli.interactive.widgets.i18n✕
- Connections
- 1 pair of types, where a type in dua_cli.interactive.app.deletion_progress uses a type in dua_cli.interactive.widgets.i18n.
- The types involved
dua_cli.interactive.app.deletion_progress.FilesystemDeletion→dua_cli.interactive.widgets.i18n.Language
- Direction
- dua_cli.interactive.app.deletion_progress uses dua_cli.interactive.widgets.i18n, so a change to dua_cli.interactive.widgets.i18n can break dua_cli.interactive.app.deletion_progress, while a change to dua_cli.interactive.app.deletion_progress can't break dua_cli.interactive.widgets.i18n.
- Position
- Below the diagonal: dua_cli.interactive.app.deletion_progress uses a module listed above it, which is the healthy direction.
27→5 dua_cli.interactive.app.deletion_progress uses dua_cli.interactive.app.tree_view✕
- Connections
- 2 pairs of types, where a type in dua_cli.interactive.app.deletion_progress uses a type in dua_cli.interactive.app.tree_view.
- The types involved
dua_cli.interactive.app.deletion_progress.FilesystemDeletion→dua_cli.interactive.app.tree_view.TreeViewdua_cli.interactive.app.deletion_progress.deletion_progress$module→dua_cli.interactive.app.tree_view.TreeView
- Direction
- dua_cli.interactive.app.deletion_progress uses dua_cli.interactive.app.tree_view, so a change to dua_cli.interactive.app.tree_view can break dua_cli.interactive.app.deletion_progress, while a change to dua_cli.interactive.app.deletion_progress can't break dua_cli.interactive.app.tree_view.
- Position
- Below the diagonal: dua_cli.interactive.app.deletion_progress uses a module listed above it, which is the healthy direction.
27→10 dua_cli.interactive.app.deletion_progress uses dua_cli.common✕
- Connections
- 1 pair of types, where a type in dua_cli.interactive.app.deletion_progress uses a type in dua_cli.common.
- The types involved
dua_cli.interactive.app.deletion_progress.FilesystemDeletion→dua_cli.common.ByteFormat
- Direction
- dua_cli.interactive.app.deletion_progress uses dua_cli.common, so a change to dua_cli.common can break dua_cli.interactive.app.deletion_progress, while a change to dua_cli.interactive.app.deletion_progress can't break dua_cli.common.
- Position
- Below the diagonal: dua_cli.interactive.app.deletion_progress uses a module listed above it, which is the healthy direction.
27→22 dua_cli.interactive.app.deletion_progress uses dua_cli.interactive.app.navigation✕
- Connections
- 1 pair of types, where a type in dua_cli.interactive.app.deletion_progress uses a type in dua_cli.interactive.app.navigation.
- The types involved
dua_cli.interactive.app.deletion_progress.deletion_progress$module→dua_cli.interactive.app.navigation.Navigation
- Direction
- dua_cli.interactive.app.deletion_progress uses dua_cli.interactive.app.navigation, so a change to dua_cli.interactive.app.navigation can break dua_cli.interactive.app.deletion_progress, while a change to dua_cli.interactive.app.deletion_progress can't break dua_cli.interactive.app.navigation.
- Position
- Below the diagonal: dua_cli.interactive.app.deletion_progress uses a module listed above it, which is the healthy direction.
27→26 dua_cli.interactive.app.deletion_progress uses dua_cli.interactive.app.deletion✕
- Connections
- 2 pairs of types, where a type in dua_cli.interactive.app.deletion_progress uses a type in dua_cli.interactive.app.deletion.
- The types involved
dua_cli.interactive.app.deletion_progress.FilesystemDeletion→dua_cli.interactive.app.deletion.DeletionEventdua_cli.interactive.app.deletion_progress.FilesystemDeletion→dua_cli.interactive.app.deletion.DeletionTask
- Direction
- dua_cli.interactive.app.deletion_progress uses dua_cli.interactive.app.deletion, so a change to dua_cli.interactive.app.deletion can break dua_cli.interactive.app.deletion_progress, while a change to dua_cli.interactive.app.deletion_progress can't break dua_cli.interactive.app.deletion.
- Position
- Below the diagonal: dua_cli.interactive.app.deletion_progress uses a module listed above it, which is the healthy direction.
27→28 dua_cli.interactive.app.deletion_progress uses dua_cli.traverse part of a loop✕
- Connections
- 2 pairs of types, where a type in dua_cli.interactive.app.deletion_progress uses a type in dua_cli.traverse.
- The types involved
dua_cli.interactive.app.deletion_progress.FilesystemDeletion→dua_cli.traverse.TreeIndexdua_cli.interactive.app.deletion_progress.Target→dua_cli.traverse.TreeIndex
- Direction
- dua_cli.interactive.app.deletion_progress uses dua_cli.traverse, so a change to dua_cli.traverse can break dua_cli.interactive.app.deletion_progress, while a change to dua_cli.interactive.app.deletion_progress can't break dua_cli.traverse.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
28→6 dua_cli.traverse uses dua_core.macos✕
- Connections
- 1 pair of types, where a type in dua_cli.traverse uses a type in dua_core.macos.
- The types involved
dua_cli.traverse.traverse$module→dua_core.macos.Metadata
- Direction
- dua_cli.traverse uses dua_core.macos, so a change to dua_core.macos can break dua_cli.traverse, while a change to dua_cli.traverse can't break dua_core.macos.
- Position
- Below the diagonal: dua_cli.traverse uses a module listed above it, which is the healthy direction.
28→9 dua_cli.traverse uses dua_core✕
- Connections
- 2 pairs of types, where a type in dua_cli.traverse uses a type in dua_core.
- The types involved
dua_cli.traverse.TraversalEntry→dua_core.Entrydua_cli.traverse.Tree→dua_core.Entry
- Direction
- dua_cli.traverse uses dua_core, so a change to dua_core can break dua_cli.traverse, while a change to dua_cli.traverse can't break dua_core.
- Position
- Below the diagonal: dua_cli.traverse uses a module listed above it, which is the healthy direction.
28→10 dua_cli.traverse uses dua_cli.common✕
- Connections
- 5 pairs of types, where a type in dua_cli.traverse uses a type in dua_cli.common.
- The types involved
dua_cli.traverse.BackgroundTraversal→dua_cli.common.Throttledua_cli.traverse.BackgroundTraversal→dua_cli.common.WalkOptionsdua_cli.traverse.CleanCandidate→dua_cli.common.WalkOptionsdua_cli.traverse.CleanInput→dua_cli.common.WalkOptionsdua_cli.traverse.traverse$module→dua_cli.common.WalkOptions
- Direction
- dua_cli.traverse uses dua_cli.common, so a change to dua_cli.common can break dua_cli.traverse, while a change to dua_cli.traverse can't break dua_cli.common.
- Position
- Below the diagonal: dua_cli.traverse uses a module listed above it, which is the healthy direction.
28→15 dua_cli.traverse uses dua_cli.inodefilter✕
- Connections
- 2 pairs of types, where a type in dua_cli.traverse uses a type in dua_cli.inodefilter.
- The types involved
dua_cli.traverse.BackgroundTraversal→dua_cli.inodefilter.InodeFilterdua_cli.traverse.traverse$module→dua_cli.inodefilter.InodeFilter
- Direction
- dua_cli.traverse uses dua_cli.inodefilter, so a change to dua_cli.inodefilter can break dua_cli.traverse, while a change to dua_cli.traverse can't break dua_cli.inodefilter.
- Position
- Below the diagonal: dua_cli.traverse uses a module listed above it, which is the healthy direction.
28→27 dua_cli.traverse uses dua_cli.interactive.app.deletion_progress✕
- Connections
- 1 pair of types, where a type in dua_cli.traverse uses a type in dua_cli.interactive.app.deletion_progress.
- The types involved
dua_cli.traverse.Entry→dua_cli.interactive.app.deletion_progress.Target
- Direction
- dua_cli.traverse uses dua_cli.interactive.app.deletion_progress, so a change to dua_cli.interactive.app.deletion_progress can break dua_cli.traverse, while a change to dua_cli.traverse can't break dua_cli.interactive.app.deletion_progress.
- Position
- Below the diagonal: dua_cli.traverse uses a module listed above it, which is the healthy direction.
29→28 dua_cli.interactive uses dua_cli.traverse✕
- Connections
- 2 pairs of types, where a type in dua_cli.interactive uses a type in dua_cli.traverse.
- The types involved
dua_cli.interactive.interactive$module→dua_cli.traverse.Treedua_cli.interactive.interactive$module→dua_cli.traverse.TreeIndex
- Direction
- dua_cli.interactive uses dua_cli.traverse, so a change to dua_cli.traverse can break dua_cli.interactive, while a change to dua_cli.interactive can't break dua_cli.traverse.
- Position
- Below the diagonal: dua_cli.interactive uses a module listed above it, which is the healthy direction.
30→3 dua_cli.interactive.app.clean_hub uses dua_cli.interactive.app.common✕
- Connections
- 1 pair of types, where a type in dua_cli.interactive.app.clean_hub uses a type in dua_cli.interactive.app.common.
- The types involved
dua_cli.interactive.app.clean_hub.HubRow→dua_cli.interactive.app.common.EntryDataBundle
- Direction
- dua_cli.interactive.app.clean_hub uses dua_cli.interactive.app.common, so a change to dua_cli.interactive.app.common can break dua_cli.interactive.app.clean_hub, while a change to dua_cli.interactive.app.clean_hub can't break dua_cli.interactive.app.common.
- Position
- Below the diagonal: dua_cli.interactive.app.clean_hub uses a module listed above it, which is the healthy direction.
30→18 dua_cli.interactive.app.clean_hub uses dua_cli.interactive.app.handlers✕
- Connections
- 1 pair of types, where a type in dua_cli.interactive.app.clean_hub uses a type in dua_cli.interactive.app.handlers.
- The types involved
dua_cli.interactive.app.clean_hub.CleanHub→dua_cli.interactive.app.handlers.CursorDirection
- Direction
- dua_cli.interactive.app.clean_hub uses dua_cli.interactive.app.handlers, so a change to dua_cli.interactive.app.handlers can break dua_cli.interactive.app.clean_hub, while a change to dua_cli.interactive.app.clean_hub can't break dua_cli.interactive.app.handlers.
- Position
- Below the diagonal: dua_cli.interactive.app.clean_hub uses a module listed above it, which is the healthy direction.
30→19 dua_cli.interactive.app.clean_hub uses dua_cli.interactive.widgets.entries✕
- Connections
- 2 pairs of types, where a type in dua_cli.interactive.app.clean_hub uses a type in dua_cli.interactive.widgets.entries.
- The types involved
dua_cli.interactive.app.clean_hub.CleanHub→dua_cli.interactive.widgets.entries.Entriesdua_cli.interactive.app.clean_hub.CleanHub→dua_cli.interactive.widgets.entries.EntriesProps
- Direction
- dua_cli.interactive.app.clean_hub uses dua_cli.interactive.widgets.entries, so a change to dua_cli.interactive.widgets.entries can break dua_cli.interactive.app.clean_hub, while a change to dua_cli.interactive.app.clean_hub can't break dua_cli.interactive.widgets.entries.
- Position
- Below the diagonal: dua_cli.interactive.app.clean_hub uses a module listed above it, which is the healthy direction.
30→22 dua_cli.interactive.app.clean_hub uses dua_cli.interactive.app.navigation✕
- Connections
- 1 pair of types, where a type in dua_cli.interactive.app.clean_hub uses a type in dua_cli.interactive.app.navigation.
- The types involved
dua_cli.interactive.app.clean_hub.CleanHub→dua_cli.interactive.app.navigation.Navigation
- Direction
- dua_cli.interactive.app.clean_hub uses dua_cli.interactive.app.navigation, so a change to dua_cli.interactive.app.navigation can break dua_cli.interactive.app.clean_hub, while a change to dua_cli.interactive.app.clean_hub can't break dua_cli.interactive.app.navigation.
- Position
- Below the diagonal: dua_cli.interactive.app.clean_hub uses a module listed above it, which is the healthy direction.
30→28 dua_cli.interactive.app.clean_hub uses dua_cli.traverse✕
- Connections
- 3 pairs of types, where a type in dua_cli.interactive.app.clean_hub uses a type in dua_cli.traverse.
- The types involved
dua_cli.interactive.app.clean_hub.CleanHub→dua_cli.traverse.Traversaldua_cli.interactive.app.clean_hub.CleanHub→dua_cli.traverse.TreeIndexdua_cli.interactive.app.clean_hub.HubRow→dua_cli.traverse.TreeIndex
- Direction
- dua_cli.interactive.app.clean_hub uses dua_cli.traverse, so a change to dua_cli.traverse can break dua_cli.interactive.app.clean_hub, while a change to dua_cli.interactive.app.clean_hub can't break dua_cli.traverse.
- Position
- Below the diagonal: dua_cli.interactive.app.clean_hub uses a module listed above it, which is the healthy direction.
31→1 dua_cli.interactive.widgets.glob uses dua_cli.interactive.widgets.i18n✕
- Connections
- 2 pairs of types, where a type in dua_cli.interactive.widgets.glob uses a type in dua_cli.interactive.widgets.i18n.
- The types involved
dua_cli.interactive.widgets.glob.GlobPaneProps→dua_cli.interactive.widgets.i18n.Languagedua_cli.interactive.widgets.glob.glob$module→dua_cli.interactive.widgets.i18n.Language
- Direction
- dua_cli.interactive.widgets.glob uses dua_cli.interactive.widgets.i18n, so a change to dua_cli.interactive.widgets.i18n can break dua_cli.interactive.widgets.glob, while a change to dua_cli.interactive.widgets.glob can't break dua_cli.interactive.widgets.i18n.
- Position
- Below the diagonal: dua_cli.interactive.widgets.glob uses a module listed above it, which is the healthy direction.
31→4 dua_cli.interactive.widgets.glob uses dua_core.macos.attributes✕
- Connections
- 1 pair of types, where a type in dua_cli.interactive.widgets.glob uses a type in dua_core.macos.attributes.
- The types involved
dua_cli.interactive.widgets.glob.GlobPane→dua_core.macos.attributes.Cursor
- Direction
- dua_cli.interactive.widgets.glob uses dua_core.macos.attributes, so a change to dua_core.macos.attributes can break dua_cli.interactive.widgets.glob, while a change to dua_cli.interactive.widgets.glob can't break dua_core.macos.attributes.
- Position
- Below the diagonal: dua_cli.interactive.widgets.glob uses a module listed above it, which is the healthy direction.
31→14 dua_cli.interactive.widgets.glob uses dua_cli.config✕
- Connections
- 3 pairs of types, where a type in dua_cli.interactive.widgets.glob uses a type in dua_cli.config.
- The types involved
dua_cli.interactive.widgets.glob.GlobPane→dua_cli.config.KeysConfigdua_cli.interactive.widgets.glob.GlobPaneProps→dua_cli.config.KeysConfigdua_cli.interactive.widgets.glob.glob$module→dua_cli.config.KeysConfig
- Direction
- dua_cli.interactive.widgets.glob uses dua_cli.config, so a change to dua_cli.config can break dua_cli.interactive.widgets.glob, while a change to dua_cli.interactive.widgets.glob can't break dua_cli.config.
- Position
- Below the diagonal: dua_cli.interactive.widgets.glob uses a module listed above it, which is the healthy direction.
31→28 dua_cli.interactive.widgets.glob uses dua_cli.traverse✕
- Connections
- 2 pairs of types, where a type in dua_cli.interactive.widgets.glob uses a type in dua_cli.traverse.
- The types involved
dua_cli.interactive.widgets.glob.glob$module→dua_cli.traverse.Treedua_cli.interactive.widgets.glob.glob$module→dua_cli.traverse.TreeIndex
- Direction
- dua_cli.interactive.widgets.glob uses dua_cli.traverse, so a change to dua_cli.traverse can break dua_cli.interactive.widgets.glob, while a change to dua_cli.interactive.widgets.glob can't break dua_cli.traverse.
- Position
- Below the diagonal: dua_cli.interactive.widgets.glob uses a module listed above it, which is the healthy direction.
32→28 dua_cli.snapshot uses dua_cli.traverse✕
- Connections
- 4 pairs of types, where a type in dua_cli.snapshot uses a type in dua_cli.traverse.
- The types involved
dua_cli.snapshot.DecodedEntry→dua_cli.traverse.EntryDatadua_cli.snapshot.Snapshot→dua_cli.traverse.Traversaldua_cli.snapshot.Snapshot→dua_cli.traverse.TreeIndexdua_cli.snapshot.snapshot$module→dua_cli.traverse.Traversal
- Direction
- dua_cli.snapshot uses dua_cli.traverse, so a change to dua_cli.traverse can break dua_cli.snapshot, while a change to dua_cli.snapshot can't break dua_cli.traverse.
- Position
- Below the diagonal: dua_cli.snapshot uses a module listed above it, which is the healthy direction.
33→6 dua_cli.aggregate uses dua_core.macos✕
- Connections
- 1 pair of types, where a type in dua_cli.aggregate uses a type in dua_core.macos.
- The types involved
dua_cli.aggregate.aggregate$module→dua_core.macos.Metadata
- Direction
- dua_cli.aggregate uses dua_core.macos, so a change to dua_core.macos can break dua_cli.aggregate, while a change to dua_cli.aggregate can't break dua_core.macos.
- Position
- Below the diagonal: dua_cli.aggregate uses a module listed above it, which is the healthy direction.
33→9 dua_cli.aggregate uses dua_core✕
- Connections
- 1 pair of types, where a type in dua_cli.aggregate uses a type in dua_core.
- The types involved
dua_cli.aggregate.aggregate$module→dua_core.Entry
- Direction
- dua_cli.aggregate uses dua_core, so a change to dua_core can break dua_cli.aggregate, while a change to dua_cli.aggregate can't break dua_core.
- Position
- Below the diagonal: dua_cli.aggregate uses a module listed above it, which is the healthy direction.
33→10 dua_cli.aggregate uses dua_cli.common✕
- Connections
- 3 pairs of types, where a type in dua_cli.aggregate uses a type in dua_cli.common.
- The types involved
dua_cli.aggregate.TraversalProgress→dua_cli.common.Throttledua_cli.aggregate.aggregate$module→dua_cli.common.ByteFormatdua_cli.aggregate.aggregate$module→dua_cli.common.WalkOptions
- Direction
- dua_cli.aggregate uses dua_cli.common, so a change to dua_cli.common can break dua_cli.aggregate, while a change to dua_cli.aggregate can't break dua_cli.common.
- Position
- Below the diagonal: dua_cli.aggregate uses a module listed above it, which is the healthy direction.
33→32 dua_cli.aggregate uses dua_cli.snapshot✕
- Connections
- 2 pairs of types, where a type in dua_cli.aggregate uses a type in dua_cli.snapshot.
- The types involved
dua_cli.aggregate.aggregate$module→dua_cli.snapshot.Replaydua_cli.aggregate.aggregate$module→dua_cli.snapshot.Snapshot
- Direction
- dua_cli.aggregate uses dua_cli.snapshot, so a change to dua_cli.snapshot can break dua_cli.aggregate, while a change to dua_cli.aggregate can't break dua_cli.snapshot.
- Position
- Below the diagonal: dua_cli.aggregate uses a module listed above it, which is the healthy direction.
34→4 dua_cli.diff uses dua_core.macos.attributes✕
- Connections
- 1 pair of types, where a type in dua_cli.diff uses a type in dua_core.macos.attributes.
- The types involved
dua_cli.diff.Cursor→dua_core.macos.attributes.Cursor
- Direction
- dua_cli.diff uses dua_core.macos.attributes, so a change to dua_core.macos.attributes can break dua_cli.diff, while a change to dua_cli.diff can't break dua_core.macos.attributes.
- Position
- Below the diagonal: dua_cli.diff uses a module listed above it, which is the healthy direction.
34→10 dua_cli.diff uses dua_cli.common✕
- Connections
- 1 pair of types, where a type in dua_cli.diff uses a type in dua_cli.common.
- The types involved
dua_cli.diff.diff$module→dua_cli.common.ByteFormat
- Direction
- dua_cli.diff uses dua_cli.common, so a change to dua_cli.common can break dua_cli.diff, while a change to dua_cli.diff can't break dua_cli.common.
- Position
- Below the diagonal: dua_cli.diff uses a module listed above it, which is the healthy direction.
34→32 dua_cli.diff uses dua_cli.snapshot✕
- Connections
- 2 pairs of types, where a type in dua_cli.diff uses a type in dua_cli.snapshot.
- The types involved
dua_cli.diff.Cursor→dua_cli.snapshot.ReplayEntriesdua_cli.diff.diff$module→dua_cli.snapshot.Replay
- Direction
- dua_cli.diff uses dua_cli.snapshot, so a change to dua_cli.snapshot can break dua_cli.diff, while a change to dua_cli.diff can't break dua_cli.snapshot.
- Position
- Below the diagonal: dua_cli.diff uses a module listed above it, which is the healthy direction.
35→1 dua_cli.interactive.app.state uses dua_cli.interactive.widgets.i18n✕
- Connections
- 1 pair of types, where a type in dua_cli.interactive.app.state uses a type in dua_cli.interactive.widgets.i18n.
- The types involved
dua_cli.interactive.app.state.AppState→dua_cli.interactive.widgets.i18n.Language
- Direction
- dua_cli.interactive.app.state uses dua_cli.interactive.widgets.i18n, so a change to dua_cli.interactive.widgets.i18n can break dua_cli.interactive.app.state, while a change to dua_cli.interactive.app.state can't break dua_cli.interactive.widgets.i18n.
- Position
- Below the diagonal: dua_cli.interactive.app.state uses a module listed above it, which is the healthy direction.
35→3 dua_cli.interactive.app.state uses dua_cli.interactive.app.common✕
- Connections
- 3 pairs of types, where a type in dua_cli.interactive.app.state uses a type in dua_cli.interactive.app.common.
- The types involved
dua_cli.interactive.app.state.AppState→dua_cli.interactive.app.common.EntryCheckdua_cli.interactive.app.state.AppState→dua_cli.interactive.app.common.EntryDataBundledua_cli.interactive.app.state.AppState→dua_cli.interactive.app.common.SortMode
- Direction
- dua_cli.interactive.app.state uses dua_cli.interactive.app.common, so a change to dua_cli.interactive.app.common can break dua_cli.interactive.app.state, while a change to dua_cli.interactive.app.state can't break dua_cli.interactive.app.common.
- Position
- Below the diagonal: dua_cli.interactive.app.state uses a module listed above it, which is the healthy direction.
35→5 dua_cli.interactive.app.state uses dua_cli.interactive.app.tree_view✕
- Connections
- 1 pair of types, where a type in dua_cli.interactive.app.state uses a type in dua_cli.interactive.app.tree_view.
- The types involved
dua_cli.interactive.app.state.AppState→dua_cli.interactive.app.tree_view.TreeView
- Direction
- dua_cli.interactive.app.state uses dua_cli.interactive.app.tree_view, so a change to dua_cli.interactive.app.tree_view can break dua_cli.interactive.app.state, while a change to dua_cli.interactive.app.state can't break dua_cli.interactive.app.tree_view.
- Position
- Below the diagonal: dua_cli.interactive.app.state uses a module listed above it, which is the healthy direction.
35→9 dua_cli.interactive.app.state uses dua_core✕
- Connections
- 1 pair of types, where a type in dua_cli.interactive.app.state uses a type in dua_core.
- The types involved
dua_cli.interactive.app.state.AppState→dua_core.Event
- Direction
- dua_cli.interactive.app.state uses dua_core, so a change to dua_core can break dua_cli.interactive.app.state, while a change to dua_cli.interactive.app.state can't break dua_core.
- Position
- Below the diagonal: dua_cli.interactive.app.state uses a module listed above it, which is the healthy direction.
35→10 dua_cli.interactive.app.state uses dua_cli.common✕
- Connections
- 2 pairs of types, where a type in dua_cli.interactive.app.state uses a type in dua_cli.common.
- The types involved
dua_cli.interactive.app.state.AppState→dua_cli.common.WalkOptionsdua_cli.interactive.app.state.AppState→dua_cli.common.WalkResult
- Direction
- dua_cli.interactive.app.state uses dua_cli.common, so a change to dua_cli.common can break dua_cli.interactive.app.state, while a change to dua_cli.interactive.app.state can't break dua_cli.common.
- Position
- Below the diagonal: dua_cli.interactive.app.state uses a module listed above it, which is the healthy direction.
35→11 dua_cli.interactive.app.state uses dua_cli.interactive.app.input✕
- Connections
- 1 pair of types, where a type in dua_cli.interactive.app.state uses a type in dua_cli.interactive.app.input.
- The types involved
dua_cli.interactive.app.state.AppState→dua_cli.interactive.app.input.TerminalFocus
- Direction
- dua_cli.interactive.app.state uses dua_cli.interactive.app.input, so a change to dua_cli.interactive.app.input can break dua_cli.interactive.app.state, while a change to dua_cli.interactive.app.state can't break dua_cli.interactive.app.input.
- Position
- Below the diagonal: dua_cli.interactive.app.state uses a module listed above it, which is the healthy direction.
35→14 dua_cli.interactive.app.state uses dua_cli.config✕
- Connections
- 1 pair of types, where a type in dua_cli.interactive.app.state uses a type in dua_cli.config.
- The types involved
dua_cli.interactive.app.state.AppState→dua_cli.config.Config
- Direction
- dua_cli.interactive.app.state uses dua_cli.config, so a change to dua_cli.config can break dua_cli.interactive.app.state, while a change to dua_cli.interactive.app.state can't break dua_cli.config.
- Position
- Below the diagonal: dua_cli.interactive.app.state uses a module listed above it, which is the healthy direction.
35→16 dua_cli.interactive.app.state uses dua_cli.interactive.app.bytevis✕
- Connections
- 1 pair of types, where a type in dua_cli.interactive.app.state uses a type in dua_cli.interactive.app.bytevis.
- The types involved
dua_cli.interactive.app.state.AppState→dua_cli.interactive.app.bytevis.DisplayOptions
- Direction
- dua_cli.interactive.app.state uses dua_cli.interactive.app.bytevis, so a change to dua_cli.interactive.app.bytevis can break dua_cli.interactive.app.state, while a change to dua_cli.interactive.app.state can't break dua_cli.interactive.app.bytevis.
- Position
- Below the diagonal: dua_cli.interactive.app.state uses a module listed above it, which is the healthy direction.
35→18 dua_cli.interactive.app.state uses dua_cli.interactive.app.handlers✕
- Connections
- 4 pairs of types, where a type in dua_cli.interactive.app.state uses a type in dua_cli.interactive.app.handlers.
- The types involved
dua_cli.interactive.app.state.AppState→dua_cli.interactive.app.handlers.AnnotationKinddua_cli.interactive.app.state.AppState→dua_cli.interactive.app.handlers.CursorDirectiondua_cli.interactive.app.state.AppState→dua_cli.interactive.app.handlers.CursorModedua_cli.interactive.app.state.AppState→dua_cli.interactive.app.handlers.MarkEntryMode
- Direction
- dua_cli.interactive.app.state uses dua_cli.interactive.app.handlers, so a change to dua_cli.interactive.app.handlers can break dua_cli.interactive.app.state, while a change to dua_cli.interactive.app.state can't break dua_cli.interactive.app.handlers.
- Position
- Below the diagonal: dua_cli.interactive.app.state uses a module listed above it, which is the healthy direction.
35→19 dua_cli.interactive.app.state uses dua_cli.interactive.widgets.entries✕
- Connections
- 1 pair of types, where a type in dua_cli.interactive.app.state uses a type in dua_cli.interactive.widgets.entries.
- The types involved
dua_cli.interactive.app.state.AppState→dua_cli.interactive.widgets.entries.Column
- Direction
- dua_cli.interactive.app.state uses dua_cli.interactive.widgets.entries, so a change to dua_cli.interactive.widgets.entries can break dua_cli.interactive.app.state, while a change to dua_cli.interactive.app.state can't break dua_cli.interactive.widgets.entries.
- Position
- Below the diagonal: dua_cli.interactive.app.state uses a module listed above it, which is the healthy direction.
35→22 dua_cli.interactive.app.state uses dua_cli.interactive.app.navigation✕
- Connections
- 1 pair of types, where a type in dua_cli.interactive.app.state uses a type in dua_cli.interactive.app.navigation.
- The types involved
dua_cli.interactive.app.state.AppState→dua_cli.interactive.app.navigation.Navigation
- Direction
- dua_cli.interactive.app.state uses dua_cli.interactive.app.navigation, so a change to dua_cli.interactive.app.navigation can break dua_cli.interactive.app.state, while a change to dua_cli.interactive.app.state can't break dua_cli.interactive.app.navigation.
- Position
- Below the diagonal: dua_cli.interactive.app.state uses a module listed above it, which is the healthy direction.
35→24 dua_cli.interactive.app.state uses dua_cli.interactive.widgets.mark✕
- Connections
- 1 pair of types, where a type in dua_cli.interactive.app.state uses a type in dua_cli.interactive.widgets.mark.
- The types involved
dua_cli.interactive.app.state.AppState→dua_cli.interactive.widgets.mark.MarkMode
- Direction
- dua_cli.interactive.app.state uses dua_cli.interactive.widgets.mark, so a change to dua_cli.interactive.widgets.mark can break dua_cli.interactive.app.state, while a change to dua_cli.interactive.app.state can't break dua_cli.interactive.widgets.mark.
- Position
- Below the diagonal: dua_cli.interactive.app.state uses a module listed above it, which is the healthy direction.
35→27 dua_cli.interactive.app.state uses dua_cli.interactive.app.deletion_progress✕
- Connections
- 1 pair of types, where a type in dua_cli.interactive.app.state uses a type in dua_cli.interactive.app.deletion_progress.
- The types involved
dua_cli.interactive.app.state.AppState→dua_cli.interactive.app.deletion_progress.FilesystemDeletion
- Direction
- dua_cli.interactive.app.state uses dua_cli.interactive.app.deletion_progress, so a change to dua_cli.interactive.app.deletion_progress can break dua_cli.interactive.app.state, while a change to dua_cli.interactive.app.state can't break dua_cli.interactive.app.deletion_progress.
- Position
- Below the diagonal: dua_cli.interactive.app.state uses a module listed above it, which is the healthy direction.
35→28 dua_cli.interactive.app.state uses dua_cli.traverse✕
- Connections
- 4 pairs of types, where a type in dua_cli.interactive.app.state uses a type in dua_cli.traverse.
- The types involved
dua_cli.interactive.app.state.AppState→dua_cli.traverse.Traversaldua_cli.interactive.app.state.AppState→dua_cli.traverse.TraversalStatsdua_cli.interactive.app.state.AppState→dua_cli.traverse.TreeIndexdua_cli.interactive.app.state.FilesystemScan→dua_cli.traverse.BackgroundTraversal
- Direction
- dua_cli.interactive.app.state uses dua_cli.traverse, so a change to dua_cli.traverse can break dua_cli.interactive.app.state, while a change to dua_cli.interactive.app.state can't break dua_cli.traverse.
- Position
- Below the diagonal: dua_cli.interactive.app.state uses a module listed above it, which is the healthy direction.
35→30 dua_cli.interactive.app.state uses dua_cli.interactive.app.clean_hub✕
- Connections
- 1 pair of types, where a type in dua_cli.interactive.app.state uses a type in dua_cli.interactive.app.clean_hub.
- The types involved
dua_cli.interactive.app.state.AppState→dua_cli.interactive.app.clean_hub.CleanHub
- Direction
- dua_cli.interactive.app.state uses dua_cli.interactive.app.clean_hub, so a change to dua_cli.interactive.app.clean_hub can break dua_cli.interactive.app.state, while a change to dua_cli.interactive.app.state can't break dua_cli.interactive.app.clean_hub.
- Position
- Below the diagonal: dua_cli.interactive.app.state uses a module listed above it, which is the healthy direction.
35→38 dua_cli.interactive.app.state uses dua_cli.interactive.widgets.main part of a loop✕
- Connections
- 1 pair of types, where a type in dua_cli.interactive.app.state uses a type in dua_cli.interactive.widgets.main.
- The types involved
dua_cli.interactive.app.state.AppState→dua_cli.interactive.widgets.main.MainWindow
- Direction
- dua_cli.interactive.app.state uses dua_cli.interactive.widgets.main, so a change to dua_cli.interactive.widgets.main can break dua_cli.interactive.app.state, while a change to dua_cli.interactive.app.state can't break dua_cli.interactive.widgets.main.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
35→39 dua_cli.interactive.app.state uses dua_cli.interactive.app.eventloop part of a loop✕
- Connections
- 1 pair of types, where a type in dua_cli.interactive.app.state uses a type in dua_cli.interactive.app.eventloop.
- The types involved
dua_cli.interactive.app.state.AppState→dua_cli.interactive.app.eventloop.Refresh
- Direction
- dua_cli.interactive.app.state uses dua_cli.interactive.app.eventloop, so a change to dua_cli.interactive.app.eventloop can break dua_cli.interactive.app.state, while a change to dua_cli.interactive.app.state can't break dua_cli.interactive.app.eventloop.
- 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.
36→10 dua_cli.stacks uses dua_cli.common✕
- Connections
- 1 pair of types, where a type in dua_cli.stacks uses a type in dua_cli.common.
- The types involved
dua_cli.stacks.stacks$module→dua_cli.common.WalkOptions
- Direction
- dua_cli.stacks uses dua_cli.common, so a change to dua_cli.common can break dua_cli.stacks, while a change to dua_cli.stacks can't break dua_cli.common.
- Position
- Below the diagonal: dua_cli.stacks uses a module listed above it, which is the healthy direction.
36→28 dua_cli.stacks uses dua_cli.traverse✕
- Connections
- 4 pairs of types, where a type in dua_cli.stacks uses a type in dua_cli.traverse.
- The types involved
dua_cli.stacks.stacks$module→dua_cli.traverse.Traversaldua_cli.stacks.stacks$module→dua_cli.traverse.TraversalEventdua_cli.stacks.stacks$module→dua_cli.traverse.Treedua_cli.stacks.stacks$module→dua_cli.traverse.TreeIndex
- Direction
- dua_cli.stacks uses dua_cli.traverse, so a change to dua_cli.traverse can break dua_cli.stacks, while a change to dua_cli.stacks can't break dua_cli.traverse.
- Position
- Below the diagonal: dua_cli.stacks uses a module listed above it, which is the healthy direction.
36→32 dua_cli.stacks uses dua_cli.snapshot✕
- Connections
- 1 pair of types, where a type in dua_cli.stacks uses a type in dua_cli.snapshot.
- The types involved
dua_cli.stacks.stacks$module→dua_cli.snapshot.Replay
- Direction
- dua_cli.stacks uses dua_cli.snapshot, so a change to dua_cli.snapshot can break dua_cli.stacks, while a change to dua_cli.stacks can't break dua_cli.snapshot.
- Position
- Below the diagonal: dua_cli.stacks uses a module listed above it, which is the healthy direction.
37→10 dua_cli.tree uses dua_cli.common✕
- Connections
- 2 pairs of types, where a type in dua_cli.tree uses a type in dua_cli.common.
- The types involved
dua_cli.tree.tree$module→dua_cli.common.ByteFormatdua_cli.tree.tree$module→dua_cli.common.WalkOptions
- Direction
- dua_cli.tree uses dua_cli.common, so a change to dua_cli.common can break dua_cli.tree, while a change to dua_cli.tree can't break dua_cli.common.
- Position
- Below the diagonal: dua_cli.tree uses a module listed above it, which is the healthy direction.
37→28 dua_cli.tree uses dua_cli.traverse✕
- Connections
- 3 pairs of types, where a type in dua_cli.tree uses a type in dua_cli.traverse.
- The types involved
dua_cli.tree.tree$module→dua_cli.traverse.Traversaldua_cli.tree.tree$module→dua_cli.traverse.Treedua_cli.tree.tree$module→dua_cli.traverse.TreeIndex
- Direction
- dua_cli.tree uses dua_cli.traverse, so a change to dua_cli.traverse can break dua_cli.tree, while a change to dua_cli.tree can't break dua_cli.traverse.
- Position
- Below the diagonal: dua_cli.tree uses a module listed above it, which is the healthy direction.
37→32 dua_cli.tree uses dua_cli.snapshot✕
- Connections
- 1 pair of types, where a type in dua_cli.tree uses a type in dua_cli.snapshot.
- The types involved
dua_cli.tree.tree$module→dua_cli.snapshot.Replay
- Direction
- dua_cli.tree uses dua_cli.snapshot, so a change to dua_cli.snapshot can break dua_cli.tree, while a change to dua_cli.tree can't break dua_cli.snapshot.
- Position
- Below the diagonal: dua_cli.tree uses a module listed above it, which is the healthy direction.
38→1 dua_cli.interactive.widgets.main uses dua_cli.interactive.widgets.i18n✕
- Connections
- 1 pair of types, where a type in dua_cli.interactive.widgets.main uses a type in dua_cli.interactive.widgets.i18n.
- The types involved
dua_cli.interactive.widgets.main.main$module→dua_cli.interactive.widgets.i18n.Language
- Direction
- dua_cli.interactive.widgets.main uses dua_cli.interactive.widgets.i18n, so a change to dua_cli.interactive.widgets.i18n can break dua_cli.interactive.widgets.main, while a change to dua_cli.interactive.widgets.main can't break dua_cli.interactive.widgets.i18n.
- Position
- Below the diagonal: dua_cli.interactive.widgets.main uses a module listed above it, which is the healthy direction.
38→4 dua_cli.interactive.widgets.main uses dua_core.macos.attributes✕
- Connections
- 1 pair of types, where a type in dua_cli.interactive.widgets.main uses a type in dua_core.macos.attributes.
- The types involved
dua_cli.interactive.widgets.main.MainWindow→dua_core.macos.attributes.Cursor
- Direction
- dua_cli.interactive.widgets.main uses dua_core.macos.attributes, so a change to dua_core.macos.attributes can break dua_cli.interactive.widgets.main, while a change to dua_cli.interactive.widgets.main can't break dua_core.macos.attributes.
- Position
- Below the diagonal: dua_cli.interactive.widgets.main uses a module listed above it, which is the healthy direction.
38→14 dua_cli.interactive.widgets.main uses dua_cli.config✕
- Connections
- 2 pairs of types, where a type in dua_cli.interactive.widgets.main uses a type in dua_cli.config.
- The types involved
dua_cli.interactive.widgets.main.MainWindowProps→dua_cli.config.Configdua_cli.interactive.widgets.main.main$module→dua_cli.config.KeysConfig
- Direction
- dua_cli.interactive.widgets.main uses dua_cli.config, so a change to dua_cli.config can break dua_cli.interactive.widgets.main, while a change to dua_cli.interactive.widgets.main can't break dua_cli.config.
- Position
- Below the diagonal: dua_cli.interactive.widgets.main uses a module listed above it, which is the healthy direction.
38→16 dua_cli.interactive.widgets.main uses dua_cli.interactive.app.bytevis✕
- Connections
- 1 pair of types, where a type in dua_cli.interactive.widgets.main uses a type in dua_cli.interactive.app.bytevis.
- The types involved
dua_cli.interactive.widgets.main.MainWindowProps→dua_cli.interactive.app.bytevis.DisplayOptions
- Direction
- dua_cli.interactive.widgets.main uses dua_cli.interactive.app.bytevis, so a change to dua_cli.interactive.app.bytevis can break dua_cli.interactive.widgets.main, while a change to dua_cli.interactive.widgets.main can't break dua_cli.interactive.app.bytevis.
- Position
- Below the diagonal: dua_cli.interactive.widgets.main uses a module listed above it, which is the healthy direction.
38→19 dua_cli.interactive.widgets.main uses dua_cli.interactive.widgets.entries✕
- Connections
- 1 pair of types, where a type in dua_cli.interactive.widgets.main uses a type in dua_cli.interactive.widgets.entries.
- The types involved
dua_cli.interactive.widgets.main.MainWindow→dua_cli.interactive.widgets.entries.Entries
- Direction
- dua_cli.interactive.widgets.main uses dua_cli.interactive.widgets.entries, so a change to dua_cli.interactive.widgets.entries can break dua_cli.interactive.widgets.main, while a change to dua_cli.interactive.widgets.main can't break dua_cli.interactive.widgets.entries.
- Position
- Below the diagonal: dua_cli.interactive.widgets.main uses a module listed above it, which is the healthy direction.
38→23 dua_cli.interactive.widgets.main uses dua_cli.interactive.widgets.help✕
- Connections
- 1 pair of types, where a type in dua_cli.interactive.widgets.main uses a type in dua_cli.interactive.widgets.help.
- The types involved
dua_cli.interactive.widgets.main.MainWindow→dua_cli.interactive.widgets.help.HelpPane
- Direction
- dua_cli.interactive.widgets.main uses dua_cli.interactive.widgets.help, so a change to dua_cli.interactive.widgets.help can break dua_cli.interactive.widgets.main, while a change to dua_cli.interactive.widgets.main can't break dua_cli.interactive.widgets.help.
- Position
- Below the diagonal: dua_cli.interactive.widgets.main uses a module listed above it, which is the healthy direction.
38→24 dua_cli.interactive.widgets.main uses dua_cli.interactive.widgets.mark✕
- Connections
- 1 pair of types, where a type in dua_cli.interactive.widgets.main uses a type in dua_cli.interactive.widgets.mark.
- The types involved
dua_cli.interactive.widgets.main.MainWindow→dua_cli.interactive.widgets.mark.MarkPane
- Direction
- dua_cli.interactive.widgets.main uses dua_cli.interactive.widgets.mark, so a change to dua_cli.interactive.widgets.mark can break dua_cli.interactive.widgets.main, while a change to dua_cli.interactive.widgets.main can't break dua_cli.interactive.widgets.mark.
- Position
- Below the diagonal: dua_cli.interactive.widgets.main uses a module listed above it, which is the healthy direction.
38→31 dua_cli.interactive.widgets.main uses dua_cli.interactive.widgets.glob✕
- Connections
- 1 pair of types, where a type in dua_cli.interactive.widgets.main uses a type in dua_cli.interactive.widgets.glob.
- The types involved
dua_cli.interactive.widgets.main.MainWindow→dua_cli.interactive.widgets.glob.GlobPane
- Direction
- dua_cli.interactive.widgets.main uses dua_cli.interactive.widgets.glob, so a change to dua_cli.interactive.widgets.glob can break dua_cli.interactive.widgets.main, while a change to dua_cli.interactive.widgets.main can't break dua_cli.interactive.widgets.glob.
- Position
- Below the diagonal: dua_cli.interactive.widgets.main uses a module listed above it, which is the healthy direction.
38→35 dua_cli.interactive.widgets.main uses dua_cli.interactive.app.state✕
- Connections
- 2 pairs of types, where a type in dua_cli.interactive.widgets.main uses a type in dua_cli.interactive.app.state.
- The types involved
dua_cli.interactive.widgets.main.MainWindowProps→dua_cli.interactive.app.state.AppStatedua_cli.interactive.widgets.main.main$module→dua_cli.interactive.app.state.FocussedPane
- Direction
- dua_cli.interactive.widgets.main uses dua_cli.interactive.app.state, so a change to dua_cli.interactive.app.state can break dua_cli.interactive.widgets.main, while a change to dua_cli.interactive.widgets.main can't break dua_cli.interactive.app.state.
- Position
- Below the diagonal: dua_cli.interactive.widgets.main uses a module listed above it, which is the healthy direction.
39→4 dua_cli.interactive.app.eventloop uses dua_core.macos.attributes✕
- Connections
- 1 pair of types, where a type in dua_cli.interactive.app.eventloop uses a type in dua_core.macos.attributes.
- The types involved
dua_cli.interactive.app.eventloop.eventloop$module→dua_core.macos.attributes.Cursor
- Direction
- dua_cli.interactive.app.eventloop uses dua_core.macos.attributes, so a change to dua_core.macos.attributes can break dua_cli.interactive.app.eventloop, while a change to dua_cli.interactive.app.eventloop can't break dua_core.macos.attributes.
- Position
- Below the diagonal: dua_cli.interactive.app.eventloop uses a module listed above it, which is the healthy direction.
39→38 dua_cli.interactive.app.eventloop uses dua_cli.interactive.widgets.main✕
- Connections
- 2 pairs of types, where a type in dua_cli.interactive.app.eventloop uses a type in dua_cli.interactive.widgets.main.
- The types involved
dua_cli.interactive.app.eventloop.eventloop$module→dua_cli.interactive.widgets.main.MainWindowdua_cli.interactive.app.eventloop.eventloop$module→dua_cli.interactive.widgets.main.MainWindowProps
- Direction
- dua_cli.interactive.app.eventloop uses dua_cli.interactive.widgets.main, so a change to dua_cli.interactive.widgets.main can break dua_cli.interactive.app.eventloop, while a change to dua_cli.interactive.app.eventloop can't break dua_cli.interactive.widgets.main.
- Position
- Below the diagonal: dua_cli.interactive.app.eventloop uses a module listed above it, which is the healthy direction.
40→1 dua_cli.interactive.app.terminal uses dua_cli.interactive.widgets.i18n✕
- Connections
- 1 pair of types, where a type in dua_cli.interactive.app.terminal uses a type in dua_cli.interactive.widgets.i18n.
- The types involved
dua_cli.interactive.app.terminal.terminal$module→dua_cli.interactive.widgets.i18n.Language
- Direction
- dua_cli.interactive.app.terminal uses dua_cli.interactive.widgets.i18n, so a change to dua_cli.interactive.widgets.i18n can break dua_cli.interactive.app.terminal, while a change to dua_cli.interactive.app.terminal can't break dua_cli.interactive.widgets.i18n.
- Position
- Below the diagonal: dua_cli.interactive.app.terminal uses a module listed above it, which is the healthy direction.
40→10 dua_cli.interactive.app.terminal uses dua_cli.common✕
- Connections
- 2 pairs of types, where a type in dua_cli.interactive.app.terminal uses a type in dua_cli.common.
- The types involved
dua_cli.interactive.app.terminal.TerminalApp→dua_cli.common.ByteFormatdua_cli.interactive.app.terminal.TerminalApp→dua_cli.common.WalkOptions
- Direction
- dua_cli.interactive.app.terminal uses dua_cli.common, so a change to dua_cli.common can break dua_cli.interactive.app.terminal, while a change to dua_cli.interactive.app.terminal can't break dua_cli.common.
- Position
- Below the diagonal: dua_cli.interactive.app.terminal uses a module listed above it, which is the healthy direction.
40→14 dua_cli.interactive.app.terminal uses dua_cli.config✕
- Connections
- 1 pair of types, where a type in dua_cli.interactive.app.terminal uses a type in dua_cli.config.
- The types involved
dua_cli.interactive.app.terminal.TerminalApp→dua_cli.config.Config
- Direction
- dua_cli.interactive.app.terminal uses dua_cli.config, so a change to dua_cli.config can break dua_cli.interactive.app.terminal, while a change to dua_cli.interactive.app.terminal can't break dua_cli.config.
- Position
- Below the diagonal: dua_cli.interactive.app.terminal uses a module listed above it, which is the healthy direction.
40→16 dua_cli.interactive.app.terminal uses dua_cli.interactive.app.bytevis✕
- Connections
- 1 pair of types, where a type in dua_cli.interactive.app.terminal uses a type in dua_cli.interactive.app.bytevis.
- The types involved
dua_cli.interactive.app.terminal.TerminalApp→dua_cli.interactive.app.bytevis.DisplayOptions
- Direction
- dua_cli.interactive.app.terminal uses dua_cli.interactive.app.bytevis, so a change to dua_cli.interactive.app.bytevis can break dua_cli.interactive.app.terminal, while a change to dua_cli.interactive.app.terminal can't break dua_cli.interactive.app.bytevis.
- Position
- Below the diagonal: dua_cli.interactive.app.terminal uses a module listed above it, which is the healthy direction.
40→28 dua_cli.interactive.app.terminal uses dua_cli.traverse✕
- Connections
- 3 pairs of types, where a type in dua_cli.interactive.app.terminal uses a type in dua_cli.traverse.
- The types involved
dua_cli.interactive.app.terminal.TerminalApp→dua_cli.traverse.Traversaldua_cli.interactive.app.terminal.TerminalApp→dua_cli.traverse.TraversalStatsdua_cli.interactive.app.terminal.terminal$module→dua_cli.traverse.Traversal
- Direction
- dua_cli.interactive.app.terminal uses dua_cli.traverse, so a change to dua_cli.traverse can break dua_cli.interactive.app.terminal, while a change to dua_cli.interactive.app.terminal can't break dua_cli.traverse.
- Position
- Below the diagonal: dua_cli.interactive.app.terminal uses a module listed above it, which is the healthy direction.
40→35 dua_cli.interactive.app.terminal uses dua_cli.interactive.app.state✕
- Connections
- 1 pair of types, where a type in dua_cli.interactive.app.terminal uses a type in dua_cli.interactive.app.state.
- The types involved
dua_cli.interactive.app.terminal.TerminalApp→dua_cli.interactive.app.state.AppState
- Direction
- dua_cli.interactive.app.terminal uses dua_cli.interactive.app.state, so a change to dua_cli.interactive.app.state can break dua_cli.interactive.app.terminal, while a change to dua_cli.interactive.app.terminal can't break dua_cli.interactive.app.state.
- Position
- Below the diagonal: dua_cli.interactive.app.terminal uses a module listed above it, which is the healthy direction.
40→38 dua_cli.interactive.app.terminal uses dua_cli.interactive.widgets.main✕
- Connections
- 1 pair of types, where a type in dua_cli.interactive.app.terminal uses a type in dua_cli.interactive.widgets.main.
- The types involved
dua_cli.interactive.app.terminal.TerminalApp→dua_cli.interactive.widgets.main.MainWindow
- Direction
- dua_cli.interactive.app.terminal uses dua_cli.interactive.widgets.main, so a change to dua_cli.interactive.widgets.main can break dua_cli.interactive.app.terminal, while a change to dua_cli.interactive.app.terminal can't break dua_cli.interactive.widgets.main.
- Position
- Below the diagonal: dua_cli.interactive.app.terminal uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Event Sourcing
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 32 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 11 | Medium |
| A02:2025 — Security Misconfiguration | 5 | High / Critical |
Roadmap
Begin by resolving the eleven code churn and complexity hotspots in main.rs, mod.rs, and traverse.rs to stabilize the codebase. Simultaneously, establish architectural governance by documenting significant design decisions in the docs/adr folder and adding a high-level architecture overview to the root README. Finally, enable automated dependency review tools such as Dependabot or Renovate to ensure ongoing security and maintenance.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +10.5 pts | Low | ADR Quality |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +9.8 pts | Medium | Architecture documentation |
| Add an 'Architecture' / 'How it works' section to the root README — the high-level shape. | +3.2 pts | Medium | Documentation (README) |
| Resolve the 11 Hotspot finding(s) in Churn × Complexity Hotspots — start with main.rs (2), mod.rs (2), traverse.rs. | +2.7 pts | High | Churn × Complexity Hotspots |
| Enable Dependabot/Renovate or a dependency-review gate. | +2.4 pts | Medium | Security & performance tooling |
| Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it. | +2.1 pts | Medium | Deployment & Rollback |
| Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. | +0.5 pts | Low | Static Analysis (SAST) |
| Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). | +0.5 pts | Low | Static Analysis (SAST) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 0.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.0 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 5.9 | Mixed | Dependency Vulnerabilities: Medium advisory (unsound): REDACTED |
| src/interactive/app/eventloop.rs | 7.0 | Mixed | Cyclomatic Complexity: AppState::process_terminal_event (cyclomatic 54) |
| src/traverse.rs | 7.0 | Mixed | Cyclomatic Complexity: BackgroundTraversal::integrate_traversal_event (cyclomatic 42) |
| src/snapshot/mod.rs | 7.0 | Mixed | Cyclomatic Complexity: Decoder::next_entry (cyclomatic 18) |
| src/main.rs | 7.1 | Mixed | Cyclomatic Complexity: dua_cli::main (cyclomatic 39) |
| src/diff.rs | 7.2 | Mixed | Cyclomatic Complexity: dua_cli::diff::walk_changes (cyclomatic 23) |
| crates/dua-lib/src/lib.rs | 7.2 | Mixed | Cyclomatic Complexity: dua_core::read_dir_native (cyclomatic 18) |
| src/interactive/widgets/entries.rs | 7.2 | Mixed | Cognitive Complexity: DisplayPath::compact_by_removing_components (cognitive 18) |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| crates/dua-lib/src/macos/attributes.rs | 7.4 | Mixed | Cyclomatic Complexity: dua_core::macos::attributes::parse_record (cyclomatic 44) |
| src/clean.rs | 7.4 | Mixed | Cyclomatic Complexity: dua_cli::clean::discover (cyclomatic 39) |
| src/interactive/app/deletion_progress.rs | 7.4 | Mixed | Cyclomatic Complexity: AppState::flush_deletion (cyclomatic 36) |
| src/aggregate.rs | 7.4 | Mixed | Cyclomatic Complexity: dua_cli::aggregate::aggregate_inner (cyclomatic 21) |
| src/interactive/widgets/main.rs | 7.4 | Mixed | Cyclomatic Complexity: MainWindow::render (cyclomatic 17) |
| src/interactive/widgets/mark.rs | 7.4 | Mixed | Cyclomatic Complexity: MarkPane::process_events (cyclomatic 16) |
| src/interactive/widgets/i18n.rs | 7.4 | Mixed | God Classes: TooManyFields: UiText |
| src/interactive/app/clean_hub.rs | 7.8 | Mixed | Cyclomatic Complexity: AppState::process_clean_key (cyclomatic 28) |
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. 47 of 47 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 — 47 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, 136 of 161 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.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (78 contributor(s) across 1329 commit(s) sampled, automation and bot accounts excluded). One of them holds 84% of the history; the other 77 hold 0.2% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D19 Documentation Quality — measured, with a gap in what it reached — 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.
- 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. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- 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.
- D44 Platform End-of-Life — 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 dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a Dockerfile) is simply not read here yet.
- AX6 Interface segregation — not measured this run — 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) — -------------------- 1 | >>> from guangie88/rustfmt-clippy:nightly 2 | 3 | run cargo install hyperfine watchexec -------------------- ERROR: failed to solve: guangie88/rustfmt-clippy:nightly: failed to resolve source metadata for docker.io/guangie88/rustfmt-clippy:nightly: failed to do request: Head "https://registry-1.docker.io/v2/guangie88/rustfmt-clippy/manifests/nightly": 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.
- 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.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- 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.
- 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.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
15 function(s) exceeded the cyclomatic complexity threshold of 15; the worst was AppState::process_terminal_event at 54. A further 4 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 Key::from_str at 29 — they are counted neither in the figure above nor in this dimension's score. 2 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold functions was excluded, so the exclusion is disclosed nowhere in the file itself: src/config.rs (Key::from_str at 29), src/interactive/widgets/i18n.rs (Language::annotation_message at 16). 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 15 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with AppState::process_terminal_event (cyclomatic 54), dua_core::macos::attributes::parse_record (cyclomatic 44), BackgroundTraversal::integrate_traversal_event (cyclomatic 42). — 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 15 together lifts Cyclomatic Complexity from 7.4 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- 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
27 function(s) exceeded the cognitive complexity threshold of 15; the worst was BackgroundTraversal::integrate_traversal_event at 84.
What to do
- Bring the 9 bodies over 30 down to 30 or less in Cognitive Complexity — start with BackgroundTraversal::integrate_traversal_event (cognitive 84), dua_cli::clean::discover (cognitive 82), dua_cli::main (cognitive 73). — 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 9 together lifts Cognitive Complexity from 4.7 to about 6.7/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
30 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 10 MethodTooLong finding(s) in God Classes — start with eventloop.rs (4), traverse.rs, mark.rs. — One of this dimension's main actionable groups (10 warning-level).
- Resolve the 8 FileTooLong finding(s) in God Classes — start with traverse.rs, lib.rs, i18n.rs. — One of this dimension's main actionable groups (8 warning-level).
- Resolve the 6 FunctionTooLong finding(s) in God Classes — start with main.rs, aggregate.rs, attributes.rs. — One of this dimension's main actionable groups (6 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
4 duplicated block group(s) detected.
What to do
- Resolve the 1 Duplicated block (14 lines × 3) finding(s) in Code Duplication — start with entries.rs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (11–12 lines × 2) finding(s) in Code Duplication — start with eventloop.rs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with entries.rs. — One of this dimension's main actionable groups (1 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.
D5 · Coupling
2 production modules (Cargo), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 1 module(s) off the main sequence.
What to do
- Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
0 of 42 classes have LCOM4 above 3.
D9 · Test Distribution
334 test methods: 301 unit, 33 integration, 0 BDD, 0 e2e. The Rust suite contributes 334 `#[test]` function(s) across 40 file(s) declaring at least one; its unit/integration split is Cargo's own — 6 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
0 flaky across 1 measured tier(s). Rust (repository root, 40 test files): measured (0 flaky).
D12 · Dependency Hygiene
17 outdated, 0 yanked direct Cargo dependencies. 32 of 33 direct crates were graded against crates.io (0 not published there, 1 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
- 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 361 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/main.rs (41×39=1599); src/traverse.rs (25×42=1050); src/interactive/app/eventloop.rs (14×54=756)
What to do
- Resolve the 11 Hotspot finding(s) in Churn × Complexity Hotspots — start with main.rs (2), mod.rs (2), traverse.rs. — One of this dimension's main actionable groups (11 warning-level).
D17 · Explicit Debt
2 deducted task-comment markers across 25672 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 2 TodoComment finding(s) in Explicit Debt — start with glob.rs, journeys_readonly.rs. — One of this dimension's main actionable groups (2 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. 1 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
0 of 2 build units (Cargo) flagged as possibly oversized/incoherent.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
32 finding(s): 0 critical, 24 high, 8 medium, 0 low. 19 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 1 file(s) — `crates/dua-lib/src/windows.rs` (line 68, line 77, line 224, …) — 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 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 19 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (19 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
6 finding(s): 0 critical, 0 high, 6 medium, 0 low.
What to do
- Resolve the 3 Medium advisory (unsound) finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 3 Medium vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 warning-level).
D31 · IaC & Container Security
5 finding(s): 0 critical, 3 high, 2 medium, 0 low.
What to do
- Resolve the 3 High IaC finding(s) in IaC & Container Security — start with REDACTED (3). — One of this dimension's main actionable groups (3 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 40 of the 48 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
2/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
Frontend & cross-cutting dimensions
AX10 · Code composition
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
ES1 · Fold determinism
ES2 · Immutable events
M1 · Documentation (README)
What to do
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Add a README to the 1 of 1 project(s) that lack one — worth up to 2 pts.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
P3 · Security & performance tooling
What to do
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
What to do
- Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
P6 · Release Hygiene
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 | 88% | Strong | Solid. |
| Architecture | 95% | Exemplary | Solid. |
| Maturity | 55% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 68% | Adequate | Acceptable, with room to improve. |
| Security | 76% | Adequate — gated by D29 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Event Sourcing | 100% | Exemplary | Strongest area. |
Unscored — 2 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 71 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) — -------------------- 1 | >>> from guangie88/rustfmt-clippy:nightly 2 | 3 | run cargo install hyperfine watchexec -------------------- ERROR: failed to solve: guangie88/rustfmt-clippy:nightly: failed to resolve source metadata for docker.io/guangie88/rustfmt-clippy:nightly: failed to do request: Head "https://registry-1.docker.io/v2/guangie88/rustfmt-clippy/manifests/nightly": 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 — ~4548 lines of test source are present (.rs) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — 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. Aggregate roots were found in only one source directory (interactive), which is a layered codebase, not two contexts. 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.
- D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — applicable but not scored (3 signals for this style, 3 needed — the count is met but a required primary signal is absent): 2 aggregate root(s) (types guarding their own state behind command methods — this language has no AggregateRoot base to inherit); 14 value object(s); 4 domain event(s); its domain events are published by services or handlers — no domain entity raises one; no aggregate is declared and no domain structure surrounds the state-guarding types: not claimed as DDD
- 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
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- M4 Documentation accuracy — Not applicable: the 1 current-state document(s) make no claim of a kind M4 checks. 1 claim(s) of kinds M4 does not check were not checked (environment variable 1); M4 checks only links and versions.
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the Rust source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — 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
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `#[bench]`, criterion's `bench_function`/`bench_with_input`, `#[divan::bench]` or `#[library_benchmark]` in any `.rs` file, or criterion, divan, iai or a `[[bench]]` target in a Cargo.toml, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not 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.
- PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
- S1 Web-Security Posture — No web surface: 46 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.
- 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.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 27 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 109 finding(s)
- Hotspot: src/main.rs src/main.rs:95
- Hotspot: src/traverse.rs src/traverse.rs:1274
- Hotspot: src/interactive/app/eventloop.rs src/interactive/app/eventloop.rs:647
- Hotspot: src/aggregate.rs src/aggregate.rs:268
- Hotspot: crates/dua-lib/src/lib.rs crates/dua-lib/src/lib.rs:1163
- Hotspot: crates/dua-lib/src/macos/mod.rs crates/dua-lib/src/macos/mod.rs:362
- Hotspot: src/interactive/widgets/mark.rs src/interactive/widgets/mark.rs:166
- Hotspot: crates/dua-lib/src/macos/attributes.rs crates/dua-lib/src/macos/attributes.rs:174
- Hotspot: src/interactive/widgets/main.rs src/interactive/widgets/main.rs:48
- Hotspot: src/interactive/app/common.rs src/interactive/app/common.rs:132
- Hotspot: src/snapshot/mod.rs src/snapshot/mod.rs:547
- MethodTooLong: BackgroundTraversal.integrate_traversal_event src/traverse.rs:1274
- MethodTooLong: MarkPane.render src/interactive/widgets/mark.rs:252
- MethodTooLong: HelpPane.render src/interactive/widgets/help.rs:70
- MethodTooLong: AppState.process_terminal_event src/interactive/app/eventloop.rs:647
- MethodTooLong: MainWindow.render src/interactive/widgets/main.rs:48
- MethodTooLong: AppState.flush_deletion src/interactive/app/deletion_progress.rs:186
- MethodTooLong: AppState.process_event src/interactive/app/eventloop.rs:438
- MethodTooLong: AppState.scan_parent src/interactive/app/eventloop.rs:191
- MethodTooLong: Decoder.next_entry src/snapshot/mod.rs:547
- MethodTooLong: AppState.refresh src/interactive/app/eventloop.rs:829
- dua_cli::clean::discover (cognitive 82) src/clean.rs:42
- dua_cli::main (cognitive 73) src/main.rs:95
- dua_cli::diff::walk_changes (cognitive 47) src/diff.rs:365
- dua_cli::aggregate::aggregate_inner (cognitive 41) src/aggregate.rs:268
- dua_cli::snapshot::write_raw (cognitive 29) src/snapshot/mod.rs:310
- dua_cli::traverse::walk_clean_candidates (cognitive 26) src/traverse.rs:1628
- dua_cli::extract_aggregate_inputs_maybe_set_cwd (cognitive 24) src/main.rs:767
- dua_cli::interactive::app::deletion::delete_directory_recursively (cognitive 20) src/interactive/app/deletion.rs:137
- dua_cli::clean::git::has_tracked_paths (cognitive 19) src/clean/git.rs:101
- FileTooLong: src/traverse.rs src/traverse.rs
- FileTooLong: src/lib.rs crates/dua-lib/src/lib.rs
- FileTooLong: widgets/i18n.rs src/interactive/widgets/i18n.rs
- FileTooLong: app/eventloop.rs src/interactive/app/eventloop.rs
- FileTooLong: src/main.rs src/main.rs
- FileTooLong: snapshot/mod.rs src/snapshot/mod.rs
- FileTooLong: src/diff.rs src/diff.rs
- FileTooLong: widgets/entries.rs src/interactive/widgets/entries.rs
- FunctionTooLong: dua_cli::main src/main.rs:95
- FunctionTooLong: dua_cli::aggregate::aggregate_inner src/aggregate.rs:268
- FunctionTooLong: dua_core::macos::attributes::parse_record crates/dua-lib/src/macos/attributes.rs:174
- FunctionTooLong: dua_cli::clean::discover src/clean.rs:42
- FunctionTooLong: dua_cli::snapshot::write_raw src/snapshot/mod.rs:310
- FunctionTooLong: dua_cli::traverse::walk_clean_candidates src/traverse.rs:1628
- dua_cli::clean::discover (cyclomatic 39) src/clean.rs:42
- dua_cli::main (cyclomatic 39) src/main.rs:95
- dua_cli::diff::walk_changes (cyclomatic 23) src/diff.rs:365
- dua_cli::aggregate::aggregate_inner (cyclomatic 21) src/aggregate.rs:268
- dua_cli::traverse::walk_clean_candidates (cyclomatic 17) src/traverse.rs:1628
- AppState::flush_deletion (cognitive 62) src/interactive/app/deletion_progress.rs:186
- AppState::process_terminal_event (cognitive 56) src/interactive/app/eventloop.rs:647
- AppState::process_clean_key (cognitive 34) src/interactive/app/clean_hub.rs:292
- AppState::refresh (cognitive 28) src/interactive/app/eventloop.rs:829
- AppState::scan_parent (cognitive 17) src/interactive/app/eventloop.rs:191
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- AppState::process_terminal_event (cyclomatic 54) src/interactive/app/eventloop.rs:647
- AppState::flush_deletion (cyclomatic 36) src/interactive/app/deletion_progress.rs:186
- AppState::process_clean_key (cyclomatic 28) src/interactive/app/clean_hub.rs:292
- AppState::refresh (cyclomatic 19) src/interactive/app/eventloop.rs:829
- TooManyFields: UiText src/interactive/widgets/i18n.rs:493
- TooManyFields: HelpText src/interactive/widgets/i18n.rs:102
- TooManyFields: KeysConfig src/config.rs:426
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- dua_core::macos::attributes::parse_record (cyclomatic 44) crates/dua-lib/src/macos/attributes.rs:174
- dua_core::read_dir_native (cyclomatic 18) crates/dua-lib/src/lib.rs:1163
- TodoComment src/interactive/widgets/glob.rs:39
- TodoComment src/interactive/app/tests/journeys_readonly.rs:558
- BackgroundTraversal::integrate_traversal_event (cognitive 84) src/traverse.rs:1274
- BackgroundTraversal::start_inner (cognitive 17) src/traverse.rs:1043
- dua_core::macos::attributes::parse_record (cognitive 62) crates/dua-lib/src/macos/attributes.rs:174
- dua_core::read_dir_native (cognitive 25) crates/dua-lib/src/lib.rs:1163
- ReadDir::refill (cognitive 25) crates/dua-lib/src/macos/mod.rs:362
- ReadDir::probe_metadata_with_cpu_time (cognitive 18) crates/dua-lib/src/macos/mod.rs:284
- REDACTED
- REDACTED
- TooManyMethods: AppState src/interactive/app/state.rs:42
- TooManyMethods: Tree src/traverse.rs:234
- REDACTED
- REDACTED
- BackgroundTraversal::integrate_traversal_event (cyclomatic 42) src/traverse.rs:1274
- Decoder::next_entry (cyclomatic 18) src/snapshot/mod.rs:547
- MainWindow::render (cyclomatic 17) src/interactive/widgets/main.rs:48
- MarkPane::process_events (cyclomatic 16) src/interactive/widgets/mark.rs:166
- SnapshotReader::read (cognitive 29) src/snapshot/mod.rs:110
- MarkPane::render (cognitive 25) src/interactive/widgets/mark.rs:252
- MainWindow::render (cognitive 24) src/interactive/widgets/main.rs:48
- Decoder::next_entry (cognitive 24) src/snapshot/mod.rs:547
- Walk::next_with_cancellation (cognitive 18) crates/dua-lib/src/lib.rs:555
- DisplayPath::compact_by_removing_components (cognitive 18) src/interactive/widgets/entries.rs:332
- CleanCandidate::forward_entry (cognitive 17) src/traverse.rs:1559
- REDACTED
- ClassTooLong: BackgroundTraversal src/traverse.rs:812
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (14 lines × 3) src/interactive/widgets/entries.rs:472
- Duplicated block (11–12 lines × 2) src/interactive/app/eventloop.rs:192
- Duplicated block (10 lines × 2) src/interactive/widgets/entries.rs:468
- Duplicated block (9 lines × 2) src/diff.rs:447
- Off the main sequence: dua-core
Minor — 8 finding(s)
- No ADRs found
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- No release approval gate
- Duplicated predicate crates/dua-lib/src/macos/mod.rs:317
- Silent fallback default on Err src/interactive/app/gitignore.rs:47
Minor — 17 finding(s)
- Outdated: anyhow
- Outdated: bstr
- Outdated: byte-unit
- Outdated: chrono
- Outdated: clap
- Outdated: clap_complete
- Outdated: crossbeam
- Outdated: human_format
- Outdated: jiff
- Outdated: libc
- Outdated: log
- Outdated: open
- Outdated: owo-colors
- Outdated: serde
- Outdated: toml
- Outdated: trash
- Outdated: unicode-segmentation
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-98795a3e963141fdb1046658ff6c94c1/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-98795a3e963141fdb1046658ff6c94c1/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 . | 32 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 6 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 5 | 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 |